WO2018121453A1 - Procédé de gestion de réseau, système de gestion de réseau et système de gestion d'élément de réseau - Google Patents

Procédé de gestion de réseau, système de gestion de réseau et système de gestion d'élément de réseau Download PDF

Info

Publication number
WO2018121453A1
WO2018121453A1 PCT/CN2017/118145 CN2017118145W WO2018121453A1 WO 2018121453 A1 WO2018121453 A1 WO 2018121453A1 CN 2017118145 W CN2017118145 W CN 2017118145W WO 2018121453 A1 WO2018121453 A1 WO 2018121453A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
alarm information
management system
network slice
slice instance
Prior art date
Application number
PCT/CN2017/118145
Other languages
English (en)
Chinese (zh)
Inventor
陆伟
杨水根
孙文琦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018121453A1 publication Critical patent/WO2018121453A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H04L41/0609—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on severity or priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring

Definitions

  • the present patent application relates to the field of communications, and more particularly to a network management method, a network management system, and a network element management system.
  • 5G fifth generation wireless communication technology
  • 5G will support diverse application needs, including support for higher speed experiences and greater bandwidth access, lower latency and highly reliable information interaction, and the connection of larger and lower cost machine-like communication devices. Entry and management, etc.
  • 5G will support a variety of vertical industry applications for vehicle networking, emergency communications, and industrial Internet. Faced with these performance requirements and application scenarios of 5G, 5G networks need to be closer to the specific needs of users, and their customization capabilities need to be further improved.
  • 5G introduced the important concept of network slicing.
  • One or more network slice instances are included in the network system.
  • it may include Critical Machine Type Communication (Critical MTC) network slicing instance, Massive Machine Type Communication (Massive MTC) network slicing instance, and Mobile Broad Band (MBB for short).
  • Critical MTC Critical Machine Type Communication
  • Massive Machine Type Communication Massive Machine Type Communication
  • MBB Mobile Broad Band
  • Embodiments of the present invention provide a method and apparatus for network management, in order to implement management of a network system including a network slice instance.
  • the first aspect provides a network management method, including: a network management system sends a request for configuring alarm information to a network element management system, where the request for configuring the alarm information includes a parameter of the alarm information; and the network management system receives the The alarm information configuration completion information sent by the NE management system.
  • the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance.
  • the alarm information configuration completion information is used to instruct the network element management system to perform parameter configuration of the alarm information of the network slice instance according to the request for configuring the alarm information.
  • the configuration of the alarm information can be completed, thereby implementing management of the network system including the network slice instance, in particular, fault management of the network system.
  • the parameter of the alarm information is corresponding to the network slice instance, and the configuration of the parameter of the alarm information can meet the requirements of fault management of different network slice instances.
  • 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 service of the fault to the network slice instance from the alarm information. influences.
  • the method further includes: the network management system sending an alarm information configuration modification notification to the network element management system.
  • the network management system receives an alarm information configuration modification confirmation sent by the network element management system.
  • the alarm information configuration modification notification includes adjustment of the parameter of the alarm information, and the adjustment of the parameter of the alarm information is corresponding to the network slice instance.
  • the alarm information configuration modification confirmation is used to instruct the network element management system to perform configuration modification of the parameter of the network segment instance alarm information according to the alarm information configuration modification request.
  • the modification notification by the alarm information the parameters of the alarm information can be adjusted, which is beneficial for the EMS to feed back the network function and/or the sub-network slice instance according to the network function and/or the sub-network slice instance fault report. influences.
  • the method further includes: the network management system sends a request for acquiring an alarm quantity to the network element management system, where the alarm quantity request is used to request to obtain an alarm quantity of a corresponding network slice instance;
  • the network management system receives the number of alarms sent by the network element management system corresponding to the network slice instance.
  • the alarm quantity request includes an alarm quantity filtering condition.
  • the filtering condition of the alarm quantity is filtering corresponding to the number of alarms of the at least two network slice instances. condition. Receiving, by the network management system, the number of alarms corresponding to the network slice instance sent by the network element management system, where the network management system receives an instance of the network slice that is sent by the network element management system, and is consistent with the Number of alarms for the filtering conditions of the number of alarms of the network snippet instance.
  • the alarm quantity request includes the alarm quantity filtering condition of the corresponding network snippet instance, so that the network management system can flexibly obtain the required number of alarms of the corresponding network sharding instance according to the different impacts of the fault on each network sharding instance, and focus on the network snippet instance service.
  • the alarm quantity filtering condition is an alarm quantity filtering condition of the at least two network slice instances. . This allows the network management system to distinguish the impact of the network function and/or the fault of the sub-network sharding instance on different network snippet instances, and obtain the number of alarms that meet the alarm quantity filtering conditions of different network sharding instances.
  • the method further includes: the network management system sending a request for acquiring an alarm list to the network element management system, where the alarm list request is used to request an alarm in an alarm list corresponding to a network slice instance.
  • the network management system receives the alarm information that is sent by the network element management system and meets the alarm information parameter.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm information is corresponding to the Filtering conditions of alarm information of at least two network slice instances.
  • the network management system receives the alarm information that is sent by the network element management system and meets the alarm information parameter, and the network management system receives the network slice instance that is sent by the network element management system and meets the Alarm information of the alarm information filtering condition of the network snippet instance.
  • the alarm list request includes the alarm information filtering condition of the corresponding network snippet instance, so that the network management system can flexibly obtain the required alarm information of the corresponding network sharding instance according to the different impacts of the fault on each network sharding instance, and focus on the network snippet instance service.
  • the alarm information filtering condition is the alarm information filtering condition of the at least two network slice instances. . This allows the network management system to distinguish the impact of the network function and/or the sub-network snippet instance fault on different network snippet instances, and obtain the alarm information of the different network snippet instances that meet the filtering conditions of the alarm information.
  • the method further includes: the network management system receiving an alarm configuration request sent by the network element management system, where the alarm configuration request is used to request the network management system to manage the network element The system sends a request to configure alarm information.
  • a method of managing network slices including the following steps.
  • the network element management system receives the request for configuring the alarm information sent by the network management system, where the request for configuring the alarm information includes the parameter of the alarm information; and the network element management system sends the alarm information configuration completion information to the network management system.
  • the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance.
  • the alarm information configuration completion information is used to instruct the network element management system to perform parameter configuration of the alarm information of the network slice instance according to the request for configuring the alarm information.
  • the method further includes: the network element management system receives an alarm information configuration modification notification sent by the network management system, where the alarm information configuration modification notification includes adjustment of an alarm information parameter, and alarm information.
  • the adjustment of the parameters is corresponding to the network slice instance.
  • the network element management system sends an alarm information configuration modification confirmation to the network management system, where the alarm information configuration modification confirmation is used to instruct the network element management system to perform an alarm of the network slice instance according to the alarm information configuration modification request.
  • the configuration modification of the parameters of the information is performed by the network management system, where the alarm information configuration modification notification includes adjustment of an alarm information parameter, and alarm information.
  • the adjustment of the parameters is corresponding to the network slice instance.
  • the network element management system sends an alarm information configuration modification confirmation to the network management system, where the alarm information configuration modification confirmation is used to instruct the network element management system to perform an alarm of the network slice instance according to the alarm information configuration modification request.
  • the configuration modification of the parameters of the information is performed by the network management system, where the alarm information configuration modification notification includes adjustment of an
  • the method further includes: receiving, by the network element management system, a request for acquiring an alarm quantity sent by the network management system, where the number of alarms is used to request to obtain an alarm quantity of a corresponding network slice instance;
  • the network element management system sends the number of alarms corresponding to the network slice instance to the network management system.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the number of alarms
  • the filter condition is a filter condition corresponding to the number of alarms of the at least two network slice instances
  • the network element management system sends the number of alarms corresponding to the network slice instance to the network management system, including: the network element management The system sends, to the network management system, an alarm quantity corresponding to the network slice instance and the filtering condition that meets the number of alarms of the network slice instance.
  • the network element management system receives an acquisition alarm list request sent by the network 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 meta management system sends the alarm information that meets the alarm information parameter to the network management system.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information
  • the filter condition is a filter condition corresponding to the alarm information of the at least two network slice instances;
  • the network element management system sends the alarm information that meets the alarm information parameter to the network management system, including: the network element management The system sends the alarm information corresponding to the network slice instance and the alarm information filtering condition of the network slice instance to the network management system.
  • a network management system including: a transceiver, a memory, and a processor.
  • the memory is configured to store instructions, the processor being coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:
  • the transceiver sends a request for configuring the alarm information to the network element management system, where the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or Or the sub-network segment instance; receiving, by the transceiver, the 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 the request according to the configuration alarm information The configuration of the parameters of the alarm information of the network slice instance is performed.
  • the processor when executing the instruction, further performing the step of: sending, by the transceiver, an alarm information configuration modification notification to the network element management system, where the alarm information configuration modification notification includes an alarm
  • the adjustment of the parameter of the information, the adjustment of the parameter of the alarm information is corresponding to the network slice instance; receiving, by the transceiver, the alarm information configuration modification confirmation sent by the network element management system, where the alarm information configuration modification confirmation is used to indicate the location
  • the network element management system performs configuration modification of the parameter of the alarm information of the network segmentation instance according to the configuration information of the alarm information configuration modification request.
  • the processor further performs the following steps: sending, by the transceiver, a request for acquiring an alarm quantity to the network element management system by using the transceiver, where the alarm quantity request is used to request to obtain a corresponding The number of alarms of the network shard instance; the number of alarms sent by the network element management system corresponding to the network shard instance is received by the transceiver.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the number of alarms
  • the filtering condition is a filtering condition corresponding to the number of alarms of the at least two network slice instances.
  • the processor further performs the following steps: receiving, by the transceiver, an alarm sent by the network element management system corresponding to the network slice instance and the filtering condition that meets the number of alarms of the network slice instance. Quantity.
  • the processor when executing the instruction, further performs the step of: sending, by the transceiver, a request for acquiring an alarm list to the network element management system, where the alarm list request is used to request to obtain a corresponding The alarm information in the alarm list of the network splicing instance; the alarm information sent by the network element management system that meets the alarm information parameter is received by the transceiver.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information
  • the filtering condition is a filtering condition corresponding to the alarm information of the at least two network slice instances.
  • the processor further performs the following steps: receiving, by the transceiver, the alarm information that is sent by the network element management system and corresponds to the network slice instance and the alarm information filtering condition that meets the network slice instance. .
  • a network element management system including: a transceiver, a memory, and a processor.
  • the memory is configured to store instructions, the processor being coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:
  • the transceiver receives a request for configuring the alarm information sent by the network management system, where the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or Or the sub-network pinging instance; sending, by the transceiver, the alarm information configuration completion information to the network management system, where the alarm information configuration completion information is used to instruct the network element management system to perform the request according to the configuration alarm information. Configuration of the parameters of the alarm information of the network slice instance.
  • the processor further performs the following steps: receiving, by the transceiver, an alarm information configuration modification notification sent by the network management system by using the transceiver, where the alarm information configuration modification notification includes an alarm
  • the alarm information configuration modification notification includes an alarm
  • the transceiver sends an alarm information configuration modification confirmation to the network management system, and the alarm information configuration modification confirmation is used to indicate the network
  • the meta-management system performs configuration modification of the parameters of the alarm information of the network sharding instance according to the configuration information of the alarm information.
  • the processor further performs the following steps: receiving, by the transceiver, a request for acquiring an alarm sent by the network management system by using the transceiver, where the alarm quantity request is used to request to obtain a corresponding The number of alarms of the network slice instance; the number of alarms corresponding to the network slice instance is sent to the network management system by the transceiver.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the number of alarms
  • the filtering condition is a filtering condition corresponding to the number of alarms of the at least two network slice instances; when the processor executes the instruction, the processor further performs the following steps: sending, by the transceiver, the corresponding to the network management system The number of alarms of the network snippet instance and the filtering conditions that match the number of alarms of the network snippet instance.
  • the processor further performs the following steps: receiving, by the transceiver, an acquisition alarm list request sent by the network management system, where the alarm list request is used to request to obtain a corresponding The alarm information in the alarm list of the network splicing instance; the alarm information corresponding to the alarm information parameter is sent to the network management system by the transceiver.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the alarm information
  • the filter condition is a filter condition corresponding to the alarm information of the at least two network slice instances; when the processor executes the instruction, the processor further performs the following steps: the network element management system sends a corresponding place to the network management system The network slice instance and the alarm information that meets the filtering conditions of the alarm information of the network slice instance.
  • the request for configuring the alarm information further includes the identifier information of the at least two network slice instances.
  • the network management system can resolve the different impacts of faults on each of the network slicing instances in at least two network slicing instances, thereby helping operators to locate fault causes faster and focus on critical faults. To protect key services.
  • the adjustment 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.
  • the parameter of the alarm information is adjusted, and the identifier of the newly created network slice instance is added to the parameter of the alarm information. It is beneficial to reflect the impact of the fault on the newly created network slice instance in the alarm information.
  • the adjustment of the parameter of the alarm information includes deleting the identifier of the terminated network slice instance in the parameter of the alarm information.
  • the parameter of the alarm information is adjusted, and the identifier of the terminated network slice instance is deleted in the parameter of the alarm information. Adjusting the parameter configuration of the corresponding alarm information is beneficial to the fact that the impact of the fault on the terminated network slice instance is no longer reflected in the alarm information.
  • the adjustment of the parameters of the alert information includes adjusting parameters of the alert information.
  • the value when the network function and/or the sub-network slice instance is extended, contracted, or updated, the parameter of the alarm information is adjusted, and the value of the parameter of the alarm information is adjusted in the parameter of the alarm information. Adjusting the parameter configuration of the corresponding alarm information is beneficial to embody the impact of the adjusted network function/sub-network slice instance fault on the network slice instance in the alarm information.
  • the parameters of the alarm information include one or more of the following: a parameter of a fault severity, a parameter of a fault trend, a parameter of a fault threshold, a monitored attribute parameter, and an offer. Repair action parameters.
  • a network system comprising the network management system of the third aspect and the network element management system of the fourth aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • FIG. 1A is a schematic diagram of a network management architecture in accordance with an embodiment of the present invention.
  • FIG. 1B is a schematic diagram of another network management architecture in accordance with an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of an example of a network slice, in accordance with an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of another example of a network slice, in accordance with an embodiment of the present invention.
  • FIG. 4 is a hierarchical structure diagram of an NSM&O according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of interaction of a network management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of interaction 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.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • Embodiments of the present invention relate to network slicing techniques.
  • the network slicing technology logically abstracts the network into one or more network slices, where each network slice contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
  • network slicing is an on-demand networking, which enables operators to adjust according to changing user requirements and quickly New services that meet the needs of new applications.
  • the network slicing technology abstracts the network physical infrastructure resources into a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model.
  • a network slice instance can be thought of as an instantiated network.
  • Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.
  • Network slice refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including a terminal, an access network, a transmission network, a core network, and an application server, and can provide telecommunication services and have certain network capabilities; the network slice can also be the above terminal and access network. Any combination of the transport network, the core network, and the application server, for example, the network slice only includes the access network and the core network.
  • a network slice may have one or more of the following characteristics: the access network may or may not slice.
  • the access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.
  • Network Slice Instance A real-world logical network that meets certain network characteristics or service requirements.
  • a network slice instance may provide one or more services.
  • a network sharding instance can be created by the network management system.
  • a network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances.
  • a network tile instance may or may not be created from a network tile template.
  • a complete network sharding instance can provide complete end-to-end network services, and the network sharding instances can be sub-network slice instances and/or network functions.
  • the sub-network slicing instance may not need to provide a complete network service end-to-end.
  • the sub-network slicing instance may be a network function component set of the same device vendor in the network slicing instance, or may be a set of network functions divided by domain, for example, The core network sub-network snippet instance and the access network sub-network snippet instance.
  • a subnet slice instance may be shared by multiple network slice instances.
  • a sub-network slice instance is proposed to facilitate network management system management.
  • 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; A network slice instance may also consist of only a few network functions.
  • Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • one network tile instance may provide multiple services simultaneously. For example, operators use a network slicing instance to provide water companies with water metering services and power meter companies to provide meter reading services. If required, the management data of different services can be isolated, including performance data and fault information.
  • the network management system can 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 each service instance.
  • Network Slice Template A method of generating a network slice instance to provide a reference for generating a network slice instance.
  • the network slice template specifies how the network slice instance should be generated.
  • the network slicing module can indicate which network functions are included in the network slice, and Key Performance Indicators (KPIs) that should be reached.
  • KPIs Key Performance Indicators
  • Network function It is a processing function in the network, which defines functional behaviors and interfaces.
  • the network functions can be implemented by dedicated hardware, or by running software on dedicated hardware, or by virtualizing on a common hardware platform. The form of the function is implemented. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple network slice instances, different network functions can be used independently. This network function is called a dedicated network function. It is also possible to share the same network function, which is called a shared network function.
  • FIG. 1A shows a network management architecture 100.
  • the network management architecture 100 includes three layers, namely, a network management system (NMS), an element management system (EMS), and a network element (NE).
  • NMS network management system
  • EMS element management system
  • NE network element
  • the interface between the EMS and the NMS can be an Itf-N interface.
  • the interface may have other names as well.
  • the NMS can include one or more network managers, which mainly provide network management functions, can manage networks of different regions and different device vendors, and the network administrator can comprehensively monitor the network through the NMS.
  • NMS provides the basic functions of network management. For example: Fault, Configuration, Accounting, Performance, and Security Management.
  • the EMS may include an element manager (EM) and/or a domain manager (DM).
  • the EM is a network module for managing network elements, and may be set on the network element or separately.
  • the DM is a management system module that is one level larger than the management scope of the EM.
  • the DM can manage one or more EMs, for example, the DM can 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 equipment. For example, EM manages a series of base stations, and DM manages a network equipment belonging to the equipment vendor (English: vendor). For domain management functions, DM has a larger scope than EM.
  • EM devices are used to perform configuration of network functions. However, the possibility that the DM performs the process performed by the EM is not excluded in the embodiment of the present invention.
  • the EM can be set separately, as illustrated in Figure 1A. It may also be set on a certain NE, which is illustrated in Figure
  • the NE may be a physical network function (PNF) module and/or a virtualized network function (VNF) module.
  • the Physical Network Function (PNF) module is a physical device that provides fixed network functionality.
  • the physical network function module may be a network element (NE) in a traditional 3GPP network management architecture, that is, a physical network element.
  • the NE can be an access network device or a core network device.
  • the NE may be a base station, a Mobility Management Entity (MME), or a Serving Gateway (SGW).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the Virtualized Network Function (VNF) module can be the smallest virtual unit that can be monitored and managed in the network management architecture.
  • a network slice instance can be implemented on the NE.
  • Network slice instances are created by the NMS, and an NMS may create and manage one or more network slice instances.
  • a network slice instance may be composed of several sub-network slice instances, each sub-network slice instance consisting of several network functions; one network slice instance may also be composed of several sub-network slice instances and network functions that are not divided into sub-network slice instances; It is also possible for a network slice instance to consist of only a few network functions.
  • the radio access network may or may not be sliced. In FIG. 1A, the radio access network is not sliced, and the network slice instance 1 and the network slice instance 2 share the radio access network. In FIG. 1B, the radio access network is sliced, and network slice instance 1 and network slice instance 2 respectively include slice instances of different radio access network portions.
  • FIG. 2 is a schematic structural block diagram of an example of a network slice according to an embodiment of the present invention.
  • a network access instance 1 and a slice instance 2 share a radio access network (English: Radio Access Network, abbreviated as RAN).
  • the network slice instance 1 includes a radio access network and a core network slice instance 1 (which may also be referred to as a core network sub-network slice instance 1).
  • the network slice instance 2 includes a radio access network and a core network slice instance 2 (which may also be referred to as a core network sub-network slice instance 2). Core network slice instance 1 and core network slice instance 2 are logically completely isolated.
  • FIG. 3 is a schematic structural block diagram of a network slice instance according to another embodiment of the present invention. In FIG. 3, a core shared network slice instance 1 and a core network slice instance 2 have a partially shared control plane function, which is called sharing.
  • each network slice instance also has a dedicated core network control plane network function (English: Common Control Plane Network Function, abbreviated: slice -specificCP NF) and exclusive core-specific User Plane Network Function (slice-specific User Plane Network Function, abbreviated: slice-specific UP NF).
  • the network slice instance 1 includes a radio access network, a shared core network control plane network function, a dedicated core network control plane network function 1 and a dedicated core network user plane network function 1.
  • the network slice instance 2 includes a radio access network, a shared core network control plane network function, a dedicated core network control plane network function 2, and a dedicated core network user plane network function 2 .
  • the radio access network may also be sliced, the radio access network may include a network slice instance of the access network that is logically completely isolated, or the network slice instances of the radio access network may also be partially shared. Network function.
  • the core network may include a core network slice instance that is logically completely isolated or a core network slice instance may have a partially shared network function.
  • the core network may include a core network slice instance that is logically completely isolated or a core network slice instance may have a partially shared network function.
  • the network slice manager and orchestrator (“NSM&O") module is introduced in the NMS.
  • the NSM&O module can be set to an NM or it can be set separately.
  • the structure diagram of the NSM&O module is shown in Figure 4. Its main functions include monitoring, which is used to detect and report performance information and fault information of network slice instances.
  • the main functions of the NSM&O module also include any of the following:
  • Service conversion Receives service description information sent by the sender device through an interface, for example, an Application Programming Interface (API), and translates the service description information into a network requirement.
  • API Application Programming Interface
  • Network Slice Design Describes the composition of the network slice based on the results of the service transformation. For example, it may be a Design Network Slice Descriptor ("NSLD").
  • NSLD Design Network Slice Descriptor
  • Network Slice Management Manage the life cycle of network slices according to a well-designed strategy. For example, it may be network slice instantiation, network slice instance scaling, network slice instance update, network slice instance termination, network slice deletion, and the like.
  • Network Slice Orchestration Used to specifically determine the network functions and network resources used by the network slice instance.
  • the above-mentioned sender device is a device that sends a request to the NSM&O module.
  • the sender device may be an operator, a third party client, an application involved in the communication service, or any other physical device that may send a request to the NSM&O.
  • FIG. 5 illustrates a network management method provided by an embodiment of the present invention.
  • the method may be applied to the network architecture shown in FIG. 1A and FIG. 1B, and may also be applied to other network architectures.
  • a network architecture a network management system for managing network slice instances, and a network management system may include one or more network managers.
  • the element management system may include EM and/or DM.
  • a network slice instance includes multiple network functions and/or multiple sub-network tiles.
  • the network management method in the embodiment of the present invention does not limit the network architecture. As shown in FIG. 5, the method includes the following steps:
  • the network management system sends a request for configuring the alarm information to the network element management system, and the network element management system receives the request for configuring the alarm information.
  • the request for configuring the alarm information includes parameters of the alarm information corresponding to the network slice instance.
  • the alarm information refers to the alarm information (AlarmInformation) that needs to be generated after the EM and/or DM in the NE management system receives the fault report of the network function and/or the sub-network snippet instance managed by the MME. Enter the alarm list (AlarmList) of the EM and/or DM.
  • AlarmInformation is a collection of one or more parameters. Each parameter may have one or more elements, and the values of each element have different determination methods (for example, calculation methods).
  • the parameters of the alarm information may include one or more of the following: Persived Severity parameter, trend indication parameter, failure threshold parameter, monitored attribute parameter, and proposed repair action (proposedRepairActions) )parameter.
  • the PerceivedSeverity parameter is used to indicate the emergency of the fault.
  • the PerceivedSeverity parameter can include an element whose value can be Critical, Major, Minor, Warning, Indeterminate, and Cleared.
  • the trendIndication parameter is used to indicate that the fault condition is getting better, worse or not changing.
  • the thresholdInfo parameter is used to notify the identifier of the indicator that the EMS needs to monitor, and the threshold corresponding to the indicator. When the alarm information is reported on the EMS, the identifier of the performance indicator that crosses the threshold, the threshold set value, and the observation value that exceeds the threshold may be reported.
  • the monitoredAttributes parameter is used to indicate the monitored attributes of the change.
  • the proposed repair action parameter is used to indicate the repair action proposed by the EMS.
  • the above five parameters are only examples.
  • 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 above alarm information are all corresponding to the network slice instance. After receiving the fault report of the managed network function and/or the sub-network slice instance, the network element management system determines the alarm information of the corresponding network slice instance according to the fault report.
  • the parameter of the alarm information included in the request for configuring the alarm information in step 501 is the specific network slice.
  • the request for configuring the alarm information may further include identifier information of the specific network slice instance.
  • the identification information of the specific network slice instance may be embodied in the form of a parameter or in the form of an element. For example, when the parameter of the alarm information includes additional information (additionalText), the element of the identification information of the network slice instance may also be added.
  • the parameter of the alarm information included in the request for configuring the alarm information in step 501 is corresponding.
  • the request for configuring the alarm information may include the identifier information of the at least two network slice instances and the parameters corresponding to the alarm information of 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 parameters or in the form of elements. For example, when the parameter of the alarm information includes additional information (additionalText), the elements of the identification information of the at least two network slice instances may also be increased.
  • At least two elements may also be included to reflect the alarm information of the at least two network slice instances.
  • the PerceivedSeverity parameter it can include multiple elements, each of which can take values of Critical, Major, Minor, Warning, Indeterminate, Cleared, and the like.
  • Each element corresponds to a network slice instance, indicating the impact of the failure on the network slice instance.
  • the same failure on a network function or sub-network slice instance may have different effects on different network slice instances.
  • the parameters of the alert information may also include a method of determining the impact of the fault on different network slice instance services, such as a method of calculating the value of the element.
  • the trendIndication parameter it may also include multiple elements, and the value of each element represents that the situation of the corresponding network slice instance is getting better, worse or no change.
  • the thresholdInfo parameter it may also include multiple sets of elements, and the values of each set of elements respectively represent the identifier of the performance indicator that exceeds the threshold monitored by the corresponding network slice instance, the threshold set value, and the observed value that crosses the threshold.
  • the threshold setting value and the monitored performance index of the threshold exceeding the threshold may be different or the same.
  • the monitoredAttributes parameter it can also include multiple elements. The value of each element represents the attributes of the corresponding network slice instance that you want to monitor. The values of these elements may be the same or different.
  • the proposedRepairActions parameter can also include multiple elements that represent the desired repair strategy for different network slice instances. For example, when two network slice instances of the meter and the hazardous chemicals storage temperature sensor share the same network function or sub-network slice instance, when the network function or the sub-network slice instance fails, the former does not require immediate repair, and then You may be asked to immediately use the backup network function or backup subnet snippet instance, and then switch back after the failed network function or subnet shard instance is fixed.
  • 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 sharding instance may be in a plurality of forms, for example, the identification information is a number, or an identifier consisting of a type of the network sharding instance and a singular instance (Slice Differentiator, SD for short), which is not limited by the present invention.
  • the parameters of the alarm information of the at least two network slice instances may be the same or different.
  • the parameter of the network segment instance is included in the parameter of the alarm information, which may be implemented by adding a parameter in the alarm information, where the parameter is the identifier information of the network slice instance, or may be implemented by adding an element in the original parameter. This element is the identification information of the network slice instance. For example, if the parameter of the alarm information includes an additional information (additionalText) parameter, an element may be added, that is, the identification information of the network slice instance.
  • triggering step 501 There may be many reasons for triggering step 501, which will be described below by way of example.
  • One scenario may be that the EMS sends an alert configuration request to the network management system, and the network management system accordingly receives the alert configuration request.
  • the alarm configuration request is used to request the network management system to send a request for configuring alarm information to the network element management system. This situation may occur in situations such as EM and/or DM restarts.
  • Another situation may be the creation and initial configuration of network functions and/or sub-network tile instances.
  • the creation and initial configuration of the network function and/or sub-network slice instance may occur in the following cases: i) network slice instantiation; ii) network slice instance extension and addition of network function/sub-network slice instance; or iii) network
  • the slice instance is updated and the new network function/subnetwork slice instance replaces the original network function/subnetwork slice instance.
  • the network function and/or sub-network slice instance may be a network function and/or a sub-network slice instance shared by at least two network slice instances, or may be a network function and/or a sub-network slice instance specific to a network slice instance.
  • the EMS configures parameters of the alarm information according to the request for configuring the alarm information. Specifically, the EMS configures parameters of the alarm information corresponding to the network slice instance,
  • the EMS sends an alarm information configuration confirmation to the network management system, and the network management system receives the alarm information configuration confirmation accordingly.
  • the alarm information configuration confirmation can be used to indicate that the EMS has completed alarm information configuration.
  • the configuration of the alarm information can be completed.
  • the network element management system can generate the fault alarm information that meets the requirements, so that the network management system can analyze the impact of the fault on the service of the network slicing instance from the alarm information.
  • the network management system can know from the alarm information the impact of the failure on the dedicated network function/sub-network slice instance.
  • the network management system can distinguish the different impacts of faults on individual network slicing instances, helping operators to locate faults faster, focus on critical faults, and secure critical services.
  • the network function and/or the sub-network slice instance managed by the EMS fails, the network function and/or the sub-network slice instance reports a fault report to the EMS that manages it.
  • the fault report can 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 interruption, or a virtualization related failure.
  • the EMS After receiving the fault report, the EMS analyzes the impact 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 slicing instance, and according to the alarm information parameter in the request for configuring the alarm information. Configure the corresponding alarm information (AlarmInformation) and store it in the alarm list (AlarmList).
  • the foregoing network management method may further include the following steps:
  • the network management system sends an alarm information configuration modification notification to the network element management system, and the network element management system receives the alarm information configuration modification notification accordingly.
  • the alarm information configuration modification notification includes adjustment of the parameter of the alarm information, and the adjustment of the parameter of the alarm information is corresponding to the network slice instance.
  • the expansion, contraction, and update of the network function and/or the sub-network slice instance triggers the adjustment of the alarm information configuration of the corresponding network slice instance.
  • An extension of the network function and/or sub-network tile instance may occur when the network slice instance is extended, in particular, the extended network function and/or the sub-network slice instance includes extending its computing resources, storage resources, network resources.
  • the shrinking of network functions and/or sub-network slice instances can occur when the network slice instance shrinks, specifically, the shrink network function and/or the sub-network slice instance includes shrinking its computing resources, storage resources, network resources.
  • Updates to network functions and/or sub-network tile instances may occur when a network tile instance is updated, specifically, updating network functions and/or sub-network tile instances includes updating their software versions.
  • the network management system may send an alert message to the EMS managing the network function and/or the sub-network slice instance. Configure modification notifications.
  • the alarm information configuration modification notification includes at least one of the following: adjusting the value of the corresponding network slice instance in the PerceivedSeverity parameter; adjusting the identifier of the indicator to be monitored corresponding to the network slice instance in the thresholdInfo parameter, or the threshold corresponding to the indicator; adjusting the corresponding network slice The monitored value of the monitored attribute of the instance; adjusts the fault repairing action of the corresponding network slice instance in the proposedRepairActions; adjusts the evaluation criteria of the corresponding trend of the network slice instance in the trendIndication.
  • the present invention is not limited to only adjusting the above parameters, and it is also possible to adjust other parameters. After the network function and/or sub-network slice instance is extended, contracted, and updated, the same failure may have different impacts on its services. By configuring the modification notification by the alarm information, the impact of the failure on the network slice instance caused by the expansion, contraction, and update of the network function and/or the sub-network slice instance can be better reflected.
  • the alarm information configuration modification notification includes: adding an element to the parameter of the alarm information to indicate the newly created network slice instance. For example, add an element to the PerceivedSeverity parameter that indicates how much the fault affects the newly created network slice instance; add an element to the thresholdInfo parameter that indicates the performance of the monitored threshold for the newly created network slice instance.
  • the identifier, threshold, and value of the specific performance indicator add an element to the trendIndication parameter, which is used to indicate the impact of the fault on the newly created network slice instance; add an element in the monitoredAttributes parameter, which is used to mark the new Creating a network slice instance requires monitoring the changed parameters; an element is added to the proposedRepairActions parameter, which is used to indicate the repair method taken by the newly created network slice instance.
  • the above is only an example, and it is possible to add an element corresponding to the newly created network slice instance in one or more of the above parameters. It may also include adding elements corresponding to the newly created network slice instance to other parameters, such as adding an element in the identification information of the network slice instance, which is used to mark the newly created network slice instance. You can use the alarm information to configure the modification notification to reflect the impact of the fault on the service of the newly created network slice instance in the alarm information reported by the subsequent EMS.
  • the alarm information configuration modification notification includes: deleting an element for indicating the terminated network slice instance in the parameter of the alarm information.
  • the element is deleted in the PerceivedSeverity parameter, which indicates the degree of impact of the failure on the terminated network slice instance; the element is deleted in the thresholdInfo parameter, which indicates the performance of the monitored network slice instance that exceeds the threshold.
  • the value of the identifier, threshold, and specific performance indicator add and delete elements in the trendIndication parameter, which indicates the change of the impact of the fault on the terminated network slice instance; delete the element in the monitoredAttributes parameter, which indicates the terminated
  • the network slice instance needs to monitor the changed parameters; the deletedRepairActions parameter deletes the element, which indicates the repair method taken by the terminated network slice instance.
  • the above is only an example, and elements corresponding to the terminated network slice instance may be deleted in one or more of the above parameters.
  • the EMS configures a modification notification according to the alarm information, and modifies the configuration of the parameter of the alarm information.
  • the EMS sends an alarm information configuration modification confirmation to the network management system, and the network management system receives the alarm information configuration modification confirmation accordingly.
  • the alarm information configuration modification confirmation is used to instruct the EMS to perform configuration modification of the parameter of the network slice instance alarm information according to the alarm information configuration modification request.
  • steps 504 and 505 may also be performed again after step 508.
  • the parameters of the alarm information can be adjusted, which is beneficial for the EMS to feed back the network function and/or the sub-network slice instance according to the network function and/or the sub-network slice instance fault report. influences.
  • FIG. 6 shows another network management method provided by an embodiment of the present invention. As shown in FIG. 6, the network management method may include the following steps:
  • the network management system sends a request for obtaining an alarm quantity (getAlarmCount) 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 number of alarms corresponding to the network segment instance refers to the number of alarms corresponding to the alarm information parameter of the corresponding network slice instance.
  • the EMS sends an alarm quantity reply to the network management system.
  • the network management system receives the alarm number reply.
  • the alarm quantity reply includes the number of alarms corresponding to the network slice instance.
  • the getAlarmCount request in the step 601 may further include an alarm quantity filter condition corresponding to the network slice instance, and the function is to filter the fault alarm that has less impact on the service or the fault alarm or the associated fault alarm that the operator does not pay attention to.
  • the EMS reports only the number of alarms that meet the alarm quantity filtering condition.
  • the alarm quantity filtering condition in step 601 is the alarm quantity filtering condition of the specific network slice instance.
  • the EMS reports only the number of alarms of the specific network slice instance that meets the alarm quantity filtering condition.
  • the alarm quantity filtering condition in step 601 is the number of alarms of the at least two network snippet instances. Filter conditions.
  • the alarm number filtering conditions of the at least two network slice instances may be the same or different.
  • the EMS reports the number of alarms of at least two network slice instances that respectively meet the alarm quantity filtering conditions of the at least two network slice instances.
  • the network slice instance A and the network slice instance B share one network function or a sub-network slice instance
  • the step 601 may include the alarm number filtering condition of the network slice instance A and the alarm quantity filtering condition of the network slice instance B.
  • the EMS can initialize two counters and determine whether each AlarmInformation satisfies the filtering conditions of the network slice instance A and the network slice instance B one by one. If an AlarmInformation satisfies the condition of the network slice instance A, the condition of the network slice instance B is not satisfied. Then, the counter corresponding to the network slice instance A is incremented by one, and the counter corresponding to the network slice instance B is not added.
  • the EMS obtains the number of alarms of the network slice instance A and the network slice instance B and adds the identity of the network slice instance to the network management system.
  • the EMS does not report the number of alarms of the network segment instance when the number of alarms in the network segment is set to be filtered.
  • the getAlarmCount request includes the alarm quantity filtering condition of the corresponding network snippet instance, so that the network management system can flexibly obtain the required number of alarms of the corresponding network sharding instance according to the different impacts of the fault on each network sharding instance, and focus on the network snippet instance service generation. A large impact of the failure, but will not lose other information, which is conducive to subsequent failure repair.
  • the alarm quantity filtering condition in step 601 is an alarm of the at least two network snippet instances. Quantity filter conditions. This allows the network management system to distinguish the impact of the network function and/or the sub-network splicing instance on different network snippet instances, and obtain the alarm information of the different network snippet instances that meet the filtering parameters of the alarm parameters.
  • the network management method may further include the following steps:
  • the network management system sends a request for obtaining an alert list (getAlarmList) to the EMS. Accordingly, the EMS receives the request.
  • the getAlarmList request is used to request to obtain the alarm information in the alarm list of the corresponding network slice instance.
  • the EMS sends an alarm message to the network management system.
  • the network management system receives the alert information.
  • the alarm information may be in the form of an alarm list, and the alarm list includes alarm information corresponding to the alarm information parameter of the network slice instance.
  • the getAlarmList request in step 603 may further include an alarm information filter condition, where the filter condition is corresponding to the network slice instance, and the function is to filter the fault alarm that has little impact on the service or the operator does not pay attention to Fault alarm or associated fault alarm.
  • the alarm list reported by the EMS in step 604 includes the alarm information corresponding to the filtering condition of the alarm information corresponding to the network slice instance.
  • the alarm information filtering condition in step 603 is the alarm information filtering condition of the specific network slice instance.
  • the EMS only reports the alarm information of the specific network slice instance that meets the filtering condition of the alarm information.
  • the alarm information filtering condition in step 603 is that the alarm information filtering of the at least two network snippet instances is (filter) conditions.
  • the alarm information filtering conditions of the at least two network slice instances may be the same or different.
  • the EMS reports alarm information of at least two network slice instances that respectively meet the alarm information filtering conditions of the at least two network slice instances. The EMS will determine whether it meets the filtering conditions of the alarm information of each network slice instance for each AlarmInformation.
  • the last reported AlarmInformation only contains the corresponding identifiers of the corresponding network slice instance that meet the filtering conditions of the alarm information and the corresponding parameters.
  • Elements which can include PerceivedSeverity, trendIndication, threshold, monitoredAttributes,posedRepairActions or other parameters.
  • a shared network function of the network splicing instance A and the network splicing instance B has a different impact on the service of the network splicing instance A and the network splicing instance B.
  • the generated alarm information meets the alarm information filtering of the network splicing instance A. If the condition does not satisfy the alarm information filtering condition of the network slice instance B, the reported alarm information only includes the identifier of the network slice instance A and the corresponding element in the parameter.
  • the getAlarmList request includes the alarm information filtering condition of the corresponding network snippet instance, so that the network management system can flexibly obtain the required alarm information of the corresponding network sharding instance according to the different impacts of the fault on each network sharding instance, and focus on the network snippet instance service generation. A large impact of the failure, but will not lose other information, which is conducive to subsequent failure repair.
  • the alarm information filtering condition in step 603 is an alarm of the at least two network slice instances. Information filtering conditions. This allows the network management system to distinguish the impact of the network function and/or the sub-network splicing instance on the different network snippet instances, and obtain the alarm information of the different network snippet instances that meet the filtering conditions of the alarm information.
  • Steps 603 and 604 can take the synchronization mode, that is, the EMS receives the getAlarmList request and immediately reports the alarm list of the corresponding network slice instance according to the AlarmList stored in the current EMS.
  • Steps 603 and 604 may also adopt an asynchronous mode, that is, after receiving the getAlarmList request, the EMS does not report the alarm list of the corresponding network slice instance according to the AlarmList stored in the current EMS, but waits for the network function and/or the sub-network managed by the EMS. After the alarm report is sent, the alarm list is updated, and the alarm list of the corresponding network segment instance is reported.
  • the network management method may further include the following steps between steps 603 and 604:
  • the network function and/or the sub-network slice instance managed by the EMS fails, the network function and/or the sub-network slice instance reports the fault report to the EMS that manages it.
  • the EMS After receiving the fault report, the EMS analyzes the impact 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 slicing instance, and according to the alarm information parameter in the request for configuring the alarm information. Configure the corresponding alarm information (AlarmInformation) and store it in the alarm list (AlarmList).
  • the management method shown in Figure 5 can be extended to manage different service instances on a network sharding instance to implement the configuration of alarm information and configuration modification of alarm information for the service instance of the network snippet instance.
  • the adjustment of the parameter of the alarm information in step 506 is a service instance corresponding to the network slice instance.
  • the network management system is triggered to send an alarm information configuration modification notification to the corresponding EMS.
  • the alarm information configuration modification notification includes: adding an element for indicating the newly created service instance to the parameter of the alarm information. For example, an element is added to the PerceivedSeverity parameter that indicates the extent to which the failure affects the newly created service instance; an element is added to the thresholdInfo parameter that indicates the identity of the performance metric that exceeds the threshold for monitoring of the newly created service instance.
  • threshold value of the specific performance indicator
  • add an element in the trendIndication parameter which is used to indicate the impact of the failure on the newly created service instance
  • add an element in the monitoredAttributes parameter which is used to indicate the newly created service
  • the instance needs to monitor the changed parameters
  • the raisedRepairActions parameter adds an element that identifies the repair method taken by the newly created service instance.
  • the above is only an example. It is possible to add an element corresponding to the newly created service instance in one or more of the above parameters, and may also include adding an element corresponding to the newly created service instance among other parameters. You can use the alarm information to configure the modification notification to reflect the impact of the fault on the service of the newly created service instance in the alarm information reported by the subsequent EMS.
  • the network management system is triggered to send an alarm information configuration modification notification to the corresponding EMS.
  • the alarm information configuration modification notification includes at least one of the following: adjusting the impact condition of the impact of the fault on the service instance in the PerseivedSeverity; adjusting the identifier of the indicator to be monitored by the corresponding service instance in the thresholdInfo parameter, or the threshold corresponding to the indicator; adjusting the monitored attribute to the service instance The value of the monitoring; adjust the fault repair action for the service instance in the proposedRepairActions; adjust the evaluation criteria of the fault trend of the service instance in the trendIndication.
  • the invention is not limited to only adjusting the parameters, and it is also possible to adjust other parameters.
  • 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.
  • the alarm information configuration modification notification includes: deleting an element for indicating the terminated service instance in the parameter of the alarm information.
  • the element is deleted in the PerceivedSeverity parameter, which indicates the degree of impact of the failure on the service instance being terminated; the element is deleted in the thresholdInfo parameter, which indicates the performance index of the threshold exceeding the threshold for the monitored service instance.
  • the value of the identifier, threshold, and specific performance indicator delete the element in the trendIndication parameter, which indicates the change of the impact of the fault on the terminated service instance; delete the element in the monitoredAttributes parameter, which indicates the required service instance needs to be terminated. Monitor the changed parameters; remove the element in the proposedRepairActions parameter, which identifies the fix for the terminated service instance.
  • the above is only an example. It is possible to delete the element corresponding to the terminated service instance in one or more of the above parameters, and may also include deleting the element corresponding to the terminated service instance among other parameters.
  • step 505 after receiving the fault report, the EMS analyzes the impact of the fault in the fault report on the service instance running on the network slice instance using the network function and/or the sub-network slicing instance, and generates corresponding information according to the alarm information parameter configuration.
  • the alarm information is stored in the alarm list.
  • the alarm information can reflect the impact of the fault on the service instance of the changed network slice instance.
  • the network management system can distinguish the impact of the fault on different service instances from the reported alarm information.
  • the management method shown in FIG. 6 can be extended to the management of different service instances on a network sharding instance, and the number of alarms and the alarm list of the service instance corresponding to the network snippet instance can be obtained.
  • the getAlarmCount request in step 601 is the number of alarms for requesting to obtain the service instance of the corresponding network slice instance.
  • the number of service instance alarms corresponding to the network snippet instance refers to the number of alarms corresponding to the alarm information parameter of the service instance corresponding to the network sharding instance.
  • the number of alarms sent by the EMS in step 602 is the number of alarms corresponding to the service instance of the network slice instance.
  • the getAlarmCount request in step 601 may further include an alert quantity filter condition of the service instance corresponding to the network slice instance.
  • the EMS reports only the number of alarms that meet the alarm quantity filtering condition of the service instance of the corresponding network slice instance.
  • the getAlarmList request in step 603 is an alert list for requesting a service instance of the corresponding network slice instance.
  • the alarm list sent by the EMS to the network management system in step 604 is a service instance corresponding to the network slice instance, and the alarm list includes the alarm information of the service instance corresponding to the network slice instance.
  • the getAlarmList request in step 603 may further include an alert information filter condition corresponding to the service instance of the network slice instance.
  • the EMS reports only the alarm information of the service instance of the network slice instance that meets the filtering condition of the alarm information.
  • the management method shown in Figure 5 can be extended to different sub-network snippet instances on a network slice.
  • the sub-network snippet instance of the network snippet instance can be configured with alarm information and configuration information of the alarm information.
  • the request for configuring the alarm information in step 501 includes parameters of the alarm information of the sub-network slice instance corresponding to the network slice instance.
  • the EMS configures parameters of the alarm information corresponding to the sub-network slice instance of the network slice instance.
  • step 505 after receiving the fault report, the EMS analyzes the impact of the fault in the fault report on the sub-network slicing instance running on the network slicing instance using the network function and/or the sub-network slicing instance, and configures according to the alarm information parameter. Generate corresponding alarm information and save it in the alarm list.
  • the adjustment of the parameters of the alarm information in step 506 is a sub-network slice instance corresponding to the network slice instance.
  • the management method shown in Figure 6 can be extended to different sub-network snippet instances on a network slice, and the number of alarms and alarm lists of sub-network snippet instances corresponding to the network snippet instance can be obtained.
  • the getAlarmCount request in step 601 is the number of alarms for requesting to acquire the sub-network slice instance of the corresponding network slice instance.
  • the number of alarms of the sub-network snippet instance corresponding to the network snippet instance refers to the number of alarms corresponding to the alarm information parameter of the sub-network snippet instance of the network snippet instance.
  • the number of alarms sent by the EMS in step 602 is the number of alarms of the sub-network slice instance corresponding to the network slice instance.
  • the getAlarmCount request in step 601 may also include an alert quantity filter condition for the sub-network slice instance of the corresponding network slice instance.
  • the EMS reports only the number of alarms that match the alarm quantity filtering condition of the sub-network slice instance of the corresponding network slice instance.
  • the getAlarmList request in step 603 is an alert list for requesting a sub-network slice instance of the corresponding network slice instance.
  • the alarm list sent by the EMS to the network management system in step 604 is a sub-network snippet instance corresponding to the network sharding instance, and the alarm list includes the alarm information of the sub-network snippet instance corresponding to the network sharding instance.
  • the getAlarmList request in step 603 may further include an alert information filter condition corresponding to the sub-network slice instance of the network slice instance.
  • the EMS reports only the alarm information of the sub-network slice instance of the network slice instance that meets the filtering condition of the alarm information.
  • the network management method and network management architecture of the embodiment of the present invention are described in detail above with reference to FIG. 1A to FIG. 6.
  • the network management system and the network element management system according to the embodiment of the present invention will be described in detail below with reference to FIG. 7 to FIG.
  • FIG. 7 is a schematic block diagram of a network management system 700 in accordance with an embodiment of the present invention. It should be understood that the network management system 700 is capable of performing the various steps performed by the NMS in the methods of FIGS. 5-6, which are not described in detail herein in order to avoid redundancy.
  • the network management system 700 includes a transmitting unit 710 and a receiving unit 720 that are connected to each other.
  • the sending unit 710 is configured to send a request for configuring the alarm information to the network element management system, where the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is a corresponding network slice instance, and the network slice Examples include network functions and/or sub-network slice instances.
  • the receiving unit 720 is configured to receive the 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 the network slice instance according to the request for configuring the alarm information. Configuration of the parameters of the alarm information.
  • 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 adjustment of a parameter of the alarm information, and the adjustment of the parameter of the alarm information is a corresponding network.
  • 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 instruct the network element management system to modify the configuration according to the alarm information. The configuration modification of the parameters of the alarm information of the network slice instance is requested.
  • the sending unit 710 is further configured to send, to the network element management system, a request for acquiring an alarm quantity, where the alarm quantity request is used to request to acquire an alarm quantity of a corresponding network slice instance.
  • the receiving unit 720 is further configured to receive, by the network element management system, an alarm quantity corresponding to the network slice instance.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm quantity Is a filtering condition corresponding to the number of alarms of the at least two network slice instances.
  • the receiving unit 720 is configured to receive, by using the network element management system, the number of alarms corresponding to the network slice instance and the filtering condition that meets the number of alarms of the network slice instance.
  • the sending unit 710 is configured to send, to the network element management system, an acquiring alarm list request, where the alarm list request is used to request to acquire alarm information in an alarm list of a corresponding network slice instance.
  • the receiving unit 720 is configured to receive alarm information that is sent by the network element management system and meets the alarm information parameter.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm information Is a filtering condition corresponding to the alarm information of the at least two network slice instances.
  • the receiving unit 720 is configured to receive, by the network element management system, alarm information corresponding to the network slice instance and the alarm information filtering condition that meets the network slice instance.
  • FIG. 8 is a schematic block diagram of a network element management system 800 according to an embodiment of the present invention. It should be understood that the network element management system 800 is capable of performing the various steps performed by the EMS in the methods of FIGS. 5-6, which are not described in detail herein in order to avoid redundancy.
  • the network element management system 800 includes: a transmitting unit 810 and a receiving unit 820 that are connected to each other.
  • the receiving unit 820 is configured to receive a request for configuring the alarm information sent by the network management system, where the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is a corresponding network slice instance, and the network slice Examples include network functions and/or sub-network slice instances.
  • the sending unit 810 is configured to send the alarm information configuration completion information to the network management system, where the alarm information configuration completion information is used to instruct the network element management system to perform the network slice instance alarm information according to the request for configuring the alarm information. The configuration of the parameters.
  • 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 adjustment of a parameter of the alarm information, and the adjustment of the parameter of the alarm information is a corresponding network. Slice the 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 instruct the network element management system to perform a network segmentation instance according to the alarm information configuration modification request. The configuration of the parameters of the alarm information is modified.
  • the receiving unit 820 is further configured to receive a request for acquiring an alarm quantity sent by the network management system, where the alarm quantity request is used to request to acquire an alarm quantity of a corresponding network slice instance.
  • the sending unit 810 is further configured to send, to the network management system, an alarm quantity corresponding to the network slice instance.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm quantity Is a filtering condition corresponding to the number of alarms of the at least two network slice instances.
  • the sending unit 810 is further configured to send, to the network management system, an alarm quantity corresponding to the network slice instance and the filtering condition that meets the number of alarms of the network slice instance.
  • the receiving unit 820 is further configured to receive the acquiring an alarm list request sent by the network management system, where the alarm list request is used to request to obtain the alarm information in the alarm list of the corresponding network slice instance.
  • the sending unit 810 is further configured to send, to the network management system, alarm information that meets the alarm information parameter.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm information Is a filtering condition corresponding to the alarm information of the at least two network slice instances.
  • the sending unit 810 is further configured to send, to the network management system, alarm information corresponding to the network slice instance and the alarm information filtering condition that meets the network slice instance.
  • FIG. 9 is a schematic block diagram of a network management system 900 in accordance with 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 FIGS. 5-6, which are not described in detail herein in order to avoid redundancy.
  • Network management system 900 includes a transceiver 920, a memory 910, and a processor 930. Memory 910 is used to store instructions.
  • the processor 930 is coupled to the memory 910 and the transceiver 920, respectively, for executing the instructions stored by the memory 910 to perform the following steps: when the instruction is executed, to the network element through the transceiver 920
  • the management system sends a request for configuring the alarm information, where the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance.
  • the parameter of the alarm information is corresponding to the at least two network slice instances
  • the configuration alarm The request for information further includes identification information of the at least two network slice instances.
  • the processor 930 further performs, when executing the instruction, sending, by the transceiver 920, an alarm information configuration modification notification to the network element management system, where the alarm information configuration modification notification includes alarm information.
  • the adjustment of the parameter, the adjustment of the parameter of the alarm information is corresponding to the network slice instance; the transceiver 920 receives the alarm information configuration modification confirmation sent by the network element management system, and the alarm information configuration modification confirmation is used to indicate the The network element management system performs configuration modification of the parameter of the alarm information of the network segmentation instance according to the configuration information of the alarm information configuration modification request.
  • the processor 930 further performs, when executing the instruction, sending, by using the transceiver 920, a request for acquiring an alarm quantity to the network element management system, where the alarm quantity request is used to request to acquire a corresponding network.
  • the number of alarms of the slice instance is received by the transceiver 920, and the number of alarms corresponding to the network slice instance sent by the network element management system is received.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm quantity Is a filtering condition corresponding to the number of alarms of the at least two network slice instances.
  • the processor 930 further performs the following steps: receiving, by the transceiver 920, a filtering condition that is sent by the network element management system and corresponds to the network slice instance and the number of alarms that meet the network slice instance. The number of alarms.
  • the processor 930 further performs, when executing the instruction, sending, by using the transceiver 920, a request for acquiring an alarm list to the network element management system, where the alarm list request is used to request to acquire a corresponding network.
  • the alarm information in the alarm list of the slice instance is received by the transceiver 920, and the alarm information that is sent by the network element management system and meets the alarm information parameter is received.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm information Is a filtering condition corresponding to the alarm information of the at least two network slice instances.
  • the processor 930 further performs the following steps: receiving, by the transceiver 920, the filter instance corresponding to the network slice sent by the network element management system and the filtering condition of the alarm information that meets the network slice instance. Alarm information.
  • FIG. 10 is a schematic block diagram of a network element management system 1000 according to an embodiment of the present invention. It should be understood that the network element management system 1000 is capable of performing the various steps performed by the NMS in the methods of FIGS. 5-6, which are not 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 for storing instructions.
  • the processor 1030 is coupled to the memory 1010 and the transceiver 1020, respectively, for executing the instructions stored by the memory 1010 to perform the following steps: receiving network management through the transceiver 1020 when executing the instructions
  • the request for configuring the alarm information sent by the system, the request for configuring the alarm information includes a parameter of the alarm information, where the parameter of the alarm information is corresponding to a network slice instance, and the network slice instance includes a network function and/or a sub-network slice instance.
  • the configuration of the parameters of the alarm information is used to instruct the network element management system 1000 to perform a network slice instance according to the request for configuring the alarm information.
  • the processor 1030 when executing the instruction, further performing the step 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 alarm information.
  • the adjustment of the parameter, the adjustment of the parameter of the alarm information is corresponding to the network slice instance; the transceiver 1020 sends an alarm information configuration modification confirmation to the network management system, and the alarm information configuration modification confirmation is used to indicate the network
  • the meta management system 1000 performs configuration modification of the parameters of the alarm information of the network slice instance according to the configuration information of the alarm information configuration modification request.
  • the processor 1030 when executing the instruction, further performing the step of: receiving, by the transceiver 1020, a request for acquiring an alarm quantity sent by the network management system, where the alarm quantity request is used to request to acquire a corresponding network.
  • the number of alarms of the slice instance; the number of alarms corresponding to the network slice instance is sent to the network management system by the transceiver 1020.
  • the alarm quantity request includes an alarm quantity filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm quantity Is a filtering condition corresponding to the number of alarms of the at least two network slice instances.
  • the processor 1030 further performs the following steps: sending, by the transceiver 1020, an alarm corresponding to the network slice instance and the filtering condition that meets the number of alarms of the network slice instance to the network management system by using the transceiver 1020. Quantity.
  • the processor 1030 when executing the instruction, further performing the step of: receiving, by the transceiver 1020, an acquisition alarm list request sent by the network management system, where the alarm list request is used to request to acquire a corresponding network.
  • the alarm information in the alarm list of the slice instance; the alarm information corresponding to the alarm information parameter is sent to the network management system by the transceiver 1020.
  • the alarm list request includes an alarm information filtering condition, where the network function and/or the sub-network slice instance is shared between at least two network slice instances, the filtering condition of the alarm information Is a filtering condition corresponding to the alarm information of the at least two network slice instances.
  • the processor 1030 further performs the following steps: the network element management system 1000 sends an alarm corresponding to the network slice instance and the alarm information filtering condition of the network slice instance to the network management system. information.
  • the parameter of the alarm information is corresponding to the at least two network slice instances.
  • the request for configuring the alarm information further includes identification information of the at least two network slice instances.
  • the adjustment 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.
  • the adjusting of the parameter of the alarm information includes deleting an identifier of the terminated network slice instance in a parameter of the alarm information.
  • the adjustment of the parameter of the alarm information includes adjusting a value of a parameter of the alarm information.
  • the processor of the foregoing device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or performed by a combination of hardware and software units in the processor.
  • the software unit can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the 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 standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a disk or a CD.
  • ROM Read-Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé de gestion de réseau, un système de gestion de réseau et un système de gestion d'élément de réseau. Le procédé comprend les étapes suivantes : un système de gestion de réseau transmet une demande de configuration d'informations d'alarme à un système de gestion d'élément de réseau, la demande de configuration d'informations d'alarme comprenant des paramètres d'informations d'alarme, les paramètres des informations d'alarme correspondant à une instance de tranche de réseau, et l'instance de tranche de réseau comprenant une fonction de réseau et/ou une instance de tranche de sous-réseau ; et le système de gestion de réseau reçoit des informations d'achèvement de configuration d'informations d'alarme transmises par le système de gestion d'éléments de réseau, et les informations d'achèvement de configuration d'informations d'alarme étant configurées afin d'indiquer une configuration de paramètres d'informations d'alarme de l'instance de tranche de réseau mise en œuvre, selon la demande de configuration d'informations d'alarme, par le système de gestion d'élément de réseau. La présente invention peut compléter la configuration d'informations d'alarme de façon à gérer un système de réseau comprenant une instance de tranche de réseau, en particulier pour une gestion de défaillance du système de réseau.
