CN108024256B

CN108024256B - Method, device and system for shrinking network slice example

Info

Publication number: CN108024256B
Application number: CN201610974261.2A
Authority: CN
Inventors: 陆伟; 杨水根; 孙文琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-11-03
Filing date: 2016-11-03
Publication date: 2020-04-03
Anticipated expiration: 2036-11-03
Also published as: WO2018082545A1; CN108024256A

Abstract

The embodiment of the invention discloses a method for contracting network slice instance NSI, which comprises the following steps: a first network slice management and orchestrator NSM & O sends a network function contraction 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 network functions to be contracted of target NSIs; receiving a contraction feedback message from the management device; and updating the information of the target NSI stored in the memory according to the contraction feedback message. According to the NSI contraction method provided by the embodiment of the invention, the physical and virtual network functions/resources can be arranged and managed at the same time to realize network slicing, the network deployment time is shortened, the deployment cost is saved, and in the NSI contraction process, the influence on the services provided by other slicing instances is avoided by processing the general network function and the special network function differently.

Description

Method, device and system for shrinking network slice example

Technical Field

The embodiment of the invention relates to the field of communication, in particular to a method, a device and a system for shrinking a network slice example.

Background

With the rapid development of mobile communication, digital transformation has involved almost all the conventional industries. However, the conventional cellular network architecture can only provide uniform network services, and it is difficult to satisfy the very different communication requirements, including functional differences and performance differences, caused by the digitalized transition wave. In next generation mobile networks, the network will be abstracted as "network slice (NetworkSlice)".

Although network function virtualization is a key enabling technology for reducing the complexity and cost of network slice implementation, physical network elements and virtualized network elements will coexist for a long time and jointly flexibly constitute a network slice for the purposes of reducing deployment cost and reclaiming investment. Therefore, in order to quickly and flexibly provide differentiated communication requirements, operators need an automatic slicing operation and maintenance system capable of simultaneously managing and arranging Physical Network Functions (PNF) and Virtual Network Functions (VNF), and can realize arranging and managing Physical and virtual Network functions/resources to realize Network slicing.

Currently, neither Network Function Virtualization Orchestrator (NFVO) in a Management and organization (MANO) architecture nor Network Manager (NM) in a 3rd Generation Partnership Project (3 GPP) architecture can manage physical and virtual Network functions/resources simultaneously to implement Network slicing.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, and a system for shrinking a Network Slice Instance (NSI), where the NSI is managed by a newly designed Network architecture, so that physical and virtual Network functions/resources can be arranged and managed at the same time to implement Network slicing, thereby shortening Network deployment time and saving deployment cost. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

In one aspect, a method of contracting an NSI is provided, the method comprising: a first network slice management and orchestrator NSM & O sends a network function contraction request message to a management device, wherein the first NSM & O is used for managing and orchestrating a network slice instance NSI, the management device is used for managing a network function to be contracted of a target NSI, and the network function contraction request message is used for requesting the management device to perform contraction processing on the network function; the first NSM & O receives a contraction feedback message from the management device, wherein the contraction feedback message is used for the management device to feed back a result of contraction processing of the network function; the first NSM & O updates information of the target NSI stored in memory according to the shrink feedback message.

Therefore, the method for shrinking the NSI according to the embodiment of the present invention manages the NSI through the newly designed network architecture, and can simultaneously perform arrangement management on physical and virtual network functions/resources to implement network slicing, thereby shortening the network deployment time and saving the deployment cost. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

Optionally, the method specifically includes: the first NSM & O sends the network function contraction request message to the management device when the network function is the exclusive network function of the target NSI; or the first NSM & O sends the network function contraction request message to the management device when the network function is a shared network function of the target NSI and an associated NSI, and the network function is contracted without affecting the service of the associated NSI, wherein the associated NSI is an NSI that uses the network function together with the target NSI.

In the method for contracting the NSI provided by the embodiment of the invention, before the network function contraction request message is sent, different preprocessing modes are adopted for the shared network function and the dedicated network function, so that the service provided by other NSIs sharing the shared network function is not negatively influenced when the shared network function is contracted.

Optionally, before the first NSM & O sends the network function contraction request message to the management device, the method further includes: the first NSM & O obtaining an NSI shrink request message, wherein the NSI shrink request message comprises identification information of the target NSI, and the NSI shrink request message is used for requesting the first NSM & O to shrink the target NSI; the first NSM & O determines a network slice template NSLD of the target NSI according to the identification information; the first NSM & O determines the network function from the NSLD.

According to the method for shrinking the NSI provided by the embodiment of the invention, the first NSM & O can flexibly determine to shrink the target NSI according to the actual situation. When the operator or an authorized third-party tenant of the network slice instance finds that the performance of the existing NSI is excessive, the NSI is contracted as required, or when the performance of the NSI is excessive according to a strategy, the NSI is automatically contracted, and the operation and maintenance cost is reduced.

Optionally, after the first NSM & O obtains the NSI contraction request message and before the first NSM & O sends the network function contraction request message to the management device, the method further includes: the first NSM & O sends a notification message to a Network Manager (NM), wherein the notification message is used for notifying the NM that the first NSM & O needs to perform contraction processing on the network function; the first NSM & O receives an acknowledgement message from the NM instructing the first NSM & O to shrink the network function.

In the embodiment of the invention, the network management architecture comprises NM, the first NSM & O sends a notification message to NM before the network function to be contracted is contracted, the NM is notified that the first NSM & O needs to contract the network function, and the contraction of the network function is determined according to the confirmation message sent by NM, thereby avoiding the conflict generated when NM and NSM & O simultaneously configure the network function.

Optionally, after the first NSM & O receives a 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 sends a resource allocation request message to a Virtual Infrastructure Manager (VIM), wherein the resource allocation request message is used for requesting the VIM to release idle resources after the network function is contracted; the first NSM & O receiving a resource allocation feedback message from the VIM; the updating, by the first NSM & O, the information of the target NSI stored in memory according to the shrink feedback message includes: the first NSM & O updates information of the target NSI stored in the memory according to the contraction feedback message and the resource allocation feedback message.

According to the method for contracting the NSI provided by the embodiment of the invention, the first NSM & O requests the VIM to release the idle resources after VNF contraction by sending the resource allocation request message to the VIM, thereby improving the resource utilization rate.

Optionally, when the network function is a shared network function, the method further includes: the first NSM & O updates information of an associated NSI stored in the memory according to the shrink feedback message, the associated NSI being an NSI that uses the shared network function in common with the target NSI. So that the synchronization of information in the system can be maintained.

Optionally, the acquiring, by the first NSM & O, an NSI contraction request message includes: the first NSM & O obtains the NSI shrink request message sent by the second NSM & O.

The NSI shrinking method provided by the embodiment of the invention determines the shrinkage of the target NSI through the NSM & O with the hierarchical structure, and can flexibly manage a multi-domain and multi-vendor network.

In another aspect, a method of contracting an NSI is provided, the method comprising: receiving a network function contraction request message from a network slice management and orchestrator NSM & O by a management device, wherein the management device is used for managing network functions to be contracted of a target network slice instance NSI, and the NSM & O is used for managing and orchestrating the network slice instance NSI; the management equipment shrinks the network function according to the network function shrinking request message; and the management equipment sends a contraction feedback message to the NSM & O, wherein the contraction feedback message is used for feeding back the result of the contraction processing of the network function.

The NSI contracting method provided by the embodiment of the invention manages the NSI through the newly designed network architecture, can simultaneously perform arrangement management on physical and virtual network functions/resources to realize network slicing, shortens the network deployment time and saves the deployment cost. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

Optionally, the managing device includes a virtual network function manager VNFM, the network function includes a first virtual network function VNF instance, and the contracting, by the managing device, the network function according to the network function contraction request message includes: the 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 passes.

According to the method for shrinking the NSI provided by the embodiment of the invention, the feasibility of shrinking the VNF instance to be shrunk is checked through the VNFM, so that the VNF instance can be correctly shrunk.

Optionally, the management apparatus includes a network element manager EM, the network function includes a second VNF instance, the second VNF instance is a VNF instance generated by a network manager NM, and the shrink feedback message is used to feed back that the service of the second VNF instance has been stopped when the network function request message is used to request that the service of the second VNF instance is stopped.

In the method for shrinking the NSI according to the embodiment of the present invention, whether the VNF instance to be shrunk can be shrunk is determined by checking the attribute of the VNF instance to be shrunk through the NSM & O, so that an error occurring when the NSM & O shrinks the VNF instance generated by the NM is avoided.

In another aspect, an embodiment of the present invention provides an NSM & O, where the NSM & O may implement a function executed by the NSM & O in the method according to the above aspect, and the function may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

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

In another aspect, an embodiment of the present invention provides a management device, where the management device may implement a function executed by the management device in the method in the foregoing aspect, where the function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

In one possible design, the management device includes a processor and a communication interface, and the processor is configured to support the management device to execute the corresponding functions of the method. The communication interface is used for supporting communication between the management device and other network elements. The management device may also include a memory, coupled to the processor, that stores program instructions and data necessary for the management device.

In a possible design, the management device may be an element manager EM, a virtual network function manager VNFM, or a virtual network function orchestrator NFVO.

In still another aspect, an embodiment of the present invention provides a communication system, where the system includes the NSM & O and the management device described in the above aspect.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the NSM & O, which includes a program designed to execute the above aspects.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the management device, which includes a program designed to execute the above aspects.

Compared with the prior art, according to the method, the device and the system for shrinking the NSI provided by the embodiment of the invention, the NSI is managed through a newly designed network architecture, physical and virtual network functions/resources can be arranged and managed at the same time to realize network slicing, the network deployment time is shortened, and the deployment cost is saved. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

Drawings

FIG. 1 is a diagram of a prior art network management architecture;

FIG. 2 is a schematic diagram of an NSM & O architecture according to an embodiment of the present invention;

FIG. 3 is a diagram of a network management architecture according to an embodiment of the present invention;

FIG. 4 is a diagram of another network management architecture applied in the embodiment of the present invention;

FIG. 5 is a diagram of another network management architecture according to an embodiment of the present invention;

FIG. 6 is a diagram of another network management architecture according to an embodiment of the present invention;

