Method, device and system for communication between network management system and network element

Abstract

The embodiments of the present application provide a method, device and system for communication between a network management system and a network element. The method includes: the network management system sends a query message to a gateway network element GNE in a second routing domain, 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, 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, the response message indicates the routing information of the GNE in the second routing domain communicating with the first NGNE; the network management system establishes a communication connection with the first NGNE based on the response message. This method is beneficial to improving the efficiency of establishing a connection between the network management system and the network element, while ensuring that the network management system can access the network element through an appropriate path.

Description

Technical Field

[0001] The embodiments of the present application relate to network communication technology, and more specifically, to a method, device and system for communication between a network management system and network elements. Background Art

[0002] The data communication network (DCN) system provides management access and management control information communication functions for network devices, allowing remote deployment and management of each device from the network management system (NMS) center. A DCN system consists of an NMS, a gateway network element (GNE), a non-gateway network element (NGNE), and the connecting lines or networks between them. The NMS and the GNE are connected and can directly access each other; the GNE and multiple NGNEs directly or indirectly connected to it form a DCN routing domain. The GNEs within the DCN routing domain can directly access each other, and the GNEs within the DCN routing domain can transmit messages based on routing protocols.

[0003] In existing network applications, a corresponding GNE is assigned to each NGNE through manual planning, so that each NGNE can communicate with the NMS through the corresponding GNE. As the scale of the network continues to grow, when a new NGNE to be registered is added to the existing network, it is difficult to configure a suitable GNE for the network element to be registered based on the manual planning method, resulting in the NMS accessing the network element through a suboptimal path, and the problem of low efficiency in establishing a connection between the network management system and the network element. In addition, when a GNE fails (for example, it is disconnected from management), it is necessary to manually reselect the GNE for the NGNE corresponding to the failed GNE. The structure and scale of the existing network are usually complex. Once a failure occurs, it is difficult to restore management for the affected NGNE in a short time. The GNE disconnection cannot be accurately reported in the first time, affecting the actual business recovery time. Summary of the Invention

[0004] The embodiments of the present application provide a method, network element and system for communication between a network management system and a network element. The method is beneficial to improving the efficiency of establishing a connection between the network management system and the network element while ensuring that the network management system can access the network element through an appropriate path.

[0005] In a first aspect, a method for communication 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 within a second routing domain, the query message being used to obtain routing information of a first non-gateway network element NGNE, the first NGNE being an NGNE to be registered, the routing domain where the network management system is located being a first routing domain, and the first routing domain being different from the second routing domain; the network management system receives a response message sent by the GNE within the second routing domain, the response message indicating routing information for communication between the GNE within the second routing domain and the first NGNE; and the network management system establishes a communication connection with the first NGNE based on the response message.

[0006] In the above technical solution, the network management system in the first routing domain can 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 based on the obtained routing information of the first NGNE to be registered. The routing information of the first NGNE to be registered includes the routing information of the communication between the first NGNE to be registered and each GNE in the second routing domain. When determining to establish a communication connection with the first NGNE, the network management system fully considers the routing information of the communication between the first NGNE and each GNE in the second routing domain, so that the network management system can access the network element through an appropriate path. In addition, in the above implementation method, the manual determination of the GNE for the first NGNE to be registered is avoided, which is conducive to improving the efficiency of the network management system in establishing a connection with the network element. In other words, this method is conducive to improving the efficiency of the network management system in establishing a connection with the network element, while ensuring that the network management system can access the network element through an appropriate path.

[0007] In one possible design, 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 is used for the first NGNE to establish a communication connection with the GNE in the second routing domain.

[0008] In one example, the preset IP address of the first NGNE may refer to the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is the IP address configured at the factory for the first NGNE. In another example, the preset IP address of the first NGNE may refer to an IP address set by a user for the first NGNE based on the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is different from the IP address configured at the factory for the first NGNE. In other words, in this application, the preset IP address of the first NGNE is not specifically limited.

[0009] In another possible design, the second routing domain includes a first GNE, and the response message includes a first response message. The first response message is used to indicate first routing information of the communication between the first GNE and the first NGNE. The first routing information includes an identifier of a first port, a first network element identifier NEID and the first IP address. The first port is the 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. The network management system establishes a communication connection with the first NGNE based on the response message, including: the network management system generates second routing information based on the second IP address, the first NEID and the identifier of the first port. The second IP address is used to uniquely identify the first GNE. The second IP address is the IP address used when the first GNE establishes a communication connection with the network management system. The second routing information indicates that the first NGNE has completed registration with the network management system. The second routing information includes a mapping relationship between the second IP address, the first NEID and the first port.

[0010] In another possible design, the second routing domain also includes a second GNE, and the response message also includes a second response message. The second response message indicates third routing information for communication between the second GNE and the first NGNE, and the third routing information includes a second routing overhead. Before the network management system establishes a communication connection with the first NGNE based on the response message, the method also includes: the network management system determines that the first GNE is the primary GNE of the first NGNE based on the first routing overhead and the second routing overhead, and determines that the second GNE is the backup GNE of the first NGNE, and the first routing information also includes the first routing overhead.

[0011] In the above technical solution, the network management system determines that the first GNE is the active GNE of the first NGNE and that the second GNE is the backup GNE of the first NGNE by comparing the first routing cost and the second routing cost, so that the network management system can access the network element through an appropriate path.

[0012] In another possible design, the third routing information also includes the identifier of the second port and the first NEID, the second port is the port of the second GNE connected to the first NGNE, and the network management system establishes a communication connection with the first NGNE based on the response message, including: in the event of a failure of the first GNE, the network management system generates fourth routing information based on the third IP address, the first NEID, the identifier of the second port and the second routing cost, the third IP address is used to uniquely identify the second GNE, the third IP address is the IP address used when the second GNE establishes a communication connection with the network management system, the fourth routing information indicates that the first NGNE has completed registration with 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 cost.

[0013] The third IP address is different from the second IP address.

[0014] In the above technical solution, when the first GNE fails, the network management system can establish a communication connection with the first NGNE through its backup GNE (ie, the second GNE), which is beneficial to improving the efficiency of establishing connections between the network management system and network elements.

[0015] In another possible design, the first routing overhead is determined based on at least one of the following information: 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 based on at least one of the following information: path information from the second GNE to the first NGNE, the load condition of the second GNE, or the delay information from the second GNE to the first NGNE.

[0016] In the above technical solution, the first routing cost and the second routing cost can be determined based on actual needs, allowing the network management system to access the network element through the appropriate path. For example, if the path length from the network management system to the first NGNE needs to be minimized, the first routing cost can be determined based solely on the path information from the first GNE to the first NGNE, and the second routing cost can be determined based solely on the path information from the second GNE to the first NGNE.

[0017] According to a second aspect, a method for communication between a network management system and a network element is provided. The method includes: after a first gateway network element (GNE) establishes a communication connection with a first non-gateway network element (NGNE), the first GNE receives a query message sent by the network management system, the query message being used to obtain routing information of the first NGNE, the first NGNE being an NGNE to be registered, the routing domain in which the network management system is located being a first routing domain, the second routing domain including the first GNE and the first NGNE, the first routing domain being different from the second routing domain; the first GNE generating a first response message based on the query message and a routing table of the first GNE, the first response message indicating first routing information for communication between the first GNE and the first NGNE, and the first GNE sending the first response message to the network management system.

[0018] In the above technical solution, after a first GNE in the second routing domain receives a query message from a network management system in the first routing domain, the first GNE sends first routing information for communication between the first GNE and the first NGNE to the network management system. This allows the network management system to determine the appropriate path for accessing the first NGNE based on the first routing information. Furthermore, this implementation avoids manual intervention and improves the efficiency of establishing connections between the network management system and network elements.

[0019] In one possible design, the query message includes a first Internet Protocol IP address, which is a preset IP address of the first NGNE. The first IP address is used for the first NGNE to establish a communication connection with a GNE in the second routing domain, and the GNE in the second routing domain includes the first GNE.

