CN108259193B

CN108259193B - Network management method, network management system and network element management system

Info

Publication number: CN108259193B
Application number: CN201611236522.7A
Authority: CN
Inventors: 陆伟; 杨水根; 孙文琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-12-28
Filing date: 2016-12-28
Publication date: 2021-06-01
Anticipated expiration: 2036-12-28
Also published as: CN108259193A; WO2018121453A1

Abstract

The patent application provides a network management method, a network management system and a network element management system. The method comprises the steps that a network management system sends a request for configuring alarm information to a network element management system, wherein the request for configuring the alarm information comprises parameters of the alarm information, the parameters of the alarm information correspond to network slice examples, and the network slice examples comprise network functions and/or sub-network slice examples; and the network management system receives alarm information configuration completion information sent by the network element management system, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information. Through the method and the device, the configuration of the alarm information can be completed, so that the management of the network system comprising the network slice example, particularly the fault management of the network system, is realized.

Description

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

Technical Field

The present patent application relates to the field of communications, and in particular, to a network management method, a network management system, and a network element management system.

Background

With the rapid development of wireless communication technology, the fifth Generation (5th Generation, abbreviated as 5G) wireless communication technology has been the hot spot in the industry. The 5G will support diverse application requirements including access capability supporting higher rate experience and larger bandwidth, lower latency and highly reliable information interaction, and access and management of larger-scale and low-cost machine type communication devices, etc. In addition, 5G can support various vertical industry application scenes such as vehicle networking, emergency communication, industrial internet and the like. In the face of the performance requirements and application scenarios of 5G, the 5G network needs to be closer to the specific requirements of users, and the customization capability needs to be further improved.

To this end, 5G introduces the important concept of network slicing. One or more network slice instances are included in the network system. For example, a Critical Machine Type Communication (Critical MTC) network slice instance, a Massive Machine Type Communication (Massive MTC) network slice instance, and a Mobile broadband (MBB) network slice instance may be included, where each network slice instance serves a different instance of Communication service. However, no network management method currently exists that can manage a network system that includes network slice instances.

Disclosure of Invention

The embodiment of the invention provides a method and a device for network management, aiming at realizing the management of a network system comprising a network slice example.

In a first aspect, a network management method is provided, including: the network management system sends a request for configuring the alarm information to a network element management system, wherein the request for configuring the alarm information comprises parameters of the alarm information; and the network management system receives alarm information configuration completion information sent by the network element management system. The parameters of the alarm information are corresponding to network slice instances, and the network slice instances comprise network function and/or sub-network slice instances. The alarm information configuration completion information is used for indicating the network element management system to perform configuration of parameters of the alarm information of the network slice example according to the request for configuring the alarm information.

By the method, the configuration of the alarm information can be completed, so that the management of the network system comprising the network slice example, particularly the fault management of the network system can be realized. The parameters of the alarm information correspond to the network slice instances, so that the configuration of the parameters of the alarm information can meet the requirements of fault management of different network slice instances. When the network function and/or the sub-network slice instance has a fault, the network element management system can generate fault alarm information corresponding to the network slice instance, so that the network management system can analyze the influence of the fault on the service of the network slice instance from the alarm information.

In one possible design, the method further includes: and the network management system sends an alarm information configuration modification notice to the network element management system. And the network management system receives the alarm information configuration modification confirmation sent by the network element management system. The alarm information configuration modification notification includes an adjustment of a parameter of the alarm information, the adjustment of the parameter of the alarm information corresponding to the network slice instance. And the alarm information configuration modification confirmation is used for indicating the network element management system to carry out configuration modification on parameters of the alarm information of the network slice example according to the alarm information configuration modification request. By configuring the modification notification with alarm information, parameters of the alarm information can be adjusted, which is beneficial for the EMS to feed back the impact of the network function and/or the sub-network slice instance on its now served network slice instance based on the fault report of the network function and/or the sub-network slice instance.

In one possible design, the method further includes: the network management system sends an alarm quantity obtaining request to the network element management system, wherein the alarm quantity request is used for requesting to obtain the alarm quantity of the corresponding network slice example; and the network management system receives the alarm quantity which is sent by the network element management system and corresponds to the network slice example. By the method, the alarm quantity corresponding to the network slice example can be acquired, so that the management of the network system comprising the network slice example, particularly the fault management of the network system can be realized.

In one possible design, the alarm quantity request includes an alarm quantity filter condition. In case the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filter condition for the number of alarms is a filter condition for a number of alarms corresponding to the at least two network slice instances. The network management system receiving the alarm quantity corresponding to the network slice instance sent by the network element management system, including: and the network management system receives the alarm quantity which is sent by the network element management system, corresponds to the network slice example and accords with the filtering condition of the alarm quantity of the network slice example.

The alarm quantity request comprises the alarm quantity filtering condition of the corresponding network slice example, so that the network management system can flexibly acquire the required alarm quantity of the corresponding network slice example according to different influences of faults on each network slice example, focus on the faults which have larger influences on the network slice example service, but not lose other information, and be beneficial to follow-up fault repair. Furthermore, in case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm quantity filter condition is an alarm quantity filter condition of the at least two network slice instances. This allows the network management system to distinguish the effect of the failure of the network function and/or sub-network slice instance on different network slice instances and to obtain the alarm quantities of different network slice instances that meet the alarm quantity filtering condition, respectively.

In one possible design, the method further includes: the network management system sends a request for acquiring an alarm list to the network element management system, wherein the alarm list request is used for requesting to acquire alarm information in an alarm list corresponding to a network slice example; and the network management system receives the alarm information which is sent by the network element management system and accords with the alarm information parameter. By the method, the alarm information corresponding to the network slice example can be acquired, so that the management of the network system comprising the network slice example, particularly the fault management of the network system can be realized.

The alarm list request includes an alarm information filter condition that is a filter condition for alarm information corresponding to at least two network slice instances in the case that the network function and/or the sub-network slice instance is shared between the at least two network slice instances. The network management system receiving the alarm information which is sent by the network element management system and accords with the alarm information parameter, and the method comprises the following steps: and the network management system receives the alarm information which is sent by the network element management system, corresponds to the network slice example and accords with the alarm information filtering condition of the network slice example.

The alarm list request comprises the alarm information filtering conditions corresponding to the network slice examples, so that the network management system can flexibly acquire the required alarm information corresponding to the network slice examples according to different influences of faults on the network slice examples, focus on the faults which have larger influences on the network slice example service, but not lose other information, and be beneficial to follow-up fault repair. Furthermore, in case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm information filtering condition is an alarm information filtering condition of the at least two network slice instances. Therefore, the network management system can distinguish the influence of the network function and/or sub-network slice instance fault on different network slice instances and respectively acquire the alarm information of different network slice instances which accords with the alarm information filtering condition.

In one possible design, the method further includes: the network management system receives an alarm configuration request sent by the network element management system, wherein the alarm configuration request is used for requesting the network management system to send a request for configuring alarm information to the network element management system.

In a second aspect, a method of managing network slices is provided, comprising the following steps. The network element management system receives a request for configuring the alarm information sent by the network management system, wherein the request for configuring the alarm information comprises parameters of the alarm information; and the network element management system sends alarm information configuration completion information to the network management system. The parameters of the alarm information are corresponding to network slice instances, and the network slice instances comprise network function and/or sub-network slice instances. The alarm information configuration completion information is used for indicating the network element management system to perform configuration of parameters of the alarm information of the network slice example according to the request for configuring the alarm information.

In one possible design, the method further includes: the network element management system receives an alarm information configuration modification notice sent by the network management system, wherein the alarm information configuration modification notice comprises adjustment of parameters of alarm information, and the adjustment of the parameters of the alarm information corresponds to a network slice example. And the network element management system sends an alarm information configuration modification confirmation to the network management system, wherein the alarm information configuration modification confirmation is used for indicating the network element management system to carry out configuration modification on parameters of the alarm information of the network slice example according to the alarm information configuration modification request.

In one possible design, the method further includes: the network element management system receives an alarm quantity acquisition request sent by the network management system, wherein the alarm quantity request is used for requesting to acquire the alarm quantity of a corresponding network slice example; and the network element management system sends the alarm quantity corresponding to the network slice example to the network management system.

In one possible design, the alarm quantity request includes an alarm quantity filter condition, the alarm quantity filter condition being a filter condition of an alarm quantity corresponding to at least two network slice instances in a case where the network function and/or the sub-network slice instance is shared between the at least two network slice instances; the network element management system sends the alarm quantity corresponding to the network slice example to the network management system, and the alarm quantity comprises the following steps: and the network element management system sends the alarm quantity corresponding to the network slice example and meeting the filtering condition of the alarm quantity of the network slice example to the network management system.

In one possible design, the network element management system receives an alarm list acquisition request sent by the network management system, where the alarm list request is used to request to acquire alarm information in an alarm list corresponding to a network slice instance; and the network element management system sends alarm information which accords with the alarm information parameter to the network management system.

In one possible design, the alarm list request includes an alarm information filter condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filter condition being a filter condition of alarm information corresponding to the at least two network slice instances; the network element management system sends the alarm information meeting the alarm information parameter to the network management system, and the alarm information comprises: and the network element management system sends alarm information corresponding to the network slice example and meeting the alarm information filtering condition of the network slice example to the network management system.

