WO2018082545A1

WO2018082545A1 - Method, apparatus and system for shrinking network slice instance

Info

Publication number: WO2018082545A1
Application number: PCT/CN2017/108612
Authority: WO
Inventors: 陆伟; 杨水根; 孙文琦
Original assignee: 华为技术有限公司
Priority date: 2016-11-03
Filing date: 2017-10-31
Publication date: 2018-05-11
Also published as: CN108024256A; CN108024256B

Abstract

Disclosed is a method for shrinking a network slice instance (NSI). The method comprises: a first network slice manager and orchestrator (NSM&O) sends a network function shrinkage request message to a management device, wherein the first NSM&O is used for managing and orchestrating NSIs, and the management device is used for managing a network function to be shrunk of a target NSI; receive a shrinkage feedback message from the management device; update information of the target NSI stored in a memory according to the shrinkage feedback message. According to the method for shrinking an NSI provided by the present application, physical and virtual network functions/resources can be simultaneously orchestrated and managed to implement network slicing, so that network deployment time is shortened, and deployment costs are reduced. Moreover, during shrinkage of the NSI, by differently processing a general network function and a dedicated network function, impact on services being provided by other slice instances is avoided during the shrinkage of the general network function.

Description

Method, device and system for shrinking network slice instance

The present application claims priority to Chinese Patent Application No. 201610974261.2, filed on November 3, 2016, the entire disclosure of which is incorporated herein by reference. Combined in this application.

Technical field

The present application relates to the field of communications, and in particular, to a method, apparatus, and system for shrinking a network slice instance.

Background technique

With the rapid development of mobile communications, digital transformation involves almost all traditional industries. However, the traditional cellular network architecture can only provide a unified network service, and it is difficult to meet the extremely different communication requirements brought about by the digital transformation wave, including functional differences and performance differences. In the next generation of mobile networks, the network will be abstracted as a "network slice."

Although network function virtualization is a key enabling technology that reduces the complexity and cost of network slicing, physical network elements and virtualized network elements will coexist for a long time and flexibly form a network slice for the purpose of reducing deployment costs and recovering investment. . Therefore, in order to provide differentiated communication requirements quickly and flexibly, equipment vendors need an automated slicing operation and maintenance system that can simultaneously manage and orchestrate physical network functions (PNF) and virtualized network functions (VNF). It enables the management of physical and virtual network functions/resources to implement network slicing.

Currently, whether it is the network function virtualization orchestrator (NFVO) in the management and orchestration (MANO) architecture or the network management in the 3rd generation partnership project (3GPP) architecture Network manager (NM) can not organize physical and virtual network functions/resources at the same time to implement network slicing.

Summary of the invention

In view of this, the present application provides a method, apparatus, and system for shrinking a network slice instance (NSI), which manages NSI through a newly designed network architecture, and can simultaneously perform physical and virtual network functions/resources. Performing orchestration management to achieve network slicing shortens network deployment time and saves deployment costs. And when shrinking NSI, by treating the common network function and the dedicated network function differently, it is avoided to affect the services that other slice instances are providing when shrinking the general network function.

In a first aspect, a method for shrinking NSI is provided, the method comprising: a first network slice manager and orchestrator (NSM&O) sending a network function shrink request message to a management device, where the first NSM&O is used The NSI is managed and arranged, the management device is configured to manage the network function of the target NSI to be contracted, and the network function shrink request message is used to request the management device to perform shrink processing on the network function; the first NSM&O receives the shrink feedback message from the management device. , the shrink feedback message is used to manage the device feedback network function The result of the shrinking process; the first NSM&O updates the information of the target NSI stored in the memory based on the shrink feedback message.

Therefore, the method for shrinking the NSI provided by the present application manages the NSI through the newly designed network architecture, and can simultaneously manage the physical and virtual network functions/resources to implement network slicing, shortening the network deployment time, and saving the deployment cost. . And when shrinking NSI, by treating the common network function and the dedicated network function differently, it is avoided to affect the services that other slice instances are providing when shrinking the general network function.

Optionally, the method specifically includes: when the first NSM&O is a dedicated network function of the target NSI, sending a network function shrink request message to the management device; or when the first NSM&O is the target NSI and the network function When the shared network function of the NSI is associated, and the shrink network function does not affect the service of the associated NSI, the network function shrink request message is sent to the management device, where the associated NSI is an NSI that uses the network function together with the target NSI.

The method for shrinking NSI provided by the present application adopts different pre-processing methods for the shared network function and the dedicated network function before sending the network function shrink request message, so that the shrink sharing network function is not provided for other NSIs sharing the function. The service has a negative impact. In addition, if there is a shared network function between multiple NSIs, it is only necessary to shrink the shared network function in one of the NSIs, that is, shrinking multiple NSIs at the same time, which reduces the maintenance time and cost of the system.

Optionally, before the first NSM&O sends the network function shrink request message to the management device, the method further includes: acquiring, by the first NSM&O, an NSI shrink request message, where the NSI shrink request message includes identifier information of the target NSI, where the NSI shrinks The request message is used to request the first NSM&O to perform a shrinking process on the target NSI; the first NSM&O determines a network slice descriptor (NSLD) of the target NSI according to the identification information; the first NSM&O determines the network function according to the NSLD.

The method for shrinking NSI provided by the present application, the first NSM&O can flexibly determine the shrinking process of the target NSI according to actual conditions. When the equipment provider or the authorized network fragment instance third-party tenant finds that the existing NSI has excessive performance, it shrinks the NSI as needed, or automatically shrinks when the performance of the NSI is excessive according to the policy, which reduces the operation and maintenance cost.

Optionally, after the first NSM&O acquires the NSI shrink request message, and before the first NSM&O sends the network function shrink request message to the management device, the method further includes: the first NSM&O sends a notification message to the NM, where the notification message is used for the notification. The NM first NSM&O needs to perform shrink processing on the network function; the first NSM&O receives an acknowledgment message from the NM, the acknowledgment message is used to instruct the first NSM&O to perform shrink processing on the network function.

In the present application, the network management architecture includes an NM, and the first NSM&O sends a notification message to the NM before the shrinking process of the shrinking network function, notifying the NM that the first NSM&O needs to perform shrink processing on the network function, and sends an acknowledgement message according to the NM. It is determined that the network function is shrunk, thereby avoiding conflicts between NM and NSM&O simultaneously configuring network functions.

Optionally, after the first NSM&O receives the shrink feedback message from the management device, and before the first NSM&O updates the information of the target NSI stored in the memory according to the feedback message, the method further includes: the first NSM&O to the virtualized infrastructure The virtualized infrastructure manager (VIM) sends a resource allocation request message, where the resource allocation request message is used to request the VIM to release the idle resource after the network function shrinks; the first NSM&O receives the resource allocation feedback message from the VIM; the first NSM&O according to the Shrinking the feedback message to update the information of the target NSI stored in the memory includes: the first NSM&O updating the information of the target NSI stored in the memory according to the shrink feedback message and the resource allocation feedback message.

According to the method for shrinking NSI provided by the present application, the first NSM&O sends a resource allocation request to the VIM. The VIM is requested to release the idle resources after the VNF shrinks, thereby improving resource utilization.

Optionally, when the network function is a shared network function, the method further includes: the first NSM&O updating the information about the associated NSI stored in the memory according to the shrink feedback message, where the associated NSI is used in conjunction with the target NSI to share the network function. NSI. This keeps the information in the system synchronized.

Optionally, the first NSM&O acquires the NSI shrink request message, where the first NSM&O obtains the NSI shrink request message sent by the second NSM&O.

The method for shrinking the NSI provided by the present application can determine the shrinkage of the target NSI through the hierarchical NSM&O, and can flexibly manage the network of the multi-domain and multi-device vendors.

In a second aspect, a method for shrinking an NSI is provided, the method comprising: a management device receiving a network function shrink request message from an NSM&O, wherein the management device is configured to manage a network function of a target NSI to be contracted, the NSM&O being used for The NSI performs management and scheduling; the management device shrinks the network function according to the network function shrink request message; the management device sends a shrink feedback message to the NSM&O, and the shrink feedback message is used to feed back the result of the shrinking process of the network function.

The method for shrinking NSI provided by the present application manages the NSI through the newly designed network architecture, and can perform physical layering and management of physical and virtual network functions/resources at the same time to realize network slicing, shortening network deployment time and saving deployment cost. And when shrinking NSI, by treating the common network function and the dedicated network function differently, it is avoided to affect the services that other slice instances are providing when shrinking the general network function.

Optionally, the management device includes a virtualized network function manager (VNFM), the network function includes a first VNF instance, and the management device performs shrinking processing on the network function according to the network function shrink request message, including: VNFM Performing a shrink feasibility check on the first VNF instance according to the network function shrink request message; the VNFM shrinks the first VNF instance when the shrink feasibility check is acceptable.

The method for shrinking NSI provided by the present application checks the contraction feasibility of the VNF instance to be shrunk by VNFM, thereby ensuring that the shrinkage treatment of the VNF instance can be performed correctly.

Optionally, the management device includes an element manager (EM), the network function includes a second VNF instance, where the second VNF instance is an NM generated VNF instance, when a network function request message is used for the request When the service of the second VNF instance is stopped, the shrink feedback message is used to feed back the service of the second VNF instance has been stopped.

The method for shrinking NSI provided by the present application determines whether the VNF instance to be shrunk can be shrunk by NSM&O checking the properties of the VNF instance to be shrunk, thereby avoiding an error when NSM&O shrinks the NNF generated VNF instance.

In a third aspect, the present application provides an NSM&O, which can implement the functions performed by the NSM&O in the method related to the foregoing first aspect, and the functions can be implemented by using hardware or by executing corresponding software by hardware. The hardware or software includes one or more corresponding units or modules of the above functions.

In one possible design, the structure of the NSM&O includes a processor and a communication interface configured to support the NSM&O to perform the corresponding functions in the above methods. The communication interface is used to support communication between the NSM&O and other network elements. The NSM&O can also include a memory for coupling with the processor that holds the necessary program instructions and data for the NSM&O.

In a fourth aspect, the application provides a management device, which can implement the functions performed by the management device in the method related to the second aspect, and the functions can be implemented by using hardware or by executing corresponding software through hardware. . The hardware or software includes one or more corresponding units or modules of the above functions.

In one possible design, the management device includes a processor and a communication interface configured to support the management device to perform corresponding functions in the above methods. The communication interface is used to support communication between the management device and other network elements. The management device can also include a memory for coupling with the processor that holds the program instructions and data necessary for the management device.

In one possible design, the above management device may be EM, VNFM or NFVO.

In a fifth aspect, the present application provides a communication system including the NSM&O and management device described in the above aspects.

In a sixth aspect, the present application provides a computer storage medium for storing computer software instructions for use in the above NSM&O, comprising a program designed to perform the first aspect described above.

In a seventh aspect, the present application provides a computer storage medium for storing computer software instructions for use in the above management apparatus, comprising a program designed to perform the second aspect described above.

In an eighth aspect, the present application provides a computer program product, comprising: computer program code, when the computer program code is executed by a communication unit and a processing unit of NSM&O, causing NSM&O to perform the first aspect Methods.

In a ninth aspect, the present application provides a computer program product, comprising: computer program code, when the computer program code is run by a communication unit and a processing unit of a management device, causing the management device to perform the second aspect The method involved.

In a tenth aspect, the present application provides a chip in which instructions are stored that, when run on NSM&O, cause the chip to control NSM&O to perform the method of the first aspect above.

In an eleventh aspect, the present application provides a chip in which instructions are stored, which, when run on a management device, cause the chip control management device to perform the method of the second aspect.

DRAWINGS

1 is a schematic diagram of a network management architecture in the prior art;

