WO2018082487A1

WO2018082487A1 - Method, device and system for network slice management

Info

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

Abstract

The present application provides a method for network slice management, comprising: a network slice manager & orchestrator (NSM&O) receives a management request message of a target network slice, the management request message being used for requesting to delete the target network slice or terminating a target network slice instance; the NSM&O controls, according to the management request message, a physical network function management device and/or a virtual network function management device to perform network slice management on the target network slice. Therefore, the method for network slice management provided in the present application can implement the deletion of a network slice and the termination of a network slice instance by means of unified management on physical resources and virtual resources.

Description

Method, device and system for managing network slicing

The present application claims priority to Chinese Patent Application No. 201610958346.X, entitled "Method, Apparatus and System for Managing Network Slices", filed on November 3, 2016, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of communications, and relates to a method, device and system for managing network slices.

Background technique

The 5th generation (5G) mobile communication system needs to meet diverse business needs, such as enhanced mobile broadband, large-scale machine-like communication, ultra-reliable and low-latency communication. The network slicing technology logically abstracts the network into one or more isolated network slices, wherein each network slice contains a series of logical network functions, which specifically meet the differentiated requirements of different services, and the network slice instance is Is an instance created from a network slice template or other means.

In network slicing technology, when the service no longer needs to use network slicing (for example, machine type communication service is no longer needed), or the network no longer provides network slicing service (for example, the network provider decides to shut down the machine class based on cost-effective reasons) Network slice of communication), you need to delete the relevant network slice or terminate the relevant network slice instance. However, the prior art network management architecture (for example, the 3rd generation partnership project (3GPP) telecommunications network management architecture) can only implement the management of physical network functions (PNF), while existing The network function virtualization management and orchestration (MANO) network architecture can only implement the management of virtual network functions (VNF).

Therefore, there is a need for a method for managing network slicing, which enables unified deletion of physical resources and virtual resources to enable deletion of network slices or termination of network slicing instances.

Summary of the invention

The present application provides a method and apparatus for managing network slice instances in order to implement management of network slice instances.

In a first aspect, a method for managing a network slice is provided, comprising: a network slice manager & orchestrator (NSM&O) receiving a management request message of a target network slice, the management request message being used to request to delete the target network The target network slice instance is sliced or terminated; the NSM&O controls the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message.

Therefore, the method for managing a network slice provided by the present application can implement the deletion of the network slice and the termination of the network slice instance by the unified management of the physical resource and the virtual resource.

Further, the present application can terminate the current target network slice when the sender determines that the current target network slice instance is no longer supported; or delete the target network slice when the sender determines that the current target network slice is no longer supported. Therefore, it is possible to more flexible network slice management and reduce operating costs.

Optionally, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message, including: when the management request message is used to request to terminate the target network When the instance is sliced, the VNF management device is controlled to terminate the VNF corresponding to the target network slice instance; and/or the PNF management device is controlled to terminate the PNF corresponding to the target network slice instance.

Optionally, the PNF management device includes an EM, where the controlling the PNF management device to terminate the PNF corresponding to the target network slice instance includes: when the PNF corresponding to the target network slice instance includes the first PNF Instructing the network element manager EM managing the first PNF to configure the first PNF to terminate the service to the target network slice instance.

Optionally, the PNF management device includes an EM, where the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: when the VNF corresponding to the target network slice embodiment includes a shared VNF Instructing the EM managing the shared VNF to configure the shared VNF to terminate the service to the target network slice instance.

Optionally, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance comprises: instructing the virtualization infrastructure management device VIM to configure the shared VNF to terminate a network connection related to the target network slice instance. And/or shrinking network resources associated with the target network slice instance, wherein the VNF management device includes the VIM.

Optionally, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance comprises: instructing a virtual network function virtualization orchestrator (NFVO) to configure the shared VNF as a terminating and target network Slicing instance related network connections, and/or shrinking network resources associated with the target network slice instance, wherein the VNF management device includes the NFVO.

Optionally, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: when the VNF corresponding to the target network slice instance includes a dedicated VNF, indicating to manage the EM of the dedicated VNF End the management of the exclusive VNF.

Optionally, the VNF management device includes a VIM and a VNF management device VNFM, and the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance, including: instructing the VNFM to terminate the exclusive VNF; The VIM closes a network connection associated with the dedicated VNF and/or releases network resources associated with the second VNF.

Optionally, the VNF management device includes an NFVO, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance, and terminating the target network slice embodiment, including: indicating that the NFVO is closed and A dedicated VNF-related network connection, and/or release of network resources associated with the shared VNF.

Therefore, the network slice management of the target network slice by the NSM&O in the present application can implement the differential network management of the network slice instance and the exclusive network function, so that the termination of the target network slice embodiment does not affect other network slice instances.

Optionally, the dedicated VNF corresponding to the target network slice instance is a VNF generated by the NSM&O.

That is, if the exclusive VNF is generated for NSM&O, then NSM&O can control the PNF device and the VNF device to terminate the exclusive VNF; if not, the exclusive VNF generated by NSM&O, such as the NM generated special As a VNF, then NSM&O can instruct the PNF device and the VNF device to configure to turn off the service of the dedicated VNF to the target network slice instance.

Optionally, the method further includes: sending a notification message to the network management device NM, where the notification message is used to notify the NM to perform network slice management on the target network slice.

Optionally, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message, including: when the management request message is used to delete the target network slice The VNF and/or PNF corresponding to each instance in the target network slice is deleted.

Optionally, the deleting the VNF and/or the PNF corresponding to each instance in the target network slice comprises: terminating the VNF and/or PNF corresponding to each instance in the target network slice.

Optionally, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message, including: after determining that all instances in the target network slice are terminated And instructing a repository to delete the slice template of the target network slice.

Optionally, before the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request, the method further includes: verifying that the management request message is initiated. Whether the sender has the right to manage the network slice of the target network slice.

Optionally, verifying whether the sending end of the management request message has the right to manage the network slice of the target network slice comprises: sending a verification message to the memory, where the verification message is used by the memory to determine the sending Whether the terminal has the right to perform network slice management on the target network slice; receiving the verification completion message of the memory feedback, the verification completion message is used to notify the NSM&O whether the sending end performs network segmentation on the target network slice Managed permissions.

Optionally, the method further includes: when determining that the sending end does not have the right to manage network slice management of the target network slice, sending a verification failure message to the sending end, where the verification failure message is used for notification The sending end does not have the right to perform network slice management on the target network slice.

Optionally, the method further includes: when the NSM&O completes management of the target network slice, sending a management complete message to the sending end, where the management complete message is used to notify the sending end that the target network has been completed. The deletion of a slice or the termination of an instance of the target network slice.

Further, the present application can terminate the current target network slice when the transmitting end determines that the current target network slice instance is no longer supported; or when the transmitting end determines that the current target network slice is no longer supported, the target network slice is deleted, so Flexible network slice management to reduce operating costs.

Therefore, when the network slice needs to be deleted, NSM&O can manage the PNF and VNF, and can arrange physical and virtual resources uniformly. The policy is more flexible and can use network resources optimally. When the network slice instance needs to be terminated, the shared VNF of the network slice is terminated. When you can choose to shrink the resources of VNF according to your needs, you can improve resource utilization.

A second aspect provides a method for managing a network slice, including: sending, to an NSM&O, a management request message of the target network slice, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target. And receiving, by the NSM&O, a management complete message, where the management complete message is used to determine that the NSM&O completes deletion of the target network slice or termination of the target network slice instance.

Optionally, the method further includes: receiving a verification failure message sent by the NSM&O, where the verification fails The information is used to notify that the target network slice management is not possible.

Optionally, the method includes: receiving an authentication message of the NSM&O, where the verification message is used to verify whether a sending end that initiates the network slice management request has the right to perform network slice management on the target network slice; and verifying according to the verification message Whether the sender has the right to perform network slice management on the target network slice.

Optionally, the returning the verification completion message to the NSM&O, so that the NSM&O determines whether to manage the target network slice according to the verification feedback message, including: returning a verification completion message to the NSM&O, The verification completion message is used to notify the NSM&O whether the sending end has the right to perform network slice management on the target network slice; when the sending end does not have the network slice management authority on the target network slice or the When the instance of the target network slice does not exist, the verification feedback message is used to notify the NSM&O that the sender does not have the right to perform network slice management on the target network slice; or when the sender has the target When the network slice management authority of the network slice is used, the verification feedback message is used to notify the NSM&O that the sender has the right to perform network slice management on the target network slice.

A third aspect provides a method for managing a network slice, comprising: receiving a verification message of an NSM&O, wherein the verification message is used to verify whether a sender that initiates a network slice management request has the right to perform network slice management on a target network slice. And verifying, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.

In a fourth aspect, the present application provides a network device, where the network device can implement the functions performed by the network device in the method related to the foregoing first aspect, where the function can be implemented by using hardware or by executing corresponding software through hardware. . The hardware or software includes one or more corresponding units or modules of the above functions.

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

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

In a sixth aspect, the application provides a network device, which can implement the foregoing aspects of the third aspect. The function performed by the network device in the method, the function may be implemented by hardware, or may be implemented by hardware corresponding software. The hardware or software includes one or more corresponding units or modules of the above functions.

In a seventh aspect, a system for managing a network slice is provided, the system comprising the network device of any of the fourth aspect to the sixth aspect.

In an eighth aspect, the present application provides a computer readable storage medium storing computer program code, when executed by a processing unit or a processor, causing a network device to perform the first aspect The method described.

In a ninth aspect, the present application provides a computer readable storage medium having stored therein computer program code, when executed by a processing unit or a processor, causes the network device to perform the second aspect The method described.

In a tenth aspect, the present application provides a computer readable storage medium storing computer program code, when executed by a processing unit or a processor, causing a network device to perform the third aspect The method described.

In an eleventh aspect, there is provided a communication chip in which instructions are stored which, when run on a network device, cause the communication chip to perform the method of the first aspect described above.

According to a twelfth aspect, there is provided a communication chip in which instructions are stored which, when run on a network device, cause the communication chip to perform the method of the second aspect described above.

In a thirteenth aspect, there is provided a communication chip in which instructions are stored which, when run on a network device, cause the communication chip to perform the method of the third aspect above.

In a fourteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run by a communication unit or transceiver of a network device, and a processing unit or processor, causing the network device The method of the first aspect above is performed.

In a fifteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run by a communication unit or transceiver of a network device, and a processing unit or processor, causing the network device The method of the second aspect above is performed.

In a sixteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is run by a communication unit or transceiver of a network device, and a processing unit or processor, causing the network device The method of the third aspect above is performed.

DRAWINGS

Figure 1 shows a schematic block diagram of a network slice;

2 is a schematic structural block diagram of a network slice of one embodiment of the present application;

FIG. 3 is a schematic structural block diagram of a network slice of another embodiment of the present application; FIG.

Figure 4 shows a schematic architectural diagram of a 3GPP network;

FIG. 5 shows a schematic architectural diagram of a 3GPP network architecture and a MANO network architecture fusion;

FIG. 6 shows a schematic structural diagram of an NSM&O of one embodiment of the present application;

FIG. 7 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application; FIG.

FIG. 8 is a schematic flowchart of a method for managing a network slice according to another embodiment of the present application; FIG.

FIG. 9 is a schematic flowchart of a method for managing a network slice according to still another embodiment of the present application; FIG.

Figure 10 shows a schematic block diagram of a network architecture of one embodiment of the present application;

FIG. 11 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

FIG. 12 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

Figure 13 shows a schematic block diagram of a network architecture of one embodiment of the present application;

FIG. 14 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

FIG. 15 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

Figure 16 shows a schematic block diagram of a network architecture of one embodiment of the present application;

FIG. 17 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

Figure 18 shows a schematic block diagram of a network architecture of one embodiment of the present application;

FIG. 19 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application;

20 is a schematic block diagram of a network management and orchestrator of one embodiment of the present application;