[0020] 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, and the first NEID is used to uniquely identify the first NGNE. The first GNE generates a first response message based on the query message and the routing table of the first GNE, including: the first GNE determines the first NEID based on the first IP address and the first correspondence; the first GNE determines the path information of communication between the first GNE and the first NGNE based on the second IP address and the first NEID, the second IP address is used to uniquely identify the first GNE, and the second IP address is the IP address used by the first GNE to establish a communication connection with the network management system; the first GNE generates the first response message based on the path information.

[0021] In another possible design, the first routing information includes an identifier of a first port, a first routing cost, the first NEID and the first IP address, wherein the first port is a port of the first GNE to which the first NGNE is connected, and the first routing cost is a routing cost for the first GNE to communicate with the first NGNE.

[0022] In another possible design, the first routing cost is determined based on at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE.

[0023] According to a third aspect, a first communication device is provided, which is applied to a network management system. The device includes: a transceiver unit, configured to send a query message to a gateway network element GNE within a second routing domain, wherein the query message is used to obtain routing information of a first non-gateway network element NGNE, wherein the first NGNE is an NGNE to be registered, and the routing domain where the network management system is located is a first routing domain, which is different from the second routing domain; the transceiver unit is also configured to receive a response message sent by the GNE within the second routing domain, wherein the response message indicates routing information of communication between the GNE within the second routing domain and the first NGNE; and a processing unit, configured to establish a communication connection with the first NGNE based on the response message.

[0024] In one possible design, 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 is used for the first NGNE to establish a communication connection with the GNE in the second routing domain.

[0025] In another possible design, the second routing domain includes a first GNE, and the response message includes a first response message. The first response message is used to indicate first routing information of the communication between the first GNE and the first NGNE. The first routing information includes an identifier of a first port, a first network element identifier NEID and the first IP address. The first port is the 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. The network management system establishes a communication connection with the first NGNE based on the response message, including: the network management system generates second routing information based on the second IP address, the first NEID and the identifier of the first port. The second IP address is used to uniquely identify the first GNE. The second IP address is the IP address used when the first GNE establishes a communication connection with the network management system. The second routing information indicates that the first NGNE has completed registration with the network management system. The second routing information includes a mapping relationship between the second IP address, the first NEID and the first port.

[0026] In another possible design, the second routing domain also includes a second GNE, and the response message also includes a second response message. The second response message indicates third routing information for communication between the second GNE and the first NGNE, and the third routing information includes a second routing overhead. The processing unit is also used to: determine, based on the first routing overhead and the second routing overhead, that the first GNE is the primary GNE of the first NGNE, and determine that the second GNE is the backup GNE of the first NGNE, and the first routing information also includes the first routing overhead.

[0027] In another possible design, the third routing information also includes the identifier of the second port and the first NEID, and the second port is the port of the second GNE to which the first NGNE is connected. The processing unit is also used to: in the event of a failure of the first GNE, generate fourth routing information based on the third IP address, the first NEID, the identifier of the second port and the second routing overhead. The third IP address is used to uniquely identify the second GNE. The third IP address is the IP address used when the second GNE establishes a communication connection with the network management system. The fourth routing information indicates that the first NGNE has completed registration with the network management system. The fourth routing information includes a mapping relationship between the third IP address, the first NEID, the second port and the second routing overhead.

[0028] In another possible design, the first routing overhead is determined based on at least one of the following information: 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 based on at least one of the following information: path information from the second GNE to the first NGNE, the load condition of the second GNE, or the delay information from the second GNE to the first NGNE.

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

[0030] In one possible design, the query message includes a first Internet Protocol IP address, which is a preset IP address of the first NGNE. The first IP address is used for the first NGNE to establish a communication connection with a GNE in the second routing domain, and the GNE in the second routing domain includes the first GNE.

[0031] 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 the first network element identifier NEID and the first IP address, and the first NEID is used to uniquely identify the first NGNE. The processing unit is also used to: determine the first NEID based on the first IP address and the first correspondence; determine the path information of communication between the first GNE and the first NGNE based on the 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 the IP address used when the first GNE establishes a communication connection with the network management system; and generate the first response message based on the path information.

[0032] In another possible design, the first routing information includes an identifier of a first port, a first routing cost, the first NEID and the first IP address, the first port is the port of the first GNE to which the first NGNE is connected, and the first routing cost is the routing cost for the first GNE to communicate with the first NGNE.

[0033] In another possible design, the first routing cost is determined based on at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE.

[0034] In a fifth aspect, a first communication device is provided, which has the function of implementing the first communication device described in the third aspect. The function can be implemented based on hardware or by executing corresponding software based on hardware. The hardware or software includes one or more modules corresponding to the above functions.

[0035] In one possible design, the structure of the first communication device includes a processor, which is configured to support the first communication device to perform corresponding functions in the above method.

[0036] The first communication device may further include a memory, which is coupled to the processor and stores program instructions and data necessary for the first communication device.

[0037] In another possible design, the first communication device includes: a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus. The processor is coupled to the transmitter, receiver, random access memory, and read-only memory, respectively, via the bus. When the first communication device needs to be operated, it is booted via a basic input / output system embedded in the read-only memory or a bootloader in an embedded system, guiding the first communication device into normal operation. After the first communication device enters normal operation, an application program and an operating system are executed in the random access memory, causing the processor to execute the method of the first aspect or any possible implementation of the first aspect.

[0038] In a sixth aspect, a second communication device is provided, which has the function of implementing the second communication device described in the fourth aspect. The function can be implemented based on hardware or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0039] In one possible design, the structure of the second communication device includes a processor, which is configured to support the second communication device to perform corresponding functions in the above method.

[0040] The second communication device may further include a memory, which is coupled to the processor and stores program instructions and data necessary for the second communication device.

[0041] In another possible design, the second communication device includes: a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus. The processor is coupled to the transmitter, receiver, random access memory, and read-only memory, respectively, via the bus. When the second communication device needs to be operated, it is booted via a basic input / output system embedded in the read-only memory or a bootloader in an embedded system, guiding the second communication device into normal operation. After the second communication device enters normal operation, an application program and an operating system are executed in the random access memory, causing the processor to execute the method of the second aspect or any possible implementation of the second aspect.

[0042] In a seventh aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the above-mentioned first aspect or any possible execution method of the first aspect.

[0043] In an eighth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the second aspect or any possible execution method of the second aspect.

[0044] In a ninth aspect, a computer-readable medium is provided, wherein the computer-readable medium stores program code, and when the computer program code is executed on a computer, the computer executes the method of the first aspect or any possible execution of the first aspect. Such computer-readable storage includes, but is 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 drive.

[0045] In a tenth aspect, a computer-readable medium is provided, the computer-readable medium storing program code, which, when executed on a computer, causes the computer to execute the method of the second aspect or any possible execution of the second aspect. Such computer-readable storage includes, but is 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 drive.

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

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

[0048] In a thirteenth aspect, a system is provided, which includes the first communication device as described in the third aspect and the second communication device as described in the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 It is a schematic block diagram of the system architecture 100 provided in an embodiment of the present application.

[0050] Figure 2 It is a schematic flowchart of a method 200 for communication between a network management system and a network element provided in an embodiment of the present application.

[0051] Figure 3 This is a schematic interaction diagram of a method for communication between a network management system and a network element provided in an embodiment of the present application.

[0052] Figure 4 This is a schematic interaction diagram of another method for communication between a network management system and a network element provided in an embodiment of the present application.

[0053] Figure 5 It is a schematic diagram of a specific embodiment of the method for communication between a network management system and a network element provided in an embodiment of the present application.

[0054] Figure 6 It is a schematic diagram of a specific embodiment of the method for communication between a network management system and a network element provided in an embodiment of the present application.

[0055] Figure 7It is a schematic structural diagram of a first communication device 700 provided in an embodiment of the present application.