2 is a schematic structural diagram of an NSM&O provided by the present application;

3 is a schematic diagram of a network management architecture to which the present application applies;

4 is a schematic diagram of another network management architecture to which the present application applies;

FIG. 5 is a schematic diagram of still another network management architecture applicable to the present application; FIG.

6 is a schematic diagram of still another network management architecture applicable to the present application;

FIG. 7 is a schematic flowchart of a method for shrinking NSI provided by the present application; FIG.

FIG. 8 is a schematic structural diagram of a NSM&O having a hierarchical structure provided by the present application; FIG.

FIG. 9 is a schematic flowchart of a method for shrinking NSI of a hierarchical NSM&O provided by the present application; FIG.

FIG. 10 is a schematic flowchart of another method for shrinking NSI provided by the present application; FIG.

FIG. 11 is a schematic flowchart of still another method for shrinking NSI provided by the present application;

FIG. 12 is a schematic flowchart of still another method for shrinking NSI provided by the present application; FIG.

FIG. 13 is a schematic flowchart of still another method for shrinking NSI provided by the present application;

FIG. 14 is a schematic flowchart of still another method for shrinking NSI provided by the present application; FIG.

15 is a schematic structural diagram of a possible NSM&O provided by the present application;

16 is a schematic structural diagram of another possible NSM&O provided by the present application;

17 is a schematic structural diagram of a possible management device provided by the present application;

FIG. 18 is a schematic structural diagram of another possible management device provided by the present application.

detailed description

This application relates to network slicing techniques. The network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types. For example, in the fifth generation ^(the 5 ^th generation, 5G) mobile communication network, the network is an on-demand networking slice manner, the device can be adjusted to bring supplier to changing user needs and to quickly meet new applications New services for demand.

The network slicing technology abstracts the 5G network physical infrastructure resources into a plurality of independent parallel NSIs according to the scene requirements. Each NSI performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model. An NSI can be viewed as an instantiated 5G network. Such a network structure allows device vendors to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.

In the network slicing technology, when the equipment provider or tenant finds that the performance of the NSI is excessive, the NSI needs to be contracted. Shrinking NSI involves configuring the PNF, releasing VNF calculations, storage, network and other resources, and terminating VNF.

In order to make the objects, technical solutions and advantages of the present application more clear, the technical solutions in the present application will be described below in conjunction with the drawings in the present application.

The network architecture and the service scenario described in this application are for the purpose of more clearly explaining the technical solutions of the present application, and do not constitute a limitation of the technical solutions provided by the present application. Those skilled in the art may know that with the evolution of the network architecture and new business scenarios, The technical solution provided by the present application is equally applicable to similar technical problems.

It should be noted that the terms "network management architecture", "network system", "system" and the like in this document can be replaced with each other. In addition, for convenience of description, the terms "VNF instance" and "VNF" may also be substituted for each other, and the specific meaning thereof is determined by the meaning of the statement in which the term is placed, and is not to be construed as limiting the present application. For ease of understanding, some of the terms that appear in this article are introduced.

Network slicing: is a concept that describes a system behavior, which is implemented by NSI.

NSLD: Used to describe the constituent elements of a network slice (for example, network functions, resource requirements, etc.) and their relationships (for example: network function organization structure, network function/resource configuration, and workflow between network functions, etc.). It should be understood that NSLD is only a concept defined for describing the above features of the network slice, and should not be construed as limiting the scope of application of the present application. Other concepts for describing the above features of the network slice are applicable to the present application.

NSI: An instance created for the function of network slicing can be created according to NSLD or created according to other methods. The NSI can meet different communication requirements, for example, enhanced mobile broadband (eMBB) network slicing, massive Machine type communication (mMTC) network slicing and ultra-reliable and low latency communication (URLLC) network slicing.

Network function: It is a processing function in the network, which defines the functional behavior and interface. The network function can be implemented as a dedicated hardware or a software running on a dedicated hardware, or on a general hardware platform. The implementation of virtual functions. Therefore, from the perspective of implementation, network functions can be divided into PNF and VNF. And from From the perspective of use, the network function can be divided into a dedicated network function and a shared network function. Specifically, for multiple network slice instances, different network functions can be used independently. This network function is called a dedicated network function, and can also be used. Sharing the same network function, this network function is called shared network function.

In order to facilitate the understanding of the present application, the network management architecture in the prior art is first introduced. FIG. 1 illustrates a network management architecture 100 in the prior art. As an example, the network management architecture 100 of FIG. 1 may be a 3GPP public land mobile network (PLMN) network management architecture that incorporates the MANO architecture. Specifically, the network management architecture 100 includes both a module for managing the PNF and a module for managing the VNF. The modules in the network management architecture 100 are described in turn below.

PNF: is a physical device that provides fixed network functionality. For example, the PNF may be a network element (NE) in a conventional 3GPP network management architecture, that is, a physical network element. The NE may be a base station, a mobility management entity (MME), or a serving gateway (SGW).

VNF: Can be the smallest virtual unit that can be monitored and managed in the network management architecture. There is a communication interface between the VNF and the network function virtualized infrastructure (NFVI) described below. The VNF module can create virtual network functions and perform some parameter configuration on the basis of NFVI to implement a certain network function.

NE: The smallest physical unit that can be monitored and managed in the network management architecture. For example, the NE may be a base station or an MME, and the NE may also be referred to as a PNF module.

EM: Network module for managing network elements. EM can be used to manage both PNF and VNF.

Domain manager (DM): A management system module that is one level larger than the management scope of EM. The DM can manage one or more EMs, for example, the DM can be a vendor's management system.

It should be noted that EM and DM are different in definition. EM directly manages the same type of network equipment. For example, EM manages a series of base stations. DM manages a network device belonging to a vendor and provides domain management. Functional, DM is more manageable than EM. Typically, EM devices are used to perform configuration of network functions. However, the possibility that the DM performs the process performed by the EM is not excluded in this application.

NM: A network-level management module that provides network management functions and management equipment exchanges. For example, NM can be responsible for the distribution, configuration, control, and monitoring of network resources, and NM is supported by EM or DM.

NFVI: Provides hardware and virtual resources for the entire system, consisting of hardware resources (including computing, networking, and storage), virtualization layers (virtualizing hardware resources into resource pools), and virtual resources (also divided into computing, networking, and storage). Part) composition. From a VNF perspective, the virtualization layer and hardware resources appear to be an entity that provides the required virtual resources.

Network functions virtualization-management and orchestration (NFV-MANO) system module: It has an interface with NFVI, VNF, EM and NM for managing virtual network functions at the network level, including The following three modules:

NFVO: Used to implement network service, VNF lifecycle management, and optimize network resources from the perspective of NFVI globally.

VNFM: Implements lifecycle management of VNF instances, including initialization of VNF instances, expansion or shrinkage of VNF instances, and termination of VNF instances.

VIM: An interface exists between NFVI and VNF. It is used for management, monitoring, and fault reporting of infrastructure layer hardware resources and virtualized resources. It provides virtualized resource pools for upper-layer applications.

It can be seen from the above description of the network management architecture 100 in the prior art that the network management architecture in the prior art can manage physical network functions and virtual network functions. However, it is not capable of managing and orchestrating network slices. Therefore, the network management architecture in the prior art cannot meet the requirements of the network slicing technology application in the future communication system, that is, the network slicing cannot be managed and arranged flexibly. In the prior art, the physical network element and the virtualized network element will coexist for a long time and flexibly constitute a network slice for the purpose of reducing deployment cost and the like. Therefore, there is a need for a network management system that enables physical network functions or network resources as well as virtual network functions or network resources to be arranged and managed to implement network slicing applications.

The central idea of the present application is to introduce NSM&O in the network management architecture 100, and manage the NSI shrinking process through NSM&O to realize the automatic shrinking of the NSI and improve the efficiency of managing the NSI. It should be understood that NSM&O is merely a concept defined to describe "a device that implements the organization and management of physical network functions or network resources and virtual network functions or network resources", and should not be construed as being applicable to the scope of application of the present application. Limitations, other concepts for describing "a device that implements the organization or management of physical network functions or network resources and virtual network functions or network resources" are applicable to the present application.

The network management architecture of the present application is described below. This application introduces NSM&O on the basis of the existing network management architecture 100. The structure diagram of NSM&O is shown in Figure 2. Its main functions include:

Service conversion: receiving service description information sent by the sender device through an interface (for example, an application programming interface (API)), and converting the service description information into a requirement for the network.

Network Slice Design: Describes the composition of the network slice based on the results of the service transformation. For example, it can be a design NSLD.

Network Slice Management Strategy: Design a management strategy for network slices. For example, on-boarding, instantiation, shrinking and scaling, update, termination, and deletion.

Network Slice Orchestration: Used to specifically determine the network functions and network resources used by the network slice instance.

Monitoring: Status parameters used to detect and report network slice instances. For example, you can monitor key performance indicators (KPI) parameters for network slicing instances.

The sender device of the above-mentioned sender device is a device that sends a request to NSM&O. For example, the sender device may be a device vendor, a third party client, an application involved in the communication service, or any other physical device that may send a request to the NSM&O.

Optionally, the network management architecture in the application may further include a storage device, where the storage device may be used to record information of the generated network slice instance.

Figures 3 through 6 illustrate four network management architectures suitable for use in the present application. NSM&O is included in all four network management architectures. For convenience of distinction, the network management architectures of FIGS. 3 through 6 are hereinafter referred to as network management architecture 200, network management architecture 300, network management architecture 400, and network management architecture 500, respectively.

FIG. 3 illustrates a network management architecture 200 to which the present application is applied. As shown in FIG. 3, the network management architecture 200 is a network management architecture that is enhanced and modified based on the network management architecture 100. The network management architecture 200 does not include the NM, but the NM&O performs the function of the NM in the network management architecture 100. In other words, in addition to the functions shown in Figure 2, NSM&O can also include all the functions of the NM. NSM&O can interact with the EM through a communication interface to implement management of network functions corresponding to the NSI. Among them, the management of network functions includes the management of PNF and VNF. NSM&O can also receive VNF status information from NFVO through the communication interface, as well as The communication interface sends an instruction to the NFVO.

For the network management architecture 200, NSM&O can directly manage the PNF, and can use NFVO to implement resource scheduling management of the NFVI and implement VNF generation.

FIG. 4 illustrates another network management architecture 300 to which the present application is applied. As shown in FIG. 4, the network management architecture 300 is also a network management architecture that is enhanced and modified based on the network management architecture 100. The network management architecture 300 is different from the network management architecture 200 in that the network management architecture 200 does not include an entity of NFVO. The function of NFVO is implemented by NSM&O. In other words, NSM&O's capabilities include the management of virtual network resources and VNF lifecycle management. There is a communication interface between NSM&O and VNFM. In Figure 4, this interface can be referred to as the NG1 interface. There is a communication interface between NSM&O and VIM. In Figure 4, the interface can be referred to as an NG2 interface.

Among them, NSM&O and VNFM can perform the following interactions through the NG1 interface: support authorization, reservation, allocation, and release of NFVI resources made by VNF; query running status information, such as VNF instance query; VNF initialization update, scaling, termination, etc. ; Transmit VNF related events, status information, etc.

NSM&O and VIM can perform the following interactions through the NG2 interface: NFVI resource reservation, allocation, release, etc.; VNF software image (image) addition, deletion, update, etc.; transmission of NFVI-related configuration information, events, measurement results, upgrade records, etc. .

For the network management architecture 300, in addition to being able to directly manage the PNF, NSM&O can also manage the VNF and VNF lifecycle. Therefore, it is possible to uniformly manage and orchestrate physical and virtual network resources and functions, and optimize resources from a global perspective.