PCT/CN2017/118145 2016-12-28 2017-12-23 Procédé de gestion de réseau, système de gestion de réseau et système de gestion d'élément de réseau WO2018121453A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611236522.7 2016-12-28
CN201611236522.7A CN108259193B (zh) 2016-12-28 2016-12-28 一种网络管理方法、网络管理系统和网元管理系统

Publications (1)

Publication Number Publication Date
WO2018121453A1 true WO2018121453A1 (fr) 2018-07-05

Family

ID=62710170

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/118145 WO2018121453A1 (fr) 2016-12-28 2017-12-23 Procédé de gestion de réseau, système de gestion de réseau et système de gestion d'élément de réseau

Country Status (2)

Country Link
CN (1) CN108259193B (fr)
WO (1) WO2018121453A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110022233A (zh) * 2019-04-11 2019-07-16 四川长虹电器股份有限公司 一种基于hfc分布式网管系统的告警管理方法
CN110602717A (zh) * 2019-09-18 2019-12-20 四川长虹电器股份有限公司 一种5g网络切片的容灾处理方法
CN113765683A (zh) * 2020-06-03 2021-12-07 中国移动通信集团浙江有限公司 网络切片的割接告警屏蔽方法及装置
CN113992504A (zh) * 2021-11-03 2022-01-28 中交信通网络科技有限公司 一种基于工业互联网标识解析的网络传输设备管理方法
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109240876B (zh) * 2018-07-18 2022-05-27 平安科技（深圳）有限公司 实例监控方法、计算机可读存储介质和终端设备
CN111130825B (zh) * 2018-10-31 2022-09-23 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
CN111447077B (zh) * 2019-01-17 2023-05-09 中国移动通信有限公司研究院 一种网元配置方法、装置和存储介质
CN109768895A (zh) * 2019-03-29 2019-05-17 南京邮电大学 一种网络切片故障管理方法及系统
CN111092752B (zh) * 2019-11-27 2021-03-16 中盈优创资讯科技有限公司 跨多个网络切片的故障定位方法及装置
CN113810212B (zh) * 2020-06-15 2023-04-18 中国移动通信集团浙江有限公司 5g切片用户投诉的根因定位方法及装置
CN113727381B (zh) * 2021-08-31 2023-06-27 中国联合网络通信集团有限公司 网络容灾方法、装置、系统及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621818A (zh) * 2008-07-05 2010-01-06 中兴通讯股份有限公司 一种处理错误告警的处理方法和装置
WO2016192643A1 (fr) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de trafic réseau avec un opérateur réseau

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10111163B2 (en) * 2015-06-01 2018-10-23 Huawei Technologies Co., Ltd. System and method for virtualized functions in control and data planes
CN106210042B (zh) * 2016-07-11 2019-06-18 清华大学 一种基于端到端网络切片的用户服务请求选择方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621818A (zh) * 2008-07-05 2010-01-06 中兴通讯股份有限公司 一种处理错误告警的处理方法和装置
WO2016192643A1 (fr) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de trafic réseau avec un opérateur réseau

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110022233A (zh) * 2019-04-11 2019-07-16 四川长虹电器股份有限公司 一种基于hfc分布式网管系统的告警管理方法
CN110602717A (zh) * 2019-09-18 2019-12-20 四川长虹电器股份有限公司 一种5g网络切片的容灾处理方法
CN110602717B (zh) * 2019-09-18 2021-12-31 四川长虹电器股份有限公司 一种5g网络切片的容灾处理方法
CN113765683A (zh) * 2020-06-03 2021-12-07 中国移动通信集团浙江有限公司 网络切片的割接告警屏蔽方法及装置
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN113992504A (zh) * 2021-11-03 2022-01-28 中交信通网络科技有限公司 一种基于工业互联网标识解析的网络传输设备管理方法
CN113992504B (zh) * 2021-11-03 2024-03-26 中交信通网络科技有限公司 一种基于工业互联网标识解析的网络传输设备管理方法

