WO2018171465A1 - 管理网络切片实例的方法、装置和系统 - Google Patents

管理网络切片实例的方法、装置和系统 Download PDF

Info

Publication number
WO2018171465A1
WO2018171465A1 PCT/CN2018/078793 CN2018078793W WO2018171465A1 WO 2018171465 A1 WO2018171465 A1 WO 2018171465A1 CN 2018078793 W CN2018078793 W CN 2018078793W WO 2018171465 A1 WO2018171465 A1 WO 2018171465A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network device
network slice
instance
self
Prior art date
Application number
PCT/CN2018/078793
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to EP18771388.8A priority Critical patent/EP3588852B1/en
Publication of WO2018171465A1 publication Critical patent/WO2018171465A1/zh
Priority to US16/574,211 priority patent/US10993127B2/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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5025—Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present application relates to the field of communications and, more particularly, to methods, apparatus, 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 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 slice instance, including: determining, by a first network device, that a configuration parameter of a first network slice subnet instance needs to be modified, where the first network device is configured to manage the first network slice a subnet instance; the first network device modifies configuration parameters of the first network slice subnet instance; the first network device sends report information to the second network device, where the report information is used to indicate that the a result of a configuration parameter of a network slicing subnet instance, wherein the second network device is configured to manage a first network slice instance, the first network slice instance comprising the first network slice subnet instance.
  • the first network device that manages the first network segment subnet instance may determine that the configuration parameter of the first network slice subnet instance needs to be modified, and report the modified first network slice subnet to the second network device.
  • the result of the configuration parameters of the instance Thereby, 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 receiving a self-optimization policy from the second network device, where the self-optimization policy is used to indicate a rule for modifying a network slice subnet instance; The modifying, by the network device, the configuration parameter of the first network slice subnet instance, the first network device modifying the configuration parameter of the first network slice subnet instance based on the self-optimization policy.
  • the method further includes: the first network device receiving, from the second network device, authorization information, where the authorization information is used to indicate that the configuration parameter of the first network slice subnet instance is allowed to be modified. .
  • the method further includes: the configuration parameter of the first network slice subnet instance includes: a capacity size of the first network slice subnet instance, and an capability of the first network slice subnet instance parameter.
  • a second aspect provides a method for managing an instance of a network slice, the second network device receiving report information from the first network device, where the report information is used to indicate that the configuration parameter of the first network slice subnet instance is modified. a result, wherein the first network device is configured to manage the first network slice subnet instance, the second network device is configured to manage a first network slice instance, and the first network slice instance includes the first A network sliced subnet instance.
  • the method further includes: sending, by the second network device, a self-optimization policy to the first network, where the self-optimization policy is used to indicate a rule for modifying a network slice subnet instance.
  • the method further includes: the second network device sending, to the first network device, authorization information, where the authorization information is used to indicate that the configuration parameter of the first network slice subnet instance is allowed to be modified. .
  • the method further includes: the configuration parameter of the first network slice subnet instance includes: a capacity size of the first network slice subnet instance, and an capability of the first network slice subnet instance parameter.
  • a third aspect provides a method for managing a network slice instance, including: determining, by a first network device, configuration parameters of a first network slice instance, the first network slice instance including at least one network slice subnet instance; The first network device sends the first indication information to the at least one second network device, where the first indication information is used to indicate that the at least one second network device modifies configuration parameters of the at least one network slice subnet instance; The first network device receives first reply information from the at least one second network device, where the first reply information is used to indicate a result of modifying configuration parameters of the at least one network slice subnet instance.
  • the first network device may autonomously determine to modify the first network slice instance, where the first network slice instance includes at least one network slice subnet instance, and the second network device that manages the first network sliced subnet instance
  • the first indication information is sent to modify the network slice subnet instance, and the network slice instance can be flexibly modified, thereby improving the efficiency of managing the network slice instance.
  • the method further includes: the first network device acquiring current configuration information of the at least one network slice subnet instance from the at least one second network device; the first network device determining to modify The configuration parameter of the first network slice instance includes: determining, by the first network device, the configuration parameter of the first network slice instance based on current configuration information of the at least one network slice subnet instance.
  • the method before the first network device sends the first indication information to the at least one second network device, the method further includes: the first network device acquiring authorization information from the third network device, where The authorization information is used to indicate that the configuration parameters of the first network slice instance are allowed to be modified.
  • the method further includes: the first network device receiving a self-optimization policy from a third network device, where the self-optimization policy is used to indicate a rule for modifying a network slice instance; the first network device determines The modifying the configuration parameter of the first network slice instance includes: determining, by the first network device, the configuration parameter of the first network slice instance based on the self-optimization policy.
  • the method further includes: the first network device sending report information to the third network device, where the report information is used to indicate a result of modifying configuration parameters of the first network slice instance.
  • the configuration parameter of the first network slice instance includes at least one of the following: a capacity size of the first network slice instance, and a capability parameter of the first network slice instance.
  • a fourth aspect provides a method for managing a network sharding instance, where the second network device receives the first indication information sent by the first network device, where the first indication information is used to indicate that the second network device modifies the a network sliced subnet instance, the first network device is configured to manage a first network slice instance, the first network slice instance includes the first network sliced subnet instance; and the second network device is configured to A network device sends a first reply message, where the first reply message is used to indicate a result of modifying a configuration parameter of the first network slice subnet instance.
  • the method further includes: sending, by the second network device, current configuration information of the first network slice subnet instance to the first network device.
  • the configuration parameter of the first network slice instance includes at least one of: a capacity size of the first network slice instance, and a capability parameter of the first network slice instance.
  • a fifth aspect provides a method for managing an instance of a network segment, including: determining, by the first network device, that the first network function included in the first network slice instance needs to be optimized; and the first network device performing optimization on the first network function
  • the optimizing process includes: modifying configuration parameters of the first network function, or copying the first network function, and adding the second network function to the first network slice instance, where a network splicing instance includes the second network function; the first network device sends reporting information to the second network device, where the reporting information is used to instruct the first network device to optimize the first network function
  • the second network device is configured to manage the first network slice instance.
  • the first network device may manage the first network function; the second network device manages the first network function by using the first network device, where the first network slice instance includes the first network function.
  • 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 receiving a self-optimization policy from the second network device, where the self-optimization policy is used to indicate a rule for modifying a network function; the first network device Optimizing the first network function, the first network device performs optimization processing on the first network function based on the self-optimization policy.
  • the first network device obtains authorization information from the second network device, where the authorization information is used to indicate that the first network function is allowed to be optimized.
  • the configuration parameters of the first network function include: a location parameter, a topology parameter, and a function parameter of the first network function.
  • the method further includes: the first network device sending, to the third network device, reservation request information, where the reservation request information is used to indicate that the third network device is the first network
  • the function reserves network resources, and the third network device is configured to allocate network resources for network functions.
  • a method for managing an instance of a network slice includes: receiving, by the second network device, report information from the first network device, where the report information is used to indicate a result of modifying configuration parameters of the first network function,
  • the first network device is configured to manage the first network function
  • the second network device is configured to manage a first network slice instance
  • the first network slice instance includes the first network function.
  • the method further includes: the second network device sending a self-optimization policy to the first network device, where the self-optimization policy is used to indicate a rule for modifying a network function.
  • the method further includes: sending, by the second network device, authorization information to the first network device, where the authorization information is used to indicate a configuration parameter that allows modification of the first network function.
  • the configuration parameters of the first network function include: a location parameter, a topology parameter, and a function parameter of the first network function.
  • a network device for managing a network slice instance for performing the method of any of the foregoing 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 first aspect or any of the possible implementations of the first aspect.
  • a network device for managing an instance of a network slice for performing the method of any of the foregoing second aspect or any of the possible implementations of the second aspect.
  • the network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • a network device for managing an instance of a network slice for performing the method of any of the foregoing third aspect or any of the possible implementations of the third aspect.
  • 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 managing an instance of a network slice for performing the method of any of the above-described fourth aspect or any possible implementation 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 network device for managing an instance of a network slice for performing the method of any of the above fifth aspect or any of the possible implementations of the fifth aspect.
  • the network device comprises means for performing the method of any of the possible implementations of the fifth or fifth aspect above.
  • the network device for managing an instance of a network slice for performing the method of any of the above sixth or sixth possible implementations.
  • the network device comprises means for performing the method of any of the possible implementations of the sixth or sixth aspect described above.
  • the invention provides a network system, comprising the network device according to the seventh aspect, the eighth aspect, or the network device of the foregoing ninth and tenth aspects, or the foregoing tenth A network device as described in one aspect and the twelfth aspect.
  • a network device for managing a network slice instance 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 for managing a network slice instance 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 for managing a network slice instance 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
  • 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 for managing a network slice instance 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
  • the execution causes the processor to perform the method of any of the possible implementations of the fourth aspect or the fourth aspect.
  • a network device for managing a network slice instance 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
  • the execution causes the processor to perform the method of any of the possible implementations of the fifth aspect or the fifth aspect.
  • a network device for managing a network slice instance 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
  • the execution causes the processor to perform the method of any of the possible implementations of the sixth aspect or the sixth aspect.
  • the invention provides a network system, comprising the network device according to the fourteenth aspect, the fifteenth aspect, or the network device according to the sixteenth aspect and the seventeenth aspect, or The network device according to the eighteenth aspect and the nineteenth aspect described above.
  • 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 network management architecture according to still another embodiment of the present application.
  • FIG. 6 is a schematic diagram of a method for managing a network slice instance according to an 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 method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 11 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 12 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 13 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 14 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 15 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 16 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 17 is a schematic diagram of a method for managing a network slice instance according to still another embodiment of the present application.
  • FIG. 18 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 20 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 21 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 22 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 23 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 24 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 25 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 26 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 27 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 28 is a schematic diagram of a network device according to still another embodiment of the present application.
  • FIG. 29 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 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 a complete network service end-to-end.
  • the network slice subnet instance can be a network function set of the same device vendor in the network slice instance. It 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.
  • Network slice instance can automatically change the configuration while continuously providing services to adapt to dynamically changing traffic, topology, network resources, and service status.
  • the network slice management system monitors several parameters of the network slice instance and automatically modifies the NSI related configuration within the allowed range to improve overall performance.
  • the concept of network slice automatic optimization belongs to the automatic orchestration and management of network slicing, try to avoid the impact on services and minimize human participation.
  • FIG. 1 shows a schematic diagram of a network architecture 100 of an embodiment of the present application.
  • the functions and interfaces of the various modules in Figure 1 are as follows:
  • 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 EM.
  • 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, is a logical entity, can exist independently of NF, can also be located in NF, or located in other functional modules, used to implement management of NF, such as management NF
  • the life cycle configure the functional parameters of the NF, allocate network resources for the NF, and so on.
  • 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 NSMF 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 The interface between the NSMF and the NFM is applicable to the scenario where the NSMF can sense and manage the NF. That is, the NSMF interacts with the NFM through the interface to send and manage commands to the NF. The NFM receives the message from the NSMF through the interface. And the information about the NF is fed back 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.
  • 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.
  • the solution of the present application can be applied to two scenarios.
  • the first one is that the NSMF only manages the NSSMF, the NF information is not perceived, and the NF cannot be managed.
  • the second is that the NSMF can sense and directly manage the NF, which can be similar to the traditional network management system.
  • Other new network function management functions are also available.
  • the NSMF can directly manage the NF through the network function manager NFM.
  • FIG. 2 is a schematic structural diagram of a network management architecture 200 in an embodiment of the present application. As shown in FIG. 2, the network management architecture 200 can be used to manage network slice instances. The functions of the modules in the network management architecture 200 may be the same or similar to those of the modules corresponding to the network management architecture 100. The various modules included in the network management architecture 200 are described below.
  • N_SO_MMF network slice self-optimization monitor and management function
  • the relevant parameters required to generate the NSI self-optimization function mainly include the NSI parameters to be monitored, the threshold for triggering self-optimization, and the range of NSI self-optimization;
  • NSS_SO_MMF Communicate with NSS_SO_MMF to provide an optimization strategy for the NSSI self-optimization function, and learn the operation of the NSSI self-optimization function to obtain the self-optimization result of the NSSI.
  • NSS_SO_MMF Network slice subnet self-optimization monitor and management function
  • NS_SO_MMF Communicate with NS_SO_MMF, receive an optimization strategy of the NSSI self-optimization function, and report the operation of the NSSI self-optimization function, and related self-optimization results;
  • the relevant parameters required to generate the NSSI self-optimization function mainly include the NSSI parameters to be monitored, the threshold for triggering self-optimization, and the range of NSSI self-optimization;
  • NF_SO_MMF Network function self-optimization monitor and management function
  • the relevant parameters required to generate the NF self-optimization function mainly include the NF parameters to be monitored, the threshold for triggering self-optimization, and the range of NF self-optimization;
  • the module may include and is not limited to at least one of the following functions:
  • the configuration of the NSI is adjusted according to the output of the NSI self-optimization algorithm.
  • the module may include but is not limited to at least one of the following functions:
  • the NSSI configuration is adjusted according to the output of the NSSI self-optimization algorithm.
  • NF_SO_F network function self-optimization function
  • the module may include but is not limited to at least one of the following functions:
  • the functions of the NSFM, NSSMF, and NFM in FIG. 2 may have the same or similar functions as the corresponding modules in FIG. 1.
  • Interface 2 and interface 3 in Figure 2 may be the corresponding interfaces in Figure 1.
  • the NSMF may include NS_SO_MMF
  • the NSSMF may include NSS_SO_MMF
  • the NFM may include NF_SO_MMF.
  • the NSSI can allow nesting, that is, one NSSI contains another NSSI, and both can have their own NSSMF; if the NSI includes NSSI 1, NSSI 1 includes NSSI 2, and NSSMF 1 and NSSMF 2 are NSSI 1 and NSSI 2 manager, there are two options for managing NSSI 2 at this time.
  • Option 1 is that NSSMF 1 interacts with NSSMF 2 to manage NSSI 2. This option is applicable to scenarios where there is a direct interface between NSSMF 1 and NSSMF 2.
  • option 2 is to manage NSSI 2 by NSMF.
  • FIG. 3 to FIG. 5 respectively show three network management architectures of the embodiments of the present application.
  • FIG. 3 is a schematic structural diagram of a network management architecture 300 according to an embodiment of the present application.
  • the NSS_SO_F2 of the nested NSSI is managed by the NSS_SO_MMF1 of the upper layer NSSI; the upper layer of NSS_SO_MMF1 is managed by the NS_SO_MMF.
  • the NS_SO_MMF may send a self-optimization strategy for the NSSI 1 to the NSS_SO_MMF1, and may also send a self-optimization strategy of the NSSI 2, and the self-optimization strategy of the NSSI 2 may also be generated by the NSS_SO_MMF1.
  • NSS_SO_MMF1 can configure NSS_SO_F2.
  • FIG. 4 is a schematic structural diagram of a network management architecture 400 according to an embodiment of the present application. As shown in FIG. 4, the nested NSSI NSS_SO_F2 can be directly managed by NSS_SO_MMF2, and NSS_SO_MMF2 receives the policy from NSS_SO_MMF1.
  • the NS_SO_MMF may send a self-optimization strategy for the NSSI 2 to the NSS_SO_MMF1, and may also send a self-optimization strategy of the NSSI 2 (the self-optimization strategy of the NSSI 2 may also be generated by the NSS_SO_MMF1).
  • NSS_SO_MMF1 sends the self-optimization strategy of NSSI 2 to NSS_SO_MMF2.
  • the interaction between NSS_SO_MMF1 and NSS_SO_MMF2 includes sending a self-optimization strategy of NSSI 2, obtaining the operation of the NSSI2 self-optimization function, and obtaining the self-optimization result of NSSI 2.
  • FIG. 5 is a schematic structural diagram of a network management architecture 500 according to an embodiment of the present application.
  • the NSS_SO_F2 of the nested NSSI is managed by its own NSS_SO_MMF2; its own NSS_SO_MMF2 can be managed by NS_SO_MMF.
  • NSS_SO_MMF2 there may be some coordination relationship between NSS_SO_MMF2 and NSS_SO_MMF1
  • the nested NSSI is automatically optimized, it may be necessary to notify the optimization result to the NSSI of the upper layer.
  • the NS_SO_MMF can directly send a self-optimization strategy for NSSI2 to the NSS_SO_MMF2.
  • 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_SO_MMF module and the NS_SO_F module may be combined into one functional module, and the functional module has NS_SO_MMF. All functions of the module and the NS_SO_F module, or the NS_SO_MMF module and the NS_SO_F module, can be separate 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 present invention, and such modifications or substitutions are intended to be included within the scope of the present invention.
  • FIG. 6 is 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 applied to any of the network management architectures illustrated in Figures 1 through 5.
  • the first network device may be an NSSMF module or an NSS_SO_MMF module
  • the NSSMF module may include an NSS_SO_MMF module and an NSS_SO_F module
  • the second network device may be an NSMF module or an NS_SO_MMF module.
  • method 600 includes:
  • the first network device determines that configuration parameters of the first network slice subnet instance need to be modified, and the first network device is configured to manage the first network slice subnet instance.
  • the first network device modifies configuration parameters of the first network slice subnet instance.
  • the configuration parameter of the first network slice subnet instance may include: a capacity size, a capability parameter, a location parameter, a topology parameter, a function parameter, and the like of the first network slice subnet instance. This application does not limit this.
  • the modifying the configuration parameter of the first network slice subnet instance may also be performed to perform self-optimization on the first network slice subnet instance.
  • the modification of the NSSI capacity may refer to modifying the total number of users that the NSSI can support, the maximum number of connections on the control plane, the maximum number of PDU connections, and the total bandwidth.
  • the modification of the capability parameters of the NSSI may refer to some network characteristics. For example, support high mobility, medium mobility, low mobility; support high latency, medium latency, low latency, and the like.
  • the modification action may include adding an NF, deleting an NF, or updating an NF feature.
  • the first network device sends report information to the second network device, where the report information is used to indicate a result of modifying a configuration parameter of the first network slice subnet instance, where the second network device is used to Managing a first network slice instance, the first network slice instance including the first network slice subnet instance.
  • the reporting information indicates a result of modifying the configuration parameter of the first network slice subnet instance, and may also be referred to as the report information indicating a result of performing self-optimization on the first network sliced subnet instance.
  • the report information may include the identifier of the first network slice instance, the identifier of the first network slice subnet instance, the modified configuration parameter, and the like.
  • the modified configuration parameter may include information such as the modified capacity size and the modified capability parameter.
  • the first network device that manages the first network segment subnet instance may determine that the configuration parameter of the first network slice subnet instance needs to be modified, and report the modified first network slice subnet to the second network device.
  • the result of the configuration parameters of the instance Thereby, the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
  • the first network device determines that the configuration parameter of the first network slice subnet instance needs to be modified, including: the first network device receives a self-optimization policy from the second network device, where the self-optimization policy is used to indicate Modifying a rule of the network sliced subnet instance; the first network device modifying the configuration parameter of the first network sliced subnet instance, including: the first network device modifying the first network based on the self-optimization policy The configuration parameters for the sliced subnet instance.
  • the second network device may determine, according to the self-optimization policy of the entire NSI, a self-optimization policy of each NSSI, and send a self-optimization policy of each NSSI to the corresponding NSS_SO_MMF.
  • the content of the self-optimization policy may include at least one of the following: an identifier of the NSI, used to indicate which NSI the self-optimization policy belongs to; an identifier of the NSSI to indicate which NSSI the self-optimization policy is applied to; and a parameter threshold that triggers optimization, The range in which the NSSI capacity can be adjusted.
  • the second network device may receive the self-optimization policy of the NSI from other management modules (such as the SvMF, the policy management module, and the like) provided by the operator, and send the self-optimization to the first network device according to the NSI self-optimization policy.
  • the self-optimization strategy of the NSI may be a self-optimization strategy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, trigger condition of self-optimization function, effective range of self-optimization parameters, whether confirmation is needed before optimization, whether feedback Optimization results, etc.
  • the method 600 further includes: the first network device receiving authorization information from the second network device, the authorization information being used to indicate that configuration parameters of the first network slice subnet instance are allowed to be modified.
  • the authorization information may be authorization information of the operator.
  • the first network device may obtain the operator authorization through the second network device, that is, notify the operator of the upcoming changes to the NSI capacity, and confirm whether the permission is allowed.
  • FIG. 7 shows a schematic flowchart of a method 700 for managing a network slice instance according to an embodiment of the present application.
  • the example of Figure 7 shows the process by which NSSMF automatically optimizes the capacity of the NSSI.
  • the second network device in method 600 may be an NS_SO_MMF module
  • the first network device in method 600 may be an NSS_SO_MMF module, or an NSSMF module.
  • the NSSMF module includes an NSS_SO_MMF module and an NSS_SO_F module.
  • the method 700 includes:
  • NS_SO_MMF receives an NSI self-optimization policy from the SvMF or other policy management module.
  • the self-optimization strategy of the NSI may be a self-optimization strategy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: for example, whether to allow NSI self-optimization, trigger conditions of self-optimization function, effective range of self-optimization parameters, automatic optimization function allowing operation, whether confirmation is required before optimization, whether or not Feedback optimization results, etc.
  • S702 and NS_SO_MMF obtain a self-optimization strategy for each NSSI according to the self-optimization strategy of the entire NSI, and send a self-optimization strategy of each NSSI to the NSS_SO_MMF.
  • the content of the self-optimization policy may include at least one of the following: an identifier of the NSI, used to indicate which NSI the self-optimization policy belongs to; an identifier of the NSSI to indicate which NSSI the self-optimization policy is applied to; and a parameter threshold that triggers optimization, The range in which the NSSI capacity can be adjusted.
  • NSS_SO_MMF send a self-optimization function configuration message to the NSS_SO_F, which may include: an NSSI identifier, a trigger condition for automatically optimizing the NSSI capacity, and a range of NSSI capacity adjustment.
  • the capacity of the NSSI can be measured by parameters such as the number of supported users, the number of supported connections, and the total bandwidth.
  • this step may be regarded as an internal interaction of the network device.
  • NSS_SO_F modifies the capacity of the NSSI, or, in other words, NSS_SO_F performs self-optimization on the NSSI.
  • the NS_SO_MMF and the NSS_SO_MMF obtain authorization information from the SvMF, where the authorization information may be authorization information sent by the operator. That is, the SvMF or other policy management module can be used to notify the operator that the configuration parameters of the NSI will be modified. Please ask the operator to confirm whether it is allowed.
  • the S707 and the NSS_SO_MMF report the self-optimization result to the NS_SO_MMF, and may include an NSI ID, an NSSI ID, and a modified NSSI capacity.
  • the NS_SO_MMF reports the report information to the SvMF or other policy management module, where the report information is used to indicate the result of modifying the configuration parameter of the NSSI, or the self-optimization result.
  • the report information may include information of the NSI ID, the NSSI ID, or the size of the NSSI modified capacity.
  • the capacity automatic optimization function of the NSSI can be controlled by the NS_SO_MMF to meet the automatic adjustment requirement of the NSI capacity of the NSI. Increased flexibility in managing NSI and NSSI, which in turn improves the efficiency of managing NSI.
  • the NSSMF when the capacity occupancy of the NSSI reaches a certain threshold, the NSSMF can automatically determine to expand or reduce the capacity, optimize performance, and improve resource utilization.
  • FIG. 8 is a schematic flowchart of a method 800 for managing a network slice according to another embodiment of the present application.
  • Method 800 presents a process for NSSMF to automatically optimize the NSSI capability parameters.
  • the second network device in method 600 may be an NS_SO_MMF module
  • the first network device in method 600 may be an NSS_SO_MMF module, or an NSSMF module.
  • the NSSMF module includes an NSS_SO_MMF module and an NSS_SO_F module.
  • the method 800 includes:
  • NS_SO_MMF receives an NSI self-optimization policy from the SvMF or other policy management module.
  • the self-optimization strategy of the NSI may be a self-optimization strategy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, whether confirmation is required before optimization, whether to feedback optimization results, and the like.
  • S802 and NS_SO_MMF obtain a self-optimization strategy for each NSSI according to the self-optimization strategy of the entire NSI, and send a self-optimization strategy of each NSSI to the NSS_SO_MMF.
  • the content of the self-optimization policy may include at least one of the following: an identifier of the NSI, indicating which NSI the self-optimization policy belongs to; an identifier of the NSSI to indicate which NSSI the self-optimization policy is applied to; and a parameter threshold for triggering the self-optimization , NSSI's ability parameters can be adjusted options.
  • NSSI can automatically adjust support for mobility based on the judgment of user mobility characteristics, such as high mobility, medium mobility, and low mobility.
  • the options for capacity adjustment can be combined, for example, between high mobility & medium latency, and medium mobility & lower latency.
  • NSS_SO_MMF send a self-optimization function configuration message to the NSS_SO_F, which may include: an NSSI identifier, a trigger condition for automatically optimizing the NSSI capacity, and an option for NSSI capability adjustment.
  • the ability to modify NSSI is to add or delete several NFs by NSSMF, or to modify the characteristics of related NFs.
  • NSS_SO_F modify the capability parameter of NSSI, or NSS_SO_F performs self-optimization.
  • the NS_SO_MMF and the NSS_SO_MMF obtain authorization information from the SvMF, where the authorization information may be authorization information sent by the operator. That is, the SvMF or other policy management module can notify the operator to modify the configuration parameters of the NSI, and ask the operator to confirm whether it is allowed.
  • the S807 and the NSS_SO_MMF report the self-optimization result to the NS_SO_MMF, and may include the NSI ID, the NSSI ID, and the NSSI modified capability parameter.
  • the S808 and the NS_SO_MMF report the report information to the SvMF or other policy management module, where the report information is used to indicate a result of modifying the capability parameter of the first network slice subnet instance, or a self-optimization result.
  • the reporting information may include an NSI ID, an NSSI ID, and a modified capability parameter of the NSSI.
  • the automatic optimization function of the NSSI capability can be controlled by the NS_SO_MMF, the NSI can automatically adjust the requirements of the NSSI capability, and the flexibility of managing the NSI and the NSSI is improved, thereby improving the efficiency of managing the NSI.
  • the NSSMF when the capability of detecting the NSSI can be appropriately reduced, the NSSMF can automatically modify the NSSI capability, and reduce the resource consumption such as calculation and storage in the network; when the NSSMF detects that the NSSI capability can be changed, the service can be better.
  • the NSSI capability is automatically modified to optimize the support of the entire network slicing instance.
  • FIG. 9 is a schematic flowchart of a method 900 for managing a network slice instance according to an embodiment of the present application.
  • Method 900 can be applied to any of the network management architectures illustrated in Figures 1 through 5.
  • the first network device may be an NSMF module or an NS_SO_MMF module.
  • the NSMF module may include an NS_SO_MMF module and an NS_SO_F module
  • the second network device may be an NSSMF module or an NSS_SO_MMF module.
  • the third network device can be an SvMF or other policy management module.
  • method 900 includes:
  • the first network device determines to modify configuration parameters of the first network slice instance, where the first network slice instance includes at least one network slice subnet instance.
  • the first network device may be configured to manage the first network slice instance.
  • the first network device may be the aforementioned NSMF module, or the NS_SO_MMF module included in the NSMF module.
  • the first network slice instance may be composed of at least one network slice subnet instance. Modifying the configuration parameters of the first network slice instance may be understood as modifying the at least one network slice subnet instance.
  • the configuration parameter of the first network slice instance includes at least one of the following: a capacity size, a capability parameter, a location parameter, a topology parameter, a function parameter, and the like of the first network slice instance.
  • the first network device sends the first indication information to the at least one second network device, where the first indication information is used to indicate that the at least one second network device modifies the configuration of the at least one network slice subnet instance. parameter.
  • the configuration parameter of the network slice subnet instance may include: a capacity size of the network slice subnet instance, and a capability parameter of the network slice subnet instance.
  • the modifying the configuration parameter of the network slice instance may also be performed as performing self-optimization on the network slice instance.
  • Modifying the configuration parameters of the network slicing subnet instance can also be referred to as performing self-optimization on the network slicing subnet instance.
  • the NSSI capacity size is modified, such as the total number of users that the NSSI can support, the maximum number of connections on the control plane, the maximum number of PDU connections, and the total bandwidth.
  • the modification of the capability parameters of the NSSI can refer to some network characteristics. Modifications such as support for high mobility, medium mobility, low mobility; support for high latency, medium latency, low latency, etc.
  • the modification action may include adding an NF, deleting an NF, or updating an NF feature.
  • the first network device receives first reply information from the at least one second network device, where the first reply information is used to indicate a result of modifying a configuration parameter of the at least one network slice subnet instance.
  • the first network device may autonomously determine to modify the first network slice instance, where the first network slice instance includes at least one network slice subnet instance, and the second network device that manages the first network sliced subnet instance
  • the first indication information is sent to modify the network slice subnet instance, and the network slice instance can be flexibly modified, thereby improving the efficiency of managing the network slice instance.
  • the method 900 further includes: the first network device acquiring current configuration information of the at least one network slice subnet instance from the at least one second network device; the first network device determining to modify the first network
  • the configuration parameter of the slice instance includes: the first network device determines to modify a configuration parameter of the first network slice instance based on current configuration information of the at least one network slice subnet instance.
  • the first network device may send request information to the second network device, where the request information is used to instruct the second network device to send current configuration information of the network slice subnet instance to the first network device.
  • the second network device may periodically send the current configuration information of the network slice subnet instance to the first network device.
  • the first network device may compare the current configuration information of the network slice subnet instance with a preset rule to determine whether to modify the configuration parameter of the network slice subnet instance.
  • the preset rule may be a self-optimizing strategy below.
  • the first network device may send a request to the second network device to request the NSSI size, and the NSSMF is reported to be reported on time or the capacity established in the network slice subnet is reached. After a certain threshold is reported, when the NSI is composed of multiple NSSIs, multiple NSSMFs are requested to obtain the capacity occupation of each NSSI.
  • the method 900 further includes: the first network device receiving a self-optimization policy from the third network device, where the self-optimization policy is used to indicate a rule for modifying a network slice instance; the first network device determines to modify the first
  • the configuration parameter of the network slice instance includes: determining, by the first network device, the configuration parameter of the first network slice instance based on the self-optimization policy.
  • the foregoing third network device may be an SvMF module, or may be an operator server, or another network management module.
  • the self-optimization strategy may be a self-optimization strategy sent by the operator.
  • the self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, trigger condition of self-optimization function, effective range of self-optimization parameters, whether confirmation is required before optimization, and whether feedback optimization result is fed back Wait.
  • the method 900 further includes: the first network device sending report information to the third network device, where the report information is used to indicate a result of modifying configuration parameters of the first network slice instance.
  • the reporting information indicates a result of modifying the configuration parameter of the first network slice subnet instance, and may also be referred to as the report information indicating a result of performing self-optimization on the first network sliced subnet instance.
  • the report information may include the identifier of the first network slice instance, the identifier of the first network slice subnet instance, the modified configuration parameter, and the like.
  • the modified configuration parameter may include information such as the modified capacity size and the modified capability parameter.
  • FIG. 10 shows a schematic flowchart of a method 1000 for managing a network slice instance according to an embodiment of the present application.
  • the example of Figure 10 shows the process by which NSMF automatically optimizes the capacity of the NSI.
  • the first network device in the method 900 may be the NS_SO_MMF module in FIG. 10, or may be an NSMF module, where the NSMF module may include an NS_SO_MMF module and an NS_SO_F module.
  • the second network device in method 900 can be the NSSMF module of FIG.
  • the method 1000 includes:
  • NS_SO_MMF receives an NSI self-optimization policy from an SvMF module or other policy module.
  • the self-optimization strategy of the NSI may be a self-optimization strategy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: for example, whether to allow self-optimization for NSI, automatic optimization function to allow operation, trigger condition of self-optimization function, effective range of self-optimization parameter, whether confirmation is needed before optimization, whether or not Feedback optimization results, etc.
  • the NS_SO_MMF sends a configuration message to the NS_SO_F.
  • the configuration message may include: an NSI identifier, a trigger condition for automatically optimizing the NSI capacity, and a range of NSI capacity adjustment.
  • the capacity of the NSI can be measured by the number of supported users, the number of supported connections, and the total bandwidth.
  • the occupancy of the capacity can be measured by the proportion of occupancy.
  • this step may be regarded as an internal interaction of the network device.
  • S1003 and NS_SO_F are started in parallel according to the command of NS_SO_MMF, and a self-optimization algorithm is executed to monitor the occupancy of the NSI, including monitoring the NSSIs of the various NSIs.
  • S1004 and NS_SO_F send the request information to the NSSMF to request the capacity occupancy of the NSSI.
  • the NSSMF may be reported to be reported on time or after the NSSI capacity reaches a certain threshold.
  • the NS_SO_F may request multiple NSSMFs. Get the capacity occupancy of each NSSI.
  • S1005 and NSSMF report the NSSI capacity occupation status to NS_SO_F according to the request, at regular intervals, or when the capacity occupancy trigger threshold is reached.
  • S1006 and NS_SO_F determine whether the capacity occupancy of the current NSI exceeds a threshold according to the capacity of multiple NSSIs. If the threshold exceeds the threshold, the self-optimization action is triggered.
  • the current NSI supports the number of connections X.
  • the current capacity occupancy rate reaches 90%*X, and the number of NSI support connections is 150%*X.
  • the NS_SO_MMF and the NSSMF Before performing self-optimization on the NSSI, the NS_SO_MMF and the NSSMF obtain authorization information from the SvMF module or other policy module, where the authorization information may be authorization information sent by the operator. That is, the SvMF module or other policy module can be used to notify the operator that the configuration parameters of the NSI will be modified. Please check whether the carrier allows it.
  • S1008 Perform self-optimization results, configure the NSI, and expand the capacity, including requesting the NSSMF to expand the NSSI capacity.
  • the action of expanding the capacity includes: checking all the NSSIs included in the NSI, and the capacity supported by the NSSI, and determining that the capacity that each NSSI can support is expanded; for example, the NSSI 1 support capacity is X, and the NSSI 2 supports.
  • the capacity is 150% X, because each NSSI may support the NSI differently according to its own resources.
  • the NSSMF needs to be extended to expand the capacity of NSSI 1, that is, to send a capacity expansion request.
  • S1010 and NS_SO_F report the self-optimization result to the NS_SO_MMF, and may include an NSI ID, an NSSI ID, and a modified NSSI capacity.
  • the S1011, the NS_SO_MMF reports the report information to the SvMF module or the other policy module, where the report information is used to indicate the result of modifying the configuration parameter of the first network slice subnet instance, or the self-optimization result.
  • the report information may include information of the NSI ID and the size of the NSI modified capacity.
  • FIG. 11 is a schematic flowchart of a method 1100 for managing a network slice instance according to an embodiment of the present application. Method 1100 can be applied to any of the network management architectures illustrated in Figures 1 through 5.
  • the first network device may include an NF_SO_MMF module or an NFM module, where the NFM module may include an NF_SO_MMF module and an NF_SO_F module.
  • the second network device can include an NS_SO_MMF module.
  • the third network device may include a network function virtualization orchestrator (NFVO) module, and the NFVO module may be connected to at least one NF and may be used to manage the NF.
  • NFVO network function virtualization orchestrator
  • method 1100 includes:
  • the first network device determines that the first network function included in the first network slice instance needs to be optimized.
  • the first network device performs optimization processing on the first network function, where the optimization process includes: modifying configuration parameters of the first network function, or copying the first network function, and A network function is added to the first network slice instance, the first network slice instance including the second network function.
  • the foregoing first network function and the second network function may jointly provide services.
  • the first network device may automatically copy a second network function that is the same as the first network function, and add the second network function to the first network slice.
  • the service is provided in conjunction with the first network function.
  • the configuration parameters of the first network function may include: a location parameter, a topology parameter, and a function parameter of the first network function.
  • the first network device sends report information to the second network device, where the report information is used to indicate a result of the first network device performing optimization processing on the first network function, where the second network device is used by the second network device.
  • the first network slice instance is managed.
  • the reporting information indicates a result of optimizing configuration parameters of the first network function.
  • the reporting information may include the identifier of the first network slice instance, the identifier of the first network function, the identifier of the second network function, or the result information of the first network function replication.
  • the first network device may manage the first network function; the second network device manages the first network function by using the first network device, where the first network slice instance includes the first network function.
  • the network slice instance can be managed flexibly, and the efficiency of managing the network slice instance is improved.
  • the method 1100 further includes: the first network device receiving a self-optimization policy from the second network device, where the self-optimization policy is used to indicate a rule for modifying a network function;
  • the first network function performs optimization processing, including: the first network device performs optimization processing on the first network function based on the self-optimization policy.
  • the self-optimization policy may include an NSI identifier to indicate which NSI the self-optimization policy belongs to; an NF identifier, a command to enable the NF automatic replication function, a parameter and a threshold for triggering the NF automatic replication, for example, the number of users of the NF service, When the number of services reaches a certain threshold, automatic copying of the NF is performed.
  • the method 1100 further includes: the first network device acquiring authorization information from the second network device, where the authorization information is used to indicate that the first network function is allowed to be optimized.
  • the authorization information may be authorization information of the operator.
  • the first network device may obtain the operator authorization through the second network device, that is, notify the operator that the NF is to be optimized, and whether the permission is allowed.
  • the configuration parameter of the first network function includes: a location parameter of the first network function.
  • the location of the NF may be modified according to the traffic, resource status, and user characteristics in the network, for example, the user plane function (UPF) is migrated to a location closer to the user, or Migrate to a location with sufficient network resources.
  • the NF position automatic modification function is applicable to a scenario in which the network behavior can be predicted to a certain extent, and the position adjustment can be realized relatively quickly by setting a threshold and giving a plurality of selectable positions.
  • the method 1100 further includes: the first network device sends, to the third network device, reservation request information, where the reservation request information is used to indicate that the third network device is reserved for the first network function.
  • a network resource, the third network device is configured to allocate network resources for network functions.
  • the foregoing network resource may be a computing resource, a storage resource, or other type of resource allocated for the network function.
  • the network resource of the NF mainly refers to the virtual resource occupied by the NF, and therefore needs to have certain interaction with the device (ie, the third network device) that manages the network resource allocation of the network function.
  • the device ie, the third network device
  • the resources supporting NF are insufficient, for example, monitoring other processing parameters such as the processing speed of the NF, when the threshold is triggered, the resources are automatically increased for the NF within a certain range.
  • the first network device may instruct the third network device to reserve a certain resource for the NF, and automatically adjust the network resource corresponding to the NF within a certain range, so as to quickly improve the performance of the NF and better serve the service in the NSI.
  • FIG. 12 shows a schematic flowchart of a method 1200 for managing a network slice instance according to an embodiment of the present application.
  • the example of Figure 12 shows the process by which the NF_SO_MMF module replicates network functions.
  • the first network device in the method 1100 may be an NS_SO_MMF module, or may be an NSMF module, and the NSMF module may include an NS_SO_MMF module.
  • the second network device may be an NF_SO_MMF module or an NFM module, where the NFM module may include an NF_SO_MMF module and an NF_SO_F module.
  • method 1200 includes:
  • NS_SO_MMF receives an NSI self-optimization policy from the operator, and the self-optimization policy of the NSI may be a self-optimization policy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, whether confirmation is required before optimization, whether to feedback optimization results, and the like.
  • NS_SO_MMF sends an NF self-optimization policy to the NF_SO_MMF, where the self-optimization policy may include an NSI identifier to indicate which NSI the self-optimization policy belongs to; an NF identifier; a command to enable the NF automatic replication function; and a parameter and a threshold for triggering the NF automatic replication. . For example, if the number of users and the number of services of the NF service reach a certain threshold, automatic copying of the NF is performed.
  • S1203 and NF_SO_MMF are configured with NF_SO_F, and the content includes an NF identifier, a parameter that triggers automatic replication, and a threshold.
  • S1204 and NF_SO_F configure and execute an automatic copy function of the NF, and when detecting that the parameter reaches the threshold, perform an automatic copy action.
  • the NS_SO_MMF and the NF_SO_MMF obtain authorization information from the SvMF module or other policy module, where the authorization information may be authorization information sent by the operator. That is, the SvMF module or other policy module can be used to notify the operator that the configuration parameters of the NSI will be modified. Please check whether the carrier allows it.
  • NF_SO_F inform NF_SO_MMF about the NF automatic replication result.
  • NF_SO_MMF informs NS_SO_MMF about the NF automatic replication result, which may include the NSI identifier, the NF identifier, and the NF replication result.
  • the S1208 and the NS_SO_MMF report the report information to the SvMF module or other policy module, where the report information is used to indicate the result of modifying the configuration parameter of the NF, or the self-optimization result.
  • the reporting information may include an NSI identifier, an NF identifier, and a copy result of the NF.
  • an identical NF is automatically copied to jointly serve the NSI.
  • NF can be quickly copied and serviced to improve the performance of the entire NSI. This improves the efficiency of managing network slice instances.
  • FIG. 13 shows a schematic flowchart of a method 1300 for managing a network slice instance according to an embodiment of the present application.
  • the example of Figure 13 shows the process by which the NF_SO_MMF module optimizes the positional parameters of the network functions.
  • the first network device in the method 1100 may be an NS_SO_MMF module, or may be an NSMF module, and the NSMF module may include an NS_SO_MMF module.
  • the second network device may be an NF_SO_MMF module or an NFM module, where the NFM module may include an NF_SO_MMF module and an NF_SO_F module.
  • the method 1300 includes:
  • NS_SO_MMF receives an NSI self-optimization policy from the operator, and the self-optimization policy of the NSI may be a self-optimization policy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, whether confirmation is required before optimization, whether to feedback optimization results, and the like.
  • NS_SO_MMF sends an NF self-optimization policy to the NF_SO_MMF
  • the self-optimization policy may include an NSI identifier to indicate which NSI the self-optimization policy belongs to; an NF identifier, a parameter and a threshold for triggering automatic location modification; and an optional location list.
  • a method for identifying a location is an IP address of a virtual resource, and migrating the NF to the corresponding virtual resource realizes migration of the location.
  • NF_SO_MMF configure NF_SO_F, the content includes the NF identifier, parameters and thresholds that trigger automatic location modification, and an optional list of NF locations.
  • S1304 and NF_SO_F configure and execute the automatic position modification function of the NF, and modify the NF position when it detects that the parameter reaches the threshold.
  • the NS_SO_MMF and the NF_SO_MMF obtain authorization information from the SvMF module or other policy module, where the authorization information may be authorization information sent by the operator. That is, the SvMF module or other policy module can be used to notify the operator that the configuration parameters of the NSI will be modified. Please check whether the carrier allows it.
  • NF_SO_MMF informs NS_SO_MMF about the automatic modification result of the NF position, and may include the NSI identifier, the NF identifier, and the location of the NF.
  • the S1308 and the NS_SO_MMF report the report information to the SvMF module or other policy module, where the report information is used to indicate the result of modifying the configuration parameter of the NF, or the self-optimization result.
  • the reporting information may include an NSI identifier, an NF identifier, and a copy result of the NF.
  • the location of the NF may be changed to adapt to the change, and the performance of the entire NSI is improved.
  • Automatic position modification can quickly migrate NF to one of several optional locations. This can improve the efficiency of managing network slice instances.
  • FIG. 14 shows a schematic flowchart of a method 1400 for managing a network slice instance in an embodiment of the present application.
  • the example of Figure 14 shows the process by which NF_SO_MMF reserves network resources for network functions.
  • the first network device in the method 1100 may be an NS_SO_MMF module, or may be an NSMF module, and the NSMF module may include an NS_SO_MMF module.
  • the second network device may be an NF_SO_MMF module or an NFM module, where the NFM module may include an NF_SO_MMF module and an NF_SO_F module.
  • method 1400 includes:
  • the S1401 and the NS_SO_MMF receive an NSI self-optimization policy from the operator, and the self-optimization strategy of the NSI may be a self-optimization policy sent by the operator.
  • the NSI self-optimization strategy may include at least one of the following: whether to allow self-optimization for NSI, automatic optimization function that allows operation, whether confirmation is required before optimization, whether to feedback optimization results, and the like.
  • S1402 NS_SO_MMF sends resource reservation request information to the NFVO to request NFVO to reserve network resources for the NF.
  • the network resource includes a computing resource or a storage resource, and the reserved resource is used for resource expansion for the NF.
  • NS_SO_MMF issue an NF self-optimization policy to the NF_SO_MMF, which may include an NSI identifier to indicate which NSI the optimization policy belongs to; an NF identifier; a parameter and a threshold for triggering network resource modification; a range of network resource adjustment; and available network resources.
  • Identification such as virtual machine identification, storage identification, and so on.
  • the configuration includes the resource self-optimization function of the NF.
  • the configuration includes the NF identifier, the parameters and thresholds for triggering resource modification, the scope of resource self-optimization, and the available resource identifier.
  • the NS_SO_MMF and the NF_SO_MMF obtain authorization information from the SvMF module or other policy module, where the authorization information may be authorization information sent by the operator. That is, the SvMF module or other policy module can be used to notify the operator that the configuration parameters of the NSI will be modified. Please check whether the carrier allows it.
  • NF_SO_F3 inform NF_SO_MMF about the automatic optimization result of NF resources
  • NF_SO_MMF informs NS_SO_MMF about the result of automatic optimization of NF resources, and may include an NSI identifier, an NF identifier, and a resource of the NF.
  • S1409 and NS_SO_MMF notify the operator of the result of automatic optimization of the NF resource, and may include an NSI identifier, an NF identifier, and a resource of the NF.
  • the resources corresponding to the NF can be automatically adjusted within a certain range on the premise of reserved resources, and the performance of the NF can be quickly improved to better serve the services in the NSI. Thereby improving the efficiency of managing network slice instances.
  • FIG. 15 illustrates a method 1500 of managing a network slice instance.
  • the example of FIG. 15 can be applied to the network management architecture 300 of FIG.
  • NS_SO_MMF may send a self-optimization strategy for NSSI 1 to NSS_SO_MMF1, or may also send a self-optimization strategy of NSSI 2, or a self-optimization strategy of NSSI 2 Can be generated by NSS_SO_MMF1.
  • NSS_SO_MMF1 is configured for the NSS_SO_F2. For the configuration, refer to the corresponding content in Figure 6 to Figure 14, and details are not described here.
  • the method 1500 includes:
  • NS_SO_MMF sends a self-optimization strategy of NSS1 to NSS_SO_MMF1.
  • NS_SO_MMF may also send a self-optimization strategy of NSSI 2 to NSS_SO_MMF1.
  • NS_SO_MMF1 sends automation function configuration information to NSS_SO_F2.
  • NSS_SO_F2 send NSSI2 self-optimization result feedback to NSS_SO_MMF1.
  • NSS_SO_MMF1 send a self-optimization result of NSSI 1 to the NS_SO_MMF.
  • the NSS_SO_MMF1 may also send a self-optimization result of the NSSI 2 to the NS_SO_MMF.
  • FIG. 16 illustrates a method 1600 of managing a network slice instance.
  • the example of FIG. 16 can be applied to the network management architecture 400 of FIG.
  • NSSI nesting that is, when NSSI 1 includes NSSI2, NS_SO_MMF may send a self-optimization strategy for NSSI 2 to NSS_SO_MMF1, or may also send a self-optimization strategy of NSSI 2, or a self-optimization strategy of NSSI 2 may also Generated by NSS_SO_MMF1.
  • NSS_SO_MMF1 sends the self-optimization strategy of NSSI 2 to NSS_SO_MMF2.
  • the interaction between NSS_SO_MMF1 and NSS_SO_MMF2 includes sending a self-optimization strategy of NSSI 2, obtaining the operation of the NSSI 2 self-optimization function, and obtaining the self-optimization result of NSSI 2.
  • a self-optimization strategy of NSSI 2 obtaining the operation of the NSSI 2 self-optimization function, and obtaining the self-optimization result of NSSI 2.
  • the method 1600 includes:
  • NS_SO_MMF sends a self-optimization strategy of NSS1 to NSS_SO_MMF1.
  • NS_SO_MMF may also send a self-optimization strategy of NSSI 2 to NSS_SO_MMF1.
  • NS_SO_MMF1 sends a self-optimization strategy of NSSI 2 to NSS_SO_MMF2.
  • S1603 and NS_SO_MMF2 send automation function configuration information to NSS_SO_F2.
  • NSS_SO_F2 send NSSI2 self-optimization result feedback to NSS_SO_MMF2.
  • NSS_SO_MMF2 send NSSI2 self-optimization result feedback to NSS_SO_MMF1.
  • NSS_SO_MMF1 sends a self-optimization result of NSSI 1 to NS_SO_MMF.
  • NSS_SO_MMF1 may also send a self-optimization result of NSSI 2 to NS_SO_MMF.
  • FIG. 17 illustrates a method 1700 of managing network slice instances.
  • the example of FIG. 17 can be applied to the network management architecture 500 of FIG.
  • NSSI nesting that is, when NSSI 1 includes NSSI2, NS_SO_MMF directly sends a self-optimization strategy for NSSI 2 to NSS_SO_MMF2, and NSS_SO_MMF2 configures NSS_SO_F2.
  • NSSI nesting that is, when NSSI 1 includes NSSI2
  • NS_SO_MMF directly sends a self-optimization strategy for NSSI 2 to NSS_SO_MMF2
  • NSS_SO_MMF2 configures NSS_SO_F2.
  • For the configuration content refer to the corresponding content in FIG. 6 to FIG. , will not repeat them here.
  • the method 1700 includes:
  • NS_SO_MMF sends a self-optimization strategy of NSS2 to NSS_SO_MMF2.
  • NS_SO_MMF2 sends automation function configuration information to NSS_SO_F2.
  • NSS_SO_F2 send NSSI2 self-optimization result feedback to NSS_SO_MMF2.
  • NSS_SO_MMF2 send NSSI2 self-optimization result feedback to NSS_SO_MMF1.
  • NSS_SO_MMF2 send the self-optimization result of NSSI 2 to NS_SO_MMF.
  • the method for managing a network slice and the network management architecture of the embodiment of the present invention are described in detail above with reference to FIG. 1 to FIG. 17.
  • the network device of the embodiment of the present invention will be described in detail below with reference to FIG. 18 to FIG.
  • FIG. 18 is a schematic block diagram of a network device 1800 according to an embodiment of the present invention. It should be understood that the network device 1800 can perform the various steps performed by the first network device in the methods of FIGS. 6-8, which are not detailed herein to avoid repetition.
  • the network device 1800 includes: a processing unit 1801 and a communication unit 1802,
  • the processing unit 1801 is configured to determine that configuration parameters of the first network slice subnet instance need to be modified, the first network device is configured to manage the first network slice subnet instance, and modify the first network slice subnet a configuration parameter of the instance; and transmitting, by the communication unit 1802, report information to the second network device, the report information being used to indicate a result of modifying a configuration parameter of the first network slice subnet instance, wherein the second The network device is configured to manage the first network slice instance, and the first network slice instance includes the first network slice subnet instance.
  • FIG. 19 is a schematic block diagram of a network device 1900 according to an embodiment of the present invention. It should be understood that the network device 1900 can perform the various steps performed by the second network device in the methods of FIGS. 6-8, which are not described in detail herein to avoid repetition.
  • the network device 1900 includes: a processing unit 1901 and a communication unit 1902,
  • the processing unit 1901 is configured to receive report information from the first network device by using the communication unit 1902, where the report information is used to indicate a result of modifying a configuration parameter of the first network slice subnet instance, where the A network device is configured to manage the first network slice subnet instance, the second network device is configured to manage a first network slice instance, and the first network slice instance includes the first network slice subnet instance.
  • FIG. 20 is a schematic block diagram of a network device 2000 according to an embodiment of the present invention. It should be understood that the network device 2000 can perform the various steps performed by the first network device in the method of FIG. 9 or FIG. 10, and is not detailed herein to avoid repetition.
  • the network device 2000 includes: a processing unit 2001 and a communication unit 2002,
  • the processing unit 2001 is configured to determine to modify a configuration parameter of the first network slice instance, where the first network slice instance includes at least one network slice subnet instance; and send the first indication to the at least one second network device by using the communication unit 2002 Information, the first indication information is used to instruct the at least one second network device to modify configuration parameters of the at least one network slice subnet instance; and receive, by the communication unit 2002, the first network device from the at least one second network device And replying to the information, the first reply information is used to indicate a result of modifying a configuration parameter of the at least one network slice subnet instance.
  • FIG. 21 is a schematic block diagram of a network device 2100 according to an embodiment of the present invention. It should be understood that the network device 2100 can perform the various steps performed by the second network device in the method of FIG. 9 or FIG. 10, and is not detailed herein to avoid repetition.
  • the network device 2100 includes: a processing unit 2101 and a communication unit 2102,
  • the processing unit 2101 is configured to receive, by using the communication unit 2102, the first indication information that is sent by the first network device, where the first indication information is used to indicate that the second network device modifies the first network slice subnet instance, the first network
  • the device is configured to manage a first network slice instance, the first network slice instance includes the first network slice subnet instance; and send, by the communication unit 2102, first reply information to the first network device, The first reply information is used to indicate a result of modifying configuration parameters of the first network slice subnet instance.
  • FIG. 22 is a schematic block diagram of a network device 2200 according to an embodiment of the present invention. It should be understood that the network device 2200 can perform the various steps performed by the first network device in the methods of FIGS. 11-14, which are not detailed herein to avoid repetition.
  • the network device 2200 includes: a processing unit 2201 and a communication unit 2202,
  • the processing unit 2201 is configured to determine that the first network function included in the first network slice instance needs to be optimized; and perform optimization processing on the first network function, where the optimization process includes: modifying configuration parameters of the first network function Or copying the first network function and adding the second network function to the first network slice instance, the first network slice instance including the second network function; and through the communication
  • the unit 2202 sends the report information to the second network device, where the report information is used to indicate a result of the first network device performing optimization processing on the first network function, and the second network device is configured to manage the first Network slice instance.
  • FIG. 23 is a schematic block diagram of a network device 2300 according to an embodiment of the present invention. It should be understood that the network device 2300 can perform the various steps performed by the second network device in the methods of FIGS. 11-14, which are not detailed herein to avoid repetition.
  • the network device 2300 includes: a processing unit 2301 and a communication unit 2302,
  • the processing unit 2301 is configured to receive report information from the first network device by using the communication unit 2302, where the report information is used to indicate a result of modifying a configuration parameter of the first network slice subnet instance, where the first network
  • the device is configured to manage the first network slice subnet instance
  • the second network device is configured to manage a first network slice instance
  • the first network slice instance includes the first network slice subnet instance.
  • FIG. 24 is a schematic block diagram of a network device 2400 according to an embodiment of the present invention. It should be understood that the network device 2400 is capable of performing the various steps performed by the first network device in the methods of FIGS. 6-8, which are not described in detail herein in order to avoid redundancy.
  • Network device 2400 includes:
  • a memory 2410 configured to store a program
  • transceiver 2420 configured to communicate with other devices
  • the processor 2430 is configured to execute a program in the memory 2410. When the program is executed, the processor 2430 is configured to determine that configuration parameters of the first network slice subnet instance need to be modified, where the first network device is used to modify Managing the first network slice subnet instance; and modifying configuration parameters of the first network slice subnet instance; and transmitting, by the transceiver 2420, report information to the second network device, the report information being used to indicate modification a result of the configuration parameter of the first network slice subnet instance, wherein the second network device is configured to manage a first network slice instance, and the first network slice instance includes the first network slice subnet instance.
  • FIG. 25 is a schematic block diagram of a network device 2500 according to an embodiment of the present invention. It should be understood that the network device 2500 can perform the various steps performed by the second network device in the methods of FIGS. 6-8, which are not described in detail herein to avoid repetition.
  • Network device 2500 includes:
  • a memory 2510 configured to store a program
  • a transceiver 2520 configured to communicate with other devices
  • the processor 2530 is configured to execute a program in the memory 2510. When the program is executed, the processor 2530 is configured to receive, by the transceiver 2520, report information from the first network device, where the report information is used to indicate a modification. a result of a configuration parameter of a first network slice subnet instance, wherein the first network device is configured to manage the first network slice subnet instance, and the second network device is configured to manage a first network slice instance, The first network slice instance includes the first network slice subnet instance.
  • FIG. 26 is a schematic block diagram of a network device 2600 according to an embodiment of the present invention. It should be understood that the network device 2600 can perform the various steps performed by the first network device in the method of FIG. 9 or FIG. 10, and is not described in detail herein to avoid repetition.
  • Network device 2600 includes:
  • a memory 2610 configured to store a program
  • a transceiver 2620 configured to communicate with other devices
  • the processor 2630 is configured to execute a program in the memory 2410, when the program is executed, the processor 2630 is configured to determine to modify configuration parameters of the first network slice instance, where the first network slice instance includes at least one network And the first indication information is sent to the at least one second network device by the transceiver 2620, where the first indication information is used to instruct the at least one second network device to modify the at least one network slice subnet instance a configuration parameter; and receiving, by the transceiver 2620, first reply information from the at least one second network device, the first reply information being used to indicate a result of modifying a configuration parameter of the at least one network slice subnet instance.
  • FIG. 27 is a schematic block diagram of a network device 2700 according to an embodiment of the present invention. It should be understood that the network device 2700 can perform the various steps performed by the second network device in the method of FIG. 9 or FIG. 10, and is not detailed herein to avoid repetition.
  • Network device 2700 includes:
  • a memory 2710 configured to store a program
  • the transceiver 2720 is configured to communicate with other devices;
  • the processor 2730 is configured to execute a program in the memory 2710, when the program is executed, the processor 2730 is configured to receive, by using the transceiver 2720, first indication information sent by the first network device, where the first indication information is And the first network device is configured to modify the first network slice subnet instance, where the first network slice instance includes the first network slice subnet instance Transmitting, by the transceiver 2720, the first reply information to the first network device, where the first reply information is used to indicate a result of modifying a configuration parameter of the first network slice subnet instance.
  • Network device 2800 includes:
  • a memory 2810 configured to store a program
  • transceiver 2820 configured to communicate with other devices
  • a processor 2830 configured to execute a program in the memory 2810, when the program is executed, the processor 2830 is configured to determine that a first network function included in the first network slice instance needs to be optimized; and to the first network The function performs optimization processing, including: modifying a configuration parameter of the first network function, or copying the first network function, and adding the second network function to the first network slice instance
  • the first network slice instance includes the second network function; and the report information is sent to the second network device by the transceiver 2820, where the report information is used to indicate the first network device to the first network function
  • the second network device is configured to manage the first network slice instance.
  • FIG. 29 is a schematic block diagram of a network device 2900 according to an embodiment of the present invention. It should be understood that the network device 2900 is capable of performing the various steps performed by the second network device in the methods of FIGS. 11-14, which are not described in detail herein to avoid repetition.
  • Network device 2900 includes:
  • a memory 2910 configured to store a program
  • transceiver 2920 for communicating with other devices
  • the processor 2930 is configured to execute a program in the memory 2910. When the program is executed, the processor 2930 is configured to receive, by the transceiver 2920, report information from the first network device, where the report information is used to indicate the modification. a result of a configuration parameter of a first network slice subnet instance, wherein the first network device is configured to manage the first network slice subnet instance, and the second network device is configured to manage a first network slice instance, The first network slice instance includes the first network slice subnet instance.
  • 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 purpose of the solution of the embodiment.
  • 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.