21 is a schematic flow chart of managing a network slice of an embodiment of the present application;

FIG. 22 is a schematic structural block diagram of a network device according to an embodiment of the present application; FIG.

23 is a schematic structural block diagram of a network device according to an embodiment of the present application;

24 is a schematic structural block diagram of a network device according to another embodiment of the present application;

Figure 25 is a schematic structural block diagram of an apparatus of still another embodiment of the present application;

Figure 26 is a schematic structural block diagram of an apparatus of still another embodiment of the present application;

Figure 27 is a block diagram showing the schematic structure of an apparatus of still another embodiment of the present application.

detailed description

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

The technical solution of the present application can be applied to various communication systems, for example, a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, and a wideband code division multiple access (wideband) Code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) frequency division duplex (FDD) system, LTE time division duplex (time) Division duplex, TDD), universal mobile telecommunication system (UMTS) and 5G communication system.

It should be noted that the terms "network management architecture", "network system", "system" and the like may be replaced with each other.

This application relates to network slicing techniques. The network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types. For example, in the network of a 5G mobile communication system, network slicing is an on-demand networking method, which provides operators with new services that can be adjusted according to changing user requirements and quickly meet the needs of new applications.

Network slice template (NST): Refers to the logical representation of the network functions and their corresponding resources required for telecommunication services and network capabilities.

Network slice instance (NSI): Refers to an instance created from a network slice template.

Network slice (NS): Describes the system behavior implemented by network slices.

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

Figure 1 shows a schematic block diagram of a network slice. As shown in FIG. 1, three network slices in a 3GPP network are shown, which are a real machine type communication network slice, a mass machine type communication slice, and a large machine type communication network slice and Mobile broadband network slice. Figure 1 shows a typical scenario of a network slice. Personal mobile users (such as mobile phones, laptops), smart meters, and vehicles all have access to mobile networks, but they have different service requirements for mobile networks. Specifically, personal mobile users need mobile broadband (MBB) services to meet high-speed Internet access requirements, but have lower requirements for delay, reliability, and number of connections; smart meter users need large-scale machine-like communications. Service, there is a high demand for the number of connections, and the requirements for mobility and access rate are low; vehicles (car network users) need real-time machine-like communication services, which have high requirements for delay and reliability, and the number of connections. The access rate is lower. For the sake of deployment and operation cost, operators hope to connect the above users with different service requirements to the same wireless access network, and adopt logical and physical slicing to provide different customers with the same network infrastructure. Different services.

Although network function virtualization is a key enabling technology that reduces the complexity and cost of network slicing, physical network elements (such as 3GPP network architecture) and virtualized network elements (MANO networks) for the purpose of reducing deployment costs and recovering investment Architecture) will coexist for a long time and be flexible together to form a network slice. Therefore, in order to provide differentiated communication requirements quickly and flexibly, operators need an automated slicing operation and maintenance system that can simultaneously manage and orchestrate PNF and virtualized network functions, enabling the management of physical and virtual network functions/resources. Implement network slicing. The network slice operation and maintenance system is also an important part of the next phase of 3GPP SA5 standardization.

When multiple network slices coexist, network slices may be completely isolated, and some network resources and functions may be shared. For multi-slice coexistence, two main scenarios are given in TR 23.799: Group A and Group B, as shown in Figures 2 and 3, respectively. 2 is a schematic structural block diagram of a network slice according to an embodiment of the present application. In FIG. 2, a slice instance 1 and a slice instance 2 share a radio access network (RAN), and a slice instance of the core network is in Logically completely isolated, the two slice instances are also completely isolated in management; FIG. 3 shows a schematic structural block diagram of a network slice of another embodiment of the present application, in FIG. 3, slice instance 1 and slice instance 2 There is a part of the shared control plane network function (common control plane network function, common CP NF), and each slice instance has a dedicated slice-specific control plane network function (slice-specific control plane network function, Slice-specific CP NF) and slice-specific user plane network function (slice-specific UP NF), Group B slice instance 1 (Instance slice 1) and slice instance (Instance slice 2) are managed In the process, you need to consider the impact of sharing on other slice instances.

Figure 4 shows a schematic architectural diagram of a 3rd Generation Partnership Project 3GPP network.

The existing 3GPP telecommunications network management architecture is shown in Figure 4. The network management architecture 400 includes at least one network element (NE), at least one element manager (EM) module, and at least one Domain manager (DM) and network manager (NM) modules.

The NE module is the smallest unit that can be monitored and managed in the network management architecture. The EM module is responsible for managing a single NE, and provides functions for processing a separate NE, including alarm management, notification management, log recording, and software and hardware maintenance.

The NM is responsible for managing the entire telecommunication network. It is supported by multiple EMs, but can also be directly connected to the NE. It mainly provides online management functions, management device interactions, and other related functions, such as branching of network resources. Configuration, control and monitoring.

In the prior art, the network management architecture of the 3GPP can only implement management of physical resources and PNFs, but cannot manage virtual resources and VNFs, and can not manage network slices and network slice instances.

FIG. 5 shows a schematic architecture diagram of a 3GPP network architecture and a MANO network architecture fusion, so that the NM can manage not only the PNF but also the VNF.

As shown in Figure 5, the MANO network architecture in the left virtual box mainly includes: NFVO, which is responsible for network service, VNF lifecycle management, and optimizes the network functions virtualization infrastructure (NFVI) from a global perspective. Resource utilization; virtual infrastructure manager (VIM) for controlling the management, storage, and network resources of NFVI; virtualized network function manager (VNFM) for managing VNF.

As shown in Figure 5, the network architecture in the virtual box on the right is basically the same as the 3GPP PLMN network architecture, except that the NFVI and the new EM capable of managing the VNF are added.

The network architecture shown in FIG. 5 can implement management of virtual network resources and VNFs alone, or management of physical network resources and PNFs, and cannot implement management of network slicing, that is, physical resources, network functions, and virtual Resources and network functions are managed and arranged to support the requirements of complete isolation, independent management, resource scheduling, etc. of multi-slices in the next-generation mobile network without shared functions. It is not able to support resources when there are shared functions between multiple slices. , network function sharing, network specific functions, resource isolation, independent management and other requirements.

FIG. 6 shows a schematic structural diagram of an NSM&O of one embodiment of the present application.

The traditional 3GPP network management system and the network management system after the integration of MANO are not able to perform unified management and scheduling of network slicing. Therefore, this application proposes NSM&O. The structure of NSM&O is as shown in Figure 6, which mainly includes the following functional modules: service conversion. Module, network slicing design module, network slicing policy management module, network slicing orchestration module, network slicing monitoring module.

Specifically, the service translation module is configured to: receive an application description sent by the sending end through an application programming interface (API), and convert the service description into a requirement for the network.

The slice design module is used to: design a network slice template NSLD according to the result of the service conversion, and describe the composition of the network slice.

The slice policy management module is used for: on-boarding, instantiation, shrinking and scaling, updating, terminating, deleting network slices, etc. aspect.

The slice orchestration module is used to: specifically determine network functions (NF), resources, and the like included in the network slice instance.

The monitoring and reporting module is used to: monitor and report key performance indicators of network slicing instances (key Performance indicator, KPI) parameters, etc.

The entity related to the NSM&O further includes: a repository, where the network slice description (NSLD) and the generated network slice instance related information are recorded; the sender may be an operator. The third party customer/tenant, the service design application, the vendor, or any entity in the SP domain that may send a request to the NSM&O is not limited in this application.

It should be understood that the above concepts such as NSM&O and network slice target may be replaced by different names in different scenarios, and entities capable of implementing the above network functions fall within the protection scope of the present application.

FIG. 7 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application. The execution body of the method may be NSM&O. As shown in FIG. 7, the method includes:

Step 710: The NSM&O receives a management request message of a target network slice, where the management request message is used to request to delete the target network slice or terminate the target network slice instance.

Step 720: The NSM&O controls the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message.

In step 710, the target network slice refers to the network slice that the sender requests to delete. Specifically, the target network slice instance termination request may include an identifier of the target network slice instance, an identity of the sender, and the like. The target network slice deletion request may include an identifier of the NSLD corresponding to the network slice, an identity of the sender, and the like. The sender may be an authorized third-party tenant, carrier, or an application that has the right to terminate the network slice instance/delete network slice.

In step 720, the NSM&O performs network slice management on the target network slice according to the management request message, that is, when the management request message requests to delete the target network slice, the target network slice is deleted; when the management request message requests to terminate the target network slice In the case of an instance, the target network slice instance is terminated.

Further, the NSM&O can control the PNF management device to perform network slice management on the target network slice, the PNF device can include one or more physical entities in the 3GPP network architecture, such as EM, etc.; the NSM&O can also control the VNF management device to slice the target network. For network slice management, the VNF management device may include one or more entities in the MANO network structure, such as VNFM, etc. Similarly, NSM&O may simultaneously manage the target network slice using the PNF management device and the VNF management device.

Optionally, as an embodiment of the present application, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message, including: when the management request message is used Controlling the VNF management device to terminate the VNF corresponding to the target network slice instance, and/or controlling the PNF management device to terminate the PNF corresponding to the target network slice instance.

That is, NSM&O can terminate the VNF corresponding to the target network slice instance by controlling the VNF management device; and NSM&O can terminate the PNF corresponding to the target network slice instance by controlling the PNF management device; further, NSM&O can control the VNF management device and PNF management device that implements PNF and in the network slicing instance The end of VNF.

Optionally, as an embodiment of the present application, the PNF management device includes an EM, where the controlling the PNF management device to terminate the PNF corresponding to the target network slice instance includes: when the target network slice instance corresponds to When the PNF includes the first PNF, the network element manager EM indicating that the first PNF is managed configures the first PNF to terminate the service to the target network slice instance.

Specifically, when the first PNF is a shared PNF, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the Itf-N interface, indicating that the EM managing the shared PNF sets the shared PNF to terminate the target network. A service of a slice instance, including but not limited to: instructing the EM to stop providing services to the target network slice instance, deleting configuration parameters for supporting the target network slice instance service, such as a network slice instance identifier, and deleting a policy of the service target network slice instance Ending/deleting the network connection between the first PNF and the target network slice instance-specific network function, and the EM sets the shared PNF as a service for terminating the target network slice instance, without affecting other network slice instances that use the shared PNF. Service.

Specifically, when the target network slice instance includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM that manages the dedicated PNF through the Itf-N interface, and indicates that the EM managing the shared PNF sets the dedicated PNF as the termination target. The service of the network slice instance, the request includes but is not limited to: instructing the EM to stop providing the service to the target network slice instance, deleting configuration parameters for supporting the target network slice instance service, such as a network slice instance identifier, and deleting the service target network slice instance. Policy, terminating/deleting the network connection between the PNF and the target network slice instance-specific network function.

Further, the EM managing the dedicated PNF executes the request and feeds back the execution result. If the EM is built into the PNF, NSM&O closes/deregisters the virtual port of the dedicated PNF; otherwise the EM closes/deregisters the virtual port of the PNF.

It should be understood that the shared PNF may also be referred to as a general-purpose PNF, and the shared VNF may also be referred to as a general-purpose VNF. Among them, the dedicated network function refers to the function exclusive to the target network slice, and is not shared with other network slice instances; and the shared network function refers to the PNF that multiple network slice instances can share.

Optionally, as an embodiment of the present application, the PNF management device includes an EM, and the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: when the target network slice embodiment corresponds to When the VNF includes a shared VNF, the EM indicating that the shared VNF is managed configures the shared VNF to terminate the service to the target network slice instance.

That is, when the VNF in the target network slice instance includes the shared VNF, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, indicating that the EM managing the shared VNF sets the shared VNF. To terminate the service to the target network slice instance, the request includes but is not limited to: instructing the EM to stop providing the service to the target network slice instance, deleting the configuration parameters used to support the target network slice instance service, such as the network slice instance identifier, and deleting the service target. The strategy of the network slice instance.