FIG. 5 illustrates another network management architecture 400 to which the present application is applied. As shown in FIG. 5, NM is reserved in the network management architecture 400, and NSM&O and NM are independent of each other. Also, there is a communication interface between NSM&O and NM. In Figure 5, the communication interface can be referred to as an NG3 interface. There is also a communication interface between NSM&O and NFVO. In Figure 5, the communication interface can be referred to as an NG4 interface. There is also a communication interface between NSM&O and EM. In Figure 5, the communication interface can be referred to as an NG5 interface.

The NSM&O and the NM can perform the following interactions on the NG3 interface: the negotiation information between the NSM&O and the NM is transmitted, for example, the NSM&O queries the VNF generated by the NM; the NM feeds back the generated VNF information to the NSM&O, and confirms that the NSM&O is allowed to modify the VNF information; NSM&O informs NM which PNF/VNF will be modified; NSM&O notifies NM of specific modifications to PNF/VNF.

NSM&O and NFVO can interact with each other through NG4 interface: NSM&O participates in VNF lifecycle management through NG4 interface, for example, notifies NFVO to generate, update, and delete a VNF; NSM&O queries NFVO for VNF and NFVI operation information; NFVO to NSM&O Feedback VNF, NFVI operation information; policy management, NSM&O can send a policy to NFVO, indicating the need for VNF deployment; NSM&O performs VNF package management through NG4 interface.

NSM&O and EM can interact with each other through the NG5 interface: NSM&O communicates with the EM through the NG5 interface to manage PNF and VNF (if EM supports management of VNF).

For the network management architecture 400, NSM&O employs a new communication interface to interact with various physical modules in the prior art. NSM&O can orchestrate and manage virtual resources through NFVO and participate in VNF lifecycle management. NSM&O and NM can directly manage PNF. And NSM&O and NM can manage VNF through NFVO or EM. Therefore, for the management of PNF and VNF, NSM&O and NM can be coordinated through communication.

FIG. 6 illustrates another network management architecture 500 to which the present application is applied. As shown in FIG. 6, the NM is also retained in the network management architecture 500. NSM&O and NM are also independent of each other. The network management architecture 500 differs from the third network management architecture in that the entity of the network management architecture 500 does not include NF. The functionality of the NFVO module is implemented by NSM&O. In other words, NSM&O's capabilities include the management of virtual network resources and VNF lifecycle management. Among them, there is a communication interface between NSM&O and VNFM. In Figure 6, the communication interface can be referred to as an NG1 interface. There is a communication interface between NSM&O and VIM. In Figure 6, the communication interface can be referred to as an NG2 interface. There is a communication interface between NSM&O and EM. In Figure 6, the communication interface can be referred to as an NG5 interface. For the specific functions of the NG1 interface, the NG2 interface, and the NG5 interface, the same or similar contents in FIG. 4 and FIG. 5 can be referred to. For the sake of brevity, it will not be repeated here.

For the network management architecture 500, NSM&O uses a new communication interface to interact with various physical modules in the prior art. NSM&O can organize and manage virtual resources and participate in VNF lifecycle management through NFVO. NSM&O and NM can directly manage PNF. Therefore, for the management of PNF, NSM&O and NM can be coordinated through communication. And because NSM&O incorporates the capabilities of NFVO, NSM&O can also directly manage virtual network resources and participate in VNF lifecycle management. NM cannot manage virtual network resources and VNFs.

Those skilled in the art can understand that the examples of FIG. 3 to FIG. 6 are only for facilitating the understanding of the present application by those skilled in the art, and the present application is not limited to the specific numerical values or specific scenarios illustrated. It will be obvious to those skilled in the art that various modifications and changes can be made without departing from the scope of the present application.

Further, it should be noted that the respective functional modules and units introduced above are considered from the viewpoint of the functions they have. In practical applications, each of the foregoing functional modules may be physically present, or two or more devices may be integrated into one unit. Those skilled in the art can easily think of various kinds within the technical scope disclosed in the present application. Equivalent modifications or substitutions are intended to be included within the scope of the present application.

The method of NSI shrinking provided by the present application will be described in detail below in conjunction with the network management architecture 200 to the network management architecture 500.

Figure 7 illustrates a method of shrinking NSI provided by the present application. As shown in FIG. 7, the method 700 includes:

S710. The first NSM&O sends a network function shrink request message to the management device, where the first NSM&O is used to manage and schedule the NSI, where the management device is configured to manage a network function of the target NSI to be contracted, where the network The function shrink request message is used to request the management device to perform shrink processing on the network function.

S720. The first NSM&O receives a shrink feedback message from the management device, where the shrink feedback message is used by the management device to feed back a result of the shrinking process of the network function.

S730. The first NSM&O updates information of the target NSI stored in the memory according to the shrink feedback message.

In the present application, the first NSM&O is used to manage and orchestrate an NSI (for example, a target NSI), and the management device is a device for managing a network function to be contracted of a target NSI, and the management device may be an EM or a VNFM. It can also be NFVO. It should be understood that a network function may include multiple PNFs or multiple VNFs, and thus shrinking of network functions includes at least one of a method of terminating PNF, shrinking PNF, terminating VNF, and shrinking VNF. In addition, the NSI may include multiple network functions. The contracted NSI may refer to a network function that shrinks the NSI, and may also refer to multiple network functions that shrink the NSI. According to the network function to be shrunk, the network function shrinks request cancellation The content of the message and the object to be sent are also different. The above will be described separately.

Case 1,

When the network function to be shrunk is implemented by PNF:

The first NSM&O transmits a network function contraction request message (hereinafter, simply referred to as "first request message") to the EM of the PNF through the corresponding communication interface. Specifically, according to the attributes of the PNF and the scheduling result, the content of the first request message has the following four cases:

a) If the PNF is a PNF shared by multiple NSIs, and the result of the arrangement is to configure the PNF to use less resources (such as storage resources, central processing unit (CPU) usage time, network bandwidth, etc.) service target NSI And the associated NSI, the content of the first request message is to request the PNF to allocate fewer resource service target NSIs and associated NSIs, and adjust related operating parameters and policy information. In the present application, the associated NSI is an NSI that uses the network function in conjunction with the target NSI.

b) If the PNF is a PNF shared by multiple NSIs, and the scheduling result is to stop the PNF from serving the target NSI and the associated NSI, the content of the first request message sent by the first NSM&O to the EM includes but is not limited to i) deleting NSI related parameters, such as the identifier of the target NSI and associated NSI, NSI monitoring and reporting information, etc.; ii) deletion of relevant operating parameters and policy information; iii) closing to other shared functions or/and target NSI-specific functions, associated NSI-specific functions Network connection.

c) If the PNF is a target NSI-specific PNF, and the result of the arrangement is that the existing PNF is configured to use the less resource serving target NSI, the content of the first request message sent by the first NSM&O to the EM is to allocate less resources to the PNF. Serve the target NSI and adjust related operational parameters and policy information.

d) If the PNF is a target NSI-specific PNF, and the scheduling result is to stop the PNF from serving the target NSI, the content of the first request message sent by the first NSM&O to the EM includes, but is not limited to, i) deleting the NSI related parameter, Such as the identification of the target NSI, NSI monitoring and reporting information, etc.; ii) deleting operating parameters and policy information; iii) deleting network connections to other shared functions or/and target NSI-specific functions.

After completing the configuration of the PNF according to the first request message, the EM sends a shrink feedback message to the first NSM&O, and feeds back the result of the shrinking process to the PNF to the first NSM&O.

Case 2,

When the network function to be shrunk is implemented by the VNF, and the result of the orchestration is to terminate the VNF, and the first NSM&O can communicate directly with the VNFM:

The first NSM&O sends a first request message to the EM through a corresponding communication interface, and the content of the first request message includes, but is not limited to, stopping monitoring the running status of the VNF, and deleting the VNF from the management object of the EM.

After performing the termination process on the VNF according to the first request message, the EM sends a shrink feedback message to the first NSM&O, where the shrink feedback message is used to feed back to the first NSM&O that the VNF has been terminated. After receiving the shrink feedback message, the first NSM&O commands the EM to log off/close the VNF virtual port and stop the service.

Then, the first NSM&O sends a notification message to the VNFM to terminate the VNF, and the content of the notification message includes but is not limited to the identity of the VNF, and terminates the command. The VNFM normally closes the VNF according to the notification message and the VNF.

After the VNF is turned off, the VNFM sends a feedback message (ie, a shrink feedback message) to the first NSM&O, and the feedback message is used to feedback that the VNF has been terminated.

Case 3,

When the network function to be shrunk is implemented by the VNF, and the result of the arrangement is to shrink the VNF, and the first NSM&O can communicate directly with the VNFM:

The first NSM&O sends a first request message to the VNFM through a corresponding communication interface, and the content of the first request message includes, but is not limited to, an identity of the VNF to be contracted, and a contraction parameter.

The VNFM performs a VNF contraction feasibility check based on the first request message, including but not limited to verifying whether the first NSM&O is eligible to shrink the VNF, and checking whether the contraction parameter conforms to the specification.

After completing the shrinking process on the VNF, the VNFM sends a feedback message (ie, a shrink feedback message) to the first NSM&O, the feedback message including information authorizing the start of the VNF lifecycle change (if the shrink feasibility check is acceptable), optionally, the The first request message also includes the modified parameters and the resources involved in shrinking the VNF.

The first NSM&O adjusts the contracted VNF application parameters, such as execution functions and operational strategy adjustments, by the EM.

Case 4,

When the network function to be shrunk is implemented by the VNF, and the result of the orchestration is to terminate the VNF, and the first NSM&O cannot communicate directly with the VNFM:

Then, the first NSM&O sends a notification message to the NFVO to terminate the VNF, and the content of the notification message includes but is not limited to the identity of the VNF, the termination command, and the configuration network connection request. The NFVO performs termination processing on the VNF according to the notification message.

After the VNF is terminated, the NFVO sends a feedback message (ie, a shrink feedback message) to the first NSM&O, the feedback message is used to feed back the VNF has been terminated and the configuration network connection is completed.

Case 5,

When the network function to be shrunk is implemented by the VNF, and the result of the orchestration is to shrink the VNF, and the first NSM&O cannot communicate directly with the VNFM:

The first NSM&O sends a first request message to the NFVO through a corresponding communication interface, and the content of the first request message includes, but is not limited to, an identity of the VNF to be contracted, and a contraction parameter.

The NFVO performs a contraction process on the VNF according to the first request message, for example, instructing the VNFM to perform a VNF contraction feasibility check, including but not limited to verifying whether the first NSM&O is eligible to shrink the VNF, and checking whether the contraction parameter conforms to the specification.

After the NFVO completes the contraction process for the VNF, a feedback message (ie, a contraction feedback message) is sent to the first NSM&O, the feedback message including information authorizing the start of the VNF lifecycle change (if the shrink feasibility check is acceptable).

The first NSM&O adjusts the contracted VNF application parameters, such as execution functions and operational strategies, through the EM.

For the above five cases, after receiving the shrink feedback message from the management device, the first NSM&O may update the information of the target NSI stored in the memory according to the shrink feedback message, for example, update the VNF/PNF information of the target NSI.

The foregoing embodiment is only an example, and the application is not limited thereto. For example, the foregoing embodiment determines the receiving end of the first request message, and then determines the content of the first request message according to the attribute of the network function to be contracted. Also First, the content of the first request message is determined according to the attribute of the network function to be contracted, and then the receiving end of the first request message is determined.

Optionally, the method 700 specifically includes:

S701. The first NSM&O sends the network function shrink request message to the management device when the network function is a dedicated network function of the target NSI; or