Landscapes

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

Abstract

一种管理网络切片实例的方法、装置和系统。包括：第一网络设备确定第一网络切片子网实例的配置参数需要修改，第一网络设备用于管理第一网络切片子网实例；第一网络设备修改第一网络切片子网实例的配置参数；第一网络设备向第二网络设备发送汇报信息，汇报信息用于指示修改第一网络切片子网实例的配置参数的结果，其中，第二网络设备用于管理第一网络切片实例，第一网络切片实例包括第一网络切片子网实例。

Description

管理网络切片实例的方法、装置和系统
本申请要求于2017年03月20日提交中国专利局、申请号为201710167282.8、发明名称为“管理网络切片实例的方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及管理网络切片实例的方法、装置和系统。
背景技术
随着移动通信的高速发展，未来的移动通信系统需要满足多样化的业务需求，例如，增强型移动宽带，大规模机器类通信、超高可靠与低延迟的通信等。因此在下一代移动通信系统中提出了网络切片的概念。网络切片技术是指将网络在逻辑上抽象为一个或者多个网络切片，其中每个网络切片包含一系列的逻辑网络功能，一个网络切片可以满足某一类或一个用例的连接通信服务需求。下一代移动通信系统可以由满足不同连接能力的大量网络切片组成。
在通信网络中，如何提供一种有效的网络管理方式，以满足网络切片层面灵活的管理需求，是一个亟待解决的问题。
发明内容
本申请提供一种管理网络切片实例的方法、装置和系统，能够提高管理网络切片实例的效率。
第一方面，提供了一种管理网络切片实例的方法，包括：第一网络设备确定第一网络切片子网实例的配置参数需要修改，所述第一网络设备用于管理所述第一网络切片子网实例；所述第一网络设备修改所述第一网络切片子网实例的配置参数；所述第一网络设备向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
在本申请实施例中，管理第一网络切片子网实例的第一网络设备可以自主确定第一网络切片子网实例的配置参数需要修改，并向第二网络设备上报修改第一网络切片子网实例的配置参数的结果。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。
在一种可能的实现方式中，还包括：所述第一网络设备从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则；所述第一网络设备修改所述第一网络切片子网实例的配置参数，包括：所述第一网络设备基于所述自优化策略，修改所述第一网络切片子网实例的配置参数。
在一种可能的实现方式中，还包括：所述第一网络设备从所述第二网络设备接收授权 信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
在一种可能的实现方式中，还包括：所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
第二方面，提供了一种管理网络切片实例的方法，包括：第二网络设备从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设发送自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则。
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
在一种可能的实现方式中，还包括：所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
第三方面，提供了一种管理网络切片实例的方法，包括：第一网络设备确定修改第一网络切片实例的配置参数，所述第一网络切片实例包括至少一个网络切片子网实例；所述第一网络设备向至少一个第二网络设备发送第一指示信息，所述第一指示信息用于指示所述至少一个第二网络设备修改所述至少一个网络切片子网实例的配置参数；所述第一网络设备从所述至少一个第二网络设备接收第一回复信息，所述第一回复信息用于指示修改所述至少一个网络切片子网实例的配置参数的结果。
在本申请实施例中，第一网络设备可以自主确定修改第一网络切片实例，第一网络切片实例包括至少一个网络切片子网实例，并向管理第一网络切片子网实例的第二网络设备发送第一指示信息，以修改网络切片子网实例，能够灵活地修改网络切片实例，从而提高了管理网络切片实例的效率。
在一种可能的实现方式中，还包括：所述第一网络设备从所述至少一个第二网络设备获取所述至少一个网络切片子网实例的当前配置信息；所述第一网络设备确定修改第一网络切片实例的配置参数，包括：所述第一网络设备基于所述至少一个网络切片子网实例的当前配置信息，确定修改所述第一网络切片实例的配置参数。
在一种可能的实现方式中，在所述第一网络设备向至少一个第二网络设备发送第一指示信息之前，还包括：所述第一网络设备从第三网络设备获取授权信息，所述授权信息用于指示允许修改所述第一网络切片实例的配置参数。
在一种可能的实现方式中，还包括：所述第一网络设备从第三网络设备接收自优化策略，所述自优化策略用于指示修改网络切片实例的规则；所述第一网络设备确定修改第一网络切片实例的配置参数，包括：所述第一网络设备基于所述自优化策略，确定修改所述第一网络切片实例的配置参数。
在一种可能的实现方式中，还包括：所述第一网络设备向第三网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片实例的配置参数的结果。
在一种可能的实现方式中，还包括：所述第一网络切片实例的配置参数包括以下至少一种：所述第一网络切片实例的容量大小、所述第一网络切片实例的能力参数。
第四方面，提供了一种管理网络切片实例的方法，包括：第二网络设备接收第一网络 设备发送的第一指示信息，所述第一指示信息用于指示所述第二网络设备修改第一网络切片子网实例，所述第一网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例；所述第二网络设备向所述第一网络设备发送第一回复信息，所述第一回复信息用于指示修改所述第一网络切片子网实例的配置参数的结果。
在一种可能的实现方式中，所述方法还包括：所述第二网络设备向所述第一网络设备发送所述第一网络切片子网实例的当前配置信息。
在一种可能的实现方式中，所述第一网络切片实例的配置参数包括以下至少一种：所述第一网络切片实例的容量大小、所述第一网络切片实例的能力参数。
第五方面，提供了一种管理网络切片实例的方法，包括：第一网络设备确定第一网络切片实例包括的第一网络功能需要优化；第一网络设备对所述第一网络功能进行优化处理，所述优化处理包括：修改所述第一网络功能的配置参数，或，复制所述第一网络功能，并将所述第二网络功能加入到所述第一网络切片实例中，所述第一网络切片实例包括所述第二网络功能；所述第一网络设备向第二网络设备发送汇报信息，所述汇报信息用于指示所述第一网络设备对所述第一网络功能进行优化处理的结果，所述第二网络设备用于管理所述第一网络切片实例。
在本申请实施例中，所述第一网络设备可以管理第一网络功能；第二网络设备通过第一网络设备管理第一网络功能，第一网络切片实例包含第一网络功能。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。
在一种可能的实现方式中，还包括：所述第一网络设备从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络功能的规则；所述第一网络设备对所述第一网络功能进行优化处理，包括：所述第一网络设备基于所述自优化策略，对所述第一网络功能进行优化处理。
在一种可能的实现方式中，所述第一网络设备从第二网络设备获取授权信息，所述授权信息用于指示允许对所述第一网络功能进行优化处理。
在一种可能的实现方式中，所述第一网络功能的配置参数包括：所述第一网络功能的位置参数、拓扑参数、功能参数。
在一种可能的实现方式中，还包括：所述第一网络设备向第三网络设备发送预留请求信息，所述预留请求信息用于指示所述第三网络设备为所述第一网络功能预留网络资源，所述第三网络设备用于为网络功能分配网络资源。
第六方面，提供了一种管理网络切片实例的方法，包括：第二网络设备从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络功能的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络功能，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络功能。
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送自优化策略，所述自优化策略用于指示修改网络功能的规则。
在一种可能的实现方式中，还包括：所述第二网络设备向所述第一网络设备发送授权信息，所述授权信用于指示允许修改所述第一网络功能的配置参数。
在一种可能的实现方式中，所述第一网络功能的配置参数包括：所述第一网络功能的位置参数、拓扑参数、功能参数。
第七方面，提供了一种管理网络切片实例的网络设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第八方面，提供了另一种管理网络切片实例的网络设备，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第九方面，提供了另一种管理网络切片实例的网络设备，用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第三方面或第三方面的任意可能的实现方式中的方法的单元。
第十方面，提供了另一种管理网络切片实例的网络设备，用于执行上述第四方面或第四方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第四方面或第四方面的任意可能的实现方式中的方法的单元。
第十一方面，提供了另一种管理网络切片实例的网络设备，用于执行上述第五方面或第五方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第五方面或第五方面的任意可能的实现方式中的方法的单元。
第十二方面，提供了另一种管理网络切片实例的网络设备，用于执行上述第六方面或第六方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第六方面或第六方面的任意可能的实现方式中的方法的单元。
第十三方面，提供了一种网络系统，该系统包括上述第七方面、第八方面所述的网络设备，或包括上述第九方面和第十方面所述的网络设备、或包括上述第十一方面和第十二方面所述的网络设备。
第十四方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第十五方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第十六方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第三方面或第三方面的任意可能的实现方式中的方法。
第十七方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口 接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第四方面或第四方面的任意可能的实现方式中的方法。
第十八方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第五方面或第五方面的任意可能的实现方式中的方法。
第十九方面，提供了一种管理网络切片实例的网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第六方面或第六方面的任意可能的实现方式中的方法。
第二十方面，提供了一种网络系统，该系统包括上述第十四方面、第十五方面所述的网络设备，或包括上述第十六方面和第十七方面所述的网络设备、或包括上述第十八方面和第十九方面所述的网络设备。
附图说明
图1是本申请实施例的网络管理架构的示意图。
图2是本申请又一实施例的网络管理架构的示意图。
图3是本申请又一实施例的网络管理架构的示意图。
图4是本申请又一实施例的网络管理架构的示意图。
图5是本申请又一实施例的网络管理架构的示意图。
图6是本申请实施例的管理网络切片实例的方法的示意图。
图7是本申请又一实施例的管理网络切片实例的方法的示意图。
图8是本申请又一实施例的管理网络切片实例的方法的示意图。
图9是本申请又一实施例的管理网络切片实例的方法的示意图。
图10是本申请又一实施例的管理网络切片实例的方法的示意图。
图11是本申请又一实施例的管理网络切片实例的方法的示意图。
图12是本申请又一实施例的管理网络切片实例的方法的示意图。
图13是本申请又一实施例的管理网络切片实例的方法的示意图。
图14是本申请又一实施例的管理网络切片实例的方法的示意图。
图15是本申请又一实施例的管理网络切片实例的方法的示意图。
图16是本申请又一实施例的管理网络切片实例的方法的示意图。
图17是本申请又一实施例的管理网络切片实例的方法的示意图。
图18是本申请实施例的网络设备的示意图。
图19是本申请又一实施例的网络设备的示意图。
图20是本申请又一实施例的网络设备的示意图。
图21是本申请又一实施例的网络设备的示意图。
图22是本申请又一实施例的网络设备的示意图。
图23是本申请又一实施例的网络设备的示意图。
图24是本申请又一实施例的网络设备的示意图。
图25是本申请又一实施例的网络设备的示意图。
图26是本申请又一实施例的网络设备的示意图。
图27是本申请又一实施例的网络设备的示意图。
图28是本申请又一实施例的网络设备的示意图。
图29是本申请又一实施例的网络设备的示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
在介绍本申请的管理网络切片实例的方法、装置和系统之前，为了便于理解本申请的内容，先描述本文中出现的一些个术语和网络切片管理系统。
网络切片(Network slice)：指在物理或者虚拟的网络基础设施之上，根据不同的服务需求定制化不同的逻辑网络。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供电信服务，具有一定网络能力；网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合，例如，网络切片只包含接入网和核心网。网络切片可能具有如下一个或多个特性：接入网可能切片，也可能不切片。接入网可能是多个网络切片共用的。不同的网络切片的特性和组成它们的网络功能可能是不一样。
网络切片实例(Network slice instance,NSI)：是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种服务。网络切片实例可以由网管系统创建，一个网管系统可能创建多个网络切片实例并同时对它们进行管理，包括在网络切片实例运行过程中的性能监视和故障管理等。当多个网络切片实例共存时，网络切片实例之间可能共享部分网络资源和网络功能。网络切片实例可能从网络切片模板创建，也可能不从网络切片模板创建。一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例(network slice subnet instance)和/或网络功能。网络功能可以包括物理网络功能和/或虚拟网络功能。以下统称物理网络功能和/或虚拟网络功能为网络功能。
网络切片子网实例(network slice subnet instance)：网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由其他方式组成集合。网络切片子网实例可能被多个网络切片实例共享。提出网络切片子网实例，可以方便网管系统管理。一个网络切片实例可能由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或若干网络切片子网实例组成；一个网络切片实例可能由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能组成；一个网络切片实例也可能仅由若干网络功能组成。
网络功能(Network function,NF)：是网络中的一种处理功能，定义了功能性的行为和接口，网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为 物理网络功能和虚拟网络功能。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能，具体地，对于多个(子)网络切片实例而言，可以独立地使用不同的网络功能，这种网络功能称为专属网络功能，也可以共享同一个网络功能，这种网络功能称为共享网络功能。
网络切片自动优化：是指网络切片实例(Network slice instance，NSI)能在持续提供服务的同时，自动化的更改配置，从而适应动态变化的流量、拓扑、网络资源、业务状态等。网络切片管理系统监控网络切片实例的若干参数，并在允许的范围内自动化地修改NSI有关的配置，提高整体性能。网络切片自动优化的概念属于网络切片的自动化编排和管理，尽量避免对服务的影响，尽量减少人工参与。
图1示出了本申请实施例的网络架构100的示意图。图1中的各个模块的功能和接口如下所述：
服务管理功能模块(Sevice management function,SvMF)：负责将运营商和/或第三方客户的电信服务需求转化为对网络切片的需求，向NSMF发送对网络切片的需求，接收运营商和/或第三方客户对网络切片管理数据(例如性能数据、故障数据、故障修复数据等)的订阅需求，从NSMF获取网络切片的管理数据等。
网络切片管理功能模块(network slice management function,NSMF)：负责接收SvMF发送的网络切片需求，对网络切片实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)，编排网络切片实例的组成，分解网络切片实例的需求为各网络切片子网实例的需求，向各NSSMF发送网络切片子网实例管理请求，向EM发送网络功能管理请求。
网络切片子网管理功能模块(network slice subnet management function,NSSMF)：从NSMF接收对网络切片子网实例的需求，从而对网络切片子网实例的生命周期、性能、故障等进行管理(以下将生命周期、性能、故障管理简称管理)，编排网络切片实例的组成。
网络功能管理模块(network function management,NFM):用于管理NF，是一个逻辑实体，可以独立于NF存在，也可以位于NF，或者位于其它的功能模块，用于实现对NF的管理例如管理NF的生命周期，配置NF的功能参数，为NF分配网络资源等。
接口1：SvMF和NSMF之间的接口，用于SVMF向NSMF发送业务对网络切片的需求，NSMF向SVMF反馈NSI和业务的运行情况，并提供一定的管理数据。
接口2：NSMF和NSSMF之间的接口，NSMF在管理和编排NSI时，通过该接口向NSSMF传递对NSSI的需求，例如创建、修改、获取管理数据等，NSSMF通过该接口向NSMF反馈有关NSSI的信息。
接口3：NSMF和NFM之间的接口，适用于NSMF能够感知并且管理NF的场景，即NSMF通过该接口和NFM交互，发送对NF进行管理和配置命令；NFM通过该接口接收来自NSMF的消息，并且通过该接口反馈关于NF的信息。
接口4：NSSMF之间的接口，用于NSSMF之间的互相协调，NSSMF通过该接口请求另一个NSSMF对其所管辖的NSSI进行管理，包括生命周期管理、性能管理、故障管理等。
另外，图1中还展示了几种NSI的组成方式，包括：NSI由若干个NSSI组成；NSI由若干个NSSI，以及若干个NF组成；NSI由若干个NF组成。
本申请的方案可以适用于两种场景，第一种为NSMF仅管理NSSMF，感知不到NF的信息，也不能管理NF；第二种为NSMF可以感知并直接管理NF，可以类似于传统网管系统，也可以通过其它新的网络功能管理功能，例如，在图2所示的网络管理架构200中，NSMF可以通过网络功能管理器NFM对NF直接进行管理。
图2是本申请实施例中的网络管理架构200的结构示意图。如图2所示，网络管理架构200可以用于管理网络切片实例。网络管理架构200中的模块的功能可以与网络管理架构100对应的模块的功能相同或相似。下文介绍网络管理架构200包括的各个模块。
A.网络切片自优化监控和管理模块(network slice self-optimization monitor and management function，NS_SO_MMF)，该模块可以包括并不限于以下功能中的至少一项：
负责从运营商接收网络切片自优化策略；
生成NSI自优化功能需要的相关参数主要包括需要监测的NSI参数、触发自优化的阈值、NSI自优化的范围；
监控和管理NSI自优化功能；
与NSS_SO_MMF通信，为NSSI自优化功能提供优化策略，并且获知NSSI自优化功能的运行情况，获取NSSI的自优化结果。
B.网络切片子网自优化监控和管理模块(network slice subnet self-optimization monitor and management function，NSS_SO_MMF)，该模块可以包括并不限于以下功能中的至少一项：
与NS_SO_MMF通信，接收NSSI自优化功能的优化策略，并且上报NSSI自优化功能的运行情况，以及相关的自优化结果；
也可以根据NSSI的情况，决定在NSSI内部做自优化，并不与NS_SO_MMF协调，这种情况属于内部动作；
生成NSSI自优化功能需要的相关参数主要包括需要监测的NSSI参数、触发自优化的阈值、NSSI自优化的范围；
监控管理NSSI自优化功能。
C.网络功能自优化监控和管理功能模块(network function self-optimization monitor and management function,NF_SO_MMF)，该模块可以包括并不限于以下功能中的至少一项：
与NS_SO_MMF通信，接收NF自优化功能的优化策略，并且上报NF自优化功能的运行情况；
生成NF自优化功能需要的相关参数主要包括需要监测的NF参数、触发自优化的阈值、NF自优化的范围；
监控管理NF自优化功能。
D.网络功能自优化功能模块(network slice self-optimization function,NS_SO_F),该模块可以包括并不限于以下功能中的至少一项：
与NS_SO_MMF通信，接收NSI的自优化策略，并反馈自优化的结果；
执行NSI自优化算法；
根据NSI自优化算法的输出结果，调整NSI的配置。
E.网络切片子网自优化功能模块(network slice subnet self-optimization function, NSS_SO_F)，该模块可以包括但并不限于以下功能中的至少一项：
与NSS_SO_MMF通信，接收NSSI的自优化策略，并反馈自优化的结果；
执行NSSI自优化算法；
根据NSSI自优化算法的输出结果，调整NSSI的配置。
F.网络功能自优化模块(network function self-optimization function,NF_SO_F)，该模块可以包括但并不限于以下功能中的至少一项：
与NF_SO_MMF通信，接收NF的自优化策略，并反馈自优化的结果；
执行NF自优化算法；
根据NF自优化算法的输出结果，调整NF的参数配置、资源配置；
需要说明的是，图2中的NSFM、NSSMF以及NFM的功能可以与图1中相应的模块具有相同或相似的功能。图2中的接口2和接口3可以是图1中相应的接口。其中，NSMF可以包括NS_SO_MMF，NSSMF可以包括NSS_SO_MMF，NFM可以包括NF_SO_MMF。
可选地，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交互来管理NSSI 2，该选项适用于NSSMF 1和NSSMF 2之间有直接接口的场景下；选项2是由NSMF来管理NSSI 2。
在NSSI允许嵌套的情况下，图3至图5分别示出了三种本申请实施例的网络管理架构。
图3是本申请实施例的网络管理架构300的结构示意图。如图3所示，被嵌套的NSSI的NSS_SO_F2由上一层NSSI的NSS_SO_MMF1管理；上一层的NSS_SO_MMF1又被NS_SO_MMF管理。
在网络管理架构300中，NS_SO_MMF向NSS_SO_MMF1发送有关NSSI 1的自优化策略的同时，也可以发送NSSI 2的自优化策略，NSSI 2的自优化策略也可以由NSS_SO_MMF1生成。NSS_SO_MMF1可以对NSS_SO_F2进行配置。
图4是本申请实施例的网络管理架构400的结构示意图。如图4所示，被嵌套的NSSI的NSS_SO_F2可以直接由NSS_SO_MMF2管理,NSS_SO_MMF2从NSS_SO_MMF1接收策略。
在网络管理架构400中，NS_SO_MMF向NSS_SO_MMF1发送有关NSSI 1的自优化策略的同时，也可以发送NSSI 2的自优化策略(NSSI 2的自优化策略也可以由NSS_SO_MMF1生成)。NSS_SO_MMF1将NSSI 2的自优化策略发送给NSS_SO_MMF2，NSS_SO_MMF1和NSS_SO_MMF2之间的交互包括发送NSSI 2的自优化策略，获得NSSI2自优化功能的运行情况，以及获取NSSI 2的自优化结果。
图5是本申请实施例的网络管理架构500的结构示意图。如图5所示，被嵌套的NSSI的NSS_SO_F2由它本身的NSS_SO_MMF2管理；它自身的NSS_SO_MMF2可以由NS_SO_MMF管理。另外NSS_SO_MMF2与NSS_SO_MMF1之间可以存在着一些协调关系，因为被嵌套的NSSI自动优化后，可能需要将优化结果通知到上一层的NSSI。
在网络管理架构500中，NS_SO_MMF可以直接向NSS_SO_MMF2发送有关NSSI2的自优化策略。
此外，应当注意的是，上述引入的各个功能模块和单元，是从它们所具有的功能的角度考虑的。实际应用中，上述各功能模块可以是单独的物理存在，也可以是两个或两个以上设备集成在一个单元中，例如，NS_SO_MMF模块和NS_SO_F模块可以合并为一个功能模块，该功能模块具有NS_SO_MMF模块和NS_SO_F模块的所有功能，或者NS_SO_MMF模块和NS_SO_F模块可以分别是独立的模块，并通过模块之间的接口进行通信。本领域普通技术人员在本发明揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本发明的保护范围之内。
上文介绍了本申请实施例的网络管理架构，下文将结合附图，介绍本申请实施例的管理网络切片实例的方法、装置和系统。
图6是本申请实施例的管理网络切片实例的方法600的示意性流程图。方法600可以应用于图1至图5所示的任一种网络管理架构中。可选地，在图6中，第一网络设备可以是NSSMF模块或NSS_SO_MMF模块，NSSMF模块可以包括NSS_SO_MMF模块和NSS_SO_F模块；第二网络设备可以是NSMF模块或NS_SO_MMF模块。
如图6所示，方法600包括：
S601，第一网络设备确定第一网络切片子网实例的配置参数需要修改，所述第一网络设备用于管理所述第一网络切片子网实例。
S602，所述第一网络设备修改所述第一网络切片子网实例的配置参数。
可选地，第一网络切片子网实例的配置参数可以包括：所述第一网络切片子网实例的容量大小、能力参数、位置参数、拓扑参数、功能参数等。本申请对此不作限定。
可选地，在本申请实施例中，上述修改所述第一网络切片子网实例的配置参数，也可以称为对所述第一网络切片子网实例执行自优化。
对NSSI容量大小的修改可以指修改NSSI所能够支持的总用户数、控制面最大连接数、最大的PDU连接数、总带宽等；对NSSI的能力参数的修改可以指在一些网络特性方面的修改，例如支持高移动性、中移动性、低移动性；支持高时延、中等时延、低时延等。在第一网络设备具体修改NSSI时，修改动作可以包括增加一个NF、删除一个NF，或者更新一个NF的特性。
S603，所述第一网络设备向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
可选地，上述汇报信息指示修改所述第一网络切片子网实例的配置参数的结果，也可以称为，上述汇报信息指示对所述第一网络切片子网实例执行自优化的结果。
可选地，上述汇报信息可以包括被第一网络切片实例的标识，第一网络切片子网实例的标识、修改后的配置参数等信息。例如，修改后的配置参数可以包括修改后的容量大小、修改后的能力参数等信息。
在本申请实施例中，管理第一网络切片子网实例的第一网络设备可以自主确定第一网络切片子网实例的配置参数需要修改，并向第二网络设备上报修改第一网络切片子网实例的配置参数的结果。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。
可选地，第一网络设备确定第一网络切片子网实例的配置参数需要修改，包括：所述第一网络设备从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络切 片子网实例的规则；所述第一网络设备修改所述第一网络切片子网实例的配置参数，包括：所述第一网络设备基于所述自优化策略，修改所述第一网络切片子网实例的配置参数。
可选地，第二网络设备可以根据整个NSI的自优化策略，决策获得每个NSSI的自优化策略，并将每个NSSI的自优化策略发送给对应的NSS_SO_MMF。自优化策略的内容可以包括以下至少一种：NSI的标识，以用于指示该自优化策略是属于哪个NSI；NSSI的标识，以指示该自优化策略应用于哪个NSSI；触发优化的参数阈值，NSSI容量可以调整的范围。
可选地，第二网络设备可以从从运营商提供的其它管理模块(如SvMF、策略管理模块等)接收NSI的自优化策略，并基于该NSI自优化策略，向第一网络设备发送自优化策略。该NSI的自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：是否允许对NSI自优化、允许运行的自动优化功能、自优化功能的触发条件、自优化参数的有效范围、是否需要在优化前获得确认、是否反馈优化结果等。
可选地，方法600还包括：所述第一网络设备从所述第二网络设备接收授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
例如，该授权信息可以是运营商的授权信息。在执行对NSI配置之前，第一网络设备可以通过第二网络设备获得运营商授权，即通知运营商即将对NSI容量进行的改动，确认是否允许。
作为一个具体示例，图7示出了本申请实施例的管理网络切片实例的方法700的示意性流程图。图7的例子给出了NSSMF对NSSI的容量大小进行自动优化的过程。在图7中，方法600中的第二网络设备可以是NS_SO_MMF模块，方法600中的第一网络设备可以是NSS_SO_MMF模块，或者NSSMF模块。其中，NSSMF模块包括NSS_SO_MMF模块和NSS_SO_F模块。
如图7所示，该方法700包括：
S701、NS_SO_MMF从SvMF或其它策略管理模块接收NSI自优化策略。该NSI的自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、自优化功能的触发条件、自优化参数的有效范围、允许运行的自动优化功能、是否需要在优化前获得确认、是否反馈优化结果等。
S702、NS_SO_MMF根据整个NSI的自优化策略，决策获得每个NSSI的自优化策略，并将每个NSSI的自优化策略发送给NSS_SO_MMF。自优化策略的内容可以包括以下至少一种：NSI的标识，以用于指示该自优化策略是属于哪个NSI；NSSI的标识，以指示该自优化策略应用于哪个NSSI；触发优化的参数阈值，NSSI容量可以调整的范围。
S703、NSS_SO_MMF给NSS_SO_F发送自优化功能配置消息，可以包括：NSSI标识，NSSI容量自动优化的触发条件，NSSI容量调整的范围。NSSI的容量可以由支持的用户数、支持的连接数、总带宽等参数来衡量。可选地，当NSS_SO_MMF和NSS_SO_F设置在同一网络设备时，本步骤可以视为网络设备的内部的交互。
S704、NSS_SO_F修改NSSI的容量大小，或者，换句话说，NSS_SO_F对NSSI执行自优化。
S705、在对NSSI执行自优化之前，NS_SO_MMF和NSS_SO_MMF从SvMF获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF或其它策略管理模 块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。
S706、NSS_SO_F向NSS_SO_MMF上报自优化结果。
S707、NSS_SO_MMF向NS_SO_MMF上报自优化结果，可以包含NSI ID，NSSI ID，以及修改后的NSSI容量。
S708、NS_SO_MMF向SvMF或其它策略管理模块上报汇报信息，所述汇报信息用于指示修改NSSI的配置参数的结果，或者说自优化结果。汇报信息可以包含NSI ID，NSSI ID，或NSSI修改后的容量大小的信息。
在本申请实施例中，可以通过NS_SO_MMF控制NSSI的容量自动优化功能，满足NSI对其包括的NSSI的容量自动调整需求。提高了管理NSI和NSSI的灵活性，进而提高了管理NSI的效率。
在本申请实施例中，当NSSI的容量占用达到一定阈值时，NSSMF可以自动确定扩大或缩小容量，优化性能、提高了资源利用率。
作为一个具体示例，图8是本申请另一实施例的管理网络切片的方法800的示意性流程图。方法800给出了NSSMF对NSSI的能力参数进行自动优化的过程。在图8中，方法600中的第二网络设备可以是NS_SO_MMF模块，方法600中的第一网络设备可以是NSS_SO_MMF模块，或者NSSMF模块。其中，NSSMF模块包括NSS_SO_MMF模块和NSS_SO_F模块。
如图8所示，该方法800包括：
S801、NS_SO_MMF从SvMF或其它策略管理模块接收NSI自优化策略。该NSI的自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、允许运行的自动优化功能、是否需要在优化前获得确认、是否反馈优化结果等。
S802、NS_SO_MMF根据整个NSI的自优化策略，决策获得每个NSSI的自优化策略，并将每个NSSI的自优化策略发送给NSS_SO_MMF。自优化策略的内容可以包括以下至少一种：NSI的标识，以用于指示该自优化策略是属于哪个NSI；NSSI的标识，以指示该自优化策略应用于哪个NSSI；触发自优化的参数阈值，NSSI的能力参数可以调整的选项。
例如，NSSI可以根据对用户移动特性的判断，自动调整对移动性的支持，如高移动性、中移动性、低移动性。能力调整的选项可是组合的，例如，在高移动性&中等时延，和中移动性&较低时延之间调整。
S803、NSS_SO_MMF给NSS_SO_F发送自优化功能配置消息，可以包括：NSSI标识，NSSI容量自动优化的触发条件，NSSI能力调整的选项。NSSI的能力修改是由NSSMF增加或者删除若干NF、或者修改相关NF的特性等。
S804、NSS_SO_F修改NSSI的能力参数，或者说NSS_SO_F执行自优化。
S805、在对NSSI执行自优化之前，NS_SO_MMF和NSS_SO_MMF从SvMF获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF或其它策略管理模块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。
S806、NSS_SO_F向NSS_SO_MMF上报自优化结果。
S807、NSS_SO_MMF向NS_SO_MMF上报自优化结果，可以包含NSI ID，NSSI ID，以及NSSI修改后的能力参数。
S808、NS_SO_MMF向SvMF或其它策略管理模块上报汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的能力参数的结果，或者说自优化结果。汇报信息可以包含NSI ID，NSSI ID，以及NSSI修改后的能力参数。
在本申请实施例中，可以通过NS_SO_MMF控制NSSI的能力自动优化功能，满足NSI对组成的NSSI的能力自动调整需求，提高了管理NSI和NSSI的灵活性，进而提高了管理NSI的效率。
在本申请实施例中，NSSMF在检测到NSSI的能力可以适当降低时，可以自动修改NSSI能力，减少网络中计算、存储等资源开销；当NSSMF检测到可以通过改变NSSI能力对业务进行更好的支持时，自动修改NSSI能力，优化整个网络切片实例对业务的支持。
图9是本申请实施例的管理网络切片实例的方法900的示意性流程图。方法900可以应用于图1至图5所示的任一种网络管理架构中。可选地，在图9中的例子中，第一网络设备可以是NSMF模块或NS_SO_MMF模块。NSMF模块可以包括NS_SO_MMF模块和NS_SO_F模块，第二网络设备可以是NSSMF模块或NSS_SO_MMF模块。第三网络设备可以是SvMF或其它策略管理模块。
如图9所示，方法900包括：
S901、第一网络设备确定修改第一网络切片实例的配置参数，所述第一网络切片实例包括至少一个网络切片子网实例。
可选地，第一网络设备可以用于管理第一网络切片实例。例如，第一网络设备可以是前述的NSMF模块，或NSMF模块包括的NS_SO_MMF模块。
可选地，第一网络切片实例可以由至少一个网络切片子网实例组成。对第一网络切片实例的配置参数进行修改，可以相应地理解为对至少一个网络切片子网实例进行修改。
可选地，所述第一网络切片实例的配置参数包括以下至少一种：所述第一网络切片实例的容量大小、能力参数、位置参数、拓扑参数、功能参数等。
S902、所述第一网络设备向至少一个第二网络设备发送第一指示信息，所述第一指示信息用于指示所述至少一个第二网络设备修改所述至少一个网络切片子网实例的配置参数。
可选地，网络切片子网实例的配置参数可以包括：所述网络切片子网实例的容量大小、所述网络切片子网实例的能力参数。
可选地，在本申请实施例中，上述修改网络切片实例的配置参数，也可以称为对网络切片实例执行自优化。上述修改网络切片子网实例的配置参数，也可以称为对网络切片子网实例执行自优化。
可选地，对NSSI容量大小的修改如NSSI所能够支持的总用户数、控制面最大连接数、最大的PDU连接数、总带宽等；对NSSI的能力参数的修改可以指在一些网络特性方面的修改，例如支持高移动性、中移动性、低移动性；支持高时延、中等时延、低时延等。在第二网络设备具体修改NSSI时，修改动作可以包括增加一个NF、删除一个NF，或者更新一个NF的特性。
S903、所述第一网络设备从所述至少一个第二网络设备接收第一回复信息，所述第一回复信息用于指示修改所述至少一个网络切片子网实例的配置参数的结果。
在本申请实施例中，第一网络设备可以自主确定修改第一网络切片实例，第一网络切 片实例包括至少一个网络切片子网实例，并向管理第一网络切片子网实例的第二网络设备发送第一指示信息，以修改网络切片子网实例，能够灵活地修改网络切片实例，从而提高了管理网络切片实例的效率。
可选地，方法900还包括：所述第一网络设备从所述至少一个第二网络设备获取所述至少一个网络切片子网实例的当前配置信息；所述第一网络设备确定修改第一网络切片实例的配置参数，包括：所述第一网络设备基于所述至少一个网络切片子网实例的当前配置信息，确定修改所述第一网络切片实例的配置参数。
可选地，第一网络设备可以向第二网络设备发送请求信息，该请求信息用于指示第二网络设备向第一网络设备发送网络切片子网实例的当前配置信息。或者，第二网络设备可以定时向第一网络设备发送网络切片子网实例的当前配置信息。
可选地，第一网络设备可以将网络切片子网实例当前配置信息与预设规则进行比较，以确定是否修改网络切片子网实例的配置参数。该预设规则可以是下文中的自优化策略。
例如，在配置参数为网络切片子网实例的情况下，第一网络设备可以向第二网络设备发送请求，请求获取NSSI的当容量大小，规定NSSMF按时上报或者在网络切片子网设立的容量达到一定阈值后上报；当NSI由多个NSSI组成，则请求多个NSSMF以获取每个NSSI的容量占用情况。
可选地，方法900还包括：所述第一网络设备从第三网络设备接收自优化策略，所述自优化策略用于指示修改网络切片实例的规则；所述第一网络设备确定修改第一网络切片实例的配置参数，包括：所述第一网络设备基于所述自优化策略，确定修改所述第一网络切片实例的配置参数。
可选地，上述第三网络设备可以是SvMF模块，也可以是运营商服务器、或者其他网络管理模块。
该自优化策略可以是运营商发送的自优化策略。自优化策略可以包括以下至少一项：是否允许对NSI自优化、允许运行的自动优化功能、自优化功能的触发条件、自优化参数的有效范围、是否需要在优化前获得确认、是否反馈优化结果等。
可选地，方法900还包括：所述第一网络设备向第三网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片实例的配置参数的结果。
可选地，上述汇报信息指示修改所述第一网络切片子网实例的配置参数的结果，也可以称为，上述汇报信息指示对所述第一网络切片子网实例执行自优化的结果。
可选地，上述汇报信息可以包括被第一网络切片实例的标识，第一网络切片子网实例的标识、修改后的配置参数等信息。例如，修改后的配置参数可以包括修改后的容量大小、修改后的能力参数等信息。
作为一个具体示例，图10示出了本申请实施例的管理网络切片实例的方法1000的示意性流程图。图10的例子给出了NSMF对NSI的容量大小进行自动优化的过程。在图10中，方法900中的第一网络设备可以是图10中的NS_SO_MMF模块，也可以是NSMF模块，其中，NSMF模块可以包括NS_SO_MMF模块和NS_SO_F模块。方法900中的第二网络设备可以是图10中的NSSMF模块。
如图10所示，该方法1000包括：
S1001、NS_SO_MMF从SvMF模块或其他策略模块接收NSI自优化策略。该NSI的 自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、允许运行的自动优化功能、自优化功能的触发条件、自优化参数的有效范围、是否需要在优化前获得确认、是否反馈优化结果等。
S1002、NS_SO_MMF向NS_SO_F发送配置消息，该配置消息可以包括：NSI标识，NSI容量自动优化的触发条件，NSI容量调整的范围。NSI的容量可以由支持的用户数、支持的连接数、总带宽等参数来衡量，容量的占用情况可用占用比例来衡量。可选地，当NS_SO_MMF和NS_SO_F设置在同一网络设备时，本步骤可以视为网络设备的内部的交互。
S1003、NS_SO_F根据NS_SO_MMF的命令配置并行启动，执行自优化算法，监控NSI容量占用情况，包括监控各个组成NSI的NSSI。
S1004、NS_SO_F向NSSMF发送请求信息，以请求获取NSSI的容量占用情况，可以规定NSSMF按时上报或者在NSSI容量大小达到一定阈值后上报；当NSI由多个NSSI组成，则NS_SO_F可以请求多个NSSMF以获取每个NSSI的容量占用情况。
S1005、NSSMF根据请求，每隔一定时段，或者当容量占用触发阈值，向NS_SO_F上报NSSI容量占用情况。
S1006、NS_SO_F根据多个NSSI的容量情况，判断当前NSI的容量占用是否超过阈值，超过阈值则触发自优化动作。
例如当前NSI支持连接数X，目前容量占用率达到90％*X，则可扩展NSI支持连接数150％*X。
S1007、在对NSSI执行自优化之前，NS_SO_MMF和NSSMF从SvMF模块或其他策略模块获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF模块或其他策略模块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。S1008、执行自优化结果，对NSI进行配置，扩展容量，包括请求NSSMF扩展NSSI容量。
可选地，扩展容量的动作包括：检查NSI所包含的所有NSSI，以及NSSI所支持的容量，判断需要对每个NSSI可以支持的容量进行扩展；例如NSSI 1支持容量为X，NSSI 2支持的容量为150％X，因为在创建的时候，每个NSSI可能根据自身的资源情况，对NSI进行了不同的支持，此时，需要请求NSSMF扩展NSSI 1的容量，即发送一个扩容请求。
S1009、NSSMF向NS_SO_F上报NSSI容量修改完成。
S1010、NS_SO_F向NS_SO_MMF上报自优化结果，可以包含NSI ID，NSSI ID，以及修改后的NSSI容量。
S1011、NS_SO_MMF向SvMF模块或其他策略模块上报汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，或者说自优化结果。汇报信息可以包含NSI ID，NSI修改后的容量大小的信息。
图11是本申请实施例的管理网络切片实例的方法1100的示意性流程图。方法1100可以应用于图1至图5所示的任一种网络管理架构中。可选地，在图11中，第一网络设备可以包括NF_SO_MMF模块或NFM模块，其中，NFM模块可以包括NF_SO_MMF模块和NF_SO_F模块。第二网络设备可以包括NS_SO_MMF模块。第三网络设备可以包括网络功能虚拟化编排(Network function virtualization orchestrator,NFVO)模块，NFVO模块可以与至少一个个NF相连，可以用于管理NF。
如图11所示，方法1100包括：
S1101，第一网络设备确定第一网络切片实例包括的第一网络功能需要优化。
S1102，第一网络设备对所述第一网络功能进行优化处理，所述优化处理包括：修改所述第一网络功能的配置参数，或，复制所述第一网络功能，并将所述第二网络功能加入到所述第一网络切片实例中，所述第一网络切片实例包括所述第二网络功能。
可选地，上述第一网络功能和第二网络功能可以共同提供服务。
可选地，在第一网络功能的计算能力发生不足的情况下，第一网络设备可以自动复制一个与第一网络功能相同的第二网络功能，并将第二网络功能加入到第一网络切片实例中，与第一网络功能共同提供服务。
上述第一网络功能的配置参数可以包括：第一网络功能的位置参数、拓扑参数、功能参数。
S1103，所述第一网络设备向第二网络设备发送汇报信息，所述汇报信息用于指示所述第一网络设备对所述第一网络功能进行优化处理的结果，所述第二网络设备用于管理所述第一网络切片实例。
可选地，上述汇报信息指示优化所述第一网络功能的配置参数的结果。
可选地，上述汇报信息可以包括第一网络切片实例的标识，第一网络功能的标识、第二网络功能的标识或对第一网络功能复制的结果信息等信息。
在本申请实施例中，所述第一网络设备可以管理第一网络功能；第二网络设备通过第一网络设备管理第一网络功能，第一网络切片实例包含第一网络功能。从而能够灵活地管理网络切片实例，提高了管理网络切片实例的效率。
可选地，方法1100还包括：所述第一网络设备从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络功能的规则；所述第一网络设备对所述第一网络功能进行优化处理，包括：所述第一网络设备基于所述自优化策略，对所述第一网络功能进行优化处理。
例如，该自优化策略可以包括NSI标识，以指示该自优化策略是属于哪个NSI；NF标识，开启NF自动复制功能的命令，触发NF自动复制的参数和阈值，例如，NF服务的用户数、业务数达到一定的阈值，则执行NF的自动复制。
可选地，方法1100还包括：所述第一网络设备从第二网络设备获取授权信息，所述授权信息用于指示允许对所述第一网络功能进行优化处理。
例如，该授权信息可以是运营商的授权信息。在执行对NF的优化处理之前，第一网络设备可以通过第二网络设备获得运营商授权，即通知运营商即将对NF进行优化，确认是否允许。
可选地，在方法1100中：所述第一网络功能的配置参数包括：所述第一网络功能的位置参数。
例如，在NSI提供服务的过程中，可能根据网络中的流量、资源状态、用户特性，修改NF的位置，例如将用户面功能(user plane function,UPF)迁移至距离用户更近的位置，或者进行迁移至网络资源充足的位置。NF位置自动修改功能适用于网络行为可以一定程度上被预测的场景，可以通过设定阈值和给出若干可选的位置的方式，较为快速地实现位置调整。
可选地，方法1100还包括：所述第一网络设备向第三网络设备发送预留请求信息，所述预留请求信息用于指示所述第三网络设备为所述第一网络功能预留网络资源，所述第三网络设备用于为网络功能分配网络资源。
可选地，上述网络资源可以是为网络功能分配的计算资源、存储资源或其他类型的资源。
在本申请实施例中，NF的网络资源主要指NF所占用的虚拟资源，因此需要与管理网络功能的网络资源分配的设备(即第三网络设备)有一定的交互。当支持NF的资源出现不足，例如监测NF的处理速度等其它性能参数，当触发阈值时，在一定范围内为NF自动增加资源。
例如，第一网络设备可以指示第三网络设备为NF预留一定资源，在一定范围内自动调整NF对应的网络资源，可以快速提升NF的性能，更好地为NSI中的业务提供服务。
作为一个具体示例，图12示出了本申请实施例的管理网络切片实例的方法1200的示意性流程图。图12的例子给出了NF_SO_MMF模块对网络功能进行复制的过程。在图12中，方法1100中的第一网络设备可以是NS_SO_MMF模块，也可以是NSMF模块，NSMF模块可以包括NS_SO_MMF模块。第二网络设备可以是NF_SO_MMF模块，也可以是NFM模块，其中，NFM模块可以包括NF_SO_MMF模块和NF_SO_F模块。
如图12所示，方法1200包括：
S1201、NS_SO_MMF从运营商接收NSI自优化策略，该NSI的自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、允许运行的自动优化功能、是否需要在优化前获得确认、是否反馈优化结果等。
S1202、NS_SO_MMF向NF_SO_MMF发送NF自优化策略，该自优化策略可以包括NSI标识，以指示该自优化策略是属于哪个NSI；NF标识；开启NF自动复制功能的命令；触发NF自动复制的参数和阈值。例如，NF服务的用户数、业务数达到一定的阈值，则执行NF的自动复制。
S1203、NF_SO_MMF配置NF_SO_F，内容包括NF标识，触发自动复制的参数和阈值。
S1204、NF_SO_F配置并执行NF的自动复制功能，当检测到参数达到阈值时，执行自动复制动作。
S1205、在对NF执行自优化之前，NS_SO_MMF和NF_SO_MMF从SvMF模块或其他策略模块获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF模块或其他策略模块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。
S1206、NF_SO_F通知NF_SO_MMF关于NF自动复制结果。
S1207、NF_SO_MMF通知NS_SO_MMF关于NF自动复制结果，可以包括NSI标识，NF标识，以及NF的复制结果。
S1208、NS_SO_MMF向SvMF模块或其他策略模块上报汇报信息，所述汇报信息用于指示修改所NF的配置参数的结果，或者说自优化结果。汇报信息可以包括NSI标识，NF标识，以及NF的复制结果。
在本申请实施例中，当NF的计算和处理能力受限时，自动复制一个相同的NF，共 同服务于NSI。通过设定触发的参数、或允许复制的动作，可以使得NF能够被快速复制并提供服务，提高整个NSI的性能。从而提高了管理网络切片实例的效率。
作为一个具体示例，图13示出了本申请实施例的管理网络切片实例的方法1300的示意性流程图。图13的例子给出了NF_SO_MMF模块对网络功能的位置参数进行优化的过程。在图13中，方法1100中的第一网络设备可以是NS_SO_MMF模块，也可以是NSMF模块，NSMF模块可以包括NS_SO_MMF模块。第二网络设备可以是NF_SO_MMF模块，也可以是NFM模块，其中，NFM模块可以包括NF_SO_MMF模块和NF_SO_F模块。
如图13所示，方法1300包括：
S1301、NS_SO_MMF从运营商接收NSI自优化策略，该NSI的自优化策略可以是运营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、允许运行的自动优化功能、是否需要在优化前获得确认、是否反馈优化结果等。
S1302、NS_SO_MMF向NF_SO_MMF发送NF自优化策略，该自优化策略可以包括NSI标识，以指示该自优化策略是属于哪个NSI；NF标识，触发自动位置修改的参数和阈值；以及可选的位置列表。例如，一种标识位置的方法为虚拟资源的IP地址，将NF迁移至对应的虚拟资源上即实现了位置的迁移。
S1303、NF_SO_MMF配置NF_SO_F，内容包括NF标识，触发自动位置修改的参数和阈值，以及可选的NF位置列表。
S1304、NF_SO_F配置并执行NF的自动位置修改功能，当检测到参数达到阈值时，修改NF位置。
S1305、在对NF执行自优化之前，NS_SO_MMF和NF_SO_MMF从SvMF模块或其他策略模块获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF模块或其他策略模块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。
S1306、NF_SO_F通知NF_SO_MMF关于NF位置自动修改结果。
S1307、NF_SO_MMF通知NS_SO_MMF关于NF位置自动修改结果，可以包括NSI标识，NF标识，以及NF的位置。
S1308、NS_SO_MMF向SvMF模块或其他策略模块上报汇报信息，所述汇报信息用于指示修改所NF的配置参数的结果，或者说自优化结果。汇报信息可以包括NSI标识，NF标识，以及NF的复制结果。
在本申请实施例中，当用户特性或者网络中的流量发送变化时，可以更改NF的位置以适应变化，提高整个NSI的性能。自动位置修改可以快速将NF迁移至若干可选位置当中的一个。从而可以提高管理网络切片实例的效率。
作为一个具体示例，图14示出了本申请实施例的管理网络切片实例的方法1400的示意性流程图。图14的例子给出了NF_SO_MMF为网络功能预留网络资源的过程。在图14中，方法1100中的第一网络设备可以是NS_SO_MMF模块，也可以是NSMF模块，NSMF模块可以包括NS_SO_MMF模块。第二网络设备可以是NF_SO_MMF模块，也可以是NFM模块，其中，NFM模块可以包括NF_SO_MMF模块和NF_SO_F模块。
如图14所示，方法1400包括：
S1401、NS_SO_MMF从运营商接收NSI自优化策略，该NSI的自优化策略可以是运 营商发送的自优化策略。NSI的自优化策略可以包括以下至少一项：例如是否允许对NSI自优化、允许运行的自动优化功能、是否需要在优化前获得确认、是否反馈优化结果等。
S1402、NS_SO_MMF向NFVO发送资源预留请求信息，以请求NFVO为NF预留网络资源。网络资源包括计算资源或存储资源，该预留的资源用于为NF做资源扩展。
S1403、NS_SO_MMF向NF_SO_MMF下发NF自优化策略，可以包括NSI标识，以指示该优化策略是属于哪个NSI；NF标识；触发网络资源修改的参数和阈值；网络资源调整的范围；以及可用的网络资源标识，例如虚拟机标识、存储标识等。
S1404、NF_SO_MMF配置NF_SO_F，配置内容包括NF的资源自优化功能，配置内容包括NF标识，触发资源修改的参数和阈值，资源自优化的范围，可用资源标识等。
S1405、NF_SO_F执行NF资源自优化功能配置和启动
S1406、在对NF执行自优化之前，NS_SO_MMF和NF_SO_MMF从SvMF模块或其他策略模块获取授权信息，该授权信息可以是运营商发送的授权信息。即可以通过SvMF模块或其他策略模块通知运营商即将对NSI的配置参数进行修改，请运营商确认是否允许。
S1407、NF_SO_F3通知NF_SO_MMF关于NF资源自动优化结果
S1408、NF_SO_MMF通知NS_SO_MMF关于NF资源自动优化的结果，可以包括NSI标识，NF标识，以及NF的资源。
S1409、NS_SO_MMF通知运营商关于NF资源自动优化的结果，可以包括NSI标识，NF标识，以及NF的资源。
在本申请实施例中，可以在预留一定资源的前提下，在一定范围内自动调整NF对应的资源，可以快速提升NF的性能，更好地为NSI中的业务提供服务。从而提高管理网络切片实例的效率。
作为一个具体示例，图15示出了管理网络切片实例的方法1500。图15的例子可以应用于图3的网络管理架构300中。在NSSI嵌套的情况下，即NSSI 1包括NSSI2的情况下，NS_SO_MMF向NSS_SO_MMF1发送有关NSSI 1的自优化策略的同时，也可以发送NSSI 2的自优化策略，或者，NSSI 2的自优化策略也可以由NSS_SO_MMF1生成。NSS_SO_MMF1对NSS_SO_F2进行配置，配置的内容请参考图6至图14中的相应内容，此处不再赘述。
如图15所示，该方法1500包括：
S1501、NS_SO_MMF向NSS_SO_MMF1发送NSS1的自优化策略，可选地，NS_SO_MMF还可以向NSS_SO_MMF1发送NSSI 2的自优化策略。
S1502、NS_SO_MMF1向NSS_SO_F2发送自动化功能配置信息。
S1503、NSS_SO_F2向NSS_SO_MMF1发送NSSI2的自优化结果反馈。
S1504、NSS_SO_MMF1向NS_SO_MMF发送NSSI 1的自优化结果，可选地，NSS_SO_MMF1还可以向NS_SO_MMF发送NSSI 2的自优化结果。
作为一个具体示例，图16示出了管理网络切片实例的方法1600。图16的例子可以应用于图4的网络管理架构400中。在NSSI嵌套的情况下，即NSSI 1包括NSSI2的情况下，NS_SO_MMF向NSS_SO_MMF1发送有关NSSI 1的自优化策略的同时，也可以发送NSSI 2的自优化策略，或者NSSI 2的自优化策略也可以由NSS_SO_MMF1生成。 NSS_SO_MMF1将NSSI 2的自优化策略发送给NSS_SO_MMF2，NSS_SO_MMF1和NSS_SO_MMF2之间的交互包括发送NSSI 2的自优化策略，获得NSSI 2自优化功能的运行情况，以及获取NSSI 2的自优化结果。配置的内容请参考图6至图14中的相应内容，此处不再赘述。
如图16所示，该方法1600包括：
S1601、NS_SO_MMF向NSS_SO_MMF1发送NSS1的自优化策略，可选地，NS_SO_MMF还可以向NSS_SO_MMF1发送NSSI 2的自优化策略。
S1602、NS_SO_MMF1向NSS_SO_MMF2发送NSSI 2的自优化策略。
S1603、NS_SO_MMF2向NSS_SO_F2发送自动化功能配置信息。
S1604、NSS_SO_F2向NSS_SO_MMF2发送NSSI2的自优化结果反馈。
S1605、NSS_SO_MMF2向NSS_SO_MMF1发送NSSI2的自优化结果反馈。
S1606、NSS_SO_MMF1向NS_SO_MMF发送NSSI 1的自优化结果，可选地，NSS_SO_MMF1还可以向NS_SO_MMF发送NSSI 2的自优化结果。
作为一个具体示例，图17示出了管理网络切片实例的方法1700。图17的例子可以应用于图5的网络管理架构500中。在NSSI嵌套的情况下，即NSSI 1包括NSSI2的情况下，NS_SO_MMF直接向NSS_SO_MMF2发送有关NSSI 2的自优化策略，NSS_SO_MMF2对NSS_SO_F2进行配置，配置的内容请参考图6至图14中的相应内容，此处不再赘述。
如图17所示，该方法1700包括：
S1701、NS_SO_MMF向NSS_SO_MMF2发送NSS2的自优化策略。
S1702、NS_SO_MMF2向NSS_SO_F2发送自动化功能配置信息。
S1703、NSS_SO_F2向NSS_SO_MMF2发送NSSI2的自优化结果反馈。
S1704、NSS_SO_MMF2向NSS_SO_MMF1发送NSSI2的自优化结果反馈。
S1706、NSS_SO_MMF2向NS_SO_MMF发送NSSI 2的自优化结果。
上文结合图1至图17详细描述了本发明实施例的管理网络切片的方法和网络管理架构，下文将结合图18至图29详细描述本发明实施例的网络设备。
图18是本发明实施例的网络设备1800的示意性框图。应理解，网络设备1800能够执行图6至图8的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1800包括：处理单元1801和通信单元1802，
所述处理单元1801用于确定第一网络切片子网实例的配置参数需要修改，所述第一网络设备用于管理所述第一网络切片子网实例；以及修改所述第一网络切片子网实例的配置参数；以及通过所述通信单元1802向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
图19是本发明实施例的网络设备1900的示意性框图。应理解，网络设备1900能够执行图6至图8的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备1900包括：处理单元1901和通信单元1902，
所述处理单元1901用于通过所述通信单元1902从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网 络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
图20是本发明实施例的网络设备2000的示意性框图。应理解，网络设备2000能够执行图9或图10的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2000包括：处理单元2001和通信单元2002，
所述处理单元2001用于确定修改第一网络切片实例的配置参数，所述第一网络切片实例包括至少一个网络切片子网实例；以及通过通信单元2002向至少一个第二网络设备发送第一指示信息，所述第一指示信息用于指示所述至少一个第二网络设备修改所述至少一个网络切片子网实例的配置参数；以及通过通信单元2002从所述至少一个第二网络设备接收第一回复信息，所述第一回复信息用于指示修改所述至少一个网络切片子网实例的配置参数的结果。
图21是本发明实施例的网络设备2100的示意性框图。应理解，网络设备2100能够执行图9或图10的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2100包括：处理单元2101和通信单元2102，
处理单元2101用于通过通信单元2102接收第一网络设备发送的第一指示信息，所述第一指示信息用于指示所述第二网络设备修改第一网络切片子网实例，所述第一网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例；以及通过所述通信单元2102向所述第一网络设备发送第一回复信息，所述第一回复信息用于指示修改所述第一网络切片子网实例的配置参数的结果。
图22是本发明实施例的网络设备2200的示意性框图。应理解，网络设备2200能够执行图11至图14的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2200包括：处理单元2201和通信单元2202，
所述处理单元2201用于确定第一网络切片实例包括的第一网络功能需要优化；以及对所述第一网络功能进行优化处理，所述优化处理包括：修改所述第一网络功能的配置参数，或，复制所述第一网络功能，并将所述第二网络功能加入到所述第一网络切片实例中，所述第一网络切片实例包括所述第二网络功能；以及通过所述通信单元2202向第二网络设备发送汇报信息，所述汇报信息用于指示所述第一网络设备对所述第一网络功能进行优化处理的结果，所述第二网络设备用于管理所述第一网络切片实例。
图23是本发明实施例的网络设备2300的示意性框图。应理解，网络设备2300能够执行图11至图14的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2300包括：处理单元2301和通信单元2302，
所述处理单元2301用于通过通信单元2302从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
图24是本发明实施例的网络设备2400的示意性框图。应理解，网络设备2400能够执行图6至图8的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2400包括：
存储器2410，用于存储程序；
收发器2420，用于和其他设备进行通信；
处理器2430，用于执行存储器2410中的程序，当所述程序被执行时，所述处理器2430用于确定第一网络切片子网实例的配置参数需要修改，所述第一网络设备用于管理所述第一网络切片子网实例；以及修改所述第一网络切片子网实例的配置参数；以及通过所述收发器2420向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
图25是本发明实施例的网络设备2500的示意性框图。应理解，网络设备2500能够执行图6至图8的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2500包括：
存储器2510，用于存储程序；
收发器2520，用于和其他设备进行通信；
处理器2530，用于执行存储器2510中的程序，当所述程序被执行时，所述处理器2530用于通过收发器2520从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
图26是本发明实施例的网络设备2600的示意性框图。应理解，网络设备2600能够执行图9或图10的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2600包括：
存储器2610，用于存储程序；
收发器2620，用于和其他设备进行通信；
处理器2630，用于执行存储器2410中的程序，当所述程序被执行时，所述处理器2630用于确定修改第一网络切片实例的配置参数，所述第一网络切片实例包括至少一个网络切片子网实例；以及通过收发器2620向至少一个第二网络设备发送第一指示信息，所述第一指示信息用于指示所述至少一个第二网络设备修改所述至少一个网络切片子网实例的配置参数；以及通过收发器2620从所述至少一个第二网络设备接收第一回复信息，所述第一回复信息用于指示修改所述至少一个网络切片子网实例的配置参数的结果。
图27是本发明实施例的网络设备2700的示意性框图。应理解，网络设备2700能够执行图9或图10的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2700包括：
存储器2710，用于存储程序；
收发器2720，用于和其他设备进行通信；
处理器2730，用于执行存储器2710中的程序，当所述程序被执行时，所述处理器2730用于通过收发器2720接收第一网络设备发送的第一指示信息，所述第一指示信息用于指示所述第二网络设备修改第一网络切片子网实例，所述第一网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例；以及通过所述收发器2720向所述第一网络设备发送第一回复信息，所述第一回复信息用于指示修改所述第一网络切片子网实例的配置参数的结果。
图28是本发明实施例的网络设备2800的示意性框图。应理解，网络设备2800能够执行图11至图14的方法中由第一网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2800包括：
存储器2810，用于存储程序；
收发器2820，用于和其他设备进行通信；
处理器2830，用于执行存储器2810中的程序，当所述程序被执行时，所述处理器2830用于确定第一网络切片实例包括的第一网络功能需要优化；以及对所述第一网络功能进行优化处理，所述优化处理包括：修改所述第一网络功能的配置参数，或，复制所述第一网络功能，并将所述第二网络功能加入到所述第一网络切片实例中，所述第一网络切片实例包括所述第二网络功能；以及通过收发器2820向第二网络设备发送汇报信息，所述汇报信息用于指示所述第一网络设备对所述第一网络功能进行优化处理的结果，所述第二网络设备用于管理所述第一网络切片实例。
图29是本发明实施例的网络设备2900的示意性框图。应理解，网络设备2900能够执行图11至图14的方法中由第二网络设备执行的各个步骤，为了避免重复，此处不再详述。网络设备2900包括：
存储器2910，用于存储程序；
收发器2920，用于和其他设备进行通信；
处理器2930，用于执行存储器2910中的程序，当所述程序被执行时，所述处理器2930用于通过收发器2920从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各 个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory,ROM))、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利求的保护范围为准。

