WO2018171430A1 - Method and system for managing network slice instance, and network device - Google Patents

Method and system for managing network slice instance, and network device Download PDF

Info

Publication number
WO2018171430A1
WO2018171430A1 PCT/CN2018/078292 CN2018078292W WO2018171430A1 WO 2018171430 A1 WO2018171430 A1 WO 2018171430A1 CN 2018078292 W CN2018078292 W CN 2018078292W WO 2018171430 A1 WO2018171430 A1 WO 2018171430A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network device
network slice
instance
slice subnet
Prior art date
Application number
PCT/CN2018/078292
Other languages
French (fr)
Chinese (zh)
Inventor
陆伟
杨水根
孙文琦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018171430A1 publication Critical patent/WO2018171430A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis

Definitions

  • the present application relates to the field of communications and, more particularly, to methods, network devices and systems for managing network slice instances.
  • Network slicing technology refers to the logical abstraction of a network into one or more network slices, where each network slice contains a series of logical network functions, and a network slice can satisfy the connection communication service requirements of a certain class or a use case.
  • the next generation mobile communication system can be composed of a large number of network slices that satisfy different connection capabilities.
  • the fault can be found by the self-test circuit of the faulty network element, or the performance and threshold measurement tasks find the fault.
  • this self-healing system can only manage the failure of a single network function, and cannot meet the flexible fault management requirements of the network slicing level.
  • the present application provides a method, apparatus, and system for managing network slice instances, which can improve the efficiency of managing network slice instances.
  • the first aspect provides a method for managing a network sharding instance, including: determining, by a first network device, that a first network tiling subnet instance is faulty; and the first network device sending, by using the first network device, first indication information, where The first indication information is used to indicate that the second network device activates the second network slice subnet instance, wherein the second network slice subnet instance is used to replace the first network slice subnet instance.
  • the first network device when determining that the first network slice subnet instance is faulty, may instruct the second network device to activate the second network slice subnet instance to replace the first network slice subnet instance. , which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
  • the method further includes: the first network device sends second indication information to the third network device, where the second indication information is used to instruct the third network device to log off the first network Slice a subnet instance.
  • the first network device sends the second indication information to the third network device, to instruct the third network device to cancel the failed first network slice subnet instance, so as to facilitate the second network slice subnet.
  • the instance replaces 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.
  • the method further includes: the first network device sends third indication information to the fourth network device, where the third indication information is used to indicate the fourth network device reconfiguration and the first A third network slice subnet instance associated with a network slice subnet instance, the reconfigured third network slice subnet instance being associated with the second network slice subnet instance.
  • 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 first
  • the three network slicing subnet instances cooperate to provide services, which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
  • the method before the sending the second indication information to the second network device, the method further includes: the first network device backing up parameter information of the first network slice subnet instance To the storage device.
  • 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.
  • the method further includes: sending, by the first network device, fourth indication information to the third network device, if the performance of the second network slice subnet instance does not meet the predetermined condition, where The fourth indication information is used to instruct the third network device to restore the first network slice subnet instance based on parameter information of the backup of the first network slice subnet instance to the storage device.
  • the first network device instructs the third network device to restore the first network slice subnet instance based on the parameter information in the backup of the first network slice subnet instance to the storage device, so that the network slice can be flexibly managed.
  • the method further includes: the first network device acquiring performance information of the second network slice subnet instance, where the performance information is used to indicate performance of the second network slice subnet instance And determining, by the first network device, whether performance of the second network slice subnet instance meets a predetermined condition based on the performance information.
  • the first network device instructs the third network device to restore the first network slice subnet instance based on the parameter information in the backup of the first network slice subnet instance to the storage device, so that the network slice can be flexibly managed.
  • the method further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; The first network device determines that the first network slice subnet instance is faulty, and the first network device determines the first network slice subnet instance according to the fault alarm information.
  • the first network device receives the fault alarm information from the second network device, and determines that the first network slice subnet instance is faulty according to the fault alarm information, thereby flexibly managing the network slice instance and improving management. The efficiency of the network slice instance.
  • the method further includes: the first network device records, by using the second network slice subnet instance, process information of the first network slice subnet instance to a storage device.
  • the first network device records, by using the second network slice subnet instance, the process information of the first network slice subnet instance to the storage device, so that the network slice instance can be flexibly managed, and the management network slice is improved. The efficiency of the instance.
  • the method further includes: the second network slice subnet instance is a redundant network slice subnet instance managed by the second network device.
  • the method further includes: the second network slice subnet instance is a newly created network slice subnet instance of the second network device.
  • a second aspect provides a method for managing a network sharding instance, including: receiving, by a second network device, first indication information from a first network device, where the first indication information is used to indicate that the second network device activates a second a network slice subnet instance, wherein the second network slice subnet instance is configured to replace the first network slice subnet instance; the second network device activates the second network slice according to the first indication information Network instance.
  • the second network device receives the first indication information from the first network device, and the second network device activates the second network slice subnet instance to replace the first network slice according to the first indication information.
  • Network instance which enables flexible management of network slice instances and improves the efficiency of managing network slice instances.
  • the method further includes: the second network device sending fault alarm information to the first network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty.
  • the second network device sends the fault alarm information to the first network device, to indicate to the first network device that the first network slice subnet instance is faulty, so that the network slice instance can be flexibly managed, and the management is improved.
  • the efficiency of the network slice instance is improved.
  • a third aspect provides a method for managing an instance of a network slice, including: determining, by a first network device, that a first network slice subnet instance is faulty; and the first network device sends first indication information to the second network device, where The first indication information is used to instruct the second network device to perform a rollback process on the first network slice subnet instance.
  • the second network device may be instructed to perform a rollback process on the first network sliced subnet instance, so that the network can be flexibly managed.
  • Slice instances improve the efficiency of managing network slice instances.
  • the method further includes: the first network device acquiring historical parameter information of the first network slice subnet instance; the first network device is based on the first network slice subnet instance The historical parameter information determines the first indication information.
  • the first network device acquires historical parameter information of the first network slice subnet instance; and determines the first indication information based on the historical parameter information.
  • the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
  • the method further includes: the first network device acquiring, from the second network device, historical parameter information of the first network slice subnet instance; the first network device The historical parameter information of the network segment subnet instance is backed up to the storage device; the first network device acquiring the historical parameter information of the first network slice subnet instance, where the first network device obtains from the storage device The historical parameter information of the first network slice subnet instance.
  • 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.
  • the method before the first network device sends the first indication information to the second network device, the method further includes: acquiring, by the first network device, current parameters of the first network slice subnet instance The first network device backs up current parameter information of the first network slice subnet instance to the storage device.
  • the first network device backs up the current parameter information of the first network slice instance to the storage device, so as to restore the first network slice subnet instance, thereby being able to flexibly manage the network slice instance and improve the management network.
  • the efficiency of the slice instance is the efficiency of the slice instance.
  • the method further includes: the first network device is in the second network, if the performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition The device sends the second indication information, where the second indication information is used to instruct the second network device to restore the first information based on the current parameter information that is backed up to the first network slice subnet instance in the storage device. Network slice subnet instance.
  • the first network device obtains 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 improved.
  • the efficiency of managing network slice instances is the efficiency of managing network slice instances.
  • the method includes: the first network device acquiring performance information of the first network slice subnet instance after performing a rollback process, where the performance information is used to indicate the first network Slicing the performance of the subnet instance; the first network device determines, based on the performance information, whether the performance of the first network slice subnet instance meets a predetermined condition.
  • the first network device obtains performance information of the first network slice instance after the rollback process, and determines, according to the performance information, whether the performance of the first network slice subnet instance meets a predetermined condition, thereby being capable of flexibly managing Network slicing instances improve the efficiency of managing network slicing instances.
  • the method further includes: the first network device records, to the storage device, process information that performs a rollback process on the first network slice subnet instance.
  • the first network device records the process information of performing the rollback process 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.
  • the method further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; The first network device determines that the first network slice subnet instance is faulty, and the first network device determines the first network slice subnet instance according to the fault alarm information.
  • the first network device receives the fault alarm information from the second network device, and determines that the first network slice subnet instance is faulty according to the fault alarm information, thereby flexibly managing the network slice instance and improving the management network. The efficiency of the slice instance.
  • a fourth aspect provides a method for managing a network sharding instance, where the second network device receives the first indication information from the first network device, where the first indication information is used to indicate that the second network device pair is faulty.
  • the first network slice subnet instance performs a fallback process; the second network device performs a rollback process on the first network sliced subnet instance according to the first indication information.
  • the second network device receives the first indication information from the first network device, where the first indication information is used to instruct the first network device to perform a rollback process on the first network slice subnet instance, where The network device performs a fallback process on the first network slice subnet instance based on the first indication information, so that the network slice instance can be flexibly managed, and the efficiency of managing the network slice instance is improved.
  • the method before the second network device receives the first indication information from the first network device, the method further includes: the second network device sending the The current parameter information of the first network slice instance, so that the first network device backs up the current parameter information of the first network slice subnet instance to the storage device.
  • 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 backs up the current parameter information of the first network slice subnet instance to the storage.
  • Devices that provide the flexibility to manage network slicing instances and improve the efficiency of managing network slicing instances.
  • the method further includes: in a case that performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition, the second network device is from the first network The device receives the second indication information, where the second indication information is used to instruct the second network device to restore the first information based on the current parameter information that is backed up to the first network slice subnet instance in the storage device. Network slice subnet instance.
  • the second network device restores the first network slice subnet instance based on the first indication information sent by the first network device.
  • the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
  • the method further includes: the second network device sending fault alarm information to the first network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty.
  • the second network device sends fault alarm information to the first network device to indicate that the first network slice subnet instance is faulty.
  • the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
  • the method further includes: sending, by the second network device, historical parameter information of the first network slice subnet instance to the first network device, so that the first network device The historical parameter information of the first network slice subnet instance is backed up to the storage device.
  • 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 backs up the historical parameter information of the first network slice subnet instance to the storage.
  • Devices that provide the flexibility to manage network slicing instances and improve the efficiency of managing network slicing instances.
  • a network device for performing the method of any of the first aspect or the first aspect of the first aspect.
  • the network device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • the network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • the network device for performing the method in any of the possible implementations of the third aspect or the third aspect above.
  • the network device comprises means for performing the method of any of the possible implementations of the third aspect or the third aspect described above.
  • the network device for performing the method of any of the above-described fourth aspect or any of the possible implementations of the fourth aspect.
  • the network device comprises means for performing the method of any of the above-described fourth or fourth aspects of the fourth aspect.
  • the ninth aspect provides a network system, comprising the network device according to the fifth aspect, the sixth aspect, or the network device according to the seventh aspect and the eighth aspect.
  • a network device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a network device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a network device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the third aspect or the third aspect.
  • a network device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the fourth aspect or the fourth aspect.
  • the invention provides a network system, comprising the network device according to the tenth aspect, the eleventh aspect, or the network device according to the twelfth aspect and the thirteenth aspect.
  • a fifteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • a seventeenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the third aspect or any of the possible implementations of the third aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the fourth aspect or any of the possible implementations of the fourth aspect.
  • the invention provides a network system, comprising the computer readable medium of the fifteenth aspect, the computer of the sixteenth aspect, Read the media.
  • 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 still another embodiment of the present application.
  • FIG. 3 is a schematic diagram of a network management architecture according to still another embodiment of the present application.
  • FIG. 4 is a schematic diagram of a network management architecture according to still another embodiment of the present application.
  • FIG. 5 is a schematic diagram of a method for managing a network slice instance according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 7 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 8 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 9 is a schematic diagram of a method for managing a network slice instance according to still 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 still another embodiment of the present application.
  • FIG. 12 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 13 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 14 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 15 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 16 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 17 is a schematic diagram of a network device according to still another embodiment of the present application.
  • Network slice refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including a terminal, an access network, a transmission network, a core network, and an application server, and can provide telecommunication services and have certain network capabilities; the network slice can also be the above terminal and access network. Any combination of the transport network, the core network, and the application server, for example, the network slice only includes the access network and the core network.
  • a network slice may have one or more of the following characteristics: the access network may or may not slice.
  • the access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.
  • Network Slice Instance A real-world logical network that meets certain network characteristics or service requirements.
  • a network slice instance may provide one or more services.
  • a network sharding instance can be created by the network management system.
  • a network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances.
  • a network tile instance may or may not be created from a network tile template.
  • a complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slice subnet instances (NSSI) and/or network functions.
  • Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • Network slice subnet instance The network slice subnet instance does not need to provide end-to-end complete network services.
  • the network slice subnet instance can be the network function of the same device vendor in the network slice instance.
  • a collection may also be a collection of network functions divided by domain, such as a core network network sliced subnet instance, an access network network sliced subnet instance, or a collection of other methods.
  • a network sliced subnet instance may be shared by multiple network slice instances. The network slice subnet instance is proposed to facilitate network management system management.
  • a network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or several network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none It is composed of network functions that are divided into network slice subnet instances; a network slice instance may also consist of only a few network functions.
  • Network function A processing function in the network that defines functional behaviors and interfaces.
  • Network functions can be implemented through dedicated hardware, or by running software on dedicated hardware, or in general.
  • the hardware platform is implemented in the form of virtual functions. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network functions can also share the same network function, which is called shared network function.
  • Sevice management function responsible for translating the telecommunication service requirements of operators and/or third-party customers into the demand for network slicing, sending the demand for network slicing to NSMF, receiving operators and/or The three-party customer subscribes to the network slice management data (such as performance data, fault data, fault repair data, etc.), and obtains management data of the network slice from the NSMF.
  • network slice management data such as performance data, fault data, fault repair data, etc.
  • Network slice management function responsible for receiving network slice requirements sent by SvMF, managing the life cycle, performance, faults, etc. of the network slice instance (hereinafter referred to as life cycle, performance, fault management for short management)
  • the composition of the network slice instance is arranged, and the requirement of decomposing the network slice instance is the requirement of each network slice subnet instance, and the network slice subnet instance management request is sent to each NSSMF, and the network function management request is sent to the NFM.
  • Network slice subnet management function Receives the requirement of the network slice subnet instance from the NSMF to manage the life cycle, performance, faults, etc. of the network slice subnet instance (the following will be life) Cycle, performance, fault management, referred to as management), the composition of the network slice instance.
  • Network function management used to manage NF, such as managing the life cycle of NF, allocating network resources for NF, and so on.
  • Network Slice Self-Healing Monitor and Management Function (NS-SH-MMF): It includes at least one of the following functions: sending network slice self-healing algorithms and parameters to NS-SH-IF; NSS-SH-MMF information and parameters related to network slice subnet self-healing; monitor network slice instance operation and fault conditions; determine whether the network slice instance fault meets the self-healing trigger condition; send network slice to NS-SH-IF The trigger request is received; the network slice self-healing result sent by the NS-SH-IF is received; and the network slice fault data and the self-healing result are reported to the SvMF.
  • NS-SH-MMF Network Slice Self-Healing Monitor and Management Function
  • Network Slice Self-Healing Implementation Function (NS-SH-IF:): It contains at least one of the following functions: receiving network slice self-healing algorithm configuration and parameters from NS-SH-MMF; receiving NS The network slice self-healing trigger request sent by the -SH-MMF; collecting network slice running information, including but not limited to network slice instance performance data, fault alarm, configuration data, test data, etc.; determining the fault type decision fault self-repair action; Self-healing actions, including but not limited to switching faulty sub-slice instances/network functions to redundant sub-slice instances/network functions, creating new sub-slice instances/network functions instead of failed sub-slice instances/network functions, for network fragment instances that cause failures Configure, modify, rollback, etc.; back up the configuration in the existing network slicing instance; perform specific fault auto-recovery actions; evaluate the automatic fault recovery effect; determine whether it is necessary to stop the fault recovery process; NS Repository interactively records actions and failures taken
  • NSS-SH-MMF Network Slice Subnet Self-Healing Monitor and Management Function
  • NSS-SH-MMF It contains at least one of the following functions: Sending network slice subnet self-healing to NSS-SH-IF Algorithm and parameters; monitor the running condition and fault condition of the network slicing subnet instance; determine whether the network slicing subnet instance fault meets the self-healing trigger condition; send a network slice subnet self-healing trigger request to the NSS-SH-IF; receive the NSS-SH - The network slice subnet self-healing result sent by the IF; reports the network slice subnet fault data and the self-healing result to the NS-SH-MMF.
  • Network Slice Subnet Self-Healing Implementation Function (NSS-SH-IF): It includes 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 trigger request sent by the NSS-SH-MMF; collecting network slice subnet operation information, including but not limited to network slice subnet instance performance data, fault alarm, configuration data, test data, etc.; Decision fault self-repair action; perform fault self-repair action, including but not limited to switching fault sub-slice instance (nested network slice subnet instance) / network function is redundant sub-slice instance / network function, create new sub-slice instance / The network function replaces the faulty sub-slice instance (nested network slicing subnet instance)/network function, configures, modifies, and regresses the network slicing subnet instance that caused the fault; performs the configuration in the existing network slicing subnet instance.
  • Network Slice Repository It is a database in which at least one of the following is recorded: network slice instance configuration information, including network slice subnet instance configuration information, network function configuration information, and fault information. Self-repair actions and repair results, etc.
  • NS Repository can be independent of NSMF or set up on the same network device as NSMF.
  • Network Slice Subnet Repository (NSS Repository):. It is a database that records at least one of the following: network slice subnet instance configuration information, including nested network slice subnet instance configuration information, network function configuration information, fault information, self-healing actions, and repair results.
  • the NSS Repository can be independent of NSSMF or set up on the same network device as NSSMF.
  • the network management architecture 100 of FIG. 1 further includes at least one of the following interfaces:
  • Interface 1 The interface between the SvMF and the NSMF is used by the SvMF to send the service to the NSMF for network slicing.
  • the NSM feeds back the NSI and service operations to the SvMF and provides certain management data.
  • Interface 2 The interface between NSMF and NSSMF.
  • the NSMF manages and orchestrate the NSI, it passes the NSSI requirements to the NSSMF through the interface, such as creating, modifying, and obtaining management data.
  • the NSSMF feeds back NSSI to the NSMF through the interface. information.
  • Interface 3 An interface between the NSMF and the NFM, the NSMF sends a management and configuration command to the NF; the NFM receives the message from the NSMF through the interface, and feeds back information about the NF through the interface.
  • Interface 4 An interface between NSSMFs for mutual coordination between NSSMFs.
  • the NSSMF requests another NSSMF to manage the NSSIs it governs, including lifecycle management, performance management, and fault management.
  • Interface 5 Interface between NSMF and NS Repository for NSMF to record and read data in NS Repository.
  • Interface 6 The interface between NSSMF and NSS Repository for NSSMF to record and read data in the NSS Repository.
  • Interface 7 Interface between NSMF and NSS Repository for NSMF to retrieve data from the NSS Repository.
  • FIG. 1 also shows several NSI components, including: NSI is composed of several NSSIs; NSI is composed of several NSSIs, and several NFs; NSI is composed of several NFs.
  • NSSI allows nesting, that is, one NSSI contains another NSSI, both of which have their own NSSMF; assuming NSI includes NSSI 1, NSSI 1 contains NSSI 2, and NSSMF 1 and NSSMF 2 are NSSI 1 and NSSI, respectively. Manager 2, there are two options for the management of NSSI 2 at this time, Option 1 is a management request for NSI 2 sent by NSSMF 1 to NSSMF 2, this option is applicable to the scenario where interface 4 exists between NSSMF 1 and NSSMF 2. Next; option 2 is a management request for NSSI 2 to be sent directly by the NSMF to the NSSMF 2.
  • the NS Repository may be a separate entity independent of NSMF, or it may be a database internal to NSMF.
  • the NSS Repository may be a separate entity independent of NSSMF or a database internal to NSSMF. When the NSS Repository is a separate entity, it may store information for several sub-slice instances and interface 6 with several NSSMFs.
  • FIG. 2 to FIG. 4 respectively show three network management architectures of the embodiments 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.
  • the NSS_SH_IF2 of the nested NSSI is managed by the NSS_SH_MMF1 of the upper layer NSSI; the upper layer of NSS_SH_MMF1 is managed by the NS_SH_MMF.
  • FIG. 3 is a schematic structural diagram of a network management architecture 300 according to an embodiment of the present application.
  • the nested NSSI NSS_SH_IF2 can be directly managed by NSS_SH_MMF2, and NSS_SH_MMF2 receives the policy from NSS_SH_MMF1.
  • FIG. 4 is a schematic structural diagram of a network management architecture 400 according to an embodiment of the present application.
  • the NSS_SH_IF2 of the nested NSSI is managed by its own NSS_SH_MMF2; its own NSS_SH_MMF2 can be managed by NS_SH_MMF.
  • NSS_SH_MMF2 can be managed by NS_SH_MMF.
  • NSS_SH_MMF2 may be some coordination relationship between NSS_SH_MMF2 and NSS_SH_MMF1.
  • each of the foregoing functional modules may be a separate physical entity, or two or more devices may be integrated into one unit.
  • the NS_SH_MMF module and the NS_SH_IF module may be combined into one functional module, and the functional module has NS_SH_MMF. All functions of the module and the NS_SH_IF module, or the NS_SH_MMF module and the NS_SH_IF module, can be independent modules and communicate through the interface between the modules.
  • FIG. 5 is a schematic flowchart of a method 500 for managing a network slice instance according to an embodiment of the present application.
  • Method 500 can be applied to the network management architecture illustrated in Figures 1 through 4.
  • the first network device in FIG. 5 may include an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module.
  • the second network device, the third network device, and the fourth network device may include an NSSMF module.
  • the third network device to the fourth network device may respectively include a separate NSSMF module, and may also include the same NSSMF module.
  • method 500 includes:
  • the first network device determines that the first network slice subnet instance is faulty.
  • the first network device may be a module for managing and monitoring multiple network slice subnet instances.
  • the first network device can be an NSMF module.
  • the first network device is configured to manage and monitor a network slice instance, and the network slice instance includes the first network slice subnet instance.
  • the first network device determines that the first network slice subnet instance fails. For example, in one mode, the first network device may receive fault alarm information of the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty. In the second mode, the first network device may receive the trigger self-healing information of the fifth network device, where the trigger self-healing information may be sent if the first network slice subnet instance satisfies the 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.
  • the first network device sends first indication information to the second network device, where the second network device receives the first indication information.
  • the first indication information is used to indicate that the second network device activates a second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance.
  • S502 is also understood to be 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 the first network device sending a first indication to the second network device. And the first indication information is used to indicate that the second network device activates the second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance.
  • the activating the second network slice subnet instance may include notifying the second network device to start the second network slice subnet instance.
  • the user service information of the first network slice subnet instance may also be loaded into the second network slice subnet instance to facilitate recovery of the service.
  • the status of the second network slice instance in the NSS Repository and/or the NS Repository may also be marked as active.
  • the first indication information may include configuration information, where the configuration information 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, and the first network slice Interface information between the subnet instance and other NSSIs.
  • the second network device can be a module that monitors and manages network slice subnet instances.
  • the second network device can be an NSSMF module.
  • the foregoing 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 newly created by the second network device.
  • 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 newly created by the second network device.
  • the first network device when determining that the first network slice subnet instance is faulty, may instruct the second network device to activate the second network slice subnet instance to replace the first network slice subnet instance. , which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
  • the method 500 further includes: the first network device sends second indication information to the third network device, and the third network device receives the second indication information.
  • the second indication information is used to instruct the third network device to cancel the first network slice subnet instance.
  • the second indication information may be specifically used to notify the third network device to stop the service running on the first network slice subnet instance.
  • deregistering the first network slice subnet instance may further include marking a state of the first network slice subnet instance in the NSS Repository and/or the NS Repository as a logout state.
  • the method 500 further includes: the first network device sends third indication information to the fourth network device, and the fourth device receives the third indication information.
  • the third indication information is used to instruct 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 A 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 be a third network slice subnet instance that has a dependency relationship with the first network slice subnet instance.
  • the third indication information may include configuration information, where the configuration information may include application parameter change information, location change information in a network topology, interface information between second network slice subnet instances, and the like.
  • the method 500 further includes: the first network device backing up parameter information of the first network slice subnet instance to the storage device.
  • the first network device Before deregistering the first network slice subnet instance, the first network device may back up the parameter information of the first network slice subnet instance to the storage device, so as to restore the first network slice subnet instance if necessary .
  • the method 500 further includes: when the performance of the second network slice subnet instance does not meet a predetermined condition, the first network device sends fourth indication information to the third network device, where the third The 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 parameter information of the backup of the first network slice subnet instance to the storage device.
  • the method 500 further includes: the first network device acquiring performance information of the second network slice subnet instance, the performance information being used to indicate performance of the second network slice subnet instance; The first network device determines, based on the performance information, whether performance of the second network slice subnet instance meets a predetermined condition.
  • the foregoing performance information may refer to information that can reflect performance of the second network slice subnet instance.
  • the first network device may acquire performance information of the second network slice subnet instance from the second network device.
  • the first network device may obtain, from the third network device, performance information of the 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 second The performance of a network sliced subnet instance.
  • the performance information may include performance measurement information, threshold monitoring information, and the like.
  • the method 500 further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; Determining, by the network device, that the first network slice subnet instance is faulty comprises: determining, by the first network device, the first network slice subnet instance according to the fault alarm information.
  • the method 500 further includes: the first network device records, by using the second network slice subnet instance, process information of the first network slice subnet instance to a storage device.
  • FIG. 6 shows a schematic flowchart of a method 600 for managing a network slice instance according to an embodiment of the present application.
  • Method 600 can be used in any of the network management architectures of Figures 1-4.
  • Figure 6 shows a network slice management process for switching a failed NSSI to a redundant NSSI.
  • the first network device in the method 500 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module.
  • the second network device in method 600 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 the same NSSMF module.
  • the method 600 includes:
  • the configured content includes the identity of the NSI, the fault repair requirement of the NSI, the identity of the redundant NSSI allocated and/or created when the NSI is created, and redundancy.
  • the mapping relationship between the NSSI and the NSSI constituting the NSI, the triggering rules for switching to the redundant NSSI include an event, a fault type, and a condition. It should be noted that there may not be a one-to-one correspondence between the redundant NSSI and the NSSI constituting the NSI.
  • the redundant NSSI may be replaced by redundancy of any one of several NSSIs, and one redundant NSSI may be used as a number of Redundant replacement of several NSSIs of the same type in the NSI.
  • NSSI that constitutes an NSI fails, which affects the normal operation of the NSI.
  • NSSMF 1 fails, it is managed by NSSMF 1.
  • the NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2.
  • the NS-SH-MMF receives a fault alarm from NSSMF 1.
  • the fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
  • S603 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF.
  • the NS-SH-IF receives a self-healing trigger command.
  • the S604 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following items: a) the NS-SH-IF sends the performance measurement task to the NSSMF 1 through the interface 2, and the threshold measurement is performed.
  • the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the other network slice subnet instance in which the NS-SH-IF interacts with the NSSI 1 (the embodiment of the present application assumes the NSSI) 3, management function managed by NSSMF 3, that is, NSSMF 3 transmits performance measurement tasks and threshold measurement tasks, and NS-SH-IF receives performance data and threshold measurement results reported by NSSMF 3 through interface 2; c) NS-SH-IF
  • the redundancy NSSI corresponding to the faulty NSSI is found according to the self-healing configuration, and the current state is read from the NS Repository through the interface 5 (the possible states include logout, activation, termination, unusability, etc.), and the embodiment of the present application assumes NSSI 1
  • the redundant network slice sub-network instance is NSSI 2
  • NSSI 2 is managed by NSSMF 2
  • d) NS-SH-IF sends test tasks to
  • the NS-SH-IF backs up the related configuration information, the logical topology location, the user service information, and the like of the NSSI 1 to the NS Repository through the interface 5, so as to be restored when the fault self-healing fails.
  • NSSI 1 If the current state of NSSI 1 is an active state, the NS-SH-IF logs out NSSI 1. Logging out includes marking the status of NSSI 1 in the NSS Repository and/or NS Repository as a logout state, informing NSSMF 1 to stop the service running on NSSI 1.
  • the NS-SH-IF sends a command for configuring the NSSI 2 to the NSSMF 2 through the interface 2.
  • the configuration message includes at least an application parameter, a location in the network topology, and interface information between the other NSSIs.
  • the configuration content here may be consistent with the configuration when the NSSI 1 collected by the NS-SH-IF in step S604 is correctly operated, or may be different.
  • the redundant network tiling subnet instance may be specific to an NSSI. In this case, when the redundant NSSI is created, it is configured accordingly, and the corresponding NSSI configuration is modified.
  • the NSMF also informs the manager of the redundant NSSI to modify the configuration accordingly to provide the switching speed when transmitting the fault, and to ensure high reliability.
  • step S607 may not be necessary.
  • the redundant NSSI can replace several NSSIs, the NSSIs may belong to the same NSI or may belong to different NSIs. In this case, the redundant NSSIs are not configured before the self-healing mechanism is triggered. In this case, step S607 is The necessary steps.
  • the NS-SH-IF sends a command for configuring the NSSI 3 to the NSSMF 3 through the interface 2, and associates the NSSI 3 with the NSSI 2.
  • the configuration message includes at least one of the following: the application parameter change, the location change in the network topology, Interface information between NSSI 2 and so on.
  • NS-SH-IF activates NSSI 2.
  • Activation includes marking the status of NSSI 2 in the NSS Repository and/or NS Repository as an active state, notifying NSSMF 2 to initiate NSSI 2 and loading the user service information on NSSI 1 obtained in step S604 to resume the service.
  • NS-SH-IF collects information of the network slice instance and evaluates the self-healing result.
  • the information collected includes at least one of the following items: NS-SH-IF delivers performance measurement and threshold monitoring tasks for NSSI 2 and NSSI 3 to NSSMF 2 and NSSMF 3 through interface 2, and performs performance measurement and thresholds for NSSMF 2 and NSSMF 3 respectively. Monitor the task and report it to the NS-SH-IF performance measurement result and/or exceed the threshold alarm through interface 2.
  • step S611 If any step of step S606 to step S609 fails, or the information collected by the NS-SH-IF in step S610 indicates that the network slice service cannot be operated normally after switching the redundant NSSI, the recovery action is triggered. Specifically, the NS-SH-IF reads the network state and configuration before the self-healing action held in step S605, configures NSSI 3 and NSSI 1, and activates NSSI 1.
  • S612 and NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions in steps S606 to S611, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
  • S613 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF.
  • the NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
  • the network slice subnet instance constituting the network slice instance when the network slice subnet instance constituting the network slice instance fails, it can automatically switch to the redundant network slice subnet instance without manual intervention, and ensure the continuity and consistency of the service as much as possible. , improve the overall reliability of the network slice instance.
  • the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error.
  • the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly.
  • the method for managing a network slice in the embodiment of the present application may be applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and may be used when a network slice subnet instance fails to self-heal. Self-healing mechanism at the network slice level.
  • the processes and methods involved in the embodiments of the present application are also applicable to an application scenario in which a network sharding instance is composed of network functions, and when a network function fails to be self-healing, a faulty network function may be switched to a redundant network.
  • the self-healing mechanism of the function, the process and the step of switching to the self-healing mechanism of the redundant network function are similar to the process steps in the embodiment of the present application, and the information of the network slice subnet instance is replaced with the corresponding information in the interaction information between the modules.
  • the information about the network function can be.
  • NSSI 1, NSSI 2, NSSI 3, and NSSMF 1, NSSMF 2, and NSSMF 3 used in the embodiments of the present application are only for the purpose of illustration.
  • the method of the present application does not limit the faulty network slice subnet instance. Number, the number of network slicing subnet instances that interact with the failed network slicing subnet instance, and the number of redundant network slicing subnet instances. For example, a failed network slice subnet instance may need to be replaced by several redundant network slice subnet instances.
  • the faulty NSSI, the redundant NSSI, and the other NSSIs in the presence of the 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. 7 shows a schematic flowchart of a method 700 for managing a network slice instance according to an embodiment of the present application.
  • Method 700 can be used in any of the network management architectures of Figures 1-4.
  • Figure 7 shows a network slice management process that will automatically create a new NSSI to replace the failed NSSI.
  • the first network device in the method 500 may include an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module.
  • the second network device in method 500 can include an NSSMF2 module, the third network device can include an NSSMF1 module, and the fourth network device can include an NSSMF3 module.
  • the third network device to the fourth network device may be separate NSSMF modules or the same NSSMF module.
  • the method 700 includes:
  • S701 and NS-SH-MMF configure the self-healing algorithm that NS-SH-IF needs to perform.
  • the configuration includes the identity of the NSI, the fault repair requirement of the NSI, the new NSSI can be created to replace the identity of the NSSMF of the faulty NSSI, and the feasible creation is feasible.
  • the trigger rules for creating a new NSSI to replace the faulty NSSI include events, fault types and conditions.
  • NS-SH-MMF may update the configuration of the self-healing algorithm of NS-SH-IF at any time as network conditions change, such as changes in network resource usage.
  • NSSI that constitutes an NSI fails, affecting the normal operation of the network slice instance.
  • NSSMF 1 fails, it is managed by NSSMF 1.
  • the NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2.
  • the NS-SH-MMF receives a fault alarm from NSSMF 1.
  • the fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
  • S703 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF.
  • the NS-SH-IF receives a self-healing trigger command.
  • the S704 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following contents: a) the NS-SH-IF sends the performance measurement task to the NSSMF 1 through the interface 2, and the threshold measurement is performed.
  • the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the other network slice subnet instance in which the NS-SH-IF interacts with the NSSI 1 (the embodiment of the present application assumes the NSSI) 3, management function managed by NSSMF 3, that is, NSSMF 3 transmits performance measurement tasks and threshold measurement tasks, and NS-SH-IF receives performance data and threshold measurement results reported by NSSMF 3 through interface 2; c) NS-SH-IF According to the self-healing configuration, a corresponding management module that can create a new NSSI instead of a faulty NSSI is found.
  • the embodiment of the present application assumes that it is an NSSMF 3, and the NS-SH-IF sends a feasibility check request for creating a new NSSI to the NSSMF 3 through the interface 2; d) The NS-SH-IF reads the configuration information of the NSSI 1 during normal operation from the NS Repository through the interface 5, including the SLA, the location and interface information in the logical topology of the network slice instance; e) the NS-SH-IF through the interface 2 Get NSSI 1 from NSSMF 1 Running service information, including user data, configuration, etc.; f) NS-SH-IF reads the historical fault information of NSSI 1 from NS Repository through interface 5, takes the repair action, repairs the result, and reads with NSSI 1 Type of other network slicing subnet instance for fault information, taking repair actions, repairing results, etc. 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 faulty
  • the NS-SH-IF backs up the related configuration information, the logical topology location, the user service information, and the like of the NSSI 1 to the NS Repository through the interface 5, so as to be restored when the fault self-healing fails.
  • the NS-SH-IF sends an NSSI request to the NSSMF 2 through the interface 2.
  • the creation request includes at least the type of the newly created NSSI, the functions included, the SLA to be satisfied, and the network resources occupied.
  • NSSMF 2 creates NSSI 2 based on the received request.
  • the NS-SH-IF sends a command to configure the NSSI 2 to the NSSMF 2 through the interface 2.
  • the configuration message includes at least an application parameter, a location in the network topology, and interface information between other NSSIs. It should be noted that the configuration content here may be consistent with the configuration when the NSSI 1 collected by the NS-SH-IF in step S704 is correctly operated, or may be different due to the implementation of the network slice subnet instance.
  • NSSI 1 If the current state of NSSI 1 is an active state, the NS-SH-IF logs out NSSI 1. Logging out includes marking the status of NSSI 1 in the NSS Repository and/or NS Repository as a logout state, informing NSSMF 1 to stop the service running on NSSI 1.
  • the NS-SH-IF sends a command to configure the NSSI 3 to the NSSMF 3 through the interface 2, and associates the NSSI 3 with the NSSI 2.
  • the configuration message includes at least one of the following: the application parameter change, the location change in the network topology, Interface information between NSSI 2 and so on.
  • NS-SH-IF activates NSSI 2.
  • Activation includes marking the status of NSSI 2 in the NSS Repository and/or NS Repository as an active state, notifying NSSMF 2 to initiate NSSI 2 and loading the user service information on NSSI 1 obtained in step S704 to resume the service.
  • S711 and NS-SH-IF collect information of network slice instances and evaluate self-healing results.
  • the information collected includes at least one of the following items: NS-SH-IF delivers performance measurement and threshold monitoring tasks for NSSI 2 and NSSI 3 to NSSMF 2 and NSSMF 3 through interface 2, and performs performance measurement and thresholds for NSSMF 2 and NSSMF 3 respectively. Monitor the task and report it to the NS-SH-IF performance measurement result and/or exceed the threshold alarm through interface 2.
  • step S706 to step S710 fails, or the information collected by the NS-SH-IF in step S711 indicates that the newly created NSSI 2 cannot replace the faulty NSSI 1 for normal operation, the recovery action is triggered.
  • the NS-SH-IF reads the network state and configuration before the self-healing action stored in step S705, and reconfigures NSSI 3 and NSSI 1, and activates NSSI 1.
  • S713 and NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions of steps S706 to S712, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
  • S714 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF.
  • the NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
  • a new network slice subnet instance can be automatically created instead of the manual network slice subnet instance to restore the service without manual intervention. Ensure the consistency and consistency of the service, and improve the overall reliability of the network slice instance.
  • the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error.
  • the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly.
  • the embodiment of the present application is applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and a network slice level self-healing may be adopted when a network sliced subnet instance fails to self-heal. mechanism.
  • the processes and methods involved in the embodiments of the present application are also applicable to an application scenario in which a network segmentation instance is composed of network functions, and when a network function fails to be self-healing, a new network function may be adopted and the faulty network function may be replaced.
  • the self-healing mechanism, the process and the steps of creating a self-healing mechanism of the new network function are similar to the process steps in the embodiment of the present application, and the information of the network slice subnet instance is replaced with the corresponding network function in the interaction information between the modules. Information can be.
  • the NSSI 1, NSSI 2, NSSI 3, and NSSMF 1, NSSMF 2, and NSSMF 3 used in the embodiments of the present application are only for the purpose of illustration.
  • the method of the present application does not limit the number of faulty network slice subnet instances. Number of network slicing subnet instances that interact with the failed network slicing subnet instance, and the number of newly created network slicing subnet instances. For example, a failed network slice subnet instance might need to create several network slice subnet instances instead.
  • the faulty NSSI, the new NSSI, and other NSSIs that have interactions 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 flowchart of a method 800 for managing a network slice instance according to an embodiment of the present application.
  • Method 800 can be applied to the network management architecture illustrated in Figures 1-4.
  • the first network device in FIG. 8 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module.
  • the second network device can be an NSSMF module.
  • the storage device can be an NS Repository.
  • method 800 includes:
  • the first network device determines that the first network slice subnet instance is faulty.
  • the first network device may be a module for managing and monitoring multiple network slice subnet instances.
  • the first network device can be an NSMF module.
  • the first network device is configured to manage and monitor a network slice instance, and the network slice instance includes the first network slice subnet instance.
  • the first network device determines that the first network slice subnet instance fails. For example, in one mode, the first network device may receive fault alarm information of the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty. In the second mode, the first network device may receive the trigger self-healing information of the fifth network device, where the trigger self-healing information may be sent if the first network slice subnet instance satisfies the 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.
  • the first network device sends the first indication information to the second network device, where the first indication information is used to instruct the second network device to perform a rollback process on the first network slice subnet instance.
  • the foregoing backoff process may be understood as resetting a configuration parameter of the first network slice subnet instance to a configuration parameter at a certain moment before the current time.
  • the configuration parameter at a certain moment before the current moment may be a historical configuration parameter.
  • the first network device when determining that the first network slice subnet instance is faulty, may instruct the second network device to perform a rollback process on the first network sliced subnet instance, thereby being flexible.
  • Manage network segmentation instances to improve the efficiency of managing network slice instances.
  • the method 800 further includes: the first network device acquiring historical parameter information of the first network slice subnet instance; the first network device is based on historical parameter information of the first network slice subnet instance Determining the first indication information.
  • the first network device may further acquire historical parameter information of the network slice instance described by the first network slice subnet instance.
  • the historical parameter information may include information about an associated network slice instance and a network sliced subnet instance, including at least one of the following:
  • the NS-SH-IF sends the performance measurement task and the threshold measurement task to the NSSMF 1 through the interface 2, and the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2;
  • NS-SH-IF finds a corresponding management module that can create a new NSSI instead of a faulty NSSI according to the self-healing configuration.
  • the embodiment of the present application assumes that it is NSSMF 3, and the NS-SH-IF sends a new NSSI to the NSSMF 3 through the interface 2.
  • the NS-SH-IF reads the configuration information of the NSSI 1 during normal operation, including the SLA, the location and interface information in the logical topology of the network slice instance, from the NS Repository through the interface 5;
  • the NS-SH-IF obtains the service information running on the NSSI 1 from the NSSMF 1 through the interface 2, including user data, configuration, and the like;
  • NS-SH-IF reads the historical fault information of NSSI 1 from the NS Repository through interface 5, takes the repair action, repairs the result, and reads the fault information of other network slice subnet instances of the same type as NSSI 1 Repair actions, fix results, etc.
  • the method 800 further includes: the first network device acquiring historical parameter information of the first network slice subnet instance from the second network device; the first network device slices the first network The historical parameter information of the subnet instance is backed up to the storage device; the first network device acquiring the historical parameter information of the first network slice subnet instance, the first network device acquiring the first Historical parameter information of a network sliced subnet instance.
  • the method 800 further includes: before the first network device sends the first indication information to the second network device, the first network device acquires current parameter information of the first network slice subnet instance; The first network device backs up current parameter information of the first network slice subnet instance to the storage device.
  • the method 800 further includes: sending, by the first network device, the second network device to the second network device, if the performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition
  • the second indication information is used to instruct the second network device to restore the first network slice based on the current parameter information backed up to the first network slice subnet instance in the storage device. Network instance.
  • the method 800 further includes: the first network device acquiring performance information of the first network slice subnet instance after performing the rollback process, where the performance information is used to indicate the first network slice subnet Performance of the instance; the first network device determines, based on the performance information, whether performance of the first network slice subnet instance meets a predetermined condition.
  • the method 800 further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; Determining, by the network device, that the first network slice subnet instance is faulty comprises: determining, by the first network device, the first network slice subnet instance according to the fault alarm information.
  • FIG. 9 shows a schematic flowchart of a method 600 of managing a network slice instance in an embodiment of the present application.
  • Method 900 can be used in any of the network management architectures of Figures 1-4.
  • Figure 9 shows a network slice management process for replacing a newly created NSSI with a failed NSSI.
  • the first network device in the method 800 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module.
  • the second network device can be an NSSMF module.
  • the storage device can be an NS Repository.
  • the method 900 includes:
  • the configuration includes the NSI identity, the NSI fault repair requirement, the configuration and status of the network slice instance and the network slice subnet instance.
  • the backup requirements such as the backup time period, whether to overwrite the original backup, etc., trigger rules for network slice instance modification and configuration rollback include events, fault types, and conditions.
  • the NS-SH-MMF may update the configuration of the NS-SH-IF self-healing algorithm at any time.
  • S902 and NS-SH-IF determine whether it is necessary to create or update a backup of the network slice instance information according to the configured self-healing algorithm.
  • the conditions that trigger a backup may include time, events, events that are expected to occur, and so on. (Events refer to modifications, configurations, user behavior changes, etc. to network slice instances.)
  • S903 and NS-SH-IF determine information backup of the network slice instance, and obtain NSSI information from the NSSMF through interface 2.
  • the information may include the current NSSI configuration, its location in the network topology, and other NSSIs. Interface information, SLA, performance data, etc.
  • the NS-SH-IF reads the saved NSSI information from the NS Repository and determines which information needs to be updated.
  • NS-SH-IF records and/or updates information of each NSSI constituting the NSI in the NS Repository through the interface 5.
  • NSSI that constitutes an NSI fails, affecting the normal operation of the network slicing instance.
  • NSSMF 1 fails, it is managed by NSSMF 1.
  • the NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2.
  • the NS-SH-MMF receives a fault alarm from NSSMF 1.
  • the fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
  • S906 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF.
  • the NS-SH-IF receives a self-healing trigger command.
  • the S907 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following contents: a) The NS-SH-IF sends the performance measurement task and the threshold measurement to the NSSMF 1 through the interface 2.
  • the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the NS-SH-IF sends a performance measurement task to the management function of the other network slice subnet instance that interacts with the NSSI 1 The threshold measurement task, the NS-SH-IF receives the reported performance data and the threshold measurement result through the interface 2; c) the NS-SH-IF reads the backup information of the NSSI 1 during normal operation, including the SLA, from the NS Repository through the interface 5. Location, interface information, etc.
  • NS-SH-IF reads the historical fault information of NSSI 1 from the NS Repository through interface 5, the repair action taken, the repair result, the read and the NSSI 1 The fault information of other network slicing subnet instances of the same type, the repair action taken, 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 on the NSSI 1 and decides which time point of the backup information to perform the rollback.
  • the NS-SH-IF backs up the NSI 1 related configuration information, the logical topology location, the user service information, and the like to the NS Repository through the interface 5, so as to recover when the fault self-healing fails.
  • the rollback command may include: a) canceling and terminating the newly created NSSI 1, the command needs to include the identity of the NSSI 1, and b) reconfiguring the NSSI according to the NSSI configuration backup information obtained in step 7). 1; c) Restoring changes to NSSI 1, including reducing the expanded capacity, expanding the reduced capacity, adding deleted network functions, and deleting new network functions.
  • the backoff command may not be sent to the NSSMF 1, but other NSSMFs, and the command needs to include the NSSI identity, configuration information, SLA, interface information, and the like.
  • the NS-SH-IF also needs to send a configuration message to the manager of other NSSIs that interact with the NSSI.
  • NSSMF 1 (or other NSSMF) perform the corresponding action and feed back the execution result to the NS-SH-IF.
  • NS-SH-IF collects information on network slice instances and evaluates self-healing results.
  • the information collected includes at least one of the following items: the NS-SH-IF sends performance measurement and threshold monitoring tasks to the NSSMF 1 and/or other NSSMFs through the interface 2, and the corresponding NSSMF performs performance measurement and threshold monitoring tasks, and reports them to the interface 2 through the interface 2 NS-SH-IF performance measurement results and / or alarms exceeding the threshold.
  • the NS-SH-IF initiates the modification caused by the recovery backoff action. Specifically, the NS-SH-IF reads the network state and configuration before the self-healing action stored in step S908, and accordingly notifies the NSSMF 1 to reconfigure the NSSI 1 and/or restore the modification to the NSSI 1.
  • the S913 and the NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions in steps S908 to S912, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
  • S914 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF.
  • the NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
  • the method for managing a network slice and the network management architecture of the embodiment of the present application are described in detail above with reference to FIG. 1 to FIG. 9.
  • the network device of the embodiment of the present application will be described in detail below with reference to FIG. 10 to FIG.
  • 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 various steps performed by the first network device in the methods of FIGS. 5-7, which are not 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 the first network slice subnet instance is faulty, and send the first indication information to the second network device by using the communication unit 1002, where the first indication information is used to indicate the second network device Performing a fallback process on 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 can perform the various steps performed by the second network device in the methods of FIGS. 5-7, which are not 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 the first indication information from the first network device by using the communication unit 1102, where the first indication information is used to instruct the second network device to activate the second network slice subnet instance, where The second network slice subnet instance is configured to replace the first network slice subnet instance; and the second network slice subnet instance is activated 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 the network device 1200 can perform the various steps performed by the first network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein.
  • the network device 1200 includes: a processing unit 1201 and a communication unit 1202,
  • the processing unit 1201 is configured to determine that the first network slice subnet instance is faulty, and send the first indication information to the second network device by using the communication unit 1202, where the first indication information is used to indicate the second network device Performing a fallback process 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 can perform the various steps performed by the second network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein.
  • the network device 1300 includes: a processing unit 1301 and a communication unit 1302,
  • the processing unit 1301 is configured to receive first indication information from the first network device by using the communication unit 1302, where the first indication information is used to instruct the second network device to perform back on the failed first network slice subnet instance. And performing a rollback process 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 can perform the various steps performed by the first network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition.
  • Network device 1400 includes:
  • a memory 1410 configured to store a program
  • a communication interface 1420 configured to communicate with other devices
  • the processor 1430 is configured to execute a program in the memory 1410, when the program is executed, the processor 1430 is configured to determine that the first network slice subnet instance is faulty; to the second network device by using the communication interface 1420 Sending the first indication information, where the first indication information is used to indicate that the second network device activates the second network slice subnet instance, where 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 according to an embodiment of the present application. It should be understood that the network device 1500 can perform the various steps performed by the second network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition.
  • Network device 1500 includes:
  • a memory 1510 configured to store a program
  • a communication interface 1520 configured to communicate with other devices
  • the processor 1530 is configured to execute a program in the memory 1510, when the program is executed, the processor 1530 is configured to receive, by using the communication interface 1520, first indication information from a first network device, where the first indication is The information is used to indicate that the second network device activates the second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance; and activated according to the first indication information The second network slices a subnet instance.
  • FIG. 16 is a schematic block diagram of a network device 1600 according to an embodiment of the present application. It should be understood that the network device 1600 can perform the various steps performed by the first network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein.
  • Network device 1600 includes:
  • a memory 1610 configured to store a program
  • a communication interface 1620 configured to communicate with other devices
  • the processor 1630 is configured to execute a program in the memory 1610, where the processor 1630 is configured to determine that the first network slice subnet instance is faulty; to the second network device by using the communication interface 1620. Sending the first indication information, where the first indication information is used to instruct the second network device to perform a rollback process 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 the network device 1700 can perform the various steps performed by the second network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein.
  • Network device 1700 includes:
  • a memory 1710 configured to store a program
  • a communication interface 1720 configured to communicate with other devices
  • the processor 1730 is configured to execute a program in the memory 1710, when the program is executed, the processor 1730 is configured to receive first indication information from the first network device by using the communication interface 1720, the first indication The information is used to instruct the second network device to perform a fallback process on the failed first network slice subnet instance; and perform a rollback process on the first network slice subnet instance according to the first indication information.
  • the configuration and modification of the network slice instance failure may be automatically rolled back without manual intervention, and the fault is repaired instantaneously to ensure the continuity and consistency of the service. Sexuality improves the overall reliability of network slicing instances.
  • the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error.
  • the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly. Avoid the same configuration and modification of network slice instances in the future, resulting in the same error.
  • the embodiment of the present application is applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and a network slice level self-healing may be adopted when a network sliced subnet instance fails to self-heal. mechanism.
  • the process and method in the embodiment of the present application are also applicable to a self-healing mechanism for performing a rollback repair failure when an application scenario in which a network segmentation instance is composed of a network function is used to solve a failure in which the network function cannot be self-healing.
  • the process and the steps of the self-healing mechanism of the network function are similar to the process steps in the embodiment of the present application.
  • the information of the network slice subnet instance is replaced with the information of the corresponding network function in the interaction information between the modules.
  • the NSSI 1 and the NSSMF 1 used in the embodiments of the present application are only for the purpose of illustration.
  • 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 to be rolled back. .
  • Figures 2 through 4 illustrate three possible network management architectures when a network sliced subnet instance is nested with a network sliced subnet instance. A method of managing a network slice instance of the embodiment of the present application in the three network management architectures is described below.
  • the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module
  • the NSSMF 2 includes only the NSS-SH-IF 2 module.
  • the self-healing algorithm, configuration, parameters, etc. in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 1 through the interface 4, ie, steps S601, S701 and S901 in the method 600, the method 700 and the method 900
  • the transmitting end is NSS-SH-MMF 1
  • the receiving end is NSS-SH-IF 2
  • the content of the configuration is the self-healing algorithm of NSSI 2;
  • NSSI 2 fails. After the fault alarm is generated, the fault alarm is transmitted to the NSS-SH-MMF through the interface 4, that is, corresponding to the method 600, the method 700, the step S602, S702, the method 900, the step S905, the NSSMF 2 The fault alarm is reported to the NSS-SH-MMF 1;
  • the NSS-SH-MMF 1 determines whether the NSSI 2 meets 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, the corresponding method 600, steps S603 and S703 of the method 700, Step S906 in method 900;
  • the self-healing result is reported to the NSS-SH-MMF 1 through the interface 4, that is, corresponding to the step S613 of the method 600, the method 700, the steps S714 and S914 of the method 900 ;
  • the NSS-SH-MMF 1 reports the fault information and/or the self-healing result to the NS-SH-MMF.
  • the NS-SH-MMF can configure the reporting of the self-healing result in the NSS-SH-MMF 1 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -IF 1, self-healing configuration of NSS-SH-IF 2, etc.
  • the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module
  • the NSSMF 2 includes the NSS-SH-MMF 2 module and the NSS-SH-IF 2 module.
  • the self-healing algorithm, configuration, parameters, and the like in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 2, that is, the transmitting ends of the steps S601, S701, and S901 of the method 600, the method 700, and the method 900 are NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the content of the configuration is the self-healing algorithm of NSSI 2;
  • the generated fault alarm is reported to the NSS-SH-MMF 2, that is, the network fault in the NSSI 2 is monitored by the NSS-SH-MMF 2, corresponding to the steps of the method 600 and the method 700.
  • S602, S702, step S905 in the method 900 it should be noted that the network function constituting the NSSI 2 may be directly managed by the NSSMF 2, and may also be managed by the NFM, which is not limited in this application;
  • the NSS-SH-IF 2 performs the self-healing action, and reports the self-healing result to the NSS-SH-MMF 2, that is, corresponding to the step S613 of the method 600, the method 700, the steps S714 and S914 of the method 900;
  • the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSSMF 1.
  • the NSSMF 1 reports the fault information and/or the self-healing result to the NSMF.
  • the NS-SH-MMF can configure the reporting of the self-healing result in the NSS-SH-MMF 1 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -IF 1, self-healing configuration of NSS-SH-MMF 2, etc.
  • the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module
  • the NSSMF 2 includes the NSS-SH-MMF 2 module and the NSS-SH-IF 2 module.
  • the self-healing algorithm, configuration, parameters, and the like in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 2, that is, the transmitting ends of steps S601, S701, and S901 in the method 600, the method 700, and the method 900. It is NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the content of the configuration is the self-healing algorithm of NSSI 2;
  • Step S602, S702, step S905 in the method 900 it should be noted that the network function constituting the NSSI 2 may be directly managed by the NSSMF 2, and may also be managed by the NFM, which is not limited in this application;
  • NSS-SH-MMF 2 It is determined by the NSS-SH-MMF 2 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, the corresponding method 600, the method 700, the method S603, S703, the method 900 Step S906;
  • the self-healing result is reported to the NSS-SH-MMF 2, that is, corresponding to the step S613 corresponding to the method 600, the method 700, the step S714 of the method 900, S914;
  • the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSMF.
  • the NSS-SH-MMF 2 can also report the fault information and/or the self-healing result to the NSF-SH-MMF 2 NSSMF 1.
  • the NS-SH-MMF can configure the reporting of the self-healing result in the NSS-SH-MMF 2 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -MMF 2 self-healing configuration, etc.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.