In a third aspect, a network management system is provided, including: a transceiver, a memory, and a processor. The memory is used for storing instructions, and the processor is respectively connected with the memory and the transceiver and is used for executing the instructions stored in the memory so as to execute the following steps when executing the instructions: sending a request for configuring alarm information to a network element management system through the transceiver, wherein the request for configuring alarm information comprises parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances comprise network functions and/or sub-network slice instances; and receiving alarm information configuration completion information sent by the network element management system through the transceiver, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

In one possible design, the processor when executing the instructions further performs the steps of: sending an alarm information configuration modification notification to the network element management system through the transceiver, wherein the alarm information configuration modification notification includes adjustment of parameters of alarm information, and the adjustment of the parameters of the alarm information corresponds to a network slice example; and receiving an alarm information configuration modification confirmation sent by the network element management system through the transceiver, wherein the alarm information configuration modification confirmation is used for indicating the network element management system to carry out configuration modification on parameters of alarm information of a network slice example according to the alarm information configuration modification request.

In one possible design, the processor when executing the instructions further performs the steps of: sending an alarm quantity obtaining request to the network element management system through the transceiver, wherein the alarm quantity request is used for requesting to obtain the alarm quantity of the corresponding network slice example; and receiving the alarm quantity corresponding to the network slice example sent by the network element management system through the transceiver.

In one possible design, the alarm quantity request includes an alarm quantity filter condition that is a filter condition of alarm quantities corresponding to at least two network slice instances where the network function and/or the sub-network slice instance is shared between the at least two network slice instances. The processor, when executing the instructions, further performs the steps of: and receiving the alarm quantity which is sent by the network element management system and corresponds to the network slice example and accords with the filtering condition of the alarm quantity of the network slice example through the transceiver.

In one possible design, the processor when executing the instructions further performs the steps of: sending an alarm list acquisition request to the network element management system through the transceiver, wherein the alarm list acquisition request is used for requesting to acquire alarm information in an alarm list corresponding to a network slice example; and receiving the alarm information which is sent by the network element management system and accords with the alarm information parameter through the transceiver.

In one possible design, the alarm list request includes an alarm information filter condition, the alarm information filter condition being a filter condition of alarm information corresponding to at least two network slice instances in a case where the network function and/or the sub-network slice instance is shared between the at least two network slice instances. The processor, when executing the instructions, further performs the steps of: and receiving the alarm information which corresponds to the network slice example and accords with the alarm information filtering condition of the network slice example and is sent by the network element management system through the transceiver.

In a fourth aspect, there is provided a network element management system, including: a transceiver, a memory, and a processor. The memory is used for storing instructions, and the processor is respectively connected with the memory and the transceiver and is used for executing the instructions stored in the memory so as to execute the following steps when executing the instructions: receiving, by the transceiver, a request for configuring alarm information sent by a network management system, where the request for configuring alarm information includes parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances include network functions and/or sub-network slice instances; and sending alarm information configuration completion information to the network management system through the transceiver, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

In one possible design, the processor when executing the instructions further performs the steps of: receiving, by the transceiver, an alarm information configuration modification notification sent by the network management system, where the alarm information configuration modification notification includes an adjustment of a parameter of alarm information, and the adjustment of the parameter of alarm information corresponds to a network slice instance; and sending an alarm information configuration modification confirmation to the network management system through the transceiver, wherein the alarm information configuration modification confirmation is used for indicating the network element management system to carry out configuration modification on parameters of the alarm information of the network slice example according to the alarm information configuration modification request.

In one possible design, the processor when executing the instructions further performs the steps of: receiving an alarm quantity acquisition request sent by the network management system through the transceiver, wherein the alarm quantity acquisition request is used for requesting to acquire the alarm quantity of a corresponding network slice example; and sending the alarm quantity corresponding to the network slice example to the network management system through the transceiver.

In one possible design, the alarm quantity request includes an alarm quantity filter condition, the alarm quantity filter condition being a filter condition of an alarm quantity corresponding to at least two network slice instances in a case where the network function and/or the sub-network slice instance is shared between the at least two network slice instances; the processor, when executing the instructions, further performs the steps of: and sending the alarm quantity corresponding to the network slice example and meeting the filtering condition of the alarm quantity of the network slice example to the network management system through the transceiver.

In one possible design, the processor when executing the instructions further performs the steps of: receiving an alarm list acquisition request sent by the network management system through the transceiver, wherein the alarm list acquisition request is used for requesting to acquire alarm information in an alarm list corresponding to a network slice example; and sending the alarm information which accords with the alarm information parameter to the network management system through the transceiver.

In one possible design, the alarm list request includes an alarm information filter condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filter condition being a filter condition of alarm information corresponding to the at least two network slice instances; the processor, when executing the instructions, further performs the steps of: and the network element management system sends alarm information corresponding to the network slice example and meeting the alarm information filtering condition of the network slice example to the network management system.

In combination with any of the above aspects, in one possible design, in a case that the network function or sub-network slice instance is shared between at least two network slice instances, the parameter of the alarm information corresponds to the at least two network slice instances, and the request for configuring the alarm information further includes identification information of the at least two network slice instances.

For shared network functions and/or sub-network slice instances, the network management system can distinguish different influences of faults on each network slice instance of at least two network slice instances, so that operators can be helped to quickly locate fault causes, focus on key faults and guarantee key services.

In combination with any of the above aspects, in one possible design, when a network slice instance is newly created, the adjusting of the parameter of the alarm information includes adding an identification of the newly created network slice instance to the parameter of the alarm information.

When a network slice example is newly created, adjusting parameters of alarm information, and adding the identifier of the newly created network slice example in the parameters of the alarm information. It is beneficial to reflect the impact of a fault on a newly created net-slice instance in the alarm information.

In combination with any of the above aspects, in one possible design, when terminating a network slice instance, the adjusting of the parameter of the alarm information includes deleting an identifier of the terminated network slice instance in the parameter of the alarm information. When the network slice example is ended, adjusting parameters of alarm information, and deleting the identifier of the ended network slice example in the parameters of the alarm information. And the parameter configuration of the corresponding alarm information is adjusted, so that the influence of the fault on the terminated network slice example is not reflected in the alarm information.

In combination with any of the above aspects, in one possible design, when the network function and/or the sub-network slice instance is expanded, contracted, or updated, the adjusting of the parameter of the alarm information includes adjusting a value of the parameter of the alarm information. And when the network function and/or the sub-network slice example is expanded, contracted or updated, adjusting parameters of alarm information, and adjusting values of the parameters of the alarm information in the parameters of the alarm information. And adjusting the parameter configuration of the corresponding alarm information is beneficial to reflecting the influence of the adjusted network function/sub-network slice example fault on the network slice example in the alarm information.

In combination with any of the above aspects, in one possible design, the parameter of the alarm information includes one or more of the following: a parameter of fault severity, a parameter of fault trend, a parameter of fault threshold, a monitored attribute parameter, and a proposed repair action parameter.

In a fifth aspect, a network system is provided, which includes the network management system of the third aspect and the network element management system of the fourth aspect.

A sixth aspect provides a computer readable medium for storing a computer program comprising instructions for carrying out the method of the first aspect or any possible implementation of the first aspect.

In a seventh aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the method of the second aspect or any possible implementation of the second aspect.

Drawings

Fig. 1A is a schematic diagram of a network management architecture according to an embodiment of the present invention.

Fig. 1B is a diagram illustrating another network management architecture according to an embodiment of the invention.

Fig. 2 is a schematic diagram of an example of a network slice according to an embodiment of the present invention.

Fig. 3 is a schematic diagram of another example of a network slice, according to an embodiment of the invention.

Fig. 4 is a diagram of a hierarchical structure of NSM & O according to an embodiment of the present invention.

Fig. 5 is an interaction diagram of a network management method according to an embodiment of the present invention.

Fig. 6 is an interaction diagram of another network management method according to an embodiment of the present invention.

Fig. 7 is a schematic block diagram of a network management system according to an embodiment of the present invention.

Fig. 8 is a schematic block diagram of a network element management system according to an embodiment of the present invention.

Fig. 9 is a schematic block diagram of another network management system according to an embodiment of the present invention.

Fig. 10 is a schematic block diagram of another network element management system according to an embodiment of the present invention.

Detailed Description

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

It should be understood that the technical solutions of the embodiments of the present invention can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, a LTE Frequency Division Duplex (FDD) System, a LTE Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a 5G communication System, a future communication System, and the like.

The embodiment of the invention relates to a network slicing technology. The network slicing technology is to logically abstract a network into one or more network slices, wherein each network slice comprises a series of logical network functions, and the differentiated requirements of different service types are met in a targeted manner. For example, in The fifth Generation mobile communication (The 5th Generation, abbreviated as "5G") network, network slicing is an on-demand networking method, and brings new services to operators, which can be adjusted according to changing user requirements and quickly meet new application requirements.