FIG. 7 is a schematic flow chart diagram of a method for shrinking NSI provided by an embodiment of the present invention;

FIG. 8 is a schematic architecture diagram of a hierarchical NSM & O according to an embodiment of the present invention;

FIG. 9 is a schematic flow chart diagram of a method for contracting NSI for a hierarchical NSM & O according to an embodiment of the present invention;

FIG. 10 is a schematic flow chart diagram of another method for shrinking NSI provided by an embodiment of the present invention;

FIG. 11 is a schematic flow chart diagram of yet another method for NSI shrinkage provided by an embodiment of the present invention;

FIG. 12 is a schematic flow chart diagram of yet another method for NSI shrinkage provided by an embodiment of the present invention;

FIG. 13 is a schematic flow chart diagram of yet another method for NSI shrinkage provided by an embodiment of the present invention;

FIG. 14 is a schematic flow chart diagram of yet another method for NSI shrinkage provided by an embodiment of the present invention;

FIG. 15A is a schematic diagram of a possible NSM & O structure provided by an embodiment of the present invention;

FIG. 15B is a schematic diagram of another possible NSM & O configuration provided by an embodiment of the present invention;

fig. 16A is a schematic structural diagram of a possible management device according to an embodiment of the present invention;

fig. 16B is a schematic structural diagram of another possible management device according to an embodiment of the present invention.

Detailed Description

The embodiment of the invention relates to a network slicing technology. The network slicing technology is used for logically abstracting a network into one or more mutually isolated network slices, wherein each network slice comprises a series of logical network functions and purposefully meets the differentiated requirements of different service types. For example, in The fifth Generation mobile communication (The 5th Generation, abbreviated as "5G") network, network slicing is an on-demand networking method, and brings new services to operators, which can be adjusted according to changing user requirements and quickly meet new application requirements.

The network slicing technology abstracts 5G network physical infrastructure resources into a plurality of independent parallel NSIs according to scene requirements. And each NSI carries out customized cutting of network functions and arrangement management of corresponding network functions according to the requirements of the service scenes and the service models. An NSI can be viewed as an instantiated 5G network. Such a network structure allows an operator to provide a network as a service to users, and can freely combine physical networks according to the indexes of rate, capacity, coverage, delay, reliability, security, availability, and the like, so as to meet the requirements of different users.

In the network slicing technique, when an operator or a tenant finds that the performance of the NSI is excessive, the NSI needs to be shrunk. Shrinking the NSI involves configuring the PNF, releasing resources such as computation, storage, network, etc. of the VNF, and terminating the VNF, etc.

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.

The network architecture and the service scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not limit the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

It should be noted that the terms "network management architecture", "network system", "system", etc. may be used interchangeably herein. Furthermore, for the convenience of description, the terms "VNF instance" and "VNF" may be replaced with each other, and the specific meaning thereof should be determined by the meaning of the statement in which the term is located, and should not be construed as limiting the embodiments of the present invention. To facilitate understanding, some terms appearing herein are introduced.

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

Network Slice template (Network Slice Descriptor, NSLD): the network slice is used for describing the constituent elements (such as network functions, resource requirements and the like) and the relationships thereof (such as network function organization architecture, network functions/resource configuration, workflow between network functions and the like). It should be understood that NSLD is only one concept defined to describe the above-mentioned features of the network slice, and should not be construed as limiting the applicable scope of the embodiments of the present invention, and other concepts described above for describing the network slice are applicable to the embodiments of the present invention.

NSI: one example created to implement the function of network slicing may be created according to NSLD, or may be created according to other ways, and the NSI may satisfy different Communication requirements, for example, MBB (Mobile Broadband) network slicing, Massive MTC (Machine Type Communication) network slicing, Critical MTC network slicing, and so on.

Network function: the network function can be realized as a special hardware, can be realized by running software on the special hardware, and can also be realized in a virtual function mode on a general hardware platform. Thus, from an implementation perspective, network functions may be divided into PNFs and VNFs. From the perspective of usage, the network functions may be divided into an exclusive network function and a shared network function, and specifically, for a plurality of network slice instances, different network functions may be independently used, such a network function is referred to as an exclusive network function, and may also share the same network function, such a network function is referred to as a shared network function.

To facilitate understanding of the embodiments of the present invention, a 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 merges MANO architectures. Specifically, the network management architecture 100 includes both modules that manage PNFs and modules that manage VNFs. The modules in network management architecture 100 are described in turn below.

PNF: is a physical device that provides fixed network functionality. For example, the physical network function module may be a network element NE in a conventional 3GPP network management architecture, that is, a physical network element. For example, the NE may be a base station, a Mobility Management Entity (MME), a Serving Gateway (SGW), or the like.

VNF: may be the smallest virtual unit that can be monitored and managed in the network management architecture. A communication interface exists between the VNF and a Network Function Virtual Infrastructure (NFVI) described below. The VNF module may create a virtual network function and perform some parameter configuration on the basis of the NFVI, so as to implement a certain network function.

Network Element (NE): is the smallest physical unit that can be monitored and managed in a network management architecture. For example, the NE may be a base station or a Mobility Management Entity (MME), and may also be referred to as a PNF module.

Element Manager (Element Manager, EM): a network module for managing network elements. EM may be used to manage both PNF modules and VNFs.

Domain Manager (Domain Manager, DM): and the management system module is one level larger than the management range of the EM. The DM may manage one or more EMs, for example, the DM may 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 device, for example, EM manages a series of base stations, DM manages a network device belonging to an operator (in english: a vendor), provides domain management function, and DM has a larger management range than EM. Typically, EM devices are used to perform the configuration of network functions. But the present embodiment does not exclude the possibility that the DM performs the process performed by the EM.

NM: the management module of the network layer mainly provides the network management function and the related functions of the exchange between the management devices and the like. For example, a NM may be responsible for the distribution, configuration, control, monitoring, etc., of network resources, with the NM being supported by an EM or DM.

NFVI: the hardware and virtual resources for the whole system to run are provided and consist of hardware resources (including three parts of computation, network and storage), a virtualization layer (for virtualizing the hardware resources into a resource pool) and virtual resources (also divided into three parts of computation, network and storage). From the VNF perspective, the virtualization layer and hardware resources appear to be one entity that can provide the required virtual resources.

NFV-MANO (Network Functions Virtualization-Management and organization) System Module: there are interfaces between it and NFVI, VNF, EM and NM for managing virtual network functions at the network level, including the following three modules:

NFVO: the method is used for realizing the life cycle management of network services and VNFs, and optimizing network resources from the global angle of NFVI.

Virtual Network Function management module (VNFM): lifecycle management of VNF instances now includes initialization of VNF instances, expansion or contraction of VNF instances, and termination of VNF instances. .

Virtualized Infrastructure Manager (VIM): interfaces exist between the network management function and the network management function (NFVI) and between the network management function and the network management function (VNF), the interfaces are used for management, monitoring and fault reporting of hardware resources and virtualized resources of an infrastructure layer, and a virtualized resource pool is provided for upper-layer application.

As can be seen from the above description of the network management architecture 100 in the prior art, the network management architecture in the prior art can manage the physical network function and the virtual network function. It does not enable management and orchestration of network slices. Therefore, the network management architecture in the prior art cannot meet the requirements of the application of the network slicing technology in the future communication system, i.e. the network slices cannot be managed and arranged flexibly. In the prior art, in order to reduce the deployment cost, the physical network element and the virtualized network element coexist for a long time and flexibly form a network slice. Therefore, there is a need for a network management system that can perform orchestration and management of physical network functions or network resources and virtual network functions or network resources to implement network slice applications.

The central idea of the embodiment of the present invention is to introduce a Network Slice Manager and organizer (NSM & O for short) into the Network management architecture 100, and manage the shrinkage process of the NSI through the NSM & O, so as to implement the automatic shrinkage of the NSI and improve the efficiency of managing the NSI. It should be understood that NSM & O is only one concept defined for describing a "means for implementing orchestration and management of physical network functions or network resources and virtual network functions or network resources", and should not be construed as limiting the scope of applicability of the embodiments of the present invention, and other concepts for describing a "means for implementing orchestration and management of physical network functions or network resources and virtual network functions or network resources" are applicable to the embodiments of the present invention.

The following describes a network management architecture of an embodiment of the present invention. The embodiment of the invention introduces NSM & O on the basis of the existing network management architecture 100. The structural schematic diagram of the NSM & O is shown in fig. 2, and the main functions thereof include:

service conversion: the service description information transmitted by the sending-end device is received through an interface (e.g., Application Programming Interface (API)), and is converted into a requirement for the network.

Designing a network slice: the composition of the network slice is described according to the result of the service conversion. For example, a Network Slice template (NSLD) may be designed.

Network slice management policy: and designing a management strategy of the network slice. For example, On-boarding, Instantiation, contraction and expansion (Scaling), Update (Update), Termination, and Deletion (Deletion).

Network slicing and arranging: for specifically determining the network functions and network resources used by the network slice instance.

Monitoring: for detecting and reporting status parameters of network slice instances. For example, Key Performance Indicators (KPIs) parameters of a network slice instance may be monitored.

The sending end device is a device that sends a request to the NSM & O. For example, the sending end device may be an operator, a third party client, an application involved in the communication service, or any other entity device that may send a request to the NSM & O.

Optionally, the network management architecture in the embodiment of the present invention may further include a storage device, and the storage device may be configured to record information of the generated network slice instance.

Fig. 3 to fig. 6 respectively describe four network management architectures applied in the embodiment of the present invention. The four network management architectures include NSM & O. For ease of distinction, the network management architectures of fig. 3-6 are referred to hereinafter in the order of network management architecture 200, network management architecture 300, network management architecture 400, and network management architecture 500.

Fig. 3 illustrates a network management architecture 200 to which an embodiment of the present invention is applied. As shown in fig. 3, the network management architecture 200 is a network management architecture enhanced and modified on the basis of the network management architecture 100. Where the network management architecture 200 does not contain a NM, the NSM & O performs the function of the NM in the network management architecture 100. In other words, the NSM & O may include all functions of the NM in addition to the functions illustrated in fig. 2. The NSM & O can interact with the EM through a communication interface to realize the management of the network function corresponding to the NSI. Wherein the management of network functions includes management of PNFs and management of VNFs. The NSM & O may also receive VNF status information from the NFVO over the communication interface and send instructions to the NFVO over the communication interface.

