KR20180005579A - Apparatus for network management providing scalability and decentralization and method thereof - Google Patents

Abstract

Disclosed are an apparatus and a method for flexibly expanding a network management system in a scale-out scheme in accordance with a configuration distribution, characteristics, and a service goal of management object network elements for each network domain, and operating the same in a distributed form. According to one aspect of the present invention, the apparatus for managing at least one sub-network management system which is separately disposed in one or more network domains, and manages network elements configuring each of the network domains, comprises: a generating unit for generating at least one type of a network management module for independently executing a network management function; a determination unit for determining the type and number of the network management module to be distributed to the sub-network management system; and a distribution unit for distributing the network management module corresponding to the type and number determined by the determination unit to the sub-network management system.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to an apparatus and a method for providing scalability and granularity of network management,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management technology, and more particularly, to an apparatus and a method for expanding a network management system in a scale-out manner and operating the network management system in a clustered manner.

In order to realize a hyper-connected society that connects all objects, network implementation technology is also important. However, a network management system (NMS: Network Management System is also important. Since the amount of objects connected to the network and the amount of communication there is explosively increased, it is difficult to cope with the structure of the current scale-up type network management system, so it needs to be converted into a scale-out type structure.

In addition, as the emergence of new services requiring support for autonomous driving vehicles, drone remote / autonomous flight, and remote medical services such as ultra short latency is imminent, the network functions are shifting from the core to the edge ). Accordingly, it is necessary to follow the decentralized structure so that the local network elements in each domain can be managed independently in each local domain, rather than in the centralized network management system. At this time, since the characteristics and sizes of the network elements constituting each domain are different, the characteristics and size of the network management system responsible for the domain must be adjusted to be different.

In the connected society, the proportion of wireless communication increases, and the number of network connections of moving objects becomes very large. At this time, the number of managed network elements belonging to each local domain also becomes very fluid. Therefore, the structure of the network management system in charge of each domain should have a flexible structure that reflects this fluidity.

There are plans to increase the hardware and to reinforce the software system in order to solve the problem of the network elements and the liquidity which are exploding in the connection environment based on the structure and the technology of the conventional network management system.

As a method to increase the hardware system, there is a method of increasing the computing power by expanding the memory or the CPU, but there is physical / technical limit to meet the performance requirement by reinforcing one system in the hardware aspect.

A conventional network management system implementation technique for enhancing a software system is mainly a scale-up method. A typical patent is "Design for scalable network management systems (US Patent 6,968,371)", which aims to build a scalable network management system and targets large-scale voice / data networks. The management elements are managed by grouping them into groups of a certain size. Each subsystem of the network management system is arranged for each group. The subsystem consists of network management unit functions and unit processes. In one subsystem, only one network management function and one process instance are created and included. If the number of network elements to be managed increases beyond a predetermined size, the further network elements are grouped into another group, and a new subsystem is created and allocated for management of the new group.

The problem with the hardware extension method is easily recognizable to engineers with basic knowledge in this field, so no further explanation is required. Problems in the case where the reinforcement of the software system is attempted to be solved by the prior art (in particular, the above-mentioned U.S. patent) is as follows.

First, the inventor of the above-mentioned U.S. patent also defines his idea as a scale-up method. In order to manage a new network environment that continuously increases and changes with super connect, ultra-low latency, It is generally known that the scale-up method of the system can improve the performance up to the initial predetermined level, but no further performance improvement occurs after a certain point of time, or rather, performance degradation occurs.

In addition, in order to release a variety of new services requiring ultra-low latency, the network functions are moved forward to the vicinity of the user terminal. Therefore, the centralized management of these network functions is required to accurately monitor and control the required ultra- It is likely to lead to unmanageable results.

The managed network elements (eg, switches, routers, gateways, servers, links, etc.) belonging to a management group of a certain size have different characteristics as respective network devices. In the configuration distribution of the managed network elements included in each group, each group will be composed of different network elements. However, according to the related art, since the configuration type of the subsystem of the network management system that will manage each group has the same form (since the existing subsystem is copied as it is when a new group is created), computing resources are placed inefficiently .