The network slicing technology abstracts network physical infrastructure resources into a plurality of mutually independent parallel network slicing examples according to scene requirements. And each network slice example carries out customized cutting of network functions and arrangement management of corresponding network functions according to the requirements of the service scenes and the service models. A network slice instance may be considered an instantiated network. Such a network structure allows an operator to provide a network as a service to users, and can freely combine physical networks according to the indexes of rate, capacity, coverage, delay, reliability, security, availability, and the like, so as to meet the requirements of different users.

It should be noted that the terms "network management architecture", "network system", "system", etc. may be used interchangeably herein. To facilitate understanding, some terms appearing herein are introduced.

Network slice (Network slice): different logical networks are customized according to different service requirements on the basis of physical or virtual network infrastructure. The network slice can be a complete end-to-end network comprising a terminal, an access network, a transmission network, a core network and an application server, can provide telecommunication service and has certain network capacity; the network slice may also be any combination of the above terminals, access networks, transport networks, core networks and application servers, e.g. a network slice only contains access networks and core networks. A network slice may have one or more of the following characteristics: the access network may or may not be sliced. The access network may be common to multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.

Network Slice Instance (NSI): the network is a real running logic network and can meet certain network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network management system, and one network management system can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like in the operation process of the network slice instances. When multiple network slice instances coexist, portions of the network resources and network functions may be shared between the network slice instances. The network slice instance may or may not be created from a network slice template.

A complete Network slice instance is capable of providing a complete end-to-end Network service, and what constitutes the Network slice instance may be a Sub-Network slice instance (Sub-Network slice instance) and/or a Network function. The sub-network slice instance may not need to provide complete network services end to end, and the sub-network slice instance may be a network function composition set of the same equipment provider in the network slice instance, or may be a set of network functions divided by domains, such as a core network sub-network slice instance and an access network sub-network slice instance. A sub-network slice instance may be shared by multiple network slice instances. The sub-network slicing example is provided, and the network management system management can be facilitated. A network slice instance may consist of several sub-network slice instances, each sub-network slice instance consisting of several network functions; a network slice instance may consist of several sub-network slice instances and network functions that are not divided into sub-network slice instances; it is also possible that one network slice instance consists of only a few network functions. The network functions may include physical network functions and/or virtual network functions. Hereinafter, a physical network function and/or a virtual network function are collectively referred to as a network function.

Alternatively, one network slice instance may provide multiple services simultaneously. For example, the operator uses a network slice example to provide a water meter reading service for a water company and a meter reading service for a power company. If necessary, the management data of different services can be isolated, including performance data, fault information and the like. When a network slice instance provides multiple services, the network management system may assign an identity to each service instance and make the network function and/or sub-network slice instance of the network slice instance aware of the service instances.

Network slicing template: refers to a way to generate a network slice instance, which is used to provide a reference for generating the network slice instance. The network slice template specifies how the network slice instance should be generated. For example, the network slice module may indicate which network functions the network slice contains, Key Performance Indicators (KPIs) that should be achieved, and so on.

Network function: the network function can be realized by special hardware, software running on the special hardware, or virtual function on general hardware platform. Thus, from an implementation point of view, network functions may be divided into physical network functions and virtual network functions. From the perspective of usage, the network functions may be divided into an exclusive network function and a shared network function, and specifically, for a plurality of network slice instances, different network functions may be independently used, such a network function is referred to as an exclusive network function, and may also share the same network function, such a network function is referred to as a shared network function.

To facilitate understanding of the embodiments of the present invention, the network management architecture of fig. 1A is first introduced. Fig. 1A illustrates a network management architecture 100. The Network Management architecture 100 includes three layers, which are a Network Management System (NMS for short), an Element Management System (EMS for short) and an Element (NE for short). The EMS and the NE are provided with interfaces and can communicate with each other. The EMS and the NMS have interfaces and can communicate with each other. The interface between the EMS and the NMS may be an Itf-N interface. Of course, other names for the interface are possible.

The NMS may include one or more network managers, which mainly provide network management functions, and may manage networks of different regions and different equipment providers, and a network manager may perform comprehensive monitoring on the networks through the NMS. The NMS may provide the basic functions of network management. For example: fault (Fault), Configuration (Configuration), charging (Accounting), Performance (Performance) and Security (Security) management.

The EMS may include an Element Manager (EM) and/or a Domain Manager (DM). The EM is a network module for managing the network element, and may be set on the network element or set separately. The DM is a management system module of one level greater than the management range of the EM. The DM may manage one or more EMs, for example, the DM may be a vendor's management system. It should be noted that EM and DM are different in definition, EM directly manages the same type of network device, for example, EM manages a series of base stations, DM manages a network device belonging to a device vendor (vendor), DM provides domain management function, and DM has a larger management range than EM. Typically, EM devices are used to perform the configuration of network functions. But the present embodiment does not exclude the possibility that the DM performs the process performed by the EM. The EM may be separately provided, which is illustrated in fig. 1A. It is also possible to set up on a NE, which is illustrated in fig. 1B.

The NE may be a Physical Network Function (PNF) module and/or a Virtual Network Function (VNF) module. A Physical Network Function (PNF) module is a Physical device that provides fixed network functions. For example, the physical Network function module may be a Network Element (NE) in a conventional 3GPP Network management architecture, that is, a physical Network element. The NE may be an access network device or a core network device. For example, the NE may be a base station, a Mobility Management Entity (MME), a Serving Gateway (SGW), or the like. A Virtual Network Function (VNF) module may be the smallest virtual unit in a network management architecture that can be monitored and managed.

The network slice instance may be implemented on the NE. The network slice instances are created by an NMS, which may create and manage one or more network slice instances. A network slice instance may consist of several sub-network slice instances, each sub-network slice instance consisting of several network functions; a network slice instance may also consist of several sub-network slice instances and network functions that are not divided into sub-network slice instances; it is also possible that one network slice instance consists of only a number of network functions. The radio access network may or may not be sliced. In fig. 1A, the radio access network is not sliced, and network slice example 1 and network slice example 2 share the radio access network. In fig. 1B, the radio access network is sliced, and network slice example 1 and network slice example 2 each include sliced examples of different radio access network portions.

When a plurality of network slice instances coexist, the network slice instances may be completely isolated, and also may share part of network resources and functions, and for the coexistence of the plurality of network slice instances, two scenarios are provided: group a (Group a) and Group B, as shown in fig. 2 and 3, respectively. Fig. 2 shows a schematic structural block diagram of an example of a Network slice according to an embodiment of the present invention, in fig. 2, a Radio Access Network (RAN) is shared by a Network slice example 1 and a slice example 2, and the Network slice example 1 includes a Radio Access Network and a core Network slice example 1 (which may also be referred to as a core Network subnet slice example 1). Network slice example 2 includes radio access network and core network slice example 2 (which may also be referred to as core network subnet slice example 2). Core network slice example 1 and core network slice example 2 are logically completely isolated. Fig. 3 is a schematic block diagram of a Network Slice example according to another embodiment of the present invention, in fig. 3, there is a partially shared Control Plane Function between core Network Slice example 1 and core Network Slice example 2, which is called a shared core Network Control Plane Network Function (Common CP NF), and each Network Slice example further has a dedicated core Network Control Plane Network Function (Common Control Plane Network Function, Slice CP NF) and a dedicated core Network User Plane Network Function (Slice CP NF). The example network slice 1 includes a radio access network, a shared core network control plane network function, an exclusive core network control plane network function 1, and an exclusive core network user plane network function 1. The example network slice 2 includes a radio access network, a shared core network control plane network function, an exclusive core network control plane network function 2, and an exclusive core network user plane network function 2. It is noted that the radio access network may also be sliced, and the radio access network may include network slice instances of the access network that are logically completely isolated, or there may also be partially shared network functions between network slice instances of the radio access network. Also, when the radio access network comprises a logically completely isolated network slice instance of the access network, the core network may comprise a logically completely isolated core network slice instance or the core network slice instance may have partially shared network functionality. When there is a partially shared network function between network slice instances of the radio access network, the core network may include core network slice instances that are logically completely isolated or the core network slice instances may have a partially shared network function.

In the embodiment of the present invention, on the basis of the Network management architecture 100, a Network slice management and organization (referred to as "NSM & O" for short) module is introduced into the NMS. The NSM & O module may be located on a NM or may be located separately.

The schematic structural diagram of the NSM & O module is shown in fig. 4, and its main functions include monitoring, detecting and reporting performance information and fault information of a network slice instance.

The primary functions of the NSM & O module also include any of:

service conversion: the service description information sent by the sending-end device is received through an Interface, for example, an Application Programming Interface (API), and is converted into a requirement for the network.

Designing a network slice: the composition of the network slice is described according to the result of the service conversion. For example, a Network Slice template (NSLD) may be designed.

Network slice management: and managing the life cycle of the network slice according to the designed strategy. For example, there may be network slice instantiation, network slice instance scaling, network slice instance updating, network slice instance termination, network slice deletion, and the like.

Network slicing and arranging: for specifically determining the network functions and network resources used by the network slice instance.

The sending end device is a device that sends a request to the NSM & O module. For example, the sending end device may be an operator, a third party client, an application involved in the communication service, or any other entity device that may send a request to the NSM & O.