For the network management architecture 200, the NSM & O can directly manage the PNF, and can implement resource orchestration management on the NFVI and VNF generation using the NFVO.

Fig. 4 illustrates another network management architecture 300 to which embodiments of the present invention are applied. As shown in fig. 4, the network management architecture 300 is also a network management architecture enhanced and modified on the basis of 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 NFVO entities. The function of NFVO is performed by NSM & O. In other words, the functionality of NSM & O also includes orchestration management of virtual network resources and VNF lifecycle management. There is a communication interface between the NSM & O and the VNFM. In fig. 4, this interface may be referred to as the NG1 interface. There is a communication interface between NSM & O and VIM. In fig. 4, this interface may be referred to as the NG2 interface.

Wherein the NSM & O and VNFM may interact through the NG1 interface as follows: the authorization, reservation, allocation, release and the like of NFVI resources made by the VNF are supported; querying information of the running state, such as VNF instance queries; VNF initialization update, scaling, termination, etc.; VNF related events, status information, etc. are transmitted.

NSM & O and VIM may interact through the NG2 interface as follows: NFVI resource reservation, allocation, release, etc.; VNF software image (image) add, delete, update, etc.; configuration information, events, measurements, upgrade records, etc. related to the NFVI are transmitted.

For the network management architecture 300, the NSM & O may manage the VNF and VNF lifecycle in addition to being able to directly manage the PNF. Therefore, physical and virtual network resources and functions can be uniformly managed and arranged, and resource optimization from the perspective of global situation is facilitated.

Fig. 5 illustrates another network management architecture 400 to which embodiments of the present invention are applied. As shown in fig. 5, the NM is maintained in the network management architecture 400, and the NSM & O is independent of the NM. Also, there is a communication interface between NSM & O and NM. In fig. 5, this communication interface may be referred to as the NG3 interface. There is also a communication interface between NSM & O and NFVO. In fig. 5, this communication interface may be referred to as the NG4 interface. There is also a communication interface between NSM & O and EM. In fig. 5, this communication interface may be referred to as the NG5 interface.

Wherein, NSM & O and NM can interact with each other through NG 3: transmitting negotiation information between the NSM & O and the NM, for example, the NSM & O inquires the VNF generated by the NM; NM feeds back the generated VNF information to NSM & O and confirms that NSM & O is allowed to modify the VNF information; NSM & O informs the NM which PNF/VNF to modify; the NSM & O informs the NM of the specific modifications to the PNF/VNF.

The following interactions between NSM & O and NFVO may be made over the NG4 interface: NSM & O participates in the lifecycle management of VNFs through the NG4 interface, for example, notifies NFVO to generate, update, delete a VNF, etc.; NSM & O inquires operation information of VNF and NFVI from NFVO; the NFVO feeds back operation information of VNF and NFVI to the NSM & O; policy management, the NSM & O may send a policy to the NFVO indicating the need for VNF deployment; NSM & O VNF package (package) management through NG4 interface.

The following interactions between NSM & O and EM may be made over the NG5 interface: the NSM & O communicates with the EM over the NG5 interface to manage the PNF and VNF (if the EM supports management of the VNF).

For the network management architecture 400, the NSM & O employs a new communication interface to interact with each entity module in the prior art. NSM & O may orchestrate and manage virtual resources through NFVO and lifecycle management of VNFs both NSM & O and NM may directly manage PNFs. And both NSM & O and NM can manage VNF through NFVO or EM. Thus, for the management of PNF and VNF, the NSM & O and NM may be coordinated through communication.

Fig. 6 illustrates another network management architecture 500 to which embodiments of the present invention are applied. As shown in fig. 6, the NM is also maintained 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: entities of the NF are not included in the network management architecture 500. The function of the NFVO module is performed by NSM & O. In other words, the functionality of NSM & O also includes orchestration management of virtual network resources and VNF lifecycle management. Wherein a communication interface exists between the NSM & O and the VNFM. In fig. 6, this communication interface may be referred to as the NG1 interface. There is a communication interface between NSM & O and VIM. In fig. 6, this communication interface may be referred to as the NG2 interface. There is a communication interface between NSM & O and EM. In fig. 6, this communication interface may be referred to as the NG5 interface. The specific functions of the NG1 interface, the NG2 interface, and the NG5 interface can be referred to the same or similar contents in fig. 4 and fig. 5. For brevity, no further description is provided herein.

For the network management architecture 500, the NSM & O employs a new communication interface to interact with each entity module in the prior art. NSM & O may orchestrate and manage virtual resources through NFVO and participate in lifecycle management for VNFs, both NSM & O and NM may directly manage PNFs. Thus, for management of PNF, coordination between NSM & O and NM may be through communication. And since the NSM & O incorporates the functionality of the NFVO, the NSM & O can also directly orchestrate the management of virtual network resources and participate in the lifecycle management of the VNF. The NM is then unable to manage the virtual network resources and VNF.

Those skilled in the art will appreciate that the examples of fig. 3-6 are merely provided to assist those skilled in the art in understanding embodiments of the present invention, and are not intended to limit embodiments of the present invention to the specific values or specific contexts illustrated. It will be apparent to those skilled in the art that various equivalent modifications or variations are possible in light of the examples given in figures 3 through 6, and such modifications or variations are intended to be included within the scope of embodiments of the present invention.

Furthermore, it should be noted that the various functional modules and units introduced above are considered from the point of view of the functions they have. In practical applications, each functional module may exist alone physically, or two or more devices may be integrated into one unit, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present disclosure, and these modifications or substitutions should be covered by the protection scope of the present disclosure.

The method for NSI contraction according to the embodiments of the present invention will be described in detail below with reference to the network management architectures 200 to 500.

Fig. 7 illustrates a method for shrinking an NSI according to an embodiment of the present invention. As shown in fig. 7, the method 700 includes:

s710, a first NSM & O sends a network function contraction request message to a management device, where the first NSM & O is used to manage and organize an NSI, the management device is used to manage a network function to be contracted of a target NSI, and the network function contraction request message is used to request the management device to perform contraction processing on the network function.

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

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

In this embodiment of the present invention, the first NSM & O is configured to manage and orchestrate an NSI (e.g., a target NSI), and the management device is a device configured to manage a network function to be contracted of the target NSI, where the management device may be an EM, a VNFM, or an NFVO. It should be understood that a network function may include multiple PNFs or multiple VNFs, and thus, the contraction of the network function includes at least one of terminating a PNF, contracting a PNF, terminating a VNF, and contracting a VNF. In addition, the NSI may include multiple network functions, and contracting the NSI may refer to contracting one or more network functions of the NSI. The contents and transmission objects of the network function contraction request message are different according to the difference of the network functions to be contracted. The above cases will be described below.

Case 1

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

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

a) if the PNF is a PNF shared by a plurality of NSIs and the scheduling result is that the PNF is configured to use fewer resources (such as storage resources, usage time of a central processing unit CPU, network bandwidth, etc.) for serving the target NSI and the associated NSI, the content of the first request message allocates the fewer resources for the PNF to serve the target NSI and the associated NSI, and adjusts related operation parameters and policy information, etc. In an embodiment of the present invention, the association NSI is an NSI that uses the network function in common with the target NSI.

b) If the PNF is a PNF shared by multiple NSIs and the scheduling result is that the PNF is stopped providing service for 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 identifiers of the target NSI and the associated NSI, NSI monitoring and reporting information, and the like; ii) deleting relevant operation parameters and strategy information and the like; iii) close network connections to other shared functions or/and target NSI-specific functions, associated NSI-specific functions, etc.

c) If the PNF is a PNF dedicated to the target NSI and the orchestration result is that the existing PNF is configured to use the fewer resource service targets NSI, the content of the first request message sent by the first NSM & O to the EM allocates the fewer resource service targets NSI to the PNF, and adjusts the related operation parameters, the policy information, and the like.

d) If the PNF is a PNF dedicated to the target NSI and the scheduling result is that the PNF stops providing service for 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 relevant parameters of the NSI, such as the identifier of the target NSI, the NSI monitoring and reporting information, and the like; ii) deleting operation parameters and strategy information, and the like; iii) delete network connections to other shared functions or/and target NSI-specific functions.

And after the EM finishes the configuration of the PNF according to the first request message, the EM sends a contraction feedback message to the first NSM & O, and feeds back the result of the contraction processing of the PNF to the first NSM & O.

Case 2

When the network function to be contracted is implemented by the VNF and the result of the orchestration is that the VNF is terminated and the first NSM & O and the VNFM can communicate directly:

the first NSM & O sends a first request message to the EM through the corresponding communication interface, wherein the content of the first request message comprises but is not limited to stopping monitoring the running state of the VNF, and the VNF is deleted from a management object of the EM.

And after the EM executes the termination processing on the VNF according to the first request message, the EM sends a contraction feedback message to the first NSM & O, wherein the contraction feedback message is used for feeding back that the VNF is terminated to the first NSM & O. The first NSM & O, upon receiving the shrink feedback message, instructs the EM to logout/close the VNF virtual port, stopping service.

Subsequently, the first NSM & O sends a notification message to the VNFM terminating the VNF, the content of the notification message including, but not limited to, the identity of the VNF, the terminate command. The VNFM normally closes the VNF according to the notification message and the VNF cooperation.

After the VNF is turned off, the VNFM sends a feedback message (i.e., a shrink feedback message) to the first NSM & O for feeding back that the VNF has been terminated.

Case 3

When the network function to be contracted is implemented by the VNF and the orchestration result is to contract the VNF, and the first NSM & O and the VNFM can communicate directly:

the first NSM & O sends a first request message to the VNFM through the corresponding communication interface, the content of the first request message including, but 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 qualified to contract the VNF, checking whether the contraction parameters meet specifications.

After the VNFM has finished the contraction process on the VNF, a feedback message (i.e. a contraction feedback message) is sent to the first NSM & O, the feedback message comprising information authorizing the start of the VNF lifecycle change (if the contraction feasibility check is qualified), optionally the first request message further comprising the modified parameters and the resources involved in contracting the VNF.