Abstract

The present application provides a method and system for managing a network slice instance, and a network device, capable of improving the management efficiency of network slice instances. The method comprises: a first network device determines that a fault occurs to a first network slice subnet instance; the first network device sends first indication information to a second network device, the first indication information being used for indicating the second network device to activate a second network slice subnet instance, wherein 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
本申请要求于2017年03月20日提交中国专利局、申请号为201710167783.6、发明名称为“管理网络切片实例的方法、网络设备和***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。The present application claims priority to Chinese Patent Application No. 200910167783.6, entitled "Methods for Managing Network Slice Examples, Network Devices and Systems", filed on March 20, 2017, the entire contents of which are incorporated by reference. In this application.
技术领域Technical field
本申请涉及通信领域，并且更具体地，涉及管理网络切片实例的方法、网络设备和***。The present application relates to the field of communications and, more particularly, to methods, network devices and systems for managing network slice instances.
背景技术Background technique
随着移动通信的高速发展，未来的移动通信***需要满足多样化的业务需求，例如，增强型移动宽带，大规模机器类通信、超高可靠与低延迟的通信等。因此在下一代移动通信***中提出了网络切片的概念。网络切片技术是指将网络在逻辑上抽象为一个或者多个网络切片，其中每个网络切片包含一系列的逻辑网络功能，一个网络切片可以满足某一类或一个用例的连接通信服务需求。下一代移动通信***可以由满足不同连接能力的大量网络切片组成。With the rapid development of mobile communications, future mobile communication systems need to meet diverse business needs, such as enhanced mobile broadband, large-scale machine-like communications, ultra-reliable and low-latency communications. Therefore, the concept of network slicing is proposed in the next generation mobile communication system. Network slicing technology refers to the logical abstraction of a network into one or more network slices, where each network slice contains a series of logical network functions, and a network slice can satisfy the connection communication service requirements of a certain class or a use case. The next generation mobile communication system can be composed of a large number of network slices that satisfy different connection capabilities.
在通信网络中，当网元发生故障时，可由故障网元的自检电路发现故障，或性能、阈值测量任务发现故障。但这种自愈***仅能对单个网络功能的故障进行自愈管理，不能满足网络切片层面灵活的故障管理需求。In the communication network, when the network element fails, the fault can be found by the self-test circuit of the faulty network element, or the performance and threshold measurement tasks find the fault. However, this self-healing system can only manage the failure of a single network function, and cannot meet the flexible fault management requirements of the network slicing level.
发明内容Summary of the invention
本申请提供一种管理网络切片实例的方法、装置和***，能够提高管理网络切片实例的效率。The present application provides a method, apparatus, and system for managing network slice instances, which can improve the efficiency of managing network slice instances.
第一方面，提供了一种管理网络切片实例的方法，包括：第一网络设备确定第一网络切片子网实例出现故障；所述第一网络设备向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。The first aspect provides a method for managing a network sharding instance, including: determining, by a first network device, that a first network tiling subnet instance is faulty; and the first network device sending, by using the first network device, first indication information, where The first indication information is used to indicate that the second network device activates the second network slice subnet instance, wherein the second network slice subnet instance is used to replace the first network slice subnet instance.
在本申请实施例中，第一网络设备在确定第一网络切片子网实例出现故障的情况下，可以指示第二网络设备激活第二网络切片子网实例，以替换第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device, when determining that the first network slice subnet instance is faulty, may instruct the second network device to activate the second network slice subnet instance to replace the first network slice subnet instance. , which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
在一种可能的实现方式中，还包括：所述第一网络设备向第三网络设备发送第二指示信息，所述第二指示信息用于指示所述第三网络设备注销所述第一网络切片子网实例。In a possible implementation, the method further includes: the first network device sends second indication information to the third network device, where the second indication information is used to instruct the third network device to log off the first network Slice a subnet instance.
在本申请实施例中，第一网络设备向第三网络设备发送第二指示信息，以指示所述第三网络设备注销出现故障的第一网络切片子网实例，以便于第二网络切片子网实例替换第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效 率。In the embodiment of the present application, the first network device sends the second indication information to the third network device, to instruct the third network device to cancel the failed first network slice subnet instance, so as to facilitate the second network slice subnet. The instance replaces 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 a possible implementation, the method further includes: the first network device sends third indication information to the fourth network device, where the third indication information is used to indicate the fourth network device reconfiguration and the first A third network slice subnet instance associated with a network slice subnet instance, the reconfigured third network slice subnet instance being associated with the second network slice subnet instance.
在本申请实施例中，第一网络设备指示第四网络设备重配置与所述第一网络切片子网实例相关联的第三网络切片子网实例，以使第一网络切片子网实例和第三网络切片子网实例协作提供服务，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In this embodiment, 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 first The three network slicing subnet instances cooperate to provide services, which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
在一种可能的实现方式中，在所述向第二网络设备发送第二指示信息之前，所述方法还包括：所述第一网络设备将所述第一网络切片子网实例的参数信息备份至存储设备。In a possible implementation, before the sending the second indication information to the second network device, the method further includes: the first network device backing up parameter information of the first network slice subnet instance To the storage device.
在本申请实施例中，第一网络设备将第一网络切片子网实例的参数信息备份至存储设备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present 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 a possible implementation, the method further includes: sending, by the first network device, fourth indication information to the third network device, if the performance of the second network slice subnet instance does not meet the predetermined condition, where The fourth indication information is used to instruct the third network device to restore the first network slice subnet instance based on parameter information of the backup of the first network slice subnet instance to the storage device.
在本申请实施例中，第一网络设备指示第三网络设备基于第一网络切片子网实例的备份至存储设备中的参数信息，复原第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device instructs the third network device to restore the first network slice subnet instance based on the parameter information in the backup of the first network slice subnet instance to the storage device, so that the network slice can be flexibly managed. An example that improves the efficiency of managing network tile instances.
在一种可能的实现方式中，还包括：所述第一网络设备获取所述第二网络切片子网实例的性能信息，所述性能信息用于指示所述第二网络切片子网实例的性能；所述第一网络设备基于所述性能信息，确定所述第二网络切片子网实例的性能是否符合预定条件。In a possible implementation, the method further includes: the first network device acquiring performance information of the second network slice subnet instance, where the performance information is used to indicate performance of the second network slice subnet instance And determining, by the first network device, whether performance of the second network slice subnet instance meets a predetermined condition based on the performance information.
在本申请实施例中，第一网络设备指示第三网络设备基于第一网络切片子网实例的备份至存储设备中的参数信息，复原第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device instructs the third network device to restore the first network slice subnet instance based on the parameter information in the backup of the first network slice subnet instance to the storage device, so that the network slice can be flexibly managed. An example that improves the efficiency of managing network tile instances.
在一种可能的实现方式中，还包括：所述第一网络设备从所述第二网络设备接收故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障；所述第一网络设备确定第一网络切片子网实例出现故障，包括：所述第一网络设备根据所述故障报警信息确定所述第一网络切片子网实例。In a possible implementation, the method further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; The first network device determines that the first network slice subnet instance is faulty, and the first network device determines the first network slice subnet instance according to the fault alarm information.
在本申请实施例中，第一网络设备从第二网络设备接收故障报警信息，并根据故障报警信息确定述第一网络切片子网实例出现故障，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device receives the fault alarm information from the second network device, and determines that the first network slice subnet instance is faulty according to the fault alarm information, thereby flexibly managing the network slice instance and improving management. The efficiency of the network slice instance.
在一种可能的实现方式中，还包括：所述第一网络设备将使用所述第二网络切片子网实例替换所述第一网络切片子网实例的过程信息记录至存储设备。In a possible implementation manner, the method further includes: the first network device records, by using the second network slice subnet instance, process information of the first network slice subnet instance to a storage device.
在本申请实施例中，第一网络设备将使用第二网络切片子网实例替换第一网络切片子网实例的过程信息记录至存储设备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device records, by using the second network slice subnet instance, the process information of the first network slice subnet instance to the storage device, so that the network slice instance can be flexibly managed, and the management network slice is improved. The efficiency of the instance.
在一种可能的实现方式中，还包括：所述第二网络切片子网实例是所述第二网络设备管理的冗余的网络切片子网实例。In a 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 a possible implementation, the method further includes: the second network slice subnet instance is a newly created network slice subnet instance of the second network device.
第二方面，提供了一种管理网络切片实例的方法，包括：第二网络设备从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换第一网络切片子网实例；所述第二网络设备根据所述第一指示信息，激活所述第二网络切片子网实例。A second aspect provides a method for managing a network sharding instance, including: receiving, by a second network device, first indication information from a first network device, where the first indication information is used to indicate that the second network device activates a second a network slice subnet instance, wherein the second network slice subnet instance is configured to replace the first network slice subnet instance; the second network device activates the second network slice according to the first indication information Network instance.
在本申请实施例中，第二网络设备从第一网络设备接收第一指示信息，第二网络设备根据第一指示信息，激活所述第二网络切片子网实例，以替换第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the second network device receives the first indication information from the first network device, and the second network device activates the second network slice subnet instance to replace the first network slice according to the first indication information. Network instance, which enables flexible management of network slice instances and improves the efficiency of managing network slice instances.
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障。In a possible implementation, the method further includes: the second network device sending fault alarm information to the first network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty.
在本申请实施例中，第二网络设备向第一网络设备发送故障报警信息，以向第一网络设备指示第一网络切片子网实例出现故障，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the second network device sends the fault alarm information to the first network device, to indicate to the first network device that the first network slice subnet instance is faulty, so that the network slice instance can be flexibly managed, and the management is improved. The efficiency of the network slice instance.
第三方面，提供了一种管理网络切片实例的方法，包括：第一网络设备确定第一网络切片子网实例出现故障；所述第一网络设备向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备对所述第一网络切片子网实例执行回退处理。A third aspect provides a method for managing an instance of a network slice, including: determining, by a first network device, that a first network slice subnet instance is faulty; and the first network device sends first indication information to the second network device, where The first indication information is used to instruct the second network device to perform a rollback process on the first network slice subnet instance.
在本申请实施例中，第一网络设备确定第一网络切片子网实例出现故障的情况下，可以指示第二网络设备对第一网络切片子网实例执行回退处理，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, when the first network device determines that the first network slice subnet instance is faulty, the second network device may be instructed to perform a rollback process on the first network sliced subnet instance, so that the network can be flexibly managed. Slice instances improve the efficiency of managing network slice instances.
在一种可能的实现方式中，还包括：所述第一网络设备获取所述第一网络切片子网实例的历史参数信息；所述第一网络设备基于所述第一网络切片子网实例的历史参数信息，确定所述第一指示信息。In a possible implementation, the method further includes: the first network device acquiring historical parameter information of the first network slice subnet instance; the first network device is based on the first network slice subnet instance The historical parameter information determines the first indication information.
在本申请实施例中，第一网络设备获取第一网络切片子网实例的历史参数信息；并基于该历史参数信息，确定所述第一指示信息。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device acquires historical parameter information of the first network slice subnet instance; and determines the first indication information based on the historical parameter information. Thereby, the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
在一种可能的实现方式中，还包括：所述第一网络设备从所述第二网络设备获取所述第一网络切片子网实例的历史参数信息；所述第一网络设备将所述第一网络切片子网实例的历史参数信息备份至存储设备；所述第一网络设备获取所述第一网络切片子网实例的历史参数信息，包括：所述第一网络设备从所述存储设备获取所述第一网络切片子网实例的历史参数信息。In a possible implementation, the method further includes: the first network device acquiring, from the second network device, historical parameter information of the first network slice subnet instance; the first network device The historical parameter information of the network segment subnet instance is backed up to the storage device; the first network device acquiring the historical parameter information of the first network slice subnet instance, where the first network device obtains from the storage device The historical parameter information of the first network slice subnet instance.
在本申请实施例中，第一网络设备将历史参数信息备份至存储设备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present 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, before the first network device sends the first indication information to the second network device, the method further includes: acquiring, by the first network device, current parameters of the first network slice subnet instance The first network device backs up current parameter information of the first network slice subnet instance to the storage device.
在本申请实施例中，第一网络设备将第一网络切片实例的当前参数信息备份至存储设备，以便于复原第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device backs up the current parameter information of the first network slice instance to the storage device, so as to restore the first network slice subnet instance, thereby being able to flexibly manage the network slice instance and improve the management network. The efficiency of the slice instance.
在一种可能的实现方式中，还包括：在执行回退处理后的所述第一网络切片子网实例的性能不符合预定条件的情况下，所述第一网络设备向所述第二网络设备发送第二指示信息，所述第二指示信息用于指示所述第二网络设备基于备份至所述存储设备中的第一网络切片子网实例的所述当前参数信息，复原所述第一网络切片子网实例。In a possible implementation, the method further includes: the first network device is in the second network, if the performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition The device sends the second indication information, where the second indication information is used to instruct the second network device to restore the first information based on the current parameter information that is backed up to the first network slice subnet instance in the storage device. Network slice subnet instance.
在本申请实施例中，第一网络设备从存储设备获取第一网络切片实例的当前参数信息，并根据该当前参数信息复原第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device obtains 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 improved. The efficiency of managing network slice instances.
在一种可能的实现方式中，还包括：所述第一网络设备获取执行回退处理后的所述第一网络切片子网实例的性能信息，所述性能信息用于指示所述第一网络切片子网实例的性能；所述第一网络设备基于所述性能信息，确定所述第一网络切片子网实例的性能是否符合预定条件。In a possible implementation manner, the method includes: the first network device acquiring performance information of the first network slice subnet instance after performing a rollback process, where the performance information is used to indicate the first network Slicing the performance of the subnet instance; the first network device determines, based on the performance information, whether the performance of the first network slice subnet instance meets a predetermined condition.
在本申请实施例中，第一网络设备获取回退处理后的第一网络切片实例的性能信息，并基于性能信息确定第一网络切片子网实例的性能是否符合预定条件，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device obtains performance information of the first network slice instance after the rollback process, and determines, according to the performance information, whether the performance of the first network slice subnet instance meets a predetermined condition, thereby being capable of flexibly managing Network slicing instances improve the efficiency of managing network slicing instances.
在一种可能的实现方式中，还包括：所述第一网络设备将对所述第一网络切片子网实例执行回退处理的过程信息记录至存储设备。In a possible implementation manner, the method further includes: the first network device records, to the storage device, process information that performs a rollback process on the first network slice subnet instance.
在本申请实施例中，第一网络设备将对第一网络切片子网实例执行回退处理的过程信息记录至存储设备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device records the process information of performing the rollback process 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 possible implementation, the method further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; The first network device determines that the first network slice subnet instance is faulty, and the first network device determines the first network slice subnet instance according to the fault alarm information.
在本申请实施例中，第一网络设备从第二网络设备接收故障报警信息，并根据故障报警信息确定第一网络切片子网实例出现故障，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device receives the fault alarm information from the second network device, and determines that the first network slice subnet instance is faulty according to the fault alarm information, thereby flexibly managing the network slice instance and improving the management network. The efficiency of the slice instance.
第四方面，提供了一种管理网络切片实例的方法，包括：第二网络设备从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备对出现故障的第一网络切片子网实例执行回退处理；所述第二网络设备根据所述第一指示信息，对所述第一网络切片子网实例执行回退处理。A fourth aspect provides a method for managing a network sharding instance, where the second network device receives the first indication information from the first network device, where the first indication information is used to indicate that the second network device pair is faulty. The first network slice subnet instance performs a fallback process; the second network device performs a rollback process on the first network sliced subnet instance according to the first indication information.
在本申请实施例中，第二网络设备从第一网络设备接收第一指示信息，该第一指示信息用于指示所述第一网络设备对第一网络切片子网实例执行回退处理，第二网络设备基于该第一指示信息对所述第一网络切片子网实例执行回退处理，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the second network device receives the first indication information from the first network device, where the first indication information is used to instruct the first network device to perform a rollback process on the first network slice subnet instance, where The network device performs a fallback process on the first network slice subnet instance based on the first indication information, 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 second network device receives the first indication information from the first network device, the method further includes: the second network device sending the The current parameter information of the first network slice instance, so that the first network device backs up the current parameter information of the first network slice subnet instance to the storage device.
在本申请实施例中，第二网络设备向第一网络设备发送第一网络切片子网实例的当前参数信息，以便于第一网络设备将第一网络切片子网实例的当前参数信息备份至存储设 备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present 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 backs up the current parameter information of the first network slice subnet instance to the storage. Devices that provide the flexibility to manage network slicing instances and improve the efficiency of managing network slicing instances.
在一种可能的实现方式中，还包括：在执行回退处理后的所述第一网络切片子网实例的性能不符合预定条件的情况下，所述第二网络设备从所述第一网络设备接收第二指示信息，所述第二指示信息用于指示所述第二网络设备基于备份至所述存储设备中的第一网络切片子网实例的所述当前参数信息，复原所述第一网络切片子网实例。In a possible implementation manner, the method further includes: in a case that performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition, the second network device is from the first network The device receives the second indication information, where the second indication information is used to instruct the second network device to restore the first information based on the current parameter information that is backed up to the first network slice subnet instance in the storage device. Network slice subnet instance.
在本申请实施例中，第二网络设备基于第一网络设备发送的第一指示信息，复原第一网络切片子网实例。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the 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. Thereby, the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障。In a possible implementation, the method further includes: the second network device sending fault alarm information to the first network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty.
在本申请实施例中，第二网络设备向第一网络设备发送故障报警信息，以指示第一网络切片子网实例出现故障。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the second network device sends fault alarm information to the first network device to indicate that the first network slice subnet instance is faulty. Thereby, the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送所述第一网络切片子网实例的历史参数信息，以便于所述第一网络设备将所述第一网络切片子网实例的历史参数信息备份至存储设备。In a possible implementation, the method further includes: sending, by the second network device, historical parameter information of the first network slice subnet instance to the first network device, so that the first network device The historical parameter information of the first network slice subnet instance is backed up to the storage device.
在本申请实施例中，第二网络设备向第一网络设备发送第一网络切片子网实例的历史参数信息，以便于第一网络设备将第一网络切片子网实例的历史参数信息备份至存储设备，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present 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 backs up the historical parameter information of the first network slice subnet instance to the storage. Devices that provide the flexibility to manage network slicing instances and improve the efficiency of managing network slicing instances.
第五方面，提供了一种网络设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。In a fifth aspect, a network device is provided for performing the method of any of the first aspect or the first aspect of the first aspect. In particular, the network device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
第六方面，提供了另一种网络设备，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。In a sixth aspect, there is provided another network device for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect. In particular, the network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
第七方面，提供了另一种网络设备，用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第三方面或第三方面的任意可能的实现方式中的方法的单元。In a seventh aspect, there is provided another network device for performing the method in any of the possible implementations of the third aspect or the third aspect above. In particular, the network device comprises means for performing the method of any of the possible implementations of the third aspect or the third aspect described above.
第八方面，提供了另一种网络设备，用于执行上述第四方面或第四方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第四方面或第四方面的任意可能的实现方式中的方法的单元。In an eighth aspect, there is provided another network device for performing the method of any of the above-described fourth aspect or any of the possible implementations of the fourth aspect. In particular, the network device comprises means for performing the method of any of the above-described fourth or fourth aspects of the fourth aspect.
第九方面，提供了一种网络***，该***包括上述第五方面、第六方面所述的网络设备，或包括上述第七方面和第八方面所述的网络设备。The ninth aspect provides a network system, comprising the network device according to the fifth aspect, the sixth aspect, or the network device according to the seventh aspect and the eighth aspect.
第十方面，提供了一种网络设备，该网络设备包括：通信接口、存储器、处理器和总线***。其中，该通信接口、该存储器和该处理器通过该总线***相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。In a tenth aspect, a network device is provided, the network device comprising: a communication interface, a memory, a processor, and a bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of the first aspect or any of the possible implementations of the first aspect.
第十一方面，提供了一种网络设备，该网络设备包括：通信接口、存储器、处理器和总线***。其中，该通信接口、该存储器和该处理器通过该总线***相连，该存储器用于 存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。In an eleventh aspect, a network device is provided, the network device comprising: a communication interface, a memory, a processor, and a bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the second aspect or the second aspect.
第十二方面，提供了一种网络设备，该网络设备包括：通信接口、存储器、处理器和总线***。其中，该通信接口、该存储器和该处理器通过该总线***相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第三方面或第三方面的任意可能的实现方式中的方法。In a twelfth aspect, a network device is provided, the network device comprising: a communication interface, a memory, a processor, and a bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the third aspect or the third aspect.
第十三方面，提供了一种网络设备，该网络设备包括：通信接口、存储器、处理器和总线***。其中，该通信接口、该存储器和该处理器通过该总线***相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第四方面或第四方面的任意可能的实现方式中的方法。In a thirteenth aspect, a network device is provided, the network device comprising: a communication interface, a memory, a processor, and a bus system. Wherein the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute 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 perform the method of any of the possible implementations of the fourth aspect or the fourth aspect.
第十四方面，提供了一种网络***，该***包括上述第十方面、第十一方面所述的网络设备，或包括上述第十二方面和第十三方面所述的网络设备。According to a fourteenth aspect, the invention provides a network system, comprising the network device according to the tenth aspect, the eleventh aspect, or the network device according to the twelfth aspect and the thirteenth aspect.
第十五方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。A fifteenth aspect, a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations 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 any of the second aspect or any of the possible implementations of the second aspect.
第十七方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。A seventeenth aspect, a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the third aspect or any of the possible implementations of the third aspect.
第十八方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第四方面或第四方面的任意可能的实现方式中的方法的指令。In an eighteenth aspect, a computer readable medium is provided for storing a computer program comprising instructions for performing the method of any of the fourth aspect or any of the possible implementations of the fourth aspect.
第十九方面，提供了一种网络***，该***包括上述第十五方面、第十六方面所述的计算机可读介质，或包括上述第十七方面和第十八方面所述的计算机可读介质。According to a nineteenth aspect, the invention provides a network system, comprising the computer readable medium of the fifteenth aspect, the computer of the sixteenth aspect, Read the media.
附图说明DRAWINGS
图1是本申请实施例的网络管理架构的示意图。FIG. 1 is a schematic diagram of a network management architecture according to an embodiment of the present application.
图2是本申请又一实施例的网络管理架构的示意图。2 is a schematic diagram of a network management architecture according to still another embodiment of the present application.
图3是本申请又一实施例的网络管理架构的示意图。FIG. 3 is a schematic diagram of a network management architecture according to still another embodiment of the present application.
图4是本申请又一实施例的网络管理架构的示意图。4 is a schematic diagram of a network management architecture according to still another embodiment of the present application.
图5是本申请实施例的管理网络切片实例的方法的示意图。FIG. 5 is a schematic diagram of a method for managing a network slice instance according to an embodiment of the present application.
图6是本申请又一实施例的管理网络切片实例的方法的示意图。FIG. 6 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
图7是本申请又一实施例的管理网络切片实例的方法的示意图。FIG. 7 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
图8是本申请又一实施例的管理网络切片实例的方法的示意图。FIG. 8 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
图9是本申请又一实施例的管理网络切片实例的方法的示意图。FIG. 9 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
图10是本申请实施例的网络设备的示意图。FIG. 10 is a schematic diagram of a network device according to an embodiment of the present application.
图11是本申请又一实施例的网络设备的示意图。FIG. 11 is a schematic diagram of a network device according to still another embodiment of the present application.
图12是本申请又一实施例的网络设备的示意图。FIG. 12 is a schematic diagram of a network device according to still another embodiment of the present application.
图13是本申请又一实施例的网络设备的示意图。FIG. 13 is a schematic diagram of a network device according to still another embodiment of the present application.
图14是本申请又一实施例的网络设备的示意图。FIG. 14 is a schematic diagram of a network device according to still another embodiment of the present application.
图15是本申请又一实施例的网络设备的示意图。FIG. 15 is a schematic diagram of a network device according to still another embodiment of the present application.
图16是本申请又一实施例的网络设备的示意图。FIG. 16 is a schematic diagram of a network device according to still another embodiment of the present application.
图17是本申请又一实施例的网络设备的示意图。FIG. 17 is a schematic diagram of a network device according to still another embodiment of the present application.
具体实施方式detailed description
下面将结合附图，对本申请中的技术方案进行描述。The technical solutions 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, in order to facilitate understanding of the content of the present application, some terms and network slice management systems appearing herein will be described first.
网络切片(Network slice)：指在物理或者虚拟的网络基础设施之上，根据不同的服务需求定制化不同的逻辑网络。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供电信服务，具有一定网络能力；网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合，例如，网络切片只包含接入网和核心网。网络切片可能具有如下一个或多个特性：接入网可能切片，也可能不切片。接入网可能是多个网络切片共用的。不同的网络切片的特性和组成它们的网络功能可能是不一样。Network slice: refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure. The network slice can be a complete end-to-end network including a terminal, an access network, a transmission network, a core network, and an application server, and can provide telecommunication services and have certain network capabilities; the network slice can also be the above terminal and access network. Any combination of the transport network, the core network, and the application server, for example, the network slice only includes the access network and the core network. A network slice may have one or more of the following characteristics: the access network may or may not slice. The access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.
网络切片实例(Network slice instance,NSI)：是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种服务。网络切片实例可以由网管***创建，一个网管***可能创建多个网络切片实例并同时对它们进行管理，包括在网络切片实例运行过程中的性能监视和故障管理等。当多个网络切片实例共存时，网络切片实例之间可能共享部分网络资源和网络功能。网络切片实例可能从网络切片模板创建，也可能不从网络切片模板创建。一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例(network slice subnet instance,NSSI)和/或网络功能。网络功能可以包括物理网络功能和/或虚拟网络功能。以下统称物理网络功能和/或虚拟网络功能为网络功能。Network Slice Instance (NSI): A real-world logical network that meets certain network characteristics or service requirements. A network slice instance may provide one or more services. A network sharding instance can be created by the network management system. A network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances. A network tile instance may or may not be created from a network tile template. A complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slice subnet instances (NSSI) and/or network functions. Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
网络切片子网实例(network slice subnet instance,NSSI)：网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由其他方式组成集合。网络切片子网实例可能被多个网络切片实例共享。提出网络切片子网实例，可以方便网管***管理。一个网络切片实例可能由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或若干网络切片子网实例组成；一个网络切片实例可能由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能组成；一个网络切片实例也可能仅由若干网络功能组成。Network slice subnet instance (NSSI): The network slice subnet instance does not need to provide end-to-end complete network services. The network slice subnet instance can be the network function of the same device vendor in the network slice instance. A collection may also be a collection of network functions divided by domain, such as a core network network sliced subnet instance, an access network network sliced subnet instance, or a collection of other methods. A network sliced subnet instance may be shared by multiple network slice instances. The network slice subnet instance is proposed to facilitate network management system management. A network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or several network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none It is composed of network functions that are divided into network slice subnet instances; a network slice instance may also consist of only a few network functions.
网络功能(Network function,NF)：是网络中的一种处理功能，定义了功能性的行为和接口，网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为物理网络功能和虚拟网络功能。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能，具体地，对于多个(子)网络切片实例而言，可以独立地使用不同的网络功能， 这种网络功能称为专属网络功能，也可以共享同一个网络功能，这种网络功能称为共享网络功能。Network function (NF): A processing function in the network that defines functional behaviors and interfaces. Network functions can be implemented through dedicated hardware, or by running software on dedicated hardware, or in general. The hardware platform is implemented in the form of virtual functions. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network functions can also share the same network function, which is called shared network function.
服务管理功能模块(Sevice management function,SvMF)：负责将运营商和/或第三方客户的电信服务需求转化为对网络切片的需求，向NSMF发送对网络切片的需求，接收运营商和/或第三方客户对网络切片管理数据(例如性能数据、故障数据、故障修复数据等)的订阅需求，从NSMF获取网络切片的管理数据等。Sevice management function (SvMF): responsible for translating the telecommunication service requirements of operators and/or third-party customers into the demand for network slicing, sending the demand for network slicing to NSMF, receiving operators and/or The three-party customer subscribes to the network slice management data (such as performance data, fault data, fault repair data, etc.), and obtains management data of the network slice from the NSMF.
网络切片管理功能模块(network slice management function,NSMF)：负责接收SvMF发送的网络切片需求，对网络切片实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)，编排网络切片实例的组成，分解网络切片实例的需求为各网络切片子网实例的需求，向各NSSMF发送网络切片子网实例管理请求，向NFM发送网络功能管理请求。Network slice management function (NSMF): Responsible for receiving network slice requirements sent by SvMF, managing the life cycle, performance, faults, etc. of the network slice instance (hereinafter referred to as life cycle, performance, fault management for short management) The composition of the network slice instance is arranged, and the requirement of decomposing the network slice instance is the requirement of each network slice subnet instance, and the network slice subnet instance management request is sent to each NSSMF, and the network function management request is sent to the NFM.
网络切片子网管理功能模块(network slice subnet management function,NSSMF)：从NSMF接收对网络切片子网实例的需求，从而对网络切片子网实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)，编排网络切片实例的组成。Network slice subnet management function (NSSMF): Receives the requirement of the network slice subnet instance from the NSMF to manage the life cycle, performance, faults, etc. of the network slice subnet instance (the following will be life) Cycle, performance, fault management, referred to as management), the composition of the network slice instance.
网络功能管理模块(network function management,NFM)：用于管理NF，例如管理NF的生命周期，为NF分配网络资源等。Network function management (NFM): used to manage NF, such as managing the life cycle of NF, allocating network resources for NF, and so on.
网络切片自愈监视与管理功能(Network Slice Self-Healing Monitor and Management Function,NS-SH-MMF)：它包含至少如下一项功能：向NS-SH-IF发送网络切片自愈算法及参数；配置NSS-SH-MMF关于网络切片子网自愈相关的信息与参数；监控网络切片实例运行情况与故障情况；判断网络切片实例故障是否满足自愈触发条件；向NS-SH-IF发送网络切片自愈触发请求；接收NS-SH-IF发送的网络切片自愈处置结果；向SvMF报告网络切片故障数据和自愈处置结果。Network Slice Self-Healing Monitor and Management Function (NS-SH-MMF): It includes at least one of the following functions: sending network slice self-healing algorithms and parameters to NS-SH-IF; NSS-SH-MMF information and parameters related to network slice subnet self-healing; monitor network slice instance operation and fault conditions; determine whether the network slice instance fault meets the self-healing trigger condition; send network slice to NS-SH-IF The trigger request is received; the network slice self-healing result sent by the NS-SH-IF is received; and the network slice fault data and the self-healing result are reported to the SvMF.
网络切片自愈执行功能(Network Slice Self-Healing Implementation Function,NS-SH-IF：)：它包含至少如下一项功能：接收来自NS-SH-MMF的网络切片自愈算法配置及参数；接收NS-SH-MMF发送的网络切片自愈触发请求；收集网络切片运行信息，包括但不限于网络切片实例性能数据，故障告警，配置数据，测试数据等；判断故障类型决策故障自修复动作；执行故障自修复动作，包括但不限于切换故障子切片实例/网络功能为冗余子切片实例/网络功能，创建新子切片实例/网络功能取代故障子切片实例/网络功能，对造成故障的网络切片实例配置、修改进行回退等；对现有网络切片实例中的配置进行备份；执行具体故障自动恢复动作；评估故障自动恢复效果；判断是否需要停止故障恢复流程；复原故障自动恢复执行的动作；和NS Repository交互记录故障恢复所采取的动作与故障恢复结果；向NS-SH-MMF上报故障恢复结果。Network Slice Self-Healing Implementation Function (NS-SH-IF:): It contains at least one of the following functions: receiving network slice self-healing algorithm configuration and parameters from NS-SH-MMF; receiving NS The network slice self-healing trigger request sent by the -SH-MMF; collecting network slice running information, including but not limited to network slice instance performance data, fault alarm, configuration data, test data, etc.; determining the fault type decision fault self-repair action; Self-healing actions, including but not limited to switching faulty sub-slice instances/network functions to redundant sub-slice instances/network functions, creating new sub-slice instances/network functions instead of failed sub-slice instances/network functions, for network fragment instances that cause failures Configure, modify, rollback, etc.; back up the configuration in the existing network slicing instance; perform specific fault auto-recovery actions; evaluate the automatic fault recovery effect; determine whether it is necessary to stop the fault recovery process; NS Repository interactively records actions and failures taken by failure recovery Multiplexing result; NS-SH-MMF to the recovery results reported.
网络切片子网自愈监视与管理功能(Network Slice Subnet Self-Healing Monitor and Management Function,NSS-SH-MMF)：它包含至少如下一项功能：向NSS-SH-IF发送网络切片子网自愈算法及参数；监控网络切片子网实例运行情况与故障情况；判断网络切片子网实例故障是否满足自愈触发条件；向NSS-SH-IF发送网络切片子网自愈触发请求；接收NSS-SH-IF发送的网络切片子网自愈处置结果；向NS-SH-MMF报告网络切片子网故障数据和自愈处置结果。Network Slice Subnet Self-Healing Monitor and Management Function (NSS-SH-MMF): It contains at least one of the following functions: Sending network slice subnet self-healing to NSS-SH-IF Algorithm and parameters; monitor the running condition and fault condition of the network slicing subnet instance; determine whether the network slicing subnet instance fault meets the self-healing trigger condition; send a network slice subnet self-healing trigger request to the NSS-SH-IF; receive the NSS-SH - The network slice subnet self-healing result sent by the IF; reports the network slice subnet fault data and the self-healing result to the NS-SH-MMF.
网络切片自愈执行功能(Network Slice Subnet Self-Healing Implementation Function, NSS-SH-IF)：它包含至少如下一项功能：接收来自NSS-SH-MMF的网络切片子网自愈算法配置及参数；接收NSS-SH-MMF发送的网络切片子网自愈触发请求；收集网络切片子网运行信息，包括但不限于网络切片子网实例性能数据，故障告警，配置数据，测试数据等；判断故障类型决策故障自修复动作；执行故障自修复动作，包括但不限于切换故障子切片实例(嵌套的网络切片子网实例)/网络功能为冗余子切片实例/网络功能，创建新子切片实例/网络功能取代故障子切片实例(嵌套的网络切片子网实例)/网络功能，对造成故障的网络切片子网实例配置、修改进行回退等；对现有网络切片子网实例中的配置进行备份；执行具体故障自动恢复动作；评估故障自动恢复效果；判断是否需要停止故障恢复流程；复原故障自动恢复执行的动作；和NSS Repository交互记录故障恢复所采取的动作与故障恢复结果；向NSS-SH-MMF上报故障恢复结果。Network Slice Subnet Self-Healing Implementation Function (NSS-SH-IF): It includes 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 trigger request sent by the NSS-SH-MMF; collecting network slice subnet operation information, including but not limited to network slice subnet instance performance data, fault alarm, configuration data, test data, etc.; Decision fault self-repair action; perform fault self-repair action, including but not limited to switching fault sub-slice instance (nested network slice subnet instance) / network function is redundant sub-slice instance / network function, create new sub-slice instance / The network function replaces the faulty sub-slice instance (nested network slicing subnet instance)/network function, configures, modifies, and regresses the network slicing subnet instance that caused the fault; performs the configuration in the existing network slicing subnet instance. Backup; perform specific fault automatic recovery actions; evaluate the automatic recovery effect of faults; determine whether it is necessary to stop the fault recovery process The recovery failure automatically resumes the execution of the action; interacts with the NSS Repository to record the action taken and the failure recovery result of the failure recovery; and reports the failure recovery result to the NSS-SH-MMF.
网络切片信息库((Network Slice Repository,NS Repository)：它是一个数据库，其中至少记录了以下一项内容：网络切片实例配置信息，包括网络切片子网实例配置信息、网络功能配置信息，故障信息、自修复动作与修复结果等。NS Repository可以与NSMF独立开来，也可以与NSMF设置在同一网络设备中。Network Slice Repository (NS Repository): It is a database in which at least one of the following is recorded: network slice instance configuration information, including network slice subnet instance configuration information, network function configuration information, and fault information. Self-repair actions and repair results, etc. NS Repository can be independent of NSMF or set up on the same network device as NSMF.
网络切片子网信息库(Network Slice Subnet Repository,NSS Repository)：。它是一个数据库，其中至少记录了以下一项内容：网络切片子网实例配置信息，包括嵌套的网络切片子网实例配置信息、网络功能配置信息，故障信息、自修复动作与修复结果等。NSS Repository可以与NSSMF独立开来，也可以与NSSMF设置在同一网络设备中。Network Slice Subnet Repository (NSS Repository):. It is a database that records at least one of the following: network slice subnet instance configuration information, including nested network slice subnet instance configuration information, network function configuration information, fault information, self-healing actions, and repair results. The NSS Repository can be independent of NSSMF or set up on the same network device as NSSMF.
图1的网络管理架构100中还包括以下接口中的至少一种接口：The network management architecture 100 of FIG. 1 further includes at least one of the following interfaces:
接口1：SvMF和NSMF之间的接口，用于SvMF向NSMF发送业务对网络切片的需求，NSM向SvMF反馈NSI和业务的运行情况，并提供一定的管理数据。Interface 1: The interface between the SvMF and the NSMF is used by the SvMF to send the service to the NSMF for network slicing. The NSM feeds back the NSI and service operations to the SvMF and provides certain management data.
接口2：NSMF和NSSMF之间的接口，NSMF在管理和编排NSI时，通过该接口向NSSMF传递对NSSI的需求，例如创建、修改、获取管理数据等，NSSMF通过该接口向NSMF反馈有关NSSI的信息。Interface 2: The interface between NSMF and NSSMF. When the NSMF manages and orchestrate the NSI, it passes the NSSI requirements to the NSSMF through the interface, such as creating, modifying, and obtaining management data. The NSSMF feeds back NSSI to the NSMF through the interface. information.
接口3：NSMF和NFM之间的接口，NSMF发送对NF进行管理和配置命令；NFM通过该接口接收来自NSMF的消息，并且通过该接口反馈关于NF的信息。Interface 3: An interface between the NSMF and the NFM, the NSMF sends a management and configuration command to the NF; the NFM receives the message from the NSMF through the interface, and feeds back information about the NF through the interface.
接口4：NSSMF之间的接口，用于NSSMF之间的互相协调，NSSMF通过该接口请求另一个NSSMF对其所管辖的NSSI进行管理，包括生命周期管理、性能管理、故障管理等。Interface 4: An interface between NSSMFs for mutual coordination between NSSMFs. The NSSMF requests another NSSMF to manage the NSSIs it governs, including lifecycle management, performance management, and fault management.
接口5：NSMF与NS Repository之间的接口，用于NSMF在NS Repository中记录和读取数据。Interface 5: Interface between NSMF and NS Repository for NSMF to record and read data in NS Repository.
接口6：NSSMF与NSS Repository之间的接口，用于NSSMF在NSS Repository中记录和读取数据。Interface 6: The interface between NSSMF and NSS Repository for NSSMF to record and read data in the NSS Repository.
接口7：NSMF与NSS Repository之间的接口，用于NSMF从NSS Repository中获取数据。Interface 7: Interface between NSMF and NSS Repository for NSMF to retrieve data from the NSS Repository.
另外，图1中还展示了几种NSI的组成方式，包括：NSI由若干个NSSI组成；NSI由若干个NSSI，以及若干个NF组成；NSI由若干个NF组成。In addition, FIG. 1 also shows several NSI components, including: NSI is composed of several NSSIs; NSI is composed of several NSSIs, and several NFs; NSI is composed of several NFs.
需要说明的是，NSSI允许嵌套，即一个NSSI包含另一个NSSI，两者均有各自的NSSMF；假设NSI包含NSSI 1，NSSI 1又包含NSSI 2，NSSMF 1和NSSMF 2分别是 NSSI 1和NSSI 2的管理器，此时对NSSI 2的管理存在两种可选项，选项1是由NSSMF 1向NSSMF 2发送NSI 2的管理请求，该选项适用于NSSMF 1和NSSMF 2之间存在接口4的场景下；选项2是由NSMF直接向NSSMF 2发送NSSI 2的管理请求。It should be noted that NSSI allows nesting, that is, one NSSI contains another NSSI, both of which have their own NSSMF; assuming NSI includes NSSI 1, NSSI 1 contains NSSI 2, and NSSMF 1 and NSSMF 2 are NSSI 1 and NSSI, respectively. Manager 2, there are two options for the management of NSSI 2 at this time, Option 1 is a management request for NSI 2 sent by NSSMF 1 to NSSMF 2, this option is applicable to the scenario where interface 4 exists between NSSMF 1 and NSSMF 2. Next; option 2 is a management request for NSSI 2 to be sent directly by the NSMF to the NSSMF 2.
另外，NS Repository可能是独立于NSMF的单独实体，也可能是NSMF内部的一个数据库。NSS Repository可能是独立于NSSMF的单独实体，也可能是NSSMF内部的一个数据库。当NSS Repository是一个单独实体时，它可能存储若干个子切片实例的信息，和若干NSSMF存在接口6。In addition, the NS Repository may be a separate entity independent of NSMF, or it may be a database internal to NSMF. The NSS Repository may be a separate entity independent of NSSMF or a database internal to NSSMF. When the NSS Repository is a separate entity, it may store information for several sub-slice instances and interface 6 with several NSSMFs.
在NSSI允许嵌套的情况下，图2至图4分别示出了三种本申请实施例的网络管理架构。In the case where the NSSI allows nesting, FIG. 2 to FIG. 4 respectively show three network management architectures of the embodiments of the present application.
图2是本申请实施例的网络管理架构200的结构示意图。如图2所示，被嵌套的NSSI的NSS_SH_IF2由上一层NSSI的NSS_SH_MMF1管理；上一层的NSS_SH_MMF1又被NS_SH_MMF管理。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, the NSS_SH_IF2 of the nested NSSI is managed by the NSS_SH_MMF1 of the upper layer NSSI; the upper layer of NSS_SH_MMF1 is managed by the NS_SH_MMF.
图3是本申请实施例的网络管理架构300的结构示意图。如图3所示，被嵌套的NSSI的NSS_SH_IF2可以直接由NSS_SH_MMF2管理,NSS_SH_MMF2从NSS_SH_MMF1接收策略。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, the nested NSSI NSS_SH_IF2 can be directly managed by NSS_SH_MMF2, and NSS_SH_MMF2 receives the policy from NSS_SH_MMF1.
图4是本申请实施例的网络管理架构400的结构示意图。如图4所示，被嵌套的NSSI的NSS_SH_IF2由它本身的NSS_SH_MMF2管理；它自身的NSS_SH_MMF2可以由NS_SH_MMF管理。另外NSS_SH_MMF2与NSS_SH_MMF1之间可以存在着一些协调关系。FIG. 4 is a schematic structural diagram of a network management architecture 400 according to an embodiment of the present application. As shown in Figure 4, the NSS_SH_IF2 of the nested NSSI is managed by its own NSS_SH_MMF2; its own NSS_SH_MMF2 can be managed by NS_SH_MMF. In addition, there may be some coordination relationship between NSS_SH_MMF2 and NSS_SH_MMF1.
此外，应当注意的是，上述引入的各个功能模块和单元，是从它们所具有的功能的角度考虑的。实际应用中，上述各功能模块可以是单独的物理存在，也可以是两个或两个以上设备集成在一个单元中，例如，NS_SH_MMF模块和NS_SH_IF模块可以合并为一个功能模块，该功能模块具有NS_SH_MMF模块和NS_SH_IF模块的所有功能，或者NS_SH_MMF模块和NS_SH_IF模块可以分别是独立的模块，并通过模块之间的接口进行通信。本领域普通技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。Further, it should be noted that the respective functional modules and units introduced above are considered from the viewpoint of the functions they have. In practical applications, each of the foregoing functional modules may be a separate physical entity, or two or more devices may be integrated into one unit. For example, the NS_SH_MMF module and the NS_SH_IF module may be combined into one functional module, and the functional module has NS_SH_MMF. All functions of the module and the NS_SH_IF module, or the NS_SH_MMF module and the NS_SH_IF module, can be independent modules and communicate through the interface between the modules. A person skilled in the art can easily conceive various equivalent modifications or substitutions within the scope of the technical scope of the present application, and such modifications or substitutions are intended to be included within the scope of the present application.
上文介绍了本申请实施例的网络管理架构，下文将结合附图，介绍本申请实施例的管理网络切片实例的方法、装置和***。The network management architecture of the embodiment of the present application is described above. The method, device, and system for managing a network slice instance according to an embodiment of the present application are described below with reference to the accompanying drawings.
图5是本申请实施例的管理网络切片实例的方法500的示意性流程图。方法500可以适用于图1至图4所示的网络管理架构。图5中的第一网络设备可以包括NS_SH_IF模块或NSMF模块，NSMF模块包括NS_SH_MMF和NS_SH_IF模块。第二网络设备、第三网络设备、第四网络设备可以包括NSSMF模块。其中，第三网络设备至第四网络设备可以分别包括单独的NSSMF模块，也可以包括同一个NSSMF模块。FIG. 5 is a schematic flowchart of a method 500 for managing a network slice instance according to an embodiment of the present application. Method 500 can be applied to the network management architecture illustrated in Figures 1 through 4. The first network device in FIG. 5 may include an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module. The second network device, the third network device, and the fourth network device may include an NSSMF module. The third network device to the fourth network device may respectively include a separate NSSMF module, and may also include the same NSSMF module.
如图5所示，方法500包括：As shown in FIG. 5, method 500 includes:
S501、第一网络设备确定第一网络切片子网实例出现故障。S501. The first network device determines that the first network slice subnet instance is faulty.
上述第一网络设备可以是用于管理和监控多个网络切片子网实例的模块。例如，第一网络设备可以是NSMF模块。例如，上述第一网络设备用于管理和监控网络切片实例，该网络切片实例包括所述第一网络切片子网实例。The first network device may be a module for managing and monitoring multiple network slice subnet instances. For example, the first network device can be an NSMF module. For example, the first network device is configured to manage and monitor a network slice instance, and the network slice instance includes the first network slice subnet instance.
可选地，第一网络设备确定第一网络切片子网实例出现故障有多种方式。例如，在一 种方式中，第一网络设备可以接收第二网络设备的故障报警信息，该故障报警信息用于指示第一网络切片子网实例出现故障。在第二种方式中，第一网络设备可以接收第五网络设备的触发自愈信息，该触发自愈信息可以是在第一网络切片子网实例满足自愈触发条件的情况下发送的。其中，在第二种方式中，该第一网络设备可以是NS_SH_IF模块，该第五网络设备可以是NS_SH_MMF模块。Optionally, the first network device determines that the first network slice subnet instance fails. For example, in one mode, the first network device may receive fault alarm information of the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty. In the second mode, the first network device may receive the trigger self-healing information of the fifth network device, where the trigger self-healing information may be sent if the first network slice subnet instance satisfies the 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、所述第一网络设备向第二网络设备发送第一指示信息，所述第二网络设备接收所述第一指示信息。所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。S502. The first network device sends first indication information to the second network device, where the second network device receives the first indication information. The first indication information is used to indicate that the second network device activates a second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance.
可选地，S502也可以理解为，第一网络设备确定对所述第一网络切片子网实例执行自愈处理，该自愈处理包括所述第一网络设备向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。Optionally, S502 is also understood to be 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 the first network device sending a first indication to the second network device. And the first indication information is used to indicate that the second network device activates the second network slice subnet instance, where 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 into the second network slice subnet instance to facilitate recovery of the service.
可选地，还可以将第二网络切片实例在NSS Repository和/或NS Repository中的状态标记为激活态。Optionally, the status of the second network slice instance in the NSS Repository and/or the NS Repository may also be marked as active.
该第一指示信息可以包括配置信息，该配置信息可以包括以下至少一项：第一网络切片子网实例的应用参数，第一网络切片子网实例在网络拓扑中的位置信息，第一网络切片子网实例和其他NSSI之间的接口信息等。The first indication information may include configuration information, where the configuration information 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, and the first network slice Interface information between the subnet instance and other NSSIs.
第二网络设备可以是监控和管理网络切片子网实例的模块。例如，第二网络设备可以是NSSMF模块。The second network device can be a module that monitors and manages network slice subnet instances. For example, the second network device can be an NSSMF module.
可选地，上述第二网络切片子网实例是所述第二网络设备管理的冗余的网络切片子网实例，或，所述第二网络切片子网实例是所述第二网络设备新建的网络切片子网实例。Optionally, the foregoing 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 newly created by the second network device. Network slice subnet instance.
在本申请实施例中，第一网络设备在确定第一网络切片子网实例出现故障的情况下，可以指示第二网络设备激活第二网络切片子网实例，以替换第一网络切片子网实例，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device, when determining that the first network slice subnet instance is faulty, may instruct the second network device to activate the second network slice subnet instance to replace the first network slice subnet instance. , which enables flexible management of network slicing instances and improves the efficiency of managing network slicing instances.
可选地，方法500还包括：所述第一网络设备向第三网络设备发送第二指示信息，所述第三网络设备接收所述第二指示信息。所述第二指示信息用于指示所述第三网络设备注销所述第一网络切片子网实例。Optionally, the method 500 further includes: the first network device sends second indication information to the third network device, and the third network device receives the second indication information. The second indication information is used to instruct the third network device to cancel the first network slice subnet instance.
作为一个示例，第二指示信息可以具体用于通知第三网络设备停止第一网络切片子网实例上运行的服务。As an example, the second indication information may be specifically used to notify the third network device to stop the service running on the first network slice subnet instance.
在方法500中，注销第一网络切片子网实例还可以包括：将第一网络切片子网实例在NSS Repository和/或NS Repository中的状态标记为注销态。In method 500, deregistering the first network slice subnet instance may further include marking a state of the first network slice subnet instance in the NSS Repository and/or the NS Repository as a logout state.
可选地，方法500还包括：所述第一网络设备向第四网络设备发送第三指示信息，所述第四设备接收所述第三指示信息。所述第三指示信息用于指示所述第四网络设备重配置与所述第一网络切片子网实例相关联的第三网络切片子网实例，所述重配置后的所述第三网络切片子网实例与所述第二网络切片子网实例相关联。Optionally, the method 500 further includes: the first network device sends third indication information to the fourth network device, and the fourth device receives the third indication information. The third indication information is used to instruct 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 A 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 be a third network slice subnet instance that has a dependency relationship with the first network slice subnet instance.
作为一个示例，第三指示信息中可以包括配置信息，该配置信息可以包括应用参数变化信息，在网络拓扑中的位置变化信息或第二网络切片子网实例之间的接口信息等。As an example, the third indication information may include configuration information, where the configuration information may include application parameter change information, location change information in a network topology, interface information between second network slice subnet instances, and the like.
可选地，在所述向第二网络设备发送第二指示信息之前，方法500还包括：所述第一网络设备将所述第一网络切片子网实例的参数信息备份至存储设备。Optionally, before the sending the second indication information to the second network device, the method 500 further includes: the first network device backing up parameter information of the first network slice subnet instance to the storage device.
在注销第一网络切片子网实例之前，第一网络设备可以将所述第一网络切片子网实例的参数信息备份至存储设备，以便于在必要的情况下，恢复第一网络切片子网实例。Before deregistering the first network slice subnet instance, the first network device may back up the parameter information of the first network slice subnet instance to the storage device, so as to restore the first network slice subnet instance if necessary .
可选地，方法500还包括：在所述第二网络切片子网实例的性能不符合预定条件的情况下，所述第一网络设备向第三网络设备发送第四指示信息，所述第三网络设备接收所述第四指示信息。所述第四指示信息用于指示所述第三网络设备基于所述第一网络切片子网实例的备份至所述存储设备中的参数信息，复原所述第一网络切片子网实例。Optionally, the method 500 further includes: when the performance of the second network slice subnet instance does not meet a predetermined condition, the first network device sends fourth indication information to the third network device, where the third The 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 parameter information of the backup of the first network slice subnet instance to the storage device.
可选地，方法500还包括：所述第一网络设备获取所述第二网络切片子网实例的性能信息，所述性能信息用于指示所述第二网络切片子网实例的性能；所述第一网络设备基于所述性能信息，确定所述第二网络切片子网实例的性能是否符合预定条件。Optionally, the method 500 further includes: the first network device acquiring performance information of the second network slice subnet instance, the performance information being used to indicate performance of the second network slice subnet instance; The first network device determines, based on the performance information, whether performance of the second network slice subnet instance meets a predetermined condition.
可选地，上述性能信息可以指可以反映第二网络切片子网实例的性能的信息。第一网络设备可以从第二网络设备获取第二网络切片子网实例的性能信息。或者，第一网络设备可以从第三网络设备获取与第一网络切片子网实例相关联的第三网络切片子网实例的性能信息，第三网络切片子网实例的性能信息也可以反映第二网络切片子网实例的性能。Optionally, the foregoing performance information may refer to information that can reflect performance of the second network slice subnet instance. The first network device may acquire 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 the 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 second The performance of a network sliced subnet instance.
作为一个示例，该性能信息可以包括性能测量信息、阈值监控信息等。As an example, the performance information may include performance measurement information, threshold monitoring information, and the like.
可选地，方法500还包括：所述第一网络设备从所述第二网络设备接收故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障；所述第一网络设备确定第一网络切片子网实例出现故障，包括：所述第一网络设备根据所述故障报警信息确定所述第一网络切片子网实例。Optionally, the method 500 further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; Determining, by the network device, that the first network slice subnet instance is faulty comprises: determining, by the first network device, the first network slice subnet instance according to the fault alarm information.
可选地，方法500还包括：所述第一网络设备将使用所述第二网络切片子网实例替换所述第一网络切片子网实例的过程信息记录至存储设备。Optionally, the method 500 further includes: the first network device records, by using the second network slice subnet instance, process information of the first network slice subnet instance to a storage device.
作为一个示例，即使以上自愈操作未能成功修复故障，恢复服务，也需记录相应自愈动作，故障信息和自愈结果。As an example, even if the above self-healing operation fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
作为一个具体示例，图6示出了本申请实施例的管理网络切片实例的方法600的示意性流程图。方法600可以用于图1至图4中的任一网络管理架构中。图6示出了将故障NSSI切换到冗余的NSSI的网络切片管理过程。其中，方法500中的第一网络设备可以是NS_SH_IF模块或NSMF模块，NSMF模块包括NS_SH_MMF和NS_SH_IF模块。方法600中的第二网络设备可以是NSSMF2模块、第三网络设备可以是NSSMF1模块、第四网络设备可以是NSSMF3模块。其中，第三网络设备至第四网络设备可以分别是单独的NSSMF模块，也可以是同一个NSSMF模块。As a specific example, FIG. 6 shows a schematic flowchart of a method 600 for managing a network slice instance according to an embodiment of the present application. Method 600 can be used in any of the network management architectures of Figures 1-4. Figure 6 shows a network slice management process for switching a failed NSSI to a redundant NSSI. The first network device in the method 500 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module. The second network device in method 600 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 the same NSSMF module.
如图6所示，该方法600包括：As shown in FIG. 6, the method 600 includes:
S601、NS-SH-MMF配置NS-SH-IF需要执行的自愈算法。具体来说，对于切换到冗余NSSI的自愈机制，配置的内容包括NSI的身份标识，该NSI的故障修复需求，该NSI创建时分配和/或创建的冗余NSSI的身份标识，冗余NSSI和组成该NSI的NSSI的对应 关系，切换到冗余NSSI的触发规则包括事件、故障类型和条件等。需要说明的是，冗余NSSI和组成NSI的NSSI之间可能不是一一对应的关系，例如，冗余NSSI可能可以作为若干NSSI中的任意一个的冗余替代，一个冗余NSSI可能可以作为若干NSI中的若干同类型NSSI的冗余替代。S601 and NS-SH-MMF configure the self-healing algorithm that NS-SH-IF needs to perform. Specifically, for the self-healing mechanism for switching to the redundant NSSI, the configured content includes the identity of the NSI, the fault repair requirement of the NSI, the identity of the redundant NSSI allocated and/or created when the NSI is created, and redundancy. The mapping relationship between the NSSI and the NSSI constituting the NSI, the triggering rules for switching to the redundant NSSI include an event, a fault type, and a condition. It should be noted that there may not be a one-to-one correspondence between the redundant NSSI and the NSSI constituting the NSI. For example, the redundant NSSI may be replaced by redundancy of any one of several NSSIs, and one redundant NSSI may be used as a number of Redundant replacement of several NSSIs of the same type in the NSI.
S602、组成NSI的一个NSSI发生故障，影响NSI的正常运行。在本申请实施例中，假设NSSI 1发生故障，它由NSSMF 1负责管理。NSSMF 1生成网络切片子网实例故障告警并通过接口2上报给NS-SH-MMF。NS-SH-MMF收到来自NSSMF 1的故障告警。故障告警中包含了至少以下一项内容：故障告警ID，NSSI的ID，故障发生的时间，故障类型，故障原因，故障源，故障严重性，故障对服务产生的影响，可采取的修复方式等。S602. An NSSI that constitutes an NSI fails, which affects the normal operation of the NSI. In the embodiment of the present application, assuming that NSSI 1 fails, it is managed by NSSMF 1. The NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
S603、NS-SH-MMF依据故障告警判断满足自愈触发条件，向NS-SH-IF发送自愈触发命令。NS-SH-IF收到自愈触发命令。S603 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF. The NS-SH-IF receives a self-healing trigger command.
S604、NS-SH-IF收集相关网络切片实例和网络切片子网实例的信息，收集信息包括至少以下一项内容：a)NS-SH-IF通过接口2向NSSMF 1发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 1上报的性能数据和阈值测量结果；b)NS-SH-IF向和NSSI 1存在交互的其他网络切片子网实例(本申请实施例假设为NSSI 3，由NSSMF 3管理)的管理功能，即NSSMF 3发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 3上报的性能数据和阈值测量结果；c)NS-SH-IF依据自愈配置找到故障NSSI对应的冗余NSSI，通过接口5从NS Repository中读取其目前状态(可能的状态包括注销、激活、已终结、无法使用等)，本申请实施例假设NSSI 1的冗余网络切片子网络实例是NSSI 2，NSSI 2由NSSMF 2管理；d)NS-SH-IF通过接口2向NSSMF 2发送测试任务，NSSMF 2执行测试任务并通过接口2向NS-SH-IF报告测试结果；e)NS-SH-IF通过接口5从NS Repository中读取NSSI 1正常运行时的配置信息，包括SLA，在网络切片实例的逻辑拓扑中的位置、接口信息；f)NS-SH-IF通过接口2从NSSMF 1处获取NSSI 1上正在运行的服务信息，包括用户数据，配置等；g)NS-SH-IF通过接口5从NS Repository中读取NSSI 1的历史故障信息，采取的修复动作，修复结果，读取和NSSI 1同类型的其他网络切片子网实例的故障信息，采取的修复动作，修复结果等。依据收集到的信息和步骤S601中配置的自愈算法，NS-SH-IF决定用冗余NSSI 2替换故障NSSI 1。The S604 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following items: a) the NS-SH-IF sends the performance measurement task to the NSSMF 1 through the interface 2, and the threshold measurement is performed. The NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the other network slice subnet instance in which the NS-SH-IF interacts with the NSSI 1 (the embodiment of the present application assumes the NSSI) 3, management function managed by NSSMF 3, that is, NSSMF 3 transmits performance measurement tasks and threshold measurement tasks, and NS-SH-IF receives performance data and threshold measurement results reported by NSSMF 3 through interface 2; c) NS-SH-IF The redundancy NSSI corresponding to the faulty NSSI is found according to the self-healing configuration, and the current state is read from the NS Repository through the interface 5 (the possible states include logout, activation, termination, unusability, etc.), and the embodiment of the present application assumes NSSI 1 The redundant network slice sub-network instance is NSSI 2, NSSI 2 is managed by NSSMF 2; d) NS-SH-IF sends test tasks to NSSMF 2 through interface 2, NSSMF 2 performs test tasks and passes through interface 2 to NS-SH-IF Report test results; e The NS-SH-IF reads the configuration information of the NSSI 1 during normal operation from the NS Repository through the interface 5, including the SLA, the location and interface information in the logical topology of the network slice instance; f) the NS-SH-IF through the interface 2 Obtain the service information running on the NSSI 1 from the NSSMF 1, including the user data, configuration, etc.; g) The NS-SH-IF reads the historical fault information of the NSSI 1 from the NS Repository through the interface 5, and the repair action taken, Fix the result, read the fault information of other network slicing subnet instances of the same type as NSSI 1, take the repair action, repair the results, and so on. Based on the collected information and the self-healing algorithm configured in step S601, the NS-SH-IF decides to replace the failed NSSI 1 with the redundant NSSI 2.
S605、可选地，NS-SH-IF通过接口5将NSSI 1的相关配置信息、逻辑拓扑位置、用户服务信息等备份至NS Repository，以便在故障自愈失败时复原。S605. Optionally, the NS-SH-IF backs up the related configuration information, the logical topology location, the user service information, and the like of the NSSI 1 to the NS Repository through the interface 5, so as to be restored when the fault self-healing fails.
S606、如果当前NSSI 1的状态为激活状态，则NS-SH-IF注销NSSI 1。注销包括将NSSI 1在NSS Repository和/或NS Repository中的状态标记为注销态，通知NSSMF 1停止NSSI 1上运行的服务。S606. If the current state of NSSI 1 is an active state, the NS-SH-IF logs out NSSI 1. Logging out includes marking the status of NSSI 1 in the NSS Repository and/or NS Repository as a logout state, informing NSSMF 1 to stop the service running on NSSI 1.
S607、可选地，NS-SH-IF通过接口2向NSSMF 2发送配置NSSI 2的命令，配置消息至少包括应用参数，在网络拓扑中的位置，和其他NSSI之间的接口信息等。需要说明的是，此处的配置内容可能和步骤S604中NS-SH-IF收集的NSSI 1正确运行时的配置相一致，也可能不同。为了保证网络切片实例的高可靠性，冗余的网络切片子网实例可能是某个NSSI专属的，在这种情况下，创建该冗余NSSI时即对它进行相应配置，修改对应的NSSI配置时，NSMF也会同时通知该冗余NSSI的管理器相应地修改配置，用以在发送故障时提供切换速度，保证高可靠性，在这种情况下，步骤S607可以不是必须的。此 外，当冗余NSSI可以替换若干个NSSI时，这些NSSI可能属于同一NSI，也可能属于不同NSI，这种情况下，冗余NSSI不会在自愈机制触发前被配置，此时步骤S607是必要步骤。S607. Optionally, the NS-SH-IF sends a command for configuring the NSSI 2 to the NSSMF 2 through the interface 2. The configuration message includes at least an application parameter, a location in the network topology, and interface information between the other NSSIs. It should be noted that the configuration content here may be consistent with the configuration when the NSSI 1 collected by the NS-SH-IF in step S604 is correctly operated, or may be different. In order to ensure high reliability of the network sharding instance, the redundant network tiling subnet instance may be specific to an NSSI. In this case, when the redundant NSSI is created, it is configured accordingly, and the corresponding NSSI configuration is modified. At the same time, the NSMF also informs the manager of the redundant NSSI to modify the configuration accordingly to provide the switching speed when transmitting the fault, and to ensure high reliability. In this case, step S607 may not be necessary. In addition, when the redundant NSSI can replace several NSSIs, the NSSIs may belong to the same NSI or may belong to different NSIs. In this case, the redundant NSSIs are not configured before the self-healing mechanism is triggered. In this case, step S607 is The necessary steps.
S608、NS-SH-IF通过接口2向NSSMF 3发送配置NSSI 3的命令，将NSSI 3和NSSI 2相关联，配置消息至少包括以下一项内容：应用参数变化，在网络拓扑中的位置变化，和NSSI 2之间的接口信息等。S608, the NS-SH-IF sends a command for configuring the NSSI 3 to the NSSMF 3 through the interface 2, and associates the NSSI 3 with the NSSI 2. The configuration message includes at least one of the following: the application parameter change, the location change in the network topology, Interface information between NSSI 2 and so on.
S609、NS-SH-IF激活NSSI 2。激活包括将NSSI 2在NSS Repository和/或NS Repository中的状态标记为激活态，通知NSSMF 2启动NSSI 2并载入步骤S604中获取的NSSI 1上的用户服务信息以便恢复业务。S609, NS-SH-IF activates NSSI 2. Activation includes marking the status of NSSI 2 in the NSS Repository and/or NS Repository as an active state, notifying NSSMF 2 to initiate NSSI 2 and loading the user service information on NSSI 1 obtained in step S604 to resume the service.
S610、NS-SH-IF收集网络切片实例的信息并评估自愈结果。收集信息包括至少以下一项内容：NS-SH-IF通过接口2给NSSMF 2和NSSMF 3分别下发对于NSSI 2和NSSI 3的性能测量、阈值监控任务，NSSMF 2和NSSMF 3执行性能测量、阈值监控任务，并通过接口2上报给NS-SH-IF性能测量结果和/或超过阈值告警。S610, NS-SH-IF collects information of the network slice instance and evaluates the self-healing result. The information collected includes at least one of the following items: NS-SH-IF delivers performance measurement and threshold monitoring tasks for NSSI 2 and NSSI 3 to NSSMF 2 and NSSMF 3 through interface 2, and performs performance measurement and thresholds for NSSMF 2 and NSSMF 3 respectively. Monitor the task and report it to the NS-SH-IF performance measurement result and/or exceed the threshold alarm through interface 2.
S611、如果步骤S606至步骤S609有任意一步失败，或步骤S610中NS-SH-IF收集到的信息表明切换冗余NSSI后网络切片服务无法正常运行，则触发复原动作。具体来说，NS-SH-IF读取步骤S605中保存的自愈动作执行前的网络状态和配置，依此配置NSSI 3和NSSI 1，并激活NSSI 1。S611. If any step of step S606 to step S609 fails, or the information collected by the NS-SH-IF in step S610 indicates that the network slice service cannot be operated normally after switching the redundant NSSI, the recovery action is triggered. Specifically, the NS-SH-IF reads the network state and configuration before the self-healing action held in step S605, configures NSSI 3 and NSSI 1, and activates NSSI 1.
S612、NS-SH-IF通过接口5更新NS Repository中网络切片实例的运行状态，拓扑信息，配置信息等，并记录步骤S606至步骤S611的自愈动作，记录故障信息和自愈结果。需要说明的是，即使以上自愈动作未能成功修复故障，恢复服务，也需记录相应自愈动作，故障信息和自愈结果。S612 and NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions in steps S606 to S611, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
S613、NS-SH-IF向NS-SH-MMF报告采用的自愈动作和自愈结果。NS-SH-MMF通过接口1向SMF上报故障信息，自愈动作和自愈结果。S613 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF. The NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
在本申请实施例中，在组成网络切片实例的网络切片子网实例发生故障时，可以无需人工干预地自动切换到冗余的网络切片子网实例上，同时尽可能保证服务的连贯和一致性，提高了网络切片实例整体的可靠性。同时，本申请实施例的方法还可在自愈失败时恢复对网络切片实例的修改使运营商能关注于原始的错误。此外，本申请实施例提供的方法记录了故障信息、自愈动作和自愈结果可以为网络切片实例的自动化运维决策提供参考，使***更智能、快捷地处理同一类型的网络故障。In the embodiment of the present application, when the network slice subnet instance constituting the network slice instance fails, it can automatically switch to the redundant network slice subnet instance without manual intervention, and ensure the continuity and consistency of the service as much as possible. , improve the overall reliability of the network slice instance. In the meantime, the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error. In addition, the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly.
需要说明的是，本申请实施例的管理网络切片的方法可以适用于网络切片实例由网络切片子网实例构成的应用场景，解决网络切片子网实例发生无法自愈的故障时，可能采取的一种网络切片层面的自愈机制。本申请实施例涉及的流程与方法也适用于网络切片实例由网络功能构成的应用场景下，解决网络功能发生无法自愈的故障时，可能采取的一种将故障的网络功能切换为冗余网络功能的自愈机制，切换为冗余网络功能的自愈机制的流程和步骤和本申请实施例中的流程步骤相类似，各模块间的交互信息中将网络切片子网实例的信息替换为相应的网络功能的信息即可。It should be noted that the method for managing a network slice in the embodiment of the present application may be applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and may be used when a network slice subnet instance fails to self-heal. Self-healing mechanism at the network slice level. The processes and methods involved in the embodiments of the present application are also applicable to an application scenario in which a network sharding instance is composed of network functions, and when a network function fails to be self-healing, a faulty network function may be switched to a redundant network. The self-healing mechanism of the function, the process and the step of switching to the self-healing mechanism of the redundant network function are similar to the process steps in the embodiment of the present application, and the information of the network slice subnet instance is replaced with the corresponding information in the interaction information between the modules. The information about the network function can be.
需要说明的是，本申请实施例中使用的NSSI 1，NSSI 2，NSSI 3和NSSMF 1，NSSMF 2，NSSMF 3仅是为了举例说明的需要，本申请的方法不限定故障网络切片子网实例的个数，和故障网络切片子网实例存在交互的网络切片子网实例的个数，冗余的网络切片子网 实例的个数。例如，一个故障网络切片子网实例可能需要由若干个冗余网络切片子网实例同时替代。此外，故障NSSI，冗余NSSI，存在交互的其他NSSI可能由不同的NSSMF管理，也可能由一个NSSMF同时管理，本申请对此不作限定。It should be noted that the NSSI 1, NSSI 2, NSSI 3, and NSSMF 1, NSSMF 2, and NSSMF 3 used in the embodiments of the present application are only for the purpose of illustration. The method of the present application does not limit the faulty network slice subnet instance. Number, the number of network slicing subnet instances that interact with the failed network slicing subnet instance, and the number of redundant network slicing subnet instances. For example, a failed network slice subnet instance may need to be replaced by several redundant network slice subnet instances. In addition, the faulty NSSI, the redundant NSSI, and the other NSSIs in the presence of the 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.
作为一个具体示例，图7示出了本申请实施例的管理网络切片实例的方法700的示意性流程图。方法700可以用于图1至图4中的任一网络管理架构中。图7示出了将自动创建新的NSSI以替换故障NSSI的网络切片管理过程。其中，方法500中的第一网络设备可以包括NS_SH_IF模块或NSMF模块，NSMF模块包括NS_SH_MMF和NS_SH_IF模块。方法500中的第二网络设备可以包括NSSMF2模块、第三网络设备可以包括NSSMF1模块、第四网络设备可以包括NSSMF3模块。其中，第三网络设备至第四网络设备可以分别是单独的NSSMF模块，也可以是同一个NSSMF模块。As a specific example, FIG. 7 shows a schematic flowchart of a method 700 for managing a network slice instance according to an embodiment of the present application. Method 700 can be used in any of the network management architectures of Figures 1-4. Figure 7 shows a network slice management process that will automatically create a new NSSI to replace the failed NSSI. The first network device in the method 500 may include an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module. The second network device in method 500 can include an NSSMF2 module, the third network device can include an NSSMF1 module, and the fourth network device can include an NSSMF3 module. The third network device to the fourth network device may be separate NSSMF modules or the same NSSMF module.
如图7所示，该方法700包括：As shown in FIG. 7, the method 700 includes:
S701、NS-SH-MMF配置NS-SH-IF需要执行的自愈算法。具体来说，对于创建新NSSI来替换故障NSSI的自愈机制，配置的内容包括NSI的身份标识，该NSI的故障修复需求，可创建新NSSI来替换故障NSSI的NSSMF的身份标识及创建的可行性，创建新NSSI取代故障NSSI的触发规则包括事件、故障类型和条件等。需要说明的是，随着网络条件的变化，例如网络资源使用情况的变化，NS-SH-MMF可能随时更新NS-SH-IF对自愈算法的配置。S701 and NS-SH-MMF configure the self-healing algorithm that NS-SH-IF needs to perform. Specifically, for the self-healing mechanism for creating a new NSSI to replace the faulty NSSI, the configuration includes the identity of the NSI, the fault repair requirement of the NSI, the new NSSI can be created to replace the identity of the NSSMF of the faulty NSSI, and the feasible creation is feasible. Sex, the trigger rules for creating a new NSSI to replace the faulty NSSI include events, fault types and conditions. It should be noted that NS-SH-MMF may update the configuration of the self-healing algorithm of NS-SH-IF at any time as network conditions change, such as changes in network resource usage.
S702、组成NSI的一个NSSI发生故障，影响网络切片实例的正常运行。在本申请实施例中，假设NSSI 1发生故障，它由NSSMF 1负责管理。NSSMF 1生成网络切片子网实例故障告警并通过接口2上报给NS-SH-MMF。NS-SH-MMF收到来自NSSMF 1的故障告警。故障告警中包含了至少以下一项内容：故障告警ID，NSSI的ID，故障发生的时间，故障类型，故障原因，故障源，故障严重性，故障对服务产生的影响，可采取的修复方式等。S702: An NSSI that constitutes an NSI fails, affecting the normal operation of the network slice instance. In the embodiment of the present application, assuming that NSSI 1 fails, it is managed by NSSMF 1. The NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
S703、NS-SH-MMF依据故障告警判断满足自愈触发条件，向NS-SH-IF发送自愈触发命令。NS-SH-IF收到自愈触发命令。S703 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF. The NS-SH-IF receives a self-healing trigger command.
S704、NS-SH-IF收集相关网络切片实例和网络切片子网实例的信息，收集信息包括至少以下一项内容：a)NS-SH-IF通过接口2向NSSMF 1发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 1上报的性能数据和阈值测量结果；b)NS-SH-IF向和NSSI 1存在交互的其他网络切片子网实例(本申请实施例假设为NSSI 3，由NSSMF 3管理)的管理功能，即NSSMF 3发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 3上报的性能数据和阈值测量结果；c)NS-SH-IF依据自愈配置找到可创建新NSSI取代故障NSSI的相应管理模块，本申请实施例假设其为NSSMF 3，NS-SH-IF通过接口2向NSSMF 3发送创建新NSSI的可行性检查请求；d)NS-SH-IF通过接口5从NS Repository中读取NSSI 1正常运行时的配置信息，包括SLA，在网络切片实例的逻辑拓扑中的位置、接口信息；e)NS-SH-IF通过接口2从NSSMF 1处获取NSSI 1上正在运行的服务信息，包括用户数据，配置等；f)NS-SH-IF通过接口5从NS Repository中读取NSSI 1的历史故障信息，采取的修复动作，修复结果，读取和NSSI 1同类型的其他网络切片子网实例的故障信息，采取的修复动作，修复结果等。依据收集到的信息和步骤S701中配置的自愈算法，NS-SH-IF决定创建新NSSI取代故障NSSI。The S704 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following contents: a) the NS-SH-IF sends the performance measurement task to the NSSMF 1 through the interface 2, and the threshold measurement is performed. The NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the other network slice subnet instance in which the NS-SH-IF interacts with the NSSI 1 (the embodiment of the present application assumes the NSSI) 3, management function managed by NSSMF 3, that is, NSSMF 3 transmits performance measurement tasks and threshold measurement tasks, and NS-SH-IF receives performance data and threshold measurement results reported by NSSMF 3 through interface 2; c) NS-SH-IF According to the self-healing configuration, a corresponding management module that can create a new NSSI instead of a faulty NSSI is found. The embodiment of the present application assumes that it is an NSSMF 3, and the NS-SH-IF sends a feasibility check request for creating a new NSSI to the NSSMF 3 through the interface 2; d) The NS-SH-IF reads the configuration information of the NSSI 1 during normal operation from the NS Repository through the interface 5, including the SLA, the location and interface information in the logical topology of the network slice instance; e) the NS-SH-IF through the interface 2 Get NSSI 1 from NSSMF 1 Running service information, including user data, configuration, etc.; f) NS-SH-IF reads the historical fault information of NSSI 1 from NS Repository through interface 5, takes the repair action, repairs the result, and reads with NSSI 1 Type of other network slicing subnet instance for fault information, taking repair actions, repairing results, etc. 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 faulty NSSI.
S705、可选地，NS-SH-IF通过接口5将NSSI 1的相关配置信息、逻辑拓扑位置、用户服务信息等备份至NS Repository，以便在故障自愈失败时复原。S705. Optionally, the NS-SH-IF backs up the related configuration information, the logical topology location, the user service information, and the like of the NSSI 1 to the NS Repository through the interface 5, so as to be restored when the fault self-healing fails.
S706、NS-SH-IF通过接口2向NSSMF 2发送创建NSSI请求。该创建请求中至少需包括：新创建的NSSI的类型，包含的功能，需满足的SLA，所占用的网络资源等。NSSMF 2依据接收到的请求创建NSSI 2。S706. The NS-SH-IF sends an NSSI request to the NSSMF 2 through the interface 2. The creation request includes at least the type of the newly created NSSI, the functions included, the SLA to be satisfied, and the network resources occupied. NSSMF 2 creates NSSI 2 based on the received request.
S707、NS-SH-IF通过接口2向NSSMF 2发送配置NSSI 2的命令，配置消息至少包括应用参数，在网络拓扑中的位置，和其他NSSI之间的接口信息等。需要说明的是，此处的配置内容可能和步骤S704中NS-SH-IF收集的NSSI 1正确运行时的配置相一致，也可能因为网络切片子网实例的实现不同而有所不同。S707. The NS-SH-IF sends a command to configure the NSSI 2 to the NSSMF 2 through the interface 2. The configuration message includes at least an application parameter, a location in the network topology, and interface information between other NSSIs. It should be noted that the configuration content here may be consistent with the configuration when the NSSI 1 collected by the NS-SH-IF in step S704 is correctly operated, or may be different due to the implementation of the network slice subnet instance.
S708、如果当前NSSI 1的状态为激活状态，则NS-SH-IF注销NSSI 1。注销包括将NSSI 1在NSS Repository和/或NS Repository中的状态标记为注销态，通知NSSMF 1停止NSSI 1上运行的服务。S708. If the current state of NSSI 1 is an active state, the NS-SH-IF logs out NSSI 1. Logging out includes marking the status of NSSI 1 in the NSS Repository and/or NS Repository as a logout state, informing NSSMF 1 to stop the service running on NSSI 1.
S709、NS-SH-IF通过接口2向NSSMF 3发送配置NSSI 3的命令，将NSSI 3和NSSI 2相关联，配置消息至少包括以下一项内容：应用参数变化，在网络拓扑中的位置变化，和NSSI 2之间的接口信息等。S709, the NS-SH-IF sends a command to configure the NSSI 3 to the NSSMF 3 through the interface 2, and associates the NSSI 3 with the NSSI 2. The configuration message includes at least one of the following: the application parameter change, the location change in the network topology, Interface information between NSSI 2 and so on.
S710、NS-SH-IF激活NSSI 2。激活包括将NSSI 2在NSS Repository和/或NS Repository中的状态标记为激活态，通知NSSMF 2启动NSSI 2并载入步骤S704中获取的NSSI 1上的用户服务信息以便恢复业务。S710, NS-SH-IF activates NSSI 2. Activation includes marking the status of NSSI 2 in the NSS Repository and/or NS Repository as an active state, notifying NSSMF 2 to initiate NSSI 2 and loading the user service information on NSSI 1 obtained in step S704 to resume the service.
S711、NS-SH-IF收集网络切片实例的信息并评估自愈结果。收集信息包括至少以下一项内容：NS-SH-IF通过接口2给NSSMF 2和NSSMF 3分别下发对于NSSI 2和NSSI 3的性能测量、阈值监控任务，NSSMF 2和NSSMF 3执行性能测量、阈值监控任务，并通过接口2上报给NS-SH-IF性能测量结果和/或超过阈值告警。S711 and NS-SH-IF collect information of network slice instances and evaluate self-healing results. The information collected includes at least one of the following items: NS-SH-IF delivers performance measurement and threshold monitoring tasks for NSSI 2 and NSSI 3 to NSSMF 2 and NSSMF 3 through interface 2, and performs performance measurement and thresholds for NSSMF 2 and NSSMF 3 respectively. Monitor the task and report it to the NS-SH-IF performance measurement result and/or exceed the threshold alarm through interface 2.
S712、如果步骤S706至步骤S710有任意一步失败，或步骤S711中NS-SH-IF收集到的信息表明新创建的NSSI 2无法替换故障的NSSI 1正常运行，则触发复原动作。具体来说，NS-SH-IF读取步骤S705中保存的自愈动作执行前的网络状态和配置，依此重配置NSSI 3和NSSI 1，并激活NSSI 1。S712. If any step of step S706 to step S710 fails, or the information collected by the NS-SH-IF in step S711 indicates that the newly created NSSI 2 cannot replace the faulty NSSI 1 for normal operation, the recovery action is triggered. Specifically, the NS-SH-IF reads the network state and configuration before the self-healing action stored in step S705, and reconfigures NSSI 3 and NSSI 1, and activates NSSI 1.
S713、NS-SH-IF通过接口5更新NS Repository中网络切片实例的运行状态，拓扑信息，配置信息等，并记录步骤S706至步骤S712的自愈动作，记录故障信息和自愈结果。需要说明的是，即使以上自愈动作未能成功修复故障，恢复服务，也需记录相应自愈动作，故障信息和自愈结果。S713 and NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions of steps S706 to S712, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
S714、NS-SH-IF向NS-SH-MMF报告采用的自愈动作和自愈结果。NS-SH-MMF通过接口1向SMF上报故障信息，自愈动作和自愈结果。S714 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF. The NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
在本申请实施例中，在组成网络切片实例的网络切片子网实例发生故障时，可以无需人工干预地自动创建新的网络切片子网实例取代故障网络切片子网实例来恢复服务，同时尽可能保证服务的连贯和一致性，提高了网络切片实例整体的可靠性。同时，本申请实施例的方法还可在自愈失败时恢复对网络切片实例的修改使运营商能关注于原始的错误。此外，本申请实施例提供的方法记录了故障信息、自愈动作和自愈结果可以为网络切片实例的自动化运维决策提供参考，使***更智能、快捷地处理同一类型的网络故障。In the embodiment of the present application, when the network slice subnet instance constituting the network slice instance fails, a new network slice subnet instance can be automatically created instead of the manual network slice subnet instance to restore the service without manual intervention. Ensure the consistency and consistency of the service, and improve the overall reliability of the network slice instance. In the meantime, the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error. In addition, the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly.
需要说明的是，本申请实施例适用于网络切片实例由网络切片子网实例构成的应用场 景，解决网络切片子网实例发生无法自愈的故障时，可能采取的一种网络切片层面的自愈机制。本申请实施例涉及的流程与方法也适用于网络切片实例由网络功能构成的应用场景下，解决网络功能发生无法自愈的故障时，可能采取的一种创建新网络功能并取代故障网络功能的自愈机制，创建新网络功能的自愈机制的流程和步骤和本申请实施例中的流程步骤相类似，各模块间的交互信息中将网络切片子网实例的信息替换为相应的网络功能的信息即可。It should be noted that the embodiment of the present application is applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and a network slice level self-healing may be adopted when a network sliced subnet instance fails to self-heal. mechanism. The processes and methods involved in the embodiments of the present application are also applicable to an application scenario in which a network segmentation instance is composed of network functions, and when a network function fails to be self-healing, a new network function may be adopted and the faulty network function may be replaced. The self-healing mechanism, the process and the steps of creating a self-healing mechanism of the new network function are similar to the process steps in the embodiment of the present application, and the information of the network slice subnet instance is replaced with the corresponding network function in the interaction information between the modules. Information can be.
另外，本申请实施例中使用的NSSI 1，NSSI 2，NSSI 3和NSSMF 1，NSSMF 2，NSSMF 3仅是为了举例说明的需要，本申请的方法不限定故障网络切片子网实例的个数，和故障网络切片子网实例存在交互的网络切片子网实例的个数，新创建的网络切片子网实例的个数。例如，一个故障网络切片子网实例可能需要创建若干个网络切片子网实例来替代。此外，故障NSSI，新NSSI，存在交互的其他NSSI可能由不同的NSSMF管理，也可能由一个NSSMF同时管理，本申请对此不作限定。In addition, the NSSI 1, NSSI 2, NSSI 3, and NSSMF 1, NSSMF 2, and NSSMF 3 used in the embodiments of the present application are only for the purpose of illustration. The method of the present application does not limit the number of faulty network slice subnet instances. Number of network slicing subnet instances that interact with the failed network slicing subnet instance, and the number of newly created network slicing subnet instances. For example, a failed network slice subnet instance might need to create several network slice subnet instances instead. In addition, the faulty NSSI, the new NSSI, and other NSSIs that have interactions may be managed by different NSSMFs, or may be managed by one NSSMF at the same time, which is not limited in this application.
图8是本申请实施例的管理网络切片实例的方法800的示意性流程图。方法800可以适用于图1至图4所示的网络管理架构。图8中的第一网络设备可以是NS_SH_IF模块或NSMF模块，NSMF模块包括NS_SH_MMF和NS_SH_IF模块。第二网络设备可以是NSSMF模块。存储设备可以是NS Repository。为了简洁，方法800中与前文相同或相似的内容请参考前文相应的内容，此处不再赘述。FIG. 8 is a schematic flowchart of a method 800 for managing a network slice instance according to an embodiment of the present application. Method 800 can be applied to the network management architecture illustrated in Figures 1-4. The first network device in FIG. 8 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module. The second network device can be an NSSMF module. The storage device can be an NS Repository. For the sake of brevity, please refer to the corresponding content in the method 800 for the same or similar content as the foregoing, and details are not described herein again.
如图8所示，方法800包括：As shown in FIG. 8, method 800 includes:
S801、第一网络设备确定第一网络切片子网实例出现故障。S801. The first network device determines that the first network slice subnet instance is faulty.
上述第一网络设备可以是用于管理和监控多个网络切片子网实例的模块。例如，第一网络设备可以是NSMF模块。例如，上述第一网络设备用于管理和监控网络切片实例，该网络切片实例包括所述第一网络切片子网实例。The first network device may be a module for managing and monitoring multiple network slice subnet instances. For example, the first network device can be an NSMF module. For example, the first network device is configured to manage and monitor a network slice instance, and the network slice instance includes the first network slice subnet instance.
可选地，第一网络设备确定第一网络切片子网实例出现故障有多种方式。例如，在一种方式中，第一网络设备可以接收第二网络设备的故障报警信息，该故障报警信息用于指示第一网络切片子网实例出现故障。在第二种方式中，第一网络设备可以接收第五网络设备的触发自愈信息，该触发自愈信息可以是在第一网络切片子网实例满足自愈触发条件的情况下发送的。其中，在第二种方式中，该第一网络设备可以是NS_SH_IF模块，该第五网络设备可以是NS_SH_MMF模块。Optionally, the first network device determines that the first network slice subnet instance fails. For example, in one mode, the first network device may receive fault alarm information of the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty. In the second mode, the first network device may receive the trigger self-healing information of the fifth network device, where the trigger self-healing information may be sent if the first network slice subnet instance satisfies the 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.
S802、所述第一网络设备向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备对所述第一网络切片子网实例执行回退处理。S802. The first network device sends the first indication information to the second network device, where the first indication information is used to instruct the second network device to perform a rollback process on the first network slice subnet instance.
可选地，上述回退处理，可以理解为将第一网络切片子网实例的配置参数重新设置为当前时刻之前的某一时刻的配置参数。该当前时刻之前的某一时刻的配置参数可以为历史配置参数。Optionally, the foregoing backoff process may be understood as resetting a configuration parameter of the first network slice subnet instance to a configuration parameter at a certain moment before the current time. The configuration parameter at a certain moment before the current moment may be a historical configuration parameter.
在本申请实施例中，第一网络设备在确定第一网络切片子网实例出现故障的情况下，可以指示第二网络设备对所述第一网络切片子网实例执行回退处理，从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。In the embodiment of the present application, the first network device, when determining that the first network slice subnet instance is faulty, may instruct the second network device to perform a rollback process on the first network sliced subnet instance, thereby being flexible. Manage network segmentation instances to improve the efficiency of managing network slice instances.
可选地，方法800还包括：所述第一网络设备获取所述第一网络切片子网实例的历史参数信息；所述第一网络设备基于所述第一网络切片子网实例的历史参数信息，确定所述第一指示信息。Optionally, the method 800 further includes: the first network device acquiring historical parameter information of the first network slice subnet instance; the first network device is based on historical parameter information of the first network slice subnet instance Determining the first indication information.
作为一个示例，所述第一网络设备还可以获取第一网络切片子网实例所述的网络切片实例的历史参数信息。例如，历史参数信息可以包括相关网络切片实例和网络切片子网实例的信息，包括至少以下一项内容：As an example, the first network device may further acquire historical parameter information of the network slice instance described by the first network slice subnet instance. For example, the historical parameter information may include information about an associated network slice instance and a network sliced subnet instance, including at least one of the following:
a)NS-SH-IF通过接口2向NSSMF 1发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 1上报的性能数据和阈值测量结果；a) The NS-SH-IF sends the performance measurement task and the threshold measurement task to the NSSMF 1 through the interface 2, and the NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2;
b)NS-SH-IF向和NSSI 1存在交互的其他网络切片子网实例的管理功能，即NSSMF 3发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 3上报的性能数据和阈值测量结果；b) The management function of the NS-SH-IF to the other network slicing subnet instance that interacts with the NSSI 1, that is, the NSSMF 3 transmits the performance measurement task and the threshold measurement task, and the NS-SH-IF receives the performance reported by the NSSMF 3 through the interface 2. Data and threshold measurements;
c)NS-SH-IF依据自愈配置找到可创建新NSSI取代故障NSSI的相应管理模块，本申请实施例假设其为NSSMF 3，NS-SH-IF通过接口2向NSSMF 3发送创建新NSSI的可行性检查请求；c) NS-SH-IF finds a corresponding management module that can create a new NSSI instead of a faulty NSSI according to the self-healing configuration. The embodiment of the present application assumes that it is NSSMF 3, and the NS-SH-IF sends a new NSSI to the NSSMF 3 through the interface 2. Feasibility inspection request;
d)NS-SH-IF通过接口5从NS Repository中读取NSSI 1正常运行时的配置信息，包括SLA，在网络切片实例的逻辑拓扑中的位置、接口信息；d) The NS-SH-IF reads the configuration information of the NSSI 1 during normal operation, including the SLA, the location and interface information in the logical topology of the network slice instance, from the NS Repository through the interface 5;
e)NS-SH-IF通过接口2从NSSMF 1处获取NSSI 1上正在运行的服务信息，包括用户数据，配置等；e) The NS-SH-IF obtains the service information running on the NSSI 1 from the NSSMF 1 through the interface 2, including user data, configuration, and the like;
f)NS-SH-IF通过接口5从NS Repository中读取NSSI 1的历史故障信息，采取的修复动作，修复结果，读取和NSSI 1同类型的其他网络切片子网实例的故障信息，采取的修复动作，修复结果等。f) NS-SH-IF reads the historical fault information of NSSI 1 from the NS Repository through interface 5, takes the repair action, repairs the result, and reads the fault information of other network slice subnet instances of the same type as NSSI 1 Repair actions, fix results, etc.
可选地，方法800还包括：所述第一网络设备从所述第二网络设备获取所述第一网络切片子网实例的历史参数信息；所述第一网络设备将所述第一网络切片子网实例的历史参数信息备份至存储设备；所述第一网络设备获取所述第一网络切片子网实例的历史参数信息，包括：所述第一网络设备从所述存储设备获取所述第一网络切片子网实例的历史参数信息。Optionally, the method 800 further includes: the first network device acquiring historical parameter information of the first network slice subnet instance from the second network device; the first network device slices the first network The historical parameter information of the subnet instance is backed up to the storage device; the first network device acquiring the historical parameter information of the first network slice subnet instance, the first network device acquiring the first Historical parameter information of a network sliced subnet instance.
可选地，方法800还包括：在所述第一网络设备向第二网络设备发送第一指示信息之前，所述第一网络设备获取所述第一网络切片子网实例的当前参数信息；所述第一网络设备将所述第一网络切片子网实例的当前参数信息备份至存储设备。Optionally, the method 800 further includes: before the first network device sends the first indication information to the second network device, the first network device acquires current parameter information of the first network slice subnet instance; The first network device backs up current parameter information of the first network slice subnet instance to the storage device.
可选地，方法800还包括：在执行回退处理后的所述第一网络切片子网实例的性能不符合预定条件的情况下，所述第一网络设备向所述第二网络设备发送第二指示信息，所述第二指示信息用于指示所述第二网络设备基于备份至所述存储设备中的第一网络切片子网实例的所述当前参数信息，复原所述第一网络切片子网实例。Optionally, the method 800 further includes: sending, by the first network device, the second network device to the second network device, if the performance of the first network slice subnet instance after performing the rollback process does not meet a predetermined condition The second indication information is used to instruct the second network device to restore the first network slice based on the current parameter information backed up to the first network slice subnet instance in the storage device. Network instance.
可选地，方法800还包括：所述第一网络设备获取执行回退处理后的所述第一网络切片子网实例的性能信息，所述性能信息用于指示所述第一网络切片子网实例的性能；所述第一网络设备基于所述性能信息，确定所述第一网络切片子网实例的性能是否符合预定条件。Optionally, the method 800 further includes: the first network device acquiring performance information of the first network slice subnet instance after performing the rollback process, where the performance information is used to indicate the first network slice subnet Performance of the instance; the first network device determines, based on the performance information, whether performance of the first network slice subnet instance meets a predetermined condition.
可选地，方法800还包括：所述第一网络设备从所述第二网络设备接收故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障；所述第一网络设备确定第一网络切片子网实例出现故障，包括：所述第一网络设备根据所述故障报警信息确定所述第一网络切片子网实例。Optionally, the method 800 further includes: the first network device receiving fault alarm information from the second network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty; Determining, by the network device, that the first network slice subnet instance is faulty comprises: determining, by the first network device, the first network slice subnet instance according to the fault alarm information.
作为一个具体示例，图9示出了本申请实施例的管理网络切片实例的方法600的示意 性流程图。方法900可以用于图1至图4中的任一网络管理架构中。图9示出了将新建的NSSI替换故障的NSSI的网络切片管理过程。其中，方法800中的第一网络设备可以是是NS_SH_IF模块或NSMF模块，NSMF模块包括NS_SH_MMF和NS_SH_IF模块。第二网络设备可以是NSSMF模块。存储设备可以是NS Repository。As a specific example, FIG. 9 shows a schematic flowchart of a method 600 of managing a network slice instance in an embodiment of the present application. Method 900 can be used in any of the network management architectures of Figures 1-4. Figure 9 shows a network slice management process for replacing a newly created NSSI with a failed NSSI. The first network device in the method 800 may be an NS_SH_IF module or an NSMF module, and the NSMF module includes an NS_SH_MMF and an NS_SH_IF module. The second network device can be an NSSMF module. The storage device can be an NS Repository.
如图9所示，该方法900包括：As shown in FIG. 9, the method 900 includes:
S901、NS-SH-MMF配置NS-SH-IF需要执行的自愈算法。具体来说，对于网络切片实例修改、配置回退的自愈机制，配置的内容包括NSI的身份标识，该NSI的故障修复需求，对网络切片实例和网络切片子网实例的配置、状态等信息的备份需求，如备份时间周期，是否覆盖原备份等，网络切片实例修改、配置回退的触发规则包括事件、故障类型和条件等。需要说明的是，NS-SH-MMF可能随时更新NS-SH-IF的自愈算法的配置。S901 and NS-SH-MMF configure the self-healing algorithm that NS-SH-IF needs to perform. Specifically, for the self-healing mechanism of the network slice instance modification and the configuration rollback, the configuration includes the NSI identity, the NSI fault repair requirement, the configuration and status of the network slice instance and the network slice subnet instance. The backup requirements, such as the backup time period, whether to overwrite the original backup, etc., trigger rules for network slice instance modification and configuration rollback include events, fault types, and conditions. It should be noted that the NS-SH-MMF may update the configuration of the NS-SH-IF self-healing algorithm at any time.
S902、NS-SH-IF依据配置的自愈算法，判断是否需要创建或更新对网络切片实例信息的备份。触发备份的条件可能包括时间、事件、预期将发生的事件等。(事件是指对网络切片实例的修改、配置、用户行为变化等。)S902 and NS-SH-IF determine whether it is necessary to create or update a backup of the network slice instance information according to the configured self-healing algorithm. The conditions that trigger a backup may include time, events, events that are expected to occur, and so on. (Events refer to modifications, configurations, user behavior changes, etc. to network slice instances.)
S903、NS-SH-IF决定对网络切片实例的信息备份，通过接口2从NSSMF处获取NSSI的信息，这些信息可能包括当前NSSI的配置，它在网络拓扑中的位置，它和其他NSSI之间的接口信息，SLA，性能数据等。可选地，NS-SH-IF从NS Repository中读取已保存的NSSI的信息，并判断需要更新哪些信息。S903 and NS-SH-IF determine information backup of the network slice instance, and obtain NSSI information from the NSSMF through interface 2. The information may include the current NSSI configuration, its location in the network topology, and other NSSIs. Interface information, SLA, performance data, etc. Optionally, the NS-SH-IF reads the saved NSSI information from the NS Repository and determines which information needs to be updated.
S904、NS-SH-IF通过接口5在NS Repository中记录和/或更新组成NSI的各NSSI的信息。S904, NS-SH-IF records and/or updates information of each NSSI constituting the NSI in the NS Repository through the interface 5.
S905、组成NSI的一个NSSI发生故障，影响网络切片实例的正常运行。在本申请实施例中，假设NSSI 1发生故障，它由NSSMF 1负责管理。NSSMF 1生成网络切片子网实例故障告警并通过接口2上报给NS-SH-MMF。NS-SH-MMF收到来自NSSMF 1的故障告警。故障告警中包含了至少以下一项内容：故障告警ID，NSSI的ID，故障发生的时间，故障类型，故障原因，故障源，故障严重性，故障对服务产生的影响，可采取的修复方式等。S905: An NSSI that constitutes an NSI fails, affecting the normal operation of the network slicing instance. In the embodiment of the present application, assuming that NSSI 1 fails, it is managed by NSSMF 1. The NSSMF 1 generates a network segment subnet instance fault alarm and reports it to the NS-SH-MMF through interface 2. The NS-SH-MMF receives a fault alarm from NSSMF 1. The fault alarm contains at least one of the following: fault alarm ID, NSSI ID, time when the fault occurred, fault type, fault cause, fault source, fault severity, impact of the fault on the service, possible repair methods, etc. .
S906、NS-SH-MMF依据故障告警判断满足自愈触发条件，向NS-SH-IF发送自愈触发命令。NS-SH-IF收到自愈触发命令。S906 and NS-SH-MMF satisfy the self-healing trigger condition according to the fault alarm, and send a self-healing trigger command to the NS-SH-IF. The NS-SH-IF receives a self-healing trigger command.
S907、NS-SH-IF收集相关网络切片实例和网络切片子网实例的信息，收集信息包括至少以下一项内容：a)NS-SH-IF通过接口2向NSSMF 1发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收NSSMF 1上报的性能数据和阈值测量结果；b)NS-SH-IF向和NSSI 1存在交互的其他网络切片子网实例的管理功能发送性能测量任务、阈值测量任务，NS-SH-IF通过接口2接收上报的性能数据和阈值测量结果；c)NS-SH-IF通过接口5从NS Repository中读取NSSI 1正常运行时的备份信息，包括SLA，在网络切片实例的逻辑拓扑中的位置、接口信息等；d)NS-SH-IF通过接口5从NS Repository中读取NSSI 1的历史故障信息，采取的修复动作，修复结果，读取和NSSI 1同类型的其他网络切片子网实例的故障信息，采取的修复动作，修复结果。依据收集到的信息和步骤S901中配置的自愈算法，NS-SH-IF决定对NSSI 1采取回退动作并决定依据哪个时间点的备份信息执行回退。The S907 and the NS-SH-IF collect information about the network segment instance and the network slice subnet instance, and the collected information includes at least one of the following contents: a) The NS-SH-IF sends the performance measurement task and the threshold measurement to the NSSMF 1 through the interface 2. The NS-SH-IF receives the performance data and the threshold measurement result reported by the NSSMF 1 through the interface 2; b) the NS-SH-IF sends a performance measurement task to the management function of the other network slice subnet instance that interacts with the NSSI 1 The threshold measurement task, the NS-SH-IF receives the reported performance data and the threshold measurement result through the interface 2; c) the NS-SH-IF reads the backup information of the NSSI 1 during normal operation, including the SLA, from the NS Repository through the interface 5. Location, interface information, etc. in the logical topology of the network slice instance; d) NS-SH-IF reads the historical fault information of NSSI 1 from the NS Repository through interface 5, the repair action taken, the repair result, the read and the NSSI 1 The fault information of other network slicing subnet instances of the same type, the repair action taken, 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 on the NSSI 1 and decides which time point of the backup information to perform the rollback.
S908、可选地，NS-SH-IF通过接口5将NSSI 1的相关配置信息、逻辑拓扑位置、用 户服务信息等备份至NS Repository，以便在故障自愈失败时复原。S908. Optionally, the NS-SH-IF backs up the NSI 1 related configuration information, the logical topology location, the user service information, and the like to the NS Repository through the interface 5, so as to recover when the fault self-healing fails.
S909、NS-SH-IF通过接口2向NSSMF 1发送回退命令。依据网络故障的具体情况，回退命令可能包括：a)注销并终结新创建的NSSI 1，该命令需包括NSSI 1的身份标识；b)依据步骤7)得到的NSSI配置备份信息，重新配置NSSI 1；c)恢复对NSSI 1的修改，包括缩小扩展的容量，扩展缩小的容量，添加删除的网络功能，删除新增的网络功能等。当回退命令为创建并激活被终结的NSSI时，该回退命令可能不是发送给NSSMF 1的，而是其他NSSMF，该命令需包括NSSI的身份标识，配置信息，SLA，接口信息等。此外，当回退命令为创建被终结的NSSI时，NS-SH-IF还需向和所述NSSI有交互的其他NSSI的管理器发送配置消息。S909 and NS-SH-IF send a backoff command to NSSMF 1 through interface 2. According to the specific situation of the network fault, the rollback command may include: a) canceling and terminating the newly created NSSI 1, the command needs to include the identity of the NSSI 1, and b) reconfiguring the NSSI according to the NSSI configuration backup information obtained in step 7). 1; c) Restoring changes to NSSI 1, including reducing the expanded capacity, expanding the reduced capacity, adding deleted network functions, and deleting new network functions. When the backoff command is to create and activate the terminated NSSI, the backoff command may not be sent to the NSSMF 1, but other NSSMFs, and the command needs to include the NSSI identity, configuration information, SLA, interface information, and the like. In addition, when the backoff command is to create the terminated NSSI, the NS-SH-IF also needs to send a configuration message to the manager of other NSSIs that interact with the NSSI.
S910、NSSMF 1(或其他NSSMF)执行完相应动作并向NS-SH-IF反馈执行结果。S910, NSSMF 1 (or other NSSMF) perform the corresponding action and feed back the execution result to the NS-SH-IF.
S911、NS-SH-IF收集网络切片实例的信息并评估自愈结果。收集信息包括至少以下一项内容：NS-SH-IF通过接口2给NSSMF 1和/或其他NSSMF下发性能测量、阈值监控任务，相应NSSMF执行性能测量、阈值监控任务，并通过接口2上报给NS-SH-IF性能测量结果和/或超过阈值告警。S911, NS-SH-IF collects information on network slice instances and evaluates self-healing results. The information collected includes at least one of the following items: the NS-SH-IF sends performance measurement and threshold monitoring tasks to the NSSMF 1 and/or other NSSMFs through the interface 2, and the corresponding NSSMF performs performance measurement and threshold monitoring tasks, and reports them to the interface 2 through the interface 2 NS-SH-IF performance measurement results and / or alarms exceeding the threshold.
S912、如果回退失败，或步骤S911中NS-SH-IF收集到的信息表明回退后故障依然存在且没有好转，则NS-SH-IF启动复原回退动作造成的修改。具体来说，NS-SH-IF读取步骤S908中保存的自愈动作执行前的网络状态和配置，依此通知NSSMF 1重配置NSSI 1和/或恢复对NSSI 1的修改。S912. If the rollback fails, or the information collected by the NS-SH-IF in step S911 indicates that the fault still exists and does not improve after the rollback, the NS-SH-IF initiates the modification caused by the recovery backoff action. Specifically, the NS-SH-IF reads the network state and configuration before the self-healing action stored in step S908, and accordingly notifies the NSSMF 1 to reconfigure the NSSI 1 and/or restore the modification to the NSSI 1.
S913、NS-SH-IF通过接口5更新NS Repository中网络切片实例的运行状态，拓扑信息，配置信息等，并记录步骤S908至步骤S912的自愈动作，记录故障信息和自愈结果。需要说明的是，即使以上自愈动作未能成功修复故障，恢复服务，也需记录相应自愈动作，故障信息和自愈结果。The S913 and the NS-SH-IF update the running state, topology information, configuration information, and the like of the network slice instance in the NS Repository through the interface 5, and record the self-healing actions in steps S908 to S912, and record the fault information and the self-healing result. It should be noted that even if the above self-healing action fails to repair the fault and restore the service, it is necessary to record the corresponding self-healing action, fault information and self-healing result.
S914、NS-SH-IF向NS-SH-MMF报告采用的自愈动作和自愈结果。NS-SH-MMF通过接口1向SMF上报故障信息，自愈动作和自愈结果。S914 and NS-SH-IF report the self-healing action and self-healing result adopted to NS-SH-MMF. The NS-SH-MMF reports the fault information, self-healing action and self-healing result to the SMF through interface 1.
上文结合图1至图9详细描述了本申请实施例的管理网络切片的方法和网络管理架构，下文将结合图10至图17详细描述本申请实施例的网络设备。The method for managing a network slice and the network management architecture of the embodiment of the present application are described in detail above with reference to FIG. 1 to FIG. 9. The network device of the embodiment of the present application will be described in detail below with reference to FIG. 10 to FIG.
图10是本申请实施例的网络设备1000的示意性框图。应理解，网络设备1000能够执行图5至图7的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1000包括：处理单元1001和通信单元1002，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 various steps performed by the first network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition. The network device 1000 includes: a processing unit 1001 and a communication unit 1002,
所述处理单元1001用于确定第一网络切片子网实例出现故障；通过所述通信单元1002向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备对所述第一网络切片子网实例执行回退处理。The processing unit 1001 is configured to determine that the first network slice subnet instance is faulty, and send the first indication information to the second network device by using the communication unit 1002, where the first indication information is used to indicate the second network device Performing a fallback process on the first network slice subnet instance.
图11是本申请实施例的网络设备1100的示意性框图。应理解，网络设备1100能够执行图5至图7的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1100包括：处理单元1101和通信单元1102，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 can perform the various steps performed by the second network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition. The network device 1100 includes: a processing unit 1101 and a communication unit 1102,
所述处理单元1101用于通过所述通信单元1102从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换第一网络切片子网实例；根据所述第一指示信息，激活所述第二网络切片子网实例。The processing unit 1101 is configured to receive the first indication information from the first network device by using the communication unit 1102, where the first indication information is used to instruct the second network device to activate the second network slice subnet instance, where The second network slice subnet instance is configured to replace the first network slice subnet instance; and the second network slice subnet instance is activated according to the first indication information.
图12是本申请实施例的网络设备1200的示意性框图。应理解，网络设备1200能够执行图8或图9的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1200包括：处理单元1201和通信单元1202，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 the network device 1200 can perform the various steps performed by the first network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein. The network device 1200 includes: a processing unit 1201 and a communication unit 1202,
所述处理单元1201用于确定第一网络切片子网实例出现故障；通过所述通信单元1202向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备对所述第一网络切片子网实例执行回退处理。The processing unit 1201 is configured to determine that the first network slice subnet instance is faulty, and send the first indication information to the second network device by using the communication unit 1202, where the first indication information is used to indicate the second network device Performing a fallback process on the first network slice subnet instance.
图13是本申请实施例的网络设备1300的示意性框图。应理解，网络设备1300能够执行图8或图9的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1300包括：处理单元1301和通信单元1302，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 can perform the various steps performed by the second network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein. The network device 1300 includes: a processing unit 1301 and a communication unit 1302,
所述处理单元1301用于通过通信单元1302从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备对出现故障的第一网络切片子网实例执行回退处理；以及根据所述第一指示信息，对所述第一网络切片子网实例执行回退处理。The processing unit 1301 is configured to receive first indication information from the first network device by using the communication unit 1302, where the first indication information is used to instruct the second network device to perform back on the failed first network slice subnet instance. And performing a rollback process on the first network slice subnet instance according to the first indication information.
图14是本申请实施例的网络设备1400的示意性框图。应理解，网络设备1400能够执行图5至图7的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1400包括：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 can perform the various steps performed by the first network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition. Network device 1400 includes:
存储器1410，用于存储程序；a memory 1410, configured to store a program;
通信接口1420，用于和其他设备进行通信；a communication interface 1420, configured to communicate with other devices;
处理器1430，用于执行存储器1410中的程序，当所述程序被执行时，所述处理器1430用于确定第一网络切片子网实例出现故障；通过所述通信接口1420向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。The processor 1430 is configured to execute a program in the memory 1410, when the program is executed, the processor 1430 is configured to determine that the first network slice subnet instance is faulty; to the second network device by using the communication interface 1420 Sending the first indication information, where the first indication information is used to indicate that the second network device activates the second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice Subnet instance.
图15是本申请实施例的网络设备1500的示意性框图。应理解，网络设备1500能够执行图5至图7的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1500包括：FIG. 15 is a schematic block diagram of a network device 1500 according to an embodiment of the present application. It should be understood that the network device 1500 can perform the various steps performed by the second network device in the methods of FIGS. 5-7, which are not described in detail herein to avoid repetition. Network device 1500 includes:
存储器1510，用于存储程序；a memory 1510, configured to store a program;
通信接口1520，用于和其他设备进行通信；a communication interface 1520, configured to communicate with other devices;
处理器1530，用于执行存储器1510中的程序，当所述程序被执行时，所述处理器1530用于通过所述通信接口1520从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换第一网络切片子网实例；根据所述第一指示信息，激活所述第二网络切片子网实例。The processor 1530 is configured to execute a program in the memory 1510, when the program is executed, the processor 1530 is configured to receive, by using the communication interface 1520, first indication information from a first network device, where the first indication is The information is used to indicate that the second network device activates the second network slice subnet instance, where the second network slice subnet instance is used to replace the first network slice subnet instance; and activated according to the first indication information The second network slices a subnet instance.
图16是本申请实施例的网络设备1600的示意性框图。应理解，网络设备1600能够执行图8或图9的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1600包括：FIG. 16 is a schematic block diagram of a network device 1600 according to an embodiment of the present application. It should be understood that the network device 1600 can perform the various steps performed by the first network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein. Network device 1600 includes:
存储器1610，用于存储程序；a memory 1610, configured to store a program;
通信接口1620，用于和其他设备进行通信；a communication interface 1620, configured to communicate with other devices;
处理器1630，用于执行存储器1610中的程序，当所述程序被执行时，所述处理器1630用于确定第一网络切片子网实例出现故障；通过所述通信接口1620向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备对所述第一网络切片子网实例执行回退处理。The processor 1630 is configured to execute a program in the memory 1610, where the processor 1630 is configured to determine that the first network slice subnet instance is faulty; to the second network device by using the communication interface 1620. Sending the first indication information, where the first indication information is used to instruct the second network device to perform a rollback process on the first network slice subnet instance.
图17是本申请实施例的网络设备1700的示意性框图。应理解，网络设备1700能够执行图8或图9的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1700包括：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 the network device 1700 can perform the various steps performed by the second network device in the method of FIG. 8 or FIG. 9, in order to avoid repetition, which will not be described in detail herein. Network device 1700 includes:
存储器1710，用于存储程序；a memory 1710, configured to store a program;
通信接口1720，用于和其他设备进行通信；a communication interface 1720, configured to communicate with other devices;
处理器1730，用于执行存储器1710中的程序，当所述程序被执行时，所述处理器1730用于通过所述通信接口1720从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备对出现故障的第一网络切片子网实例执行回退处理；以及根据所述第一指示信息，对所述第一网络切片子网实例执行回退处理。The processor 1730 is configured to execute a program in the memory 1710, when the program is executed, the processor 1730 is configured to receive first indication information from the first network device by using the communication interface 1720, the first indication The information is used to instruct the second network device to perform a fallback process on the failed first network slice subnet instance; and perform a rollback process on the first network slice subnet instance according to the first indication information.
在本申请实施例中，在组成网络切片实例的网络切片子网实例发生故障时，可以无需人工干预地自动回退造成网络切片实例故障的配置和修改，即时修复故障，保证服务的连贯和一致性，提高了网络切片实例整体的可靠性。同时，本申请实施例的方法还可在自愈失败时恢复对网络切片实例的修改使运营商能关注于原始的错误。此外，本申请实施例提供的方法记录了故障信息、自愈动作和自愈结果可以为网络切片实例的自动化运维决策提供参考，使***更智能、快捷地处理同一类型的网络故障，还可避免日后对网络切片实例采取同样的配置、修改，产生同样的错误。In the embodiment of the present application, when the network slice subnet instance constituting the network slice instance fails, the configuration and modification of the network slice instance failure may be automatically rolled back without manual intervention, and the fault is repaired instantaneously to ensure the continuity and consistency of the service. Sexuality improves the overall reliability of network slicing instances. In the meantime, the method in the embodiment of the present application can also restore the modification of the network slice instance when the self-healing fails, so that the operator can pay attention to the original error. In addition, the method provided by the embodiment of the present application records the fault information, the self-healing action, and the self-healing result, which can provide reference for the automatic operation and maintenance decision of the network slice instance, so that the system can handle the same type of network fault more intelligently and quickly. Avoid the same configuration and modification of network slice instances in the future, resulting in the same error.
需要说明的是，本申请实施例适用于网络切片实例由网络切片子网实例构成的应用场景，解决网络切片子网实例发生无法自愈的故障时，可能采取的一种网络切片层面的自愈机制。本申请实施例涉及的流程与方法也适用于网络切片实例由网络功能构成的应用场景下，解决网络功能发生无法自愈的故障时，执行回退修复故障的自愈机制。网络功能回退的自愈机制的流程和步骤和本申请实施例中的流程步骤相类似，各模块间的交互信息中将网络切片子网实例的信息替换为相应的网络功能的信息即可。It should be noted that the embodiment of the present application is applicable to an application scenario in which a network slice instance is composed of a network sliced subnet instance, and a network slice level self-healing may be adopted when a network sliced subnet instance fails to self-heal. mechanism. The process and method in the embodiment of the present application are also applicable to a self-healing mechanism for performing a rollback repair failure when an application scenario in which a network segmentation instance is composed of a network function is used to solve a failure in which the network function cannot be self-healing. The process and the steps of the self-healing mechanism of the network function are similar to the process steps in the embodiment of the present application. The information of the network slice subnet instance is replaced with the information of the corresponding network function in the interaction information between the modules.
另外，本申请实施例中使用的NSSI 1和NSSMF 1仅是为了举例说明的需要，本申请的方法不限定故障网络切片子网实例的个数和需回退的网络切片子网实例的个数。In addition, the NSSI 1 and the NSSMF 1 used in the embodiments of the present application are only for the purpose of illustration. 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 to be rolled back. .
图2至图4示出了当网络切片子网实例嵌套了网络切片子网实例时，可能存在三种网络管理架构。下文介绍在这三种网络管理架构中如何执行本申请实施例的管理网络切片实例的方法。Figures 2 through 4 illustrate three possible network management architectures when a network sliced subnet instance is nested with a network sliced subnet instance. A method of managing a network slice instance of the embodiment of the present application in the three network management architectures is described below.
例如，在图2所示的***中，NSSMF 1中包含NSS-SH-MMF 1模块和NSS-SH-IF 1模块，NSSMF 2中仅包含NSS-SH-IF 2模块。在执行管理网络切片实例的方法的过程中，For example, in the system shown in FIG. 2, the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module, and the NSSMF 2 includes only the NSS-SH-IF 2 module. In the process of performing a method of managing a network slice instance,
A)NSS-SH-IF 2模块中的自愈算法、配置、参数等均由NSS-SH-MMF 1通过接口4进行配置，即方法600、方法700和方法900中的步骤S601、S701和S901的发送端是NSS-SH-MMF 1，接收端是NSS-SH-IF 2，通过接口4，配置的内容是NSSI 2的自愈算法；A) The self-healing algorithm, configuration, parameters, etc. in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 1 through the interface 4, ie, steps S601, S701 and S901 in the method 600, the method 700 and the method 900 The transmitting end is NSS-SH-MMF 1, the receiving end is NSS-SH-IF 2, and through interface 4, the content of the configuration is the self-healing algorithm of NSSI 2;
B)NSSI 2发生故障，生成故障告警后会将故障告警通过接口4传递到NSS-SH-MMF 1，即对应于方法600、方法700的步骤S602、S702，方法900中的步骤S905，NSSMF 2会将故障告警上报给NSS-SH-MMF 1；B) NSSI 2 fails. After the fault alarm is generated, the fault alarm is transmitted to the NSS-SH-MMF through the interface 4, that is, corresponding to the method 600, the method 700, the step S602, S702, the method 900, the step S905, the NSSMF 2 The fault alarm is reported to the NSS-SH-MMF 1;
C)由NSS-SH-MMF 1判断NSSI 2是否满足故障自愈触发条件，并通过接口4向NSS-SH-IF 2发送自愈触发请求，即对应方法600、方法700的步骤S603、S703，方法900中的步骤S906；C) The NSS-SH-MMF 1 determines whether the NSSI 2 meets 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, the corresponding method 600, steps S603 and S703 of the method 700, Step S906 in method 900;
D)NSS-SH-IF 2执行自愈动作后，会将自愈结果通过接口4上报给NSS-SH-MMF 1， 即对应于方法600的步骤S613，方法700、方法900的步骤S714、S914；D) After the NSS-SH-IF 2 performs the self-healing action, the self-healing result is reported to the NSS-SH-MMF 1 through the interface 4, that is, corresponding to the step S613 of the method 600, the method 700, the steps S714 and S914 of the method 900 ;
E)最后，可选地，NSS-SH-MMF 1将故障信息和/或自愈结果上报给NS-SH-MMF。在如图2所示的***中，可选地，NS-SH-MMF可通过接口2配置NSS-SH-MMF 1中的自愈结果的上报，自愈触发条件和/或其对NSS-SH-IF 1，NSS-SH-IF 2的自愈配置等。E) Finally, optionally, the NSS-SH-MMF 1 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 can configure the reporting of the self-healing result in the NSS-SH-MMF 1 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -IF 1, self-healing configuration of NSS-SH-IF 2, etc.
例如，在图3所示的***中，NSSMF 1中包含NSS-SH-MMF 1模块和NSS-SH-IF 1模块，NSSMF 2中包含NSS-SH-MMF 2模块和NSS-SH-IF 2模块。在执行管理网络切片实例的方法的过程中，For example, in the system shown in FIG. 3, the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module, and the NSSMF 2 includes the NSS-SH-MMF 2 module and the NSS-SH-IF 2 module. . In the process of performing a method of managing a network slice instance,
A)NSS-SH-IF 2模块中的自愈算法、配置、参数等均由NSS-SH-MMF 2进行配置，即方法600、方法700和方法900的步骤S601、S701和S901的发送端是NSS-SH-MMF 2，接收端是NSS-SH-IF 2，配置的内容是NSSI 2的自愈算法；A) The self-healing algorithm, configuration, parameters, and the like in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 2, that is, the transmitting ends of the steps S601, S701, and S901 of the method 600, the method 700, and the method 900 are NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the content of the configuration is the self-healing algorithm of NSSI 2;
B)当NSSI 2中的网络功能发生故障，生成故障告警会上报给NSS-SH-MMF 2，即由NSS-SH-MMF 2监测NSSI 2中的网络故障，对应于方法600、方法700的步骤S602、S702，方法900中的步骤S905，需要说明的是，组成NSSI 2的网络功能可能由NSSMF 2直接管理，也可能由NFM管理，本申请对此不作限定；B) When the network function in the NSSI 2 fails, the generated fault alarm is reported to the NSS-SH-MMF 2, that is, the network fault in the NSSI 2 is monitored by the NSS-SH-MMF 2, corresponding to the steps of the method 600 and the method 700. S602, S702, step S905 in the method 900, it should be noted that the network function constituting the NSSI 2 may be directly managed by the NSSMF 2, and may also be managed by the NFM, which is not limited in this application;
C)由NSS-SH-MMF 2判断NSSI 2是否满足故障自愈触发条件，并向NSS-SH-IF 2发送自愈触发请求即对应方法600、方法700的步骤S603、S703，方法900中的步骤S906；C) determining, by the NSS-SH-MMF 2, whether the NSSI 2 satisfies the fault self-healing trigger condition, and transmitting a self-healing trigger request to the NSS-SH-IF 2, that is, the corresponding method 600, steps S603 and S703 of the method 700, in the method 900 Step S906;
D)NSS-SH-IF 2执行自愈动作后，会将自愈结果上报给NSS-SH-MMF 2，即对应于方法600的步骤S613，方法700、方法900的步骤S714、S914；D) The NSS-SH-IF 2 performs the self-healing action, and reports the self-healing result to the NSS-SH-MMF 2, that is, corresponding to the step S613 of the method 600, the method 700, the steps S714 and S914 of the method 900;
E)最后，NSS-SH-MMF 2将故障信息和/或自愈结果上报给NSSMF 1，可选地，NSSMF 1将故障信息和/或自愈结果上报给NSMF。在如图10所示的***中，可选地，NS-SH-MMF可通过接口2配置NSS-SH-MMF 1中的自愈结果的上报，自愈触发条件和/或其对NSS-SH-IF 1，NSS-SH-MMF 2的自愈配置等。E) Finally, the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSSMF 1. Optionally, the NSSMF 1 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 can configure the reporting of the self-healing result in the NSS-SH-MMF 1 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -IF 1, self-healing configuration of NSS-SH-MMF 2, etc.
例如，在图4所示的***中，NSSMF 1中包含NSS-SH-MMF 1模块和NSS-SH-IF 1模块，NSSMF 2中包含NSS-SH-MMF 2模块和NSS-SH-IF 2模块，NSMF和NSSMF 2之间存在直接接口2。在执行本申请实施例的管理网络切片实例的过程中，For example, in the system shown in FIG. 4, the NSSMF 1 includes the NSS-SH-MMF 1 module and the NSS-SH-IF 1 module, and the NSSMF 2 includes the NSS-SH-MMF 2 module and the NSS-SH-IF 2 module. There is a direct interface 2 between NSMF and NSSMF 2. In the process of executing the management network slice instance of the embodiment of the present application,
A)NSS-SH-IF 2模块中的自愈算法、配置、参数等均由NSS-SH-MMF 2进行配置，即方法600、方法700和方法900中的步骤S601、S701和S901的发送端是NSS-SH-MMF 2，接收端是NSS-SH-IF 2，配置的内容是NSSI 2的自愈算法；A) The self-healing algorithm, configuration, parameters, and the like in the NSS-SH-IF 2 module are all configured by the NSS-SH-MMF 2, that is, the transmitting ends of steps S601, S701, and S901 in the method 600, the method 700, and the method 900. It is NSS-SH-MMF 2, the receiving end is NSS-SH-IF 2, and the content of the configuration is the self-healing algorithm of NSSI 2;
B)当NSSI 2中的网络功能发生故障，生成故障告警会上报给NSS-SH-MMF 2，即由NSS-SH-MMF 2监测NSSI 2中的网络故障，即对应于方法600、方法700的步骤S602、S702，方法900中的步骤S905，需要说明的是，组成NSSI 2的网络功能可能由NSSMF 2直接管理，也可能由NFM管理，本申请对此不作限定；B) When the network function in the NSSI 2 fails, the generated fault alarm is reported to the NSS-SH-MMF 2, that is, the network fault in the NSSI 2 is monitored by the NSS-SH-MMF 2, that is, corresponding to the method 600 and the method 700. Step S602, S702, step S905 in the method 900, it should be noted that the network function constituting the NSSI 2 may be directly managed by the NSSMF 2, and may also be managed by the NFM, which is not limited in this application;
C)由NSS-SH-MMF 2判断NSSI 2是否满足故障自愈触发条件，并向NSS-SH-IF 2发送自愈触发请求，即对应方法600、方法700的步骤S603、S703，方法900中的步骤S906；C) It is determined by the NSS-SH-MMF 2 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, the corresponding method 600, the method 700, the method S603, S703, the method 900 Step S906;
D)NSS-SH-IF 2执行自愈动作后，会将自愈结果上报给NSS-SH-MMF 2，即对应于实即对应于方法600的步骤S613，方法700、方法900的步骤S714、S914；D) After the NSS-SH-IF 2 performs the self-healing action, the self-healing result is reported to the NSS-SH-MMF 2, that is, corresponding to the step S613 corresponding to the method 600, the method 700, the step S714 of the method 900, S914;
E)最后，可选地，NSS-SH-MMF 2将故障信息和/或自愈结果上报给NSMF，可选地，NSS-SH-MMF 2还可将故障信息和/或自愈结果上报给NSSMF 1。在如图11所示的***中， 可选地，NS-SH-MMF可通过接口2配置NSS-SH-MMF 2中的自愈结果的上报，自愈触发条件和/或其对NSS-SH-MMF 2的自愈配置等。E) Finally, optionally, the NSS-SH-MMF 2 reports the fault information and/or the self-healing result to the NSMF. Optionally, the NSS-SH-MMF 2 can also report the fault information and/or the self-healing result to the NSF-SH-MMF 2 NSSMF 1. In the system shown in FIG. 11, optionally, the NS-SH-MMF can configure the reporting of the self-healing result in the NSS-SH-MMF 2 through the interface 2, the self-healing trigger condition and/or its pair of NSS-SH -MMF 2 self-healing configuration, etc.
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory,ROM))、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims (18)

  1. 一种管理网络切片实例的方法，其特征在于，包括：A method for managing a network slice instance, comprising:
    第一网络设备确定第一网络切片子网实例出现故障；The first network device determines that the first network slice subnet instance is faulty;
    所述第一网络设备向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。The first network device sends first indication information to the second network device, where the first indication information is used to instruct the second network device to activate a second network slice subnet instance, where the second network slice The network instance is used to replace the first network slice subnet instance.
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：所述第一网络设备向第三网络设备发送第二指示信息，所述第二指示信息用于指示所述第三网络设备注销所述第一网络切片子网实例。The method according to claim 1, wherein the method further comprises: the first network device transmitting second indication information to the third network device, the second indication information being used to indicate the third network The device logs out the first network slice subnet instance.
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：所述第一网络设备向第四网络设备发送第三指示信息，所述第三指示信息用于指示所述第四网络设备重配置与所述第一网络切片子网实例相关联的第三网络切片子网实例，所述重配置后的所述第三网络切片子网实例与所述第二网络切片子网实例相关联。The method according to claim 1 or 2, wherein the method further comprises: the first network device transmitting third indication information to the fourth network device, the third indication information being used to indicate the Reconfiguring a third network slice subnet instance associated with the first network slice subnet instance, the reconfigured third network slice subnet instance and the second network slice subnet The instance is associated.
  4. 如权利要求1至3中任一项所述的方法，其特征在于，在所述向第二网络设备发送第二指示信息之前，所述方法还包括：The method according to any one of claims 1 to 3, wherein before the sending the second indication information to the second network device, the method further comprises:
    所述第一网络设备将所述第一网络切片子网实例的参数信息备份至存储设备。The first network device backs up parameter information of the first network slice subnet instance to a storage device.
  5. 如权利要求4所述的方法，其特征在于，所述方法还包括：在所述第二网络切片子网实例的性能不符合预定条件的情况下，所述第一网络设备向第三网络设备发送第四指示信息，所述第四指示信息用于指示所述第三网络设备基于所述第一网络切片子网实例的备份至所述存储设备中的参数信息，复原所述第一网络切片子网实例。The method of claim 4, wherein the method further comprises: the first network device to the third network device if the performance of the second network slice subnet instance does not meet a predetermined condition Sending the fourth indication information, the fourth indication information is used to instruct the third network device to restore the first network slice based on parameter information of the backup of the first network slice subnet instance to the storage device Subnet instance.
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：所述第一网络设备获取所述第二网络切片子网实例的性能信息，所述性能信息用于指示所述第二网络切片子网实例的性能；The method according to claim 5, wherein the method further comprises: the first network device acquiring performance information of the second network slice subnet instance, the performance information being used to indicate the second The performance of the network slicing subnet instance;
    所述第一网络设备基于所述性能信息，确定所述第二网络切片子网实例的性能是否符合预定条件。The first network device determines, according to the performance information, whether performance of the second network slice subnet instance meets a predetermined condition.
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：所述第一网络设备从所述第二网络设备接收故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障；The method according to any one of claims 1 to 6, wherein the method further comprises: the first network device receiving fault alarm information from the second network device, the fault alarm information being used Instructing the first network slice subnet instance to fail;
    所述第一网络设备确定第一网络切片子网实例出现故障，包括：The first network device determines that the first network slice subnet instance is faulty, including:
    所述第一网络设备根据所述故障报警信息确定所述第一网络切片子网实例。The first network device determines the first network slice subnet instance according to the fault alarm information.
  8. 一种管理网络切片实例的方法，其特征在于，包括：A method for managing a network slice instance, comprising:
    第二网络设备从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换第一网络切片子网实例；The second network device receives the first indication information from the first network device, where the first indication information is used to indicate that the second network device activates the second network slice subnet instance, where the second network slice subnet instance Used to replace the first network slice subnet instance;
    所述第二网络设备根据所述第一指示信息，激活所述第二网络切片子网实例。The second network device activates the second network slice subnet instance according to the first indication information.
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：The method of claim 8 wherein the method further comprises:
    所述第二网络设备向所述第一网络设备发送故障报警信息，所述故障报警信息用于指 示所述第一网络切片子网实例出现故障。The second network device sends fault alarm information to the first network device, where the fault alarm information is used to indicate that the first network slice subnet instance is faulty.
  10. 一种网络设备，其特征在于，所述网络设备为第一网络设备，包括：A network device, where the network device is a first network device, including:
    通信接口，Communication Interface,
    存储器，用于存储指令，Memory for storing instructions,
    处理器，与所述存储器和所述通信接口分别相连，用于执行所述存储器存储的所述指令，以在执行所述指令时执行如下步骤：a processor, coupled to the memory and the communication interface, for executing the instructions stored by the memory to perform the following steps when executing the instruction:
    确定第一网络切片子网实例出现故障；Determining that the first network slice subnet instance is faulty;
    通过所述通信接口向第二网络设备发送第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换所述第一网络切片子网实例。Transmitting, by the communication interface, the first indication information to the second network device, where the first indication information is used to instruct the second network device to activate a second network slice subnet instance, where the second network slice subnet An instance is used to replace the first network slice subnet instance.
  11. 如权利要求10所述的网络设备，其特征在于，所述处理器还用于通过所述通信接口向第三网络设备发送第二指示信息，所述第二指示信息用于指示所述第三网络设备注销所述第一网络切片子网实例。The network device according to claim 10, wherein the processor is further configured to send second indication information to the third network device by using the communication interface, where the second indication information is used to indicate the third The network device deregisters the first network slice subnet instance.
  12. 如权利要求10或11所述的网络设备，其特征在于，所述处理器还用于通过所述通信接口向第四网络设备发送第三指示信息，所述第三指示信息用于指示所述第四网络设备重配置与所述第一网络切片子网实例相关联的第三网络切片子网实例，所述重配置后的所述第三网络切片子网实例与所述第二网络切片子网实例相关联。The network device according to claim 10 or 11, wherein the processor is further configured to send third indication information to the fourth network device by using the communication interface, where the third indication information is used to indicate the The fourth network device reconfigures a third network slice subnet instance associated with the first network slice subnet instance, the reconfigured third network slice subnet instance and the second network slice Network instances are associated.
  13. 如权利要求10至12中任一项所述的网络设备，其特征在于，所述处理器还用于：在所述向第二网络设备发送第二指示信息之前，将所述第一网络切片子网实例的参数信息备份至存储设备。The network device according to any one of claims 10 to 12, wherein the processor is further configured to: slice the first network before sending the second indication information to the second network device The parameter information of the subnet instance is backed up to the storage device.
  14. 如权利要求13所述的网络设备，其特征在于，所述处理器还用于：在所述第二网络切片子网实例的性能不符合预定条件的情况下，通过所述通信接口向第三网络设备发送第四指示信息，所述第四指示信息用于指示所述第三网络设备基于所述第一网络切片子网实例的备份至所述存储设备中的参数信息，复原所述第一网络切片子网实例。The network device according to claim 13, wherein the processor is further configured to: go to the third through the communication interface if the performance of the second network slice subnet instance does not meet a predetermined condition The network device sends the fourth indication information, where the fourth indication information is used to instruct the third network device to restore the first information based on the parameter information of the backup of the first network slice subnet instance to the storage device. Network slice subnet instance.
  15. 如权利要求14所述的网络设备，其特征在于，所述处理器还用于获取所述第二网络切片子网实例的性能信息，所述性能信息用于指示所述第二网络切片子网实例的性能；所述第一网络设备基于所述性能信息，确定所述第二网络切片子网实例的性能是否符合预定条件。The network device according to claim 14, wherein the processor is further configured to acquire performance information of the second network slice subnet instance, where the performance information is used to indicate the second network slice subnet Performance of the instance; the first network device determines, based on the performance information, whether performance of the second network slice subnet instance meets a predetermined condition.
  16. 如权利要求10至15中任一项所述的网络设备，其特征在于，所述处理器还用于通过所述通信接口从所述第二网络设备接收故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障；在所述第一网络设备确定第一网络切片子网实例出现故障方面，所述处理器具体用于根据所述故障报警信息确定所述第一网络切片子网实例。The network device according to any one of claims 10 to 15, wherein the processor is further configured to receive fault alarm information from the second network device by using the communication interface, where the fault alarm information is used. Instructing the first network slice subnet instance to be faulty; and the processor is configured to determine, according to the fault alarm information, that the first network device determines that the first network slice subnet instance is faulty A network sliced subnet instance.
  17. 一种网络设备，其特征在于，包括：A network device, comprising:
    通信接口，Communication Interface,
    存储器，用于存储指令，Memory for storing instructions,
    处理器，与所述存储器和所述通信接口分别相连，用于执行所述存储器存储的所述指令，以在执行所述指令时执行如下步骤：a processor, coupled to the memory and the communication interface, for executing the instructions stored by the memory to perform the following steps when executing the instruction:
    通过所述通信接口从第一网络设备接收第一指示信息，所述第一指示信息用于指示所述第二网络设备激活第二网络切片子网实例，其中，所述第二网络切片子网实例用于替换 第一网络切片子网实例；Receiving first indication information from the first network device by using the communication interface, where the first indication information is used to instruct the second network device to activate a second network slice subnet instance, where the second network slice subnet The instance is used to replace the first network slice subnet instance;
    根据所述第一指示信息，激活所述第二网络切片子网实例。And the second network slice subnet instance is activated according to the first indication information.
  18. 如权利要求17所述的网络设备，其特征在于，所述处理器还用于通过所述通信接口向所述第一网络设备发送故障报警信息，所述故障报警信息用于指示所述第一网络切片子网实例出现故障。The network device according to claim 17, wherein the processor is further configured to send fault alarm information to the first network device by using the communication interface, where the fault alarm information is used to indicate the first The network slice subnet instance has failed.