S702. The first NSM&O sends the network to the management device when the network function is a shared network function of the target NSI and the associated NSI, and the contracting the network function does not affect the service of the associated NSI. A function shrink request message, wherein the associated NSI is an NSI that uses the network function in conjunction with the target NSI.

If the network function to be contracted is the shared network function of the target NSI and the associated NSI, the first NSM&O determines the associated NSI operation according to the NSLD of the associated NSI, and determines whether shrinking the shared network function affects the service being provided by the associated NSI. If there is a negative impact on the service associated with the NSI, the shared network function is not shrunk. If the network function shrink request message is triggered by the sender, the first NSM&O feeds back to the sender that the network function with the contraction is being used and cannot be shrunk. The sender may be an authorized third-party tenant, device vendor, or an application that has the right to shrink the network slice instance.

If the network function to be shrunk is a dedicated network function of the target NSI, the first NSM&O may directly send a network function shrink request message to the management device.

Therefore, the method for shrinking the NSI provided by the present application adopts different pre-processing methods for the shared network function and the dedicated network function before transmitting the network function shrink request message, so that the shrinking shared network function does not share other NSIs sharing the function. The services provided have a negative impact. In addition, if there is a shared network function between multiple NSIs, it is only necessary to shrink the shared network function in one of the NSIs, that is, shrinking multiple NSIs at the same time, which reduces the maintenance time and cost of the system.

Optionally, before the first NSM&O sends the network function shrink request message to the management device, the method 700 further includes:

S703, the first NSM&O acquires an NSI shrink request message, where the NSI shrink request message includes identifier information of the target NSI, where the NSI shrink request message is used to request the first NSM&O to perform the target NSI. Shrinkage treatment;

S704, the first NSM&O determines a network slice template NSLD of the target NSI according to the identifier information;

S705. The first NSM&O determines the network function according to the NSLD.

In this application, the NSI shrink request message acquired by the first NSM&O may be triggered by a mechanism (for example, a performance management mechanism) internal to the first NSM&O, or may be received from a sending end. The NSI shrink request message includes the identifier information of the target NSI, so that the first NSM&O determines the NSLD of the target NSI according to the identifier information, and further determines the network function to be contracted according to the NSLD. If the first NSM&O receives the NSI shrink request message from the sender, the NSI shrink request message further includes the identity of the sender, the service/function description to be contracted, and the like.

When the first NSM&O receives the NSI shrink request message from the sender, the first NSM&O can pass through the memory. Verify the identity of the sender, verify the integrity of the parameters in the NSI shrink request message, for example, verify that the format of the target NSI identification information is correct, and whether the description format of the service/function to be contracted is correct. Subsequently, the first NSM&O checks whether the target NSI exists and its operation, and associates the NSLD of the target NSI. In conjunction with the NSLD, the first NSM&O maps the descriptions to the VNF or/and PNF in the target NSI. If the target NSI does not exist, the first NSM&O feeds back to the sender that the target NSI does not exist. If the target NSI is not shrinkable, the first NSM&O feeds back to the sender that the target NSI cannot shrink. If the target NSI is contractible, the authentication sender has the authority to shrink the target NSI and its corresponding VNF and/or PNF. If the authentication fails, the first NSM&O feeds back the corresponding error information to the sender, such as the sender has no right to shrink the target NSI, the contraction command parameter is incorrect, and the like.

When the first NSM&O internally triggers the NSI contraction request message, the first NSM&O associates the NSLD of the target NSI, verifies whether the target NSI is contractible, and determines the VNF and/or PNF to be contracted in the target NSI in combination with the NSLD. If the target NSI is not shrinkable, the target NSI may be fed back to the equipment provider and/or the tenant renting the network slice instance. The target NSI performance is excessive or the resource utilization is low, and the equipment provider or the tenant decides the next action.

Therefore, the method for shrinking NSI provided by the present application, the first NSM&O can flexibly determine the shrinking process of the target NSI according to actual conditions. When the equipment provider or the authorized network fragment instance third-party tenant finds that the existing NSI has excessive performance, it shrinks the NSI as needed, or automatically shrinks when the performance of the NSI is excessive according to the policy, which reduces the operation and maintenance cost.

Optionally, after the first NSM&O acquires the NSI shrink request message, and the first NSM&O sends the network function shrink request message to the management device, the method 700 further includes:

S706, the first NSM&O sends a notification message to the network manager NM, where the notification message is used to notify the NM that the first NSM&O needs to perform a shrinking process on the network function;

S707. The first NSM&O receives an acknowledgment message from the NM, where the acknowledgment message is used to instruct the first NSM&O to perform a shrinking process on the network function.

In the present application, the network management architecture includes an NM, and the first NSM&O sends a notification message to the NM before the shrinking process of the shrinking network function, notifying the NM that the first NSM&O needs to perform shrink processing on the network function, and sends an acknowledgement message according to the NM. It is determined that the network function is shrunk to ensure that NM and NSM&O do not create configuration conflicts.

Optionally, after the first NSM&O receives the shrinking feedback message from the management device, and before the first NSM&O updates the information of the target NSI stored in the memory according to the feedback message, the method 700 further includes:

S721, the first NSM&O sends a resource allocation request message to the virtualized infrastructure manager VIM, where the resource allocation request message is used to request the VIM to release the idle resource after the network function shrinks;

S722. The first NSM&O receives a resource allocation feedback message from the VIM.

Updating, by the first NSM&O, the information of the target NSI stored in the memory according to the shrinking feedback message includes:

S731. The first NSM&O updates information of the target NSI stored in the memory according to the shrinkback feedback message and the resource allocation feedback message.

After the first NSM&O receives the shrink feedback message from the VNFM (optionally, the content of the shrink feedback message includes the parameter updated after the VNF shrinks), the first NSM&O sends a resource allocation request message to the VIM, and the resource allocation request message requests the VIM to shrink. The resource occupied by the VNF, optionally, the resource allocation request message request is further used to request the VIM to adjust the internal network connection of the VNF. If the resource allocation request message requests to shrink the existing VNF The VIM does not need to delete the VNF internal network connection. If the resource allocation request message requests to delete some VMs of the VNF, the VIM first adjusts or deletes the VNF internal resources. For example, the VIM does not need to delete the VNF internal network connection. Network connection, delete the virtual machine and release the resources.

When the first NSM&O receives the shrink feedback message from the VNFM, and the content of the shrink feedback message is the terminating VNF, the first NSM&O sends a resource allocation request message to the VIM, where the resource allocation request message requests the VIM to terminate the VNF and release the corresponding resource. . After receiving the resource allocation request message, the VIM deletes the network connection existing between the VNF and other network functions of the target NSI and releases resources constituting the VNF, such as deleting the virtual machine and releasing resources. If the terminated VNF is a VNF shared by the target NSI and the associated NSI, the VIM may also delete the network connection existing between the network function of the VNF and the associated NSI and release the corresponding resource.

After completing the corresponding processing according to the resource allocation request message, the VIM sends a resource allocation feedback message to the first NSM&O, and the resource allocation feedback message is used to feedback that the corresponding resource shrinking process has been completed. The first NSM&O updates the information of the target NSI stored in the memory according to the shrink feedback message and the resource allocation feedback message.

According to the method for shrinking NSI provided by the present application, the first NSM&O requests the VIM to release the idle resources after the VNF shrinks by sending a resource allocation request message to the VIM, thereby improving resource utilization.

Optionally, when the network function is a shared network function, the method 700 further includes:

S732. The first NSM&O updates information about an associated NSI stored in the memory according to the shrinkback feedback message, where the associated NSI is an NSI that uses the shared network function together with the target NSI.

When the contracted network function is a shared network function, the first NSM&O may update the information of the associated NSI stored in the memory according to the shrink feedback message, for example, update the VNF/PNF information of the associated NSI. This keeps the information in the system synchronized.

Optionally, the first NSM&O acquires an NSI shrink request message, including:

S708. The first NSM&O acquires the NSI shrink request message sent by the second NSM&O.

In the present application, the first NSM&O may be a module in a hierarchical NSM&O, the first NSM&O may acquire the NSI shrink request message from the second NSM&O, and the second NSM&O is another one of the hierarchical NSM&Os. A module.

Fig. 8 shows a schematic structural diagram of a NSM&O having a hierarchical structure. As shown in FIG. 8, the NSM&O includes a multi-vendor NSM&O (also referred to as a "cross-device arranging device" for managing multiple sub-network slices or devices of multiple device vendors. The concept is not limited) and three domain orchestrators (domain NSM&O). Among them, multi-vendor NSM&O is equivalent to the second NSM&O, and domain NSM&O is equivalent to the first NSM&O. Multi-vendor NSM&O acts as a total control orchestrator, managing each domain NSM&O. For example, a network slice instance may be composed of a core network sub-slice instance and an access network sub-slice instance. At this time, there is a multi-vender NSM&O responsible for overall network slice instance management and separately managing core network sub-slice instances and access networks. Two domain NSM&Os of the slice instance; or one network slice instance may be divided into sub-slice instances provided by a plurality of different device vendors, each sub-slice instance being composed of a device provider device, such as a network slice instance of a device vendor The multi-vendor NSM&O is responsible for the overall management, and the domain NSM&O provided by several equipment vendors manages the equipment provided by the equipment manufacturer. The description of the sub-slice instance is similar to the description of the entire slice instance. The information of the sub-slice instance may include network functions, connection relationships between network functions, KPI requirements, service level agreement (SLA), and operational parameters to be monitored. Wait.

Each subnet slice instance is managed by each domain NSM&O. Multi-vendor NSM&O received After shrinking the request message, you can determine which sub-network slice instances need to be shrunk, and then directly notify the corresponding domain NSM&O to shrink. The foregoing embodiment is only an example, and the application is not limited thereto, and the number of domain NSM&Os may be other numbers.

FIG. 9 shows a schematic flow chart of a method of shrinking NSI of a hierarchical NSM&O. As shown in FIG. 9, when the multi-vendor NSM&O receives the request for shrinking the NSI from the transmitting end or the multi-vendor NSM&O initiates the request to shrink the NSI, the configuration of the NSI is known to be divided into several sub-slice instances (the configuration of the NSI is The NSI is determined upon creation) and determines that one or more of the sub-slice instances (ie, the target NSI) need to shrink. The multi-vendor NSM&O then informs the corresponding domain NSM&O to complete the contraction of the sub-slice instance. How to shrink the subnet slice is determined by domain NSM&O.

Therefore, the method for shrinking NSI provided by the present application can determine the shrinkage of the target NSI through the hierarchical NSM&O, and can flexibly manage the multi-domain and multi-vendor network.

In summary, the method for shrinking NSI provided by the present application manages the NSI through the newly designed network architecture, and can simultaneously manage physical and virtual network functions/resources to implement network slicing, which shortens network deployment time and saves time. Deployment costs. And when shrinking NSI, by treating the common network function and the dedicated network function differently, it is avoided to affect the services that other slice instances are providing when shrinking the general network function.

The method for shrinking NSI provided by the present application is described in detail above from the perspective of NSM&O. Hereinafter, the method for shrinking NSI provided by the present application will be described in detail from the perspective of a management device with reference to FIG.

FIG. 10 shows a schematic flow chart of another method for shrinking NSI provided by the present application. As shown in FIG. 10, the method 1000 includes:

S1010. The management device receives a network function shrink request message from the NSM&O, where the management device is configured to manage a network function to be contracted of the target NSI, and the NSM&O is used to manage and schedule the network slice instance NSI.

S1020. The management device performs a shrinking process on the network function according to the network function shrink request message.

S1030. The management device sends a shrink feedback message to the NSM&O, where the shrink feedback message is used to feed back a result of the shrinking process of the network function.