US Patent 6,968,371 (November 22, 2005)

The present invention has been made in view of the above-described prior art, and it is an object of the present invention to provide a network management system that can be flexibly extended in a scale-out manner in accordance with the configuration distribution, And to provide an apparatus and a method for allowing a user to perform various operations.

An apparatus for managing at least one sub-network management system, which is arranged in each of at least one or more network domains and manages network elements constituting each network domain according to an aspect, includes at least one type A generation unit configured to generate the network management module; A determination unit for determining the type and number of network management modules to be distributed to the at least one sub-network management system; And a distribution unit for distributing a network management module corresponding to the type and number determined by the determination unit to the at least one sub-network management system.

The determination unit may determine the type and number of network management modules to be distributed based on characteristics of network domains managed by the at least one sub-network management system and characteristics of network elements.

The determination unit may determine the type and number of network management modules to be further distributed each time a new network element is added to a specific network domain.

When the management capability of the sub-network management system managing the specific network domain is exceeded by adding a new network element to the specific network domain, the determination unit may determine the type and number of network management modules to be further distributed.

The management module may include at least one of an interlock module, an alarm module, an analysis module, and a collection module.

The at least one sub-network management system may be an NFV (Network Function Virtualization) system, and the generation unit may generate the at least one network management module in the form of a VNF (Virtualized Network Function).

The at least one network domain may be an access network domain, a core network domain, or an edge network domain connecting the access network domain and the core network domain.

According to another aspect of the present invention, a method for managing at least one or more sub-network management systems arranged in each of at least one or more network domains in a central network management system and managing network elements constituting each network domain includes the steps of Generating at least one type of network management module capable of managing at least one type of network management module; Determining a type and number of network management modules to be distributed to the at least one sub-network management system; And distributing a network management module corresponding to the determined type and number to the at least one sub-network management system.

The determining may determine the type and number of network management modules to be distributed based on characteristics of the network domain managed by the at least one sub-network management system and characteristics of the network elements.

The determining step may determine the type and number of network management modules to be further distributed each time a new network element is added to a specific network domain.

The determining step may determine a type and a number of network management modules to be further distributed when a new network element is added to the specific network domain and the management capability of the sub-network management system managing the specific network domain is exceeded .

The management module may include at least one of an interlock module, an alarm module, an analysis module, and a collection module.

The at least one sub-network management system may be an NFV (Network Function Virtualization) system, and the generating may include generating at least one or more network management modules in a VNF (Virtualized Network Function) format.

The at least one network domain may be an access network domain, a core network domain, or an edge network domain connecting the access network domain and the core network domain.

According to an aspect of the present invention, management of network elements operating in each network domain can be performed quickly by managing each network domain in a non-centralized management type, and it is possible to provide an ultra low- have.

According to another aspect of the present invention, at least one or more types of network management modules capable of independently performing network management are generated, and the network management modules are adaptively inserted into the sub-network management system of each network domain according to the characteristics of each network domain, It is possible to prevent waste of computing resources and network resources used for management.

According to another aspect of the present invention, since all the sub-network management systems disposed in each network domain are configured by a common network management module, they can be grouped together and operated organically, and a single view .

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate preferred embodiments of the invention and, together with the description of the invention below, And should not be construed as interpretation.
BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate preferred embodiments of the invention and, together with the description of the invention below, And should not be construed as interpretation.
1 is a schematic block diagram of a system according to an embodiment of the present invention.
2 is a schematic internal configuration diagram of the network management system of FIG.
3 is an exemplary diagram of a network management module distributed by the central network management system of FIG. 1 to a sub-network management system.
4 is a schematic internal configuration diagram of the central management system of FIG. 1 managing a network management module.
5 is a schematic flowchart of a network management method according to an embodiment of the present invention.
FIG. 6 is an exemplary diagram illustrating a comparison between a conventional system and the system of FIG. 1;

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, terms and words used in the present specification and claims should not be construed as limited to ordinary or dictionary terms, and the inventor should appropriately interpret the concepts of the terms appropriately It should be interpreted in accordance with the meaning and concept consistent with the technical idea of the present invention based on the principle that it can be defined. Therefore, the embodiments described in the present specification and the configurations shown in the drawings are only the most preferred embodiments of the present invention and do not represent all the technical ideas of the present invention. Therefore, It is to be understood that equivalents and modifications are possible.