Further, the EM managing the shared VNF executes the request and feeds back the execution result.

Further, the NSM&O notifies the VIM to terminate/close the possible network connection between the shared VNF and the target network slice instance-specific network function, and release the corresponding network resource. VIM executes the request and feeds back the execution results.

Optionally, as an embodiment of the present application, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: instructing the virtualization infrastructure management device VIM to configure the shared VNF as a termination and target Networking instance related network connections, and/or shrinking network resources associated with the target network slice instance, wherein the VNF management device includes the VIM; or instructing NFVO to configure the shared VNF as Terminating a network connection associated with the target network slice instance and/or shrinking network resources associated with the target network slice instance, wherein the VNF management device includes the NFVO.

Optionally, as an embodiment of the present application, the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: when the VNF corresponding to the target network slice instance includes a dedicated VNF, indicating The EM termination of the dedicated VNF is managed to manage the dedicated VNF.

Optionally, as an embodiment of the present application, the VNF management device includes a VIM and a VNF management device VNFM, and the controlling the VNF management device to terminate the VNF corresponding to the target network slice instance includes: indicating the VNFM termination The dedicated VNF; instructing the VIM to close a network connection associated with the dedicated VNF, and/or release network resources associated with the second VNF.

Specifically, the NSM&O sends the information used to delete and release the VNFs to the VIM according to the information supporting the resources (including computing, storage, and network resources) used to run the dedicated VNF and the dedicated network connection information supporting the running of the network slice instance. The request for the network connection; the VIM performs the deletion required by the NSM&O, releases the resources used by the VNF, and deletes the request for the network connection exclusive to the network slice instance; the VIM returns the NSM&O feedback deletion and release completion confirmation.

Optionally, as an embodiment of the present application, the VNF management device includes an NFVO, where the VNF management device is configured to terminate the VNF corresponding to the target network slice instance, and the target network slice embodiment is terminated, including: Instructing the NFVO to close a network connection associated with the dedicated VNF and/or release network resources associated with the shared VNF.

Specifically, the NSM&O notifies the NFVO to terminate the target NSI-specific VNF and deletes the connection with the target NSI-specific network; the NFVO performs the slice-specific VNF termination process and the dedicated network connection deletion process; the NFVO to NSM&O feedback has completed the termination and deletion process of the above-mentioned exclusive VNF.

Optionally, as an embodiment of the present application, the dedicated VNF corresponding to the target network slice instance is a VNF generated by the NSM&O.

For example, in the target network slice instantiation process, the VNF generated by the NM, the NSM&O initiates a request to configure the network function to the EM managing the VNF. The request includes, but is not limited to, stopping the service provided to the target NSI, deleting the configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deleting the policy of the service target NSI. The EM executes the request and feeds back the execution results. NSM&O informs NFVO to terminate/close the possible network connection between the VNF and the target NSI-specific network function, and release the corresponding network resources. NFVO performs the request and feeds back the execution results.

It should be understood that all VNFs and/or PNFs included in the target network slice instance may be terminated as described above. When all VNFs and/or PNFs included in the target network slice instance are terminated, it means that the target network slice instance is terminated. It is also finished.

Optionally, as an embodiment of the present application, the method further includes: sending a notification message to the network management device NM, where the notification message is used to notify the NM to perform network slice management on the target network slice.

Optionally, as an embodiment of the present application, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message, including: when the management request message is When the target network slice is deleted, the PNF management device and/or the VNF management device are controlled to delete the target network slice.

Optionally, as an embodiment of the present application, the controlling the PNF management device and/or the VNF management device to delete the target network slice includes: controlling the PNF management device and/or the VNF management device, and terminating the The VNF and/or PNF corresponding to each of the instances in the target network slice.

That is, when the foregoing management request message is used to delete the target network slice, all instances in the target network slice need to be terminated according to the management request message, and the VNF and/or PNF termination method corresponding to each instance is similar to the foregoing method. I will not repeat them here.

Optionally, as an embodiment of the present application, the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message includes: when determining the target network slice After all instances in the terminal are terminated, the memory is instructed to delete the slice template of the target network slice.

Optionally, as an embodiment of the present application, before the controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request, the method further includes: Verifying whether the sender that initiated the management request message has the right to manage the network slice of the target network slice.

Optionally, as an embodiment of the present application, the verifying whether the sending end of the management request message has the right to manage the network slice of the target network slice includes: sending a verification message to the memory, where the verification message is sent Determining, by the memory, whether the sending end has the right to perform network slice management on the target network slice; receiving the verification completion message of the memory feedback, where the verification completion message is used to notify the NSM&O whether the sending end is Having the target network slice for network slice management.

Optionally, as an embodiment of the present application, the method further includes: when determining that the sending end does not have the right to manage the network slice of the target network slice, sending a verification failure message to the sending end, where The verification failure message is used to notify the sender that there is no right to perform network slice management on the target network slice.

Optionally, as an embodiment of the present application, the method further includes: when the NSM&O completes management of the target network slice, sending a management complete message to the sending end, where the management complete message is used to notify the The sender has completed the deletion of the target network slice or the termination of the target network slice instance.

FIG. 8 is a schematic flowchart of a method for managing a network slice according to another embodiment of the present application. The execution body of the method may be a sending end. As shown in FIG. 8, the method includes:

Step 810: The sender sends a management request message of the target network slice to the NSM&O, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target network slice instance.

Step 820: The sending end receives the management complete message sent by the NSM&O, where the management complete message is used to determine that the NSM&O completes the deletion of the target network slice or the termination of the target network slice instance.

Optionally, as an embodiment of the present application, the method further includes: receiving a verification failure message sent by the NSM&O, where the verification failure message is used to notify that the target network slice management cannot be performed.

FIG. 9 is a schematic flowchart of a method for managing a network slice according to still another embodiment of the present application. The execution body of the method is a memory. As shown in FIG. 9, the method includes:

Step 910: The memory receives an authentication message of the NSM&O, where the verification message is used to verify whether the sending end that initiates the network slice management request has the right to perform network slice management on the target network slice.

Step 910: The memory verifies, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.

Optionally, as an embodiment of the present application, the returning the verification completion message to the NSM&O, so that the NSM&O determines whether to manage the target network slice according to the verification feedback message, including: The NSM&O returns a verification completion message, where the verification completion message is used to notify the NSM&O whether the sender has the right to perform network slice management on the target network slice; when the sender does not have the slice on the target network When the network slice management authority or the instance of the target network slice does not exist, the verification feedback message is used to notify the NSM&O that the sender does not have the right to perform network slice management on the target network slice; or when When the sending end has the network slice management right of the target network slice, the verification feedback message is used to notify the NSM&O that the sending end has the right to perform network slice management on the target network slice.

FIG. 10 shows a schematic block diagram of a network architecture of an embodiment of the present application.

The network architecture 1 (option 1) shown in FIG. 10 is an improvement to the existing 3GPP operation support system (OSS) (the embodiment shown in FIG. 4), and the NSM&O can implement the original 3GPP. The function of NM in the network architecture. Specifically, the NSM&O interacts with the EM through the Itf-N interface to implement management including the PNF and the VNF; for example, the PNF in FIG. 10 may be the NE, and the NSM&O receives the status information about the VNF from the NFVO through the Os-Ma-nfvo interface, and passes This interface sends instructions to NFVO to participate in the lifecycle management process of the VNF.

Therefore, the network architecture undergoes evolution and upgrade on the OSS system, and changes to the existing network architecture and interface are small. NSM&O can directly manage the PNF, and implement NFVI resource management and VNF generation by using NFVO.

FIG. 11 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application. FIG. 11 is a flow chart showing the flow of network slice management based on the network structure shown in FIG.

As shown in FIG. 11, the method includes:

In step 1101, the sender sends a target network slice instance termination request or a target network slice deletion request to the NSM&O.

It should be understood that the request in step 1101 may be a specific implementation in the management request message in the example described in FIG. 7, which is not limited in this application.

Specifically, the target network slice instance termination request may include an identifier of the target network slice instance, an identity of the sender, and the like. The target network slice deletion request may include an identifier of the NSLD corresponding to the network slice, an identity of the sender, and the like. The sender may be an authorized third-party tenant, carrier, or an application that has the right to terminate the network slice instance/delete network slice.

Step 1102, authenticate, authenticate, verify, and check the target network slice (or target network slice instance).