The first NSM & O adjusts the contracted VNF application parameters, such as executive function and operating policy adjustments, through the EM.

Case 4

When the network function to be contracted is implemented by the VNF and the result of the orchestration is that the VNF is terminated and the first NSM & O and the VNFM cannot communicate directly:

Subsequently, the first NSM & O sends a notification message terminating the VNF to the NFVO, the content of the notification message including, but not limited to, the identity of the VNF, a terminating command, a configure network connection request. And the NFVO executes termination processing on the VNF according to the notification message.

After the VNF is terminated, the NFVO sends a feedback message (i.e., a shrink feedback message) to the first NSM & O for feeding back that the VNF is terminated and that the configuration network connection is completed.

Case 5

When the network function to be contracted is implemented by the VNF and the result of the orchestration is to contract the VNF and the first NSM & O and the VNFM cannot communicate directly:

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

The NFVO performs a contraction process on the VNF according to the first request message, e.g. instructs the VNFM to perform a VNF contraction feasibility check, including but not limited to verifying whether the first NSM & O is qualified to contract the VNF, checking whether the contraction parameters comply with the specifications.

After the NFVO completes the contraction process on the VNF, a feedback message (i.e. a contraction feedback message) is sent to the first NSM & O, which feedback message includes information authorizing the start of the VNF lifecycle change (if the contraction feasibility check is qualified).

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

For example, in the above embodiments, the receiving end of the first request message is determined first, and then the content of the first request message is determined according to the attribute of the network function to be contracted.

Optionally, the method 700 specifically includes:

s701, when the network function is the dedicated network function of the target NSI, the first NSM & O sends the network function contraction request message to the management device; or

S702, when the network function is a shared network function of the target NSI and an associated NSI and the network function is contracted without affecting a service of the associated NSI, the first NSM & O sends the network function contraction request message to the management device, where the associated NSI is an NSI that uses the network function together with the target NSI.

If the network function to be contracted is a shared network function of the target NSI and the associated NSI, the first NSM & O determines the operation condition of the associated NSI according to the NSLD of the associated NSI, and judges whether contracting the shared network function can influence the service which is being provided by the associated NSI. The shared network function is not shrunk if the services associated with the NSI are adversely affected. If the network function contraction request message is triggered by a Sender (Sender), the first NSM & O feeds back to the Sender that the network function with contraction is in use and cannot be contracted. The sender may be an authorized third party tenant, an operator, or some application with the authority to contract the network slice instance.

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

Therefore, the method for contracting the NSI according to the embodiment of the present invention employs different preprocessing methods for the shared network function and the dedicated network function before sending the network function contraction request message, so that the shared network function is contracted without negatively affecting services provided by other NSIs sharing the shared network function.

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

s703, the first NSM & O obtaining an NSI contraction request message, where the NSI contraction request message includes identification information of the target NSI, and the NSI contraction request message is used to request the first NSM & O to perform contraction processing on the target NSI;

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

s705, the first NSM & O determines the network function according to the NSLD.

In this embodiment of the present invention, the NSI contraction request message acquired by the first NSM & O may be generated by triggering of a mechanism (for example, a performance management mechanism) inside the first NSM & O, or may be received from the sending end. The NSI contraction request message includes identification information of the target NSI, so that the first NSM & O determines the NSLD of the target NSI according to the identification information, and further determines the network function to be contracted according to the NSLD. If the first NSM & O receives the NSI contraction request message from the sending end, the NSI contraction request message also comprises the identity of the sending end, the service/function description to be contracted and the like.

When the first NSM & O receives the NSI contraction request message from the sender, the first NSM & O may verify the identity of the sender through the memory, and verify the integrity of the parameters in the NSI contraction request message, for example, verify whether the format of the identification information of the target NSI 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 operating conditions, associates the NSLD of the target NSI, and in conjunction with this NSLD, the first NSM & O corresponds these descriptions to the VNF or/and PNF in the target NSI. And if the target NSI does not exist, the first NSM & O feeds back that the target NSI does not exist to the sending end. If the target NSI cannot be shrunk, the first NSM & O feeds back to the sending end that the target NSI cannot be shrunk. And if the target NSI is contractible, the authentication sending end has the authority to contract the target NSI and the VNF and/or PNF corresponding to the target NSI. If the authentication is not passed, the first NSM & O feeds back corresponding error information to the sending end, such as that the sending end has no right to shrink the target NSI, and parameters of a shrink command are wrong.

When the first NSM & O internally triggers the NSI shrink request message, the first NSM & O associates with the NSLD of the target NSI, verifies whether the target NSI is shrinkable, and determines the VNF and/or PNF to be shrunk in the target NSI in combination with the NSLD. If the target NSI is not contractable, the target NSI performance excess or resource utilization rate can be fed back to the operator and/or the tenant renting the network slice instance, and the operator or the tenant determines the next action.

Therefore, according to the method for shrinking the NSI provided by the embodiment of the present invention, the first NSM & O can flexibly determine to shrink the target NSI according to the actual situation. When the operator or an authorized third-party tenant of the network slice instance finds that the performance of the existing NSI is excessive, the NSI is contracted as required, or when the performance of the NSI is excessive according to a strategy, the NSI is automatically contracted, and the operation and maintenance cost is reduced.

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

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

s707, the first NSM & O receives an acknowledgement message from the NM, where the acknowledgement message is used to instruct the first NSM & O to perform contraction processing on the network function.

In the embodiment of the invention, the network management architecture comprises NM, the first NSM & O sends notification message to NM before the network function to be contracted is contracted, the NM is notified that the first NSM & O needs to contract the network function, and the contraction processing of the network function is determined according to the confirmation message sent by NM, thereby ensuring that NM and NSM & O do not generate configuration conflict.

Optionally, after the first NSM & O receives a contraction 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 a 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 contraction;

s722, the first NSM & O receiving a resource allocation feedback message from the VIM;

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

s731, the first NSM & O updates the information of the target NSI stored in the memory according to the contraction feedback message and the resource allocation feedback message.

After the first NSM & O receives the contraction feedback message from the VNFM (optionally, the content of the contraction feedback message includes a parameter updated after the VNF contracts), the first NSM & O sends a resource allocation request message to the VIM, where the resource allocation request message requests the VIM to contract the resource occupied by the VNF, and optionally, the resource allocation request message request is also used for requesting the VIM to adjust the internal network connection of the VNF. If the resource allocation request message requests to contract the existing resources of the VNF, such as reduction of CPU (Central processing Unit) use time, storage resource occupation amount, bandwidth occupation ratio and the like, the VIM does not need to delete the internal network connection of the VNF; if the resource allocation request message requests to delete part of the virtual machines of the VNF, the VIM firstly adjusts or deletes the internal network connection of the VNF, and then deletes the virtual machines and releases resources.

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

And the VIM completes corresponding processing according to the resource allocation request message and then sends a resource allocation feedback message to the first NSM & O, wherein the resource allocation feedback message is used for feeding back that the corresponding resource contraction processing is completed. The first NSM & O updates the information of the target NSI stored in the memory according to the contraction feedback message and the resource allocation feedback message

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

s732, the first NSM & O updating information of an associated NSI stored in the memory according to the contraction feedback message, the associated NSI being an NSI that uses the shared network function in common with the target NSI.

When the contracted network function is a shared network function, the first NSM & O may update information stored in memory associated with the NSI according to the contraction feedback message, e.g., update VNF/PNF information associated with the NSI. So that the synchronization of information in the system can be maintained.

Optionally, the acquiring, by the first NSM & O, an NSI contraction request message includes:

s708, the first NSM & O acquires the NSI contraction request message sent by the second NSM & O.

In an embodiment of the present invention, the first NSM & O may be a module in a hierarchical NSM & O, and the first NSM & O may obtain the NSI shrink request message from a second NSM & O, which is another module in the hierarchical NSM & O.

Fig. 8 shows a schematic block diagram of an NSM & O having a hierarchical structure. As shown in fig. 8, the NSM & O includes a multi-vendor NSM & O (or "cross-device orchestrator" for managing devices of multiple subnet slices or multiple vendors, which is not limited by the embodiment of the present invention) and three domain organizers domain NSM & O. Wherein the multi-vector NSM & O corresponds to the second NSM & O, and the domain NSM & O corresponds to the first NSM & O. The multi-vector NSM & O acts as a master control orchestrator, managing each domain NSM & O. For example, a network slice instance may consist of a core network sub-slice instance, an access network sub-slice instance, where there is a multi-sender NSM & O responsible for overall network slice instance management and two domain NSM & O managing the core network sub-slice instance and the access network sub-slice instance separately; alternatively, a network slice instance may be divided into sub-slice instances provided by a plurality of different operator devices, each sub-slice instance is composed of devices of a device provider, for example, a network slice instance of a certain operator is responsible for overall management by a multi-vendor NSM & O, and domain NSM & O provided by a plurality of device providers manage devices provided by the device provider. The description of the sub-slice instance is similar to that of the whole slice instance, and the information of the sub-slice instance may include network functions, connection relationships between the network functions, KPI requirements, SLAs (Service Level Agreement), operation parameters to be monitored, and the like.

Each sub-network slice instance is managed by each domain NSM & O, respectively. After receiving the contraction request message, the multi-vector NSM & O may determine which subnet slice instances need to be contracted, and then directly notify the domain NSM & O corresponding to the subnet slice instances to contract. The above embodiments are merely examples, and the embodiments of the present invention are not limited thereto, and the number of domainNSM & O may be other numbers.

Fig. 9 shows a schematic flow diagram of a method of contracting an NSI for a hierarchical NSM & O. As shown in fig. 9, when the multi-vector NSM & O receives a request to shrink an NSI from a sender or the multi-vector NSM & O initiates a request to shrink an NSI, it is known that the composition of the NSI is divided into several subslice instances (the composition is decided at the time of NSI creation), and it is determined that one or more of the subslice instances (i.e., the target NSI) need to be shrunk. The multi-vector NSM & O then notifies the corresponding domain NSM & O that the contraction of the sub-slice instance is complete. How to shrink the subnet slice is self-determined by domain NSM & O.