1 is a schematic block diagram of a system 1 according to an embodiment of the present invention.

The system 1 according to an embodiment of the present invention includes network domains 121 to 123 for providing communication services and network elements 121 to 123 corresponding to respective network domains 121 to 123, (Hereinafter referred to as a 'sub NMS') 111 to 113 that manages the sub-network management systems 111 to 113 and a core network management system (hereinafter, referred to as' (Hereinafter referred to as " central NMS ") 100. Network management refers to the management of functions and operation states of various network elements constituting a network domain for providing communication services to subscribers. Here, a network element refers to a switch, a router, a gateway, a server, a link, and the like.

The network domains 121 to 123 are constituted by respective network elements for a communication service and provide a communication service. The network domains 121 to 123 are classified according to functions and layers of the network and include an access network domain 121, an edge network domain 122, and a core network domain 123. The access NMS 111, the edge NMS 112, and the core NMS 113 corresponding to the sub NMS are allocated to the respective network domains 121 to 123. Here, the network domains 121 to 123 have unique characteristics. The characteristics include network connection, ultra-low latency, network function, layer, configuration and characteristics of network elements, and network scale as requirements of network service.

The access network domain 121 is a domain for providing a network access function to a subscriber's end terminal, and is managed by a corresponding access NMS 111. The access network domain 121 includes network elements such as an access point (AP), a base station, and a gateway device to which the end terminal is connected. The access network domain 121 provides a network connection function such as a 5G connection, a Wi-Fi connection, and a wired connection to an end terminal.

The edge network domain 122 relays signals between the at least one access network domain 121 and the core network domain 123 and is managed by the corresponding edge NMS 112. The edge network domain 122 includes network elements such as a router device, a switch device, a gateway device, and a server that relays signals between the access network and the core network.

The core network domain 123 provides a communication service to an end terminal of a subscriber connected to at least one edge network domain 121 and is managed by a corresponding core NMS 113. The core network domain 123 is composed of communication equipment unique to the generation or type of communication service. For example, the core network domain 123 includes network elements such as MME (Mobility Management Entity), HSS (Home Subscriber Server), S-GW (Serving-Gateway), and P-GW .

As described above, the sub NMSs 111 to 113 include the access NMS 111, the edge NMS 112, and the core NMS 113. The sub NMSs 111 to 113 are provided with a predetermined number of at least one network management module 101 for managing the assigned domains 121 to 123 from the central NMS 100, (101) is installed and executed. At this time, the sub NMSs 111 to 113 are constructed with an NFV (Network Function Virtualization) architecture, and the network management module 101 is implemented in the form of a VNF (Virtual Network Function) operating on a Virtual Machine .

The central NMS 100 generates the network management module 101 in consideration of the characteristics of the respective domains 121 to 123 and the characteristics of the network elements constituting the respective domains 121 to 123, And distributes and manages the determined types and the number of network management modules 101 to the sub NMSs 111 to 113. The type of the network management module 101 will be described later with reference to FIG. The central NMS 100 may also be constructed in a network function virtualization (NFV) architecture similar to the sub NMSs 111 to 113. As described above, the central NMS 100 connects the network management module 101 to a virtual machine (Virtual Network Function) type that operates on the subnetworks 111 to 113.

2 is a schematic internal configuration diagram of an NFV architecture constituting the network management systems 100 and 111 to 113 of FIG. The NFV architecture largely includes a group 101 of virtual network function (VNF) instances, an NFV infrastructure 230, and a Management and Orchestration (MANO)

MANO 210 provides physical and software resource management, delivery, and management of VNFs. Specifically, the MANO 210 manages and controls the NFV infrastructure 230 resources, namely, the computing hardware 231, the storage hardware 232, and the network hardware 233, and is capable of managing the overall network orchestration in the multi-NFV infrastructure environment, And performs management functions. In addition, the MANO 210 performs life cycle management for the VNF instance 101. [ The MANO 210 also manages virtual machine (VM) resource management, routers (or switches), firewall policies, and the like.

The MANO 210 may include an orchestrator, one or more VNF managers, and one or more virtualized infrastructure managers.

The MANO 210 is configured to perform supervision and management of the VNF instances 101 and the NFV infrastructure 230. The orchestrator may be implemented in the virtual resources within the NFV infrastructure 230 and the NFV infrastructure 230. In addition, the orchestrator may implement networks such as L2 and L3 VPN services on the NFV infrastructure 230. The orchestrator may communicate with one or more VNF managers to implement requests related to the resources, to send configuration information to the VNF manager, and to collect status information of the VNF instance 101. The orchestrator may also communicate with the virtualized infrastructure manager to preserve and exchange resource allocation and / or virtualized hardware resource configuration and status information. A VNF manager manages one or more VNF instances.

The VNF manager performs various management functions such as instantiating, updating, quering, scaling, and / or terminating the VNF instance 101. The virtualized infrastructure manager includes computing hardware 231, storage hardware 232, network 233, virtual computing 234, virtual storage, And performs management functions used to control and manage the interaction of the VNF instance 101 with the virtual network 235 and the virtual network 236. For example, a virtualized infrastructure manager performs resource management functions such as infrastructure resource management and allocation and operations such as collecting NFV infrastructure fault information. The VNF manager and the virtualized infrastructure manager communicate with each other for resource allocation requests and exchange virtualized hardware resource configuration and status information.

NFV infrastructure 230 includes hardware components, software components, or a combination thereof for building a virtual environment (e.g., a VM) and for deploying, managing and executing VNF instances 101. A hardware resource and a virtualization layer are used to provide virtualized resources such as VMs for the VNF instance 101 and other types of virtual containers. The hardware resources include computing hardware 231, storage hardware 232, and network hardware 233. The computing hardware 231 may be commercial off-the-shelf (COTS) hardware and / or custom hardware used for processing and computing resources. The storage hardware 232 provides storage capacity that resides within the network or resides within storage hardware (i.e., local memory residing within the server). The network hardware 233 may be a switch, a router, and / or other network equipment that performs a switching function that may be interconnected via a wireless or wired link. The network hardware 233 may span multiple domains and may include a plurality of networks interconnected via one or more transport networks.

The virtualization layer in the NFV infrastructure 230 abstracts the hardware resources and isolates the VNF instance 101 from the underlying physical network layer to provide the virtualized resources to the VNF instance 101 . As shown in FIG. 2, the virtualized resources include virtual computing 234, virtual storage 235, and virtual network 236. Virtual computing 234 and virtual storage 235 may be provided to VNF instance 101 in the form of a hypervisor, VM, or other virtual container. For example, one or more VNF instances 101 may be placed in a VM. The virtualization layer abstracts the network hardware 233 to form a virtual network. The virtual network includes a virtual switch that provides a connection between the VM hosting the VNF instance 101 and / or other virtual containers. The abstraction of hardware resources may be implemented using various technologies including, but not limited to, virtual LAN, VPLS, VxLAN, and NVGRE (Network Virtualization using Generic Routing Encapsulation). In addition, the transport network within the network hardware 233 may be virtualized using a central control plane and a separate forwarding plane, e.g., Software Defined Network (SDN).

The VNF instance 101 on the NFV architecture of FIG. 2 is the network management module 101 described with reference to FIG. Accordingly, the MANO 210 of the central NMS 100 collectively manages the characteristics of the domains 121 to 123 and the characteristics of the network elements constituting the domains 121 to 123 using the NFV infrastructure 230 And determines the type and number of the network management modules 101 to be distributed to the sub NMSs 111 to 113 managing the respective domains 121 to 123 and generates the determined types and the number of the network management modules 101 It can be distributed to the sub NMSs 111 to 113 and the lifecycle can be managed. Meanwhile, the MANO 210 of each of the sub NMS 111 to 113 installs and executes the network management module 101, which is a VNF instance distributed from the central NMS 100, on the VM and controls the central NMS 100 The lifecycle of the network management module 101 can be managed and deleted.

FIG. 3 is an exemplary diagram of a network management module 101 distributed by the central NMS 100 of FIG. 1 to sub NMSs 111 to 113. The central NMS 100 and the sub NMSs 111 to 113 provided by the present invention are systems for managing various network elements established to provide communication services to subscribers. The core concept proposed by the present invention is to decompose a function for managing a network into a minimum scale capable of independently operating and convert each decomposed function into a module unit and then transmit the characteristics of each network domain 121 to 123 NMS 111 to 113 which manage each network domain 121 to 123 according to the characteristics (configuration distribution, personality, etc.) of the network elements in each network domain 121 to 123 101) by a necessary amount. The network management module 101, which is decomposed into a unit in the minimum scale, is composed of various types.

3, the network management module 101 may be composed of four kinds such as "interlocking", "alarming", "analysis", "gathering" and the like. However, the present invention is not limited thereto, and various types may be configured according to functions for network management. The interworking module executes the management function for the network operation in which the network element to be managed cooperates with the external system. The alarm module implements management functions that output alarms for faults in the network elements and for threats of performance and security. The analysis module executes the management function of extracting and analyzing the events generated from the network element. The acquisition module implements management functions to collect performance and fault information from the network elements.

The types and the quantity of the network management module 101 to be distributed to the sub NMSs 111 to 113 of the present invention are determined by the characteristics of the network domains 121 to 123 to be managed and the network elements 121 to 123 constituting each of the network domains 121 to 123 Size, and purpose of the product. For example, when a communication company newly constructs a network for subscribers, it is necessary to manage the sub-MMS 111 to 113 according to whether the target area is a dense area of a factory or a company or a densely populated area such as an apartment complex The types and the number of the modules 101 are differently arranged. Because stable operation is important for the company / factory area, it is required that the "analysis" module to accurately analyze the network situation and the "alarm" module to generate timely alarm when a problem occurs. On the other hand, in residential areas (especially in apartment areas), telecom operators are required to load a large number of "collection" modules because they need to closely gather network usage information from users in individual homes.

Here, the network management modules 101 of each of the sub NMSs 111 to 113 constitute one network management system and operate the network management independently for the respective network domains 121 to 123. That is, the small sub NMS 111 performs network management only for the small access network domain 121 by the partitionability, and the large sub NMS 113 manages the network only for the large core network domain 123.

FIG. 4 is a schematic internal configuration diagram of the central NMS 100 of FIG. 1 managing the network management module 101. FIG. Referring to FIG. 4, the central NMS 100 includes a generating unit 410, a determining unit 420, and a distributing unit 430.

The generation unit 410 generates various types of network management modules 101 such as an interworking module, an alarm module, an analysis module, and a collection module, which can independently execute a disassembled network management function.

The determination unit 420 determines the type and number of the network management module 101 to be distributed to each of the sub NMSs 111 to 113 in consideration of characteristics of each network domain to be managed. Here, the determination unit 420 determines the type and number of the network management module 101 to be further distributed each time a new network element is added to the specific network domain.

The determination unit 420 determines the type of the network management module 101 to be deployed for network management of the added network element when a new network element is added and thus the management capability of the sub NMSs 111 to 113 is exceeded And the number can be determined. In addition, when a change such as the addition of a network element is made, the determination unit 42 determines whether the network element is to be additionally distributed for the network management of the changed network elements in the specific network domains 121 to 123 It is possible to determine the type and number of the network management module 101 and to delete unnecessary network management module 101 although it has already been distributed. The determination unit 420 may receive the information of the reduced network elements in the respective network domains 121 to 123 from the network management module 110 for collection distributed to the respective sub NMSs 111 to 113 .

The distribution unit 430 distributes the network management module 101 of the type and the number determined by the determination unit 420 to the sub NMSs 111 to 113 of the corresponding network domain. By this distribution, the sub NMSs 111 to 113 receive, install, and execute the network management module 101. If the deletion of the network management module 101 of the sub NMS 111 to 113 is determined, the distribution unit 430 can transmit the delete command of the network management module 101 to the corresponding sub NMS 111 to 113 have. Here, the delete command may be the information of the life cycle.

In the present invention, since the sub NMSs 111 to 113 disposed in the respective network domains 121 to 123 are composed of the network management modules 101 distributed in the central NMS 100, And thus the central NMS 100 can provide a single view for the entire network.

5 is a schematic flowchart of a network management method according to an embodiment of the present invention.

The central NMS 100 decomposes the network management function into the smallest functions that can be executed independently, and generates the network management module 101 of the decomposed function. For reference, as one embodiment, four types of network management modules 101 are created: interlocking, alarming, analyzing, and collecting. The network domains 121 to 123 configured with various network elements can be constructed. Accordingly, sub-NMSs 111 to 113 for managing network elements belonging to the corresponding network domains 121 to 123 can be constructed. That is, the sub NMSs 111 to 113, which are physical systems for managing the network domains 121 to 123, can be constructed. At this time, the network management module 101 is not distributed to the sub NMSs 111 to 113. When the new NMSs 121 to 123 and the sub-NMSs 111 to 113 for managing the new network domains 121 to 123 are constructed as described above, the central NMS 100 transmits the new network domains 121 to 123 Characteristics and characteristics of the network elements belonging to the network domains 121 to 123 and determines the type and number of the network management module 101 to be distributed to the corresponding sub NMSs 111 to 113, To the sub NMSs 111 to 113 constructed in step S501.

Thereafter, the network management module 101 distributed and subscribed to the sub NMSs 111 to 113 is installed and executed to execute the network management function to manage the target network domains 121 to 123 (S503).

During network management, network elements may be newly added to the network domains 121 to 123 for any reason (S505). The central NMS 100 can receive information of the added network elements from the manager or receive the information of the added network elements from the sub NMSs 111 to 113 managing the network domains 121 to 123 to which the network elements are added Lt; / RTI > At this time, the network management module 101 for collecting is essentially inserted into the sub NMSs 111 to 113, and the network management module 101 related to the collection collects the information of the newly added network elements, 100).

