CN108632065B

CN108632065B - Method, network device and system for managing network slice instances

Info

Publication number: CN108632065B
Application number: CN201710167783.6A
Authority: CN
Inventors: 陆伟; 杨水根; 孙文琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-03-20
Filing date: 2017-03-20
Publication date: 2020-09-11
Anticipated expiration: 2037-03-20
Also published as: WO2018171430A1; CN108632065A

Abstract

The application provides a method, network equipment and a system for managing a network slice example, which can improve the efficiency of managing the network slice example and comprise the following steps: the first network equipment determines that the first network slice subnet instance has a fault; the first network device sends first indication information to the second network device, wherein the first indication information is used for indicating the second network device to activate a second network slice subnet instance, and the second network slice subnet instance is used for replacing the first network slice subnet instance.

Description

Method, network device and system for managing network slice instances

Technical Field

The present application relates to the field of communications, and more particularly, to a method, network device and system for managing network slice instances.

Background

With the rapid development of mobile communication, future mobile communication systems are required to meet diversified service demands, such as enhanced mobile broadband, large-scale machine-type communication, ultra-high-reliability and low-delay communication, and the like. The concept of network slicing is therefore proposed in the next generation mobile communication system. Network slicing technology refers to logically abstracting a network into one or more network slices, wherein each network slice comprises a series of logical network functions, and one network slice can meet the requirements of a certain type or one use case of a connection communication service. The next generation mobile communication system may be composed of a large number of network slices satisfying different connection capabilities.

In a communication network, when a network element fails, a self-checking circuit of the failed network element can find the failure, or a performance and threshold measurement task can find the failure. However, the self-healing system can only perform self-healing management on the fault of a single network function, and cannot meet the requirement of flexible fault management at the network slice level.

Disclosure of Invention

The application provides a method, a device and a system for managing a network slice example, which can improve the efficiency of managing the network slice example.

In a first aspect, a method for managing network slice instances is provided, including: the first network equipment determines that the first network slice subnet instance has a fault; the first network device sends first indication information to a second network device, wherein the first indication information is used for indicating the second network device to activate a second network slice subnet instance, and the second network slice subnet instance is used for replacing the first network slice subnet instance.

In the embodiment of the present application, when determining that the first network slice subnet instance has a fault, the first network device may instruct the second network device to activate the second network slice subnet instance to replace the first network slice subnet instance, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: and the first network equipment sends second indication information to third network equipment, wherein the second indication information is used for indicating the third network equipment to log out the first network slice subnet instance.

In the embodiment of the present application, the first network device sends the second indication information to the third network device to indicate the third network device to logout the failed first network slice subnet instance, so that the second network slice subnet instance replaces the first network slice subnet instance, thereby flexibly managing the network slice instances and improving the efficiency of managing the network slice instances.

In one possible implementation manner, the method further includes: the first network device sends third indication information to a fourth network device, where the third indication information is used to indicate the fourth network device to reconfigure a third network slice subnet instance associated with the first network slice subnet instance, and the reconfigured third network slice subnet instance is associated with the second network slice subnet instance.

In the embodiment of the present application, the first network device instructs the fourth network device to reconfigure the third network slice subnet instance associated with the first network slice subnet instance, so that the first network slice subnet instance and the third network slice subnet instance cooperate to provide services, thereby flexibly managing the network slice instances and improving the efficiency of managing the network slice instances.

In a possible implementation manner, before the sending the first indication information to the second network device, the method further includes: and the first network equipment backs up the parameter information of the first network slice subnet instance to a storage device.

In the embodiment of the application, the first network device backs up the parameter information of the first network slice subnet instance to the storage device, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: and under the condition that the performance of the second network slice subnet instance does not meet the preset condition, the first network device sends fourth indication information to a third network device, wherein the fourth indication information is used for indicating the third network device to restore the first network slice subnet instance based on the parameter information backed up to the storage device by the first network slice subnet instance.

In the embodiment of the application, the first network device instructs the third network device to restore the first network slice subnet instance based on the parameter information backed up to the storage device by the first network slice subnet instance, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: the first network equipment acquires performance information of the second network slice subnet instance, wherein the performance information is used for indicating the performance of the second network slice subnet instance; the first network device determines whether the performance of the second network slice subnet instance meets a predetermined condition based on the performance information.

In one possible implementation manner, the method further includes: the first network device receives fault alarm information from the second network device, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault; the first network device determining that a first network slice subnet instance fails, comprising: and the first network equipment determines the first network slice subnet instance according to the fault alarm information.

In the embodiment of the application, the first network device receives the fault alarm information from the second network device, and determines that the first network slice subnet instance has a fault according to the fault alarm information, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: the first network device records process information for replacing the first network slice subnet instance with the second network slice subnet instance to a storage device.

In the embodiment of the application, the first network device records the process information of replacing the first network slice subnet instance with the second network slice subnet instance to the storage device, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: the second network slice subnet instance is a redundant network slice subnet instance managed by the second network device.

In one possible implementation manner, the method further includes: the second network slice subnet instance is a newly established network slice subnet instance of the second network device.

In a second aspect, a method for managing network slice instances is provided, including: the second network equipment receives first indication information from the first network equipment, wherein the first indication information is used for indicating the second network equipment to activate a second network slice subnet instance, and the second network slice subnet instance is used for replacing the first network slice subnet instance; and the second network equipment activates the second network slice subnet instance according to the first indication information.

In the embodiment of the application, the second network device receives the first indication information from the first network device, and according to the first indication information, the second network device activates the second network slice subnet instance to replace the first network slice subnet instance, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: and the second network equipment sends fault alarm information to the first network equipment, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault.

In the embodiment of the application, the second network device sends fault alarm information to the first network device to indicate that the first network slice subnet instance has a fault to the first network device, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In a third aspect, a method for managing network slice instances is provided, including: the first network equipment determines that the first network slice subnet instance has a fault; the first network device sends first indication information to a second network device, wherein the first indication information is used for indicating the second network device to execute rollback processing on the first network slice subnet instance.

In the embodiment of the present application, when the first network device determines that the first network sliced subnet instance has a fault, the second network device may be instructed to execute the fallback processing on the first network sliced subnet instance, so that the network sliced subnet instance can be flexibly managed, and the efficiency of managing the network sliced instance is improved.

In one possible implementation manner, the method further includes: the first network equipment acquires historical parameter information of the first network slice subnet instance; the first network device determines the first indication information based on historical parameter information for the first network slice subnet instance.

In the embodiment of the application, a first network device acquires historical parameter information of a first network slice subnet instance; and determining the first indication information based on the historical parameter information. Therefore, the network slice example can be flexibly managed, and the efficiency of managing the network slice example is improved.

In one possible implementation manner, the method further includes: the first network equipment acquires historical parameter information of the first network slice subnet instance from the second network equipment; the first network equipment backs up the historical parameter information of the first network slice subnet instance to a storage device; the first network device obtaining historical parameter information of the first network slice subnet instance includes: the first network device obtains historical parameter information of the first network slice subnet instance from the storage device.

In the embodiment of the application, the first network device backs up the historical parameter information to the storage device, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In a possible implementation manner, before the first network device sends the first indication information to the second network device, the method further includes: the first network equipment acquires current parameter information of the first network slice subnet instance; and the first network equipment backs up the current parameter information of the first network slice subnet instance to a storage device.

In the embodiment of the application, the first network device backs up the current parameter information of the first network slice instance to the storage device, so that the first network slice subnet instance is restored, the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: and under the condition that the performance of the first network slice subnet instance after executing the rollback processing does not meet a preset condition, the first network device sends second indication information to the second network device, wherein the second indication information is used for indicating the second network device to restore the first network slice subnet instance based on the current parameter information of the first network slice subnet instance backed up to the storage device.

In the embodiment of the application, the first network device acquires the current parameter information of the first network slice instance from the storage device, and restores the first network slice subnet instance according to the current parameter information, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: the first network equipment acquires the performance information of the first network slice subnet instance after executing rollback processing, wherein the performance information is used for indicating the performance of the first network slice subnet instance; the first network device determines whether performance of the first network slice subnet instance meets a predetermined condition based on the performance information.

In the embodiment of the application, the first network device obtains the performance information of the first network slice instance after rollback processing, and determines whether the performance of the first network slice subnet instance meets the predetermined condition based on the performance information, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In one possible implementation manner, the method further includes: and the first network equipment records the process information of executing the rollback processing on the first network slice subnet instance to a storage device.

In the embodiment of the application, the first network device records the process information of executing the rollback processing on the first network slice subnet instance to the storage device, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.

In a fourth aspect, a method of managing network slice instances is provided, comprising: the method comprises the steps that a second network device receives first indication information from a first network device, wherein the first indication information is used for indicating the second network device to execute rollback processing on a failed first network slice subnet instance; and the second network equipment executes rollback processing on the first network slice subnet instance according to the first indication information.

In the embodiment of the present application, the second network device receives, from the first network device, first indication information, where the first indication information is used to indicate that the first network device executes fallback processing on the first network slice subnet instance, and the second network device executes fallback processing on the first network slice subnet instance based on the first indication information, so that the network slice instance can be flexibly managed, and efficiency of managing the network slice instance is improved.

In one possible implementation, before the second network device receives the first indication information from the first network device, the method further includes: and the second network equipment sends the current parameter information of the first network slice instance to the first network equipment, so that the first network equipment can conveniently backup the current parameter information of the first network slice subnet instance to a storage device.

In the embodiment of the application, the second network device sends the current parameter information of the first network slice subnet instance to the first network device, so that the first network device can back up the current parameter information of the first network slice subnet instance to the storage device, thereby flexibly managing the network slice instance and improving the efficiency of managing the network slice instance.