Therefore, the method for shrinking the NSI according to the embodiment of the present invention determines the shrinkage of the target NSI through the NSM & O having the hierarchical structure, and can flexibly manage a multi-domain and multi-vendor network.

In summary, the method for shrinking the NSI according to the embodiment of the present invention manages the NSI through the newly designed network architecture, and can perform arrangement management on physical and virtual network functions/resources at the same time to implement network slicing, thereby shortening the network deployment time and saving the deployment cost. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

The method for shrinking the NSI provided by the embodiment of the present invention is described in detail above from the perspective of NSM & O, and will be described in detail below from the perspective of a management device with reference to fig. 10.

Fig. 10 is a schematic flow chart of another method for shrinking NSI according to an embodiment of the present invention. As shown in fig. 10, the method 1000 includes:

s1010, a management device receives a network function contraction request message from an NSM & O, where the management device is configured to manage a network function to be contracted of a target NSI, and the NSM & O is configured to manage and orchestrate a network slice instance NSI.

S1020, the management device shrinks the network function according to the network function shrinking request message.

S1030, the management device sends a contraction feedback message to the NSM & O, where the contraction feedback message is used to feed back a result of the contraction processing of the network function.

In the embodiment of the present invention, the management device is a device for managing a network function to be contracted of the target NSI, and the management device may be an EM, a VNFM, or an NFVO. NSM & O is used to manage and orchestrate NSI (e.g., target NSI), it being understood that a network function may include multiple PNFs or multiple VNFs, and thus, contracting a network function includes at least one of terminating PNF, contracting PNF, terminating VNF, and contracting VNF. In addition, the NSI may include multiple network functions, and contracting the NSI may refer to contracting one or more network functions of the NSI. The contents and transmission objects of the network function contraction request message are different according to the difference of the network functions to be contracted.

The network function contraction request message received by the management device may be a message sent by a single NSM & O (i.e., the NSM & O includes only one module) or a message sent by a domain NSM & O in a composite NSM & O (i.e., the NSM & O includes at least two hierarchically distinct modules).

The step of the management device performing the contraction processing on the network function of the target NSI according to the network function contraction request message is the same as the step of the management device involved in the method 700, and is not described herein again.

And the management equipment finishes the contraction processing on the network function of the target NSI and then sends a contraction feedback message to the NSM & O, wherein the contraction feedback message is used for feeding back the result of the contraction processing of the network function. The NSM & O sends a resource allocation request message to the VIM according to the result of the contraction process to request the VIM to release the idle resource after the contraction of the network function, and the NSM & O may also update information of the target NSI in the memory, for example, VNF/PNF information of the target NSI, according to the result of the contraction process, and if the contraction is of the shared function, the NSM & O simultaneously updates VNF/PNF information in the associated NSI.

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

the management device performing contraction processing on the network function according to the network function contraction request message includes:

s1021, the VNFM performs a contraction feasibility check on the first VNF instance according to the network function contraction request message.

S1022, the VNFM shrinks the first VNF instance when the shrink feasibility check passes.

If the network function contraction request message requests the VNFM to contract the first VNF instance, the VNFM first checks the first VNF instance for shrinkability (i.e., performs a contraction feasibility check on the first VNF instance) before performing the contraction process on the first VNF instance, including but not limited to verifying that the NSM & O is qualified to contract the first VNF instance and checking that the contraction parameters meet specifications.

If the check passes (i.e., the shrink feasibility check passes), the VNFM performs a shrink process on the first VNF instance. After performing the contraction process (e.g., modifying the contraction parameters) on the first VNF instance, the VNFM sends a contraction feedback message to the NSM & O, where the contraction feedback message is used to authorize the NSM & O to perform the processing (e.g., changing the lifecycle of the first VNF) on the first VNF instance, and optionally, the contraction feedback message also carries the modified contraction parameters and the related resources.

Therefore, the method for shrinking the NSI according to the embodiment of the present invention checks the shrinkage feasibility of the VNF instance to be shrunk through the VNFM, thereby ensuring that the process of shrinking the VNF instance can be correctly performed.

Optionally, the management device comprises an EM, the network function comprises a second VNF instance, the second VNF instance being an NM-generated VNF instance,

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

In the present example, when the system includes the NM and the VNF instance to be contracted (i.e., the second VNF instance) is the VNF instance generated by the NM, the NSM & O cannot contract the VNF instance, i.e., cannot reduce resources constituting the VNF instance, wherein the NSM & O checks in advance whether the VNF instance can be contracted.

When the system includes the NM and the result of the orchestration is that no further service needs to be provided by the second VNF instance, the NSM & O initiates a request to configure the second VNF (i.e. a network function request message for requesting termination of said second VNF instance) to the EM managing the second VNF instance over the NG5 interface. 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 (e.g., network slice instance identifier) for supporting the target NSI service are deleted, and the policy of the target NSI is deleted. The EM executes the request and feeds back the execution result through the NG5 interface. The NSM & O informs the NFVO to terminate/close a possible network connection between the second VNF instance and the target NSI-specific network function through the NG4 interface, and releases the corresponding network resource. NFVO executes the request and feeds back the execution result through 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, the service provided to the target NSI and the associated NSI is stopped, the configuration parameters (e.g., network slice instance identifier) for supporting the target NSI and the associated NSI service are deleted, and the policy for serving the target NSI and the associated NSI is deleted. The EM executes the request and feeds back the execution result through the NG5 interface. The NSM & O informs the NFVO to terminate/close the network connection that may exist between the VNF and the target NSI and associated NSI network functions through the NG4 interface, releasing the corresponding network resources. NFVO executes the request and feeds back the execution result through the NG4 interface. This substep is repeated until all VNF instances generated by the NM are configured

Therefore, the method for shrinking the NSI according to the embodiment of the present invention determines whether the VNF instance to be shrunk can be shrunk by checking the attribute of the VNF instance to be shrunk by the EM, thereby preventing the NSM & O from generating an error when the VNF instance generated by the NM is shrunk.

The embodiments of the present invention will be described in further detail below based on the common aspects related to the embodiments of the present invention described above.

Fig. 11 is a schematic flow chart of a method for shrinking an NSI according to another embodiment of the present invention. The method may be applied to the system shown in fig. 4, and as shown in fig. 11, the method 1100 includes:

s1101, option a): the NSM & O receives the NSI shrink request initiated by the sending end. The request includes an identifier of the network slice instance, an identity of the sender, and a service/function description to be contracted. The sender may be an authorized third party tenant, an operator, or some application with the authority to contract the network slice instance. Option b): other mechanisms internal to the NSM & O, such as performance management mechanisms, trigger the NSI shrink request.

S1102, the NSM & O checks the NSI state and associates the corresponding NSLD through memory authentication and authorization.

a) If the NSM & O receives the contraction request from the transmitting end.

The 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 identifier format is correct, whether the description format for the service/function to be contracted is correct, and the like.

NSM & O checks the presence and operation of the corresponding network slice instance, correlates NSLD of the network slice instance, and in conjunction with NSLD, NSM & O corresponds these descriptions to VNF or/and PNF in the NSI. If the network slice instance does not exist, the NSM & O feeds back to the sending end that the network slice instance does not exist. If the slice instance is not shrinkable, the slice instance is fed back to the sender that it is not shrinkable. And if the slice example can be contracted, the authentication sender has the network slice example of the authority contraction request and the corresponding VNF or/and PNF. If the authentication verification is not passed, the NSM & O feeds back corresponding errors to the sending end, such as an unauthorized contraction slice example, a contraction command parameter error and the like.

b) If the network slice instance shrink request is triggered by an NSM & O internal mechanism, such as a performance management trigger, the NSM & O associates with the NSLD of the network slice instance, verifies whether the slice instance is shrinkable, and determines the VNF or/and PNF to be shrunk in the NSI in combination with the NSLD. If the slice instance is not contractable, the operator and/or the tenant renting the network slice instance can be optionally fed back with target NSI performance excess or resource utilization rate, and the operator or the tenant determines the next action.

S1103, the NSM & O orchestrates VNFs or/and PNFs to be contracted, including whether to contract VNF instances, configure PNFs, terminate VNF instances, and so on, and checks network function retractability. The NSM & O determines whether the function to be contracted belongs to a general network function shared by the multi-slice instances or a network function specific to the slice instance to be contracted (hereinafter, referred to as a target NSI) according to information in the associated NSLD. If the general network function shared by the multi-slice instances needs to be shrunk, S1104 is executed, otherwise S1105 is executed.

S1104, if it is a general network function shared by multiple slice instances that needs to be shrunk, associating the NSLDs of the slice instances (hereinafter referred to as associated NSIs) except the target NSI sharing the network function. The NSM & O checks the associated NSI operational status and determines whether shrinking the generic network function will affect the service being provided by the associated NSI. If the service associated with the NSI is negatively affected, the shared network function is not shrunk (if the shrinking request is initiated by the sending end), and the shrinking request is fed back to the sending end that the network function is being used, so that the shrinking cannot be carried out.

S1105, if the function of editing result needing to shrink is realized by PNF, NSM & O sends the request of configuring the network function to EM managing the PNF through Itf-N interface:

a) if the PNF is a PNF shared by multiple slice instances and the orchestration result is that the existing PNF is configured to use fewer resources (such as storage resources, CPU time, network bandwidth, etc.) for the service target NSI and the associated NSI, the configuration request sent by the NSM & O is to allocate the fewer resource service target NSI and the associated NSI to the PNF, and adjust the relevant operating parameters and policy information, etc.

b) If the PNF is a PNF shared by multiple slice instances and the arranging result is that the PNF is stopped providing service for the target NSI and the associated NSI, the NSM & O sends a request for configuring the PNF to the EM, wherein the configuration content comprises but is not limited to i) deleting NSI related parameters, such as the target NSI and the associated NSI identifier, NSI monitoring and reporting information and the like; ii) deleting relevant operation parameters and strategy information and the like; iii) close network connections to other shared functions or/and target NSI-specific functions, associated NSI-specific functions, etc.

c) If the PNF is a PNF dedicated to the target NSI and the scheduling result is that the existing PNF is configured to use the fewer resource service targets NSI and the associated NSI, the configuration request sent by the NSM & O is to allocate the fewer resource service targets NSI to the PNF and adjust the relevant operation parameters, policy information and the like.