Fig. 5 illustrates a network management method provided in an embodiment of the present invention, which may be applied to the network architectures illustrated in fig. 1A and 1B, and may also be applied to other network architectures. For example, the following network architectures apply: a network management system is used to manage the network slice instances, and may include one or more network managers. The element management system may comprise EM and/or DM. A network slice instance includes multiple network functions and/or multiple sub-network slices. The network management method of the embodiment of the present invention does not limit the network architecture. As shown in fig. 5, the method includes the steps of:

501. the network management system sends a request for configuring the alarm information to the network element management system, and the network element management system correspondingly receives the request for configuring the alarm information. The request for configuring the alarm information comprises parameters of the alarm information corresponding to the network slice example.

The alarm information refers to alarm information (alarmlnformation) that needs to be generated after the EM and/or DM in the network element management system receives a fault report of a network function and/or sub-network slice instance managed by the EM and/or DM, and the alarm information may be stored in an alarm list (AlarmList) of the EM and/or DM. The alarmlformation is a set of one or more parameters, each of which may have one or more elements, the values of which have different determinations (e.g., calculations). The parameters of the alert information may include one or more of the following: a fault severity (permissidservity) parameter, a fault trend (pendindication) parameter, a fault threshold (threshold dinfo) parameter, a monitored attributes (monitoredtributes) parameter, and a proposed repair actions (proportionality) parameter. These parameters may include one or more elements, and each element may have a different determination method (e.g., calculation method). The PercedSeveracity parameter is used to signal an emergency of failure. The PercedSeveracity parameter may include an element whose value may be Critical (Critical), important (Major), Minor (Minor), Warning (Warning), Indeterminate (inderminated), Cleared (Cleared), and the like. the trendication parameter is used to indicate that the fault condition is getting better, bad or no change. the threshold dinfo parameter is used for notifying the EMS of the identifier of the index needing to be monitored and the threshold corresponding to the index. When the EMS reports the alarm information, the mark of the performance index crossing the threshold value, the set value of the threshold value and the observed value crossing the threshold value can be reported. The monitoredAttributes parameter is used to indicate a changed monitored attribute. The proposed repair action parameter is used to indicate the EMS proposed repair action. The above five parameters are only examples, and the embodiment of the present invention is not limited to only configuring the above parameters, and the parameters of the alarm information may also include other parameters. The parameters of the alarm information correspond to the network slice example. And after the network element management system receives the fault report of the managed network function and/or sub-network slice example, determining the alarm information of the corresponding network slice example according to the fault report.

In case the network function and/or sub-network slice instance managed by the element management system is specific to a particular network slice instance, then the parameter of the alarm information included in the request for configuring alarm information in step 501 is the parameter of the alarm information of the particular network slice instance. Optionally, the request for configuring the alarm information may further include identification information of the specific network slice instance. The identification information of the particular network slice instance may be embodied in the form of a parameter or may be embodied in the form of an element. For example, when the parameter of the alarm information includes additional information (additiontext), an element of the identification information of the network slice instance may also be added.

In case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, then the parameter of the alarm information included in the request for configuring alarm information in step 501 is the parameter of the alarm information corresponding to the at least two network slice instances. Accordingly, the request for configuring the alarm information may include identification information of the at least two network slice instances and parameters of the alarm information respectively corresponding to the at least two network slice instances. The identification information of the at least two network slice instances may be embodied in the form of a parameter or may be embodied in the form of an element. For example, when the parameter of the alarm information includes additional information (additiontext), the element of the identification information of the at least two network slice instances may also be added. At least two elements may also be included for the parameters of the alarm information to embody the alarm information of the at least two network slice instances. For example, for the PercedSeveracity parameter, it may include a plurality of elements, each of which may take on the values of Critical, Major, Minor, Warneng, index, Cleared, and the like. Each element corresponds to a network slice instance indicating the impact of the fault on that network slice instance. The same fault occurring on a network function or sub-network slice instance may affect different network slice instances differently. Optionally, the parameters of the alarm information may further include a determination method of the impact of the fault on different network slice instance services, such as a calculation method of the value of an element. For the trendication parameter, it may also include multiple elements, and the value of each element represents that the corresponding network slice instance is getting better, bad or unchanged. For the threshold dinfo parameter, it may also include multiple groups of elements, where the value of each group of elements represents the identifier of the monitored threshold-crossing performance indicator, the threshold setting value, and the threshold-crossing observation value of the corresponding network slice instance. The threshold settings and the monitored indicia of the performance indicators crossing the threshold may be different or the same for each set of elements. For the monitoredAttributes parameter, it may also include a plurality of elements, each of which represents a property of the corresponding network slice instance that it is desired to monitor, and the values of which may be the same or different. For the prosedreplieractions parameter, it may also comprise multiple elements, representing the desired repair strategy for different network slice instances. For example, when two network slice instances of an electricity meter and a dangerous chemical storage temperature sensor share the same network function or sub-network slice instance, when the network function or sub-network slice instance fails, the former does not require immediate repair, and the latter may require immediate use of a backup network function or a backup sub-network slice instance, and the failed network function or sub-network slice instance is repaired and then switched back. The above parameters are merely examples, and the present invention is not limited to the configuration of only the above parameters.

The identification information of the network Slice instance may have various forms, for example, the identification information is a number, or an identification composed of a type of the network Slice instance and a special property (SD) of the Slice instance, which is not limited in the present invention. The parameters of the alarm information of the at least two network slice instances may be the same or different. The parameters of the alarm information comprise identification information of the network slice example, and the identification information can be realized by adding parameters in the alarm information, wherein the parameters are the identification information of the network slice example; or may be implemented by adding an element to the original parameter, where the element is the identification information of the network slice instance. For example, if the parameter of the alarm information includes an additional information (additional text) parameter, an element, that is, the identification information of the network slice instance, may be added.

The reason for triggering step 501 may be various and is described below by way of example. One situation may be: the EMS sends an alarm configuration request to the network management system, which receives the alarm configuration request accordingly. The alarm configuration request is used for requesting the network management system to send a request for configuring alarm information to the network element management system. This situation may occur in the event of an EM and/or DM restart, etc. Another situation may be where the creation and initial configuration of network function and/or sub-network slice instances occurs. The creation and initialization configuration of the network function and/or sub-network slice instance may occur in the following cases: i) instantiating a network slice; ii) network slice instance extension and addition of network function/sub-network slice instances; or iii) the network slice instance is updated and the newly created network function/sub-network slice instance replaces the original network function/sub-network slice instance. The network function and/or sub-network slice instance may be a network function and/or sub-network slice instance shared by at least two network slice instances, or may be a network function and/or sub-network slice instance specific to a network slice instance.

502. And the EMS configures the parameters of the alarm information according to the request for configuring the alarm information. Specifically, the EMS configures parameters of alarm information corresponding to the network slice instance,

503. EMS sends alarm information configuration confirmation to the network management system, and the network management system correspondingly receives the alarm information configuration confirmation. The alert information configuration confirmation may be used to indicate that the EMS has completed the alert information configuration.

The configuration of the alarm information can be completed through steps 501 and 503. When the network function and/or sub-network slice example has a fault, the network element management system can generate fault alarm information meeting the requirements, so that the network management system can analyze the influence of the fault on the service of the network slice example from the alarm information. For a dedicated network function and/or sub-network slice instance, the network management system can know from the alarm information the impact of the fault on the dedicated network function/sub-network slice instance. For shared network functions and/or sub-network slice examples, the network management system can distinguish different influences of faults on each network slice example, so that operators can be helped to locate fault reasons more quickly, focus key faults and guarantee key services.

504. When a network function and/or sub-network slice instance managed by the EMS fails, the network function and/or sub-network slice instance reports the failure to the EMS managing it. The fault report may contain specific information about the fault. The failure may be a hardware failure, a software failure, a network function failure, an overload, a communication link outage, or a virtualization related failure, etc.

505. After receiving the fault report, the EMS analyzes the influence of the fault in the fault report on the service running on the network slice instance using the network function and/or the sub-network slice instance, and generates corresponding alarm information (alarmlnformation) according to the alarm information parameter configuration in the request for configuring the alarm information, and stores the alarm information (AlarmList) in an alarm list (AlarmList).

Optionally, the network management method may further include the following steps:

506. the network management system sends an alarm information configuration modification notice to the network element management system, and the network element management system correspondingly receives the alarm information configuration modification notice. The alarm information configuration modification notification includes an adjustment of a parameter of the alarm information, the adjustment of the parameter of the alarm information corresponding to the network slice instance.

Expansion, contraction, and updating of network functions and/or sub-network slice instances may trigger adjustment of the alarm information configuration for the corresponding network slice instance. The extension of the network function and/or subnetwork slice instance may occur when the network slice instance is extended, in particular extending the network function and/or subnetwork slice instance includes extending its computing resources, storage resources, network resources. Shrinking a network function and/or subnetwork slice instance may occur as the network slice instance shrinks, in particular, shrinking a network function and/or subnetwork slice instance includes shrinking its computing, storage, network resources. The updating of the network function and/or sub-network slice instance may occur when the network slice instance is updated, in particular, updating the network function and/or sub-network slice instance comprises updating its software version.