In the present application, the management device is a device for managing the network function of the target NSI to be contracted, and the management device may be an EM, a VNFM, or an NFVO. NSM&O is used to manage and orchestrate NSI (for example, target NSI). It should be understood that a network function may include multiple PNFs or multiple VNFs. Therefore, the shrinking of network functions includes terminating PNF, shrinking PNF, terminating VNF, and At least one treatment method of contracting VNF. In addition, the NSI may include multiple network functions. The contracted NSI may refer to a network function that shrinks the NSI, and may also refer to multiple network functions that shrink the NSI. The content of the network function contraction request message and the transmission object are also different according to the network function to be contracted.

The network function shrink request message received by the management device may be a single NSM&O (ie, the NSM&O includes only one module), or may be sent by the domain NSM&O in the composite NSM&O (ie, the NSM&O includes at least two different modules). Message.

The step of the management device shrinking the network function of the target NSI according to the network function shrink request message is the same as the step of managing the device involved in the method 700, and details are not described herein again.

After the management device completes the shrinking process of the network function of the target NSI, it sends a shrink feedback message to the NSM&O, which is used to feed back the result of the shrinking process of the network function. NSM&O according to the results of the shrinkage process The VIM sends a resource allocation request message, requesting the VIM to release the idle resource after the network function shrinks, and the NSM&O may also update the information of the target NSI in the memory according to the result of the shrinking process, for example, the VNF/PNF information of the target NSI, if the shrink function is the sharing function. NSM&O simultaneously updates the VNF/PNF information in the associated NSI.

Optionally, the management device includes a VNFM, and the network function includes a first VNF instance,

The shrinking process of the network function by the management device according to the network function shrink request message includes:

S1021. The VNFM performs a shrink feasibility check on the first VNF instance according to the network function shrink request message.

S1022, the VNFM shrinks the first VNF instance when the shrinkage feasibility check is passed.

If the network function shrink request message requests the VNFM to shrink the first VNF instance, the VNFM first checks the scalability of the first VNF instance before performing the shrinking process on the first VNF instance (ie, performing a shrink feasibility check on the first VNF instance) The check includes, but is not limited to, verifying whether the NSM&O is eligible to shrink the first VNF instance and checking if the shrinkage parameters are in compliance.

If the above check passes (ie, the feasibility check is passed), the VNFM performs a shrinking process on the first VNF instance. After the VNFM performs the shrinking process on the first VNF instance (eg, corrects the shrink parameter), it sends a shrink feedback message to the NSM&O, which is used to authorize the NSM&O to perform the processing of the first VNF instance (eg, changing the life cycle of the first VNF). Optionally, the shrink feedback message also carries the corrected shrink parameters and the resources involved.

Therefore, the method of shrinking NSI provided by the present application checks the contraction feasibility of the VNF instance to be shrunk by VNFM, thereby ensuring that the shrinkage processing of the VNF instance can be performed correctly.

Optionally, the management device includes an EM, the network function includes a second VNF instance, and the second VNF instance is an NM generated VNF instance,

The shrink feedback message is used to feed back the service of the second VNF instance has been stopped when the network function request message is used to request to stop the service of the second VNF instance.

In this application, when the system includes the NM, and the VNF instance to be contracted (ie, the second VNF instance) is a VNF instance generated by the NM, the NSM&O cannot shrink the VNF instance, that is, the resources constituting the VNF instance cannot be reduced, wherein , NSM&O checks in advance whether the VNF instance can be shrunk.

When the system includes the NM and the result of the orchestration is that the second VNF instance does not need to continue to provide the service, the NSM&O initiates a request to configure the second VNF to the EM managing the second VNF instance through the NG5 interface (ie, the network function request message is used to request the termination). The second VNF instance). The request includes points not limited to:

a) If the network function corresponding to the second VNF instance is a dedicated network function, the service provided to the target NSI is stopped, the configuration parameters (such as the network slice instance identifier) for supporting the target NSI service are deleted, and the policy of the service target NSI is deleted. The EM executes the request and feeds back the execution result through the NG5 interface. NSM&O informs NFVO through the NG4 interface to terminate/close the possible network connection between the second VNF instance and the target NSI-specific network function, and release the corresponding network resources. The NFVO performs the request and feeds back the execution results via the NG4 interface. This substep is repeated until all VNF instances generated by the NM are configured.

b) if the network function corresponding to the second VNF instance is a shared network function, stopping the service provided to the target NSI and the associated NSI, deleting the configuration parameters (such as the network slice instance identifier) for supporting the target NSI and the associated NSI service, and deleting the service Target NSI and associated NSI policies. The EM executes the request and feeds back the execution result through the NG5 interface. NSM&O informs NFVO through the NG4 interface to terminate/close the possible network connection between the VNF and the target NSI and the associated NSI network function, and release the corresponding network resources. The NFVO performs the request and feeds back the execution results via the NG4 interface. Repeat this substep until all VNF instances generated by NM are configured

Therefore, the method for shrinking NSI provided by the present application determines whether the VNF instance to be shrunk can be shrunk by EM checking the properties of the VNF instance to be shrunk, thereby avoiding an error when NSM&O shrinks the NNF generated VNF instance.

The present application will be further described in detail below based on the common aspects of the present application as described above.

FIG. 11 is a schematic flowchart of a method for further shrinking an NSI provided by the present application. The method is applicable to the system shown in FIG. 4, as shown in FIG. 11, the method 1100 includes:

S1101, option a): NSM&O receives an NSI contraction request initiated by the sender. The request shall include the identifier of the network slice instance, the identity of the sender, and the service/function description to be shrunk. The sender may be an authorized third-party tenant, device vendor, or an application that has the right to shrink the network slice instance. Option b): Other mechanisms within NSM&O, such as performance management mechanisms, trigger NSI shrink requests.

S1102: The NSM&O checks the NSI status and associates the corresponding NSLD through the memory authentication and authentication.

a) If NSM&O receives a shrink request from the sender.

i.NSM&O needs to verify the identity of the sender through the memory, verify the integrity of the parameters in the request, such as whether the network slice instance identification format is correct, and whether the description format of the service/function to be contracted is correct.

Ii. NSM&O checks whether the corresponding network slice instance exists and its operation, and associates the NSLD of the network slice instance with NSLD, and NSM&O maps these descriptions to the VNF or/and PNF in the NSI. If the network segmentation instance does not exist, NSM&O feeds back to the sender that the network slice instance does not exist. If the slice instance is not shrinkable, the slice instance cannot be shrunk back to the sender. If the slice instance is shrinkable, the authentication sender has permission to shrink the requested network slice instance and its corresponding VNF or/and PNF. If the authentication verification fails, NSM&O feeds back the corresponding error to the sender, such as the right to shrink the slice instance, the shrink command parameter error, and so on.

b) If the network slice instance shrink request is triggered by the NSM&O internal mechanism, such as performance management trigger, the NSM&O associates the network NSLD instance to verify whether the slice instance is shrinkable, and combines NSLD to determine the VNF or/and PNF to be shrunk in the NSI. If the slice instance is not shrinkable, you can choose to report the target NSI performance excess or low resource utilization to the equipment provider and/or the tenant renting the network slice instance. The equipment provider or tenant decides the next action.

S1103, NSM&O orchestrate the VNF or/and PNF to be shrunk, including whether to shrink the VNF instance, configure the PNF, terminate the VNF instance, etc., and check the network function scalability. Based on the information in the associated NSLD, NSM&O determines whether the function to be shrunk belongs to the common network function shared by the multi-slice instance or the network function exclusive to the fragmented instance (hereinafter referred to as the target NSI). If it is necessary to shrink the general network function shared by the multi-slice instance, execute S1104, otherwise execute S1105.

S1104: If the general network function shared by the multi-slice instance is to be contracted, the NSLD of the other slice instance (hereinafter referred to as the associated NSI) other than the target NSI sharing the network function is associated. NSM&O checks the associated NSI operation and determines whether shrinking the generic network function will affect the services being provided by the associated NSI. If the NSI-related service is adversely affected, the shared network function is not shrunk (if the shrink request is initiated by the sender), the feedback to the sender network function is being used and cannot be shrunk.

S1105. If the function of shrinking the result of the orchestration is implemented by the PNF, the NSM&O initiates a request to configure the network function to the EM that manages the PNF through the Itf-N interface:

a) If the PNF is a PNF shared by a multi-slice instance, and the result of the arrangement is to configure an existing PNF to use less resources (such as storage resources, CPU time, network bandwidth, etc.) service target NSI and associated NSI, the configuration request sent by NSM&O In order to allocate less resources to the target NSI and associated NSI, the PNF is adjusted, and relevant operational parameters and policy information are adjusted.

b) If the PNF is a PNF shared by the multi-slice instance, and the scheduling result is to stop the PNF from serving the target NSI and the associated NSI, the NSM&O sends the PNF request to the EM, where the configuration content includes but is not limited to i) deleting the NSI related Parameters such as target NSI and associated NSI identification, NSI monitoring and reporting information, etc.; ii) deletion of relevant operational parameters and policy information; iii) closure of other shared functions or/and target NSI-specific functions, associated NSI-specific functions, etc. connection.

c) if the PNF is a target NSI-specific PNF, and the result of the arrangement is that the existing PNF is configured to use the less resource serving target NSI and the associated NSI, the configuration request sent by the NSM&O is to allocate the PNF to the less resource service target NSI, and Adjust related operating parameters and policy information.

If the PNF is the target NSI-specific PNF, and the scheduling result is to stop the PNF from serving the target NSI, the NSM&O sends the configuration of the PNF, and the configuration content includes, but is not limited to, i) deleting the NSI related parameters, such as the target NSI identifier. NSI monitoring and reporting information, etc.; ii) deleting operating parameters and policy information, etc.; iii) deleting network connections to other shared functions or/and target NSI-specific functions.

S1106: The EM performs a configuration request for the PNF, and the configuration content is as described in S1105.

S1107: The EM returns to the NSM&O feedback configuration completion confirmation. If other PNFs in the target NSI are not configured, S1105 to S1107 are repeated.

S1108: If the scheduling result needs to terminate the shared or exclusive VNF instance, the NSM&O sends a request to the EM to stop the management of the VNF instance, including but not limited to stopping monitoring the running state of the VNF instance, and deleting the management object. If the layout result needs to shrink the VNF instance, step S1112 is performed.

S1109, the EM performs a request for the termination of the management of the VNF instance by S1108.

S1110, EM returns the management confirmation to NSM&O.

On S1111, the NSM&O command EM closes the virtual port of the VNF instance and stops the service.

S1112: The NSM&O sends a shrink/end VNF instance notification to the VNFM through the NG1 interface, and the content of the notification includes but is not limited to the identity of the VNF instance to be shrunk/terminated, and the contraction parameter/end command.

S1113, VNFM performs VNF contraction/termination request:

a) If the request is to shrink the VNF instance, the VNFM performs a VNF instance shrink feasibility check, including but not limited to verifying that NSM&O is eligible to shrink the VNF instance and checking that the shrinkage parameters are in compliance.

b) If the request is to terminate the VNF instance, the VNFM performs a request to terminate the VNF instance, that is, cooperates with the VNF instance itself to properly close the VNF instance.

S1114, VNFM feeds back to NSM&O through the NG1 interface:

a) If the request is to shrink the VNF instance, the feedback shrinks the feasibility check result, the feedback result contains (possibly) the modified parameters and the resources involved, and authorizes the start of the VNF instance life cycle change.

b) If the request is to terminate the VNF instance, the feedback terminates the execution confirmation.

S1115: The NSM&O initiates a resource allocation request and an internal connection adjustment/deletion request required to shrink/terminate the VNF instance to the VIM through the NG2 interface according to the updated parameter fed back by S1114 (shrinking the VNF instance only).