d) If the PNF is a PNF exclusive to the target NSI and the arranging result is that the PNF is stopped providing service for the target NSI, the NSM & O sends and configures the PNF, and the configuration content comprises but is not limited to i) deleting NSI related parameters, such as a target NSI identifier, NSI monitoring and reporting information and the like; ii) deleting operation parameters and strategy information, and the like; iii) delete network connections to other shared functions or/and target NSI-specific functions etc.

S1106, the EM executes the configuration request for the PNF, and the configuration content is as described in S1105.

S1107, the EM feeds back configuration completion confirmation to the NSM & O, and if the target NSI has other PNFs which are not configured, the S1105-S1107 are repeated.

S1108, if the orchestration 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 operation state of the VNF instance, and deleting the management object. If the VNF instance needs to be contracted as a result of the orchestration, step S1112 is executed.

S1109, the EM executes S1108 the request to terminate the management of the VNF instance.

S1110, the EM feeds back the termination management confirmation to the NSM & O.

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

S1112, the NSM & O sends a shrink/terminate VNF instance notification to the VNFM via the NG1 interface, the notification including, but not limited to, an identity of the VNF instance to be shrunk/terminated, and a shrink parameter/terminate command.

S1113, the VNFM performs a VNF shrink/terminate 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 whether the NSM & O is qualified to shrink the VNF instance, checking whether the shrink parameters meet the specifications.

b) If the request is the termination of the VNF instance, the VNFM executes the request of the termination of the VNF instance, namely, the VNF instance cooperates with the VNF instance to normally close the VNF instance

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

a) if the request is to contract the VNF instance, the contraction feasibility check result is fed back, the feedback result includes (possibly) corrected parameters and involved resources, and the VNF instance lifecycle change is authorized to start.

b) Feeding back a termination execution confirmation if the request is to terminate the VNF instance

S1115, the NSM & O initiates a resource allocation request and an internal connection adjustment/deletion request required for contracting/terminating the VNF instance to the VIM through the NG2 interface according to the updated parameters (only contracting the VNF instance) fed back by S1114.

S1116, the VIM executes the resource allocation change request and the internal connection adjustment/deletion request.

a) When contracting a shared or proprietary VNF instance:

i. if existing resources are used for contracting VNF instance part, such as reduction of CPU occupation ratio, reduction of resource usage, reduction of bandwidth and the like, internal network connection does not need to be deleted.

if part of the virtual machines are deleted for the VNF instance, the internal network connection is adjusted/deleted, then the virtual machines are closed, and resources are released.

b) When the VNF instance is terminated:

the VIM deletes network connections existing between the VNF instance and other network functions of the target NSI and releases resources constituting the VNF instance, such as deleting a virtual machine and releasing resources.

S1117, if the terminated VNF instance is a slice sharing general network function, the VIM further needs to delete the network connection existing between the VNF instance and the associated NSI network function and release the corresponding resource.

S1118, the VIM feeds back resource allocation and network connection configuration completion confirmation to the NSM & O via the NG2 interface. Only when contracting the VNF instance, the NSM & O passes this information to the VNFM through the NG1 interface.

S1119, the VNFM adjusts the VNF lifecycle parameters, deployment parameters only when contracting the VNF instance.

S1120, the VNFM feeds back to the NSM & O via the NG2 interface that the VNF instance contraction is complete only when contracting the VNF instance.

S1121, the NSM & O adjusts, through the EM, the contracted VNF application parameters, such as execution function and operation policy adjustment, only when contracting the VNF instance.

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

S1123, if the slicing example contraction request is sent by the sending end, feeding back the success of slicing example contraction to the sending end.

The NSI contraction method provided by the embodiment of the invention is based on the upgrading of the existing network management system, supports the management of the network slice example, supports the unified arrangement management of the physical network function and the virtual network function, and supports the contraction of the network slice example, and belongs to an important component part in the management of the life cycle of the network slice. The embodiment of the invention allows an operator or a third-party tenant of the authorized network slicing instance to shrink the network slicing instance as required when finding that the performance of the existing slicing instance is excessive, or automatically shrink when the performance of the slicing instance is excessive according to a strategy, thereby reducing the operation and maintenance cost and saving the expenditure. In addition, the embodiment of the invention discriminates and manages the common network function shared by the network slice example and other slice examples and the slice-specific network function, so that the contraction of the shared network function does not generate negative influence on the service provided by other slice examples.

Fig. 12 is a schematic flow chart of a method for shrinking an NSI according to another embodiment of the present invention. The method may be applied to the system shown in fig. 3, and as shown in fig. 12, the method 1200 includes:

s1201, option a): the NSM & O receives the NSI shrink request initiated by the sending end. The request includes an identifier of the network slice instance, an identity of the sender, and a service/function description to be contracted. The sender may be an authorized third party tenant, an operator, or some application with the authority to contract the network slice instance. Option b): other mechanisms internal to the NSM & O, such as performance management mechanisms, trigger the NSI shrink request.

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

a) If the NSM & O receives the contraction request from the transmitting end.

S1203, the NSM & O marshals the VNF or/and PNF to be contracted, including whether to contract the VNF instance, configure the PNF, terminate the VNF instance, and the like, and checks the network function retractability. The NSM & O determines whether the function to be contracted belongs to a general network function shared by the multi-slice instances or a network function specific to the slice instance to be contracted (hereinafter, referred to as a target NSI) according to information in the associated NSLD. If the general network function shared by the multi-slice instances needs to be shrunk, S1204 is executed, otherwise S1205 is executed.

S1204, if it is a general network function shared by multiple slice instances to be contracted, associating the NSLDs of the other slice instances (hereinafter referred to as association NSIs) except the target NSIs sharing the network function. The NSM & O checks the associated NSI operational status and determines whether shrinking the generic network function will affect the service being provided by the associated NSI. If the service associated with the NSI is negatively affected, the shared network function is not shrunk (if the shrinking request is initiated by the sending end), and the shrinking request is fed back to the sending end that the network function is being used, so that the shrinking cannot be carried out.

S1205, if the function to be contracted of the editing result is realized by the PNF, the NSM & O initiates a request for configuring the network function to the EM managing the PNF through an Itf-N interface:

S1206, the EM executes a configuration request for the PNF, the configuration content being as described in S1205.

S1207, the EM feeds back configuration completion confirmation to the NSM & O, and if the target NSI has other PNF which are not configured, the S1205-S1207 are repeated.

S1208, if the orchestration 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 operation state of the VNF instance, and deleting the management object. If the VNF instance needs to be contracted as a result of the orchestration, step S1212 is performed.

S1209, the EM executes the request to terminate the management of the VNF instance of S1208.

And S1210, the EM feeds back a termination management confirmation to the NSM & O.

S1211, the NSM & O commands the EM to close the virtual port of the VNF instance and stop the service.

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

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

The NFVO requests the VNFM to perform a VNF shrink/terminate request:

VNFM feeds back to NFVO:

And the NFVO initiates a resource allocation request and an internal connection adjustment/deletion request required for contracting/terminating the VNF instance to the VIM according to the updated parameters (only contracting the VNF instance) fed back by the VNFM.

The VIM executes the resource allocation change request and the internal connection adjustment/deletion request:

a) when contracting a shared or proprietary VNF instance:

b) When the VNF instance is terminated:

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

And the VIM feeds back resource allocation and network connection configuration completion confirmation to the NFVO. The NFVO passes this information to the VNFM only when the VNF instance is collapsed.

Only when the VNF instance is contracted, the VNFM adjusts VNF lifecycle parameters, deployment parameters.

S1214, when contracting the VNF instance, the NFVO feeds back the VNF instance contraction end to the NSM & O; when the VNF instance is terminated, the NFVO feeds back VNF instance contraction termination completion to the NSM & O, and configures a network connection completion notification.

S1215, the NSM & O adjusts the contracted VNF application parameters, such as execution function and operation policy adjustments, through the EM only when the VNF instance is contracted.

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

S1217, if the slicing instance contraction request is sent by the sending end, feeding back to the sending end that the slicing instance contraction is successful.

The NSI contraction method provided by the embodiment of the invention is based on the upgrading of the existing network management system, supports slice management, supports the direct arrangement management of the physical network function, uses the NFV MANO system management arrangement for the virtual network function, supports the contraction of the network slice example under the system architecture, and belongs to an important component part in the network slice life cycle management. The invention allows an operator or an authorized third-party tenant of the network slicing instance to shrink the network slicing instance as required when finding that the performance of the existing slicing instance is excessive, or automatically shrink when the performance of the slicing instance is excessive according to a strategy, thereby reducing the operation and maintenance cost and saving the resource overhead. In addition, the invention discriminates and manages the common network function shared with other slice examples and the slice-specific network function in the network slice example, so that the contraction of the shared network function does not generate negative influence on the service provided by other slice examples.

Fig. 13 is a schematic flow chart of a method for shrinking an NSI according to another embodiment of the present invention. The method may be applied to the system shown in fig. 5, and as shown in fig. 13, the method 1300 includes:

s1301, option a): the NSM & O receives the NSI shrink request initiated by the sending end. The request includes an identifier of the network slice instance, an identity of the sender, and a service/function description to be contracted. The sender may be an authorized third party tenant, an operator, or some application with the authority to contract the network slice instance. Option b): other mechanisms internal to the NSM & O, such as performance management mechanisms, trigger the NSI shrink request.

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

a) If the NSM & O receives the contraction request from the transmitting end.

S1303, the NSM & O lays out VNFs or/and PNFs to be shrunk, including whether to shrink a VNF instance, configure a PNF, terminate a VNF instance, and check network function shrinkability, and if a VNF generated by the NM is used during instantiation, update, or expansion of a network slice, the NSM & O cannot shrink the VNF, that is, cannot reduce resources constituting the VNF. The NSM & O determines whether the function to be contracted belongs to a general network function shared by the multi-slice instances or a network function specific to the slice instance to be contracted (hereinafter, referred to as a target NSI) according to information in the associated NSLD. If it is a common network function shared by the multi-slice instances that needs to be contracted, S1304 is performed, otherwise S1305 is performed.