PCT/CN2018/078292 2017-03-20 2018-03-07 Method and system for managing network slice instance, and network device WO2018171430A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710167783.6A CN108632065B (en) 2017-03-20 2017-03-20 Method, network device and system for managing network slice instances
CN201710167783.6 2017-03-20

Publications (1)

Publication Number Publication Date
WO2018171430A1 true WO2018171430A1 (en) 2018-09-27

Family

ID=63585037

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078292 WO2018171430A1 (en) 2017-03-20 2018-03-07 Method and system for managing network slice instance, and network device

Country Status (2)

Country Link
CN (1) CN108632065B (en)
WO (1) WO2018171430A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11246088B2 (en) 2020-04-10 2022-02-08 Cisco Technology, Inc. Failover and management of multi-vendor network slices

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111526030B (en) * 2019-02-03 2021-12-14 华为技术有限公司 Information processing method and device
CN110602717B (en) * 2019-09-18 2021-12-31 四川长虹电器股份有限公司 Disaster recovery processing method for 5G network slice
CN112838942A (en) * 2019-11-25 2021-05-25 中兴通讯股份有限公司 Network operation and maintenance method, electronic equipment and storage medium
CN113993148B (en) * 2020-07-10 2023-08-15 ***通信集团浙江有限公司 5G network slice disaster recovery switching method and device based on machine learning
CN114143163B (en) * 2020-08-14 2023-11-14 ***通信集团浙江有限公司 Slice false alarm identification method and device based on graph attention network
CN114286359A (en) * 2020-09-27 2022-04-05 华为技术有限公司 Communication method and communication device
CN113068227B (en) * 2020-11-24 2023-10-27 锐捷网络股份有限公司 Method and base station for switching slices in 5G network
CN115442216B (en) * 2021-06-04 2023-09-05 ***通信集团浙江有限公司 Network slice fault self-healing method, device, equipment and computer storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105516312A (en) * 2015-12-09 2016-04-20 重庆邮电大学 Software defined networking load balancingdevice and method
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
US20160360408A1 (en) * 2015-06-02 2016-12-08 Huawei Technologies Co., Ltd. Method and apparatus to use infra-structure or network connectivity services provided by 3rd parties
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
US20160360408A1 (en) * 2015-06-02 2016-12-08 Huawei Technologies Co., Ltd. Method and apparatus to use infra-structure or network connectivity services provided by 3rd parties
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
CN105516312A (en) * 2015-12-09 2016-04-20 重庆邮电大学 Software defined networking load balancingdevice and method

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11246088B2 (en) 2020-04-10 2022-02-08 Cisco Technology, Inc. Failover and management of multi-vendor network slices