S1116. The VIM performs a resource allocation change request and an internal connection adjustment/deletion request.

a) When shrinking a shared VNF instance or a proprietary VNF instance:

i. If the VNF instance part of the existing resources, such as reducing the CPU usage, storage resource usage, bandwidth reduction, etc., do not need to delete the internal network connection.

Ii. If you delete some VMs for the VNF instance, first adjust/delete the internal network connection, then shut down the VM and release the resources.

b) When terminating the VNF instance:

The VIM deletes the network connection between the VNF instance and other network functions of the target NSI and releases the resources that constitute the VNF instance, such as deleting the virtual machine and releasing resources.

S1117: If the terminated VNF instance is a slice sharing common network function, the VIM is also required to delete the network connection existing between the VNF instance and the associated NSI network function and release the corresponding resource.

On S1118, the VIM confirms the resource allocation and network connection configuration to the NSM&O through the NG2 interface. NSM&O passes this information to the VNFM through the NG1 interface only when shrinking the VNF instance.

S1119, the VNFM adjusts the VNF life cycle parameters and deployment parameters only when the VNF instance is shrunk.

S1120, only when the VNF instance is shrunk, the VNFM feeds back to the NSM&O through the NG2 interface to end the contraction of the VNF instance.

S1121, only when shrinking the VNF instance, NSM&O adjusts the contracted VNF application parameters, such as execution function and operational strategy adjustment, by EM.

S1122, NSM&O updates the VNF/PNF information of the target NSI in the memory slice instance memory. If the shared function is shrunk, the VNF/PNF information in the associated NSI is updated at the same time.

S1123: If the slice instance shrink request is sent by the sending end, the slice instance is successfully fed back to the sending end.

The method for shrinking the NSI provided by the present application is based on the upgrade of the existing network management system, supports the network slice instance management, supports the unified orchestration management of the physical network function and the virtual network function, and supports the shrinking of the network slice instance, and belongs to the network slice lifecycle management. important parts of. This application allows the device vendor or the authorized network segment instance. The third-party tenant can shrink the network slice instance as needed when the existing slice instance is over-performing, or automatically shrink when the slice instance has excessive performance according to the policy, reducing the operation and maintenance cost and saving the overhead. In addition, the present application differentially manages the common network functions shared by other slice instances in the network slice instance and the slice-specific network functions, so that the shrinkage of the shared network function does not adversely affect the services provided by other slice instances.

FIG. 12 is a schematic flowchart of a method for further shrinking an NSI provided by the present application. The method is applicable to the system shown in FIG. 3, as shown in FIG. 12, the method 1200 includes:

S1201, option a): NSM&O receives an NSI contraction request initiated by the sender. The request shall include the identifier of the network slice instance, the identity of the sender, and the service/function description to be shrunk. The sender may be an authorized third-party tenant, device vendor, or an application that has the right to shrink the network slice instance. Option b): NSM&O internal Other mechanisms, such as performance management mechanisms, trigger NSI shrink requests.

S1202, NSM&O checks the NSI status and associates the corresponding NSLD through memory authentication and authentication.

a) If NSM&O receives a shrink request from the sender.

S1203, NSM&O orchestrate the VNF or/and PNF to be shrunk, including whether to shrink the VNF instance, configure the PNF, terminate the VNF instance, etc., and check the network function scalability. Based on the information in the associated NSLD, NSM&O determines whether the function to be shrunk belongs to the common network function shared by the multi-slice instance or the network function exclusive to the fragmented instance (hereinafter referred to as the target NSI). If the general network function shared by the multi-slice instance is to be shrunk, S1204 is performed, otherwise S1205 is performed.

S1204: If the general network function shared by the multi-slice instance is to be contracted, the NSLD of the other slice instance (hereinafter referred to as the associated NSI) other than the target NSI sharing the network function is associated. NSM&O checks the associated NSI operation and determines whether shrinking the generic network function will affect the services being provided by the associated NSI. If the NSI-related service is adversely affected, the shared network function is not shrunk (if the shrink request is initiated by the sender), the feedback to the sender network function is being used and cannot be shrunk.

S1205. If the function of shrinking the result of the orchestration is implemented by the PNF, the NSM&O initiates a request to configure the network function to the EM that manages the PNF through the Itf-N interface:

S1206: The EM performs a configuration request for the PNF, and the configuration content is as described in S1205.

S1207: The EM feeds back to the NSM&O to complete the configuration confirmation. If the other NNFs in the target NSI are not configured, S1205 to S1207 are repeated.

S1208: If the scheduling result needs to terminate the shared or exclusive VNF instance, the NSM&O sends a request to the EM to stop the management of the VNF instance, including but not limited to stopping monitoring the running state of the VNF instance, and deleting the management object. If the result of the arrangement needs to shrink the VNF instance, step S1212 is performed.

S1209, the EM performs a request for termination of management of the VNF instance by S1208.

S1210, EM returns the management confirmation to NSM&O.

On S1211, the NSM&O command EM closes the virtual port of the VNF instance and stops the service.

S1212: The NSM&O sends a shrink/end VNF instance notification to the NFVO. The content of the notification includes but is not limited to the identity of the VNF instance to be shrunk/terminated, and the shrink parameter/end command.

S1213, NFVO performs the following method according to the shrink/end VNF instance notification.

NFVO requests VNFM to perform VNF contraction/termination request:

VNFM feedback to NFVO:

The NFVO initiates a resource allocation request and an internal connection adjustment/deletion request required to shrink/terminate the VNF instance to the VIM according to the updated parameters of the VNFM feedback described above (shrinking only the VNF instance).

VIM performs resource allocation change requests and internal connection adjustment/deletion requests:

a) When shrinking a shared VNF instance or a proprietary VNF instance:

b) When terminating the VNF instance:

If the terminated VNF instance is a slice sharing common network function, the VIM is also required to delete the network connection existing between the VNF instance and the associated NSI network function and release the corresponding resource.

The VIM acknowledges the NFVO feedback resource allocation and network connection configuration. NFVO only when shrinking VNF instances Pass this information to VNFM.

VNFM adjusts VNF lifecycle parameters and deployment parameters only when shrinking VNF instances.

S1214, when shrinking the VNF instance, the NFVO feeds back to the NSM&O VNF instance contraction end; when terminating the VNF instance, the NFVO feeds back to the NSM&O VNF instance contract termination, and configures the network connection completion notification.

S1215, only when shrinking the VNF instance, NSM&O adjusts the contracted VNF application parameters, such as execution function and operational strategy adjustment, by EM.

S1216, NSM&O updates the VNF/PNF information of the target NSI in the memory slice instance memory. If the shared function is shrunk, the VNF/PNF information in the associated NSI is updated at the same time.

S1217: If the slice instance shrink request is sent by the sending end, the slice instance is successfully fed back to the sending end.

The method for shrinking NSI provided by the present application is based on upgrading an existing network management system, supporting slice management, and supporting direct management of physical network functions. For virtual network functions, the NFV MANO system is used to manage orchestration, and network slice under the system architecture is supported. Instance shrinkage is an important part of network slice lifecycle management. This application allows the device vendor or the authorized network segment instance. The third-party tenant to shrink the network slice instance as needed when the existing slice instance is over-performing, or automatically shrink when the slice instance has excessive performance according to the policy, reducing the operation and maintenance cost and saving the resource overhead. . In addition, the present application differentially manages the common network functions shared by other slice instances in the network slice instance and the slice-specific network functions, so that the shrinkage of the shared network function does not adversely affect the services provided by other slice instances.

FIG. 13 is a schematic flowchart of a method for further shrinking an NSI provided by the present application. The method is applicable to the system shown in FIG. 5, as shown in FIG. 13, the method 1300 includes:

S1301, option a): NSM&O receives an NSI contraction request initiated by the sender. The request shall include the identifier of the network slice instance, the identity of the sender, and the service/function description to be shrunk. The sender may be an authorized third-party tenant, device vendor, or an application that has the right to shrink the network slice instance. Option b): Other mechanisms within NSM&O, such as performance management mechanisms, trigger NSI shrink requests.

S1302, NSM&O checks the NSI status and associates the corresponding NSLD through memory authentication and authentication.

a) If NSM&O receives a shrink request from the sender.

S1303, NSM&O orchestration needs to shrink VNF or / and PNF, including whether to shrink VNF instances, configure PNF, terminate VNF instances, etc., and check network function scalability, if network slice instantiation / update / extension is used NM generated VNF, NSM & O can not shrink the VNF, that is, can not reduce the resources that constitute the VNF. Based on the information in the associated NSLD, NSM&O determines whether the function to be shrunk belongs to the common network function shared by the multi-slice instance or the network function exclusive to the fragmented instance (hereinafter referred to as the target NSI). If it is required to shrink the common network function shared by the multi-slice instance, execute S1304, otherwise execute S1305.

S1304: If the general network function shared by the multi-slice instance is to be contracted, the NSLD of the other slice instance (hereinafter referred to as the associated NSI) other than the target NSI sharing the network function is associated. NSM&O checks the associated NSI operation and determines whether shrinking the generic network function will affect the services being provided by the associated NSI. If the NSI-related service is adversely affected, the shared network function is not shrunk (if the shrink request is initiated by the sender), the feedback to the sender network function is being used and cannot be shrunk.

S1305, NSM&O informs the NM which network functions (including PNF and VNF) will be configured through the NG3 interface.

On the S1306, the NM sends an acknowledgment to the NSM&O through the NG3 interface. This prevents the NM and NSM&O from being configured at the same time.

S1307. If the function of shrinking the result of the orchestration is implemented by the PNF, the NSM&O initiates a request to configure the network function to the EM that manages the PNF through the Itf-N interface:

S1308, the EM performs a configuration request for the PNF, and the configuration content is as described in S1305.

In S1309, the EM returns to the NSM&O feedback configuration completion confirmation. If other PNFs in the target NSI are not configured, S1307 to S1309 are repeated.

S1310: When the scheduling result is that the VNF is not required to provide the service, the NSM&O initiates a request for configuring the network function to the EM that manages the VNF through the NG5 interface. The request includes but is not limited to:

a) If the VNF is a dedicated network function, stop the service provided to the target NSI, delete the configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and delete the policy of the service target NSI. The EM executes the request and feeds back the execution result through the NG5 interface. NSM&O informs NFVO to terminate/close the VNF and mesh through the NG4 interface. A possible network connection between NSI-specific network functions releases the corresponding network resources. The NFVO performs the request and feeds back the execution results via the NG4 interface. This substep is repeated until all VNFs generated by the NM are configured.

b) If the VNF is a shared network function, the services provided to the target NSI and the associated NSI are stopped, the configuration parameters for supporting the target NSI and the associated NSI service, such as the network slice instance identifier, and the policy of deleting the service target NSI and the associated NSI are deleted. The EM executes the request and feeds back the execution result through the NG5 interface. NSM&O informs NFVO through the NG4 interface to terminate/close the possible network connection between the VNF and the target NSI and the associated NSI network function, and release the corresponding network resources. The NFVO performs the request and feeds back the execution results via the NG4 interface. This substep is repeated until all VNFs generated by the NM are configured.

S1311: If the scheduling result needs to terminate the shared or exclusive VNF instance, the NSM&O sends a request to the EM to stop the management of the VNF instance, including but not limited to stopping monitoring the running status of the VNF instance, and deleting the management object. If the result of the arrangement needs to shrink the VNF instance, step S1312 is performed.

S1312. The EM performs a request for termination of management of the VNF instance by S1311.

S1313, EM returns the management confirmation to NSM&O.

On S1314, the NSM&O command EM closes the virtual port of the VNF instance and stops the service.