Claims (16)

  1. 一种管理网络切片实例的方法，其特征在于，包括：
    第一网络设备确定第一网络切片子网实例的配置参数需要修改，所述第一网络设备用于管理所述第一网络切片子网实例；
    所述第一网络设备修改所述第一网络切片子网实例的配置参数；
    所述第一网络设备向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：所述第一网络设备从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则；
    所述第一网络设备修改所述第一网络切片子网实例的配置参数，包括：
    所述第一网络设备基于所述自优化策略，修改所述第一网络切片子网实例的配置参数。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：所述第一网络设备从所述第二网络设备接收授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
  5. 一种管理网络切片实例的方法，其特征在于，包括：
    第二网络设备从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：所述第二网络设备向所述第一网络设发送自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则。
  7. 如权利要求5或6所述的方法，其特征在于，所述方法还包括：所述第二网络设备向所述第一网络设备发送授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
  8. 如权利要求5至7中任一项所述的方法，其特征在于，所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
  9. 一种网络设备，其特征在于，所述网络设备为第一网络设备，包括：处理单元和通信单元，
    所述处理单元用于确定第一网络切片子网实例的配置参数需要修改，所述第一网络设 备用于管理所述第一网络切片子网实例；以及修改所述第一网络切片子网实例的配置参数；以及通过所述通信单元向第二网络设备发送汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
  10. 如权利要求9所述的网络设备，其特征在于，所述处理单元还用于通过所述通信单元从所述第二网络设备接收自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则；在修改所述第一网络切片子网实例的配置参数方面，所述处理单元具体用于基于所述自优化策略，修改所述第一网络切片子网实例的配置参数。
  11. 如权利要求9或10所述的网络设备，其特征在于，所述处理单元还用于通过所述通信单元从所述第二网络设备接收授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
  12. 如权利要求9至11中任一项所述的网络设备，其特征在于，所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
  13. 一种网络设备，其特征在于，所述网络设备为第二网络设备，包括：处理单元和通信单元，
    所述处理单元用于通过所述通信单元从第一网络设备接收汇报信息，所述汇报信息用于指示修改所述第一网络切片子网实例的配置参数的结果，其中，所述第一网络设备用于管理所述第一网络切片子网实例，所述第二网络设备用于管理第一网络切片实例，所述第一网络切片实例包括所述第一网络切片子网实例。
  14. 如权利要求13所述的网络设备，其特征在于，所述处理单元还用于通过所述通信单元向所述第一网络设发送自优化策略，所述自优化策略用于指示修改网络切片子网实例的规则。
  15. 如权利要求13或14所述的网络设备，其特征在于，所述处理单元还用于通过所述通信单元向所述第一网络设备发送授权信息，所述授权信息用于指示允许修改所述第一网络切片子网实例的配置参数。
  16. 如权利要求13至15中任一项所述的网络设备，其特征在于，所述第一网络切片子网实例的配置参数包括：所述第一网络切片子网实例的容量大小、所述第一网络切片子网实例的能力参数。