In one possible implementation manner, the method further includes: and under the condition that the performance of the first network slice subnet instance after executing the rollback processing does not meet a preset condition, the second network device receives second indication information from the first network device, wherein the second indication information is used for indicating the second network device to restore the first network slice subnet instance based on the current parameter information of the first network slice subnet instance backed up in the storage device.

In this embodiment of the present application, the second network device restores the first network slice subnet instance based on the first indication information sent by the first network device. Therefore, the network slice example can be flexibly managed, and the efficiency of managing the network slice example is improved.

In this embodiment of the present application, the second network device sends failure alarm information to the first network device to indicate that the first network slice subnet instance has a failure. Therefore, the network slice example can be flexibly managed, and the efficiency of managing the network slice example is improved.

In one possible implementation manner, the method further includes: the second network device sends the historical parameter information of the first network slice subnet instance to the first network device, so that the first network device can backup the historical parameter information of the first network slice subnet instance to a storage device.

In the embodiment of the application, the second network device sends the historical parameter information of the first network slice subnet instance to the first network device, so that the first network device can backup the historical parameter information of the first network slice subnet instance to the storage device, thereby flexibly managing the network slice instance and improving the efficiency of managing the network slice instance.

In a fifth aspect, a network device is provided for performing the method of the first aspect or any possible implementation manner of the first aspect. In particular, the network device comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

A sixth aspect provides another network device for performing the method of the second aspect or any possible implementation manner of the second aspect. In particular, the network device comprises means for performing the method of the second aspect described above or any possible implementation of the second aspect.

A seventh aspect provides another network device, configured to perform the method of the third aspect or any possible implementation manner of the third aspect. In particular, the network device comprises means for performing the method of the third aspect or any possible implementation manner of the third aspect.

In an eighth aspect, there is provided another network device for performing the method of the fourth aspect or any possible implementation manner of the fourth aspect. In particular, the network device comprises means for performing the method of the fourth aspect described above or any possible implementation manner of the fourth aspect.

A ninth aspect provides a network system, which includes the network device of the fifth aspect, the sixth aspect, or the network device of the seventh aspect and the eighth aspect.

In a tenth aspect, there is provided a network device, comprising: communication interface, memory, processor and bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is configured to store instructions, and the processor is configured to execute the instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method of the first aspect or any possible implementation manner of the first aspect.

In an eleventh aspect, a network device is provided, which includes: communication interface, memory, processor and bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is used for storing instructions, the processor is used for executing the instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method of the second aspect or any possible implementation manner of the second aspect.

In a twelfth aspect, a network device is provided, which includes: communication interface, memory, processor and bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is used for storing instructions, the processor is used for executing the instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method of the third aspect or any possible implementation manner of the third aspect.

In a thirteenth aspect, a network device is provided, which includes: communication interface, memory, processor and bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is used for storing instructions, the processor is used for executing the instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method in any possible implementation manner of the fourth aspect or the fourth aspect.

In a fourteenth aspect, there is provided a network system including the network device of the tenth aspect, the eleventh aspect, or the twelfth aspect and the thirteenth aspect.

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

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

A seventeenth aspect provides a computer-readable medium storing a computer program comprising instructions for performing the method of the third aspect or any possible implementation of the third aspect.

In an eighteenth aspect, there is provided a computer readable medium for storing a computer program comprising instructions for performing the method of the fourth aspect or any possible implementation manner of the fourth aspect.

A nineteenth aspect provides a network system comprising the computer-readable medium of the fifteenth aspect, the sixteenth aspect, or the seventeenth and eighteenth aspects.

Drawings

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

Fig. 2 is a schematic diagram of a network management architecture according to another embodiment of the present application.

Fig. 3 is a schematic diagram of a network management architecture according to another embodiment of the present application.

Fig. 4 is a schematic diagram of a network management architecture according to another embodiment of the present application.

Fig. 5 is a schematic diagram of a method for managing a network slice example according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a method of managing network slice instances according to yet another embodiment of the present application.

Fig. 7 is a schematic diagram of a method of managing network slice instances according to yet another embodiment of the present application.

Fig. 8 is a schematic diagram of a method of managing network slice instances according to yet another embodiment of the present application.

Fig. 9 is a schematic diagram of a method of managing network slice instances according to yet another embodiment of the present application.

Fig. 10 is a schematic diagram of a network device according to an embodiment of the present application.

Fig. 11 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 12 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 13 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 14 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 15 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 16 is a schematic diagram of a network device according to yet another embodiment of the present application.

Fig. 17 is a schematic diagram of a network device according to yet another embodiment of the present application.

Detailed Description

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

Before introducing the method, apparatus, and system for managing network slice instances of the present application, some terms and network slice management systems appearing herein are described to facilitate understanding of the contents of the present application.

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

Network Slice Instance (NSI): the network is a real running logic network and can meet certain network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network management system, and one network management system can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like in the operation process of the network slice instances. When multiple network slice instances coexist, portions of the network resources and network functions may be shared between the network slice instances. The network slice instance may or may not be created from a network slice template. A complete network slice instance is capable of providing a complete end-to-end network service, and what constitutes the network slice instance may be a Network Slice Subnet Instance (NSSI) and/or a network function. The network functions may include physical network functions and/or virtual network functions. Hereinafter, a physical network function and/or a virtual network function are collectively referred to as a network function.

Network Slice Subnet Instance (NSSI): the network slice subnet instance may not need to provide complete network service end to end, and the network slice subnet instance may be a set of network functions of the same equipment provider in the network slice instance, or may be a set of network functions divided by domains, such as a core network slice subnet instance, an access network slice subnet instance, or a set composed by other manners. A network slice subnet instance may be shared by multiple network slice instances. The network slicing subnet example is provided, and the management of a network management system can be facilitated. A network slice instance may be composed of a number of network slice subnet instances, each network slice subnet instance composed of a number of network functions and/or a number of network slice subnet instances; a network slice instance may consist of several network slice subnet instances and network functions that are not divided into network slice subnet instances; it is also possible that one network slice instance consists of only a few network functions.

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

Service management function (SvMF): the method is used for converting telecommunication service requirements of an operator and/or a third party customer into requirements for network slices, sending the requirements for the network slices to the NSMF, receiving subscription requirements of the operator and/or the third party customer for network slice management data (such as performance data, fault repair data and the like), acquiring the management data of the network slices from the NSMF and the like.

Network Slice Management Function (NSMF): the network slicing management method is used for receiving network slicing requirements sent by the SvMF, managing life cycle, performance, faults and the like of network slicing examples (management of life cycle, performance and fault management is abbreviated as management in the following), arranging the composition of the network slicing examples, decomposing the requirements of the network slicing examples into the requirements of each network slicing sub-network example, sending network slicing sub-network example management requests to each NSSMF, and sending network function management requests to the NFM.

Network Slice Subnet Management Function (NSSMF): and receiving the requirement of the network slice subnet instance from the NSMF, thereby managing the life cycle, performance, fault and the like of the network slice subnet instance (hereinafter, the life cycle, performance and fault management is simply referred to as management), and arranging the composition of the network slice instance.

Network function management module (NFM): for managing NFs, e.g., managing the life cycle of an NF, allocating network resources to an NF, etc.

Network Slice Self-Healing monitoring and management Function (NS-SH-MMF): it comprises at least one of the following functions: sending a network slice self-healing algorithm and parameters to the NS-SH-IF; configuring information and parameters related to self-healing of the network slice subnet by the NSS-SH-MMF; monitoring the operation condition and the fault condition of the network slice example; judging whether the fault of the network slice example meets a self-healing triggering condition; sending a network slice self-healing triggering request to the NS-SH-IF; receiving a self-healing processing result of the network slice sent by the NS-SH-IF; and reporting the network slice fault data and the self-healing treatment result to the SvMF.

Network Slice Self-Healing implementation function (NS-SH-IF:): it comprises at least one of the following functions: receiving network slice self-healing algorithm configuration and parameters from the NS-SH-MMF; receiving a network slice self-healing triggering request sent by the NS-SH-MMF; collecting network slice operation information including but not limited to network slice instance performance data, fault alarms, configuration data, test data, etc.; judging the fault type and deciding the self-repairing action of the fault; executing fault self-repairing actions, including but not limited to switching fault subslice instances/network functions into redundant subslice instances/network functions, creating new subslice instances/network functions to replace fault subslice instances/network functions, and returning network slicer instances causing faults to be configured and modified; backing up the configuration in the existing network slice example; executing a specific fault automatic recovery action; evaluating the automatic recovery effect of the fault; judging whether the fault recovery process needs to be stopped or not; an act of restoring the fault auto-recovery execution; the NS repeatability records the action taken by the fault recovery and the fault recovery result; and reporting the fault recovery result to the NS-SH-MMF.

Network Slice Subnet Self-healing monitoring and Management Function (NSS-SH-MMF): it comprises at least one of the following functions: sending a network slice subnet self-healing algorithm and parameters to the NSS-SH-IF; monitoring the operation condition and the fault condition of the network slice subnet example; judging whether the fault of the network slice subnet example meets a self-healing triggering condition or not; sending a self-healing triggering request of the network slice subnet to the NSS-SH-IF; receiving a self-healing treatment result of the network slice subnet sent by NSS-SH-IF; and reporting the network slice subnet fault data and the self-healing treatment result to the NS-SH-MMF.