S1315: The NSM&O sends a shrink/end VNF instance notification to the NFVO. The content of the notification includes but is not limited to the identity of the VNF instance to be shrunk/terminated, and the contraction parameter/end command.

S1316, NFVO performs the following method according to the shrink/end VNF instance notification.

NFVO requests VNFM to perform VNF contraction/termination request:

VNFM feedback to NFVO:

a) When shrinking a shared VNF instance or a proprietary VNF instance:

b) When terminating the VNF instance:

The VIM acknowledges the NFVO feedback resource allocation and network connection configuration. The NFVO passes this information to the VNFM only when the VNF instance is shrunk.

NFVO adjusts VNF lifecycle parameters and deployment parameters only when shrinking VNF instances.

S1317, only when shrinking the VNF instance, NFVO feeds back to the NSM&O VNF instance contraction end; when terminating the VNF instance, NFVO feeds back to the NSM&O VNF instance contract termination completion, and configures the network connection completion notification.

S1318, only when shrinking the VNF instance, NSM&O adjusts the contracted VNF application parameters, such as execution function and operational strategy adjustment, by EM.

S1319, NSM&O informs the NM network that the function configuration has been completed, and informs the specific content of the configuration.

S1320, NSM&O updates the VNF/PNF information of the target NSI in the memory slice instance memory. If the shared function is shrunk, the VNF/PNF information in the associated NSI is updated at the same time.

S1321: If the slice instance shrink request is sent by the sending end, the slice instance is successfully fed back to the sending end.

The method for shrinking NSI provided by the present application retains the existing network management system, adopts an independent network management system for the network slicing service, and supports direct programming management of the physical network function, and uses the NFV MANO system management orchestration for the virtual network function, and supports this. The network slice instance shrinks under the system architecture, which is an important part of network slice lifecycle management. This application allows the device vendor or the authorized network segment instance. The third-party tenant can shrink the network slice instance as needed when the performance is excessive, or automatically shrink when the slice instance has excessive performance according to the policy, which reduces the operation and maintenance cost and saves resource overhead. In addition, the present application differentially manages the common network functions shared by other slice instances in the network slice instance and the slice-specific network functions, so that the shrinkage of the shared network function does not adversely affect the services provided by other slice instances.

FIG. 14 is a schematic flowchart of a method for further shrinking an NSI provided by the present application. The method is applicable to the system shown in FIG. 4, as shown in FIG. 14, the method 1400 includes:

S1401, option a): NSM&O receives an NSI contraction request initiated by the sender. The request shall include the identifier of the network slice instance, the identity of the sender, and the service/function description to be shrunk. The sender may be an authorized third-party tenant, device vendor, or an application that has the right to shrink the network slice instance. Option b): Other mechanisms within NSM&O, such as performance management mechanisms, trigger NSI shrink requests.

S1402, NSM&O checks the NSI status and associates the corresponding NSLD through memory authentication and authentication.

a) If NSM&O receives a shrink request from the sender.

b) If the network slice instance shrink request is triggered by the NSM&O internal mechanism, such as performance management trigger, the NSM&O associates the network NSLD instance to verify whether the slice instance is shrinkable, and combines NSLD to determine the VNF or/and PNF to be shrunk in the NSI. If the slice instance is not shrinkable, you can choose to ship to the device vendor and/or rent the network slice instance. The tenant feedback target NSI has excessive performance or low resource utilization, and the equipment provider or tenant decides the next action.

S1403, NSM&O orchestrate the VNF or/and PNF to be shrunk, including whether to shrink the VNF instance, configure the PNF, terminate the VNF instance, etc., and check the network function scalability. Based on the information in the associated NSLD, NSM&O determines whether the function to be shrunk belongs to the common network function shared by the multi-slice instance or the network function exclusive to the fragmented instance (hereinafter referred to as the target NSI). If it is required to shrink the common network function shared by the multi-slice instance, execute S1404, otherwise execute S1405.

S1404: If the general network function shared by the multi-slice instance is to be contracted, the NSLD of the other slice instance (hereinafter referred to as the associated NSI) other than the target NSI sharing the network function is associated. NSM&O checks the associated NSI operation and determines whether shrinking the generic network function will affect the services being provided by the associated NSI. If the NSI-related service is adversely affected, the shared network function is not shrunk (if the shrink request is initiated by the sender), the feedback to the sender network function is being used and cannot be shrunk.

S1405, NSM&O informs the NM which network functions (such as PNF) are to be configured through the NG3 interface.

On the S1406, the NM sends an acknowledgment to the NSM&O through the NG3 interface to prevent the NM and NSM&O from being configured at the same time.

S1407. If the function of shrinking the result of the orchestration is implemented by the PNF, the NSM&O initiates a request to configure the network function to the EM that manages the PNF through the Itf-N interface:

S1408, the EM performs a configuration request for the PNF, and the configuration content is as described in S1407.

S1409: The EM feeds back to the NSM&O to complete the configuration confirmation. If the other NNFs in the target NSI are not configured, S1407 to S1409 are repeated.

After the PNF is configured on the S1410 and the NSM&O, the specific content of the PNF configuration is fed back to the NM through the NG3.

S1411: If the scheduling result needs to terminate the shared or dedicated VNF instance, the NSM&O sends a request to the EM to stop the management of the VNF instance, including but not limited to stopping monitoring the running state of the VNF instance, and deleting the management object. If the layout result needs to shrink the VNF instance, step S1412 is performed.

S1412, the EM performs a request for termination of management of the VNF instance by S1411.

S1413, EM returns the management confirmation to NSM&O.

On S1414, the NSM&O command EM closes the virtual port of the VNF instance and stops the service.

S1415: The NSM&O sends a shrink/end VNF instance notification to the VNFM through the NG1 interface. The content of the notification includes but is not limited to the identity of the VNF instance to be shrunk/terminated, and the shrink parameter/end command.

S1416, VNFM performs VNF shrink/end request:

S1417, VNFM feeds back to NSM&O through the NG1 interface:

S1418, NSM&O initiates a resource allocation request and an internal connection adjustment/deletion request required to shrink/terminate the VNF instance to the VIM through the NG2 interface according to the updated parameters fed back by S1417 (shrinking only the VNF instance).

S1419, the VIM performs a resource allocation change request and an internal connection adjustment/deletion request.

a) When shrinking a shared VNF instance or a proprietary VNF instance:

b) When terminating the VNF instance:

S1420: If the terminated VNF instance is a slice sharing common network function, the VIM is also required to delete the network connection between the VNF instance and the associated NSI network function and release the corresponding resource.

On S1421, the VIM returns to the NSM&O feedback resource allocation and network connection configuration through the NG2 interface. NSM&O passes this information to the VNFM through the NG1 interface only when shrinking the VNF instance.

S1422, the VNFM adjusts the VNF life cycle parameters and deployment parameters only when the VNF instance is shrunk.

S1423, only when the VNF instance is shrunk, the VNFM feeds back to the NSM&O through the NG2 interface that the VNF instance shrinks.

S1424, only when shrinking the VNF instance, NSM&O adjusts the contracted VNF application parameters, such as execution function and operational strategy adjustment, by EM.

S1425, NSM&O updates the VNF/PNF information of the target NSI in the memory slice instance memory. If the shared function is shrunk, the VNF/PNF information in the associated NSI is updated at the same time.

S1426, if the slice instance shrink request is sent by the sender, the slice instance is successfully fed back to the sender.

The method for shrinking NSI provided by the present application retains the existing network management system, and adopts an independent network management system for the network slicing service, and supports direct management of physical network functions and virtual network functions, and supports the network under the system architecture. The shrinking of the slice instance is an important part of the network slice lifecycle management. This application allows the device vendor or the authorized network segment instance. The third-party tenant can shrink the network slice instance as needed when the performance is excessive, or automatically shrink when the slice instance has excessive performance according to the policy, which reduces the operation and maintenance cost and saves resource overhead. In addition, the present application manages the common network functions shared by other slice instances in the network slice instance and the slice-specific network functions, so that the shrinkage of the shared network function can benefit the multi-slice instance. The present application differentially manages the common network functions shared by other slice instances in the network slice instance and the slice-specific network functions, so that the shrinkage of the shared network function does not adversely affect the services provided by other slice instances.

The foregoing embodiment mainly introduces the solution of the present application from the perspective of interaction between the network elements. It can be understood that each network element, such as NSM&O, management device, etc., in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A skilled person can use different methods to implement the described functionality for each particular application, but such implementation should not be considered beyond the scope of this application.

The application may divide the functional units of the NSM&O, the management device (for example, EM, VNFM, or NFVO) according to the above method examples. For example, each functional unit may be divided according to each function, or two or more functions may be integrated. In one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

In the case of employing an integrated unit, FIG. 15 shows a possible structural diagram of the NSM&O involved in the above embodiment. The NSM&O 1500 includes a processing unit 1502 and a communication unit 1503. The processing unit 1502 is configured to perform control management on the actions of the NSM&O 1500. For example, the processing unit 1502 is configured to support the NSM&O 1500 to execute S1020 of FIG. 10, and the processing unit 1502 may further be configured to support the NSM&O 1500 to execute S1103 of FIG. 11, and/or for use in this document. Other processes of the described technology. Communication unit 1503 is used to support communication between NSM&O 1500 and other network entities, such as communication with the EM shown in FIG. The NSM&O 1500 may also include a storage unit 1501 for storing program code and data of the NSM&O 1500.

The processing unit 1502 may be a processor or a controller, such as a CPU, a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and field programmable. Field programmable gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 1503 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces. The storage unit 1501 may be a memory.

When the processing unit 1502 is a processor, the communication unit 1503 is a communication interface, and the storage unit 1501 is a memory, the NSM&O referred to in the present application may be the NSM&O shown in FIG. 16.

Referring to FIG. 16, the NSM&O 1610 includes a processor 1612, a communication interface 1613, and a memory 1611. The communication interface 1613, the processor 1612, and the memory 1611 can communicate with each other through an internal connection path to transfer control and/or data signals.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

Therefore, the NSM&O provided by the present application can simultaneously manage physical and virtual network functions/resources to implement network slicing, shorten network deployment time, and save deployment costs. And when shrinking NSI, by treating the common network function and the dedicated network function differently, it is avoided to affect the services that other slice instances are providing when shrinking the general network function.

In the case of employing an integrated unit, FIG. 17 shows a possible structural diagram of the management device involved in the above embodiment. The management device 1700 includes a processing unit 1702 and a communication unit 1703. The processing unit 1702 is configured to perform control management on the action of the management device 1700. For example, the processing unit 1702 is configured to support the management device 1700 to execute S730 of FIG. 7. The processing unit 1702 is further configured to support the management device 1700 to execute S1106 of FIG. 11, and / or other processes for the techniques described herein. The communication unit 1703 is for supporting communication between the management device 1700 and other network entities, such as the communication with the NSM&O shown in FIG. The management device 1700 may further include a storage unit 1701 for storing program codes and data of the management device 1700.

The processing unit 1702 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 1703 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces. The storage unit 1701 may be a memory.

When the processing unit 1702 is a processor, the communication unit 1703 is a communication interface, and the storage unit 1701 is a memory, the management device involved in the present application may be the management device shown in FIG. 18.

Referring to FIG. 18, the management device 1810 includes a processor 1812, a communication interface 1813, and a memory 1811. The communication interface 1813, the processor 1812, and the memory 1811 can communicate with each other through an internal connection path to transfer control and/or data signals.

Therefore, the management device provided by the present application manages the NSI through the newly designed network architecture, and can perform physical layering and management of physical and virtual network functions/resources at the same time to implement network slicing, which shortens network deployment time and saves deployment costs. And when shrinking the NSI, by distinguishing between the general network function and the dedicated network function, it is possible to avoid affecting the services that other slice instances are providing when shrinking the general network function.