PCT/CN2018/078793 2017-03-20 2018-03-13 管理网络切片实例的方法、装置和系统 WO2018171465A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18771388.8A EP3588852B1 (en) 2017-03-20 2018-03-13 Method, apparatus and system for managing network slice instance
US16/574,211 US10993127B2 (en) 2017-03-20 2019-09-18 Network slice instance management method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710167282.8A CN108632063B (zh) 2017-03-20 2017-03-20 管理网络切片实例的方法、装置和系统
CN201710167282.8 2017-03-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/574,211 Continuation US10993127B2 (en) 2017-03-20 2019-09-18 Network slice instance management method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2018171465A1 true WO2018171465A1 (zh) 2018-09-27

Family

ID=63586297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078793 WO2018171465A1 (zh) 2017-03-20 2018-03-13 管理网络切片实例的方法、装置和系统

Country Status (4)

Country Link
US (1) US10993127B2 (zh)
EP (1) EP3588852B1 (zh)
CN (1) CN108632063B (zh)
WO (1) WO2018171465A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109560952B (zh) * 2017-09-27 2021-04-09 华为技术有限公司 一种网络切片管理方法及设备
JP6973300B2 (ja) * 2018-06-04 2021-11-24 日本電信電話株式会社 サービスチェイン設計装置、サービスチェイン設計方法、および、サービスチェイン設計プログラム
US10986010B2 (en) 2018-08-09 2021-04-20 At&T Intellectual Property I, L.P. Mobility network slice selection
US10667179B1 (en) * 2019-03-13 2020-05-26 Verizon Patent And Licensing Inc. Multiple-slice application delivery based on network slice associations
CN112860496A (zh) * 2019-11-27 2021-05-28 华为技术有限公司 故障修复操作推荐方法、装置及存储介质
CN112968788A (zh) * 2019-12-13 2021-06-15 中兴通讯股份有限公司 网络切片容量设置方法、控制方法、装置、设备及介质
CN111343027B (zh) * 2020-03-11 2022-08-26 中国电子科技集团公司第五十四研究所 一种基于遗传算法的网络切片部署方法和装置
WO2021223103A1 (en) * 2020-05-06 2021-11-11 Nokia Shanghai Bell Co., Ltd. Method and apparatus for preventing network attacks in a network slice
CN111935737B (zh) * 2020-07-16 2022-03-01 北京思特奇信息技术股份有限公司 实现网络切片生命周期管理的网络切片管理系统和方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832A (zh) * 2015-07-07 2017-01-18 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6493549B1 (en) * 2000-02-10 2002-12-10 Lucent Technologies Inc. Over the air parameter administration for mobile telecommunications stations
US10644955B2 (en) * 2015-08-21 2020-05-05 Huawei Technologies Co., Ltd. Method and apparatus for network slicing
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
US11095526B2 (en) * 2016-11-14 2021-08-17 Huawei Technologies Co., Ltd. System and method for accelerated provision of network services
CN108632058B (zh) * 2017-03-18 2020-10-09 华为技术有限公司 网络切片的管理方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832A (zh) * 2015-07-07 2017-01-18 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Study on Management and Orchestration of Network Slicing for Next Generation Network", 3GPP TR 28. 801, no. V1.0.0, 2 March 2017 (2017-03-02), XP051290419 *
See also references of EP3588852A4