Network Slice Self-Healing implementation function (NSS-SH-IF): it comprises at least one of the following functions: receiving network slice subnet self-healing algorithm configuration and parameters from NSS-SH-MMF; receiving a network slice subnet self-healing triggering request sent by NSS-SH-MMF; collecting operation information of the network slice subnet, including but not limited to network slice subnet example performance data, fault alarm, configuration data, test data and the like; judging the fault type and deciding the self-repairing action of the fault; executing fault self-repairing actions, including but not limited to switching a fault subslice instance (nested network slice subnet instance)/network function into a redundant subslice instance/network function, creating a new subslice instance/network function to replace the fault subslice instance (nested network slice subnet instance)/network function, and returning the configuration and modification of the network slice subnet instance causing the fault; backing up the configuration in the existing network slice subnet example; executing a specific fault automatic recovery action; evaluating the automatic recovery effect of the fault; judging whether the fault recovery process needs to be stopped or not; an act of restoring the fault auto-recovery execution; interacting with NSS hierarchy to record the action taken by fault recovery and the fault recovery result; and reporting the fault recovery result to the NSS-SH-MMF.

The Network Slice information base (NS replication) is a database in which at least one of Network Slice instance configuration information including Network Slice subnet instance configuration information, Network function configuration information, failure information, self-healing action and healing result, etc. is recorded.

Network Slice subnet information base (NSS hierarchy, Network Slice subnet hierarchy): . It is a database in which at least one of the following is recorded: the network slice subnet instance configuration information comprises nested network slice subnet instance configuration information, network function configuration information, fault information, self-repairing action and repairing result and the like. Nssrepositivity may be separate from NSSMF or may be located in the same network device as NSSMF.

Also included in the network management architecture 100 of fig. 1 is at least one of the following interfaces:

interface 1: and the interface between the SvMF and the NSMF is used for the SvMF to send the service requirement on the network slice to the NSMF, and the NSMF feeds back the NSI and the service operation condition to the SvMF and provides certain management data.

And (3) interface 2: an interface between the NSMF and the NSSMF, through which the NSMF communicates the needs for the NSSI, e.g., creates, modifies, obtains management data, etc., to the NSSMF when managing and orchestrating the NSI, through which the NSSMF feeds back information about the NSSI to the NSMF.

And interface 3: the NSMF sends a command for managing and configuring the NF; the NFM receives messages from the NSMF over the interface and feeds back information about the NF over the interface.

And interface 4: the NSSMF interface is used for mutual coordination among NSSMFs, and the NSSMF requests another NSSMF to manage the administered NSSI through the interface, wherein the NSSMF interface comprises life cycle management, performance management, fault management and the like.

And interface 5: and the interface between the NSMF and the NS repeatability is used for the NSMF to record and read data in the NS repeatability.

And interface 6: the NSSMF interface is used for NSSMF to record and read data in NSS repeatability.

And an interface 7: and the interface between the NSMF and the NSS repeatability is used for the NSMF to acquire data from the NSS repeatability.

In addition, several NSI components are also shown in fig. 1, including: the NSI consists of several NSSIs; the NSI consists of a plurality of NSSIs and a plurality of NFs; the NSI consists of several NFs.

It should be noted that NSSI allows nesting, i.e., one NSSI contains another NSSI, both with their own NSSMF; assuming that NSI includes NSSI1, NSSI1 includes NSSI 2, and NSSMF1 and NSSMF2 are managers of NSSI1 and NSSI 2, respectively, there are two options for managing NSSI 2, where option 1 is sending a management request for NSI 2 from NSSMF1 to NSSMF2, and this option is applicable in a scenario where an interface 4 exists between NSSMF1 and NSSMF 2; option 2 is a management request by NSMF to send NSSI 2 directly to NSSMF 2.

In addition, the NS hierarchy may be a separate entity independent of the NSMF, or may be a database within the NSMF. The NSS hierarchy may be a separate entity from the NSSMF or may be a database within the NSSMF. When NSS hierarchy is a single entity, it may store information for several subslice instances, and several NSSMF presence interfaces 6.

In the case that NSSI allows nesting, fig. 2 to 4 respectively show three network management architectures of the embodiment of the present application.

Fig. 2 is a schematic structural diagram of a network management architecture 200 according to an embodiment of the present application. As shown in fig. 2, NSS _ SH _ IF2 of the nested NSSI is managed by NSS _ SH _ MMF1 of the previous layer NSSI; the NSS _ SH _ MMF1 of the previous layer is managed by the NS _ SH _ MMF again.

Fig. 3 is a schematic structural diagram of a network management architecture 300 according to an embodiment of the present application. As shown in fig. 3, NSS _ SH _ IF2 of a nested NSSI may be managed directly by NSS _ SH _ MMF2, with NSS _ SH _ MMF2 receiving policies from NSS _ SH _ MMF 1.

Fig. 4 is a schematic structural diagram of a network management architecture 400 according to an embodiment of the present application. As shown in fig. 4, NSS _ SH _ IF2 of a nested NSSI is managed by its own NSS _ SH _ MMF 2; its own NSS _ SH _ MMF2 may be managed by the NS _ SH _ MMF. In addition, there may be some coordination between NSS _ SH _ MMF2 and NSS _ SH _ MMF 1.

Furthermore, it should be noted that the various functional modules and units introduced above are considered from the point of view of the functions they have. In practical applications, the above functional modules may exist separately physically, or two or more devices may be integrated into a unit, for example, the NS _ SH _ MMF module and the NS _ SH _ IF module may be combined into a functional module having all functions of the NS _ SH _ MMF module and the NS _ SH _ IF module, or the NS _ SH _ MMF module and the NS _ SH _ IF module may be separate modules, and communicate through an interface between the modules. Those skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope of the present disclosure, and such modifications or substitutions are intended to be included within the scope of the present disclosure.

The network management architecture of the embodiment of the present application is described above, and a method, an apparatus, and a system for managing a network slice example of the embodiment of the present application are described below with reference to the accompanying drawings.

Fig. 5 is a schematic flow chart diagram of a method of managing a network slice example of an embodiment of the present application. The method of fig. 5 may be applied to the network management architectures shown in fig. 1-4. The first network device in fig. 5 may include an NS _ SH _ IF module or an NSMF module that includes NS _ SH _ MMF and NS _ SH _ IF modules. The second network device, the third network device, and the fourth network device may include NSSMF modules. The third to fourth network devices may include separate NSSMF modules, or may include the same NSSMF module.

As shown in fig. 5, the method includes:

s501, the first network device determines that the first network slice subnet example has a fault.

The first network device may be a module for managing and monitoring a plurality of network slice subnet instances. For example, the first network device may be an NSMF module. For example, the first network device described above is used to manage and monitor network slice instances that include the first network slice subnet instance.

Optionally, there are multiple ways for the first network device to determine that the first network slice subnet instance fails. For example, in one approach, a first network device may receive failure alert information of a second network device indicating that a first network slice subnet instance has failed. In a second manner, the first network device may receive trigger self-healing information of the fifth network device, where the trigger self-healing information may be sent when the first network slice subnet instance satisfies a self-healing trigger condition. In the second mode, the first network device may be an NS _ SH _ IF module, and the fifth network device may be an NS _ SH _ MMF module.

S502, the first network equipment sends first indication information to second network equipment, and the second network equipment receives the first indication information. The first indication information is used to indicate the second network device to activate a second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance.

Optionally, S502 may also be understood that the first network device determines to perform a self-healing process on the first network slice subnet instance, where the self-healing process includes that the first network device sends first indication information to the second network device, where the first indication information is used to indicate the second network device to activate the second network slice subnet instance, and the second network slice subnet instance is used to replace the first network slice subnet instance.

Optionally, the activating the second network slice subnet instance may include notifying the second network device to start the second network slice subnet instance.

Optionally, the user service information of the first network slice subnet instance may also be loaded to the second network slice subnet instance to facilitate traffic restoration.

Optionally, the status of the second network slice instance in NSS hierarchy and/or NS hierarchy may also be marked as active.

The first indication information may include configuration information, which may include at least one of: application parameters of the first network slice subnet instance, location information of the first network slice subnet instance in the network topology, interface information between the first network slice subnet instance and other NSSIs, and the like.

The second network device may be a module that monitors and manages network slice subnet instances. For example, the second network device may be a NSSMF module.

Optionally, the second network slice subnet instance is a redundant network slice subnet instance managed by the second network device, or the second network slice subnet instance is a newly-built network slice subnet instance of the second network device.

Optionally, the method of fig. 5 further comprises: the first network equipment sends second indication information to third network equipment, and the third network equipment receives the second indication information. The second indication information is used for indicating the third network device to logout the first network slice subnet instance.

As an example, the second indication information may be specifically for informing the third network device to stop the service running on the first network slice subnet instance.

In the method of fig. 5, deregistering the first network slice subnet instance may further include: the state of the first network slice subnet instance in NSS repetition and/or NS repetition is marked as unregistered.

Optionally, the method of fig. 5 further comprises: the first network equipment sends third indication information to fourth network equipment, and the fourth equipment receives the third indication information. The third indication information is used to indicate the fourth network device to reconfigure a third network slice subnet instance associated with the first network slice subnet instance, where the reconfigured third network slice subnet instance is associated with the second network slice subnet instance.

The third network slice subnet instance associated with the first network slice subnet instance may refer to the third network slice subnet instance having a dependency relationship with the first network slice subnet instance.

As an example, the third indication information may include configuration information, which may include application parameter change information, location change information in the network topology or interface information between the second network slice subnet instances, etc.

Optionally, before the sending the first indication information to the second network device, the method of fig. 5 further includes: and the first network equipment backs up the parameter information of the first network slice subnet instance to a storage device.