After a network function and/or sub-network slice instance is expanded/contracted/updated, the network management system may send an alert information configuration modification notification to the EMS that manages the network function and/or sub-network slice instance, taking into account the impact of the fault on its corresponding network slice instance. The alert information configuration modification notification includes at least one of: adjusting a value taking method of a corresponding network slice example in the PercedSeverability parameter; adjusting the identifier of the index needing to be monitored corresponding to the network slice example in the threshold dInfo parameter or the threshold corresponding to the index; adjusting the monitored value of monitoredAttributes for the corresponding network slice instance; adjusting the repairing action of the corresponding network slice example in the proposedreparations on the fault; and adjusting the evaluation standard of the corresponding network slice example in the trending, and the like. The present invention is not limited to the above-described adjustment of parameters, and may be adjusted to other parameters. After a network function and/or sub-network slice instance is expanded, contracted, and updated, the same fault may affect its services differently. Through the alarm information configuration modification notification, the influence of the fault on the changed network slice example caused by the expansion, contraction and update of the network function and/or the sub-network slice example can be better reflected.

When newly creating a network slice instance requires using an existing network function and/or sub-network slice instance, the network function and/or sub-network slice instance needs to be configured to serve the network slice instance. The configuration may trigger the network management system to send an alert information configuration modification notification to the EMS that manages the network function and/or sub-network slice instance. The alert information configuration modification notification includes: an element is added to the parameters of the alarm information to indicate the newly created network slice instance. For example, an element is added to the permissidservity parameter, and the element is used for marking the influence degree of the fault on the newly created network slice instance; adding an element to the threshold dinfo parameter indicating an identity of a monitored performance indicator exceeding a threshold for the newly created network slice instance, a threshold, a value of a specific performance indicator; adding an element in the trendication parameter, wherein the element is used for marking the change situation of the influence of the fault on the newly created network slice instance; adding an element in the monitoredAttributes parameter, wherein the element is used for indicating that the newly created network slice instance needs to monitor the changed parameter; and adding an element in the promodedprearachions parameter, wherein the element is used for marking the repair method adopted by the newly created network slice instance. The above is merely an illustration, and elements corresponding to newly created network slice instances may be added in one or more of the above parameters. It is also possible to include adding an element corresponding to the newly created network slice instance in other parameters, for example, adding an element in the identification information of the network slice instance, the element being used to identify the newly created network slice instance. Through the alarm information configuration modification notification, the influence of the fault on the service of the newly created network slice instance can be embodied in the alarm information reported by the subsequent EMS.

When a network slice instance uses a shared network function and/or sub-network slice instance and this network slice instance terminates, the shared network function and/or sub-network slice instance cannot be terminated, but rather needs to be configured to terminate its relationship with the network slice instance. The configuration may trigger the network management system to send an alert information configuration modification notification to the EMS that manages the network function and/or sub-network slice instance. The alert information configuration modification notification includes: and deleting the element for indicating the terminated network slice instance in the parameter of the alarm information. For example: deleting an element in the PercedSeverability parameter, wherein the element marks the influence degree of the fault on the terminated network slice instance; deleting elements in the threshold dinfo parameter, which indicate the identity of the monitored performance indicators exceeding the threshold, the value of the specific performance indicator of the terminated network slice instance; adding and deleting elements in the trendication parameter, wherein the elements mark the influence change condition of the fault on the terminated network slice instance; deleting an element in the monitoredAttributes parameter that identifies a parameter for which the terminated network slice instance needs to monitor for changes; the promodedpreairations parameter has an element removed that identifies the repair method to be taken by the terminated network slice instance. The above is merely an illustration, and elements corresponding to terminated network slice instances may be deleted in one or more of the above parameters. It is also possible to include deleting the element corresponding to the terminated network slice instance in other parameters, for example, deleting the element in the identification information of the network slice instance, where the element is used to identify the terminated network slice instance. Through the alarm information configuration modification notification, the influence of the fault on the service of the terminated network slice instance can not be reflected in the alarm information reported by the subsequent EMS any more.

507. And the EMS modifies the configuration of the parameters of the alarm information according to the alarm information configuration modification notice.

508. EMS sends alarm information configuration modification confirmation to the network management system, and the network management system correspondingly receives the alarm information configuration modification confirmation. And the alarm information configuration modification confirmation is used for indicating the EMS to carry out configuration modification on parameters of the alarm information of the network slice example according to the alarm information configuration modification request.

Optionally, steps 504 and 505 may also be re-performed after step 508.

By configuring the modification notification with alarm information, parameters of the alarm information can be adjusted, which is beneficial for the EMS to feed back the impact of the network function and/or the sub-network slice instance on its now served network slice instance based on the fault report of the network function and/or the sub-network slice instance.

Fig. 6 illustrates another network management method according to an embodiment of the present invention. As shown in fig. 6, the network management method may include the steps of:

601. the network management system transmits a get alarm number (getAlarmCount) request to the EMS. Accordingly, the EMS receives the request. The getAlarmCount request is used to request the number of alarms for the corresponding network slice instance. The alarm quantity corresponding to the network slice example refers to the alarm quantity which corresponds to the network slice example and accords with the alarm information parameter.

602. The EMS sends an alarm quantity reply to the network management system. Accordingly, the network management system receives the alarm quantity reply. The alarm quantity reply comprises the alarm quantity corresponding to the network slice example.

The getAlarmCount request in step 601 may further include an alarm quantity filtering (filter) condition corresponding to the network slice instance, and the filter condition is used to filter a fault alarm that has a small impact on the service, a fault alarm that is not concerned by the operator, or an alarm related to the fault. Accordingly, the EMS reports only the alarm number satisfying the alarm number filtering condition in step 602.

In case the network function and/or sub-network slice instance managed by the element management system is specific to a particular network slice instance, the alarm quantity filter condition in step 601 is the alarm quantity filter condition of the particular network slice instance. Accordingly, the EMS only reports the alarm number of the particular network slice instance that meets the alarm number filtering condition in step 602.

In case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm quantity filter condition in step 601 is a respective alarm quantity filter condition of the at least two network slice instances. The alarm quantity filtering conditions of the at least two network slice instances can be the same or different. Accordingly, in step 602, the EMS reports the alarm numbers of the at least two network slice instances respectively meeting the alarm number filtering conditions of the at least two network slice instances. For example, network slice instance a and network slice instance B share one network function or subnetwork slice instance, then the alarm quantity filtering condition for network slice instance a and the alarm quantity filtering condition for network slice instance B may be included in step 601. Correspondingly, the EMS may initialize two counters and judge, item by item, whether each alarmninformation satisfies the filtering condition of the network slice instance a and the network slice instance B, and if a certain alarmninformation satisfies the condition of the network slice instance a and does not satisfy the condition of the network slice instance B, the counter corresponding to the network slice instance a is incremented, and the counter corresponding to the network slice instance B is not incremented. Finally, the EMS acquires the alarm quantity of the network slice example A and the network slice example B, adds the identity identification of the network slice example and reports the alarm quantity to the network management system. When the alarm quantity filtering condition of a certain network slice example is configured as full filtering, the EMS does not report the alarm quantity of the network slice example.

The getAllarmCount request comprises an alarm quantity filtering condition corresponding to the network slice example, so that the network management system can flexibly acquire the required alarm quantity corresponding to the network slice example according to different influences of faults on each network slice example, focuses on the faults which have larger influences on the network slice example service, and does not lose other information, thereby being beneficial to follow-up fault repair. Furthermore, in case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm quantity filter condition in step 601 is an alarm quantity filter condition of the at least two network slice instances. Therefore, the network management system can distinguish the influence of the network function and/or the sub-network slice example on different network slice examples and respectively acquire the alarm information which accords with the alarm parameter filtering condition of different network slice examples.

The network management method may further include the steps of:

603. the network management system transmits a get alarm list (getAlarmList) request to the EMS. Accordingly, the EMS receives the request. The getAlarmList request is used to request to obtain alarm information in an alarm list corresponding to a network slice instance.

604. The EMS transmits alarm information to the network management system. Accordingly, the network management system receives the alarm information. The form of the alarm information may be an alarm list, and the alarm list includes alarm information corresponding to the network slice instance and conforming to the alarm information parameter.

The getAlarmList request in step 603 may further include an alarm information filtering (filter) condition, where the alarm information filtering (filter) condition is corresponding to the network slice instance, and is used to filter the fault alarm that has a small impact on the service, the fault alarm that is not concerned by the operator, or the alarm of the associated fault, and the like. Accordingly, the alarm list reported by the EMS in step 604 includes the alarm information corresponding to the network slice instance and meeting the alarm information filtering condition.

In case the network function and/or sub-network slice instance managed by the element management system is specific to a particular network slice instance, the alarm information filtering condition in step 603 is the alarm information filtering condition of the particular network slice instance. Accordingly, in step 604, the EMS only reports the alarm information of the specific network slice instance that meets the alarm information filtering condition.