[0056] Figure 8 It is a schematic structural diagram of a second communication device 800 provided in an embodiment of the present application.

[0057] Figure 9 Schematic diagram of the hardware structure of a communication device 900 provided in an embodiment of the present application.

[0058] Figure 10 It is a schematic structural diagram of a system 1000 provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0060] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0061] In this application, the terms "first", "second", "third", etc. are used to distinguish identical or similar items with basically the same effects and functions. There is no logical or temporal dependency between "first", "second" and "third", nor are there any limitations on quantity and execution order.

[0062] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0063] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0064] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0065] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0066] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0067] The following describes in detail the relevant technologies of the embodiments of this application:

[0068] First, combine Figure 1 Introduce the system architecture applicable to the embodiments of the present application.

[0069] Figure 1 1 is a schematic block diagram of the system architecture 100 provided in an embodiment of the present application. Figure 1 As shown, the system architecture 100 includes but is not limited to multiple routing domains. Figure 1 Taking routing domain 1 and routing domain 2 as examples, the system architecture 100 includes routing domain 1, an Internet Protocol (IP) bearer network 120, and routing domain 2. A network device within any routing domain can propagate the route of the network device to network devices other than the network device within the routing domain by means of routing forwarding.

[0070] Routing domain 1 includes but is not limited to a network management system (NMS), which is also called a network manager. NMS can provide comprehensive network element and network-level alarm, security, performance, topology, log, inventory, report, and database management functions in the form of a graphical user interface (GUI). NMS supports batch configuration of network element services by configuring templates, importing data tables, and loading configuration files. It also supports backup, recovery, and synchronization of network management and network element data, and can easily implement rapid service provisioning in a GUI manner. For example, Figure 1 The routing domain 1 shown in FIG. 1 includes only one NMS 110. Optionally, routing domain 1 may also include multiple NMSs. The NMS in routing domain 1 can communicate with the gateway network element (GNE) in routing domain 2 via the IP bearer network 120. The NMS in routing domain 1 and the GNE in routing domain 2 can communicate via, but are not limited to, the Transmission Control Protocol (TCP). Communication between the NMS and the gateway network element is also called external DCN communication. Optionally, when routing domain 1 includes multiple NMSs, external DCN communication also includes communication between the multiple NMSs.

[0071] Routing domain 2 includes but is not limited to GNE, DCN140 and NGNE. GNE and NGNE can be collectively referred to as network elements. GNE refers to a network element directly connected to the network management system, or a network element whose application layer directly communicates with the application layer of the network management system. NGNE refers to a network element that communicates with GNE and meets the management requirements of GNE. GNE and NGNE are based on DCN140 and use Ethernet-based point-to-point protocol (PPPoE) for communication. Communication between network elements is also called internal DCN communication. For example, Figure 1 2 GNEs (i.e., GNE.A 130 and GNE.B 131) and 2 NGNEs (i.e., NGNE.A 151 and NGNE.B 152) are shown. Both of these GNEs may communicate with NGNE.A 151 or NGNE.B 152, or only one of these two GNEs may communicate with NGNE.A 151 or NGNE.B 152. Optionally, routing domain 2 may further include fewer (e.g., one) or more (e.g., three, four, or ten) GNEs and NGNEs.

[0072] Based on the above Figure 1In the illustrated system architecture 100, NMS 110 can access NGNEs (e.g., NGNE.A151 or NGNE.B152) through GNEs (e.g., GNE.A130 or GNE.B131). NMS 110 can access NGNEs using the GNE's IP address and the NGNE's network element identifier (NEID). The NEID of an NGNE corresponds to its factory-configured IP address. The NGNE can establish a communication connection with the GNE using its factory-configured IP address. A corresponding relationship is then recorded in the GNE's routing table, indicating the corresponding relationship between the NEID of the NGNE and its factory-configured IP address. When NMS 110 accesses NGNE through GNE, NMS 110 uses the IP address of GNE to find the GNE. Then, the GNE determines the destination IP corresponding to the destination NEID based on the destination NEID carried in the message sent by NMS 110 and the correspondence between NEID and IP address recorded in the routing table. Then, the GNE successfully finds the destination NGNE based on the destination IP, thereby enabling NMS 110 to access NGNE through GNE.

[0073] It should be understood that the above Figure 1 This is for illustration only and does not constitute any limitation on the system architecture applicable to the embodiments of this application. Figure 1 The routing domain 2 in the example may also include a larger number of GNEs or NGNEs. Figure 1 The routing domain 1 in can also include more NMSs. Figure 1 NGNE.A 151 and / or NGNE.B 152 in the NGNE may also be NGNEs to be registered.

[0074] Figure 2 This is a schematic flow chart of a method 200 for communication between a network management system and a network element provided in an embodiment of the present application. The method 200 can be applied to, but is not limited to, the above Figure 1 When the method 200 is applied to the system architecture 100, the network management system in the method 200 may be the NMS 110 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 (in this case, the NGNE.B 152 in the system architecture 100 is the NGNE to be registered). Figure 2As shown, the method 200 includes steps 210 to 230. Steps 210 to 230 are described below.

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

[0076] In step 210, the network management system may periodically send query messages to the GNEs in the second routing domain to obtain routing information of the first NGNE. The length of the period is not specifically limited, for example, the period may be 1 hour, 2 hours, or 5 hours.

[0077] 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 communication between the GNE in the second routing domain and the first NGNE.

[0078] Step 230: The network management system establishes a communication connection with the first NGNE according to the response message.

[0079] In some implementations, the second routing domain in the above method 200 may include only one GNE (ie, the first GNE) that communicates with the first NGNE. For ease of description, this implementation is referred to as implementation 1 below. Figure 3 The method for implementing method 1 is specifically introduced and will not be described in detail here.

[0080] In other implementations, the second routing domain in the above method 200 may include multiple GNEs that communicate with the first NGNE. For ease of description, this implementation is referred to as implementation 2 below. Figure 4 The method for implementing the second method is specifically introduced and will not be described in detail here.

[0081] The following describes the implementation methods one and two in detail.

[0082] Implementation method 1:

[0083] like Figure 3 As shown, when the second routing domain may include only one GNE (i.e., the first GNE) that communicates with the first NGNE, implementation method 1 may include steps 310 to 340. Optionally, implementation method 1 may also include steps 350 and 360. Steps 310 to 360 are described below.

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

[0085] The query message in step 310 includes a first Internet Protocol (IP) address, which is a preset IP address of the first NGNE and is used for the first NGNE to establish a communication connection with the first GNE.

[0086] Optionally, before step 310, steps 350 and 360 may be included. The order in which steps 350 and 360 are performed is not specifically limited. For example, step 350 may be performed before step 360. For another example, step 360 may be performed before step 350. Steps 350 and 360 are described below.

[0087] In the embodiments of the present application, the preset IP address of the first NGNE may refer to the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is the IP address configured at the factory for the first NGNE. In another example, the preset IP address of the first NGNE may refer to an IP address set by a user for the first NGNE based on the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is different from the IP address configured at the factory for the first NGNE. In other words, in the present application, the preset IP address of the first NGNE is not specifically limited.

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

[0089] The first GNE uses the first IP address to establish a communication connection with the first NGNE, which may include the following steps: the first NGNE uses the first IP address to access the DCN in the second routing domain, the first NGNE runs a routing protocol (such as but not limited to open shortest path first (OSPF)) with the GNE and / or NGNE in the second routing domain through the communication port of the first NGNE. first, OSPF) protocol, and diffuses the first IP address to the outside; the first NGNE also learns the routes diffused from the GNE and / or NGNE in the second routing domain, but the first NGNE itself does not perceive the role and position of the first GNE in the second routing domain; at the same time, the first GNE in the second routing domain learns the first IP address through route diffusion; thereafter, the first GNE can use the first IP address to access the first NGNE, that is, the first GNE establishes a communication connection with the first NGNE. In specific implementation, the first GNE can allocate a port of the first GNE according to the first IP address, and the first GNE establishes a communication connection with the first NGNE through a port of the first GNE and the first IP address. It can be understood that after the first GNE establishes a communication connection with the first NGNE, the first corresponding relationship will be recorded in the routing table of the first GNE. The first corresponding relationship is the corresponding relationship between the first network element identifier NEID and the first IP address. The first NEID is used to uniquely identify the first NGNE. The first NEID refers to the device identifier of the first NGNE.