Specifically, after receiving the target network slice instance termination request or the target network slice deletion request sent by the sending end, the NSM&O needs to perform information interaction with the memory, and authenticate the identity of the sending end through the memory, and verify the integrity of the parameter in the request (eg, Whether the target network slice instance identifier format is correct, whether the NSLD identifier format corresponding to the target network slice is correct, etc., whether the authentication sender end has permission to terminate the requested target network slice instance or delete the target network slice. At the same time, NSM&O checks whether the target network slice instance exists and the target network slice instance runs, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.

When the request sent by the sender is the termination target network slice instance in step 1101, the following steps are performed:

If the authentication fails, the step 1102' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to terminate the slice instance, and cannot verify the identity of the sending end;

If the authentication authentication is passed and the target network slice instance exists, step 1103 is performed;

If the verification authentication is passed but the network sharding instance does not exist, step 1102' is performed, that is, the NSM&O feeds back a parameter error to the transmitting end, and informs the transmitting end that the target network sharding instance does not exist.

Alternatively, when the request sent by the sender is to delete the target network slice in step 1101, the following steps are performed:

If the verification authentication fails, step 1102' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to delete the network slice, and cannot verify the identity of the sending end;

If the verification authentication succeeds and the NSLD corresponding to the target network slice exists, after deleting all the instances of the target network slice, the NSM&O performs step 1112 again to delete the NSLD corresponding to the target network slice.

If the NSLD corresponding to the target network segment does not exist, NSM&O feeds back the parameter error to the sender, and informs the sender that the target network slice does not exist.

It should be understood that steps 1101 to 1102 or step 1102' are specific interaction flows for the NSM&O to verify whether the sender of the management request message has the right to manage the network slice of the target network slice.

Step 1103: The NSM&O controls the EM and the NFVO to perform the configuration network function, delete the configuration related to the target network slice instance, and the network connection, and specifically includes:

NSM&O checks whether the target network slice instance to be terminated (referred to as the target NSI) and other network slice instances have shared common network functions, including shared VNF and shared PNF; and whether NSM&O detects the target NSI that needs to be terminated to have exclusive network functions.

(1) When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the Itf-N interface, indicating that the EM managing the shared PNF sets the shared PNF to terminate the target NSI. Service, the request includes but is not limited to: instructs the EM to stop sharing the PNF service provided to the target NSI Delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, the policy of deleting the service target NSI, and terminate/delete the network connection between the PNF and the target NSI-specific network function.

Further, the EM managing the shared PNF executes the request and feeds back the execution result.

Further, the above configuration steps are repeated until all shared PNFs in the target NSI terminate the service to the target NSI.

It should be understood that (1) in step 1103 indicates that the NEM&O indicates that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating the service to the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, indicating that the EM managing the shared VNF sets the shared VNF to terminate the target NSI. The service includes, but is not limited to, instructing the EM to stop sharing the service provided by the VNF to the target NSI, deleting the configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deleting the policy of the service target NSI.

Further, NSM&O notifies the NFVO to terminate the shared VNF of the target NSI through the Os-Ma-nfvo interface, indicating that the NFVO shrinks the resources of the shared VNF without affecting the services of other network slice instances.

It should be understood that (2) in step 1103 indicates that the NSM&O indicates that the EM managing the shared VNF configures the shared VNF as a specific interaction procedure for terminating the service to the target network slice instance.

Further, the above steps are repeated until all shared VNFs in the target NSI are configured to terminate the service to the target NSI.

Further, in step 1103, the NSM&O detects whether the target NSI that needs to be terminated has a dedicated network function.

(3) When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the Itf-N interface, indicating that the EM managing the dedicated PNF sets the dedicated PNF to terminate the target NSI. Service, the request includes but is not limited to: instructing the EM to stop the service provided by the dedicated PNF to the target NSI, deleting configuration parameters for supporting the target NSI service such as the network slice instance identifier, deleting the policy of the service target NSI, and terminating/deleting the PNF and the target Network connection between NSI-specific network functions, etc.

Further, the EM managing the dedicated PNF executes the request and feeds back the execution result. If the EM is built into the PNF, NSM&O closes/deregisters the virtual port of the PNF; otherwise the EM closes/deregisters the virtual port of the PNF.

It should be understood that (3) in step 1103 indicates that the NEM&O indicates that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating the service to the target network slice instance. At this time, the first PNF is a dedicated PNF.

Further, the above steps are repeated until all the dedicated PNFs in the target NSI are configured to terminate the service to the target NSI.

(4) When the target NSI includes a dedicated VNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated VNF through the Itf-N interface, indicating that the EM managing the dedicated VNF sets the dedicated VNF to terminate the target NSI. The service, at the same time, terminates the management of the exclusive VNF by the EM, that is, the step 1104 in the process shown in FIG. 11, terminating the exclusive VNF management request, the request includes but not limited to: indicating to stop monitoring the VNF running state, terminating the VNF Management function to delete management objects.

If the shared NNF of the target NSI, the exclusive VNF, the shared PNF, and the proprietary PNF have been terminated, the network The slice instance has been terminated and step 1114 is performed.

It should be understood that the foregoing process of terminating the shared PNF, the dedicated PNF, the shared VNF, and the dedicated VNF does not have a sequence of requirements for the process of the target network slicing service, which is not limited in this application.

In step 1105, the management object of the VNF is deleted, that is, the EM that manages the exclusive VNF performs the NSM&O request to terminate the VNF management in step 1104.

In step 1106, the feedback VNF management object is terminated, that is, the EM managing the dedicated VNF is confirmed to the NSM&O feedback termination management through the Itf-N interface.

In step 1107, the NSM&O notifies the EM that manages the dedicated VNF to close the virtual port of the dedicated VNF through the Itf-N interface, and stops the service to the target NSI.

In step 1108, the NSM&O informs the NFVO to terminate the target NSI-specific VNF through the Os-Ma-nfvo interface and deletes the connection with the target NSI-specific network.

In step 1109, the NFVO performs a slice-specific VNF termination process and a dedicated network connection deletion process.

In step 1110, the feedback VNF termination is completed, that is, the NFVO feedback to the NSM&O through the Os-Ma-nfvo interface has completed the termination and deletion process of the above-mentioned exclusive VNF.

It should be understood that steps 1104 through 1110 indicate to NSM&O that the EM managing the dedicated VNF configures the dedicated VNF as a specific interaction flow for terminating services to the target network slice instance.

Step 1111: Update the slice instance. Specifically, if there are other functions in the dedicated network function of the target NSI that are not implemented by the exclusive VNF, the steps 1104 to 1110 are repeated. If all the VNFs and PNFs corresponding to the target NSI have been terminated. If the target NSI has been terminated, NSM&O deletes the information of the target NSI in the memory slice instance. If the sender sends a network slice instance termination request in step 1101, step 1114 is performed, otherwise step 1112 is performed.

Optionally, in step 1112, NSM&O checks the status of the network slice instance instantiated by the NSLD of the target network slice to be deleted. If there is an unterminated network slice instance in the target network slice, step 1103-1111 is repeated for the slice instance. If there is no network slice instance generated according to the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used. . If the NSLD is being used, the feedback network slice is deleted incorrectly. If the NSLD is not being used, step 1113 is performed.

Optionally, in step 1113, NSM&O deletes the NSLD of the current target network slice in the memory.

It should be understood that step 1112 and step 1113 need to be performed only when the sender sends a network slice deletion request.

Step 1114, notifying the sender that the network slice instance termination/network slice deletion is completed.

Therefore, the present application controls the PNF management device and the VNF management device, supports network slice management, and supports direct programming management of the PNF. For the VNF, the NFV MANO system management orchestration is used to support the network slice instance termination and network slice deletion in the system architecture. In this application, the third-party tenant that can allow the operator or the authorized network slice instance to discover that the existing slice instance cost is higher than the benefit of the service is requested to terminate the network slice instance, and the operator is allowed to decide not to support the current When a type network is sliced, such as a network slice version upgrade, the network slice is requested to be deleted.

In addition, the present application separately manages the common network function shared by the network slice instance and other slice instances and the slice-specific network function in the embodiment, so that the termination of the current network slice instance does not affect the services of other network slice instances.

FIG. 12 shows a schematic flow chart of a management network slice of an embodiment of the present application. Figure 12 is the step in Figure 11 Detailed flow chart of step 1103.

Specifically includes:

When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM that manages the shared PNF through the Itf-N interface, that is, in step 1103_1, a configuration sharing PNF request is sent, indicating that the EM managing the shared PNF will The shared PNF is set to terminate the service to the target NSI, and the request includes, but is not limited to, indicating that the EM stops sharing the PNF to provide the service provided by the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deleting the service target NSI. The strategy of terminating/deleting the network connection between the PNF and the target NSI-specific network functions.

Further, the EM managing the shared PNF executes the request and feeds back the execution result, that is, step 1103_2, the EM configures the shared PNF.

Further, in step 1103_3, the confirmation configuration completion message is sent, and the foregoing configuration steps are repeated until all the shared PNFs in the target NSI are configured to terminate the service to the target NSI.

When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, that is, in step 1103_4, sending a configuration sharing VNF request indicating that the EM managing the shared VNF will The shared VNF is set to terminate the service to the target NSI, and the request includes but is not limited to: instructing the EM to stop sharing the VNF to provide the service provided by the target NSI, deleting configuration parameters for supporting the target NSI service, such as a network slice instance identifier, and deleting the service target NSI. Strategy.

Further, the EM managing the shared VNF executes the request and feeds back the execution result, that is, step 1103_5, the EM configures the shared VNF and the step 1103_6, and the EM returns a configuration complete confirmation message to the NSM&O.

Further, the NSM&O informs the NFVO to terminate the shared VNF of the target NSI through the Os-Ma-nfvo interface, and instructs the NFVO to shrink the resources of the shared VNF without affecting the services of other network slice instances, that is, step 1103_7, indicating that the VNF resources are shrunk. .

Step 1103_8, NFVO shrinks the VNF resource under the direction of step 1103_8.

After the NFVO completes the contraction of the shared VNF resources, the NSM&O is fed back to the shrink complete message, which is step 1103_9.

When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the Itf-N interface, that is, step 1103_10, sending a configuration-specific PNF request to the EM, indicating that the EM managing the dedicated PNF will be The dedicated PNF is set to terminate the service to the target NSI, and the request includes, but is not limited to, indicating that the EM stops the dedicated PNF to provide the service to the target NSI, deletes the configuration parameter used to support the target NSI service, such as the network slice instance identifier, and deletes the service target. NSI's strategy to terminate/delete network connections between PNF and target NSI-specific network functions.

Further, the EM managing the dedicated PNF executes the request and feeds back the execution result. If the EM is built in PNF, NSM&O closes/deregisters the virtual port of the PNF; otherwise the EM closes/deregisters the virtual port of the PNF, specifically, corresponding to steps 1103_11 and 1103_12 in FIG.

It should be understood that the label size of the above steps does not represent the execution order, and it should be understood that, in the specific implementation process, according to For the specific case of the target network sharding instance, some or all of the steps may be selected, which is not limited in this application.

FIG. 13 shows a schematic block diagram of a network architecture of an embodiment of the present application.

The network architecture 2 (option 2) shown in FIG. 13 is an improvement to the existing 3GPP OSS system (such as the embodiment shown in FIG. 4), and the NSM&O can implement the function of the NM in the original 3GPP network architecture. Specifically, the NSM&O interacts with the EM to implement the management of the PNF and the VNF through the Itf-N interface; the NSM&O interacts with the VNFM through the NG1 interface, and the NSM&O interacts with the VIM through the NG2 interface to participate in the VNF. The lifecycle management process, other interfaces do not change compared to architecture 1. The interface between the NSM&O and the VNFM is temporarily called the NG1 interface, and the interface between the NSM&O and the VIM is temporarily called the NG2 interface.

Specifically, the functions of the NG1 interface mainly include: authorization, reservation, allocation, and release of NFVI resources for supporting the VNF; querying information of the running state; initializing, updating, scaling, and terminating the VNF, and transmitting events related to the VNF, Status information, etc.

The functions of the NG2 interface mainly include: NFVI resource reservation, allocation, release, etc.; VNF software addition, deletion, update, etc.; transmission of configuration information, events, measurement results, upgrade records, etc. related to NFVI.

Therefore, the network architecture is upgraded and upgraded on the OSS system, and the changes to the existing network architecture and interfaces are small. NSM&O adds functions for virtual resources and VNF lifecycle management, and uniformly manages and orchestrate physical and virtual network resources. And features that help optimize resources from a global perspective.

FIG. 14 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application. FIG. 14 is a flow chart showing the flow of network slice management based on the network structure shown in FIG.

As shown in FIG. 14, the method includes:

In step 1401, the sender sends a target network slice instance termination request or a target network slice deletion request to the NSM&O.

It should be understood that the request in step 1401 may be a specific implementation manner in the management request message in the example described in FIG. 7 , which is not limited in this application.

Step 1402, authenticate, authenticate, verify, and check the target network slice (or target network slice instance).

When the request sent by the sender is the termination target network slice instance in step 1401, the following steps are performed:

If the verification authentication fails, step 1402' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to terminate the slice instance, and the identity of the sending end cannot be verified;

Alternatively, when the request sent by the sender is to delete the target network slice in step 1401, the following steps are performed:

If the authentication fails, the step 1402' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to delete the network slice, and cannot verify the identity of the sending end;

If the authentication is passed and the NSLD corresponding to the target network slice exists, after all the instances of the target network slice are deleted, the NSM&O performs step 1415 to delete the NSLD corresponding to the target network slice.

It should be understood that steps 1401 to 1402 or step 1402' are a specific interaction flow for the NSM&O to verify whether the sender of the management request message has the right to manage the network slice of the target network slice.

Step 1403: The NSM&O checks whether the target network slice instance to be terminated (referred to as the target NSI) and other network slice instances have shared common network functions, including the shared VNF and the shared PNF; and whether the NSM&O detects the target NSI that needs to be terminated. Internet function.

(1) When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the Itf-N interface, indicating that the EM managing the shared PNF sets the shared PNF to terminate the target NSI. The service includes, but is not limited to, instructing the EM to stop sharing the PNF to provide the service to the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, deleting the service target NSI policy, and terminating/deleting the PNF and Network connection between target NSI-specific network functions, etc.

Further, the above configuration steps are repeated until all shared PNFs in the target NSI are configured to terminate the service to the target NSI.

It should be understood that (1) in step 1403 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating services to the target network slice instance. At this time, the first PNF is a shared PNF.

Further, the NSM&O notifies the VIM to terminate/close the possible network connection between the shared VNF and the target NSI-specific network function through the NG2 interface, and release the corresponding network resource. The VIM executes the request and feeds back the execution result through the NG2 interface.

Further, in step 1403, the NSM&O detects whether the target NSI that needs to be terminated has a dedicated network function.

It should be understood that (2) in step 1403 indicates to NSM&O that the EM that manages the shared VNF configures the shared VNF as a specific interaction flow to terminate the service to the target network slice instance.

(3) When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the Itf-N interface, indicating that the EM managing the dedicated PNF sets the dedicated PNF to terminate the target NSI. Service, the request includes but is not limited to: instructing the EM to stop sharing the PNF to provide services to the target NSI, deleting configuration parameters for supporting the target NSI service, such as a network slice instance identifier, deleting a service target NSI, and terminating/deleting the PNF and target. Network connection between NSI-specific network functions, etc.

It should be understood that (3) in step 1403 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating the service to the target network slice instance. At this time, the first PNF is a dedicated PNF.

(4) When the target NSI includes a dedicated VNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated VNF through the Itf-N interface, indicating that the EM managing the shared VNF sets the dedicated VNF to terminate the target NSI. The service, at the same time, configures the EM to terminate the management of the dedicated VNF, that is, the step 1404 in the process shown in FIG. 14, the request includes, but is not limited to, indicating that the monitoring of the VNF running state is stopped, and the management function of the VNF is terminated. Delete the management object.

If the shared VNF, the dedicated VNF, the shared PNF, and the dedicated PNF of the target NSI have been terminated, the network slice instance is terminated, and step 1414 is performed.

Step 1405, the EM managing the dedicated VNF performs the NSM&O request to terminate the VNF management in step 1404.

In step 1406, the EM managing the dedicated VNF is fed back to the NSM&O through the Itf-N interface to complete the management.

In step 1407, the NSM&O notifies the EM that manages the dedicated VNF to close the virtual port of the dedicated VNF through the Itf-N interface, and stops the service to the target NSI.

Step 1408: The NSM&O initiates a terminal-specific VNF request to the VNFM through the NG1 interface, where the request includes terminating the service that is running on the target NSI, and closing the dedicated VNF.

Step 1409, the VNFM performs the NSM&O in step 1408 to terminate the service that is running on the dedicated VNF, and the VNFM and VNF internal mechanisms jointly close the VNF.

Optionally, in step 1410, the VNFM feeds back the completion message of the dedicated VNF to the NSM&O through the NG1 interface.

In step 1411, the NSM&O sends and deletes and releases the VNFs to the VIM through the NG2 interface according to the information of the resources (including the computing, storage, and network resources) used to run the dedicated VNF and the network connection information that supports running the network slice instance. Requests for resources and network connections.

In step 1412, the VIM performs the deletion required by the NSM&O in step 1411, releases the resources used by the VNFs, and deletes the request for the network connection exclusive to the network slice instance.

In step 1413, the VIM sends a feedback deletion and release completion confirmation to the NSM&O through the NG2 interface.

It should be understood that steps 1404 through 1413 indicate to NSM&O that the EM managing the dedicated VNF configures the dedicated VNF to terminate the specific interaction flow for the service to the target network slice instance.

Step 1414: If the function of the dedicated NNF in the target network of the target NSI is not terminated, the steps 1404 to 1413 are repeated. If all the VNFs and PNFs corresponding to the target NSI have been terminated, the target NSI is terminated. NSM&O deletes the information of the target NSI in the memory slice instance. If the sender sends a network slice instance termination request in step 1401, step 1417 is performed, otherwise step 1415 is performed.

Optionally, in step 1415, the NSM&O checks the status of the network slice instance instantiated by the NSLD of the target network slice to be deleted. If there is an unterminated network slice instance in the target network slice, repeat steps 1403-1414 for the slice instance. If there is no network slice instance generated according to the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used. . If the NSLD is being used, the feedback network slice is deleted incorrectly. If the NSLD is not being used, step 1416 is performed.

Optionally, in step 1416, NSM&O deletes the current version of NSLD in memory.

It should be understood that step 1415 and step 1416 need to be performed only when the sender sends a network slice deletion request.

Step 1417, notifying the sender that the network slice instance termination/network slice deletion is completed.

FIG. 15 shows a schematic flow chart of a management network slice of an embodiment of the present application. Figure 15 is a detailed flow chart of step 1403 of Figure 14.

Specifically includes:

When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the Itf-N interface, that is, step 1403_1, sending a configuration sharing PNF request indicating that the EM managing the shared PNF shares the share. The PNF is set to terminate the service to the target NSI, the request includes but is not limited to: instructing the EM to stop sharing the PNF to provide the service provided by the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deleting the service target NSI. Policy, terminating/deleting network connections between PNF and target NSI-specific network functions, etc.

Further, the EM managing the shared PNF executes the request and feeds back the execution result, that is, step 1403_2, the EM configures the shared PNF.

Further, in step 1403_3, a confirmation configuration completion message is sent.

The above configuration steps are repeated until all shared PNFs in the target NSI are configured to terminate the service to the target NSI.

When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, that is, step 1403_4, sending a configuration sharing VNF request indicating that the EM managing the shared VNF will The shared VNF is set to terminate the service to the target NSI, and the request includes but is not limited to: The EM stops sharing the service provided by the VNF to the target NSI, deletes the configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deletes the policy of the service target NSI.

Further, the EM managing the shared VNF executes the request and feeds back the execution result, that is, step 1403_5, the EM configures the shared VNF and the step 1403_6, and the EM returns a configuration completion confirmation message to the NSM&O.

Step 1403_7, informing the VNFM to shrink the resources of the shared VNF through the NG1 interface.

Step 1403_8, VNFM performs the shrinkage feasibility test. Specifically, two things are to be done: i) check whether the shrinkage requirements of NSM&O meet the specifications, if not, modify the parameters and then feed back to NSM&O; ii) if shrinking VNF involves Close some of the virtual machine VMs that make up the VNF, and the VNFM puts these virtual machines.