Before logging out the first network slice subnet instance, the first network device may backup parameter information of the first network slice subnet instance to a storage device to facilitate restoring the first network slice subnet instance if necessary.

Optionally, the method of fig. 5 further comprises: and under the condition that the performance of the second network slice subnet instance does not meet the preset condition, the first network device sends fourth indication information to a third network device, and the third network device receives the fourth indication information. The fourth indication information is used to instruct the third network device to restore the first network slice subnet instance based on the parameter information backed up to the storage device by the first network slice subnet instance.

Optionally, the method of fig. 5 further comprises: the first network equipment acquires performance information of the second network slice subnet instance, wherein the performance information is used for indicating the performance of the second network slice subnet instance; the first network device determines whether the performance of the second network slice subnet instance meets a predetermined condition based on the performance information.

Alternatively, the performance information may refer to information that may reflect the performance of the second network slice subnet instance. The first network device may obtain performance information of the second network slice subnet instance from the second network device. Alternatively, the first network device may obtain, from the third network device, performance information of a third network-slice subnet instance associated with the first network-slice subnet instance, and the performance information of the third network-slice subnet instance may also reflect the performance of the second network-slice subnet instance.

As one example, the performance information may include performance measurement information, threshold monitoring information, and the like.

Optionally, the method of fig. 5 further comprises: the first network device receives fault alarm information from the second network device, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault; the first network device determining that a first network slice subnet instance fails, comprising: and the first network equipment determines the first network slice subnet instance according to the fault alarm information.

Optionally, the method of fig. 5 further comprises: the first network device records process information for replacing the first network slice subnet instance with the second network slice subnet instance to a storage device.

As an example, even if the above self-healing operation fails to successfully repair the fault, the service is restored, and the corresponding self-healing action, fault information, and self-healing result are recorded.

As a specific example, fig. 6 shows a schematic flow chart of a method for managing a network slice instance according to an embodiment of the present application. The method of fig. 6 may be used in any of the network management architectures of fig. 1-4. Fig. 6 illustrates a network slice management procedure for switching a failed NSSI to a redundant NSSI. The first network device may be an NS _ SH _ IF module or an NSMF module, which includes NS _ SH _ MMF and NS _ SH _ IF modules. The second network device may be an NSSMF2 module, the third network device may be an NSSMF1 module, and the fourth network device may be an NSSMF3 module. The third network device to the fourth network device may be separate NSSMF modules, or may be the same NSSMF module.

As shown in fig. 6, the method includes:

s601, the NS-SH-MMF configures a self-healing algorithm which needs to be executed by the NS-SH-IF. Specifically, for the self-healing mechanism for switching to the redundant NSSI, the configured content includes an identity of the NSI, a fault repair requirement of the NSI, an identity of the redundant NSSI allocated and/or created when the NSI is created, a correspondence between the redundant NSSI and the NSSI constituting the NSI, and the trigger rule for switching to the redundant NSSI includes an event, a fault type, a condition, and the like. It should be noted that there may not be a one-to-one correspondence between redundant NSSI and the NSSI that make up an NSI, for example, a redundant NSSI may be used as a redundant replacement for any one of several NSSIs, and a redundant NSSI may be used as a redundant replacement for several NSSIs of the same type in several NSIs.

S602, one NSSI forming the NSI is in failure, and the normal operation of the NSI is influenced. In the present embodiment, it is assumed that NSSI1 fails, which is managed by NSSMF 1. NSSMF1 generates a network slice subnet instance fault alarm and reports to NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm comprises at least one of the following contents: fault alarm ID, NSSI ID, time of occurrence of a fault, fault type, cause of fault, source of fault, severity of fault, impact of fault on service, available repair methods, etc.

And S603, the NS-SH-MMF judges that the self-healing triggering condition is met according to the fault alarm, and sends a self-healing triggering command to the NS-SH-IF. The NS-SH-IF receives the self-healing trigger command.

S604, NS-SH-IF collects information of related network slice instances and network slice subnet instances, wherein the collected information comprises at least one of the following contents: a) NS-SH-IF sends performance measurement task and threshold measurement task to NSSMF1 through interface 2, NS-SH-IF receives performance data and threshold measurement result reported by NSSMF1 through interface 2; b) the NS-SH-IF sends a performance measurement task and a threshold measurement task to the management function of another network slice subnet instance (in the embodiment of the present application, NSSI 3 is assumed to be NSSI 3, and is managed by NSSMF 3) interacting with NSSI1, that is, NSSMF3 receives the performance data and the threshold measurement result reported by NSSMF3 through interface 2; c) the NS-SH-IF finds the redundant NSSI corresponding to the failed NSSI according to the self-healing configuration, and reads the current state (possible states include logout, activation, terminated, unavailable, and the like) from the NS replication through the interface 5, and in the embodiment of the present application, it is assumed that the example of the redundant network slice sub-network of the NSSI1 is NSSI 2, and the NSSI 2 is managed by the NSSMF 2; d) NS-SH-IF sends test task to NSSMF2 through interface 2, NSSMF2 executes test task and reports test result to NS-SH-IF through interface 2; e) NS-SH-IF reads configuration information of NSSI1 in normal operation from NS replication through interface 5, wherein the configuration information comprises SLA, position in the logic topology of the network slice instance and interface information; f) the NS-SH-IF acquires the service information running on the NSSI1 from the NSSMF1 through the interface 2, wherein the service information comprises user data, configuration and the like; g) the NS-SH-IF reads the historical fault information of the NSSI1, the adopted repair action and the repair result from the NS repeatability through the interface 5, reads the fault information of other network slice subnet examples of the same type as the NSSI1, the adopted repair action and the repair result, and the like. Based on the collected information and the self-healing algorithm configured in step S601, NS-SH-IF decides to replace the failed NSSI1 with redundant NSSI 2.

S605, optionally, the NS-SH-IF backs up relevant configuration information, logical topology location, user service information, etc. of the NSSI1 to the NS hierarchy through the interface 5, so as to recover when the self-healing failure occurs.

S606, IF the current state of NSSI1 is activated, NS-SH-IF logs off NSSI 1. Deregistration includes marking the status of NSSI1 in NSS reproducibility and/or NS reproducibility as deregistered, informing NSSMF1 to stop the service running on NSSI 1.

S607, optionally, NS-SH-IF sends a command to NSSMF2 via interface 2 to configure NSSI 2, the configuration message including at least application parameters, location in the network topology, interface information between other NSSIs, etc. It should be noted that the configuration content may be the same as or different from the configuration when NSSI1 collected by NS-SH-IF in step S604 operates correctly. In order to ensure high reliability of the network slice instance, the redundant network slice subnet instance may be specific to a NSSI, in this case, the NSSI is configured accordingly when it is created, and when the corresponding NSSI configuration is modified, the NSMF will simultaneously notify the manager of the redundant NSSI to modify the configuration accordingly, so as to provide switching speed when a failure is sent, and ensure high reliability, in this case, step S607 may not be necessary. In addition, when the redundant NSSI can replace several NSSIs, these NSSIs may belong to the same NSI or different NSIs, in this case, the redundant NSSI will not be configured before the self-healing mechanism is triggered, and step S607 is a necessary step.

S608, NS-SH-IF sends a command to NSSMF3 via interface 2 to configure NSSI 3, associating NSSI 3 with NSSI 2, the configuration message including at least one of: application parameter changes, location changes in the network topology, and interface information between NSSI 2, etc.

S609, NS-SH-IF activates NSSI 2. Activation includes marking the status of NSSI 2 in NSS hierarchy and/or nshierarchy as active, informing NSSMF2 to start NSSI 2 and loading the user service information on NSSI1 acquired in step S604 to restore service.

S610, NS-SH-IF collects information of the network slice example and evaluates self-healing results. The collected information includes at least one of: NS-SH-IF issues performance measurement and threshold monitoring tasks for NSSI 2 and NSSMF3 respectively to NSSMF2 and NSSMF3 through interface 2, NSSMF2 and NSSMF3 execute the performance measurement and threshold monitoring tasks, and report the result of the performance measurement and/or the alarm of the threshold exceeding to NS-SH-IF through interface 2.

S611, IF any one of the steps S606 to S609 fails, or the information collected by the NS-SH-IF in step S610 indicates that the network slice service cannot operate normally after the redundant NSSI is switched, a recovery action is triggered. Specifically, the NS-SH-IF reads the network status and configuration before the self-healing action is performed, which are saved in step S605, and accordingly configures NSSI 3 and NSSI1, and activates NSSI 1.

S612, NS-SH-IF updates the running state, topology information, configuration information and the like of the network slice instance in NS replication through an interface 5, records the self-healing actions from step S606 to step S611, and records fault information and self-healing results. It should be noted that, even if the self-healing action fails to repair the fault and recover the service, the corresponding self-healing action, fault information and self-healing result need to be recorded.

S613, NS-SH-IF reports the adopted self-healing action and self-healing result to NS-SH-MMF. And the NS-SH-MMF reports the fault information, the self-healing action and the self-healing result to the SMF through the interface 1.

In the embodiment of the application, when the network slice subnet examples forming the network slice examples have faults, the redundant network slice subnet examples can be automatically switched to without manual intervention, the consistency and consistency of services can be ensured as much as possible, and the overall reliability of the network slice examples is improved. Meanwhile, the method of the embodiment of the application can also recover the modification of the network slice example when the self-healing fails, so that an operator can pay attention to the original error. In addition, the method provided by the embodiment of the application records the fault information, the self-healing action and the self-healing result, and can provide reference for the automatic operation and maintenance decision of the network slice example, so that the system can process the network fault of the same type more intelligently and quickly.