Also Published As

Publication number Publication date
CN108259193A (zh) 2018-07-06
CN108259193B (zh) 2021-06-01

Similar Documents

Publication Publication Date Title
WO2018121453A1 (fr) Procédé de gestion de réseau, système de gestion de réseau et système de gestion d'élément de réseau
US11140037B2 (en) Communication method, network device, and system
US11038972B2 (en) Service providing method, apparatus, and system
EP3557818A1 (fr) Procédé, dispositif et système de gestion d'instance de tranche de réseau
US11070989B2 (en) Network slice management method, management unit, and system
US20190149998A1 (en) Method and apparatus for managing network slice
WO2018171459A1 (fr) Procédé et dispositif de gestion de tranche de réseau
CN110463141B (zh) 通信方法、装置和系统
WO2019056960A1 (fr) Procédé et dispositif d'abonnement à des informations
US10848366B2 (en) Network function management method, management unit, and system
US20190260636A1 (en) Method and apparatus for managing network slice instance
US20220166664A1 (en) Method and Apparatus for Obtaining Management Data
WO2019056954A1 (fr) Procédé et dispositif de gestion de tranche de réseau
CN108632848B (zh) 网络切片自优化协调方法及装置
WO2018090993A1 (fr) Procédé et dispositif de gestion de modèle de tranche de réseau
WO2019141089A1 (fr) Procédé, dispositif, système et terminal d'alarme de réseau
US9622096B2 (en) Method and device for subscribing to radio link failure report
WO2018000389A1 (fr) Procédé et dispositif de gestion de tranche de réseau
EP3806392A1 (fr) Procédé de gestion de défauts et dispositif associé
US10284467B2 (en) Method and apparatus for controlling packet transmission and network functions virtualization system
WO2018127068A1 (fr) Procédé et appareil de gestion de réseau
JP6452834B2 (ja) 情報送信方法、管理対象システム、および管理システム
CN109417558B (zh) 管理网络切片的方法、设备和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17886207

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17886207

Country of ref document: EP

Kind code of ref document: A1