In step 1403_9, the VNFM returns a shrink confirmation message to the NSM&O.

Further, the NSM&O notifies the VIM to terminate/close the possible network connection between the shared VNF and the target NSI-specific network function through the NG2 interface, that is, step 1403_10, sends a connection request to the VIM, and optionally requests a resource allocation change. Release the corresponding network resources.

In step 1403_11, the VIM executes the request, and in step 1403_12, it is notified that the NSM&O has deleted the connection, releases the resource, and feeds back the execution result through the NG2 interface.

Further, in step 1403_13, the VNFM also needs to configure the contracted VNF deployment parameters according to the configuration result of step 1403_12.

In step 1403_14, the VNFM sends a configuration shrink end feedback to the NSM&O.

When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the Itf-N interface, that is, step 1403_15, sending a configuration-specific PNF request to the EM, indicating that the EM managing the dedicated PNF will be The dedicated PNF is set to terminate the service to the target NSI, and the request includes, but is not limited to, indicating that the EM stops sharing the PNF to provide the service provided by the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, and deleting the service target. NSI's strategy to terminate/delete network connections between PNF and target NSI-specific network functions.

Further, in step 1403_15 and step 1403_16, the EM managing the dedicated PNF executes the request, that is, configures the contracted VNF deployment parameters and feeds back the execution result. If the EM is built into the PNF, NSM&O closes/deregisters the virtual port of the PNF; otherwise the EM closes/deregisters the virtual port of the PNF.

It should be understood that the label size of the above steps does not represent the execution order. It should be understood that, in the specific implementation process, some or all of the steps may be selected according to the specific situation of the target network slice instance, which is not limited in this application.

Figure 16 shows a schematic block diagram of a network architecture of one embodiment of the present application.

The network architecture 3 (option 3) shown in FIG. 16 is an improvement to the existing 3GPP OSS system (such as the embodiment shown in FIG. 4), and the NSM&O can implement the function of the NM in the original 3GPP network architecture. Specifically, NSM&O interacts with the EM through the NG5 interface to implement management of the PNF and the VNF; the NSM&O is independent of the existing NM system, does not make any upgrade changes to the NM system, and introduces a new slice management and system, wherein NSM&O The interface between the NSM&O and the NFVO is temporarily called the NG4 interface, and the interface between the NSM&O and the EM is temporarily called the NG5 interface.

Specifically, the functions of the NG3 mainly include: transmitting the negotiation information between the NSM&O and the NM, for example, the NSM&O queries the NNF that has been generated by the NM; the NM feeds back the VNF information that has been generated by the NSM&O, and confirms that the modification is allowed; and the NSM&O notifies the NM which PNF is to be used. /VNF is modified; NSM&O notifies NM of specific changes to PNF/VNF.

The functions of NG4 mainly include: NSM&O participates in VNF lifecycle management through this interface, such as notifying NFVO to generate, update, and delete a VNF; NSM&O queries NFVO, NFVO feeds back NNF&O to report VNF and NFVI operation information; policy management, NSM&O can The NFVO sends a policy that indicates the need for VNF deployment; NSM&O performs VNF package management through this interface.

The functions of NG5 mainly include: If EM supports the management of VNF, NSM&O communicates with EM through this interface to manage PNF and VNF.

Therefore, the network architecture does not change the existing network architecture and interface by evolving and upgrading on the OSS system. The architecture does not need to change the NM, but provides a new management system, which requires a new interface and an existing interface. Each entity interacts. Both NSM&O and NM can directly manage PNF, and NSM&O and NM can manage VNF through NFVO or EM; further, NSM&O can manage virtual resources through NFVO orchestration.

FIG. 17 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application. FIG. 17 is a flow chart showing the flow of network slice management based on the network structure shown in FIG.

As shown in FIG. 17, the method includes:

Step 1701: The sender sends a target network slice instance termination request or a target network slice deletion request to the NSM&O.

It should be understood that the request in step 1701 may be a specific implementation in the management request message in the example described in FIG. 7, which is not limited in this application.

Step 1702, authenticate, authenticate, verify, and check the target network slice (or target network slice instance).

When the request sent by the sender is the termination target network slice instance in step 1701, the following steps are performed:

If the authentication fails, the step 1702' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to terminate the slice instance, and cannot verify the identity of the sending end;

If the authentication authentication is passed and the target network slice instance exists, step 1703 is performed;

If the verification authentication is passed but the network slice instance does not exist, step 1702' is performed, that is, the NSM&O feeds back a parameter error to the sender, and informs the sender that the target network slice instance does not exist.

Alternatively, when the request sent by the sender is to delete the target network slice in step 1701, the following steps are performed:

If the authentication fails, the step 1702' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to delete the network slice, and cannot verify the identity of the sending end;

If the verification authentication passes and the NSLD corresponding to the target network slice exists, after all the network slice instances included in the target network slice are terminated, the NSM&O performs step 1714;

It should be understood that steps 1701 to 1702 or step 1702' are a specific interaction flow for the NSM&O to verify whether the sender of the management request message has the right to manage the network slice of the target network slice.

In step 1703, the NSM&O notifies the NM that the network function is to be configured. Specifically, the NSM&O notifies the NM that the PNF and the VNF that are jointly managed by the NM are adjusted through the NG3 interface to prevent the conflict, and the notification needs to include at least the involved Identification of PNF and VNF.

In step 1704, the NM returns an acknowledgement to the NSM&O, that is, after receiving the notification, the NM receives a notification confirmation from the NMM&O through the NG3 interface. These PNFs and VNFs are no longer monitored before the NM receives the NSM&O modification completion message, and the configuration is modified.

Step 1705: The NSM&O checks whether the target network slice instance to be terminated (referred to as the target NSI) and other network slice instances have shared common network functions, including the shared VNF and the shared PNF; and whether the NSM&O detects whether the target NSI needs to be terminated or not. Internet function.

(1) When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the NG5 interface, indicating that the EM managing the shared PNF sets the shared PNF to terminate the service to the target NSI. The request includes but is not limited to: instructing the EM to stop sharing the PNF to provide the service to the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, deleting the service target NSI, and terminating/deleting the PNF and the target NSI. Network connections between proprietary network functions, etc.

It should be understood that (1) in step 1705 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating services to the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the shared NNF is included in the target NSI, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the NG5 interface, indicating that the EM managing the shared VNF sets the shared VNF to terminate the service to the target NSI. The request includes, but is not limited to, indicating that the EM stops sharing the service provided by the VNF to the target NSI, and deletes a configuration parameter for supporting the target NSI service, such as a network slice instance identifier, and a policy of deleting the service target NSI.

Further, the NSM&O informs the NFVO to terminate the shared VNF of the target NSI through the NG4 interface, and instructs the NFVO to shrink the resources of the shared VNF without affecting the services of other network slice instances.

Further, in step 1705, the NSM&O detects whether the target NSI that needs to be terminated has a dedicated network function.