[0090] Step 360: The network management system establishes a communication connection with the first GNE using the second IP address, where the second IP address is used to uniquely identify the first GNE.

[0091] 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 specifically limited. In some implementations, the network management system may include the following steps: the network management system receives an access request message from the first GNE, the access request message requesting to establish a communication connection with the network management system using the second IP address, the access request message including the second IP address; and the network management system establishes a communication connection with the first GNE using the second IP address. Optionally, the access request message may also carry the port identifier of the first GNE. Based on this, the network management system may establish a communication connection with the first GNE using the second IP address and the port identifier of the first GNE. It is understood that after the network management system establishes a connection with the first GNE, the network management system records information regarding the communication connection establishment with the first GNE, which includes at least the second IP address. Optionally, this information may also include the port identifier of the first GNE. It is understood that when the network management system communicates with the first GNE, the network management system is responsible for managing the first GNE.

[0092] Step 320: The first GNE generates a first response message according to the query message and the routing table of the first GNE. The first response message indicates first routing information for communication between the first GNE and the first NGNE.

[0093] In the above step 320, the first GNE generates a first response message based on the query message and the routing table of the first GNE, which may include the following steps: the first GNE determines the first NEID based on the first IP address and the first correspondence; the first GNE determines the path information of the communication between the first GNE and the first NGNE based on the second IP address and the first NEID, the second IP address is used to uniquely identify the first GNE, and the second IP address is the IP address used when the first GNE establishes a communication connection with the network management system; the first GNE generates a first response message based on the path information.

[0094] The first routing information includes a first port identifier, a first routing cost, a first NEID, and a first IP address. The first routing cost is the routing cost for communication between the first GNE and the first NGNE. The first routing cost is determined based on at least one of the following information: path information from the first GNE to the first NGNE, the load of the first GNE, or latency information from the first GNE to the first NGNE. The load of the first GNE can be understood as the number of NGNEs communicating with the first GNE, or the number of NGNEs managed by the first GNE. It is understood that if the first GNE communicates with one NGNE, the first GNE is responsible for managing the one NGNE.

[0095] Optionally, in some other implementations, when the first GNE fails to successfully establish communication with the first NGNE, that is, 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 based on the query message and the routing table of the first GNE. In this case, the first response message is used to indicate that the first GNE and the first NGNE are in different routing domains.

[0096] Step 330: The network management system receives a first response message sent by the first GNE.

[0097] Step 340: The network management system establishes a communication connection with the first NGNE according to the first response message.

[0098] In the above step 340, the network management system establishes a communication connection with the first NGNE based on the response message, including: the network management system generates second routing information based on the second IP address, the first NEID and the identifier of the first port, the second routing information indicating that the first NGNE is registered with the network management system, and the second routing information includes a mapping relationship between the second IP address, the first NEID and the first port.

[0099] Optionally, after step 340, the following step may be included: the network management system creates a management instance of the first NGNE. This creation of the management instance of the first NGNE by the network management system can be understood as a software action. In specific implementation, the network management system allocates a memory block to the first NGNE. This memory is used to store information about the first NGNE's communications, the current state configuration, and other information that can be presented, and presents it in a visual manner.

[0100] Optionally, after the above step 340, the following step may also be included: the network management system may also determine whether the network management system can reach the first NGNE through the first GNE based on the first routing information. Exemplarily, the network management system may generate a probe message based on the first routing information and periodically send the probe message to the first GNE and the first NGNE. The probe message may include the second IP address and / or the first NEID. The network management system receives a response from the first GNE and the first NGNE within a preset time and determines that the first NGNE can be reached through the first GNE. Optionally, if the network management system does not receive a response from the first GNE and the first NGNE within the preset time and determines that the first NGNE cannot be reached through the first GNE, the network management system may deem that the first GNE and the first NGNE are out of management.

[0101] Implementation method 2:

[0102] In the second implementation, the second routing domain may include multiple GNEs that communicate with the first NGNE. Figure 4 As shown in FIG, it is shown that both GNEs (ie, the first GNE and the second GNE) in the second routing domain can communicate with the first GNE. Figure 4 It can be seen that the second implementation method may include steps 410 to 450. Optionally, the second implementation method may also include steps 460 to 480. The following describes steps 410 to 480 in detail.

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

[0104] Step 410: The network management system sends a query message to the first GNE. The query message is used to obtain routing information of the first NGNE. The first NGNE is the NGNE to be registered.

[0105] The query message in step 410 includes the first IP address, which is a preset IP address of the first NGNE and is used for the first NGNE to establish a communication connection with the first GNE.

[0106] Optionally, steps 460, 461, and 470 may be performed before step 410. The order in which steps 460, 461, and 470 are performed is not specifically limited. For example, step 470 may be performed before step 460. For another example, step 460 may be performed before step 470. Steps 460 and 470 are described below.

[0107] In the embodiments of the present application, the preset IP address of the first NGNE may refer to the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is the IP address configured at the factory for the first NGNE. In another example, the preset IP address of the first NGNE may refer to an IP address set by a user for the first NGNE based on the IP address configured at the factory for the first NGNE. In this implementation, the preset IP address of the first NGNE is different from the IP address configured at the factory for the first NGNE. In other words, in the present application, the preset IP address of the first NGNE is not specifically limited.

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

[0109] It is 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. 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. The first NEID refers to the device identifier of the first NGNE.

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

[0111] It is understandable that after the second GNE establishes a communication connection with the first NGNE, the first corresponding relationship will be recorded in the routing table of the second GNE.

[0112] The method for establishing a communication connection in the above steps 460 and 461 is the same as the principle of the method for establishing a communication connection in the above step 350. For details, please refer to the relevant description in the above step 350, which will not be repeated here.

[0113] In step 470, the network management system establishes a communication connection with the first GNE using the second IP address, and establishes a communication connection with the second GNE using the third IP address. 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.

[0114] The third IP address is different from the second IP address.

[0115] The method for establishing a communication connection in the above step 470 is the same as the principle of the method for establishing a communication connection in the above step 360. For details, please refer to the relevant description in the above step 360, which will not be repeated here.

[0116] Step 411: The network management system sends a query message to the second GNE.

[0117] Step 420: The first GNE generates a first response message according to the query message and the routing table of the first GNE. The first response message indicates first routing information for communication between the first GNE and the first NGNE.

[0118] The method described in the above step 420 is the same as the method described in the above step 320. For details, please refer to the relevant description in the above step 320, which will not be repeated here.

[0119] Step 421: The second GNE generates a second response message according to the query message and the routing table of the second GNE. The second response message indicates third routing information for communication between the second GNE and the first GNE.

[0120] In the above step 421, the second GNE generates a second response message based on the query message and the routing table of the first GNE, which may include the following steps: the second GNE determines the first NEID based on the first IP address and the first correspondence; the second GNE determines the path information for communication between the second GNE and the first NGNE based on the third IP address and the first NEID, where the third IP address is used to uniquely identify the second GNE, and the third IP address is the IP address used when the second GNE establishes a communication connection with the network management system; the second GNE generates a second response message based on the path information.

[0121] The second response message indicates third routing information for communication between the second GNE and the first NGNE. The third routing information includes a second routing cost, i.e., the second routing cost is the routing cost for communication between the second GNE and the first NGNE. The second routing cost can be determined based on at least one of the following information: path information from the second GNE to the first NGNE, load status of the second GNE, or latency information from the second GNE to the first NGNE.