In the present application, the size of the serial number of each process does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the present application.

In addition, the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist at the same time. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

The steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can Stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable Reader memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in an NSM&O or management device. Of course, the processor and the storage medium can also exist as discrete components in the NSM&O or management device.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD), or a semiconductor medium (eg, a solid state disk (SSD)). Wait.

The specific embodiments of the present invention have been described in detail with reference to the specific embodiments of the present application. It is to be understood that the foregoing description is only The scope of protection, any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application are included in the scope of protection of the present application.

Claims

A method for shrinking a network slice instance, comprising:

The first network slice management and orchestrator NSM&O sends a network function shrink request message to the management device, where the first NSM&O is used to manage and arrange the network slice instance NSI, and the management device is configured to manage the target NSI to be contracted. Network function, the network function shrink request message is used to request the management device to perform shrink processing on the network function;

Receiving, by the first NSM&O, a shrink feedback message from the management device, where the shrink feedback message is used by the management device to feed back a result of shrinking processing of the network function;

The first NSM&O updates information of the target NSI stored in the memory according to the shrink feedback message.
The method of claim 1 wherein the method comprises:

The first NSM&O sends the network function shrink request message to the management device when the network function is a dedicated network function of the target NSI; or

The first NSM&O sends the network function contraction to the management device when the network function is a shared network function of the target NSI and an associated NSI, and shrinking the network function does not affect the service of the associated NSI. A request message, wherein the associated NSI is an NSI that uses the network function in conjunction with the target NSI.
The method according to claim 1 or 2, wherein before the first NSM&O sends a network function shrink request message to the management device, the method further includes:

The first NSM&O acquires an NSI shrink request message, where the NSI shrink request message includes identification information of the target NSI, and the NSI shrink request message is used to request the first NSM&O to perform shrink processing on the target NSI. ;

Determining, by the first NSM&O, the network slice template NSLD of the target NSI according to the identifier information;

The first NSM&O determines the network function according to the NSLD.
The method according to claim 3, wherein, after the first NSM&O acquires the NSI shrink request message, and the first NSM&O sends the network function shrink request message to the management device, the method further includes:

The first NSM&O sends a notification message to the network manager NM, where the notification message is used to notify the NM that the first NSM&O needs to perform a shrinking process on the network function;

The first NSM&O receives an acknowledgment message from the NM, where the acknowledgment message is used to instruct the first NSM&O to perform a shrinking process on the network function.
The method according to any one of claims 1 to 4, wherein after the first NSM&O receives the shrink feedback message from the management device, and the first NSM&O updates the memory in the update according to the feedback message Before the information of the target NSI, the method further includes:

The first NSM&O sends a resource allocation request message to the virtualized infrastructure manager VIM, where the resource allocation request message is used to request the VIM to release the idle resource after the network function shrinks;

Receiving, by the first NSM&O, a resource allocation feedback message from the VIM;

Updating, by the first NSM&O, the information of the target NSI stored in the memory according to the shrinking feedback message includes:

The first NSM&O updates information of the target NSI stored in the memory according to the shrink feedback message and the resource allocation feedback message.
The method according to any one of claims 1 to 5, wherein when the network function is a shared network function, the method further comprises:

The first NSM&O updates information of an associated NSI stored in the memory according to the shrinkback feedback message, the associated NSI being an NSI that uses the shared network function in conjunction with the target NSI.
The method according to any one of claims 3 to 6, wherein the first NSM&O acquires an NSI shrink request message, including:

The first NSM&O acquires the NSI shrink request message sent by the second NSM&O.
A method of shrinking a network slice instance, the method comprising:

The management device receives a network function shrink request message from the network slice management and orchestrator NSM&O, wherein the management device is configured to manage a network function to be contracted of the target network slice instance NSI, and the NSM&O is used to manage the network slice instance NSI And arrangement;

The management device performs a shrinking process on the network function according to the network function shrink request message;

The management device sends a shrink feedback message to the NSM&O, the shrink feedback message being used to feed back a result of the shrinking process of the network function.
The method according to claim 8, wherein the management device comprises a virtual network function manager VNFM, and the network function comprises a first virtual network function VNF instance,

The shrinking process of the network function by the management device according to the network function shrink request message includes:

Performing, by the VNFM, a shrink feasibility check on the first VNF instance according to the network function shrink request message;

The VNFM contracts the first VNF instance upon passing the shrinkability feasibility check.
The method according to claim 8 or 9, wherein the management device comprises a network element manager EM, the network function comprises a second VNF instance, and the second VNF instance is a VNF generated by the network manager NM Example,

The shrink feedback message is used to feed back the service of the second VNF instance has been stopped when the network function request message is used to request to stop the service of the second VNF instance.
An apparatus for shrinking a network slice instance, wherein the apparatus is configured to manage and schedule a network slice instance NSI, the apparatus comprising a processing unit and a communication unit,

The processing unit is configured to send, by the communication unit, a network function shrink request message to a management device, where the management device is configured to manage a network function to be contracted of a target NSI, where the network function shrink request message is used to request the The management device performs a shrinking process on the network function; and is configured to receive, by the communication unit, a shrink feedback message from the management device, the shrink feedback message being used by the management device to feed back a shrinkage process of the network function a result; and information for updating the target NSI stored in the memory according to the shrink feedback message.
The device according to claim 11, wherein the processing unit is specifically configured to:

Sending, by the communication unit, the network function shrink request message to the management device when the network function is a dedicated network function of the target NSI; or

When the network function is a shared network function of the target NSI and the associated NSI, and shrinking the network function does not affect the service of the associated NSI, sending, by the communication unit, the network function contraction to the management device please A message is obtained, wherein the associated NSI is an NSI that uses the network function in conjunction with the target NSI.
The device according to claim 11 or 12, wherein the processing unit is further configured to:

Obtaining an NSI shrink request message, where the NSI shrink request message includes identification information of the target NSI, the NSI shrink request message is used to request the device to perform shrink processing on the target NSI; The identification information determines a network slice template NSLD of the target NSI; and is configured to determine the network function according to the NSLD.
The device according to claim 13, wherein the processing unit is further configured to:

Sending, by the communication unit, a notification message to the network manager NM, the notification message is used to notify the NM that the device needs to perform shrink processing on the network function; and is configured to receive from the NM by the communication unit And a confirmation message, the confirmation message is used to instruct the first NSM&O to perform a shrinking process on the network function.
The device according to any one of claims 11 to 14, wherein the processing unit is further configured to:

Transmitting, by the communication unit, a resource allocation request message to the virtualization infrastructure manager VIM, where the resource allocation request message is used to request the VIM to release the idle resource after the network function shrinks; and for using the communication unit Receiving a resource allocation feedback message from the VIM;

And information for updating the target NSI stored in the memory according to the shrink feedback message and the resource allocation feedback message.
The device according to any one of claims 11 to 15, wherein when the network function is a shared network function, the processing unit is further configured to:

Updating the information of the associated NSI stored in the memory according to the shrinkback feedback message, the associated NSI being an NSI that uses the shared network function in conjunction with the target NSI.
The device according to any one of claims 13 to 16, wherein the processing unit is specifically configured to:

Obtaining the NSI shrink request message sent by the second network slice management and orchestrator NSM&O.
An apparatus for shrinking a network slice instance, wherein the apparatus is configured to manage a network function to be contracted of a target network slice instance NSI, the device comprising a processing unit and a communication unit,

The processing unit is configured to receive, by the communication unit, a network function shrink request message from the network slice management and orchestrator NSM&O; and configured to perform shrink processing on the network function according to the network function shrink request message; The communication unit sends a shrink feedback message to the NSM&O, the shrink feedback message being used to feed back a result of the shrinking process of the network function.
The apparatus according to claim 18, wherein said apparatus comprises a virtual network function manager VNFM, said network function comprising a first virtual network function VNF instance,

The processing unit is specifically configured to:

Performing a shrink feasibility check on the first VNF instance according to the network function shrink request message; and for shrinking the first VNF instance when the shrink feasibility check is acceptable.
The device according to claim 18 or 19, wherein the management device comprises a network element manager EM, the network function comprises a second VNF instance, and the second VNF instance is a VNF generated by the network manager NM Example,

The shrink feedback message is used to feed back the service of the second VNF instance has been stopped when the network function request message is used to request to stop the service of the second VNF instance.
A method for shrinking a network slice, comprising:

The cross-device network slice management and orchestrator NSM&O sends a first request message to the first domain NSM&O, the first request message is used to request the first domain NSM&O to shrink the first sub-network slice instance, the first domain NSM&O For managing and orchestrating the first sub-network slice instance;

The cross-device vendor NSM&O receives a first shrink complete message from the first domain NSM&O.
The method of claim 21 wherein

The method further includes:

The inter-device NSM&O sends a second request message to the second domain NSM&O, where the second request message is used to request the second domain NSM&O to shrink the second sub-network slice instance, where the second domain NSM&O is used for management and Arranging the second sub-network slice instance;

The cross-device vendor NSM&O receives a second shrink complete message from the second domain NSM&O.
The method according to claim 21 or 22, wherein before the sending the first request message to the first domain NSM&O by the inter-device network slice management and orchestrator NSM&O, the method further includes:

The cross-device vendor NSM&O decomposes the network slice instance into the plurality of sub-network slice instances.
A method for shrinking a network slice, comprising:

The first domain network slice management and orchestrator NSM&O receives a first request message from the cross-device NSM&O, the first request message is used to request the first domain NSM&O to shrink the first sub-network slice instance;

The first domain NSM&O shrinks the first sub-network slice instance;

The first domain NSM&O sends a first shrink complete message to the cross-device vendor NSM&O.
A method for shrinking a network slice, comprising:

The second domain network slice management and orchestrator NSM&O receives a second request message from the cross-device NSM&O, the second request message is used to request the second domain NSM&O to shrink the second sub-network slice instance;

The second domain NSM&O shrinks the second sub-network slice instance;

The second domain NSM&O sends a second shrink complete message to the cross-device vendor NSM&O.
A network slice management and orchestrator NSM&O management device, comprising:

transceiver,

a memory for storing instructions;

The processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:

Sending a first request message to the first domain NSM&O, the first request message is used to request the first domain NSM&O to shrink the first sub-network slice instance, where the first domain NSM&O is used to manage and arrange the first sub- Network slice instance;

A first shrink complete message from the first domain NSM&O is received.
The NSM&O management device according to claim 26, wherein the processor is further configured to perform the following steps:

Sending a second request message to the second domain NSM&O, the second request message is used to request the second domain NSM&O to shrink the second sub-network slice instance, where the second domain NSM&O is used to manage and arrange the second sub- Network slice instance;

A second shrink complete message from the second domain NSM&O is received.
The NSM&O management device according to claim 26 or 27, wherein the processor is further configured to perform the following steps:

Decomposing the network slice instance into the plurality of sub-network slice instances.
A network slice management and orchestrator NSM&O, characterized in that it comprises:

transceiver,

a memory for storing instructions;

The processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:

Receiving a first request message from the cross-device NSM&O, the first request message is used to request the NSM&O to shrink the first sub-network slice instance;

Shrinking the first sub-network slice instance;

Sending a first shrink complete message to the cross-device vendor NSM&O.
A network slice management and orchestrator NSM&O, characterized in that it comprises:

transceiver,

a memory for storing instructions;

The processor is coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:

Receiving a second request message from the cross-device NSM&O, the second request message is used to request the NSM&O to shrink the second sub-network slice instance;

Shrinking the second sub-network slice instance;

Sending a second shrink complete message to the cross-device vendor NSM&O.