It should be understood that (2) in step 1705 indicates to NSM&O that the EM that manages the shared VNF configures the shared VNF to terminate a specific interaction flow for the service to the target network slice instance.

(3) When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the NG5 interface, and instructs the EM managing the dedicated PNF to set the dedicated PNF to terminate the service to the target NSI. The request includes but is not limited to: instructing the EM to stop the service provided by the dedicated PNF to the target NSI, deleting configuration parameters for supporting the target NSI service, such as the network slice instance identifier, deleting the service target NSI, and terminating/deleting the PNF and the target NSI exclusive. Network connection between network functions, etc.

It should be understood that (3) in step 1705 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating services to the target network slice instance. At this time, the first PNF is a dedicated PNF.

It should also be understood that the interaction process of step 1705 is similar to the interaction process in FIG. 12, and details are not described herein again.

(4) When the target NSI includes a dedicated VNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated VNF through the NG5 interface, indicating that the EM managing the dedicated VNF sets the dedicated VNF to terminate the service to the target NSI. At the same time, the management of the exclusive VNF is terminated, that is, the step 1706 in the process shown in FIG. 17, the NSM&O sends a termination-specific VNF management request to the EM, and the request includes, but is not limited to, indicating that the monitoring of the VNF running state is stopped, and the terminal is terminated. The management function of the VNF removes the management object.

It should be understood that if the above-mentioned exclusive VNF is not generated by NSM&O, such as a dedicated VNF generated by NM, then NSM&O may indicate that the PNF device and the VNF device are configured to turn off the service of the dedicated VNF to the target network slice instance, and cannot terminate the exclusive VNF. The service to the target network slice instance.

If the shared VNF, the dedicated VNF, the shared PNF, and the dedicated PNF of the target NSI have been terminated, the network slice instance is terminated, and step 1716 is performed.

Step 1707, the EM managing the exclusive VNF performs the NSM&O request to terminate the exclusive VNF management in step 1706, and deletes the management object of the exclusive VNF.

In step 1708, the EM managing the dedicated VNF passes the NG5 interface to the NSM&O feedback termination management completion confirmation, and feeds back the VNF management object termination completion message.

Step 1709, NSM&O or EM closes/deregisters the virtual port of the VNF, and the NSM&O informs the EM that manages the dedicated VNF through the NG5 interface to close the virtual port of the dedicated VNF, and stops the service to the target NSI.

In step 1710, the NSM&O initiates a request to terminate the exclusive VNF to the NFVO through the NG4 interface, the request including terminating the service that is running on the dedicated VNF.

In step 1711, the NFVO performs the NSM&O in step 1710 to terminate the service that is running on the dedicated VNF, terminate the exclusive VNF, and delete the exclusive connection of the exclusive VNF.

Optionally, in step 1712, the NFVO feeds back to the NSM&O through the NG4 interface to terminate the completion of the exclusive VNF. interest.

In step 1713, the NSM&O informs the NM configuration that the corresponding PNF and VNF in the target network slice instance have been terminated by the NG3 interface, and the specific modification result to the EM is notified. Used to notify NM that you can now configure the network and tell it which PNFs to configure, which VNFs are terminated and shrunk, and the NM's awareness of the network is updated.

It should be understood that steps 1706 through 1713 indicate to NSM&O that the EM managing the dedicated VNF configures the dedicated VNF to terminate the specific interaction flow for the service to the target network slice instance.

Optionally, in step 1714, the network slice instance stored in the memory is updated, and the NSM&O checks the status of the network slice instance instantiated by the NSLD of the target network slice to be deleted. If there is an unterminated network slice instance in the target network slice, steps 1706-1714 are repeated for the slice instance. If there is no network slice instance generated according to the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used. . If the NSLD is being used, the feedback network slice is deleted incorrectly. If the NSLD is not being used, step 1715 is performed.

Optionally, in step 1715, NSM&O deletes the current version of NSLD in memory.

It should be understood that steps 1714 and 1715 need to be performed only when the sender sends a network slice deletion request.

Step 1716, notifying the sender that the network slice instance termination/network slice deletion is completed.

In the present application, the existing 3GPP network architecture and the MANO network architecture system are retained, and an independent network management system is adopted for the network slicing service to support the direct orchestration management of the PNF. For the VNF, the NFV MANO system management orchestration is used to support the system architecture. The network slice instance is terminated and the network slice is deleted. In this application, the third-party tenant that can allow the operator or the authorized network slice instance to discover that the existing slice instance cost is higher than the benefit of the service is requested to terminate the network slice instance, and the operator is allowed to decide not to support the current When a type network is sliced, such as a network slice version upgrade, the network slice is requested to be deleted.

FIG. 18 shows a schematic block diagram of a network architecture of an embodiment of the present application. The network architecture 4 (option 4) shown in FIG. 18 is an improvement to the existing 3GPP OSS system (such as the embodiment shown in FIG. 4), and the NSM&O can implement the function of the NM in the original 3GPP network architecture. Specifically, NSM&O interacts with the EM through the Itf-N interface to implement management of the PNF including the PNF (managed by the NE) and the VNF; the NSM&O is independent of the existing NM system, does not make any upgrade changes to the NM system, and introduces a new set of The interface between the NSM&O and the NM system is temporarily called the NG1 interface. The interface between the NSM&O and the VNFM is temporarily called the NG1 interface. The interface between the NSM&O and the VIM is temporarily called the NG2 interface. NSM&O and The interface between the EMs is temporarily called the NG5 interface.

Specifically, the functions of the NG1 interface mainly include: authorization, reservation, allocation, and release of NFVI resources for supporting VNF; querying information query of running state; VNF initializing update, scaling, termination, etc., transmitting VNF-related events , status information, etc.

Specifically, the functions of the NG3 mainly include: transmitting the negotiation information between the NSM&O and the NM, for example, the NSM&O queries the NNF that has been generated by the NM; the NM feeds back the VNF information that has been generated by the NSM&O, and confirms that the modification is allowed; and the NSM&O notifies the NM which PNF is to be used. /VNF is modified; NSM&O notifies NM specifically for PNF/VNF Modify the content.

Therefore, the network architecture undergoes evolution and upgrade on the OSS system, and the existing network architecture and interface are less modified. The architecture does not need to change the NM, but provides a new management system, and needs to adopt a new interface and current Some entities interact. Both NSM&O and NM can directly manage PNF, and NSM&O directly orchestrate management of virtual resources and participate in VNF lifecycle management.

FIG. 19 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present application. FIG. 19 is a flow chart showing the flow of network slice management based on the network structure shown in FIG. 18.

As shown in FIG. 19, the method includes:

Step 1901: The sender sends a target network slice instance termination request or a target network slice deletion request to the NSM&O.

It should be understood that the request in step 1901 may be a specific implementation in the management request message in the example described in FIG. 7, which is not limited in this application.

Step 1902, authenticate, authenticate, verify, and check the target network slice (or target network slice instance).

When the request sent by the sender is the termination target network slice instance in step 1901, the following steps are performed:

If the verification authentication fails, step 1902' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to terminate the slice instance, and cannot verify the identity of the sending end;

If the authentication authentication is passed and the target network slice instance exists, step 1903 is performed;

If the verification authentication is passed but the network slice instance does not exist, step 1902' is performed, that is, the NSM&O feeds back a parameter error to the sender, and informs the sender that the target network slice instance does not exist.

Alternatively, when the request sent by the sender is to delete the target network slice in step 1901, the following steps are performed:

If the verification authentication fails, step 1902' is performed, and the NSM&O feeds back the corresponding error to the sending end, for example, the sending end does not have the right to delete the network slice, and cannot verify the identity of the sending end;

If the verification authentication succeeds and the NSLD corresponding to the target network slice exists, after all the instances of the target network slice are terminated, the NSM&O performs step 1916;

It should be understood that steps 1901 to 1902 or step 1902' are a specific interaction flow for the NSM&O to verify whether the sender of the management request message has the right to manage the network slice of the target network slice.

Step 1903: Before terminating the network sharding instance, the NSM&O notifies the NM of the adjustment of the PNF that is jointly managed by the NM through the NG3 interface to avoid conflicts. The notification must include at least the PNF identifier involved.

In step 1904, after receiving the notification, the NM receives a notification confirmation from the NMM&O through the NG3 interface. These PNFs and VNFs are no longer monitored and the configuration is modified before the NM receives the NSM&O modification completion message.

Step 1905: The NSM&O checks whether the target network slice instance to be terminated (referred to as the target NSI) and other network slice instances have shared common network functions, including the shared VNF and the shared PNF; and whether the NSM&O detects the target NSI that needs to be terminated. Internet function.

It should be understood that (1) in step 1905 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating services to the target network slice instance. At this time, the first PNF is a shared PNF.

Further, in step 1905, the NSM&O detects whether the target NSI that needs to be terminated has a dedicated network function.

It should be understood that (2) in step 1905 indicates that the NSM&O indicates that the EM managing the shared VNF configures the shared VNF as a specific interaction flow terminating the service to the target network slice instance.

(3) When the target NSI includes a dedicated PNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the NG5 interface, and instructs the EM managing the dedicated PNF to set the dedicated PNF to terminate the service to the target NSI. The request includes, but is not limited to, instructing the EM to stop the service provided by the dedicated PNF to the target NSI, deleting configuration parameters for supporting the target NSI service, such as a network slice instance identifier, and deleting the service target NSI. Terminate/delete the network connection between the PNF and the target NSI-specific network functions.

It should be understood that (3) in step 1905 indicates to NSM&O that the network element manager EM managing the first PNF configures the first PNF as a specific interaction procedure for terminating services to the target network slice instance. At this time, the first PNF is a dedicated PNF.

In step 1906, the NSM&O notifies the NM configuration that the corresponding PNF in the target network slice instance has been terminated by the NG3 interface, and the modification result is notified.

(4) When the target NSI includes a dedicated VNF, the NSM&O initiates a request to configure the network function to the EM managing the dedicated VNF through the NG5 interface, indicating that the EM managing the shared VNF sets the dedicated VNF to terminate the service to the target NSI. That is, in step 1907 in the flow shown in FIG. 19, the request includes, but is not limited to, indicating that the monitoring of the VNF running state is stopped, terminating the management function of the VNF, and deleting the management object.

If the shared VNF, the dedicated VNF, the shared PNF, and the dedicated PNF of the target NSI have been terminated, the network slice instance is terminated, and step 1918 is performed.

Step 1908, the EM managing the dedicated VNF performs the NSM&O request to terminate the VNF management in step 1907.

In step 1909, the EM managing the dedicated VNF is returned to the NSM&O through the NG5 interface to terminate the management and complete the confirmation.

In step 1910, the NSM&O notifies the EM that manages the dedicated VNF to close the virtual port of the dedicated VNF through the NG5 interface, and stops the service to the target NSI.

Step 1911: The NSM&O initiates a terminal-specific VNF request to the VNFM through the NG1 interface, where the request includes terminating the service that is running on the target NSI, and closing the dedicated VNF. .

In step 1912, the VNFM performs the NSM&O in step 1308 to terminate the service that is running on the dedicated VNF, and the VNFM and VNF internal mechanisms jointly close the VNF.

Optionally, in step 1913, the VNFM feeds back the completion message of the dedicated VNF to the NSM&O through the NG1 interface.

In step 1914, the NSM&O sends and deletes and releases the VNFs to the VIM through the NG2 interface according to the information supporting the resources (including computing, storage, and network resources) used to run the dedicated VNF and the network connection information that supports running the network slice instance. Requests for resources and network connections.

In step 1915, the VIM performs the deletion required by the NSM&O in step 1914, releases the resources used by the VNFs, and deletes the request for the network connection exclusive to the network slice instance.

In step 1916, the VIM sends a feedback deletion and release completion confirmation to the NSM&O through the NG2 interface.

It should be understood that steps 1905 through 1916 indicate to NSM&O that the EM managing the dedicated VNF configures the dedicated VNF as a specific interaction flow that terminates the service to the target network slice instance.