[0122] Optionally, the third routing information further includes an identifier of a second port and the first NEID, where the second port is a port of a second GNE to which the first NGNE is connected.

[0123] In the embodiment of the present application, the execution order of the above steps 410 to 421 is not specifically limited, but it is necessary to ensure that step 410 is executed before step 420, and step 411 is executed before step 421.

[0124] Step 430: The first GNE sends a first response message to the network management system.

[0125] Step 431: The second GNE sends a second response message to the network management system.

[0126] Step 440: The network management system determines, based on the response message, that the first GNE is the active GNE of the first NGNE and that the second GNE is the backup GNE of the first NGNE. The response message includes a first response message and a second response message.

[0127] The network management system determines, based on the response message, that the first GNE is the primary GNE of the first NGNE, and determines that the second GNE is the backup GNE of the first NGNE, including: the network management system determines, based on the first routing overhead and the second routing overhead, that the first GNE is the primary GNE of the first NGNE, and determines that the second GNE is the backup GNE of the first NGNE, and the first routing information also includes the first routing overhead.

[0128] For example, a network management system determines, based on a first routing cost and a second routing cost, that a first GNE is the primary GNE of the first NGNE and that a second GNE is the backup GNE of the first NGNE. For example, if the first routing cost is determined based on path information from the first GNE to the first NGNE, and the second routing cost is determined based on path information from the second GNE to the first NGNE, the network management system determines, through comparison, that the first routing cost is less than the second routing cost, thereby determining 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. The fact that the first routing cost is less than the second routing cost can be understood as meaning that the path length from the first GNE to the first NGNE, as indicated by the first routing cost, is less than the path length from the second GNE to the first NGNE, as indicated by the second routing cost. For another example, if the first routing cost is determined based on the load of the first GNE, and the second routing cost is determined based on the load of the second GNE, the network management system determines, through comparison, that the value of the first routing cost is less than the value of the second routing cost, thereby determining 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. The fact that the value of the first routing cost is less than the value of the second routing cost can be understood as meaning that the load of the first GNE indicated by the value of the first routing cost is less than the load of the second GNE indicated by the value of the second routing cost. For another example, if the first routing cost is determined based on the delay information from the first GNE to the first NGNE, and the second routing cost is determined based on the delay information from the second GNE to the first NGNE, the network management system determines, through comparison, that the value of the first routing cost is less than the value of the second routing cost, thereby determining 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. The first routing cost is smaller than the second routing cost. This means that the delay from the first GNE to the first NGNE indicated by the first routing cost is smaller than the delay from the second GNE to the first NGNE indicated by the second routing cost.

[0129] Step 450: The network management system establishes a communication connection with the first NGNE through the first GNE.

[0130] The method for establishing a communication connection in the above step 450 is the same as the principle of the method for establishing a communication connection in the above step 340. For details, please refer to the relevant description in the above step 340, which will not be repeated here.

[0131] Optionally, after step 450, the following step may be further included: the network management system creates a management instance of the first NGNE. This creation of the management instance of the first NGNE by the network management system can be understood as a software action. In specific implementation, the network management system allocates a memory block to the first NGNE. This memory is used to store information about the first NGNE's communications, as well as current status and configuration information that can be presented, and presents the information in a visual manner.

[0132] Optionally, after step 450, the following step may be further included: the network management system may also determine whether the network management system can reach the first NGNE through the first GNE based on the first routing information. Exemplarily, the network management system may generate a probe message based on the first routing information and periodically send the probe message to the first GNE and the first NGNE. The probe message may include the second IP address and / or the first NEID. The network management system receives a response from the first GNE and the first NGNE within a preset time and determines that the first NGNE can be reached through the first GNE. Optionally, if the network management system does not receive a response from the first GNE and the first NGNE within the preset time and determines that the first NGNE cannot be reached through the first GNE, the network management system may deem that the first GNE and the first NGNE are out of management.

[0133] Optionally, after the above step 450, step 480 may be further included.

[0134] Step 480: When the first GNE fails, the network management system establishes a communication connection with the first GNE through the second GNE.

[0135] In which, in the event that the first GNE fails, the network management system establishes a communication connection with the first NGNE through the second GNE, including: in the event that the first GNE fails, the network management system generates fourth routing information based on the third IP address, the first NEID, the identifier of the second port and the second routing overhead, the third IP address is used to uniquely identify the second GNE, the third IP address is the IP address used when the second GNE establishes a communication connection with the network management system, the fourth routing information indicates that the first NGNE is registered with 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.

[0136] Optionally, after the above step 480, the following step may also be included: the network management system may also determine whether the network management system can reach the first NGNE through the second GNE based on the first routing information. Exemplarily, the network management system may generate a probe message based on the first routing information and periodically send the probe message to the second GNE and the first NGNE. The probe message may include a third IP address and / or a first NEID. The network management system receives a response from the second GNE and the first NGNE within a preset time and determines that the first NGNE can be reached through the second GNE. Thereafter, the network management system will switch from the current state of accessing the first NGNE through the first GNE to the state of accessing the second NGNE through the second GNE. Optionally, if the network management system does not receive a response from the second GNE and the first NGNE within the preset time and determines that the first NGNE cannot be reached through the second GNE, the network management system may deem that the second GNE and the first NGNE are out of management.

[0137] Optionally, after step 480, the following step may be further included: the network management system updates the information of the first GNE recorded in the network management system, where the updated information of the first GNE indicates that the first GNE has failed. Similarly, the network management system may also update the information of the second GNE recorded in the network management system, where the updated information of the second GNE indicates that the second GNE is the active GNE of the first GNE.

[0138] In an embodiment of the present application, the network management system within the first routing domain can proactively query the GNE within the second routing domain for the routing information of the first NGNE to be registered, and determine a suitable GNE for the first NGNE to be registered based on the obtained routing information of the first NGNE to be registered. This method is beneficial to improving the efficiency of establishing a connection between the network management system and the network element while ensuring that the network management system can access the network element through a suitable path. Among them, the network management system queries the routing of the first NGNE to be registered from each GNE communicating with the network management system, and by comparing the routing cost of each GNE with the first NGNE to be registered, the network management system can obtain the optimal path to access the first NGNE to be registered. In the above implementation process, the network management system can periodically query the routing information of the first NGNE to be registered from the GNE communicating with the network management system, and determine the optimal routing information for accessing the first NGNE to be registered through the network management system based on the queried routing information of the first NGNE to be registered. The entire process does not require the participation of operation and maintenance personnel, which is beneficial to improving the efficiency of establishing a connection between the network management system and the network element. In addition, when the network management system considers the GNE load when determining the primary GNE for the first NGNE to be registered based on the acquired routing information of the first NGNE to be registered, it can avoid that the GNE manages too many NGNEs and affects the configuration of normal services.

[0139] In the above, combined Figures 2 to 4 The network management system and the method for network element communication provided by the embodiment of the present application are introduced. Figure 5 and Figure 6 A specific embodiment of the method for communication between a network management system and a network element provided in an embodiment of the present application is introduced. Figure 5 and Figure 6 The examples are only for helping those skilled in the art to understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Figure 5 and Figure 6 It is obvious that various equivalent modifications or changes can be made, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0140] See also Figure 5 NGNE.B is shown with a dotted line. NGNE.B is the NGNE to be registered in routing domain 2. Figure 5 In the scenario shown, the method for communication between a network management system and a network element provided by the embodiment of the present application may include steps 510 to 570. Steps 510 to 570 are described in detail below.

[0141] Step 510: NGNE.B accesses the DCN using IP1 and establishes a communication connection with GNE.A.