In case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm information filtering condition in step 603 is an alarm information filtering (filter) condition of the at least two network slice instances. The alarm information filtering conditions of the at least two network slice instances can be the same or different. Accordingly, in step 604, the EMS reports the alarm information of the at least two network slice instances respectively meeting the alarm information filtering conditions of the at least two network slice instances. The EMS may determine whether the alarmninformation conforms to the filtering condition of the alarm information of each network slice instance, and each alarmninformation reported finally only contains the corresponding element in the identity and related parameters of the corresponding network slice instance that satisfies the filtering condition of the alarm information, which may include permissivedserversity, trendinglndication, threshold, monitoredtributes, promosedpreaeration, or other parameters. For example, if a shared network function of the network slice instance a and the network slice instance B fails, the failure has different influences on the services of the network slice instance a and the network slice instance B, and the generated alarm information satisfies the alarm information filtering condition of the network slice instance a but does not satisfy the alarm information filtering condition of the network slice instance B, the reported alarm information only contains the identifier of the network slice instance a and corresponding elements in the parameters.

The getAlarm List request comprises an alarm information filtering condition corresponding to the network slice instance, so that the network management system can flexibly acquire required alarm information corresponding to the network slice instance according to different influences of faults on each network slice instance, focuses on faults which have larger influences on the service of the network slice instance, but does not lose other information, and is beneficial to follow-up fault repair. Furthermore, in case the network function and/or sub-network slice instance managed by the element management system is shared between at least two network slice instances, the alarm information filtering condition in step 603 is an alarm information filtering condition of the at least two network slice instances. Therefore, the network management system can distinguish the influence of the network function and/or the sub-network slice example on different network slice examples and respectively acquire the alarm information of different network slice examples, which accords with the alarm information filtering condition.

Steps 603 and 604 may adopt a synchronization mode, that is, after receiving the getallirmlist request, the EMS immediately reports the alarm list of the corresponding network slice instance according to the alarmllist stored in the current EMS.

Steps 603 and 604 may also adopt an asynchronous mode, that is, after receiving the getallirmlist request, the EMS does not report the alarm list of the corresponding network slice instance according to the alarmllist stored in the current EMS, but reports the alarm list of the corresponding network slice instance after updating the alarmllist after receiving the fault report sent by the managed network function and/or sub-network slice. In this case, the network management method may further include the following steps between steps 603 and 604:

605. when a network function and/or sub-network slice instance managed by the EMS fails, the network function and/or sub-network slice instance reports the failure to the EMS managing it.

606. After receiving the fault report, the EMS analyzes the influence of the fault in the fault report on the service running on the network slice instance using the network function and/or the sub-network slice instance, and generates corresponding alarm information (alarmlnformation) according to the alarm information parameter configuration in the request for configuring the alarm information, and stores the alarm information (AlarmList) in an alarm list (AlarmList).

The management method shown in fig. 5 may be extended to manage different service instances on one network slice instance, and implement configuration of alarm information and configuration modification of alarm information for the service instances of the network slice instance.

The adjustment of the parameter of the alarm information in step 506 is the service instance corresponding to the network slice instance. Specifically, when a service instance is newly created on a network slice instance, the network management system is triggered to send an alert information configuration modification notification to the corresponding EMS. The alert information configuration modification notification includes: and adding an element for indicating the newly created service instance in the parameter of the alarm information. For example, an element is added to the PercedSeveracity parameter, and the element indicates the degree of influence of the fault on the newly created service instance; adding an element to the threshold dinfo parameter indicating an identity of the monitored performance indicator exceeding the threshold for the newly created service instance, a threshold, a value of the specific performance indicator; adding an element in the trendication parameter, wherein the element is used for marking the influence change situation of the fault on the newly created service instance; adding an element in the monitoredAttributes parameter, wherein the element is used for marking the parameter which needs to monitor the change for the newly created service instance; and adding an element in the promodedRepearicons parameter, wherein the element is used for marking the repair method adopted by the newly created service instance. The above is merely an example, and it is possible to add an element corresponding to a newly created service instance in one or more of the above parameters, and it is also possible to include an element corresponding to a newly created service instance in other parameters. Through the alarm information configuration modification notification, the influence of the fault on the service of the newly created service instance can be embodied in the alarm information reported by the subsequent EMS.

When a service instance is adjusted on a network slice instance, a network management system is triggered to send an alarm information configuration modification notification to a corresponding EMS. The alert information configuration modification notification includes at least one of: adjusting the condition for judging the influence degree of the fault in the PercedSeveracity on the service instance; adjusting the identifier of the index which is required to be monitored by the corresponding service instance in the threshold dInfo parameter or the threshold value corresponding to the index; adjusting the monitored value of monitored attributes for the service instance; adjusting a fault repairing action for the service instance in the promodedRepiaractons; and adjusting the evaluation standard of the change trend of the fault in the trendIndication to the service instance. The invention is not limited to only the adjustment of said parameters, but also other parameters are possible. After a network function and/or sub-network slice instance is expanded, contracted, and updated, the same fault may affect its services differently. Through the alarm information configuration modification notification, the influence of the fault on the changed network slice example caused by the expansion, contraction and update of the network function and/or the sub-network slice example can be better reflected. Adjusting a service instance includes adjusting a resource usage policy of the service instance, such as adjusting network resources, computing resources, or storage resources used by the service instance.

When the service instance is terminated on the network slice instance, the network management system is triggered to send an alarm information configuration modification notification to the corresponding EMS. The alert information configuration modification notification includes: and deleting the element for indicating the terminated service instance in the parameter of the alarm information. For example: deleting an element in the PercedSeverability parameter, wherein the element marks the influence degree of the fault on the terminated service instance; deleting elements in the threshold dinfo parameter that identify an identity of a monitored performance indicator that exceeds a threshold for the terminated service instance, the threshold, a value of the specific performance indicator; deleting an element in the trendication parameter, wherein the element marks the influence change situation of the fault on the terminated service instance; deleting an element in the monitoredAttributes parameter, the element indicating that the terminated service instance needs to monitor for a changed parameter; the promodedpreawaractions parameter has an element removed that identifies the repair method to be taken for the terminated service instance. The above is merely an example, and it is possible to delete the element corresponding to the terminated service instance in one or more of the above parameters, and it is also possible to include deleting the element corresponding to the terminated service instance in other parameters. Through the alarm information configuration modification notification, the influence of the fault on the service of the terminated service instance can not be reflected in the alarm information reported by the subsequent EMS any more.

In step 505, after receiving the fault report, the EMS analyzes the effect of the fault in the fault report on the service instance running on the network slice instance using the network function and/or sub-network slice instance, and generates corresponding alarm information according to the alarm information parameter configuration, and stores the alarm information in the alarm list.

When the service instance on the network slice instance is changed (such as newly built, adjusted or terminated), the alarm information can reflect the influence of the fault on the service instance of the changed network slice instance. The network management system can distinguish the influence of the fault on different service instances from the reported alarm information.

The management method shown in fig. 6 may be extended to management of different service instances on one network slice instance, and may obtain the number of alarms and the alarm list of the service instance corresponding to the network slice instance. In this case, the getAlarmCount request in step 601 is an alarm number for requesting to acquire a service instance of the corresponding network slice instance. The service instance alarm quantity corresponding to the network slice instance refers to the alarm quantity of the service instance corresponding to the network slice instance, which accords with the alarm information parameter. The number of alarms sent by the EMS in step 602 is the number of alarms for the service instance corresponding to the network slice instance.

The getAlarmCount request in step 601 may also include an alarm quantity filter (filter) condition for the service instance corresponding to the network slice instance. Accordingly, the EMS only reports the number of alarms meeting the alarm number filtering condition of the service instance of the corresponding network slice instance in step 602.

The getAlarmList request in step 603 is an alarm list for requesting a service instance of the corresponding network slice instance. In step 604, the alarm list sent by the EMS to the network management system is a service instance corresponding to the network slice instance, and the alarm list includes alarm information of the service instance corresponding to the network slice instance.

The getAlarmList request in step 603 may also include an alarm information filter (filter) condition for the service instance corresponding to the network slice instance. Accordingly, in step 604, the EMS only reports the alarm information of the service instance of the network slice instance that meets the alarm information filtering condition.

The management method shown in fig. 5 may be extended to different sub-network slice examples on one network slice, and the configuration of the alarm information and the configuration modification of the alarm information may be performed on the sub-network slice example of the network slice example. In this case, the request for configuring alarm information in step 501 includes parameters of alarm information for the sub-network slice instance corresponding to the network slice instance. In step 502, the EMS configures parameters of the alarm information of the sub-network slice instance corresponding to the network slice instance. In step 505, after receiving the fault report, the EMS analyzes the effect of the fault in the fault report on the sub-network slice instance running on the network slice instance using the network function and/or the sub-network slice instance, and generates corresponding alarm information according to the alarm information parameter configuration, and stores the alarm information in the alarm list. The adjustment of the parameter of the alarm information in step 506 is the sub-network slice instance corresponding to the network slice instance.