Step 1917: If there are other functions in the dedicated network function of the target NSI that are not implemented by the dedicated VNF, the steps 1905 to 1916 are repeated until the target NSI is terminated, and the NSM&O deletes the information of the target NSI in the memory slice instance. If the sender sends a network slice instance termination request in step 1901, the steps are performed. 1920, otherwise step 1918 is performed.

Optionally, in step 1918, the NSM&O checks the status of the network slice instance instantiated by the NSLD of the target network slice to be deleted. If there is an unterminated network slice instance in the target network slice, repeat steps 1905-1515 for the slice instance. If there is no network slice instance generated according to the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used. . If the NSLD is being used, the feedback network slice is deleted incorrectly. If the NSLD is not being used, step 1919 is performed.

Optionally, in step 1919, NSM&O deletes the current version of NSLD in memory.

It should be understood that step 1918 and step 1919 need to be performed only when the sender sends a network slice deletion request.

Step 1920, notifying the sender that the network slice instance termination/network slice deletion is completed.

Further, in the present application, when the PNF managed by the NSM&O and the existing network management system is managed, the conflict caused by the joint management can be avoided.

It should be understood that there are overlapping steps in the four flowcharts described for each of the four network architectures in FIGS. 10 to 19, and the same flow methods in the several embodiments are similar, and are not described in full detail for the sake of brevity.

It should be understood that only one EM is drawn in the above-mentioned FIG. 11, FIG. 13, FIG. 17, and FIG. 19, but NSM&O needs to interact with a plurality of different EMs when terminating different network functions, and manage the network according to the network function that needs to be terminated. The function EM sends a request message. For example, in the actual system, there may be an EM that manages the PNF, an EM that manages the VNF, and an EM that manages the PNF and the VNF, and the like.

It should be understood that the label size of the above steps does not represent the execution order. In the specific implementation process, some or all of the steps may be selected according to the specific situation of the target network slice instance, which is not limited in this application.

FIG. 7 to FIG. 9 describe in detail the flow of the method for managing network slices in the present application, and the four embodiments described in FIG. 10 to FIG. 19 respectively are directed to four architectures, and the method for terminating the network slice instance and the method for deleting the network slice are respectively performed. The entity that performs the slice instance termination/slice deletion is NSM&O. In the implementation process, NSM&O may be a plurality of modules having a hierarchical structure, as shown in FIG. 20, which shows a schematic block diagram of a network management and orchestrator of one embodiment of the present application. Among them, multi-vendor NSM&O is a total control orchestrator that manages the management orchestrator domain NSM&O of each domain. In Figure 20, the NSM&O management device refers to multi-vender NSM&O, and the figure An NSM&O, the second NSM&O and the nth NSM&O refer to the domain NSM&O, where each domain NSM&O is responsible for managing the sub-network slicing, and the management of the multi-vender load overall network slicing, it should be understood that the NSM&O described in the above embodiment Both can be used as domain NSM&O. Specifically, for example, a complete slice instance may be composed of a core network sub-slice instance and a RAN sub-slice instance. At this time, there is a multi-vender NSM&O responsible for overall network slice instance management and separately managing core network sub-slice instances and RAN sub- Two domain NSM&Os of a slice instance; or a complete slice instance can be divided into multiple sub-slice instances, each sub-slice instance consisting of a device provider's device, such as an operator's network slice instance is handled by a multi-vendor NSM&O Overall management, domain NSM&O provided by several equipment vendors manages the equipment provided by this equipment manufacturer. The description of the sub-slice instance is similar to the description of the entire slice instance, and the information contained may include network functions, connection relationships between network functions, KPI requirements, SLAs, operational parameters to be monitored, and the like. When the multi-vendor NSM&O receives a request from the sender and needs to terminate a network slice instance, it is known that the slice instance is divided into several sub-slice instances (this configuration is determined when the network slice instance is created), at this time multi-vendor NSM&O notifies each domain NSM&O to complete the termination of the sub-slice instance. How to terminate the sub-network slicing is determined by domain NSM&O.

The process of terminating the network slice request is initiated by the multi-vendor NSM&O. The process performed by each domain NSM&O is as shown in FIG. 21. FIG. 21 is a schematic flowchart of a management network slice according to an embodiment of the present application. As shown in FIG. 21, multi-vendor NSM&O is an NSM&O management device in which the NSM&O management device manages the first NSM&O and the second NSM&O.

Specifically, in step 2101, the NSM&O management device decomposes the entire network slice instance into several sub-network slice instances, including a sub-network slice instance 1 and a sub-network slice instance 2, which are respectively managed by the first NSM&O and the second NSM&O.

Step 2102: Send a request to the first NSM&O to request to terminate the sub-network slice instance 1.

Step 2103: The first NSM&O performs the process of terminating the sub-network splicing instance 1. The specific termination process may be similar to the embodiment described in FIG. 7 to FIG. 19, and details are not described herein again.

Step 2104: The first NSM&O sends a termination complete message to the NSM&O management device.

Step 2105: Send a request to the second NSM&O to request to terminate the sub-network slice instance 2.

In the step 2106, the second NSM&O performs the process of terminating the sub-network splicing instance 2. The specific termination process may be similar to the embodiment described in FIG. 7 to FIG. 19, and details are not described herein again.

In step 2107, the first NSM&O sends a termination complete message to the NSM&O management device.

That is, after all the domain NSM&Os complete the management of the sub-network slicing instance, the multi-vendor NSM&O can confirm the management of the entire network slicing instance.

Therefore, the network slice management and orchestration of the domain structure is beneficial to: 1) each device of the multi-device vendor is independently managed by each domain NSM&O, and thus the configuration problem caused by the device configuration script of each device vendor is not standardized. This architecture solves. The network device of a device vendor is managed by the domain NSM&O provided by the device vendor, which facilitates the management system design and eliminates the difference between the device vendors managed by another domain NSM&O through multi-vendor NSM&O, which is beneficial to the unified management of the operator. Networking with orchestration. 2) Domain management of network slice instances. The independent management and orchestration architecture of the domain supports the independent creation, adjustment, update, configuration, and deletion of a domain without affecting other domains, making the management and orchestration of network slicing instances more flexible, and facilitating the positioning of operators. Network problems, design network deployment scenarios.

FIG. 22 is a schematic structural block diagram of a network device according to an embodiment of the present application.

The method for managing a network slice and the network management architecture of the present application are described in detail above with reference to FIG. 1 to FIG. 21, and the network device of the present application will be described in detail below with reference to FIGS. 22 to 27.

22 is a schematic block diagram of a network device 2200 of the present application. It should be understood that the network device 2200 can perform the various steps performed by the NSM&O in the methods of FIGS. 1 through 21, and to avoid repetition, it will not be described in detail herein. Network design Preparation 2200 includes:

The receiving unit 2210 is configured to receive, by using the transceiver, a management request message of a target network slice, where the management request message is used to request to delete the target network slice or terminate the target network slice instance.

The control unit 2220 is configured to control the PNF management device and/or the VNF management device to perform network slice management on the target network slice according to the management request message.

It should be understood that the actions performed by the determining unit 2210 can be implemented by a processor, and the actions performed by the transmitting unit 2220 can be implemented by the transceiver under the control of the processor.

FIG. 23 is a schematic structural block diagram of a network device according to an embodiment of the present application. 23 is a schematic block diagram of a network device 2300 of the present application. It should be understood that the network device 2300 can perform the various steps performed by the transmitting end in the methods of FIGS. 1 through 21, and in order to avoid repetition, it will not be described in detail herein. Network device 2300 includes:

The determining unit 2310 is configured to send, to the NSM&O, the management request message of the target network slice, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target network slice instance.

The sending unit 2320 is configured to receive a management complete message sent by the NSM&O, where the management complete message is used to determine that the NSM&O completes deletion of the target network slice or termination of the target network slice instance.

It should be understood that the actions performed by the determining unit 2310 may be implemented by a processor, and the actions performed by the transmitting unit 2320 may be implemented by a transceiver under the control of the processor.

FIG. 24 is a schematic structural block diagram of a network device according to an embodiment of the present application. 24 is a schematic block diagram of a network device 2400 of the present application. It should be understood that the network device 2400 is capable of performing the various steps performed by the memory in the methods of FIGS. 1 through 21, and to avoid repetition, will not be described in detail herein. Network device 2400 includes:

The receiving unit 2410 is configured to receive an authentication message of the NSM&O, where the verification message is used to verify whether the sending end that initiates the network slice management request has the right to perform network slice management on the target network slice.

The processing unit 2420 is configured to verify, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.

It should be understood that the actions performed by the determining unit 2410 can be implemented by a processor, and the actions performed by the transmitting unit 2420 can be implemented by the transceiver under the control of the processor.

Further, the present application can terminate the current target network slice when the transmitting end determines that the current target network slice instance is no longer supported, or delete the target network slice when the transmitting end determines that the current target network slice is no longer supported. Therefore, it is possible to more flexible network slice management and reduce operating costs.

Figure 25 is a block diagram showing the schematic structure of an apparatus of an embodiment of the present application. FIG. 25 shows an apparatus 2500 for managing network slices provided by the present application. It should be understood that the apparatus 2500 is capable of performing the various steps performed by the NSM&O in the methods of FIGS. 1 through 21, and to avoid repetition, will not be described in detail herein. Apparatus 2500 includes:

a memory 2510, configured to store a program;

a transceiver 2520, configured to communicate with other devices;

a processor 2530 for executing a program in the memory 2510, the processor 2530 being respectively connected to the memory 2510 and the transceiver 2520 for executing the instruction stored by the memory 2510 to execute the instruction Perform the following steps:

The processor 2530 is configured to receive, by using the transceiver 2520, a management request message of a target network slice, where the management request message is used to request to delete the target network slice or terminate the target network slice instance; according to the management request message, Controlling the PNF management device and/or the VNF management device to perform network slice management on the target network slice.

It should be understood that the device 2500 may be specifically the NSM&O in the above embodiment, and may be used to perform various steps and/or processes corresponding to the NSM&O in the above method embodiment.

FIG. 26 is a schematic structural block diagram of an apparatus of another embodiment of the present application. FIG. 26 shows an apparatus 2600 for managing network slices provided by the present application. It should be understood that the apparatus 2600 is capable of performing the various steps performed by the NSM&O in the methods of FIGS. 1 through 21, and to avoid repetition, will not be described in detail herein. Apparatus 2600 includes:

a memory 2610, configured to store a program;

a transceiver 2620, configured to communicate with other devices;

a processor 2630 for executing a program in the memory 2610, the processor 2630 being respectively coupled to the memory 2610 and the transceiver 2620 for executing the instructions stored by the memory 2610 for executing the instructions Perform the following steps:

The processor 2630 is configured to send, by the transceiver 2620, a management request message of the target network slice to the NSM&O, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target network slice instance. Receiving a management complete message sent by the NSM&O, where the management complete message is used to determine that the NSM&O completes deletion of the target network slice or termination of the target network slice instance.

It should be understood that the device 2600 may be specifically the sending end in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the sending end in the foregoing method embodiments.

FIG. 27 is a schematic structural block diagram of an apparatus according to another embodiment of the present application. FIG. 27 shows an apparatus 2700 for managing network slices provided by the present application. It should be understood that the apparatus 2700 is capable of performing the various steps performed by the memory in the methods of FIGS. 1 through 21, and to avoid repetition, details are not described herein. Device 2700 includes:

a memory 2710, configured to store a program;

The transceiver 2720 is configured to communicate with other devices;

The processor 2730 is configured to execute a program in the memory 2710, and the processor 2730 is connected to the memory 2710 and the transceiver 2720, respectively, for executing the instruction stored by the memory 2710 to execute the instruction. Perform the following steps:

The processor 2730 is configured to receive, by using the transceiver 2720, an authentication message of the NSM&O, where the verification message is used to verify whether the sending end that initiates the network slice management request has the right to perform network slice management on the target network slice.