S1304, if it is a common network function shared by multiple slice instances that needs to be contracted, associate the NSLDs of the slice instances (hereinafter referred to as association NSIs) other than the target NSI that share the network function. The NSM & O checks the associated NSI operational status and determines whether shrinking the generic network function will affect the service being provided by the associated NSI. If the service associated with the NSI is negatively affected, the shared network function is not shrunk (if the shrinking request is initiated by the sending end), and the shrinking request is fed back to the sending end that the network function is being used, so that the shrinking cannot be carried out.

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

S1306, NM feeds back confirmation to NSM & O via NG3 interface, thereby avoiding NM and NSM & O configuration at the same time, causing collision.

S1307, if the function of the editing result needing to be contracted is realized by the PNF, the NSM & O initiates a request for configuring the network function to the EM managing the PNF through the Itf-N interface:

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

S1309, the EM feeds back configuration completion confirmation to the NSM & O, and if the target NSI has other PNFs which are not configured, the steps from S1307 to S1309 are repeated.

S1310, when the orchestration result is that the VNF is not needed to provide service again, the NSM & O initiates a request to configure the network function to the EM managing the VNF through the NG5 interface. The request includes, but is not limited to:

a) if the VNF 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 for serving the target NSI is deleted. The EM executes the request and feeds back the execution result through the NG5 interface. The NSM & O informs the NFVO to terminate/close the network connection that may exist between the VNF and the target NSI-specific network function through the NG4 interface, and releases the corresponding network resource. NFVO executes the request and feeds back the execution result through the NG4 interface. This substep is repeated until all VNFs generated by NM are configured.

b) If the VNF is a shared network function, the services provided to the target NSI and associated NSI are stopped, configuration parameters such as network slice instance identification for supporting the target NSI and associated NSI services are deleted, and policies for servicing the target NSI and associated NSI are deleted. The EM executes the request and feeds back the execution result through the NG5 interface. The NSM & O informs the NFVO to terminate/close the network connection that may exist between the VNF and the target NSI and associated NSI network functions through the NG4 interface, releasing the corresponding network resources. NFVO executes the request and feeds back the execution result through the NG4 interface. This substep is repeated until all VNFs generated by NM are configured.

S1311, if the orchestration 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 operation state of the VNF instance, and deleting the management object. If the VNF instance needs to be contracted as a result of the orchestration, step S1312 is performed.

S1312, the EM executes the request of S1311 to terminate the management of the VNF instance.

S1313, the EM feeds back the termination management confirmation to the NSM & O.

S1314, the NSM & O instructs the EM to close the virtual port of the VNF instance and stop the service.

S1315, the NSM & O sends a shrink/terminate VNF instance notification to the NFVO, where the notification includes, but is not limited to, an identity of a VNF instance to be shrunk/terminated, and a shrink parameter/terminate command.

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

The NFVO requests the VNFM to perform a VNF shrink/terminate request:

VNFM feeds back to NFVO:

a) when contracting a shared or proprietary VNF instance:

b) When the VNF instance is terminated:

The NFVO adjusts VNF lifecycle parameters, deployment parameters, only when the VNF instance is contracted.

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

S1318, only when the VNF instance is shrunk, the NSM & O adjusts the shrunk VNF application parameters through the EM, such as performing function and operation policy adjustment.

S1319, NSM & O informs NM network function configuration is completed and informs the configuration of specific contents.

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

S1321, if the slicing example contraction request is sent by the sending end, the success of slicing example contraction is fed back to the sending end.

The NSI contraction method provided by the embodiment of the invention reserves the existing network management system, adopts a set of independent network management system for network slice service, supports direct arrangement management of physical network functions, uses NFVMANO system management arrangement for virtual network functions, supports contraction of network slice examples under the system architecture, and belongs to an important component part in network slice life cycle management. The invention allows an operator or a third-party tenant obtaining authorization to shrink the network slicing instance as required when the performance is excessive, or automatically shrink when the performance of the slicing instance is excessive according to a strategy, thereby reducing the operation and maintenance cost and saving the resource expenditure. In addition, the invention discriminates and manages the common network function shared with other slice examples and the slice-specific network function in the network slice example, so that the contraction of the shared network function does not generate negative influence on the service provided by other slice examples.

Fig. 14 is a schematic flow chart of a method for shrinking an NSI according to another embodiment of the present invention. The method may be applied to the system shown in fig. 4, and as shown in fig. 14, the method 1400 includes:

s1401, option a): the NSM & O receives the NSI shrink request initiated by the sending end. The request includes an identifier of the network slice instance, an identity of the sender, and a service/function description to be contracted. The sender may be an authorized third party tenant, an operator, or some application with the authority to contract the network slice instance. Option b): other mechanisms internal to the NSM & O, such as performance management mechanisms, trigger the NSI shrink request.

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

a) If the NSM & O receives the contraction request from the transmitting end.

S1403, the NSM & O orchestrates the VNF or/and PNF to be contracted, including whether to contract VNF instances, configure PNF, terminate VNF instances, etc., and checks network function scalability. The NSM & O determines whether the function to be contracted belongs to a general network function shared by the multi-slice instances or a network function specific to the slice instance to be contracted (hereinafter, referred to as a target NSI) according to information in the associated NSLD. If it is a common network function shared by the multi-slice instances that needs to be collapsed, then S1404 is performed, otherwise S1405 is performed.

S1404, if the general network function shared by the multiple slice instances needs to be shrunk, associating the NSLDs of the slice instances (hereinafter referred to as association NSIs) except the target NSIs sharing the network function. The NSM & O checks the associated NSI operational status and determines whether shrinking the generic network function will affect the service being provided by the associated NSI. If the service associated with the NSI is negatively affected, the shared network function is not shrunk (if the shrinking request is initiated by the sending end), and the shrinking request is fed back to the sending end that the network function is being used, so that the shrinking cannot be carried out.

S1405, NSM & O informs the NM via the NG3 interface which network functions (e.g. PNF) are to be configured.

S1406, NM feeds back confirmation to NSM & O through NG3 interface, thereby avoiding NM and NSM & O configuration at the same time, causing collision.

S1407, if the function of the editing result needing to be contracted is realized by the PNF, the NSM & O initiates a request for configuring the network function to the EM managing the PNF through the Itf-N interface:

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

S1409, the EM feeds back the configuration completion confirmation to the NSM & O, if the target NSI has other PNF which is not configured, the S1407 to the S1409 are repeated.

S1410, after the NSM & O has configured the PNF, the specific content of configuring the PNF is fed back to the NM through the NG 3.

S1411, if the orchestration 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 operation state of the VNF instance, and deleting the management object. If the VNF instance needs to be contracted as a result of the orchestration, step S1412 is performed.

S1412, the EM executes the request to terminate management of VNF instances of S1411.

S1413, the EM feeds back the termination management confirmation to the NSM & O.

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

S1415, the NSM & O sends a shrink/terminate VNF instance notification to the VNFM via the NG1 interface, the notification including, but not limited to, an identity of the VNF instance to be shrunk/terminated, and a shrink parameter/terminate command.

S1416, the VNFM performs a VNF shrink/terminate request:

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

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

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

a) When contracting a shared or proprietary VNF instance:

b) When the VNF instance is terminated:

S1420, if the terminated VNF instance is the slice sharing general network function, the VIM further needs to delete the network connection existing between the VNF instance and the associated NSI network function and release the corresponding resource.

S1421, the VIM feeds back resource allocation and network connection configuration completion confirmation to the NSM & O through the NG2 interface. Only when contracting the VNF instance, the NSM & O passes this information to the VNFM through the NG1 interface.

S1422, the VNFM adjusts the VNF lifecycle parameters, deployment parameters only when contracting the VNF instance.

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

S1424, only when the VNF instance is shrunk, the NSM & O adjusts the shrunk VNF application parameters through the EM, such as performing function and operation policy adjustment.

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

S1426, if the slicing example contraction request is sent by the sending end, feeding back to the sending end that the slicing example contraction is successful.

The NSI contraction method provided by the embodiment of the invention reserves the existing network management system, adopts a set of independent network management system for network slicing service, supports direct arrangement management of physical network function and virtual network function, supports contraction of network slicing examples under the system architecture, and belongs to an important component part in network slicing life cycle management. The invention allows an operator or a third-party tenant obtaining authorization to shrink the network slicing instance as required when the performance is excessive, or automatically shrink when the performance of the slicing instance is excessive according to a strategy, thereby reducing the operation and maintenance cost and saving the resource expenditure. In addition, the invention discriminates and manages the common network function shared by the network slice example and other slice examples and the slice-specific network function, so that the contraction of the shared network function can benefit the multi-slice example. The invention discriminates and manages the common network function shared by the network slice example and other slice examples and the slice exclusive network function, so that the contraction of the shared network function does not generate negative influence on the service provided by other slice examples.

The above embodiments mainly introduce the solutions of the embodiments of the present invention from the perspective of interaction between network elements. It is to be understood that each network element, for example, NSM & O, management device, etc., contains corresponding hardware structures and/or software modules for performing each function in order to implement the above functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention

The embodiments of the present invention may perform functional unit division on the NSM & O, the management device (e.g., EM, VNFM, or NFVO), and the like according to the above method examples, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of integrated units, fig. 15A shows a possible structural schematic of the NSM & O involved in the above embodiments. NSM & O1500 includes: a processing unit 1502 and a communication unit 1503. Processing unit 1502 is configured to control and manage actions of NSM & O1500, for example, processing unit 1502 is configured to support NSM & O1500 to perform S1020 of fig. 10, processing unit 1502 may also be configured to support NSM & O1500 to perform S1103 of fig. 11, and/or other processes for the techniques described herein. The communication unit 1503 is used to support communications of the NSM & O1500 with other network entities, for example, communications with the EM shown in fig. 11. NSM & O1500 may also include a storage unit 1501 to store program codes and data for NSM & O1500.

The processing Unit 1502 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 1503 may be a communication interface, a transceiver, a transceiving circuit, etc., wherein the communication interface is a generic term 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 according to the embodiment of the present invention may be the NSM & O shown in fig. 15B.