It should be noted that the method for managing network slices according to the embodiment of the present application may be applied to an application scenario in which a network slice instance is composed of a network slice subnet instance, and a self-healing mechanism at a network slice level may be adopted when a fault that the network slice subnet instance cannot self-heal is solved. The process and the method related to the embodiment of the application are also suitable for an application scene that the network slice example is composed of network functions, and when a fault that the network function cannot be self-healed occurs, a self-healing mechanism that the network function of the fault is switched to a redundant network function is adopted, the process and the steps of the self-healing mechanism that the network function is switched to the redundant network function are similar to the process steps in the embodiment of the application, and the information of the network slice subnet example is replaced by the information of the corresponding network function in the interactive information among the modules.

It should be noted that NSSI1, NSSI 2, NSSI 3, NSSMF1, NSSMF2, and NSSMF3 used in the embodiments of the present application are only for illustration, and the method of the present application does not limit the number of failed network slice subnet instances, the number of network slice subnet instances where interaction exists with the failed network slice subnet instances, and the number of redundant network slice subnet instances. For example, a failed network slice subnet instance may need to be replaced by several redundant network slice subnet instances at the same time. In addition, the failure NSSI, the redundancy NSSI, and other NSSIs with interaction may be managed by different NSSMFs, or may be managed by one NSSMF at the same time, which is not limited in this application.

As a specific example, fig. 7 shows a schematic flow chart of a method for managing a network slice instance according to an embodiment of the present application. The method of fig. 7 may be used in any of the network management architectures of fig. 1-4. Figure 7 illustrates a network slice management process that will automatically create a new NSSI to replace a failed NSSI. Wherein the first network device may include an NS _ SH _ IF module or an NSMF module including an NS _ SH _ MMF and an NS _ SH _ IF module. The second network device may include a NSSMF2 module, the third network device may include a NSSMF1 module, and the fourth network device may include a NSSMF3 module. The third network device to the fourth network device may be separate NSSMF modules, or may be the same NSSMF module.

As shown in fig. 7, the method includes:

s701, configuring a self-healing algorithm which needs to be executed by the NS-SH-IF through the NS-SH-MMF. Specifically, for the self-healing mechanism that creates a new NSSI to replace a failed NSSI, the configured content includes an identity of an NSI, a fault repair requirement of the NSI, an identity of an NSSMF that can create a new NSSI to replace a failed NSSI, and feasibility of creation, and the trigger rule for creating a new NSSI to replace a failed NSSI includes an event, a fault type, a condition, and the like. It should be noted that, as network conditions change, for example, the network resource usage changes, the NS-SH-MMF may update the configuration of the self-healing algorithm by the NS-SH-IF at any time.

S702, one NSSI forming the NSI is in failure, and normal operation of the network slice example is influenced. In the present embodiment, it is assumed that NSSI1 fails, which is managed by NSSMF 1. NSSMF1 generates a network slice subnet instance fault alarm and reports to NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm comprises at least one of the following contents: fault alarm ID, NSSI ID, time of occurrence of a fault, fault type, cause of fault, source of fault, severity of fault, impact of fault on service, available repair methods, etc.

And S703, the NS-SH-MMF judges that the self-healing triggering condition is met according to the fault alarm, and sends a self-healing triggering command to the NS-SH-IF. The NS-SH-IF receives the self-healing trigger command.

S704, NS-SH-IF collects information of related network slice instances and network slice subnet instances, wherein the collected information comprises at least one of the following contents: a) NS-SH-IF sends performance measurement task and threshold measurement task to NSSMF1 through interface 2, NS-SH-IF receives performance data and threshold measurement result reported by NSSMF1 through interface 2; b) the NS-SH-IF sends a performance measurement task and a threshold measurement task to the management function of another network slice subnet instance (in the embodiment of the present application, NSSI 3 is assumed to be NSSI 3, and is managed by NSSMF 3) interacting with NSSI1, that is, NSSMF3 receives the performance data and the threshold measurement result reported by NSSMF3 through interface 2; c) the NS-SH-IF finds a corresponding management module capable of creating a new NSSI to replace the failure NSSI according to the self-healing configuration, the management module is assumed to be NSSMF3 in the embodiment of the application, and the NS-SH-IF sends a feasibility checking request for creating the new NSSI to the NSSMF3 through an interface 2; d) NS-SH-IF reads configuration information of NSSI1 in normal operation from NS replication through interface 5, wherein the configuration information comprises SLA, position in the logic topology of the network slice instance and interface information; e) the NS-SH-IF acquires the service information running on the NSSI1 from the NSSMF1 through the interface 2, wherein the service information comprises user data, configuration and the like; f) the NS-SH-IF reads the historical fault information of the NSSI1, the adopted repair action and the repair result from the NS repeatability through the interface 5, reads the fault information of other network slice subnet examples of the same type as the NSSI1, the adopted repair action and the repair result, and the like. Based on the collected information and the self-healing algorithm configured in step S701, the NS-SH-IF decides to create a new NSSI instead of the failed NSSI.

S705, optionally, the NS-SH-IF backs up relevant configuration information, logical topology location, user service information, etc. of the NSSI1 to the NS hierarchy through the interface 5, so as to recover when the self-healing failure occurs.

S706, NS-SH-IF sends a create NSSI request to NSSMF2 over interface 2. The creation request at least includes: the type of the newly created NSSI, the included functionality, the SLA to be satisfied, the occupied network resources, etc. NSSMF2 creates NSSI 2 upon the received request.

S707, NS-SH-IF sends a command to NSSMF2 via interface 2 to configure NSSI 2, the configuration message including at least application parameters, location in the network topology, interface information between other NSSIs, etc. It should be noted that the configuration content here may be consistent with the configuration of NSSI1 collected by NS-SH-IF in step S704 when it runs correctly, or may be different because of different implementations of the network slice subnet instances.

S708, IF the current state of the NSSI1 is the activated state, the NS-SH-IF logs off the NSSI 1. Deregistration includes marking the status of NSSI1 in NSS reproducibility and/or NS reproducibility as deregistered, informing NSSMF1 to stop the service running on NSSI 1.

S709, NS-SH-IF sends a command to NSSMF3 via interface 2 to configure NSSI 3, associating NSSI 3 with NSSI 2, the configuration message including at least one of: application parameter changes, location changes in the network topology, and interface information between NSSI 2, etc.

S710, NS-SH-IF activates NSSI 2. Activation includes marking the status of NSSI 2 in NSS hierarchy and/or nshierarchy as active, informing NSSMF2 to start NSSI 2 and loading the user service information on NSSI1 acquired in step S704 to restore service.

S711, NS-SH-IF collects information of the network slice instance and evaluates the self-healing result. The collected information includes at least one of: NS-SH-IF issues performance measurement and threshold monitoring tasks for NSSI 2 and NSSMF3 respectively to NSSMF2 and NSSMF3 through interface 2, NSSMF2 and NSSMF3 execute the performance measurement and threshold monitoring tasks, and report the result of the performance measurement and/or the alarm of the threshold exceeding to NS-SH-IF through interface 2.

And S712, IF any step from the step S706 to the step S710 fails, or the information collected by the NS-SH-IF in the step S711 indicates that the newly created NSSI 2 can not replace the failed NSSI1 to normally operate, triggering a recovery action. Specifically, the NS-SH-IF reads the network status and configuration before the self-healing operation is performed, which are saved in step S705, and thus reconfigures NSSI 3 and NSSI1 and activates NSSI 1.

S713, NS-SH-IF updates the operation state, topology information, configuration information and the like of the network slice instance in NS replication through an interface 5, records the self-healing actions from step S706 to step S712, and records fault information and self-healing results. It should be noted that, even if the self-healing action fails to repair the fault and recover the service, the corresponding self-healing action, fault information and self-healing result need to be recorded.

S714, NS-SH-IF reports the adopted self-healing action and self-healing result to NS-SH-MMF. And the NS-SH-MMF reports the fault information, the self-healing action and the self-healing result to the SMF through the interface 1.

In the embodiment of the application, when the network slice subnet examples forming the network slice examples have faults, new network slice subnet examples can be automatically created without manual intervention to replace the fault network slice subnet examples to recover the service, meanwhile, the consistency and consistency of the service are ensured as much as possible, and the reliability of the whole network slice examples is improved. Meanwhile, the method of the embodiment of the application can also recover the modification of the network slice example when the self-healing fails, so that an operator can pay attention to the original error. In addition, the method provided by the embodiment of the application records the fault information, the self-healing action and the self-healing result, and can provide reference for the automatic operation and maintenance decision of the network slice example, so that the system can process the network fault of the same type more intelligently and quickly.

It should be noted that the embodiment of the present application is applicable to an application scenario in which the network slice instance is composed of network slice subnet instances, and solves a possible self-healing mechanism at a network slice level when a failure that the network slice subnet instances cannot self-heal occurs. The process and the method related to the embodiment of the application are also suitable for an application scene that the network slice example is composed of network functions, and when a fault that the network function cannot self-heal occurs, a self-healing mechanism that creates a new network function and replaces the fault network function is possibly adopted, the process and the steps of creating the self-healing mechanism of the new network function are similar to the process steps in the embodiment of the application, and the information of the network slice subnet example is replaced by the information of the corresponding network function in the interaction information among the modules.