By adding network elements, the central NMS 100 analyzes the characteristics of the network elements added to the network domains 121 to 123 to be managed and the characteristics of the corresponding network domains 121 to 123, (S507, S509). The type and quantity of the network management module 101 are determined and distributed to the sub NMSs 111 to 113, and the network management module 101 is determined. At this time, the central NMS 100 can additionally distribute the network management module 101 only when the management capabilities of the corresponding sub NMSs 111 to 113 are exceeded by the added network elements when new network elements are added .

FIG. 6 is an exemplary diagram illustrating a comparison between a conventional system and the system of FIG. 1; For convenience of explanation, a case where a communication network is added by the formation of a new city is taken as an example. In the conventional system for network management, as shown in FIG. 6 (a), when the new network is formed, (2) the communication network is expanded, and (3) the existing network management system The subsystem of the existing network management system that manages the area according to the scale-up method is divided into a memory, a CPU and a memory, DB and other hardware resources are added to manage the communication network. On the other hand, in the system of one embodiment, as shown in (b) of FIG. 6, the sub NMSs 111 to 113 managing the area for managing the expanded network are created by (1) forming a new city, (2) Scale out method. Namely, the central NMS 100 determines the type and quantity of the network management module 101 according to the characteristics of the network elements of the expanded network and the characteristics of the expanded network, and determines the type and quantity of the network management module 101 And distributes it to the sub NMSs 111 to 113 that manage the expanded communication network. (5) The sub NMSs 111 to 113 execute the network management module 101 of the determined kind and quantity to manage the newly added communication network.