[0142] Among them, IP1 can refer to the IP address configured by NGNE.B at the factory, such as Figure 5 As shown, IP1 is specifically 1.1.1.11. In a possible implementation, NGNE.B establishes a communication connection with GNE.A, which may include the following steps: NGNE.B accesses the DCN using IP1, and NGNE.B runs a routing protocol (such as but not limited to open shortest path first (OSPF)) with network elements in routing domain 2 (i.e., GNE.A, GNE.B, NGNE.A, and NGNE.B) through a communication port (i.e., NG.B-1 port). Pathfirst (OSPF) protocol, and diffuses IP1 to the outside; NGNE.B also learns the routes diffused from network elements in routing domain 2 (i.e., GNE.A, GNE.B, NGNE.A and NGNE.B), but NGNE.B itself does not perceive the role and position of GNE (i.e., GNE.A and GNE.B); at the same time, GNEs in routing domain 2 (i.e., GNE.A and GNE.B) learn IP1 through route diffusion; thereafter, GNEs in routing domain 2 (i.e., GNE.A and GNE.B) can use IP1 to establish a communication connection with NGNE.B. It should be noted that since NGNE and NMS are not in the same routing domain, GNE will not actively diffuse NGNE's routes to NMS. Figure 5 For example, since NGNE.B and NMS are not in the same routing domain, GNE (i.e. GNE.A or GNE.B) will not actively spread NGNE.B's route to NMS. Figure 5 As shown in the figure, GNE.A establishes a communication connection with NGNE.B through GA-1 port and IP1; GNE.B establishes a communication connection with NGNE.B through GB-1 port and IP1. After the communication connection is established, the corresponding relationship between IP1 and NEID1 is recorded in GNE.A's routing table, and the corresponding relationship between IP1 and NEID1 is recorded in GNE.B's routing table. NEID1 is the device ID of NGNE.B, as shown in the figure. Figure 5 As shown, the NEID is specifically 1-11.

[0143] Step 520: The NMS establishes a communication connection with the GNE in routing domain 2.

[0144] The NMS establishes a communication connection with the GNE in the routing domain 2, including: the NMS establishes a communication connection with GNE.A in the routing domain 2, and the NMS establishes a communication connection with GNE.B in the routing domain 2. The following takes the establishment of a communication connection between the NMS and GNE.A in the routing domain 2 as an example for introduction. The NMS establishes a communication connection with GNE.A in the routing domain 2, which may include the following steps: the NMS receives an access request message 1 sent by GNE.A, where the access request message 1 is used to request to establish a communication connection with the NMS using IP2, where IP2 is used to uniquely identify GNE.A, such as Figure 5 As shown, IP2 is specifically 1.1.10.11. Access request message 1 may include IP2; 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, NMS can establish a communication connection with GNE.A through IP2 and the port identifier of GNE.A. It can be understood that after NMS establishes a connection with GNE.A, the information on establishing a communication connection with GNE.A will be recorded in NMS, and this information includes at least IP2. Optionally, this information may also include the port identifier of GNE.A. Similarly, based on similar principles as above, NMS can establish a communication connection with GNE.B in routing domain 2 through IP3, and IP3 is used to uniquely identify GNE.B, such as Figure 5 As shown in the figure, IP3 is specifically 1.1.11.11.

[0145] In step 530, the operation and maintenance personnel input IP1 on the NMS side, triggering the NMS to send a query message to the GNE in routing domain 2. The query message is used to obtain the routing information of NGNE.B, and the query message includes IP1.

[0146] In step 530, triggering the NMS to send a query message to the GNEs in routing domain 2 includes: the NMS sending a query message to GNE.A in routing domain 2, and sending a query message to GNE.B in routing domain 2. After the NMS establishes a communication connection with the GNEs in routing domain 2, the NMS's routing table will record information about the GNEs in routing domain 2 (for example, but not limited to, the IP addresses of the GNEs in routing domain 2). Therefore, the NMS can send query messages to the GNEs in routing domain 2 based on the NMS's routing table.

[0147] Step 540: The GNE in routing domain 2 sends a response message to the NMS, where the response message indicates routing information for communication between the GNE in routing domain 2 and NGNE.B.

[0148] The response message includes a response message 1 and a response message 2. The response message 1 indicates routing information for communication between GNE.A and NGNE.B in routing domain 2. The response message 2 indicates routing information for communication between GNE.B and NGNE.B in routing domain 2.

[0149] Before step 540, the following step may also be included: After receiving the query message, GNE.A queries GNE.A's routing table to see if IP1 is recorded. If the mapping between IP1 and NEID1 is recorded in GNE.A's routing table, GNE.A then sends a response message 1 to the NMS. Response message 1 indicates routing information 1 for communication between GNE.A and NGNE.B. Routing information 1 may include routing cost 1 and the identifier of port GA-1. Cost A indicates the routing cost from GNE.A to NGNE.B. Optionally, if IP1 is not recorded in GNE.A's routing table, GNE.A sends a response message 1 to the NMS. Query response message 1 indicates that NGNE.B, corresponding to IP1, is not in the same routing domain as GNE.A. Based on the same principle, before step 540, the following step may also be included: After receiving the query message, GNE.B queries GNE.B's routing table to see if IP1 is recorded. If the mapping between IP1 and NEID1 is recorded in GNE.B's routing table, GNE.A sends a response message 1 to the NMS. Response message 1 indicates that NGNE.B, corresponding to IP1, is not in the same routing domain as GNE.A. Afterward, GNE.B sends a response message 2 to the NMS. Response message 2 indicates routing information 2 for communication between GNE.B and NGNE.B. Routing information 2 may include cost B and the identifier of the GB-1 port. Cost B indicates the cost of the route from GNE.B to NGNE.B. Optionally, if IP1 is not recorded in GNE.B's routing table, GNE.B sends a response message 2 to the NMS. Query response message 2 indicates that the NGNE.B corresponding to IP1 is not in the same routing domain as GNE.B.

[0150] The routing cost may be determined based on one or more of the following: GNE-to-NGNE path information, GNE load (ie, the number of NGNEs communicating with the GNE), or GNE-to-NGNE delay information.

[0151] 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, based on the response message.

[0152] The NMS determines, based on the response message, that GNE.A is the active GNE for NGNE.B and GNE.B is the backup GNE for NGNE.B, including: the NMS determines, based on cost A and cost B, that GNE.A is the active GNE for NGNE.B and GNE.B is the backup GNE for NGNE.B. In one possible implementation, when the NMS determines that cost A of GNE.A is less than cost B of GNE.B, the NMS determines that GNE.A is the active GNE for NGNE.B and GNE.B is the backup GNE for NGNE.B.

[0153] Step 560: The NMS establishes a communication connection with NGNE.B through GNE.A.

[0154] Among them, NMS establishes a communication connection with NGNE.B through GNE.A, including: NMS generates routing information 3 according to response message 1, routing information 3 indicates that NGNE.B has completed registration at NMS, routing information 3 includes NEID1:1-11, IP2:1.1.10.11, cost A, and the mapping relationship between GA ports, such as Figure 6 As shown, the mapping relationship is recorded in the routing table of the NMS. That is, the NMS generates routing information 3. It can be understood that the NMS establishes a communication connection with NGNE.B through GNE.A.

[0155] Optionally, after step 560, the following step may be included: the NMS creates a management instance for NGNE.B. This creation of the management instance for NGNE.B can be understood as a software action. In specific implementation, the NMS allocates a memory block for NGNE.B. This memory is used to store information about NGNE.B's communications, the current state and configuration, and other information, and presents it in a visual format.

[0156] Optionally, after step 560, the following step may be further performed: the NMS may further determine, based on routing information 1, whether NGNE.B is reachable from the NMS via GNE.A. For example, the NMS may generate a probe message based on routing information 1 and periodically send the probe message to GNE.A and NGNE.B. The probe message may include IP2 and / or NEID1. The NMS may receive a response from GNE.A and NGNE.B within a preset time and determine that NGNE.B is reachable via GNE.A. Optionally, if the NMS does not receive a response from GNE.A and NGNE.B within a preset time, it may determine that NGNE.B is unreachable via GNE.A. In this case, the NMS may determine that GNE.A and NGNE.B are disconnected.