Also Published As

Publication number Publication date
CN108632065B (en) 2020-09-11
CN108632065A (en) 2018-10-09

Similar Documents

Publication Publication Date Title
WO2018171430A1 (en) Method and system for managing network slice instance, and network device
US9647891B2 (en) Managing network configurations
JP7105930B2 (en) Alarm method and alarm device
CN100417081C (en) Method, system for checking and repairing a network configuration
US7702667B2 (en) Methods and systems for validating accessibility and currency of replicated data
US8370466B2 (en) Method and system for providing operator guidance in network and systems management
US10728085B1 (en) Model-based network management
US9817709B2 (en) Systems and methods for automatic replacement and repair of communications network devices
WO2018121453A1 (en) Network management method, network management system, and network element management system
US20090210427A1 (en) Secure Business Continuity and Disaster Recovery Platform for Multiple Protected Systems
EP2974238B1 (en) Method and apparatus for providing tenant redundancy
CN108347339B (en) Service recovery method and device
WO2019141089A1 (en) Network alarm method, device, system and terminal
CN106657167B (en) Management server, server cluster, and management method
CN105681077A (en) Fault processing method, device and system
CN104243205A (en) Message processing method and device used during virtual switch fault
WO2019145049A1 (en) Proactive fault management in slicing-enabled communication networks
CN111342986B (en) Distributed node management method and device, distributed system and storage medium
EP3069474B1 (en) Correlation of event reports
CN113872997B (en) Container group POD reconstruction method based on container cluster service and related equipment
JP6555721B2 (en) Disaster recovery system and method
CN111309515B (en) Disaster recovery control method, device and system
US20230164596A1 (en) Alarm log management system and method during failure in o-ran
CN114124803B (en) Device management method and device, electronic device and storage medium
CN113824595B (en) Link switching control method and device and gateway equipment

Legal Events

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

Ref document number: 18772080

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18772080

Country of ref document: EP

Kind code of ref document: A1