Referring to fig. 15B, the NSM & O1510 comprises: a processor 1512, a communications interface 1513, and a memory 1511. Optionally, NSM & O1510 may also include a bus 1514. The communication interface 1513, the processor 1512, and the memory 1511 may be connected to each other by a bus 1514; the bus 1514 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 1514 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 15B, but this is not intended to represent only one bus or type of bus.

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

Therefore, the NSM & O provided by the embodiment of the invention can simultaneously perform arrangement management on physical and virtual network functions/resources to realize network slicing, shorten the network deployment time and save the deployment cost. And when NSI shrinks, the general network function and the exclusive network function are processed in a distinguishing way, so that the influence on the service provided by other slice instances is avoided when the general network function shrinks.

In the case of an integrated unit, fig. 16A shows a schematic diagram of a possible structure of the management device involved in the above-described embodiment. The management device 1600 includes: a processing unit 1602 and a communication unit 1603. Processing unit 1602 is configured to control and manage actions of management device 1600, e.g., processing unit 1602 is configured to support management device 1600 performing S730 of fig. 7, processing unit 1602 is also configured to support management device 1600 performing S1106 of fig. 11, and/or other processes for the techniques described herein. The communication unit 1603 is used to support communication between the management device 1600 and other network entities, for example, NSM & O shown in fig. 11. The management device 1600 may further include a storage unit 1601 for storing program codes and data of the management device 1600.

The processing unit 1602 may be a processor or a controller, and may be, for example, 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. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 1603 may be a communication interface, a transceiver, a transceiving circuit, etc., wherein the communication interface is a generic term and may comprise one or more interfaces. The storage unit 1601 may be a memory.

When the processing unit 1602 is a processor, the communication unit 1603 is a communication interface, and the storage unit 1601 is a memory, the management apparatus according to the embodiment of the present invention may be the management apparatus shown in fig. 16B.

Referring to fig. 16B, the management device 1610 includes: a processor 1612, a communications interface 1613, and a memory 1611. Optionally, the management device 1610 may also include a bus 1614. Wherein the communication interface 1613, the processor 1612, and the memory 1611 may be interconnected via a bus 1614; the bus 1614 may be a PCI bus or an EISA bus, etc. The bus 1614 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 16B, but this does not indicate only one bus or one type of bus.

Therefore, the management device provided by the embodiment of the invention manages the NSI through the newly designed network architecture, can simultaneously perform arrangement management on physical and virtual network functions/resources to realize network slicing, shortens the network deployment time, and saves the deployment cost. And when NSI is contracted, the influence on the service provided by other slice instances is avoided when the general network function is contracted by processing the general network function and the special network function in a distinguishing way

In the embodiment of the present invention, the sequence number of each process does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the internal logic of the process, and should not limit the implementation process of the embodiment of the present invention at all.

In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware or in software executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in an NSM & O or management device. Of course, the processor and the storage medium may reside as discrete components in the NSM & O or management device.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in connection with the embodiments of the invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Claims

1. A method of shrinking a network slice instance, the method comprising:

a first network slice management and orchestrator (NSM & O) sends a network function contraction request message to a management device, wherein the first NSM & O is used for managing and orchestrating a Network Slice Instance (NSI), the management device is used for managing a network function to be contracted of a target NSI, and the network function contraction request message is used for requesting the management device to perform contraction processing on the network function, and when the network function is a dedicated network function of the target NSI, the first NSM & O sends the network function contraction request message to the management device; or the first NSM & O sends the network function contraction request message to the management device when the network function is a shared network function of the target NSI and an associated NSI, and the contraction of the network function does not affect the service of the associated NSI, where the associated NSI is an NSI that uses the network function in common with the target NSI;

the first NSM & O receives a contraction feedback message from the management device, wherein the contraction feedback message is used for the management device to feed back a result of contraction processing of the network function;

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

2. The method of claim 1, wherein prior to the first NSM & O sending a network function contraction request message to a management device, the method further comprises:

the first NSM & O obtaining an NSI shrink request message, wherein the NSI shrink request message comprises identification information of the target NSI, and the NSI shrink request message is used for requesting the first NSM & O to shrink the target NSI;

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

the first NSM & O determines the network function from the NSLD.

3. The method of claim 2, wherein after the first NSM & O obtains the NSI contraction request message and before the first NSM & O sends the network function contraction request message to the management device, the method further comprises:

the first NSM & O sends a notification message to a Network Manager (NM), wherein the notification message is used for notifying the NM that the first NSM & O needs to perform contraction processing on the network function;

the first NSM & O receives an acknowledgement message from the NM instructing the first NSM & O to shrink the network function.

4. A method according to any of claims 1 to 3, wherein after the first NSM & O receives a shrink feedback message from the management device and before the first NSM & O updates the information for the target NSI stored in memory according to the feedback message, the method further comprises:

the first NSM & O sends a resource allocation request message to a Virtual Infrastructure Manager (VIM), wherein the resource allocation request message is used for requesting the VIM to release idle resources after the network function is contracted;

the first NSM & O receiving a resource allocation feedback message from the VIM;

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

5. The method according to any of claims 1 to 3, 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 shrink feedback message, the associated NSI being an NSI that uses the shared network function in common with the target NSI.

6. A method according to claim 2 or 3, wherein the first NSM & O obtains an NSI contraction request message, comprising:

the first NSM & O obtains the NSI shrink request message sent by the second NSM & O.

7. A method of shrinking a network slice instance, the method comprising:

receiving, by a management device, a network function contraction request message from a network slice management and orchestrator NSM & O, wherein the management device is configured to manage a network function to be contracted of a target network slice instance NSI, and the NSM & O is configured to manage and orchestrate the network slice instance NSI, and when the network function is a network function specific to the target NSI, the management device receives the network function contraction request message from the NSM & O; or when the network function is a shared network function of the target NSI and an associated NSI and contracting the network function does not affect the service of the associated NSI, the management device receives the network function contraction request message from the NSM & O, the associated NSI being an NSI that uses the network function in common with the target NSI;

the management equipment shrinks the network function according to the network function shrinking request message;

and the management equipment sends a contraction feedback message to the NSM & O, wherein the contraction feedback message is used for feeding back the result of the contraction processing of the network function.

8. The method of claim 7, wherein the management device comprises a Virtual Network Function Manager (VNFM), wherein the network function comprises a first Virtual Network Function (VNF) instance,

the 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 passes.

9. The method according to claim 7 or 8, characterised in that said managing device comprises a network element manager, EM, said network function comprises a second VNF instance, said second VNF instance being a VNF instance generated by a network manager, NM,

10. An apparatus for shrinking network slice instances, characterized in that the apparatus is adapted to manage and orchestrate network slice instances NSIs, the apparatus comprising a processing unit and a communication unit,

the processing unit is configured to send a network function contraction request message to a management device through the communication unit, where the management device is configured to manage a network function to be contracted of a target NSI, and the network function contraction request message is configured to request the management device to perform contraction processing on the network function, and the processing unit is specifically configured to send the network function contraction request message to the management device through the communication unit 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 an associated NSI and the network function is contracted without affecting the service of the associated NSI, sending the network function contraction request message to the management device through the communication unit, wherein the associated NSI is an NSI that uses the network function together with the target NSI;

and the processing unit is used for receiving a contraction feedback message from the management device through the communication unit, wherein the contraction feedback message is used for the management device to feed back the result of the contraction processing of the network function;

and the processing unit is used for updating the information of the target NSI stored in the memory according to the contraction feedback message.

11. The apparatus of claim 10, wherein the processing unit is further configured to:

acquiring an NSI contraction request message, wherein the NSI contraction request message includes identification information of the target NSI, and the NSI contraction request message is used for requesting the device to perform contraction processing on the target NSI; and a network slice template NSLD for determining the target NSI according to the identification information; and for determining the network function from the NSLD.

12. The apparatus of claim 11, wherein the processing unit is further configured to:

sending a notification message to a network manager, NM, through said communication unit, said notification message for notifying said NM that said device needs to perform a shrink processing on said network function; and for receiving an acknowledgement message from said NM via said communication unit, said acknowledgement message instructing said apparatus to shrink said network function.

13. The apparatus according to any one of claims 10 to 12, wherein the processing unit is further configured to:

sending a resource allocation request message to a Virtualized Infrastructure Manager (VIM) through the communication unit, wherein the resource allocation request message is used for requesting the VIM to release idle resources after the network function is contracted; and for receiving, by the communication unit, a resource allocation feedback message from the VIM; and information for updating the target NSI stored in the memory according to the contraction feedback message and the resource allocation feedback message.

14. The apparatus according to any of claims 10 to 12, wherein when the network function is a shared network function, the processing unit is further configured to:

updating information of an associated NSI stored in the memory according to the shrink feedback message, the associated NSI being an NSI that uses the shared network function in common with the target NSI.

15. The apparatus according to claim 11 or 12, wherein the processing unit is specifically configured to:

and acquiring the NSI contraction request message sent by a second network slice management and orchestrator NSM & O.

16. An apparatus for shrinking a network slice instance, the apparatus being configured to manage network functions to be shrunk for a target network slice instance NSI, the apparatus comprising a processing unit and a communication unit,

the processing unit is configured to receive a network function contraction request message from a network slice manager and orchestrator NSM & O through the communication unit, wherein the processing unit receives the network function contraction request message from the NSM & O when the network function is a dedicated network function of the target NSI; or the processing unit receives the network function contraction request message from the NSM & O when the network function is a shared network function of the target NSI and an associated NSI, and the network function is contracted without affecting the service of the associated NSI, the associated NSI being an NSI that uses the network function in common with the target NSI;

the processing unit is used for carrying out contraction processing on the network function according to the network function contraction request message;

and the processing unit is used for sending a contraction feedback message to the NSM & O through the communication unit, wherein the contraction feedback message is used for feeding back the result of the contraction processing of the network function.

17. The apparatus of claim 16, wherein the apparatus comprises a Virtual Network Function Manager (VNFM), wherein the network function comprises 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 means for scaling the first VNF instance if the scaling feasibility check passes.

18. The apparatus according to claim 16 or 17, characterised in that the apparatus comprises a network element manager, EM, the network function comprises a second VNF instance, the second VNF instance being a VNF instance generated by a network manager, NM,