The management method shown in fig. 6 may be extended to different sub-network slice examples on one network slice, and may obtain the alarm number and the alarm list of the sub-network slice example corresponding to the network slice example. In this case, the getAlarmCount request in step 601 is an alarm number for requesting to obtain a subnet slice instance corresponding to the network slice instance. The sub-network slice instance alarm quantity corresponding to the network slice instance refers to the alarm quantity of the sub-network slice instance corresponding to the network slice instance, which accords with the alarm information parameter. The number of alarms sent by the EMS in step 602 is the number of alarms for the sub-network slice instance corresponding to the network slice instance.

The getAlarmCount request in step 601 may also include an alarm quantity filter (filter) condition for the sub-network slice instance corresponding to the network slice instance. Accordingly, the EMS only reports the number of alarms meeting the alarm number filtering condition of the sub-network slice instance of the corresponding network slice instance in step 602.

The getAlarmList request in step 603 is an alarm list for requesting a sub-network slice instance corresponding to the network slice instance. In step 604, the alarm list sent by the EMS to the network management system is the sub-network slice instance corresponding to the network slice instance, and the alarm list includes the alarm information of the sub-network slice instance corresponding to the network slice instance.

The getAlarmList request in step 603 may also include an alarm information filter (filter) condition for the sub-network slice instance corresponding to the network slice instance. Accordingly, in step 604, the EMS only reports the alarm information of the sub-network slice instance of the network slice instance that meets the alarm information filtering condition.

The network management method and the network management architecture according to the embodiment of the present invention are described in detail above with reference to fig. 1A to 6, and the network management system and the network element management system according to the embodiment of the present invention are described in detail below with reference to fig. 7 to 10.

Fig. 7 is a schematic block diagram of a network management system 700 of an embodiment of the present invention. It should be understood that network management system 700 is capable of performing the various steps performed by the NMS in the methods of fig. 5-6, and will not be described in detail herein to avoid repetition. The network management system 700 includes: a transmitting unit 710 and a receiving unit 720 connected to each other.

Specifically, the sending unit 710 is configured to send a request for configuring alarm information to the element management system, where the request for configuring alarm information includes a parameter of the alarm information, the parameter of the alarm information corresponds to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance. The receiving unit 720 is configured to receive alarm information configuration completion information sent by the network element management system, where the alarm information configuration completion information is used to instruct the network element management system to perform configuration of parameters of alarm information of a network slice instance according to the request for configuring the alarm information.

Optionally, the sending unit 710 is further configured to send an alarm information configuration modification notification to the network element management system, where the alarm information configuration modification notification includes an adjustment of a parameter of alarm information, and the adjustment of the parameter of alarm information corresponds to a network slice instance; the receiving unit 720 is further configured to receive an alarm information configuration modification confirmation sent by the network element management system, where the alarm information configuration modification confirmation is used to indicate that the network element management system performs configuration modification on parameters of alarm information of a network slice instance according to the alarm information configuration modification request.

Optionally, the sending unit 710 is further configured to send a request for obtaining the alarm quantity to the network element management system, where the alarm quantity request is used to request to obtain the alarm quantity of the corresponding network slice instance. The receiving unit 720 is further configured to receive the alarm quantity sent by the network element management system and corresponding to the network slice instance.

Optionally, the alarm quantity request includes an alarm quantity filter condition, and in the case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm quantity filter condition is a filter condition corresponding to the alarm quantities of the at least two network slice instances. The receiving unit 720 is configured to receive the alarm quantity corresponding to the network slice example and meeting the filtering condition of the alarm quantity of the network slice example, where the alarm quantity is sent by the network element management system.

Optionally, the sending unit 710 is configured to send a request for obtaining an alarm list to the network element management system, where the alarm list request is used to request to obtain alarm information in an alarm list of a corresponding network slice instance. The receiving unit 720 is configured to receive the alarm information that is sent by the network element management system and conforms to the alarm information parameter.

Optionally, the alarm list request includes an alarm information filtering condition, and in a case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filtering condition is a filtering condition of alarm information corresponding to the at least two network slice instances. The receiving unit 720 is configured to receive the alarm information sent by the network element management system, which corresponds to the network slice instance and meets the alarm information filtering condition of the network slice instance.

Figure 8 is a schematic block diagram of a network element management system 800 of an embodiment of the present invention. It should be understood that the element management system 800 is capable of performing the various steps performed by the EMS in the methods of fig. 5-6, and will not be described in detail herein to avoid repetition. The network element management system 800 includes: a transmitting unit 810 and a receiving unit 820 connected to each other.

Specifically, the receiving unit 820 is configured to receive a request for configuring alarm information sent by a network management system, where the request for configuring alarm information includes a parameter of the alarm information, the parameter of the alarm information corresponds to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance. The sending unit 810 is configured to send alarm information configuration completion information to the network management system, where the alarm information configuration completion information is used to indicate that the network element management system performs configuration of parameters of alarm information of a network slice instance according to the request for configuring the alarm information.

Optionally, the receiving unit 820 is further configured to receive an alarm information configuration modification notification sent by the network management system, where the alarm information configuration modification notification includes an adjustment of a parameter of alarm information, and the adjustment of the parameter of alarm information corresponds to a network slice instance. The sending unit 810 is further configured to send an alarm information configuration modification confirmation to the network management system, where the alarm information configuration modification confirmation is used to indicate that the network element management system performs configuration modification on parameters of alarm information of a network slice instance according to the alarm information configuration modification request.

Optionally, the receiving unit 820 is further configured to receive an alarm quantity obtaining request sent by the network management system, where the alarm quantity obtaining request is used to request to obtain the alarm quantity of the corresponding network slice instance. The sending unit 810 is further configured to send the alarm amount corresponding to the network slice instance to the network management system.

Optionally, the alarm quantity request includes an alarm quantity filter condition, and in the case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm quantity filter condition is a filter condition corresponding to the alarm quantities of the at least two network slice instances. The sending unit 810 is further configured to send, to the network management system, the alarm quantity corresponding to the network slice instance and meeting the filtering condition of the alarm quantity of the network slice instance.

Optionally, the receiving unit 820 is further configured to receive an alarm list obtaining request sent by the network management system, where the alarm list obtaining request is used to request to obtain alarm information in an alarm list of a corresponding network slice instance. The sending unit 810 is further configured to send alarm information meeting the alarm information parameter to the network management system.

Optionally, the alarm list request includes an alarm information filtering condition, and in a case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filtering condition is a filtering condition of alarm information corresponding to the at least two network slice instances. The sending unit 810 is further configured to send alarm information corresponding to the network slice instance and meeting the alarm information filtering condition of the network slice instance to the network management system.

Fig. 9 is a schematic block diagram of a network management system 900 of an embodiment of the present invention. It should be understood that the network management system 900 is capable of performing the various steps performed by the NMS in the methods of fig. 5-6, and will not be described in detail herein to avoid repetition. The network management system 900 includes: a transceiver 920, a memory 910, and a processor 930. The memory 910 is used to store instructions.

A processor 930 coupled to the memory 910 and the transceiver 920, respectively, is configured to execute the instructions stored in the memory 910, so as to perform the following steps when executing the instructions: sending a request for configuring alarm information to an element management system through the transceiver 920, where the request for configuring alarm information includes parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances include network functions and/or sub-network slice instances; receiving, by the transceiver 920, alarm information configuration completion information sent by the network element management system, where the alarm information configuration completion information is used to indicate that the network element management system performs configuration of parameters of alarm information of a network slice instance according to the request for configuring the alarm information.

Optionally, in a case that the network function or sub-network slice instance is shared between at least two network slice instances, the parameter of the alarm information corresponds to the at least two network slice instances, and the request for configuring the alarm information further includes identification information of the at least two network slice instances.

Optionally, the processor 930 further performs the following steps when executing the instructions: sending an alarm information configuration modification notification to the element management system through the transceiver 920, where the alarm information configuration modification notification includes an adjustment of a parameter of alarm information, and the adjustment of the parameter of alarm information corresponds to a network slice instance; receiving, by the transceiver 920, an alarm information configuration modification confirmation sent by the network element management system, where the alarm information configuration modification confirmation is used to indicate that the network element management system performs configuration modification on parameters of alarm information of a network slice instance according to the alarm information configuration modification request.

Optionally, the processor 930 further performs the following steps when executing the instructions: sending an alarm quantity obtaining request to the element management system through the transceiver 920, where the alarm quantity request is used to request to obtain the alarm quantity of the corresponding network slice instance; and receiving the alarm quantity sent by the network element management system corresponding to the network slice instance through the transceiver 920.

Optionally, the alarm quantity request includes an alarm quantity filter condition, and in the case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm quantity filter condition is a filter condition corresponding to the alarm quantities of the at least two network slice instances. The processor 930, when executing the instructions, further performs the steps of: and receiving, by the transceiver 920, the alarm quantity corresponding to the network slice instance and meeting the filtering condition of the alarm quantity of the network slice instance, where the alarm quantity is sent by the network element management system.

Optionally, the processor 930 further performs the following steps when executing the instructions: sending a request for obtaining an alarm list to the element management system through the transceiver 920, where the alarm list request is used to request to obtain alarm information in an alarm list corresponding to a network slice instance; and receiving the alarm information which is sent by the network element management system and conforms to the alarm information parameter through the transceiver 920.