In addition, NSSI1, NSSI 2, NSSI 3, NSSMF1, NSSMF2, NSSMF3 used in the embodiments of the present application are only for illustration, and the method of the present application does not limit the number of failed network slice subnet instances, the number of network slice subnet instances interacting with the failed network slice subnet instances, and the number of newly created network slice subnet instances. For example, a failed network slice subnet instance may require several network slice subnet instances to be created instead. In addition, the failed NSSI, the new NSSI, and other NSSIs with interaction may be managed by different NSSMFs, or may be managed by one NSSMF at the same time, which is not limited in this application.

Fig. 8 is a schematic flow chart diagram of a method of managing a network slice example according to an embodiment of the present application. The method of fig. 8 may be applied to the network management architectures shown in fig. 1-4. The first network device in fig. 8 may be an NS _ SH _ IF module or an NSMF module that includes NS _ SH _ MMF and NS _ SH _ IF modules. The second network device may be a NSSMF module. The storage device may be NS hierarchy. For brevity, the same or similar contents as those in the foregoing description in the method of fig. 8 refer to the corresponding contents in the foregoing description, and are not repeated herein.

As shown in fig. 8, the method includes:

s801, the first network device determines that the first network slice subnet instance has a fault.

S802, the first network device sends first indication information to a second network device, where the first indication information is used to indicate the second network device to execute a fallback processing on the first network slice subnet instance.

Alternatively, the above-mentioned rollback processing may be understood as resetting the configuration parameters of the first network slice subnet instance to the configuration parameters at a time before the current time. The configuration parameters at a time prior to the current time may be historical configuration parameters.

In the embodiment of the present application, when determining that the first network sliced subnet instance has a fault, the first network device may instruct the second network device to execute fallback processing on the first network sliced subnet instance, so that the network sliced subnet instance can be flexibly managed, and the efficiency of managing the network sliced instance is improved.

Optionally, the method of fig. 8 further comprises: the first network equipment acquires historical parameter information of the first network slice subnet instance; the first network device determines the first indication information based on historical parameter information for the first network slice subnet instance.

As an example, the first network device may further obtain historical parameter information of the network slice instance of the first network slice subnet instance. For example, the historical parameter information may include information about the network slice instances and the network slice subnet instances, including at least one of:

a) NS-SH-IF sends performance measurement task and threshold measurement task to NSSMF1 through interface 2, NS-SH-IF receives performance data and threshold measurement result reported by NSSMF1 through interface 2;

b) the NS-SH-IF sends a performance measurement task and a threshold measurement task to the management function of other network slice subnet instances interacting with the NSSI1, namely, the NSSMF3, and the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF3 through the interface 2;

c) the NS-SH-IF finds a corresponding management module capable of creating a new NSSI to replace the failure NSSI according to the self-healing configuration, the management module is assumed to be NSSMF3 in the embodiment of the application, and the NS-SH-IF sends a feasibility checking request for creating the new NSSI to the NSSMF3 through an interface 2;

d) NS-SH-IF reads configuration information of NSSI1 in normal operation from NS replication through interface 5, wherein the configuration information comprises SLA, position in the logic topology of the network slice instance and interface information;

e) the NS-SH-IF acquires the service information running on the NSSI1 from the NSSMF1 through the interface 2, wherein the service information comprises user data, configuration and the like;

f) the NS-SH-IF reads the historical fault information of the NSSI1, the adopted repair action and the repair result from the NS repeatability through the interface 5, reads the fault information of other network slice subnet examples of the same type as the NSSI1, the adopted repair action and the repair result, and the like.

Optionally, the method of fig. 8 further comprises: the first network equipment acquires historical parameter information of the first network slice subnet instance from the second network equipment; the first network equipment backs up the historical parameter information of the first network slice subnet instance to a storage device; the first network device obtaining historical parameter information of the first network slice subnet instance includes: the first network device obtains historical parameter information of the first network slice subnet instance from the storage device.

Optionally, the method of fig. 8 further comprises: before the first network equipment sends first indication information to second network equipment, the first network equipment acquires current parameter information of the first network slice subnet instance; and the first network equipment backs up the current parameter information of the first network slice subnet instance to a storage device.

Optionally, the method of fig. 8 further comprises: and under the condition that the performance of the first network slice subnet instance after executing the rollback processing does not meet a preset condition, the first network device sends second indication information to the second network device, wherein the second indication information is used for indicating the second network device to restore the first network slice subnet instance based on the current parameter information of the first network slice subnet instance backed up to the storage device.

Optionally, the method of fig. 8 further comprises: the first network equipment acquires the performance information of the first network slice subnet instance after executing rollback processing, wherein the performance information is used for indicating the performance of the first network slice subnet instance; the first network device determines whether performance of the first network slice subnet instance meets a predetermined condition based on the performance information.

Optionally, the method of fig. 8 further comprises: the first network device receives fault alarm information from the second network device, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault; the first network device determining that a first network slice subnet instance fails, comprising: and the first network equipment determines the first network slice subnet instance according to the fault alarm information.

As a specific example, fig. 9 shows a schematic flow chart of a method for managing a network slice instance according to an embodiment of the present application. The method of fig. 9 may be used in any of the network management architectures of fig. 1-4. Fig. 9 illustrates a network slice management process for replacing a newly created NSSI with a failed NSSI. The first network device may be an NS _ SH _ IF module or an NSMF module, which includes NS _ SH _ MMF and NS _ SH _ IF modules. The second network device may be a NSSMF module. The storage device may be NS hierarchy.

As shown in fig. 9, the method includes:

s901, NS-SH-MMF configures the self-healing algorithm needed to be executed by NS-SH-IF. Specifically, for a self-healing mechanism of network slice instance modification and configuration rollback, the configured content includes an identity of an NSI, a fault repair requirement of the NSI, backup requirements for information such as configuration and state of a network slice instance and a network slice subnet instance, such as a backup time period, whether to cover an original backup, and a trigger rule of network slice instance modification and configuration rollback includes an event, a fault type, a condition, and the like. It should be noted that the NS-SH-MMF may update the configuration of the self-healing algorithm of the NS-SH-IF at any time.

And S902, the NS-SH-IF judges whether the backup of the network slice instance information needs to be created or updated according to the configured self-healing algorithm. Conditions that trigger a backup may include time, events expected to occur, and the like. (events refer to modifications to network slice instances, configurations, changes in user behavior, etc.)

S903, NS-SH-IF decides to backup information for the network slice instance, and obtains NSSI information from NSSMF via interface 2, which may include the configuration of the current NSSI, its location in the network topology, interface information between it and other NSSI, SLA, performance data, etc. Optionally, the NS-SH-IF reads the saved NSSI information from the NS replication and determines which information needs to be updated.

S904, NS-SH-IF records and/or updates information of each NSSI constituting the NSI in NS replication through interface 5.

S905, one NSSI forming the NSI is in failure, and normal operation of the network slice example is influenced. In the present embodiment, it is assumed that NSSI1 fails, which is managed by NSSMF 1. NSSMF1 generates a network slice subnet instance fault alarm and reports to NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm comprises at least one of the following contents: fault alarm ID, NSSI ID, time of occurrence of a fault, fault type, cause of fault, source of fault, severity of fault, impact of fault on service, available repair methods, etc.

And S906, the NS-SH-MMF judges that the self-healing triggering condition is met according to the fault alarm, and sends a self-healing triggering command to the NS-SH-IF. The NS-SH-IF receives the self-healing trigger command.

S907, NS-SH-IF collects information of related network slice instances and network slice subnet instances, and the collected information comprises at least one of the following contents: a) NS-SH-IF sends performance measurement task and threshold measurement task to NSSMF1 through interface 2, NS-SH-IF receives performance data and threshold measurement result reported by NSSMF1 through interface 2; b) NS-SH-IF sends performance measurement task and threshold measurement task to the management function of other network slice subnet instances interacting with NSSI1, NS-SH-IF receives reported performance data and threshold measurement result through interface 2; c) the NS-SH-IF reads backup information of NSSI1 in normal operation from NSReploitory through an interface 5, wherein the backup information comprises SLA, position in the logic topology of the network slice instance, interface information and the like; d) the NS-SH-IF reads the historical fault information of the NSSI1, the adopted repair action and the repair result from the NS repeatability through the interface 5, reads the fault information of other network slice subnet examples of the same type as the NSSI1, and adopts the repair action and the repair result. Based on the collected information and the self-healing algorithm configured in step S901, the NS-SH-IF decides to take a rollback action for NSSI1 and decides which point in time backup information to perform the rollback.

S908, optionally, the NS-SH-IF backs up relevant configuration information, logical topology location, user service information, etc. of the NSSI1 to the NS hierarchy through the interface 5, so as to recover when the self-healing failure occurs.

S909, NS-SH-IF sends a rollback command to NSSMF1 over interface 2. Depending on the specific case of network failure, the rollback command may include: a) logging off and terminating the newly created NSSI1, wherein the command needs to comprise the identity of the NSSI 1; b) Reconfiguring NSSI1 according to the NSSI configuration backup information obtained in the step 7); c) restoring modifications to the NSSI1 including shrinking expanded capacity, expanding reduced capacity, adding deleted network functions, deleting newly added network functions, etc. When the rollback command is to create and activate a terminated NSSI, the rollback command may not be sent to NSSMF1, but may be sent to other NSSMFs, and the command may include an identity of the NSSI, configuration information, SLA, interface information, and the like. In addition, when the rollback command is to create a terminated NSSI, the NS-SH-IF also needs to send configuration messages to the managers of other NSSIs that have an interaction with the NSSI.

S910, NSSMF1 (or other NSSMF) finishes the corresponding action and feeds back the execution result to NS-SH-IF.