[0157] Step 570: When GNE.A fails, the NMS establishes a communication connection with NGNE.B through GNE.B.

[0158] Among them, NMS establishes a communication connection with NGNE.B through GNE.B, including: NMS generates routing information 4 according to response message 2, routing information 4 indicates that NGNE.B has completed registration at NMS, routing information 4 includes NEID1:1-11, IP3:1.1.11.11, cost B, and the mapping relationship between GB ports, such as Figure 6 As shown, the mapping relationship is recorded in the routing table of the NMS. That is, the NMS generates routing information 4. It can be understood that the NMS establishes a communication connection with NGNE.B through GNE.B.

[0159] Exemplarily, the NMS may determine that GNE.A has failed in the following manner: the NMS may send a probe message to the GNE communicating with the NMS at fixed intervals. If the NMS receives a response from the GNE within a preset time, it determines that the GNE has not failed; if the NMS does not receive a response from the GNE within the preset time, it determines that the GNE has failed.

[0160] Above, combined Figures 1 to 6 The method for network management system and network element communication applicable to the embodiment of the present application is described in detail. Figures 7 to 10 The apparatus and system provided by the embodiments of the present application are described in detail. It should be understood that the descriptions of the apparatus and system embodiments correspond to the descriptions of the method embodiments. Therefore, for matters not described in detail, reference can be made to the method embodiments above. For the sake of brevity, they will not be repeated here.

[0161] Figure 7 It is a schematic structural diagram of a first communication device 700 provided in an embodiment of the present application. Figure 7 The first communication device 700 shown can execute the corresponding steps executed by the network management system in the above method embodiment.

[0162] like Figure 7 As shown, the first communication device 700 may include a transceiver unit 710 and a processing unit 720. The transceiver unit 710 may be configured to execute steps 210, 220, 310, 330, 410, 411, 430, and 431 of the above method. The processing unit 720 may be configured to execute steps 230, 340, 360, 440, 450, 470, and 480 of the above method. For details of these steps, please refer to the relevant steps above and will not be repeated here.

[0163] It should be understood that the apparatus 700 of the embodiment of the present application can be implemented by a central processing unit (CPU), or by an application-specific integrated circuit (ASIC), or by a programmable logic device (PLD), wherein the PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. When the method described in the above method embodiment is implemented by software, the apparatus 700 and its various modules can also be software modules.

[0164] Figure 8 It is a schematic structural diagram of a data transmission device 800 provided in an embodiment of the present application. Figure 8 The second communication device 800 shown can execute the corresponding steps executed by the GNE in the above method embodiment. Figure 8 As shown, the second communication device 800 may include: a transceiver unit 810 and a processing unit 820.

[0165] In some implementations, the second communication device 800 may execute the corresponding steps performed by the first GNE in the above-described method embodiment. Specifically, the transceiver unit 810 may be configured to receive the query message in step 310 and the query message in step 410, and to execute steps 330 and 430. The processing unit 820 may be configured to execute steps 420 and 460. For details of these steps, refer to the relevant steps above and will not be repeated here.

[0166] In other implementations, the second communication device 800 may execute the corresponding steps performed by the second GNE in the above-described method embodiment. Specifically, the transceiver unit 810 may be configured to receive the query message in step 411 above and to execute step 431 above. The processing unit 820 may be configured to execute steps 421 and 461 above. For details of these steps, refer to the relevant steps above and will not be repeated here.

[0167] It should be understood that the apparatus 800 of the embodiment of the present application can be implemented by a central processing unit (CPU), an application-specific integrated circuit (ASIC), or a programmable logic device (PLD), wherein the PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. When the method described in the above method embodiment is implemented by software, the apparatus 800 and its various modules can also be software modules.

[0168] Figure 9 Schematic diagram of the hardware structure of a communication device 900 provided in an embodiment of the present application.

[0169] like Figure 9 As shown, the communication device 900 includes a processor 901, a memory 902, an interface 903, and a bus 904. The interface 903 can be implemented wirelessly or wired, and specifically can be a network card. The processor 901, memory 902, and interface 903 are connected via a bus 904. The interface 903 can specifically include a transmitter and a receiver, which are used by the data transmission device to implement the above-mentioned transmission and reception. The processor 901 is used to execute the processing performed by the data transmission device in the above-mentioned embodiment. The memory 902 includes an operating system 9021 and an application 9022, which are used to store programs, codes, or instructions. When the processor or hardware device executes these programs, codes, or instructions, the processing process involving BFIR in the method embodiment can be completed. Optionally, the memory 902 can include read-only memory (ROM) and random access memory (RAM). The ROM includes a basic input / output system (BIOS) or an embedded system; the RAM includes an application and an operating system. When the communication device 900 needs to be operated, it is started by the BIOS stored in the ROM or the bootloader in the embedded system, and the communication device 900 enters a normal operating state. After the communication device 900 enters a normal operating state, the application program and operating system in the RAM are run, thereby completing the processing process related to the communication device 900 in the method embodiment. Figure 9Only a simplified design of the communication device 900 is shown. In actual applications, the communication device 900 may include any number of interfaces, processors or memories.

[0170] Optionally, in some implementations, the communication device 900 may be a hardware structure diagram of the first communication device 700 . In this case, 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 .

[0171] Optionally, in other implementations, the communication device 900 may be a hardware structure diagram of the second communication device 800 . In this case, 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 .

[0172] Figure 10 1 is a schematic structural diagram of a system 1000 provided in an embodiment of the present application. Figure 10 As shown, the system 1100 may include: the above-mentioned first communication device 700 and the above-mentioned second communication device 800.

[0173] The present application also provides a computer-readable medium storing program code. When the program code is executed on a computer, the computer executes the method performed by the network management system or the GNE (i.e., the first GNE or the second GNE) in the above-described method embodiment. Such computer-readable storage includes, but is 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 a hard drive.

[0174] The embodiment of the present application also provides a chip system, which includes: 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 world, the at least one memory, the interface circuit and the at least one processor are interconnected through a line, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform the operations of the network management system or GNE (i.e., the first GNE or the second GNE) described in the above-mentioned various aspects. In the specific implementation process, the chip system can be implemented in the form of a central processing unit (CPU), a microcontroller unit (MCU), a microprocessor (MPU), a digital signal processor (DSP), a system on chip (SoC), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a programmable logic device (PLD).

[0175] An embodiment of the present application further provides a computer program product for use in a network management system. The computer program product includes a series of instructions. When the instructions are executed, the network management system operations described in the methods described in the above aspects are performed.

[0176] An embodiment of the present application also provides a computer program product, which is applied to a GNE (i.e., a first GNE or a second GNE). The computer program product includes a series of instructions. When the instructions are executed, the operations of the GNE (i.e., the first GNE or the second GNE) described in the methods described in the above aspects are performed.

[0177] As used in this specification, the terms "component," "module," "system," and the like are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0178] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0179] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0180] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0181] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

[0183] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0184] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for communication between a network management system and a network element, characterized in that: The method comprises: The network management system sends a query message to a gateway network element GNE in the second routing domain, wherein the query message is used to obtain routing information of a first non-gateway network element NGNE, where the first NGNE is an NGNE to be registered, and the routing domain where the network management system is located is a first routing domain, which is different from the second routing domain; 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 communication between the GNE in the second routing domain and the first NGNE; The network management system establishes a communication connection with the first NGNE according to the response message.

2. The method according to claim 1, characterized in that 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 is used for the first NGNE to establish a communication connection with a GNE in the second routing domain.

3. The method according to claim 2, characterized in that 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 for communication between the first GNE and the first NGNE, the first routing information includes an identifier 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, and the first NEID is used to uniquely identify the first NGNE, 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 based on a second IP address, the first NEID, and an identifier of the first port, where the second IP address is used to uniquely identify the first GNE. The second IP address is an IP address used when the first GNE establishes a communication connection with the network management system. The second routing information indicates that registration of the first NGNE with the network management system is complete, and the second routing information includes a mapping relationship between the second IP address, the first NEID, and the first port.