Optionally, the alarm list request includes an alarm information filtering condition, and in a case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filtering condition is a filtering condition of alarm information corresponding to the at least two network slice instances. The processor 930, when executing the instructions, further performs the steps of: and receiving, by the transceiver 920, alarm information corresponding to the network slice instance and meeting the alarm information filtering condition of the network slice instance, which is sent by the network element management system.

Figure 10 is a schematic block diagram of a network element management system 1000 of an embodiment of the present invention. It should be understood that the element management system 1000 can perform the various steps performed by the NMS in the methods of figures 5 to 6, and will not be described in detail herein to avoid repetition. The network element management system 1000 includes: a transceiver 1020, a memory 1010, and a processor 1030. The memory 1010 is used to store instructions.

The processor 1030 is connected to the memory 1010 and the transceiver 1020, respectively, and configured to execute the instructions stored in the memory 1010, so as to perform the following steps when executing the instructions: receiving, by the transceiver 1020, a request for configuring alarm information sent by a network management system, where the request for configuring alarm information includes a parameter of the alarm information, the parameter of the alarm information corresponds to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance; sending alarm information configuration completion information to the network management system through the transceiver 1020, where the alarm information configuration completion information is used to indicate that the network element management system 1000 performs configuration of parameters of alarm information of a network slice instance according to the request for configuring the alarm information.

Optionally, the processor 1030, when executing the instructions, further performs the steps of: receiving, by the transceiver 1020, an alarm information configuration modification notification sent by the network management system, where the alarm information configuration modification notification includes an adjustment of a parameter of alarm information, and the adjustment of the parameter of alarm information corresponds to a network slice instance; sending an alarm information configuration modification confirmation to the network management system through the transceiver 1020, where the alarm information configuration modification confirmation is used to instruct the network element management system 1000 to perform configuration modification of parameters of alarm information of a network slice instance according to the alarm information configuration modification request.

Optionally, the processor 1030, when executing the instructions, further performs the steps of: receiving, by the transceiver 1020, an alarm quantity obtaining request sent by the network management system, where the alarm quantity obtaining request is used to request to obtain an alarm quantity of a corresponding network slice instance; sending, by the transceiver 1020, an alarm quantity corresponding to the network slice instance to the network management system.

Optionally, the alarm quantity request includes an alarm quantity filter condition, and in the case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm quantity filter condition is a filter condition corresponding to the alarm quantities of the at least two network slice instances. The processor 1030, when executing the instructions, further performs the steps of: sending, by the transceiver 1020, to the network management system, an alarm quantity corresponding to the network slice instance and meeting a filtering condition of the alarm quantity of the network slice instance.

Optionally, the processor 1030, when executing the instructions, further performs the steps of: receiving, by the transceiver 1020, an alarm list acquisition request sent by the network management system, where the alarm list acquisition request is used to request to acquire alarm information in an alarm list of a corresponding network slice instance; sending the alarm information conforming to the alarm information parameter to the network management system through the transceiver 1020.

Optionally, the alarm list request includes an alarm information filtering condition, and in a case that the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information filtering condition is a filtering condition of alarm information corresponding to the at least two network slice instances. The processor 1030, when executing the instructions, further performs the steps of: the network element management system 1000 sends alarm information corresponding to the network slice instance and meeting the alarm information filtering condition of the network slice instance to the network management system.

In fig. 7-10, in case the network function or sub-network slice instance is shared between at least two network slice instances, the parameters of the alarm information are corresponding to the at least two network slice instances, and the request for configuring alarm information further comprises identification information of the at least two network slice instances.

When a network slice instance is newly created, the adjusting of the parameter of the alarm information includes adding an identifier of the newly created network slice instance to the parameter of the alarm information. Or, when terminating a network slice instance, the adjusting of the parameter of the alarm information includes deleting the identifier of the terminated network slice instance in the parameter of the alarm information. Or when the network function and/or the sub-network slice instance is expanded, contracted or updated, the adjustment of the parameter of the alarm information includes adjusting a value of the parameter of the alarm information.

It should be understood that, in the embodiment of the present invention, the processor of the above apparatus may be a Central Processing Unit (CPU), and the processor may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software elements in a processor. The software elements may be located in ram, flash, rom, prom, or eprom, registers, among other storage media that are well known in the art. The storage medium is located in a memory, and a processor executes instructions in the memory, in combination with hardware thereof, to perform the steps of the above-described method. To avoid repetition, it is not described in detail here.

Those of ordinary skill in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both, and that the steps and elements of the various embodiments have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

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

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

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

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

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

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A network management method, comprising:

the network management system sends a request for configuring the alarm information to a network element management system, wherein the request for configuring the alarm information comprises parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances comprise network functions and/or sub-network slice instances;

and the network management system receives alarm information configuration completion information sent by the network element management system, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

2. The method of claim 1, wherein:

in case the network function or sub-network slice instance is shared between at least two network slice instances, the parameters of the alarm information are for the at least two network slice instances, the request to configure alarm information further comprises identification information of the at least two network slice instances.

3. A method according to claim 1 or 2, characterized in that the method further comprises:

the network management system sends an alarm information configuration modification notice to the network element management system, wherein the alarm information configuration modification notice comprises adjustment of parameters of alarm information, and the adjustment of the parameters of the alarm information corresponds to a network slice example;

and the network management system receives an alarm information configuration modification confirmation sent by the network element management system, wherein the alarm information configuration modification confirmation is used for indicating the network element management system to carry out configuration modification on parameters of the alarm information of the network slice example according to the alarm information configuration modification request.

4. The method of claim 3, wherein:

when a network slice instance is newly created, the adjustment of the parameters of the alarm information comprises adding the identification of the newly created network slice instance in the parameters of the alarm information; or

When the network slice instance is terminated, the adjustment of the parameters of the alarm information comprises deleting the identifier of the terminated network slice instance in the parameters of the alarm information; or

When the network function and/or the sub-network slice instance is expanded, contracted or updated, the adjustment of the parameter of the alarm information includes adjusting a value of the parameter of the alarm information.

5. A method of network management, characterized in that it comprises all the features of the method of any one of claims 1 to 4, and in that it further comprises:

the network management system sends an alarm quantity obtaining request to the network element management system, wherein the alarm quantity request is used for requesting to obtain the alarm quantity of the corresponding network slice example;

and the network management system receives the alarm quantity corresponding to the network slice example sent by the network element management system.

6. The method of claim 5, wherein:

the alarm quantity request comprises an alarm quantity filter condition, the alarm quantity filter condition being a filter condition of the alarm quantity corresponding to at least two network slice instances in case the network function and/or the sub-network slice instance is shared between the at least two network slice instances;

the network management system receiving the alarm quantity corresponding to the network slice instance sent by the network element management system, including: and the network management system receives the alarm quantity which is sent by the network element management system, corresponds to the network slice example and accords with the filtering condition of the alarm quantity of the network slice example.

7. A method of network management, characterized in that it comprises all the features of the method of any one of claims 1 to 4, and in that it further comprises:

the network management system sends a request for acquiring an alarm list to the network element management system, wherein the alarm list request is used for requesting to acquire alarm information in an alarm list corresponding to a network slice example;

and the network management system receives the alarm information which is sent by the network element management system and accords with the alarm information parameter.

8. The method of claim 7, wherein:

the alarm list request comprises an alarm information filter condition, the alarm information filter condition being a filter condition of alarm information corresponding to at least two network slice instances in case the network function and/or the sub-network slice instance is shared between the at least two network slice instances;

the network management system receiving the alarm information which is sent by the network element management system and accords with the alarm information parameter, and the method comprises the following steps: and the network management system receives the alarm information which is sent by the network element management system, corresponds to the network slice example and accords with the alarm information filtering condition of the network slice example.

9. A network management method, comprising:

the network element management system receives a request for configuring the alarm information sent by the network management system, wherein the request for configuring the alarm information comprises parameters of the alarm information, the parameters of the alarm information correspond to network slice examples, and the network slice examples comprise network functions and/or sub-network slice examples;

and the network element management system sends alarm information configuration completion information to the network management system, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

10. A network management system, characterized by comprising:

a transceiver for receiving and transmitting a signal from the wireless communication device,

a memory to store instructions;

a processor is coupled to the memory and the transceiver, respectively, and configured to execute the instructions stored in the memory, so as to perform the following steps when executing the instructions:

sending a request for configuring alarm information to a network element management system through the transceiver, wherein the request for configuring alarm information comprises parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances comprise network functions and/or sub-network slice instances;

and receiving alarm information configuration completion information sent by the network element management system through the transceiver, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

11. A network element management system, comprising:

a memory to store instructions;

receiving, by the transceiver, a request for configuring alarm information sent by a network management system, where the request for configuring alarm information includes parameters of the alarm information, the parameters of the alarm information correspond to network slice instances, and the network slice instances include network functions and/or sub-network slice instances;

and sending alarm information configuration completion information to the network management system through the transceiver, wherein the alarm information configuration completion information is used for indicating that the network element management system performs configuration of parameters of alarm information of a network slice example according to the request for configuring the alarm information.

12. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a computer device, is capable of implementing the method of any one of claims 1 to 8.

13. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a computer device, is able to implement the method of claim 9.