S911 and NS-SH-IF collect information of the network slice example and evaluate a self-healing result. The collected information includes at least one of: NS-SH-IF sends down performance measurement and threshold monitoring tasks to NSSMF1 and/or other NSSMFs through interface 2, and the corresponding NSSMF executes the performance measurement and threshold monitoring tasks and reports the result of the performance measurement and/or alarm of exceeding threshold to NS-SH-IF through interface 2.

S912, IF the rollback fails, or the information collected by the NS-SH-IF in step S911 indicates that the failure still exists and does not go forward after rollback, the NS-SH-IF initiates recovery of the modification caused by the rollback action. Specifically, the NS-SH-IF reads the network status and configuration before the self-healing action saved in step S908 is performed, and accordingly notifies NSSMF1 to reconfigure NSSI1 and/or to resume modification of NSSI 1.

S913, the NS-SH-IF updates the running state, topology information, configuration information and the like of the network slice instance in the NS replication through the interface 5, records the self-healing actions from the step S908 to the step S912, and records fault information and self-healing results. It should be noted that, even if the self-healing action fails to repair the fault and recover the service, the corresponding self-healing action, fault information and self-healing result need to be recorded.

S914, NS-SH-IF reports the adopted self-healing action and self-healing result to NS-SH-MMF. And the NS-SH-MMF reports the fault information, the self-healing action and the self-healing result to the SMF through the interface 1.

The method for managing network slices and the network management architecture of the embodiment of the present application are described in detail above with reference to fig. 1 to 9, and the network device of the embodiment of the present application is described in detail below with reference to fig. 10 to 17.

Fig. 10 is a schematic block diagram of a network device 1000 according to an embodiment of the present application. It should be understood that the network device 1000 is capable of performing the steps performed by the first network device in the methods of fig. 5-7, and will not be described in detail herein to avoid repetition. The network device 1000 includes: a processing unit 1001 and a communication unit 1002,

the processing unit 1001 is configured to determine that a first network slice subnet instance fails; sending, by the communication unit 1002, first indication information to a second network device, where the first indication information is used to indicate the second network device to activate a second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance.

Fig. 11 is a schematic block diagram of a network device 1100 according to an embodiment of the present application. It should be understood that the network device 1100 is capable of performing the various steps performed by the second network device in the methods of fig. 5-7, and will not be described in detail herein to avoid repetition. The network device 1100 includes: a processing unit 1101 and a communication unit 1102,

the processing unit 1101 is configured to receive, through the communication unit 1102, first indication information from a first network device, where the first indication information is used to indicate that a second network device activates a second network slice subnet instance, where the second network slice subnet instance is used to replace a first network slice subnet instance; and activating the second network slice subnet instance according to the first indication information.

Fig. 12 is a schematic block diagram of a network device 1200 according to an embodiment of the present application. It should be understood that network device 1200 is capable of performing the various steps performed by the first network device in the method of fig. 8 or 9 and will not be described in detail herein to avoid repetition. The network device 1200 includes: a processing unit 1201 and a communication unit 1202,

the processing unit 1201 is configured to determine that a first network slice subnet instance fails; sending, by the communication unit 1202, first indication information to a second network device, where the first indication information is used to instruct the second network device to execute fallback processing on the first network slice subnet instance.

Fig. 13 is a schematic block diagram of a network device 1300 according to an embodiment of the present application. It should be understood that the network device 1300 is capable of performing the steps performed by the second network device in the method of fig. 8 or 9, and will not be described in detail herein to avoid repetition. The network device 1300 includes: a processing unit 1301 and a communication unit 1302,

the processing unit 1301 is configured to receive, through the communication unit 1302, first indication information from a first network device, where the first indication information is used to instruct the second network device to perform fallback processing on a failed first network slice subnet instance; and executing rollback processing on the first network slice subnet instance according to the first indication information.

Fig. 14 is a schematic block diagram of a network device 1400 according to an embodiment of the present application. It should be understood that the network device 1400 is capable of performing the steps performed by the first network device in the methods of fig. 5-7, and will not be described in detail herein to avoid repetition. The network device 1400 includes:

a memory 1410 for storing programs;

a communication interface 1420 for communicating with other devices;

a processor 1430 for executing a program in memory 1410, the processor 1430 for determining that a first network slice subnet instance has failed when the program is executed; sending, by the communication interface 1420, first indication information to a second network device, the first indication information being used to indicate the second network device to activate a second network slice subnet instance, wherein the second network slice subnet instance is used to replace the first network slice subnet instance.

Fig. 15 is a schematic block diagram of a network device 1500 of an embodiment of the application. It should be understood that network device 1500 is capable of performing the various steps performed by the second network device in the methods of fig. 5-7, and will not be described in detail herein to avoid repetition. The network device 1500 includes:

a memory 1510 for storing a program;

a communication interface 1520 for communicating with other devices;

a processor 1530 configured to execute a program in the memory 1510, wherein when the program is executed, the processor 1530 is configured to receive first indication information from a first network device through the communication interface 1520, the first indication information being used to indicate that a second network device activates a second network slice subnet instance, wherein the second network slice subnet instance is used to replace the first network slice subnet instance; and activating the second network slice subnet instance according to the first indication information.

Fig. 16 is a schematic block diagram of a network device 1600 of an embodiment of the application. It should be understood that network device 1600 is capable of performing the various steps performed by the first network device in the method of fig. 8 or 9, and will not be described in detail herein to avoid repetition. The network device 1600 includes:

a memory 1610 for storing programs;

a communication interface 1620 for communicating with other devices;

a processor 1630 that executes a program in memory 1610, which when executed, the processor 1630 determines that a first network slice subnet instance has failed; sending first indication information to a second network device through the communication interface 1620, where the first indication information is used to indicate the second network device to execute fallback processing on the first network slice subnet instance.

Fig. 17 is a schematic block diagram of a network device 1700 according to an embodiment of the present application. It should be understood that network device 1700 is capable of performing the various steps performed by the second network device in the method of fig. 8 or 9, and will not be described in detail herein to avoid repetition. The network device 1700 includes:

a memory 1710 for storing programs;

a communication interface 1720 for communicating with other devices;

a processor 1730 for executing a program in memory 1710, the processor 1730, when executed, for receiving first indication information from a first network device via the communication interface 1720, the first indication information for indicating to the second network device to perform fallback processing for a failed first network slice subnet instance; and executing rollback processing on the first network slice subnet instance according to the first indication information.

In the embodiment of the application, when the network slice subnet examples forming the network slice examples have faults, the configuration and the modification of the faults of the network slice examples caused by the faults of the network slice examples can be automatically backed without manual intervention, the faults are repaired immediately, the continuity and the consistency of services are ensured, and the integral reliability of the network slice examples is improved. Meanwhile, the method of the embodiment of the application can also recover the modification of the network slice example when the self-healing fails, so that an operator can pay attention to the original error. In addition, the method provided by the embodiment of the application records the fault information, the self-healing action and the self-healing result, and can provide reference for the automatic operation and maintenance decision of the network slice example, so that the system can process the same type of network fault more intelligently and quickly, and the same configuration and modification of the network slice example in the future can be avoided, and the same errors are generated.

It should be noted that the embodiment of the present application is applicable to an application scenario in which the network slice instance is composed of network slice subnet instances, and solves a possible self-healing mechanism at a network slice level when a failure that the network slice subnet instances cannot self-heal occurs. The flow and the method related to the embodiment of the application are also suitable for solving the self-healing mechanism of executing rollback to repair the fault when the network function has the fault which can not be self-healed under the application scene that the network slice example is composed of the network functions. The flow and steps of the self-healing mechanism of the network function rollback are similar to the flow steps in the embodiment of the application, and the information of the network slice subnet example in the interactive information among the modules is replaced by the information of the corresponding network function.

In addition, NSSI1 and NSSMF1 used in the embodiments of the present application are only required for illustration, and the method of the present application does not limit the number of failed network slice subnet instances and the number of network slice subnet instances that need to be rolled back.

Fig. 2-4 illustrate that when a network slice subnet instance nests a network slice subnet instance, there may be three network management architectures. The following describes how the method of managing network slice instances of the embodiments of the present application is performed in these three network management architectures.

For example, in the system shown in FIG. 2, NSSMF1 includes an NSS-SH-MMF1 module and an NSS-SH-IF 1 module, and NSSMF2 includes only an NSS-SH-IF 2 module. In performing the method of managing network slice instances,

A) the self-healing algorithm, configuration, parameters and the like in the NSS-SH-IF 2 module are configured by the NSS-SH-MMF1 through the interface 4, that is, the sending end of steps S601, S701 and S901 in the methods of fig. 6, fig. 7 and fig. 9 is the NSS-SH-MMF1, the receiving end is the NSS-SH-IF 2, and the configured content is the self-healing algorithm of the NSSI 2 through the interface 4;

B) when NSSI 2 fails, the fault alarm is transmitted to NSS-SH-MMF1 through interface 4 after the fault alarm is generated, that is, corresponding to steps S602 and S702 of the methods in fig. 6 and fig. 7 and step S905 of the method in fig. 9, NSSMF2 reports the fault alarm to NSS-SH-MMF 1;

C) the NSS-SH-MMF1 determines whether the NSSI 2 satisfies the fault self-healing trigger condition, and sends a self-healing trigger request to the NSS-SH-IF 2 through the interface 4, that is, corresponding to steps S603 and S703 of the methods of fig. 6 and fig. 7, and step S906 in the method of fig. 9;

D) after the NSS-SH-IF 2 performs the self-healing action, it will report the self-healing result to the NSS-SH-MMF1 through the interface 4, that is, corresponding to step S613 of the method in fig. 6, and steps S714 and S914 of the methods in fig. 7 and 9;