Accordingly, the system of the embodiment of the present invention manages network elements operating in each of the network domains 121 to 123 by managing the respective network domains 121 to 123 in a non-centrally managed, And can provide ultra-low ductility service. In addition, at least one type of network management module 101 capable of independently performing network management can be created and adaptively managed according to the characteristics of each of the network domains 121 to 123, Systems 111 to 113, it is possible to prevent the waste of computing resources and network resources used for network management. In addition, since the subnetwork management systems 111 to 113 disposed in the respective network domains 121 to 123 are configured not by their own modules but by the network management module 101 distributed from the central NMS 100, To work organically and provide a single view of the entire network.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. It goes without saying that various modifications and variations are possible within the scope of equivalence of the scope.

100: Central NMS 101: Network management module
111 to 113: Sub NMS 121 to 123: Network domain

Claims (14)

There is provided an apparatus for managing at least one sub-network management system which is disposed in each of at least one or more network domains and manages network elements constituting each network domain,
A generation unit configured to generate at least one type of network management module capable of independently performing a network management function;
A determination unit for determining the type and number of network management modules to be distributed to the at least one sub-network management system; And
And a distribution unit for distributing a network management module corresponding to the type and the number determined by the determination unit to the at least one sub-network management system. The method according to claim 1,
Wherein,
And determines the type and number of network management modules to be distributed based on characteristics of network domains managed by the at least one sub-network management system and characteristics of network elements. 3. The method of claim 2,
Wherein,
And the type and number of network management modules to be further distributed are determined every time a new network element is added to a specific network domain. The method of claim 3,
Wherein,
Wherein the type and number of network management modules to be further distributed are determined when a new network element is added to the specific network domain and the management capability of the sub-network management system managing the specific network domain is exceeded. The method according to claim 1,
The management module comprising:
An interlock module, an alarm module, an analysis module and a collection module. The method according to claim 1,
Wherein the at least one sub-network management system comprises:
NFV (Network Function Virtualization) system,
Wherein the generation unit comprises:
And generates the at least one network management module in the form of a VNF (Virtualized Network Function). The method according to claim 1,
Wherein the at least one network domain comprises:
An access network domain, a core network domain, and an edge network domain connecting the access network domain and the core network domain. A method for managing at least one sub-network management system in a central network management system, the network management system being arranged in each of at least one or more network domains and managing network elements constituting each network domain,
Generating at least one kind of network management module capable of independently executing the network management function;
Determining a type and number of network management modules to be distributed to the at least one sub-network management system; And
And distributing a network management module corresponding to the determined type and number to the at least one sub-network management system. 9. The method of claim 8,
Wherein the determining comprises:
Wherein the type and number of network management modules to be distributed are determined based on characteristics of network domains managed by the at least one sub-network management system and characteristics of network elements. 10. The method of claim 9,
Wherein the determining comprises:
And the type and number of network management modules to be further distributed are determined every time a new network element is added to a specific network domain. 11. The method of claim 10,
Wherein the determining comprises:
When a new network element is added to the specific network domain and the management capability of the sub-network management system managing the specific network domain is exceeded, the type and number of network management modules to be further distributed are determined. 9. The method of claim 8,
The management module comprising:
An interlock module, an alarm module, an analysis module and a collection module. 9. The method of claim 8,
Wherein the at least one sub-network management system comprises:
NFV (Network Function Virtualization) system,
Wherein the generating comprises:
And generating the at least one network management module in the form of a VNF (Virtualized Network Function). 9. The method of claim 8,
Wherein the at least one network domain comprises:
An access network domain, a core network domain, and an edge network domain connecting the access network domain and the core network domain.

Images