And verifying, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.

It should be understood that the device 2700 may be specifically the memory in the above embodiment, and may be used to perform various steps and/or processes corresponding to the memory in the foregoing method embodiments.

It should be understood that, in the present application, the processor of the above device may be a central processing unit (CPU), and the processor may also be other general purpose processors, digital signal processors (DSPs), dedicated Application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The steps of the method disclosed in connection with the present application may be directly embodied by the completion of the execution of the hardware processor or by a combination of hardware and software units in the processor. The software unit can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.

Those skilled in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the steps and composition of the various embodiments have been generally described in terms of function in the foregoing description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. Different methods may be used to implement the described functionality for each particular application, but such implementation should not be considered to be beyond the scope of the application.

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

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the present application.

The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

The steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (read only Memory, ROM), erasable programmable read ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, mobile hard disk, CD-ROM (CD-ROM) Or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor.

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

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

Claims

A method for managing network slicing, comprising:

The network slice management and orchestrator NSM&O receives a management request message of the target network slice, where the management request message is used to request to delete the target network slice or terminate the target network slice instance;

The NSM&O controls the physical network function management device and/or the virtual network function management device to perform network slice management on the target network slice according to the management request message.
The method according to claim 1, wherein the controlling the physical network function management device and/or the virtual network function management device to perform network slice management on the target network slice according to the management request message comprises:

When the management request message is used to request termination of the target network slice instance, controlling the virtual network function management device, terminating the virtual network function VNF corresponding to the target network slice instance; and/or

Controlling, by the physical network function management device, a physical network function PNF corresponding to the target network slice instance.
The method according to claim 2, wherein the physical network function management device comprises an EM, and the controlling the physical network function management device to terminate the physical network function PNF corresponding to the target network slice instance comprises:

When the PNF corresponding to the target network slice instance includes the first PNF, the network element manager EM indicating that the first PNF is managed configures the first PNF to terminate the service to the target network slice instance.
The method according to claim 2 or 3, wherein the physical network function management device comprises an EM, and the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance, including :

When the VNF corresponding to the target network slice embodiment includes a shared VNF, the EM indicating that the shared VNF is managed configures the shared VNF to terminate the service to the target network slice instance.
The method according to claim 4, wherein the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance comprises:

Instructing the virtualized infrastructure management device VIM to configure the shared VNF to terminate a network connection associated with the target network slice instance and/or to shrink network resources associated with the target network slice instance, wherein the virtual network function management The device includes the VIM; or

Instructing the virtual network function orchestrator NFVO to configure the shared VNF to terminate a network connection associated with the target network slice instance and/or to shrink network resources associated with the target network slice instance, wherein the virtual network function management device The NFVO is included.
The method according to any one of claims 2 to 5, wherein the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance comprises:

When the VNF corresponding to the target network slice instance includes a dedicated VNF, it indicates that the EM that manages the dedicated VNF terminates management of the dedicated VNF.
The method of claim 6, wherein the virtual network function management device comprises a VIM and a virtual network function management device VNFM, and the controlling the virtual network function management device terminates the target network cut The virtual network function VNF corresponding to the slice instance includes:

Instructing the VNFM to terminate the exclusive VNF;

Instructing the VIM to close a network connection associated with the dedicated VNF and/or release network resources associated with the second VNF.
The method of claim 6, wherein the virtual network function management device comprises an NFVO, the controlling the virtual network function management device terminating a virtual network function VNF corresponding to the target network slice instance, and terminating the method Target network slice embodiment, including:

Instructing the NFVO to close a network connection associated with the dedicated VNF and/or release network resources associated with the shared VNF.
The method according to claim 1, wherein the controlling the physical network function management device and/or the virtual network function management device to perform network slice management on the target network slice according to the management request message comprises:

When the management request message is used to delete the target network slice, the control physical network function management device and/or the virtual network function management device deletes the target network slice.
The method according to claim 9, wherein the controlling the physical network function management device and/or the virtual network function management device to delete the target network slice comprises:

Controlling the physical network function management device and/or the virtual network function management device to terminate a VNF and/or a PNF corresponding to each instance in the target network slice.
The method according to claim 9 or 10, wherein the controlling the physical network function management device and/or the virtual network function management device to perform network slice management on the target network slice according to the management request message, including :

After determining that all instances in the target network slice are terminated, the memory is instructed to delete the slice template of the target network slice.
The method according to any one of claims 1 to 11, wherein the controlling the physical network function management device and/or the virtual network function management device to perform the target network slice according to the management request Before the network slice management, the method further includes:

Verifying whether the sender that initiated the management request message has the right to manage the network slice of the target network slice.
A method for managing network slicing, comprising:

The sending end sends a management request message of the target network slice to the network slice management and orchestrator NSM&O, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target network slice instance;

The sending end receives the management complete message sent by the NSM&O, and the management complete message is used to determine that the NSM&O completes the deletion of the target network slice or the termination of the target network slice instance.
A method for managing network slicing, comprising:

The memory receives the verification message of the network slice management and the orchestrator NSM&O, wherein the verification message is used to verify whether the sender that initiates the network slice management request has the right to perform network slice management on the target network slice;

The memory verifies, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.
The method according to claim 14, wherein the returning the verification completion message to the NSM&O, so that the NSM&O determines whether to manage the target network slice according to the verification feedback message, includes:

Returning, to the NSM&O, a verification completion message, where the verification completion message is used to notify the NSM&O whether the sending end has the right to perform network slice management on the target network slice;

When the sending end does not have the network slice management right of the target network slice or the instance of the target network slice does not exist, the verification feedback message is used to notify the NSM&O that the sending end does not have the The target network slice performs network slice management rights; or

When the sending end has the network slice management right of the target network slice, the verification feedback message is used to notify the NSM&O that the sending end has the right to perform network slice management on the target network slice.
A network device, comprising:

transceiver;

a memory for storing instructions;

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

Receiving, by the transceiver, a management request message of a target network slice, where the management request message is used to request to delete the target network slice or terminate the target network slice instance;

And controlling the physical network function management device and/or the virtual network function management device to perform network slice management on the target network slice according to the management request message.
The network device according to claim 16, wherein the processor is specifically configured to:

When the management request message is used to request termination of the target network slice instance, controlling the virtual network function management device, terminating the virtual network function VNF corresponding to the target network slice instance; and/or

Controlling, by the physical network function management device, a physical network function PNF corresponding to the target network slice instance.
The network device according to claim 17, wherein the processor is specifically configured to:

When the PNF corresponding to the target network slice instance includes the first PNF, the network element manager EM indicating that the first PNF is managed configures the first PNF to terminate the service to the target network slice instance.
The network device according to claim 17 or 18, wherein the physical network function management device comprises an EM, and the processor is specifically configured to:

When the VNF corresponding to the target network slice embodiment includes a shared VNF, the EM indicating that the shared VNF is managed configures the shared VNF to terminate the service to the target network slice instance.
The network device according to claim 19, wherein the processor is specifically configured to:

Instructing the virtualized infrastructure management device VIM to configure the shared VNF to terminate a network connection associated with the target network slice instance and/or to shrink network resources associated with the target network slice instance, wherein the virtual network function management The device includes the VIM; or

Instructing the virtual network function orchestrator NFVO to configure the shared VNF to terminate a network connection associated with the target network slice instance and/or to shrink network resources associated with the target network slice instance, wherein the virtual network function management device The NFVO is included.
The network device according to any one of claims 17 to 20, wherein the processor is specific Used for:

When the VNF corresponding to the target network slice instance includes a dedicated VNF, it indicates that the EM that manages the dedicated VNF terminates management of the dedicated VNF.
The network device according to claim 21, wherein the virtual network function management device comprises a VIM and a virtual network function management device VNFM, and the processor is specifically configured to:

Instructing the VNFM to terminate the exclusive VNF;

Instructing the VIM to close a network connection associated with the dedicated VNF and/or release network resources associated with the second VNF.
The network device according to claim 21, wherein the virtual network function management device comprises an NFVO, and the processor is specifically configured to:

Instructing the NFVO to close a network connection associated with the dedicated VNF and/or release network resources associated with the shared VNF.
The network device according to claim 16, wherein the processor is specifically configured to:

When the management request message is used to delete the target network slice, the virtual network function VNF and/or the physical network function PNF corresponding to each instance in the target network slice is deleted.
The network device according to claim 24, wherein the processor is specifically configured to:

Terminating the VNF and/or PNF corresponding to each of the instances in the target network slice.
The network device according to claim 24 or 25, wherein the processor is specifically configured to:

After determining that all instances in the target network slice are terminated, the memory is instructed to delete the slice template of the target network slice.
The network device according to any one of claims 24 to 26, wherein the processor is specifically configured to:

Verifying whether the sender that initiated the management request message has the right to manage the network slice of the target network slice.
A network device, comprising:

transceiver;

a memory for storing instructions;

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

Sending, to the network slice management and orchestrator NSM&O, a management request message of the target network slice, where the management request message is used to request the NSM&O to delete the target network slice or terminate the target network slice instance;

Receiving a management complete message sent by the NSM&O, where the management complete message is used to determine that the NSM&O completes deletion of the target network slice or termination of the target network slice instance.
A network device, comprising:

transceiver;

a memory for storing instructions;

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

Receiving a verification message of the network slice management and orchestrator NSM&O, wherein the verification message is used for verification initiation Whether the sender of the network slice management request has the right to perform network slice management on the target network slice;

And verifying, according to the verification message, whether the sending end has the right to perform network slice management on the target network slice.
The network device according to claim 29, wherein the processor is specifically configured to:

Returning, to the NSM&O, a verification completion message, where the verification completion message is used to notify the NSM&O whether the sending end has the right to perform network slice management on the target network slice;

When the sending end does not have the network slice management right of the target network slice or the instance of the target network slice does not exist, the verification feedback message is used to notify the NSM&O that the sending end does not have the The target network slice performs network slice management rights; or

When the sending end has the network slice management right of the target network slice, the verification feedback message is used to notify the NSM&O that the sending end has the right to perform network slice management on the target network slice.
A method for managing network slicing, comprising:

The network slice management and orchestration NSM&O management device sends a first request message to the first NSM&O, the first request message is used to request the first NSM&O to terminate the first sub-network slice instance, where the first NSM&O is used for management and Arranging the first sub-network slice instance;

The NSM&O management device receives a first termination complete message from the first NSM&O.
A method of managing network slices according to claim 31, wherein

The method further includes:

The NSM&O management device sends a second request message to the second NSM&O, where the second request message is used to request the second NSM&O to terminate the second sub-network slice instance, where the second NSM&O is used to manage and schedule the Two sub-network slice instances;

The NSM&O management device receives a second termination complete message from the second NSM&O.
The method according to claim 31 or 32, wherein before the network slice management and orchestration NSM&O management device sends the first request message to the first NSM&O, the method further includes:

The NSM&O management device decomposes the network slice instance into the plurality of sub-network slice instances.
A method for managing network slicing, comprising:

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

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

The first NSM&O sends a first termination complete message to the NSM&O management device.
A method for managing network slicing, comprising:

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

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

The second NSM&O sends a second termination complete message to the NSM&O management device.
A network slice management and orchestrator NSM&O management device, comprising:

transceiver;

a memory for storing instructions;

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

Sending a first request message to the first NSM&O, the first request message is used to request the first NSM&O to terminate the first sub-network slice instance, where the first NSM&O is used to manage and schedule the first sub-network slice instance ;

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

Sending a second request message to the second NSM&O, the second request message is used to request the second NSM&O to terminate the second sub-network slice instance, where the second NSM&O is used to manage and schedule the second sub-network slice instance ;

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

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

transceiver;

a memory for storing instructions;

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

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

Terminating the first sub-network slice instance;

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

transceiver;

a memory for storing instructions;

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

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

Terminating the second sub-network slice instance;

Sending a second termination complete message to the NSM&O management device.