Also Published As

Publication number Publication date
US20200015102A1 (en) 2020-01-09
EP3588852B1 (en) 2022-03-02
EP3588852A1 (en) 2020-01-01
CN108632063B (zh) 2021-01-05
EP3588852A4 (en) 2020-03-04
US10993127B2 (en) 2021-04-27
CN108632063A (zh) 2018-10-09

Similar Documents

Publication Publication Date Title
WO2018171465A1 (zh) 管理网络切片实例的方法、装置和系统
EP3648401B1 (en) Method, device, and computer readable storage medium for managing network slice
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
JP6408602B2 (ja) Ｎｆｖシステムにおけるサービス実装のための方法および通信ユニット
CN113364850B (zh) 软件定义云边协同网络能耗优化方法和系统
KR102045865B1 (ko) 모바일 단말기 및 그 자원 관리 방법
WO2017214932A1 (zh) 一种网络切片的资源管理方法和装置
JP6636142B2 (ja) スケールアウト関連付けの方法および装置、ならびにシステム
KR102172169B1 (ko) 분산형 클라우드 기반 어플리케이션 실행 시스템, 이에 적용되는 장치 및 장치의 동작 방법
EP3525396B1 (en) Method and device for managing network slice instance
WO2018082491A1 (zh) 扩展网络切片实例的方法、网络设备和网络构架
WO2016054922A1 (zh) 决策协调方法、执行装置和决策协调器
US20220413937A1 (en) Node management method, device and apparatus, storage medium, and system
CN108738027B (zh) 一种网络处理方法、资源管理系统及网络设备
CN114301914B (zh) 一种云边协同方法、装置及存储介质
EP3280102B1 (en) Optical path allocation method and apparatus
CN114697197A (zh) 边缘计算设备和方法
WO2018127068A1 (zh) 网络管理方法和装置
CN107005468B (zh) 一种待上载的nsd的确定方法及装置
US11716382B2 (en) System and method for replication of storage presentation in application orchestration
Babou et al. HEC-NerveNet: A Resilient Edge Cloud Architecture for Beyond 5G Networks
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置
US20190268967A1 (en) Converged Controller Selection Method, Device, and Converged Controller Selection System
KR20200077943A (ko) 동적 네트워크 확장 방법, 장치 및 시스템

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: 18771388

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018771388

Country of ref document: EP

Effective date: 20190926