4. The method according to claim 3, characterized in that The second routing domain also includes a second GNE, and the response message also includes a second response message, the second response message indicating third routing information for communication between the second GNE and the first NGNE, the third routing information including a second routing cost, 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, based on the first routing cost and the second routing cost, that the first GNE is the active GNE of the first NGNE and that the second GNE is the standby GNE of the first NGNE. The first routing information further includes the first routing cost.

5. The method according to claim 4, characterized in that The third routing information further includes an identifier of a second port and the first NEID, where the second port is a port of the second GNE to which the first NGNE is connected. The network management system establishes a communication connection with the first NGNE according to the response message, including: In the event that the first GNE fails, the network management system generates fourth routing information based on the third IP address, the first NEID, the identifier of the second port, and the second routing cost. The third IP address is used to uniquely identify the second GNE. The third IP address is the IP address used when the second GNE establishes a communication connection with the network management system. The fourth routing information indicates that the first NGNE has completed registration with the network management system. The fourth routing information includes a mapping relationship between the third IP address, the first NEID, the second port, and the second routing cost.

6. The method according to claim 4 or 5, characterized in that The first routing cost is determined according to at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE; The second routing cost is determined according to at least one of the following information: path information from the second GNE to the first NGNE, load status of the second GNE, or delay information from the second GNE to the first NGNE.

7. A method for communication between a network management system and a network element, characterized in that: The method comprises: After a first gateway network element (GNE) establishes a communication connection with a first non-gateway network element (NGNE), the first GNE receives 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. The routing domain in which the network management system is located is a first routing domain. A second routing domain includes the first GNE and the first NGNE. 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 a routing table of the first GNE, where the first response message indicates first routing information for communication between the first GNE and the first NGNE; The first GNE sends the first response message to the network management system.

8. The method according to claim 7, characterized in that The query message includes a first Internet Protocol (IP) address, which is a preset IP address of the first NGNE and is used by the first NGNE to establish a communication connection with a GNE in the second routing domain, where the GNEs in the second routing domain include the first GNE.

9. The method according to claim 8, characterized in that A first correspondence is recorded in the routing table of the first GNE. 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. The first GNE generates a first response message according to the query message and the routing table of the first GNE, including: determining, by the first GNE, the first NEID according to the first IP address and the first correspondence; The first GNE determines, based on a second IP address and the first NEID, path information for communication between the first GNE and the first NGNE, where the second IP address is used to uniquely identify the first GNE and is an IP address used by the first GNE to establish a communication connection with the network management system. The first GNE generates the first response message according to the path information.

10. The method according to claim 9, characterized in that The first routing information includes an identifier of a first port, a first routing cost, the first 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 routing cost is a routing cost for the first GNE to communicate with the first NGNE.

11. The method according to claim 10, characterized in that The first routing cost is determined according to at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE.

12. A first communication device, characterized in that: The first communication device is applied to a network management system, and the device includes: a transceiver unit, configured to send a query message to a gateway network element GNE in a second routing domain, wherein the query message is used to obtain routing information of a first non-gateway network element NGNE, wherein the first NGNE is an NGNE to be registered, and 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 transceiver unit is further configured to receive a response message sent by a GNE in the second routing domain, where the response message indicates routing information for communication between the GNE in the second routing domain and the first NGNE; The processing unit is configured to establish a communication connection with the first NGNE according to the response message.

13. The device according to claim 12, characterized in that 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 is used for the first NGNE to establish a communication connection with a GNE in the second routing domain.

14. The device according to claim 13, characterized in that 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 for communication between the first GNE and the first NGNE, the first routing information includes an identifier 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, and the first NEID is used to uniquely identify the first NGNE, The processing unit is further configured to: Second routing information is generated based on the second IP address, the first NEID, and the identifier of the first port. The second IP address is used to uniquely identify the first GNE. The second IP address is the IP address used when the first GNE establishes a communication connection with the network management system. The second routing information indicates that the first NGNE has completed registration with the network management system. The second routing information includes a mapping relationship between the second IP address, the first NEID, and the first port.

15. The device according to claim 14, characterized in that The second routing domain also includes a second GNE, and the response message also includes a second response message, the second response message indicating third routing information for communication between the second GNE and the first NGNE, the third routing information including a second routing cost, The processing unit is further configured to: According to the first routing cost and the second routing cost, it is determined that the first GNE is the active GNE of the first NGNE, and the second GNE is the standby GNE of the first NGNE. The first routing information further includes the first routing cost.

16. The device according to claim 15, characterized in that The third routing information further includes an identifier of a second port and the first NEID, where the second port is a port of the second GNE to which the first NGNE is connected. The processing unit is further configured to: In the event that the first GNE fails, fourth routing information is generated based on the third IP address, the first NEID, the identifier of the second port, and the second routing cost. The third IP address is used to uniquely identify the second GNE. The third IP address is the IP address used when the second GNE establishes a communication connection with the network management system. The fourth routing information indicates that the first NGNE has completed registration with the network management system. The fourth routing information includes a mapping relationship between the third IP address, the first NEID, the second port, and the second routing cost.

17. The device according to claim 15 or 16, characterized in that The first routing cost is determined according to at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE; The second routing cost is determined according to at least one of the following information: path information from the second GNE to the first NGNE, load status of the second GNE, or delay information from the second GNE to the first NGNE.

18. A second communication device, characterized in that: The second communication device is applied to the first gateway network element GNE, and the device includes: a transceiver unit, configured to receive a query message sent by a network management system after the first GNE establishes a communication connection with a first non-gateway network element NGNE, wherein the query message is used to obtain routing information of the first NGNE, the first NGNE is an NGNE to be registered, the routing domain in which the network management system is located is a first routing domain, and a second routing domain includes the first GNE and the first NGNE, and 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 a routing table of the first GNE, where the first response message indicates first routing information for communication between the first GNE and the first NGNE; The transceiver unit is further configured to send the first response message to the network management system.

19. The device according to claim 18, characterized in that The query message includes a first Internet Protocol (IP) address, which is a preset IP address of the first NGNE and is used by the first NGNE to establish a communication connection with a GNE in the second routing domain, where the GNEs in the second routing domain include the first GNE.

20. The device according to claim 19, characterized in that A first correspondence is recorded in the routing table of the first GNE. 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. The processing unit is further configured to: Determine the first NEID according to the first IP address and the first corresponding relationship; determining, based on a second IP address and the first NEID, path information for communication between the first GNE and the first NGNE, where the second IP address is used to uniquely identify the first GNE and is an IP address used by the first GNE to establish a communication connection with the network management system; Generate the first response message according to the path information.

21. The device according to claim 20, characterized in that The first routing information includes an identifier of a first port, a first routing cost, the first 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 routing cost is a routing cost for the first GNE to communicate with the first NGNE.

22. The device according to claim 21, characterized in that The first routing cost is determined according to at least one of the following information: path information from the first GNE to the first NGNE, load status of the first GNE, or delay information from the first GNE to the first NGNE.

23. A first communication device, characterized in that: The first communication device is applied to a network management system. The device includes at least one processor and a communication interface. The at least one processor is configured to execute a computer program or instruction so that the device executes the method according to any one of claims 1 to 6.

24. A second communication device, characterized in that: The second communication device is applied to the first gateway network element GNE, and the device includes at least one processor and a communication interface. The at least one processor is used to execute a computer program or instruction so that the device performs the method according to any one of claims 7 to 11.

25. A computer-readable storage medium, characterized in that The invention comprises a computer program which, when being run on a computer, causes the computer to execute the method according to any one of claims 1 to 6.

26. A computer-readable storage medium, characterized in that The invention comprises a computer program which, when run on a computer, causes the computer to execute the method according to any one of claims 7 to 11.

27. A communication system, characterized in that: Comprising the first communication device as claimed in claim 23 and the second communication device as claimed in claim 24.

Images