E) finally, optionally, the NSS-SH-MMF1 reports the fault information and/or the self-healing result to the NS-SH-MMF. In the system shown in fig. 2, optionally, the NS-SH-MMF may configure, through the interface 2, reporting of a self-healing result in the NSs-SH-MMF1, a self-healing trigger condition and/or its self-healing configuration for the NSs-SH-IF 1, the NSs-SH-IF 2, and the like.

For example, in the system shown in FIG. 3, NSSMF1 includes a NSS-SH-MMF1 module and a NSS-SH-IF 1 module, and NSSMF2 includes a NSS-SH-MMF 2 module and a NSS-SH-IF 2 module. In performing the method of managing network slice instances,

A) the self-healing algorithm, configuration, parameters and the like in the NSS-SH-IF 2 module are configured by the NSS-SH-MMF 2, that is, the sending end of steps S601, S701 and S901 of the methods of fig. 6, fig. 7 and fig. 9 is NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the configured content is the self-healing algorithm of NSSI 2;

B) when the network function in NSSI 2 fails, a generated fault alarm is reported to NSS-SH-MMF 2, that is, the NSS-SH-MMF 2 monitors the network failure in NSSI 2, which corresponds to steps S602 and S702 of the methods in fig. 6 and fig. 7 and step S905 of the method in fig. 9, it should be noted that the network function constituting NSSI 2 may be directly managed by NSSMF2 or managed by NFM, which is not limited in this application;

C) the NSS-SH-MMF 2 determines whether the NSSI 2 satisfies the fault self-healing trigger condition, and sends a self-healing trigger request to the NSS-SH-IF 2, that is, step S603 and step S703 of the method in fig. 6 and fig. 7, and step S906 in the method in fig. 9;

D) after the NSS-SH-IF 2 performs the self-healing action, it will report the self-healing result to the NSS-SH-MMF 2, that is, corresponding to step S613 of the method in fig. 6, and steps S714 and S914 of the methods in fig. 7 and 9;

E) finally, the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSSMF1, and optionally, the NSSMF1 reports the fault information and/or the self-healing result to the NSMF. In the system shown in fig. 10, optionally, the NS-SH-MMF may configure, through the interface 2, reporting of the self-healing result in the NSs-SH-MMF1, a self-healing trigger condition and/or its self-healing configuration for the NSs-SH-IF 1, the NSs-SH-MMF 2, and the like.

For example, in the system shown in FIG. 4, NSSMF1 includes a NSS-SH-MMF1 module and a NSS-SH-IF 1 module, NSSMF2 includes a NSS-SH-MMF 2 module and a NSS-SH-IF 2 module, and a direct interface 2 exists between NSMF and NSSMF 2. In performing the process of managing network slice instances of embodiments of the present application,

A) the self-healing algorithm, configuration, parameters and the like in the NSS-SH-IF 2 module are configured by the NSS-SH-MMF 2, that is, the sending end of steps S601, S701 and S901 in the methods of fig. 6, fig. 7 and fig. 9 is NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the configured content is the self-healing algorithm of NSSI 2;

B) when the network function in NSSI 2 fails, a generated fault alarm is reported to NSS-SH-MMF 2, that is, the NSS-SH-MMF 2 monitors the network failure in NSSI 2, that is, corresponding to steps S602 and S702 of the methods in fig. 6 and fig. 7 and step S905 of the method in fig. 9, it should be noted that the network function forming NSSI 2 may be directly managed by NSSMF2 or managed by NFM, which is not limited in this application;

C) the NSS-SH-MMF 2 determines whether the NSSI 2 satisfies the fault self-healing trigger condition, and sends a self-healing trigger request to the NSS-SH-IF 2, that is, corresponding to steps S603 and S703 of the methods of fig. 6 and fig. 7, and step S906 of the method of fig. 9;

D) after the NSS-SH-IF 2 performs the self-healing action, it will report the self-healing result to the NSS-SH-MMF 2, i.e. corresponding to step S613 of the method of fig. 6, and steps S714 and S914 of the methods of fig. 7 and 9;

E) and finally, optionally, the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSMF, and optionally, the NSS-SH-MMF 2 can also report the fault information and/or the self-healing result to the NSSMF 1. In the system shown in fig. 11, optionally, the NS-SH-MMF may configure reporting of the self-healing result in the NSs-SH-MMF 2, a self-healing trigger condition and/or self-healing configuration of the NSs-SH-MMF 2 by using the interface 2.

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

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

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

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

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

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

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of managing network slice instances, comprising:

the first network equipment determines that the first network slice subnet instance has a fault;

the first network device sends first indication information to a second network device, wherein the first indication information is used for indicating the second network device to activate a second network slice subnet instance, the second network slice subnet instance is used for replacing the first network slice subnet instance, and the activating the second network slice subnet instance comprises indicating the second network device to switch the first network slice subnet instance to the second network slice subnet instance;

and the first network equipment sends second indication information to third network equipment, wherein the second indication information is used for indicating the third network equipment to log out the first network slice subnet instance.

2. The method of claim 1, wherein the method further comprises: the first network device sends third indication information to a fourth network device, where the third indication information is used to indicate the fourth network device to reconfigure a third network slice subnet instance associated with the first network slice subnet instance, and the reconfigured third network slice subnet instance is associated with the second network slice subnet instance.

3. The method of claim 1 or 2, wherein prior to said sending the first indication information to the second network device, the method further comprises:

and the first network equipment backs up the parameter information of the first network slice subnet instance to a storage device.

4. The method of claim 3, wherein the method further comprises: and under the condition that the performance of the second network slice subnet instance does not meet the preset condition, the first network device sends fourth indication information to a third network device, wherein the fourth indication information is used for indicating the third network device to restore the first network slice subnet instance based on the parameter information backed up to the storage device by the first network slice subnet instance.

5. The method of claim 4, wherein the method further comprises: the first network equipment acquires performance information of the second network slice subnet instance, wherein the performance information is used for indicating the performance of the second network slice subnet instance;

the first network device determines whether the performance of the second network slice subnet instance meets a predetermined condition based on the performance information.

6. The method of claim 1 or 2, wherein the method further comprises: the first network device receives fault alarm information from the second network device, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault;

the first network device determining that a first network slice subnet instance fails, comprising:

and the first network equipment determines the first network slice subnet instance according to the fault alarm information.

7. A method of managing network slice instances, comprising:

the second network equipment receives first indication information from the first network equipment, wherein the first indication information is used for indicating the second network equipment to activate a second network slice subnet instance, and the second network slice subnet instance is used for replacing the first network slice subnet instance;

the second network device activates the second network slice subnet instance according to the first indication information, the activating the second network slice subnet instance including instructing the second network device to switch the first network slice subnet instance to the second network slice subnet instance;

and the second network equipment sends fault alarm information to the first network equipment, wherein the fault alarm information is used for indicating that the first network slice subnet instance has a fault.

8. A network device, wherein the network device is a first network device, comprising:

a communication interface for the communication of the information to the external,

a memory for storing instructions for storing the instructions,

a processor, connected to the memory and the communication interface respectively, for executing the instructions stored in the memory, so as to execute the following steps when executing the instructions:

determining that a first network slice subnet instance fails;

sending first indication information to a second network device through the communication interface, wherein the first indication information is used for indicating the second network device to activate a second network slice subnet instance, the second network slice subnet instance is used for replacing the first network slice subnet instance, and the activating the second network slice subnet instance comprises indicating the second network device to switch the first network slice subnet instance to the second network slice subnet instance;

the processor is further configured to send second indication information to a third network device through the communication interface, where the second indication information is used to indicate the third network device to logout the first network slice subnet instance.

9. The network device of claim 8, wherein the processor is further configured to send, to a fourth network device via the communication interface, third indication information for indicating that the fourth network device reconfigured a third network slice subnet instance associated with the first network slice subnet instance, the reconfigured third network slice subnet instance associated with the second network slice subnet instance.

10. The network device of claim 8 or 9, wherein the processor is further configured to: before the first indication information is sent to the second network device, backing up the parameter information of the first network slice subnet instance to a storage device.

11. The network device of claim 10, wherein the processor is further configured to: and sending fourth indication information to a third network device through the communication interface under the condition that the performance of the second network slice subnet instance does not meet a preset condition, wherein the fourth indication information is used for indicating the third network device to restore the first network slice subnet instance based on the parameter information backed up to the storage device by the first network slice subnet instance.

12. The network device of claim 11, wherein the processor is further configured to obtain performance information for the second network slice subnet instance, the performance information indicating performance of the second network slice subnet instance; the first network device determines whether the performance of the second network slice subnet instance meets a predetermined condition based on the performance information.

13. The network device of claim 8 or 9, wherein the processor is further configured to receive fault alert information from the second network device over the communication interface, the fault alert information indicating that the first network slice subnet instance has failed; in an aspect that the first network device determines that the first network-slice subnet instance has a fault, the processor is specifically configured to determine the first network-slice subnet instance according to the fault alarm information.

14. A network device, wherein the network device is a second network device, comprising:

a memory for storing instructions for storing the instructions,

receiving first indication information from a first network device through the communication interface, the first indication information being used for indicating that a second network device activates a second network slice subnet instance, wherein the second network slice subnet instance is used for replacing a first network slice subnet instance;

activating the second network slice subnet instance according to the first indication information, the activating the second network slice subnet instance comprising instructing the second network device to switch the first network slice subnet instance to the second network slice subnet instance;

the processor is further configured to send failure alarm information to the first network device through the communication interface, where the failure alarm information is used to indicate that the first network slice subnet instance has a failure.