CN108023749A - Manage the method, apparatus and system of network section - Google Patents

Abstract

An embodiment of the present invention provides a method for managing network slices, including: the network slice management and orchestrator NSM&O receives a management request message of a target network slice, and the management request message is used to request deletion of the target network slice or termination of the target network slice. A network slice example: 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. Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Description

Method, device and system for managing network slices

technical field

The present invention relates to the communication field, and relates to a method, device and system for managing network slices.

Background technique

Future 5G mobile communication systems need to meet diverse business requirements, such as enhanced mobile broadband, large-scale machine-type communication, ultra-high reliability and low-latency communication, etc. Network slicing technology abstracts the network logically into one or more isolated network slices, where each network slice contains a series of logical network functions to meet the differentiated needs of different services, and the network slice instance is It is an instance created according to a network slice template or other methods.

In network slicing technology, when the business no longer needs to use network slicing (for example, the machine-type communication service is no longer required), or the network no longer provides network slicing services (for example, the network provider decides to close the machine-type communication network slice), you need to delete the related network slice or terminate the related network slice instance. However, the network management architecture of the prior art (for example, the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) telecom network management architecture) can only realize the management of physical network functions, while the virtualization management of the network functions of the prior art and Orchestration (English: Network Function Virtualization Management and Orchestration, abbreviation: MANO) network architecture can only realize the management of virtual network functions.

Therefore, there is an urgent need for a method for managing network slices, which can realize deletion of network slices or termination of network slice instances through unified management of physical resources and virtual resources.

Contents of the invention

Embodiments of the present invention provide a method and device for managing network slice instances, so as to realize the management of network slice instances.

In a first aspect, a method for managing network slices is provided, including: a network slice management and orchestrator NSM&O receives a management request message of a target network slice, and the management request message is used to request deletion of the target network slice or termination of the target A 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.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

With reference to the first aspect, in a first possible implementation manner of the first aspect, according to the management request message, controlling the physical network function management device and/or the virtual network function management device to perform network operations on the target network slice slice management, including: when the management request message is used to request termination of the target network slice instance, controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance; and/or controlling The physical network function management device terminates the physical network function PNF corresponding to the target network slice instance.

With reference to the first aspect and the foregoing implementation manners, in a second possible implementation manner of the first aspect, the physical network function management device includes an EM, and the controlling the physical network function management device to terminate the target network slice The physical network function PNF corresponding to the instance includes: when the PNF corresponding to the target network slice instance includes the first PNF, instruct the network element manager EM that manages the first PNF to configure the first PNF as a termination Service to target network slice instances.

With reference to the first aspect and the foregoing implementation manners, in a third possible implementation manner of the first aspect, the physical network function management device includes an EM, and the controlling the virtual network function management device to terminate the target network slice The virtual network function VNF corresponding to the instance includes: when the VNF corresponding to the target network slice embodiment includes a shared VNF, instruct the EM that manages the shared VNF to configure the shared VNF to terminate the target network slice instance of the service.

With reference to the first aspect and the foregoing implementation manners, in a fourth possible implementation manner of the first aspect, the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance includes: Instructing the virtualization infrastructure management device VIM to configure the shared VNF to terminate network connections related to the target network slice instance, and/or shrink network resources related to the target network slice instance, wherein the virtual network function management A device includes said VIM.

With reference to the first aspect and the foregoing implementation manners, in a fifth possible implementation manner of the first aspect, the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance includes: instructing the virtual network function orchestrator NFVO to configure the shared VNF to terminate network connections related to the target network slice instance, and/or shrink network resources related to the target network slice instance, wherein the virtual network function management device Including the NFVO.

With reference to the first aspect and the foregoing implementation manners thereof, in a sixth possible implementation manner of the first aspect, the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance includes: When the VNF corresponding to the target network slice instance includes a dedicated VNF, instruct the EM that manages the dedicated VNF to terminate the management of the dedicated VNF.

With reference to the first aspect and the foregoing implementation manners, in a seventh possible implementation manner of the first aspect, the virtual network function management device includes a VIM and a virtual network function management device VNFM, and the control of the virtual network function management The device terminates the virtual network function VNF corresponding to the target network slice instance, including: instructing the VNFM to terminate the dedicated VNF; instructing the VIM to close the network connection related to the dedicated VNF, and/or release the 2. VNF-related network resources.

With reference to the first aspect and the foregoing implementation manners, in an eighth possible implementation manner of the first aspect, the virtual network function management device includes NFVO, and the controlling the virtual network function management device to terminate the target network slice The virtual network function VNF corresponding to the instance terminates the target network slicing embodiment, including: instructing the NFVO to close the network connection related to the dedicated VNF, and/or release the network resources related to the shared VNF.

Therefore, in the embodiment of the present invention, the network slice management of the target network slice by NSM&O can realize the differentiated management of the general network function and the dedicated network function of the network slice instance, so that the termination of the target network slice embodiment will not cause damage to other network slice instances. influences.

With reference to the first aspect and the foregoing implementation manners thereof, in a ninth possible implementation manner of the first aspect, the dedicated VNF corresponding to the target network slice instance is a VNF generated by the NSM&O.

That is to say, if the dedicated VNF is generated by NSM&O, then NSM&O can control the physical network function device and the virtual network function device to terminate the dedicated VNF; if the dedicated VNF is not generated by NSM&O, such as the dedicated VNF generated by NM, then NSM&O can Instruct the physical network function device and the virtual network function device to be configured to close the service of the dedicated VNF to the target network slice instance.

With reference to the first aspect and the foregoing implementation manners, in a tenth possible implementation manner of the first aspect, the method further includes: sending a notification message to a network management device NM, where the notification message is used to notify the NM of The network slice management completed by the target network slice.

With reference to the first aspect and the foregoing implementation manners, in an eleventh possible implementation manner of the first aspect, according to the management request message, controlling the physical network function management device and/or the virtual network function management device to The network slice management of the target network slice includes: when the management request message is used to delete the target network slice, delete the virtual network function VNF and/or physical network function corresponding to each instance in the target network slice PNF.

With reference to the first aspect and the above-mentioned implementation manners, in a twelfth possible implementation manner of the first aspect, the deletion of the virtual network function VNF and/or physical network function corresponding to each instance in the target network slice The PNF includes: terminating the VNF and/or PNF corresponding to each instance in the target network slice.

With reference to the first aspect and the foregoing implementation manners, in a thirteenth possible implementation manner of the first aspect, according to the management request message, controlling the physical network function management device and/or the virtual network function management device to The network slice management of the target network slice includes: after it is determined that all instances in the target network slice are terminated, instructing the Repository to delete the slice template of the target network slice.

With reference to the first aspect and the foregoing implementation manners, in a fourteenth possible implementation manner of the first aspect, the controlling the physical network function management device and/or the virtual network function management device according to the management request Before performing network slice management on the target network slice, the method further includes: verifying whether the sender Sender who initiates the management request message has the authority to manage the network slice of the target network slice.

In combination with the first aspect and the above-mentioned implementation manners, in a fifteenth possible implementation manner of the first aspect, verify whether the sender Sender who initiated the management request message has the authority to manage the network slice of the target network slice , including: sending a verification message to a storage Repository, where the verification message is used by the Repository to determine whether the Sender has the authority to perform network slice management on the target network slice; receiving a verification completion message fed back by the Repository, where the verification is completed The message is used to notify the NSM&O whether the Sender has the authority to perform network slice management on the target network slice.

With reference to the first aspect and the above-mentioned implementation manners, in a sixteenth possible implementation manner of the first aspect, the method further includes: when it is determined that the Sender does not have the authority to manage the network slice of the target network slice , sending a verification failure message to the Sender, where the verification failure message is used to notify the Sender that it does not have the right to perform network slice management on the target network slice.

With reference to the first aspect and the above implementation manners, in a seventeenth possible implementation manner of the first aspect, the method further includes: when the NSM&O completes the management of the target network slice, sending Sending a management completion message, where the management completion message is used to notify the Sender that the deletion of the target network slice or the termination of the target network slice instance has been completed.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Therefore, when network slices need to be deleted, NSM&O can manage physical and virtual network functions, arrange physical and virtual resources in a unified manner, make policies more flexible, and use network resources optimally; when network slice instances need to be terminated, the network can be terminated. When slicing the shared VNF, you can choose to shrink the resources of the VNF according to your needs, which can improve resource utilization.

In a second aspect, a method for managing network slices is provided, including: sending a management request message of the target network slice to a network slice management and orchestrator NSM&O, where the management request message is used to request the NSM&O to delete the target network Slicing or terminating the target network slice instance; receiving a management completion message sent by the NSM&O, where the management completion 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 .

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: receiving a verification failure message sent by the NSM&O, where the verification failure message is used to notify that target network slice management cannot be performed.

With reference to the second aspect and the above-mentioned implementation manners, in a second possible implementation manner of the second aspect, it includes: receiving a verification message from the network slice management and orchestrator NSM&O, where the verification message is used to verify the originating network slice Whether the sending end Sender of the management request has the authority to perform network slice management on the target network slice; verify whether the Sender has the authority to perform network slice management on the target network slice according to the verification message.

With reference to the second aspect and the above-mentioned implementation manners, in a third possible implementation manner of the second aspect, the verification completion message is returned to the NSM&O, so that the NSM&O can determine whether to verify the verification according to the verification feedback message. The management of the target network slice includes: returning a verification completion message to the NSM&O, where the verification completion message is used to notify the NSM&O whether the Sender has the authority to perform network slice management on the target network slice; when the When the Sender does not have the network slice management authority for the target network slice or the instance of the target network slice does not exist, the verification feedback message is used to inform the NSM&O that the Sender does not have the network slice management authority for the target network slice Network slice management authority; or when the Sender has the network slice management authority for the target network slice, the verification feedback message is used to inform the NSM&O that the Sender has network slice management for the target network slice permission.

In a third aspect, a method for managing network slices is provided, including: receiving a verification message from a network slice management and orchestrator NSM&O, wherein the verification message is used to verify whether the sending end Sender that initiates the network slice management request has Slices have the right to manage network slices; verify whether the Sender has the right to manage network slices on the target network slice according to the verification message.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the verification completion message is returned to the NSM&O, so that the NSM&O determines whether to slice the target network according to the verification feedback message performing management, including: returning a verification completion message to the NSM&O, where the verification completion message is used to notify the NSM&O whether the Sender has the authority to perform network slice management on the target network slice; When the network slice management authority of the target network slice or the instance of the target network slice does not exist, the verification feedback message is used to inform the NSM&O that the Sender does not have the authority to perform network slice management on the target network slice or when the Sender has the network slice management authority for the target network slice, the verification feedback message is used to inform the NSM&O that the Sender has the network slice management authority for the target network slice.

In a fourth aspect, an apparatus for managing network slicing is provided, configured to execute the method in the first aspect or any possible implementation manner of the first aspect. Specifically, the apparatus includes a unit configured to execute the method in the foregoing first aspect or any possible implementation manner of the first aspect.

In a fifth aspect, there is provided another apparatus for managing network slices, which is used to execute the method in the above-mentioned second aspect or any possible implementation manner of the second aspect. Specifically, the apparatus includes a unit for performing the method in the above second aspect or any possible implementation manner of the second aspect.

In a sixth aspect, there is provided another apparatus for managing network slices, which is used to execute the method in the above third aspect or any possible implementation manner of the third aspect. Specifically, the apparatus includes a unit for performing the method in the above third aspect or any possible implementation manner of the third aspect.

In a seventh aspect, a network device is provided, and the network device includes: a transceiver, a memory, a processor, and a bus system. Wherein, the transceiver, the memory and the processor are connected through the bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive and/or send signals, and when the When the processor executes the instructions stored in the memory, the execution causes the processor to execute the method in the first aspect or any possible implementation manner of the first aspect.

In an eighth aspect, a network device is provided, and the network device includes: a transceiver, a memory, a processor, and a bus system. Wherein, the transceiver, the memory and the processor are connected through the bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive signals and/or send signals, and when When the processor executes the instruction stored in the memory, the execution causes the processor to execute the second aspect or the method in any possible implementation manner of the second aspect.

In a ninth aspect, a network device is provided, and the network device includes: a transceiver, a memory, a processor, and a bus system. Wherein, the transceiver, the memory and the processor are connected through the bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive signals and/or send signals, and when When the processor executes the instructions stored in the memory, the execution causes the processor to execute the third aspect or the method in any possible implementation manner of the third aspect.

In a tenth aspect, a system for managing network slicing is provided, and the system includes the device in the fourth aspect or any possible implementation manner of the fourth aspect, the fifth aspect, or any one of the fifth aspects The device in the possible implementation manners and the sixth aspect or the device in any of the possible implementation manners in the sixth aspect; or

The system includes the above seventh aspect or the device in any possible implementation of the seventh aspect, the eighth aspect or the device in any possible implementation of the eighth aspect, and the ninth aspect or any of the ninth aspects An apparatus in one possible implementation.

A tenth aspect provides a computer-readable medium for storing a computer program, where the computer program includes instructions for executing the method in the first aspect or any possible implementation manner of the first aspect.

In an eleventh aspect, a computer-readable medium is provided for storing a computer program, and the computer program includes instructions for executing the method in the second aspect or any possible implementation manner of the second aspect.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings required in the embodiments of the present invention. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

Figure 1 shows a schematic block diagram of network slicing.

Fig. 2 shows a schematic structural block diagram of network slicing according to an embodiment of the present invention.

Fig. 3 shows a schematic structural block diagram of network slicing according to another embodiment of the present invention.

FIG. 4 shows a schematic architecture diagram of a 3rd Generation Partnership Project 3GPP network.

FIG. 5 shows a schematic architecture diagram of the integration of the 3GPP network architecture and the MANO network architecture.

Fig. 6 shows a schematic structural diagram of a network slice management and orchestrator according to an embodiment of the present invention.

Fig. 7 is a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 8 is a schematic flowchart of a method for managing network slices according to another embodiment of the present invention.

Fig. 9 is a schematic flowchart of a method for managing network slices according to yet another embodiment of the present invention.

Fig. 10 shows a schematic block diagram of a network architecture of an embodiment of the present invention.

Fig. 11A shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

FIG. 11B shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 12 shows a schematic block diagram of the network architecture of an embodiment of the present invention.

Fig. 13A shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 13B shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 14 shows a schematic block diagram of the network architecture of an embodiment of the present invention.

Fig. 15 shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 16 shows a schematic block diagram of the network architecture of an embodiment of the present invention.

Fig. 17 shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention.

Fig. 18 shows a schematic block diagram of a network management and orchestrator according to an embodiment of the present invention.

Fig. 19 shows a schematic flowchart of managing network slices according to an embodiment of the present invention.

Fig. 20 is a schematic structural block diagram of a network device according to an embodiment of the present invention.

Fig. 21 is a schematic structural block diagram of a network device according to an embodiment of the present invention.

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

Fig. 23 is a schematic structural block diagram of a device according to an embodiment of the present invention.

Fig. 24 is a schematic structural block diagram of a device according to another embodiment of the present invention.

Fig. 25 is a schematic structural block diagram of a device according to another embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

It should be understood that the technical solutions of the embodiments of the present invention can be applied to various communication systems, for example: Global System of Mobile communication (Global System of Mobile communication, referred to as "GSM") system, Code Division Multiple Access (Code Division Multiple Access, referred to as "GSM") system CDMA") system, Wideband Code Division Multiple Access (referred to as "WCDMA") system, General Packet Radio Service (referred to as "GPRS"), Long Term Evolution (referred to as " LTE") system, LTE Frequency Division Duplex (Frequency Division Duplex, referred to as "FDD") system, LTE Time Division Duplex (Time Division Duplex, referred to as "TDD"), Universal Mobile Telecommunication System (Universal Mobile Telecommunication System, referred to as " UMTS") or Worldwide Interoperability for Microwave Access ("WiMAX" for short) communication system, etc.

It should be noted that the terms "network management architecture", "network system", and "system" in this document can be used interchangeably.

Embodiments of the present invention relate to network slicing technology. Network slicing technology abstracts the network logically into one or more isolated network slices, where each network slice contains a series of logical network functions to meet the differentiated needs of different business types. For example, in the fifth-generation mobile communication (The 5th Generation, referred to as "5G") network, network slicing is an on-demand networking method, which brings operators the ability to adjust according to changing user needs and quickly New services that meet the needs of new types of applications.

Network slice module (English: Network Slice Template, abbreviation: NST): refers to the logical representation of network functions and corresponding resources required by telecommunications services and network capabilities.

Network slice instance (English: Network Slice Instance, abbreviation: NSI): refers to the instance created according to the network slice template.

Network slicing (English: Network Slice, abbreviation: NS): describes the system behavior implemented by network slicing.

Network slicing technology abstracts 5G network physical infrastructure resources into multiple independent parallel network slices according to scenario requirements. Each network slice performs customized tailoring of network functions and orchestration management of corresponding network functions according to the needs of business scenarios and business models. A network slice can be regarded 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 speed, capacity, coverage, delay, reliability, security, and availability, so as to meet the needs of different users. Require.

Figure 1 shows a schematic block diagram of network slicing. As shown in FIG. 1 , three network slices in the 3GPP network are shown, which are real-time machine type communication network slice (English: Critical Machine Type Communication Slice, abbreviation: Critical MTC Slice), large-scale machine type communication network slice ( English: Massive MachineType Communication Slice, abbreviation: Massive MTC Slice) and mobile broadband network slice (English: Mobile Broadband Slice, abbreviation: MBB Slice). Figure 1 shows a typical network slicing scenario. Personal mobile users (such as mobile phones and laptops), smart meters, and vehicles all have requirements for accessing mobile networks, but they have different service requirements for mobile networks. Specifically, individual 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-type communication ( Massive MTC (massive machine type communication) services have high requirements for the number of connections, and low requirements for mobility and access rate; vehicles (Internet of Vehicles users) need real-time machine type communication services, and have high requirements for delay and reliability. There are very high requirements, and the requirements for the number of connections and the access rate are relatively low. In consideration of deployment and operating costs, operators hope to connect the above types of users with different service requirements to the same radio access network (RAN), and adopt logical and physical slicing methods to use the same network infrastructure for different customers with different services.

Although network function virtualization is a key enabling technology to reduce the complexity and cost of network slicing, in order to reduce deployment costs and recover investment, physical network elements (such as 3GPP network architecture) and virtualized network elements (MANO network architecture) will coexist for a long time and jointly form network slices flexibly. Therefore, in order to quickly and flexibly provide differentiated communication requirements, operators need an automated slicing operation and maintenance system that can manage and orchestrate physical network functions and virtualized network functions at the same time, and can implement physical and virtual network functions/resources Orchestration management implements network slicing. The network slicing operation and maintenance system is also an important part of the next stage of 3GPP SA5 standardization.

When multiple network slices coexist, the network slices may be completely isolated, or they may share some network resources and functions. For the coexistence of multiple slices, TR 23.799 gives two main scenarios: Group A (Group A) and Group (Group B), as shown in Figure 2 and Figure 3, respectively. Fig. 2 shows a schematic structural block diagram of network slicing according to an embodiment of the present invention. In Fig. 2, slice instance 1 and slice instance 2 share a radio access network (English: Radio Access Network, abbreviated: RAN), core network The slice instance of is completely isolated logically, and the two slice instances are also completely isolated in management; FIG. 3 shows a schematic structural block diagram of network slice in another embodiment of the present invention. In FIG. There is a part of the shared control plane function between slice instances 2, which is called the shared control plane network function (English: Common ControlPlane Network Function, abbreviation: common CP NF), and each slice instance also has its own control plane network function (English : Common Control Plane Network Function, abbreviation: slice-specific CP NF) and dedicated user plane network function (English: Slice-specific User Plane Network Function, abbreviation: slice-specific UP NF), slice instance 1 of Group B (Instance slice 1) and the slice instance (Instance slice2) in the process of management, it is necessary to consider the impact of the sharing function on other slice instances.

FIG. 4 shows a schematic architecture diagram of a 3rd Generation Partnership Project 3GPP network.

The existing 3GPP telecom network management architecture is shown in FIG. 4 . The network management architecture 400 includes at least one network element (Network Element, referred to as "NE"), at least one network element management (Element Manager, referred to as "EM") module, at least one domain manager (Domain Manager, referred to as " DM") and network management (Network Manager, referred to as "NM") module.

Among them, 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 handling individual NEs, including alarm management, notification management, log records, and software and hardware maintenance.

Among them, the NM is responsible for managing the entire telecommunication network. It is supported by multiple EMs, but it can also be directly connected to the NE. It mainly provides online management functions, management of interaction between devices and other related functions, such as the division of network resources, Configuration, control and monitoring, etc.

The 3GPP network management architecture in the prior art can only manage physical resources and physical network functions, but cannot manage virtual resources and virtual network functions, let alone manage network slices and network slice instances.

Fig. 5 shows a schematic architecture diagram of the fusion of 3GPP network architecture and MANO network architecture, so that the NM can manage not only physical network functions, but also virtual network functions.

As shown in Figure 5, the MANO network architecture in the virtual box on the left mainly includes: Network Function Virtualization Orchestrator (English: Network Functions Virtualization Orchestrator, abbreviation: NFVO), responsible for network services, virtual network function modules (English: Virtualized Network Function , abbreviation: VNF) lifecycle management, and optimize resource utilization from a global perspective for network function virtualization infrastructure (English: Network Functions Virtualization Infrastructure, abbreviation: NFVI); virtual infrastructure manager (English: VirtualizedInfrastructure Manager, abbreviation : VIM), used to control and manage computing, storage, and network resources of NFVI; virtual network function manager (English: Virtualized Network Function Manager, abbreviated: VNFM), used to manage 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 NFVI and a new type of EM capable of managing VNFs are added.

The network architecture shown in Figure 5 can realize the management of virtual network resources and virtual network functions, or the management of physical network resources and physical network functions, but cannot realize the management of network slices, that is, cannot manage physical resources, Network functions, virtual resources, and network functions are managed and orchestrated in a unified manner to support the requirements of complete resource isolation, independent management, and resource orchestration among multiple slices in the next-generation mobile network without sharing functions, and cannot support when there is sharing among multiple slices Sharing of resources and network functions during functions, and requirements for network-specific functions, isolation of resources, and independent management.

Fig. 6 shows a schematic structural diagram of a network slice management and orchestrator according to an embodiment of the present invention.

The traditional 3GPP network management system and the network management system after the integration of MANO cannot perform unified management and orchestration of network slices. Therefore, the present invention proposes a network slice manager and orchestrator (English: Network slicemanager&orchestrator, NSM&O for short). NSM&O's The structure is shown in Figure 6, which mainly includes the following functional modules: service conversion module, network slice design module, network slice policy management module, network slice orchestration module, and network slice monitoring module.

Specifically, the service translation (Service translation) module is used to: receive the service description sent by the sender Sender through an application programming interface (English: Application Programming Interface, abbreviation: API), and convert the service description into a requirement for the network.

The network slice design (Slice design) module is used for: according to the result of service conversion, design network slice template NSLD, describe the composition of network slice.

The Slice policy management module is used for: on-boarding, instantiation, scaling, update, termination, deletion of network slices, etc. aspect.

The slice orchestration (Slice orchestration) module is used for: specifically determining the network function (English: Network Function, abbreviated: NF), resources, etc. included in the network slice instance.

The monitoring and reporting (Monitoring) module is used for: monitoring and reporting the key performance indicator (English: Key performance indicator, abbreviated: KPI) parameters of the network slice instance.

Among them, the entities related to NSM&O also include: storage (English: Repository), which is used to record the network slice template (English: Network Slice Description, abbreviation: NSLD) and related information of the generated network slice instance; the sender Sender It can be an operator (operator), a third-party customer/tenant (customer/tender), a service design application (service design application), a device vendor (vendor), or any entity in the SP domain that may send a request to NSM&O. The present invention No limit.

It should be understood that the above concepts such as network slice management and orchestrator and network slice target may be replaced by different names in different scenarios, and entities capable of realizing the above network functions all fall within the scope of protection of the present invention.

Fig. 7 is a schematic flowchart of a method for managing network slicing according to an embodiment of the present invention. The execution subject of the method may be the network slicing management and orchestrator NSM&O. As shown in Fig. 7 , the method includes:

Step 710, 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 deletion of the target network slice or termination of the target network slice instance.

Step 720, 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.

In step 710, the target network slice refers to the network slice that the sender 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 the identifier of the NSLD corresponding to the network slice, the identity identifier of the Sender, and the like. Sender may be an authorized third-party tenant, operator, or an application that has the right to terminate network slice instances/delete network slices.

In step 720, NSM&O performs network slice management on the target network slice according to the management request message, which means: when the management request message requests to delete the target network slice, delete the target network slice; when the management request message requests to terminate the target network slice instance, terminate the target network slice instance.

Furthermore, NSM&O can control the physical network function management device to perform network slice management on the target network slice. The physical network function device may include one or more physical entities in the 3GPP network architecture, such as EM, etc.; NSM&O can also control the virtual network function The management device performs network slice management on the target network slice. The virtual network function management device can include one or more entities in the MANO network structure, such as VNFM, etc.; similarly, NSM&O can use the physical network function management device and the virtual network function at the same time The management device manages the target network slice.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Optionally, as an embodiment of the present invention, 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 includes: when the The management request message is used to control the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance when requesting termination of the target network slice instance; and/or control the termination of the physical network function management device The physical network function PNF corresponding to the target network slice instance.

That is to say, NSM&O can terminate the virtual network function VNF corresponding to the target network slice instance by controlling the virtual network function management device; and NSM&O can terminate the physical network function PNF corresponding to the target network slice instance by controlling the physical network function management device; further Specifically, NSM&O can realize the termination of the PNF and VNF in the network slice instance by controlling the virtual network function management device and the physical network function management device.

Optionally, as an embodiment of the present invention, the physical network function management device includes 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 includes: when the When the PNF corresponding to the target network slice instance includes the first PNF, instruct the network element manager EM that manages the first PNF to configure the first PNF to terminate services for 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, and instructs the EM managing the shared PNF to set the shared PNF as a terminal to the target network Slice instance service, the request includes but is not limited to: instruct EM to stop providing services to the target network slice instance, delete configuration parameters used to support target network slice instance services such as network slice instance identifier, delete service target network slice instance policy , terminate/delete the network connection between the first PNF and the dedicated network function of the target network slice instance, etc., and the EM sets the shared PNF as the service for terminating the target network slice instance, which does not affect other network slice instances using the shared PNF services.

Specifically, when the target network slice instance includes a dedicated PNF, NSM&O initiates a request to configure the network function to the EM managing the dedicated PNF through the Itf-N interface, and instructs the EM managing the shared PNF to set the dedicated PNF as the termination target The service of the network slice instance, the request includes but is not limited to: instruct EM to stop providing services to the target network slice instance, delete the configuration parameters used to support the service of the target network slice instance such as the network slice instance identifier, delete the service target network slice instance Policies to terminate/delete the network connection between the PNF and the dedicated network function of the target network slice instance, 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, the NSM&O closes/deregisters the virtual port dedicated to the PNF; otherwise, the EM closes/deregisters the virtual port of the PNF.

It should be understood that a shared physical network function may also be called a general physical network function, and a shared virtual network function may also be called a general virtual network function. 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; the shared network function refers to the physical network function that can be shared by multiple network slice instances.

Optionally, as an embodiment of the present invention, the physical network function management device includes 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 includes: when the When the VNF corresponding to the target network slice embodiment includes a shared VNF, instruct the EM that manages the shared VNF to configure the shared VNF to terminate services for the target network slice instance.

That is to say, when the VNF in the target network slicing instance includes a shared VNF, NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, instructing the EM managing the shared VNF to set the shared VNF In order to terminate the service to the target network slice instance, the request includes but is not limited to: instruct EM to stop providing services to the target network slice instance, delete the configuration parameters used to support the service of the target network slice instance such as the network slice instance identifier, delete the service target Policy for network slice instances.

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 dedicated network function of the target network slice instance, releasing corresponding network resources. VIM executes the request and returns the execution result.

Optionally, as an embodiment of the present invention, the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance includes: instructing the virtualization infrastructure management device VIM to transfer the shared VNF configured to terminate a network connection associated with a target network slice instance, and/or shrink network resources associated with the target network slice instance, wherein the virtual network function management device includes the VIM; or instruct a virtual network function orchestrator The NFVO configures the shared VNF to terminate network connections related to the target network slice instance and/or shrink network resources related to the target network slice instance, wherein the virtual network function management device includes the NFVO.

Optionally, as an embodiment of the present invention, the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance includes: when the VNF corresponding to the target network slice instance includes In the case of a dedicated VNF, instruct the EM managing the dedicated VNF to terminate the management of the dedicated VNF.

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

Specifically, NSM&O sends to VIM to delete, release resources used by these VNFs and A network connection request; VIM executes the deletion required by NSM&O, releases the resources used by these VNFs, and deletes the network connection request dedicated to the network slice instance; VIM feeds back the deletion and release completion confirmation to NSM&O.

Optionally, as an embodiment of the present invention, the virtual network function management device includes NFVO, and the controlling the virtual network function management device to terminate the virtual network function VNF corresponding to the target network slice instance, terminate the target The embodiment of network slicing includes: instructing the NFVO to close the network connection related to the dedicated VNF, and/or release the network resources related to the shared VNF.

Specifically, NSM&O notifies NFVO to terminate the target NSI-specific VNF and delete the dedicated network connection with the target NSI; NFVO executes the slice-specific VNF termination process and the dedicated network connection deletion process; NFVO reports to NSM&O that the above-mentioned dedicated VNF termination and deletion process has been completed.

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

For example, during the instantiation process of the target network slice, it is a VNF generated by the NM, and the NSM&O initiates a request for configuring the network function to the EM that manages the VNF. The request includes but is not limited to stopping the service provided to the target NSI, deleting the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and deleting the policy serving the target NSI. EM executes the request and feeds back the execution result. NSM&O notifies NFVO to terminate/close the possible network connection between the VNF and the target NSI dedicated network function, and release corresponding network resources. NFVO executes the request and feeds back the execution result.

It should be understood that all the VNFs and/or PNFs included in the target network slice instance can be terminated in the above manner, when all the VNFs and/or PNFs included in the target network slice instance are terminated, it means that the target network slice instance Also finished.

Therefore, in the embodiment of the present invention, the network slice management of the target network slice by NSM&O can realize the differentiated management of the general network function and the dedicated network function of the network slice instance, so that the termination of the target network slice embodiment will not cause damage to other network slice instances. influences.

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

Optionally, as an embodiment of the present invention, 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 includes: when the The management request message is used to control the physical network function management device and/or the virtual network function management device to delete the target network slice when deleting the target network slice.

Optionally, as an embodiment of the present invention, the controlling the physical network function management device and/or the virtual network function management device to delete the target network slice includes: controlling the physical network function management device and/or the virtual network function management device The network function management device terminates the VNF and/or PNF corresponding to each instance in the target network slice.

That is, when the above 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 above method, I won't repeat them here.

Optionally, as an embodiment of the present invention, 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 includes: when determining that the After all the instances in the target network slice are terminated, instruct the storage Repository to delete the slice template of the target network slice.

Optionally, as an embodiment of the present invention, before 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, the The method further includes: verifying whether the sender Sender who initiates the management request message has the authority to manage the network slice of the target network slice.

Optionally, as an embodiment of the present invention, the verifying whether the sender Sender that initiates the management request message has the authority to manage the network slice of the target network slice includes: sending a verification message to the Repository, the The verification message is used by the Repository to determine whether the Sender has the authority to perform network slice management on the target network slice; the verification completion message fed back by the Repository is received, and the verification completion message is used to notify the NSM&O whether the Sender is It has the permission to manage the network slice of the target network slice.

Optionally, as an embodiment of the present invention, the method further includes: when it is determined that the Sender does not have the authority to manage the network slice of the target network slice, sending a verification failure message to the Sender, the verification The failure message is used to notify the Sender that it does not have the right to perform network slice management on the target network slice.

Optionally, as an embodiment of the present invention, the method further includes: when the NSM&O completes the management of the target network slice, sending a management completion message to the sender Sender, and the management completion message is used to notify the The Sender has completed deleting the target network slice or terminating the target network slice instance.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Therefore, when network slices need to be deleted, NSM&O can manage physical and virtual network functions, arrange physical and virtual resources in a unified manner, make policies more flexible, and use network resources optimally; when network slice instances need to be terminated, the network can be terminated. When slicing the shared VNF, you can choose to shrink the resources of the VNF according to your needs, which can improve resource utilization.

FIG. 8 is a schematic flow chart of a method for managing network slicing according to another embodiment of the present invention. The execution subject of the method may be the sending end Sender. As shown in FIG. 8 , the method includes:

Step 810, the sending end Sender sends a management request message of the target network slice to the network slice management and orchestrator NSM&O, and 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 Sender receives a management completion message sent by the NSM&O, where the management completion 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, as an embodiment of the present invention, the method further includes: receiving a verification failure message sent by the NSM&O, where the verification failure message is used to notify that target network slice management cannot be performed.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

FIG. 9 is a schematic flowchart of a method for managing network slices according to another embodiment of the present invention. The execution subject of the method is a memory Repository. As shown in FIG. 9 , the method includes:

Step 910, the storage Repository receives a verification message from the network slice management and orchestrator NSM&O, wherein the verification message is used to verify whether the sender Sender who initiates the network slice management request has the authority to perform network slice management on the target network slice.

Step 910, the Repository verifies whether the Sender has the right to manage the network slice of the target network slice according to the verification message.

Optionally, as an embodiment of the present invention, the returning a verification completion message to the NSM&O, so that the NSM&O can determine whether to manage the target network slice according to the verification feedback message, includes: sending the NSM&O returns a verification completion message, and the verification completion message is used to notify the NSM&O whether the Sender has the authority to perform network slice management on the target network slice; when the Sender does not have the network slice to the target network slice When the management authority or the instance of the target network slice does not exist, the verification feedback message is used to inform the NSM&O that the Sender does not have the authority to perform network slice management on the target network slice; or when the Sender has the authority to When the network slice management authority of the target network slice is used, the verification feedback message is used to inform the NSM&O that the Sender has the authority to perform network slice management on the target network slice.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Fig. 10 shows a schematic block diagram of a network architecture of an embodiment of the present invention.

The network architecture 1 (option 1) shown in Figure 10 is an improvement to the existing 3GPP Operation Support System (English: Operation Support System, abbreviated: OSS system) (the embodiment shown in Figure 4 ), NSM&O It can realize the function of the NM in the original 3GPP network architecture. Specifically, NSM&O interacts with EM through the Itf-N interface to implement management including physical network function (English: Physical Network Function, abbreviated: PNF) and virtual network function (English: VirtualNetwork Function, abbreviated: VNF); for example, in Figure 10 PNF can be NE, and NSM&O receives status information about VNF from NFVO through Os-Ma-nfvo interface, and sends instructions to NFVO through this interface to participate in the life cycle management process of VNF.

Therefore, the network architecture is evolved and upgraded on the OSS system, with minor changes to the existing network architecture and interfaces. NSM&O can directly manage physical network functions, and use NFVO to realize the orchestration management of NFVI resources and the generation of VNFs.

Fig. 11A shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention. This FIG. 11A shows a flowchart of network slice management based on the network structure shown in FIG. 10 .

As shown in Figure 11A, the method includes:

Step 1101, the Sender sends a target network slice instance termination request or a target network slice deletion request to NSM&O.

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

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 the identifier of the NSLD corresponding to the network slice, the identity identifier of the Sender, and the like. Sender may be an authorized third-party tenant, operator, or an application that has the right to terminate network slice instances/delete network slices.

Step 1102, authenticating, authenticating, verifying and checking the target network slice (or the target network slice instance).

Specifically, after receiving the target network slice instance termination request or the target network slice deletion request sent by the Sender, NSM&O needs to exchange information with the Repository, authenticate the identity of the Sender through the Repository, and verify the integrity of the parameters in the request (such as target Whether the format of the network slice instance identifier is correct, whether the format of the NSLD identifier corresponding to the target network slice is correct, etc.), whether the authentication Sender has the authority 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 running status of the target network slice instance, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current status of the target network slice.

When in step 1101, the request sent by the Sender is to terminate the target network slice instance, the following steps are performed:

If the authentication fails, execute step 1102', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to terminate the slice instance, and cannot verify the identity of the Sender;

If the verification and authentication pass and the target network slice instance exists, execute step 1103;

If the verification and authentication pass but the network slice instance does not exist, execute step 1102', that is, the NSM&O feeds back a parameter error to the Sender, and informs the Sender that the above target network slice instance does not exist.

Or, when in step 1101, the request sent by the Sender is to delete the target network slice, perform the following steps:

If the authentication fails, execute step 1102', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to delete the network slice, and cannot verify the identity of the Sender;

If the authentication is passed and the NSLD corresponding to the target network slice exists, after deleting all the instances of the target network slice, NSM&O performs step 1112 to delete the NSLD corresponding to the target network slice;

If the NSLD corresponding to the target network slice does not exist, NSM&O feeds back a 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 a specific interaction process for the NSM&O to verify whether the sender Sender who initiated the management request message has the authority to manage the network slice of the target network slice.

Step 1103, NSM&O controls EM and NFVO to configure network functions, delete configurations and network connections related to target network slice instances, specifically including:

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 general network functions, including shared VNF and shared PNF; and NSM&O detects whether the target NSI to be terminated has a dedicated network function.

(1) When the target NSI includes 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, and instructs the EM managing the shared PNF to set the shared PNF as a terminal to the target NSI The service, the request includes but is not limited to: instruct EM to stop sharing the service provided by the PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the service target NSI policy, terminate/delete the PNF and Network connections between target NSI-specific network functions, etc.

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 services to the target NSI.

It should be understood that (1) in step 1103 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the target NSI includes a shared VNF, NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, and instructs the EM managing the shared VNF to set the shared VNF as a terminal to the target NSI The service, the request includes but is not limited to: instruct EM to stop the service provided by the shared VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the policy serving the target NSI.

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

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

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

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

Further, in step 1103, the NSM&O detects whether the target NSI 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, and instructs the EM managing the dedicated PNF to set the dedicated PNF as the terminal to the target NSI Service, the request includes but is not limited to: instruct EM to stop the service provided by the dedicated PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the policy of serving the target NSI, terminate/delete the PNF and the target Network connections between NSI exclusive network functions, etc.

Further, the EM managing the dedicated PNF executes the request and feeds back the execution result. If the EM is built in the PNF, the 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 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate 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 dedicated PNFs in the target NSI are configured to terminate services 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, and instructs the EM managing the dedicated VNF to set the dedicated VNF as the terminal to the target NSI service, and at the same time terminate the management of the dedicated VNF by EM, that is, step 1104 in the process shown in Figure 11, terminate the dedicated VNF management request, the request includes but is not limited to: instruct to stop monitoring the running status of the VNF, terminate the VNF management function, delete the management object.

If the shared VNF, dedicated VNF, shared PNF and dedicated PNF of the target NSI have all been terminated, the network slice instance has been terminated, and step 1114 is executed.

It should be understood that the process of terminating the shared PNF, dedicated PNF, shared VNF and dedicated VNF has no sequence requirement for the target network slicing service, which is not limited in the present invention.

Step 1105, delete the management object of the VNF, that is, the EM that manages the dedicated VNF executes the NSM&O's request for terminating the VNF management in step 1104.

Step 1106: Feedback that the termination of the VNF management object is completed, that is, the EM that manages the above-mentioned dedicated VNF feeds back the confirmation of the termination management completion to the NSM&O through the Itf-N interface.

Step 1107, NSM&O notifies the EM managing the above-mentioned dedicated VNF through the Itf-N interface to close the virtual port of the dedicated VNF and stop the service to the target NSI.

Step 1108, the NSM&O notifies the NFVO through the Os-Ma-nfvo interface to terminate the target NSI-specific VNF and delete the network connection with the target NSI-specific network.

Step 1109, NFVO executes slice-specific VNF termination process and dedicated network connection deletion process.

Step 1110: Feedback that the termination of the VNF is completed, that is, the NFVO reports to the NSM&O through the Os-Ma-nfvo interface that the termination and deletion process of the above-mentioned dedicated VNF has been completed.

It should be understood that, from step 1104 to step 1110, the NSM&O instructs the EM managing the dedicated VNF to configure the dedicated VNF to terminate the service for the target network slice instance.

Step 1111, update the slice instance memory, specifically, if there are other functions implemented by the dedicated VNF in the dedicated network function of the target NSI that have not been terminated, repeat steps 1104-1110, if all VNFs and PNFs corresponding to the target NSI have been deleted If it is terminated, the target NSI has been terminated, and NSM&O deletes the information of the target NSI in the instance memory of the Repository slice. If in step 1101 the Sender sends a network slice instance termination request, go to step 1114 , otherwise go to step 1112 .

Optionally, in step 1112, 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 1103-1111 for this slice instance, if there is no network slice instance generated based on the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used . If NSLD is being used, feedback network slice deletion error. If the NSLD is not in use, go to step 1113.

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

It should be understood that steps 1112 and 1113 need to be executed only when the Sender sends a network slice deletion request.

In step 1114, the Sender is notified that the termination of the network slice instance/deletion of the network slice is completed.

Therefore, the embodiment of the present invention controls physical network function management devices and virtual network function management devices, supports network slice management, supports direct orchestration management of physical network functions, and uses NFV MANO system management orchestration for virtual network functions to support this system architecture The next network slice instance is terminated and the network slice is deleted. In the embodiment of the present invention, the operator or the authorized third-party tenant of the network slicing instance can request to terminate the network slicing instance when the cost of maintaining the existing slicing instance is higher than the benefits brought by its service, and at the same time allows the operator to decide not to When the current type of network slicing is supported, such as network slicing version upgrade, request to delete the network slicing.

In addition, the present invention differentiates between the general network functions shared by the network slice instance and other slice instances and the slice-specific network functions in the embodiment, so that the service of other network slice instances will not be affected when the current network slice instance is terminated.

FIG. 11B shows a schematic flowchart of managing network slices according to an embodiment of the present invention. Fig. 11B is a detailed flowchart of step 1103 in Fig. 11A.

Specifically include:

When the target NSI includes a shared PNF, NSM&O initiates a request for configuring the network function to the EM managing the shared PNF through the Itf-N interface, that is, step 1103_1, sending a configuration shared PNF request, instructing the EM managing the shared PNF to The shared PNF is set to terminate the service to the target NSI. The request includes but is not limited to: instruct the EM to stop the service provided by the shared PNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI The strategy of terminating/deleting the network connection between the PNF and the target NSI dedicated network function, etc.

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, send a configuration completion confirmation message, and repeat the above configuration steps until all shared PNFs in the target NSI are configured to terminate services to the target NSI.

When the target NSI includes a shared VNF, NSM&O initiates a request to configure the network function to the EM that manages the shared VNF through the Itf-N interface, that is, step 1103_4, sends a configuration shared VNF request, and instructs the EM that manages the shared VNF to configure the shared VNF. The shared VNF is set to terminate the service to the target NSI. The request includes but is not limited to: instruct the EM to stop the service provided by the shared VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI strategy.

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

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

In step 1103_8, the NFVO shrinks the VNF resource under the instruction of step 1103_8.

After the NFVO finishes shrinking the shared VNF resources, it feeds back the shrinking completion message to the NSM&O, which is step 1103_9.

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

When the target NSI includes a dedicated PNF, 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, sends a configuration dedicated PNF request to the EM, instructing the EM managing the dedicated PNF to The dedicated PNF is set to terminate the service for the target NSI, and the request includes but is not limited to: instruct the EM to stop the service provided by the dedicated PNF for the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI's policy to terminate/delete the network connection between the PNF and the target NSI's dedicated network function, etc.

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

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

It should be understood that the numbers of the above steps do not represent the order of execution. It should also be understood that in the specific implementation process, according to the specific conditions of the target network slice instance, some or all of the steps can be selected to be executed, which is not limited by the present invention.

Fig. 12 shows a schematic block diagram of the network architecture of an embodiment of the present invention.

The network architecture 2 (option 2) shown in FIG. 12 is an improvement to the existing 3GPP OSS system (the embodiment shown in FIG. 4 ), and NSM&O can realize the function of NM in the original 3GPP network architecture. Specifically, NSM&O interacts with EM through the Itf-N interface to realize the management of physical network functions (English: Physical Network Function, abbreviated: PNF) and virtual network functions (English: Virtual Network Function, abbreviated: VNF); NSM&O communicates with EM through the NG1 interface Interact information with VNFM, and at the same time, NSM&O interacts information with VIM through the NG2 interface to jointly participate in the VNF life cycle management process. Compared with architecture 1, other interfaces do not change. The interface between NSM&O and VNFM is temporarily called NG1 interface, and the interface between NSM&O and VIM is temporarily called NG2 interface.

Specifically, the functions of the NG1 interface mainly include: authorization, reservation, allocation, and release of NFVI resources to support the VNF; query of running state information; VNF initialization update, scaling, termination, etc., transmission of VNF-related events, 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, and upgrade records related to NFVI.

Therefore, the evolution and upgrade of the network architecture on the OSS system requires minor changes to the existing network architecture and interfaces. NSM&O has added the functions of virtual resource and VNF life cycle management, and unified management and orchestration of physical and virtual network resources. and functions, which are conducive to optimizing resources from a global perspective.

Fig. 13A shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention. This FIG. 13A shows a flowchart of network slice management based on the network structure shown in FIG. 12 .

As shown in Figure 13A, the method includes:

Step 1301, the Sender sends a target network slice instance termination request or a target network slice deletion request to NSM&O.

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

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 the identifier of the NSLD corresponding to the network slice, the identity identifier of the Sender, and the like. Sender may be an authorized third-party tenant, operator, or an application that has the right to terminate network slice instances/delete network slices.

Step 1302, authenticating, authenticating, verifying and checking the target network slice (or the target network slice instance).

Specifically, after receiving the target network slice instance termination request or the target network slice deletion request sent by the Sender, NSM&O needs to exchange information with the Repository, authenticate the identity of the Sender through the Repository, and verify the integrity of the parameters in the request (such as target Whether the format of the network slice instance identifier is correct, whether the format of the NSLD identifier corresponding to the target network slice is correct, etc.), whether the authentication Sender has the authority 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 running status of the target network slice instance, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.

When in step 1301, the request sent by the Sender is to terminate the target network slice instance, the following steps are performed:

If the authentication fails, execute step 1302', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to terminate the slice instance, and cannot verify the identity of the Sender;

If the verification and authentication pass and the target network slice instance exists, execute step 1103;

If the verification and authentication pass but the network slice instance does not exist, execute step 1102', that is, the NSM&O feeds back a parameter error to the Sender, and informs the Sender that the above target network slice instance does not exist.

Or, when in step 1301, the request sent by the Sender is to delete the target network slice, the following steps are performed:

If the authentication fails, execute step 1302', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to delete the network slice, and cannot verify the identity of the Sender;

If the authentication is passed and the NSLD corresponding to the target network slice exists, after deleting all instances of the target network slice, NSM&O performs step 1315 to delete the NSLD corresponding to the target network slice;

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

It should be understood that steps 1301 to 1302 or step 1302' are a specific interaction process for the NSM&O to verify whether the sender Sender who initiated the management request message has the authority to manage the network slice of the target network slice.

Step 1303, 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 general network functions, including shared VNF and shared PNF; and NSM&O detects whether the target NSI to be terminated has a dedicated Network features.

(1) When the target NSI includes 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, and instructs the EM managing the shared PNF to set the shared PNF as a terminal to the target NSI The service, the request includes but is not limited to: instruct EM to stop sharing the service provided by the PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the service target NSI policy, terminate/delete the PNF and Network connections between target NSI-specific network functions, etc.

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 are configured to terminate services to the target NSI.

It should be understood that (1) in step 1303 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the target NSI includes a shared VNF, NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the Itf-N interface, and instructs the EM managing the shared VNF to set the shared VNF as a terminal to the target NSI The service, the request includes but is not limited to: instruct EM to stop the service provided by the shared VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the policy serving the target NSI.

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

Further, the NSM&O notifies the VIM through the NG2 interface to terminate/close the possible network connection between the shared VNF and the dedicated network function of the target NSI, releasing corresponding network resources. VIM executes the request and feeds back the execution result through the NG2 interface.

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

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

It should be understood that (2) in step 1303 is a specific interaction process instructing the NSM&O to instruct the EM managing the shared VNF to configure the shared VNF to terminate the service for 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, and instructs the EM managing the dedicated PNF to set the dedicated PNF as the terminal to the target NSI Services, the request includes but is not limited to: instruct EM to stop sharing the services provided by the PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the service target NSI policy, terminate/delete the PNF and the target Network connections between NSI exclusive network functions, etc.

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

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

It should be understood that (3) in step 1303 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for 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, and instructs the EM managing the shared VNF to set the dedicated VNF as the terminal to the target NSI service, and configure the EM to terminate the management of the dedicated VNF, which is step 1304 in the process shown in Figure 13. The request includes but is not limited to: instructing to stop monitoring the running status of the VNF, terminating the management function of the VNF, Delete managed objects.

If the shared VNF, dedicated VNF, shared PNF and dedicated PNF of the target NSI have all been terminated, the network slice instance has been terminated, and step 1114 is executed.

In step 1305, the EM managing the dedicated VNF executes the NSM&O request in step 1104 for terminating the management of the VNF.

Step 1306, the EM that manages the above-mentioned exclusive VNF feeds back a confirmation of the completion of the management to the NSM&O through the Itf-N interface.

In step 1307, the NSM&O notifies the EM managing the dedicated VNF through the Itf-N interface to close the virtual port of the dedicated VNF and stop serving the target NSI.

Step 1308, NSM&O initiates a request to terminate the dedicated VNF to the VNFM through the NG1 interface, and the request includes terminating the service running on the target NSI and shutting down the above-mentioned dedicated VNF.

In step 1309, the VNFM executes the NSM&O in step 1308 to terminate the running service of the dedicated VNF, and the VNFM and the internal mechanism of the VNF jointly shut down the VNF.

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

Step 1311, NSM&O sends a delete and release message to the VIM through the NG2 interface based on the information on the resources (including computing, storage, and network resources) used to support the operation of the dedicated VNF and the information on the exclusive network connection that supports the operation of the network slice instance. Requests for resources and network connections used.

In step 1312, the VIM executes the request to delete and release the resources used by these VNFs requested by the NSM&O in step 1311, and delete the network connection dedicated to the network slice instance.

Step 1313, the VIM feeds back a deletion and release completion confirmation to the NSM&O through the NG2 interface.

It should be understood that, from step 1304 to step 1313, the NSM&O instructs the EM managing the dedicated VNF to configure the dedicated VNF to terminate the service for the target network slice instance.

Step 1314, if there are other functions implemented by the dedicated VNF in the dedicated network function of the target NSI that have not been terminated, repeat steps 1304-1313, if all VNFs and PNFs corresponding to the target NSI have been terminated, the target NSI has been terminated , NSM&O is to delete the information of the target NSI in the instance memory of the Repository slice. If in step 1301 the Sender sends a network slice instance termination request, go to step 1317 , otherwise go to step 1315 .

Optionally, in step 1315, 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 1303-1314 for this 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 NSLD is being used, feedback network slice deletion error. If the NSLD is not in use, go to step 1316 .

Optionally, in step 1316, the NSM&O deletes the current version NSLD from the Repository.

It should be understood that steps 1315 and 1316 need to be executed only when the Sender sends a network slice deletion request.

Step 1317, notify the Sender that the termination of the network slice instance/deletion of the network slice is completed.

Therefore, the embodiment of the present invention controls physical network function management devices and virtual network function management devices, supports network slice management, supports direct orchestration management of physical network functions, and uses NFV MANO system management orchestration for virtual network functions to support this system architecture The next network slice instance is terminated and the network slice is deleted. In the embodiment of the present invention, the operator or the authorized third-party tenant of the network slicing instance can request to terminate the network slicing instance when the cost of maintaining the existing slicing instance is higher than the benefits brought by its service, and at the same time allows the operator to decide not to When the current type of network slicing is supported, such as network slicing version upgrade, request to delete the network slicing.

In addition, the present invention differentiates between the general network functions shared by the network slice instance and other slice instances and the slice-specific network functions in the embodiment, so that the service of other network slice instances will not be affected when the current network slice instance is terminated.

Fig. 13B shows a schematic flowchart of managing network slices according to an embodiment of the present invention. FIG. 13B is a detailed flowchart of step 1103 in FIG. 13A.

Specifically include:

When the target NSI includes a shared PNF, 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 1303_1, sending a configuration shared PNF request instructing the EM managing the shared PNF to set the shared The PNF is set to terminate the service for the target NSI. The request includes but is not limited to: instruct the EM to stop sharing the service provided by the PNF for the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI. Policy, terminate/delete network connection between PNF and target NSI dedicated network function, etc.

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

Further, in step 1303_3, send a confirmation configuration completion message.

Repeat the above configuration steps until all shared PNFs in the target NSI are configured to terminate services to the target NSI.

When the target NSI includes a shared VNF, 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 1303_4, sending a configuration shared VNF request, instructing the EM managing the shared VNF to The shared VNF is set to terminate the service to the target NSI. The request includes but is not limited to: instruct the EM to stop the service provided by the shared VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI strategy.

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

Step 1303_7, notify the VNFM through the NG1 interface to shrink the resources of the shared VNF.

In step 1303_8, the VNFM conducts shrinkage feasibility testing. Specifically, two things need 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; Shut down some of the virtual machines VMs that make up the VNF, and the VNFM shuts down these virtual machines.

In step 1303_9, the VNFM returns a contraction 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 dedicated network function through the NG2 interface, that is, step 1303_10, sending a connection request to the VIM, and optionally requesting a resource allocation change, Release corresponding network resources.

In step 1303_11, VIM executes the request, and in step 1303_12 informs NSM&O that the connection has been deleted, resources are released, and the execution result is fed back through the NG2 interface.

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

In step 1303_14, the VNFM sends configuration contraction end feedback to the NSM&O.

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

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 1303_15, sends a configuration dedicated PNF request to the EM, instructing the EM managing the dedicated PNF to The dedicated PNF is set to terminate the service for the target NSI, and the request includes but is not limited to: instruct the EM to stop the service provided by the shared PNF for the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the service target NSI's policy to terminate/delete the network connection between the PNF and the target NSI's dedicated network function, etc.

Further, in step 1303_15 and step 1303_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 in the PNF, the NSM&O closes/deregisters the virtual port of the PNF; otherwise, the EM closes/deregisters the virtual port of the PNF.

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

It should be understood that the numbers of the above steps do not represent the order of execution. It should also be understood that in the specific implementation process, according to the specific conditions of the target network slice instance, some or all of the steps can be selected to be executed, which is not limited by the present invention.

Fig. 14 shows a schematic block diagram of the network architecture of an embodiment of the present invention.

Network architecture 3 (option 3) shown in FIG. 14 is an improvement to the existing 3GPP OSS system (the embodiment shown in FIG. 4 ), and NSM&O can realize the function of NM in the original 3GPP network architecture. Specifically, NSM&O interacts with EM through the NG5 interface to manage physical network functions (English: Physical Network Function, abbreviated: PNF) and virtual network functions (English: Virtual Network Function, abbreviated: VNF); this NSM&O is independent of existing The NM system does not make any upgrade changes to the NM system, and introduces a new set of slice arrangement management and system. The interface between NSM&O and NM system is temporarily called NG3 interface, and the interface between NSM&O and NFVO is temporarily called NG4 Interface, the interface between NSM&O and EM is temporarily called NG5 interface.

Specifically, the functions of NG3 mainly include: transmitting the negotiation information between NSM&O and NM, such as NSM&O querying the VNF generated by NM; NM feeding back the VNF information generated by NSM&O and confirming that modification is allowed; /VNF to be modified; NSM&O notifies NM of specific modification contents for PNF/VNF.

The functions of NG4 mainly include: NSM&O participates in the lifecycle management of VNF through this interface, such as notifying NFVO to generate, update, and delete a VNF, etc.; NSM&O queries NFVO, and NFVO feeds back the operation information of VNF and NFVI to NSM&O; policy management, NSM&O can send NFVO sends policies to indicate the requirements for VNF deployment; NSM&O manages VNF packages 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 is upgraded on the OSS system without changing the existing network architecture and interfaces. This architecture does not need to change the NM, but provides a new management system, which needs to adopt new interfaces and existing Entities interact. Both NSM&O and NM can directly manage PNF, and both NSM&O and NM can manage VNF through NFVO or EM; further, NSM&O can orchestrate and manage virtual resources through NFVO.

Fig. 15 shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention. This FIG. 15 shows a flowchart of network slice management based on the network structure shown in FIG. 14 .

As shown in Figure 15, the method includes:

Step 1501, the Sender sends a target network slice instance termination request or a target network slice deletion request to NSM&O.

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

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 the identifier of the NSLD corresponding to the network slice, the identity identifier of the Sender, and the like. Sender may be an authorized third-party tenant, operator, or an application that has the right to terminate network slice instances/delete network slices.

Step 1502, authenticating, authenticating, verifying and checking 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 Sender, NSM&O needs to exchange information with the Repository, authenticate the identity of the Sender through the Repository, and verify the integrity of the parameters in the request (such as target Whether the format of the network slice instance identifier is correct, whether the format of the NSLD identifier corresponding to the target network slice is correct, etc.), whether the authentication Sender has the authority 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 running status of the target network slice instance, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.

When in step 1501, the request sent by the Sender is to terminate the target network slice instance, the following steps are performed:

If the authentication fails, execute step 1502', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to terminate the slice instance, and cannot verify the identity of the Sender;

If the verification and authentication pass and the target network slice instance exists, execute step 1503;

If the verification and authentication pass but the network slice instance does not exist, execute step 1502', that is, the NSM&O feeds back a parameter error to the Sender and informs the Sender that the above target network slice instance does not exist.

Or, when in step 1501, the request sent by the Sender is to delete the target network slice, the following steps are performed:

If the authentication fails, execute step 1502', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to delete the network slice, and cannot verify the identity of the Sender;

If the authentication is passed and the NSLD corresponding to the target network slice exists, after terminating all network slice instances included in the target network slice, NSM&O executes step 1514;

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

It should be understood that steps 1501 to 1502 or step 1502' are a specific interaction process for the NSM&O to verify whether the sender Sender who initiated the management request message has the authority to manage the network slice of the target network slice.

Step 1503: NSM&O notifies NM that it will configure network functions. Specifically, before terminating the network slice instance, NSM&O notifies NM through the NG3 interface that it will adjust the physical network functions and virtual network functions jointly managed by NM to avoid conflicts. In the notification, at least The identifiers of the physical network functions and virtual network functions involved shall be included.

In step 1504, the NM returns a notification confirmation to the NSM&O, that is, after receiving the notification, the NM feeds back a notification confirmation to the NSM&O through the NG3 interface. Before the NM receives the NSM&O modification completion message, it will no longer monitor and modify the configuration of these physical network functions and virtual network functions.

Step 1505, 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 general network functions, including shared VNF and shared PNF; and NSM&O detects whether the target NSI to be terminated has a dedicated Network features.

(1) When the target NSI includes a shared PNF, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the NG5 interface, and instructs the EM managing the shared PNF to set the shared PNF to terminate the service to the target NSI , the request includes but is not limited to: instruct EM to stop sharing the service provided by the PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the policy of serving the target NSI, terminate/delete the PNF and the target NSI Network connections between dedicated network functions, etc.

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 are configured to terminate services to the target NSI.

It should be understood that (1) in step 1505 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the target NSI includes a shared VNF, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the NG5 interface, and instructs the EM managing the shared VNF to set the shared VNF to terminate the service to the target NSI , the request includes but is not limited to: instruct the EM to stop sharing the services provided by the VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the policy serving the target NSI.

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

Further, the NSM&O notifies 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, the above steps are repeated until all shared VNFs in the target NSI are configured to terminate services to the target NSI.

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

It should be understood that (2) in step 1505 is a specific interaction process in which the NSM&O indicates that the EM managing the shared VNF configures the shared VNF to terminate the service for 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: instruct the EM to stop the service provided by the dedicated PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the policy serving the target NSI, terminate/delete the PNF and the target NSI exclusive Network connections between network functions, etc.

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

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

It should be understood that (3) in step 1505 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for the target network slice instance. At this time, the first PNF is a dedicated PNF.

It should also be understood that the interaction process in step 1505 is similar to the interaction process in FIG. 11B , and will not be repeated here.

(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, and instructs the EM managing the dedicated VNF to set the dedicated VNF to terminate the service to the target NSI, At the same time, the management of the dedicated VNF by the EM is terminated, which is step 1506 in the process shown in Figure 15. NSM&O sends a request to the EM to terminate the management of the dedicated VNF. The management function of the VNF deletes the management object.

It should be understood that if the above-mentioned dedicated VNF is not generated by NSM&O, such as the dedicated VNF generated by NM, then NSM&O can instruct the physical network function device and the virtual network function device to close the service of the dedicated VNF to the target network slice instance, instead of terminating The dedicated VNF serves the target network slice instance.

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

Step 1507, the EM managing the dedicated VNF executes the NSM&O request in step 1506 for terminating the management of the dedicated VNF, and deletes the management object of the dedicated VNF.

Step 1508, the EM that manages the above-mentioned dedicated VNF feeds back the completion confirmation of the termination management to the NSM&O through the NG5 interface, and feeds back the termination completion message of the VNF management object.

Step 1509, NSM&O or EM closes/deregisters the virtual port of the VNF, and the NSM&O notifies the EM managing the above-mentioned dedicated VNF through the NG5 interface to close the virtual port of the dedicated VNF, and stop serving the target NSI.

Step 1510, the NSM&O initiates a request to the NFVO to terminate the dedicated VNF through the NG4 interface, and the request includes terminating the running services of the dedicated VNF.

In step 1511, the NFVO executes the NSM&O in step 1510 to terminate the running service of the dedicated VNF, terminate the dedicated VNF, and delete the dedicated connection of the dedicated VNF.

Optionally, in step 1512, the NFVO feeds back the completion message of terminating the dedicated VNF to the NSM&O through the NG4 interface.

Step 1513, NSM&O notifies NM configuration through NG3 interface that the corresponding PNF and VNF in the target network slice instance have been terminated, and informs it of the specific modification result to EM. It is used to inform the NM that you can now configure the network, and tell it which PNFs to configure, which VNFs to terminate and shrink, and to update the NM's knowledge of the network.

It should be understood that, from step 1506 to step 1513, the NSM&O instructs the EM managing the dedicated VNF to configure the dedicated VNF to terminate the service for the target network slice instance.

Optionally, in step 1514, 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, repeat steps 1506-1514 for this slice instance, if there is no network slice instance generated based on the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used . If NSLD is being used, feedback network slice deletion error. If the NSLD is not in use, go to step 1515 .

Optionally, in step 1515, the NSM&O deletes the current version NSLD from the Repository.

It should be understood that steps 1514 and 1515 need to be executed only when the Sender sends a network slice deletion request.

In step 1516, the Sender is notified that the termination of the network slice instance/deletion of the network slice is completed.

In the embodiment of the present invention, the existing 3GPP network architecture and MANO network architecture system are retained, and an independent network management system is adopted for network slicing services, which supports direct orchestration management of physical network functions, and NFV MANO system management for virtual network functions Orchestration supports network slice instance termination and network slice deletion under this system architecture. In the embodiment of the present invention, the operator or the authorized third-party tenant of the network slicing instance can request to terminate the network slicing instance when the cost of maintaining the existing slicing instance is higher than the benefits brought by its service, and at the same time allows the operator to decide not to When the current type of network slicing is supported, such as network slicing version upgrade, request to delete the network slicing.

In addition, the present invention differentiates between the general network functions shared by the network slice instance and other slice instances and the slice-specific network functions in the embodiment, so that the service of other network slice instances will not be affected when the current network slice instance is terminated.

Fig. 16 shows a schematic block diagram of the network architecture of an embodiment of the present invention. The network architecture 4 (option 4) shown in FIG. 16 is an improvement to the existing 3GPP OSS system (the embodiment shown in FIG. 4 ), and NSM&O can realize the function of NM in the original 3GPP network architecture. Specifically, NSM&O interacts with EM through the Itf-N interface to implement physical network functions, including physical network functions (English: Physical Network Function, abbreviated: PNF) (managed by NE) and virtual network functions (English: Virtual Network Function, abbreviated: VNF) management; this NSM&O is independent of the existing NM system, does not make any upgrade changes to the NM system, and introduces a new slice arrangement management and system, in which the interface between NSM&O and the NM system is temporarily called the NG3 interface. The interface between NSM&O and VNFM is temporarily called NG1 interface, the interface between NSM&O and VIM is temporarily called NG2 interface, and the interface between NSM&O and EM is temporarily called NG5 interface.

Specifically, the functions of the NG1 interface mainly include: authorization, reservation, allocation, and release of NFVI resources in order to support VNF; query information query of running state; VNF initialization update, scaling, termination, etc., and transmit VNF-related events , 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, and upgrade records related to NFVI.

Specifically, the functions of NG3 mainly include: transmitting the negotiation information between NSM&O and NM, such as NSM&O querying the VNF generated by NM; NM feeding back the VNF information generated by NSM&O and confirming that modification is allowed; /VNF to be modified; NSM&O notifies NM of specific modification contents for PNF/VNF.

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 evolution and upgrade of the network architecture on the OSS system requires minor changes to the existing network architecture and interfaces. This architecture does not need to change the NM, but provides a brand new management system, which needs to adopt new interfaces and existing There are various entities that interact. Both NSM&O and NM can directly manage PNF, and NSM&O directly orchestrates and manages virtual resources and participates in the life cycle management of VNF.

Fig. 17 shows a schematic flowchart of a method for managing network slices according to an embodiment of the present invention. This FIG. 17 shows a flowchart of network slice management based on the network structure shown in FIG. 16 .

As shown in Figure 17, the method includes:

Step 1701, the Sender sends a target network slice instance termination request or a target network slice deletion request to NSM&O.

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

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 the identifier of the NSLD corresponding to the network slice, the identity identifier of the Sender, and the like. Sender may be an authorized third-party tenant, operator, or an application that has the right to terminate network slice instances/delete network slices.

Step 1702, 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 Sender, NSM&O needs to exchange information with the Repository, authenticate the identity of the Sender through the Repository, and verify the integrity of the parameters in the request (such as target Whether the format of the network slice instance identifier is correct, whether the format of the NSLD identifier corresponding to the target network slice is correct, etc.), whether the authentication Sender has the authority 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 running status of the target network slice instance, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.

When in step 1701, the request sent by the Sender is to terminate the target network slice instance, the following steps are performed:

If the authentication fails, execute step 1702', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to terminate the slice instance, and cannot verify the identity of the Sender;

If the verification and authentication pass and the target network slice instance exists, execute step 1703;

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

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

If the authentication fails, execute step 1702', NSM&O feeds back the corresponding error to the Sender, for example, informs the Sender that it has no right to delete the network slice, and cannot verify the identity of the Sender;

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

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

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

Step 1703 , before terminating the network slice instance, the NSM&O notifies the NM through the NG3 interface of the adjustment of the physical network functions that it will jointly manage with the NM to avoid conflicts. The notification shall at least contain the identification of the physical network function involved.

Step 1704, after receiving the notification, the NM feeds back a notification confirmation to the NSM&O through the NG3 interface. Before the NM receives the NSM&O modification completion message, it will no longer monitor and modify the configuration of these physical network functions and virtual network functions.

Step 1705, 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 general network functions, including shared VNF and shared PNF; and NSM&O detects whether the target NSI to be terminated has a dedicated Network features.

(1) When the target NSI includes a shared PNF, the NSM&O initiates a request to configure the network function to the EM managing the shared PNF through the NG5 interface, and instructs the EM managing the shared PNF to set the shared PNF to terminate the service to the target NSI , the request includes but is not limited to: instruct EM to stop sharing the service provided by the PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the policy of serving the target NSI, terminate/delete the PNF and the target NSI Network connections between dedicated network functions, etc.

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 are configured to terminate services to the target NSI.

It should be understood that (1) in step 1705 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service for the target network slice instance. At this time, the first PNF is a shared PNF.

(2) When the target NSI includes a shared VNF, the NSM&O initiates a request to configure the network function to the EM managing the shared VNF through the NG5 interface, and instructs the EM managing the shared VNF to set the shared VNF to terminate the service to the target NSI , the request includes but is not limited to: instruct the EM to stop sharing the services provided by the VNF to the target NSI, delete the configuration parameters used to support the target NSI service, such as the network slice instance identifier, and delete the policy serving the target NSI.

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

Further, the NSM&O notifies the VIM through the NG2 interface to terminate/close the possible network connection between the shared VNF and the dedicated network function of the target NSI, releasing corresponding network resources. VIM executes the request and feeds back the execution result through the NG2 interface.

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

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

It should be understood that (2) in step 1705 is a specific interaction process instructing the NSM&O to instruct the EM managing the shared VNF to configure the shared VNF to terminate the service for 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: instruct the EM to stop the service provided by the dedicated PNF to the target NSI, delete the configuration parameters used to support the target NSI service such as the network slice instance identifier, delete the policy serving the target NSI, terminate/delete the PNF and the target NSI exclusive Network connections between network functions, etc.

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

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

It should be understood that (3) in step 1705 is a specific interaction process in which the NSM&O instructs the network element manager EM managing the first PNF to configure the first PNF to terminate the service to the target network slice instance. At this time, the first PNF is a dedicated PNF.

In step 1706, the NSM&O notifies the NM through the NG3 interface that the configuration has terminated the corresponding PNF and VNF in the target network slice instance, and informs them of the modification result.

(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, and instructs the EM managing the shared VNF to set the dedicated VNF to terminate services to the target NSI, That is, step 1707 in the process shown in FIG. 17 , the request includes but is not limited to: instructing to stop monitoring the running status of the VNF, terminating the management function of the VNF, and deleting the management object.

If the shared VNF, dedicated VNF, shared PNF and dedicated PNF of the target NSI have all been terminated, the network slice instance has been terminated, and step 1718 is executed.

In step 1708, the EM that manages the dedicated VNF executes the NSM&O request in step 1707 for terminating the management of the VNF.

Step 1709, the EM managing the above-mentioned dedicated VNF feeds back the confirmation of the completion of the management to the NSM&O through the NG5 interface.

In step 1710, the NSM&O notifies the EM managing the dedicated VNF through the NG5 interface to close the virtual port of the dedicated VNF and stop serving the target NSI.

Step 1711, NSM&O initiates a request to terminate the dedicated VNF to the VNFM through the NG1 interface, the request includes terminating the running service to the target NSI and shutting down the above-mentioned dedicated VNF. .

In step 1712, the VNFM executes the NSM&O in step 1308 to terminate the running service of the dedicated VNF, and the VNFM and the internal mechanism of the VNF jointly shut down the VNF.

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

Step 1714, NSM&O sends the delete and release of these VNFs to the VIM through the NG2 interface according to the information of the resources (including computing, storage, and network resources) used to support the operation of the dedicated VNF and the dedicated network connection information that supports the operation of the network slice instance. Requests for resources and network connections used.

In step 1715, the VIM executes the request to delete and release the resources used by these VNFs and delete the network connection dedicated to the network slice instance requested by the NSM&O in step 1714.

Step 1716, the VIM feeds back the deletion and release completion confirmation to the NSM&O through the NG2 interface.

It should be understood that, from step 1705 to step 1716, the NSM&O instructs the EM managing the dedicated VNF to configure the dedicated VNF to terminate the service for the target network slice instance.

Step 1717, if there are other functions implemented by the dedicated VNF in the dedicated network function of the target NSI that have not been terminated, repeat steps 1705-1716 until the target NSI is terminated, and NSM&O deletes the information of the target NSI in the Repository slice instance memory. If in step 1701 the Sender sends a network slice instance termination request, go to step 1720 , otherwise go to step 1718 .

Optionally, in step 1718, 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 1705-1517 for this slice instance, if there is no network slice instance generated based on the NSLD, NSM&O checks whether the NSLD corresponding to the network slice is being used . If NSLD is being used, feedback network slice deletion error. If the NSLD is not in use, go to step 1719 .

Optionally, in step 1719, the NSM&O deletes the current version NSLD from the Repository.

It should be understood that steps 1718 and 1719 need to be executed only when the Sender sends a network slice deletion request.

Step 1720, notify the Sender that the termination of the network slice instance/deletion of the network slice is completed.

Therefore, the embodiment of the present invention controls physical network function management devices and virtual network function management devices, supports network slice management, supports direct orchestration management of physical network functions, and uses NFV MANO system management orchestration for virtual network functions to support this system architecture The next network slice instance is terminated and the network slice is deleted. In the embodiment of the present invention, the operator or the authorized third-party tenant of the network slicing instance can request to terminate the network slicing instance when the cost of maintaining the existing slicing instance is higher than the benefits brought by its service, and at the same time allows the operator to decide not to When the current type of network slicing is supported, such as network slicing version upgrade, request to delete the network slicing.

In addition, the present invention differentiates between the general network functions shared by the network slice instance and other slice instances and the slice-specific network functions in the embodiment, so that the service of other network slice instances will not be affected when the current network slice instance is terminated.

Further, in the embodiment of the present invention, when the NSM&O and the existing network management system jointly manage the physical network function, conflicts caused by joint management can be avoided.

It should be understood that there are overlapped steps in the four flowcharts described for the four network architectures in FIG. 10 to FIG. 17 , and the same processes and methods in the several embodiments are similar, and all of them are not described in detail for the sake of brevity.

It should be understood that only one EM is drawn in Figure 11, Figure 13, Figure 15, and Figure 17 above, but NSM&O may interact with multiple different EMs when it needs to terminate different network functions. Functional EM sends a request message. For example, there may be an EM for managing PNFs, an EM for managing VNFs, and an EM for managing both PNFs and VNFs in an actual system, which is not limited in the present invention.

It should also be understood that the numbers of the above steps do not represent the order of execution. During the specific implementation process, some or all of the steps may be selected to be executed according to the specific conditions of the target network slice instance, which is not limited by the present invention.

Figures 7 to 9 describe in detail the flow of the method for managing network slices in the present invention, and the four embodiments described in Figures 10 to 17 are respectively aimed at four architectures, involving the termination method of network slice instances and the network slice deletion method , the entity performing slice instance termination/slice deletion is NSM&O. During implementation, NSM&O may be multiple modules with a hierarchical structure, as shown in FIG. 18 , which shows a schematic block diagram of a network management and orchestrator according to an embodiment of the present invention. Among them, the multi-vendor association (English: Multi-Vendor) NSM&O is a general control orchestrator, which manages the management orchestrator domain NSM&O of each domain. In Figure 18, the NSM&O management device refers to the Multi-Vender NSM&O. The first NSM&O, the second NSM&O, and the nth NSM&O all refer to Domain NSM&O, where each Domain NSM&O is responsible for managing sub-network slices, and the Multi-Vender load manages the overall network slice. It should be understood that the All NSM&O can be used as Domain NSM&O. Specifically, for example, a complete slice instance can be composed of core network sub-slice instances and RAN sub-slice instances. 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-slice instances. Two domain NSM&O of the instance; or a complete slice instance can be divided into multiple sub-slice instances, each sub-slice instance is composed of a device provider's equipment, for example, a network slice instance of an operator is in charge of a multi-vendor NSM&O as a whole Management, the domain NSM&O provided by several equipment vendors manages the equipment provided by this equipment vendor. The description of the sub-slice instance is similar to the description of the whole slice instance, and the information contained may include network functions, connections between network functions, KPI requirements, SLA, and operating parameters to be monitored. 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 composition of the slice instance is divided into several sub-slice instances (the composition is determined when the network slice instance is created), at this time the multi-vendor NSM&O Each domain NSM&O is notified to complete the termination of the sub-slice instance. How to terminate the sub-network slice is determined by the domain NSM&O.

A Multi-vendor NSM&O initiates a request to terminate network slicing, and the process executed by each domain NSM&O is shown in FIG. 19 . FIG. 19 shows a schematic flowchart of managing network slicing according to an embodiment of the present invention. As shown in Figure 19, the Multi-vendor NSM&O is the NSM&O management device, and the NSM&O management device manages the first NSM&O and the second NSM&O.

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

Step 1902: Send a request to the first NSM&O, requesting to terminate subnetwork slice instance 1.

In step 1903, the first NSM&O executes the process of terminating the subnetwork slice instance 1. The specific terminating process may be similar to the embodiments described in FIG. 7 to FIG. 17 , and will not be repeated here.

Step 1904, the first NSM&O sends a termination completion message to the NSM&O management device.

Step 1905, send a request to the second NSM&O, requesting to terminate the subnetwork slice instance 2.

In step 1906, the second NSM&O executes the process of terminating the subnetwork slice instance 2. The specific terminating process may be similar to the embodiments described in FIG. 7 to FIG. 17 , and will not be repeated here.

Step 1907, the first NSM&O sends a termination completion message to the NSM&O management device.

That is, after all Domain NSM&Os complete the management of sub-network slice instances, Multi-vendorNSM&O can confirm that the management of the entire network slice instance is completed.

Therefore, the network slice management and orchestration of the domain structure is beneficial to: 1) Each device of multiple equipment vendors is independently managed by each Domain NSM&O, so that the complex configuration problems caused by the unstandardized device configuration scripts of each equipment vendor can be eliminated. Solved by this structure. The network equipment of a certain equipment vendor is managed by the Domain NSM&O provided by the equipment vendor, which can facilitate the design of the management system, and eliminate the differences with equipment vendors managed by another Domain NSM&O through Multi-vendor NSM&O, which is beneficial to the unified management of operators with orchestrating network slicing. 2) Domain-specific management of network slice instances. The domain independent management and orchestration architecture supports the independent creation, adjustment, update, configuration, and deletion of a certain domain without affecting other domains, making the management and orchestration of network slice instances more flexible, which is beneficial to operators' positioning Network problem, design network deployment plan.

Fig. 20 is a schematic structural block diagram of a network device according to an embodiment of the present invention.

The method for managing network slicing and the network management architecture of the embodiment of the present invention are described in detail above in conjunction with FIGS. 1 to 19 . The network device in the embodiment of the present invention will be described in detail below in conjunction with FIGS.

Fig. 20 is a schematic block diagram of a network device 2000 according to an embodiment of the present invention. It should be understood that the network device 2000 can execute various steps performed by the NSM&O in the methods in FIGS. 1 to 19 , and details are not described here again to avoid repetition. Network equipment 2000 includes:

The receiving unit 2010 is configured to receive, through the transceiver, a management request message of the target network slice, where the management request message is used to request deletion of the target network slice or termination of the target network slice instance.

The control unit 2020 is configured to control 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.

It should be understood that the actions performed by the determining unit 2010 may be implemented by a processor, and the actions performed by the sending unit 2020 may be implemented by a transceiver under the control of the processor.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Fig. 21 is a schematic structural block diagram of a network device according to an embodiment of the present invention. Fig. 21 is a schematic block diagram of a network device 2100 according to an embodiment of the present invention. It should be understood that the network device 2100 can execute each step performed by the Sender in the methods in FIGS. 1 to 19 , and details are not described here again to avoid repetition. Network equipment 2200 includes:

A determining unit 2110, configured to send 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 unit 2120 is configured to receive a management completion message sent by the NSM&O, where the management completion 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 2110 may be implemented by a processor, and the actions performed by the sending unit 2120 may be implemented by a transceiver under the control of the processor.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Fig. 22 is a schematic structural block diagram of a network device according to an embodiment of the present invention. Fig. 22 is a schematic block diagram of a network device 2200 according to an embodiment of the present invention. It should be understood that the network device 2200 can execute the steps performed by the Repository in the methods in FIGS. 1 to 19 , and details are not described here again to avoid repetition. Network equipment 2200 includes:

The receiving unit 2210 is configured to receive a verification message from the network slice management and orchestrator NSM&O, wherein the verification message is used to verify whether the sender Sender who initiates the network slice management request has the authority to perform network slice management on the target network slice.

The processing unit 2220 is configured to verify according to the verification message whether the Sender 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 2210 may be implemented by a processor, and the actions performed by the sending unit 2220 may be implemented by a transceiver under the control of the processor.

Therefore, the method for managing network slices provided by the embodiments of the present invention can realize deletion of network slices and termination of network slice instances through unified management of physical resources and virtual resources.

Further, in the embodiment of the present invention, when the Sender determines that the current target network slice instance is no longer supported, the current target network slice can be terminated; or, when the Sender determines that the current target network slice is no longer supported, the target network slice can be deleted, so that the current target network slice can be updated. Flexible network slice management reduces operating costs.

Fig. 23 is a schematic structural block diagram of a device according to an embodiment of the present invention. FIG. 23 shows an apparatus 2300 for managing network slices provided by an embodiment of the present invention. It should be understood that the device 2300 can execute the various steps performed by the NSM&O in the methods shown in FIGS. 1 to 19 , and details will not be described here to avoid repetition. Apparatus 2300 includes:

Memory 2310, for storing programs;

Transceiver 2320, used to communicate with other devices;

The processor 2330 is configured to execute the program in the memory 2310, the processor 2330 is connected to the memory 2310 and the transceiver 2320 respectively, and is used to execute the instructions stored in the memory 2310, so that when executing the instructions Perform the following steps:

The processor 2330 is configured to receive a management request message of the target network slice through the transceiver 2320, where the management request message is used to request deletion of the target network slice or termination of the target network slice instance; according to the management request message, 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.

It should be understood that the apparatus 2300 may specifically be the NSM&O in the foregoing embodiments, and may be configured to execute various steps and/or processes corresponding to NSM&O in the foregoing method embodiments.

Fig. 24 is a schematic structural block diagram of a device according to another embodiment of the present invention. FIG. 24 shows an apparatus 2400 for managing network slices provided by an embodiment of the present invention. It should be understood that the device 2400 is capable of executing various steps performed by the NSM&O in the methods shown in FIGS. 1 to 19 , and details are not described here to avoid repetition. Apparatus 2400 includes:

Memory 2410, for storing programs;

Transceiver 2420, used to communicate with other devices;

The processor 2430 is configured to execute the program in the memory 2410, the processor 2430 is respectively connected to the memory 2410 and the transceiver 2420, and is used to execute the instructions stored in the memory 2410, so that when executing the instructions Perform the following steps:

The processor 2430 is configured to send a management request message of the target network slice to the network slice management and orchestrator NSM&O through the transceiver 2420, and the management request message is used to request the NSM&O to delete the target network slice or terminate all The target network slice instance; receiving a management completion message sent by the NSM&O, where the management completion 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.

It should be understood that the apparatus 2400 may specifically be the Sender in the foregoing embodiments, and may be configured to execute various steps and/or processes corresponding to the Sender in the foregoing method embodiments.

Fig. 25 is a schematic structural block diagram of a device according to another embodiment of the present invention. FIG. 25 shows an apparatus 2500 for managing network slices provided by an embodiment of the present invention. It should be understood that the device 2500 can execute the various steps performed by the NSM&O in the methods shown in FIGS. 1 to 19 , and details are not described here to avoid repetition. Apparatus 2500 includes:

Memory 2510, for storing programs;

Transceiver 2520, used to communicate with other devices;

The processor 2530 is configured to execute the program in the memory 2510, and the processor 2530 is respectively connected to the memory 2510 and the transceiver 2520, and is used to execute the instructions stored in the memory 2510, so that when executing the instructions Perform the following steps:

The processor 2530 is configured to receive a verification message from the network slice management and orchestrator NSM&O through the transceiver 2520, wherein the verification message is used to verify whether the sending end Sender that initiates the network slice management request has the ability to perform network slice on the target network slice management authority;

Verifying whether the Sender has the authority to perform network slice management on the target network slice according to the verification message.

It should be understood that the apparatus 2500 may specifically be the Sender in the foregoing embodiments, and may be configured to execute various steps and/or processes corresponding to the Sender in the foregoing method embodiments.

It should be understood that, in the embodiment of the present invention, the processor of the above-mentioned device may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits ( ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the methods disclosed in conjunction with the embodiments of the present invention may be directly implemented by a hardware processor, or implemented by a combination of hardware and software units in the processor. The software unit may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor executes the instructions in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.

Those of ordinary skill in the art can realize that, in combination with the various method steps and units described in the embodiments disclosed herein, they can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the possibility of hardware and software For interchangeability, in the above description, the steps and components of each embodiment have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art may use different methods to implement the described functions for each particular application, but such implementation should not be regarded as exceeding the scope of the present invention.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, and will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of software products, and the computer software products are stored in a storage medium In, several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as "ROM"), random access memory (Random Access Memory, referred to as "RAM"), magnetic disk or optical disc, etc. Various media that can store program code.

The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person familiar with the technical field can easily think of various equivalents within the technical scope disclosed in the present invention. Modifications or replacements shall all fall within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (30)

1. A kind of 1. method for managing network section, it is characterised in that including：

   Network section management receives the management request message of objective network section, the management request message with composer NSM＆O For the request deletion objective network section or the objective network section example that terminates；

   The NSM＆O controls physical network function management equipment and/or virtual network function pipe according to the management request message Manage equipment and network section management is carried out to objective network section.
2. It is 2. according to the method described in claim 1, it is characterized in that, described according to the management request message, control Physical Network Network function management equipment and/or virtual network function management equipment, which cut into slices the objective network, carries out network section management, bag Include：

   When the management request message is used to ask to terminate the objective network section example, the virtual network function is controlled Management equipment, terminate the corresponding virtual network function VNF of the objective network section example；And/or

   Control the corresponding physical network function of the physical network function management equipment termination objective network section example PNF。
3. It is 3. described according to the method described in claim 2, it is characterized in that, the physical network function management equipment includes EM Control the corresponding physical network function PNF of the physical network function management equipment termination objective network section example, bag Include：

   When the corresponding PNF of objective network section example includes a PNF, instruction manages the net of the first PNF First PNF is configured to service of the termination to objective network section example by first manager EM.
4. 4. according to the method in claim 2 or 3, it is characterised in that the physical network function management equipment includes EM, institute The corresponding virtual network function VNF of the control virtual network function management equipment termination objective network section example is stated, Including：

   When the corresponding VNF of objective network section embodiment includes shared VNF, instruction manages the shared VNF's The shared VNF is configured to service of the termination to objective network section example by EM.
5. 5. the according to the method described in claim 4, it is characterized in that, control virtual network function management equipment termination The corresponding virtual network function VNF of objective network section example, including：

   The shared VNF is configured to termination and objective network section example phase by instruction virtualized infrastructure management equipment VIM The network connection of pass, and/or contraction and the objective network section relevant Internet resources of example, wherein, the virtual network Function management equipment includes the VIM；Or

   The shared VNF is configured to instruction virtual network function composer NFVO termination and objective network section example is relevant Network connection, and/or contraction and the objective network section relevant Internet resources of example, wherein, the virtual network function Management equipment includes the NFVO.
6. 6. the method according to any one of claim 2 to 5, it is characterised in that the control virtual network function The corresponding virtual network function VNF of the management equipment termination objective network section example, including：

   When the corresponding VNF of objective network section example includes exclusive VNF, instruction manages the EM of the exclusive VNF The management to terminate to the exclusive VNF.
7. 7. according to the method described in claim 6, it is characterised in that the virtual network function management equipment is including VIM and virtually Network function management equipment VNFM, the control virtual network function management equipment termination objective network section example Corresponding virtual network function VNF, including：

   Indicate the VNFM terminations exclusive VNF；

   Indicate that the VIM is closed and the exclusive relevant network connections of VNF, and/or release and the relevant nets of the 2nd VNF Network resource.
8. 8. according to the method described in claim 6, it is characterized in that, the virtual network function management equipment includes NFVO, institute The corresponding virtual network function VNF of the control virtual network function management equipment termination objective network section example is stated, Terminate the objective network section embodiment, including：

   It is relevant with the shared VNF with the exclusive relevant network connections of VNF, and/or release to indicate that the NFVO is closed Internet resources.
9. It is 9. according to the method described in claim 1, it is characterized in that, described according to the management request message, control Physical Network Network function management equipment and/or virtual network function management equipment, which cut into slices the objective network, carries out network section management, bag Include：

   When the management request message is used to delete objective network section, control physical network function management equipment and/ Or virtual network function management equipment deletes the objective network section.
10. 10. according to the method described in claim 9, it is characterized in that, the control physical network function management equipment and/or void Intend network function management equipment and delete the objective network section, including：

    The physical network function management equipment and/or the virtual network function management equipment are controlled, terminate the target network Each example corresponding VNF and/or PNF in network section.
11. 11. the method according to claim 9 or 10, it is characterised in that it is described according to the management request message, control thing Manage network function management equipment and/or virtual network function management equipment and network section pipe is carried out to objective network section Reason, including：

    After determining that whole examples in the objective network section all terminate, instruction memory Repository deletes the mesh Mark the section template of network section.
12. 12. the method according to claim 1 to 11, it is characterised in that described to be asked described according to the management, control Physical network function management equipment and/or virtual network function management equipment, which cut into slices the objective network, carries out network section pipe Before reason, the method further includes：

    Whether the transmitting terminal Sender that the management request message is initiated in verification there is the network cut into slices to the objective network to cut The authority of piece management.
13. A kind of 13. method for managing network section, it is characterised in that including：

    The management request that transmitting terminal Sender sends the objective network section to network section management and composer NSM＆O disappears Breath, the management request message are used to ask the NSM＆O deletions objective network section or the objective network that terminates to be cut Piece example；

    The Sender receives the management completion message that the NSM＆O is sent, and the management completion message is used to determine described NSM＆O completes the deletion to target network section or the termination to objective network section example.
14. A kind of 14. method for managing network section, it is characterised in that including：

    Memory Repository receives network section management and the verification message of composer NSM＆O, wherein, the verification message Whether the transmitting terminal Sender for verifying initiation network section management request has carries out network section to objective network section The authority of management；

    The Repository according to it is described verification information authentication described in Sender whether have cut into slices to the objective network into The authority of row network section management.
15. 15. according to the method for claim 14, it is characterised in that it is described to return to verification completion message to the NSM＆O, with Easy to the NSM＆O according to the verification feedback message, it is determined whether objective network section is managed, including：

    Verification completion message is returned to the NSM＆O, the verification completion message is used to notify that Sender described in the NSM＆O is It is no to carry out the authority of network section management to cutting into slices with the objective network；

    When the Sender does not possess network section administration authority or the objective network section to objective network section Example when being not present, the verification feedback message is used to inform that Sender described in the NSM＆O does not have to the target network Network section carries out the authority of network section management；Or

    When the Sender possesses, and administration authority is cut into slices to the network of objective network section, the verification feedback message is used The authority of network section management is carried out in informing that Sender described in the NSM＆O has to cut into slices to the objective network.
16. A kind of 16. network equipment, it is characterised in that including：

    Transceiver,

    Memory, for storing instruction；

    Processor is respectively connected with the memory and the transceiver, for performing the described instruction of the memory storage, To perform following steps when performing described instruction：

    The management request message of objective network section is received by the transceiver, the management request message is used to ask to delete The objective network section or the objective network section example that terminates；

    According to the management request message, physical network function management equipment and/or virtual network function management equipment pair are controlled The objective network section carries out network section management.
17. 17. the network equipment according to claim 16, it is characterised in that the processor is specifically used for：

    When the management request message is used to ask to terminate the objective network section example, the virtual network function is controlled Management equipment, terminate the corresponding virtual network function VNF of the objective network section example；And/or

    Control the corresponding physical network function of the physical network function management equipment termination objective network section example PNF。
18. 18. the network equipment according to claim 17, it is characterised in that the processor is specifically used for：

    When the corresponding PNF of objective network section example includes a PNF, instruction manages the net of the first PNF First PNF is configured to service of the termination to objective network section example by first manager EM.
19. 19. the network equipment according to claim 17 or 18, it is characterised in that the physical network function management equipment bag EM is included, the processor is specifically used for：

    When the corresponding VNF of objective network section embodiment includes shared VNF, instruction manages the shared VNF's The shared VNF is configured to service of the termination to objective network section example by EM.
20. 20. the network equipment according to claim 19, it is characterised in that the processor is specifically used for：

    The shared VNF is configured to termination and objective network section example phase by instruction virtualized infrastructure management equipment VIM The network connection of pass, and/or contraction and the objective network section relevant Internet resources of example, wherein, the virtual network Function management equipment includes the VIM；Or

    The shared VNF is configured to instruction virtual network function composer NFVO termination and objective network section example is relevant Network connection, and/or contraction and the objective network section relevant Internet resources of example, wherein, the virtual network function Management equipment includes the NFVO.
21. 21. the network equipment according to any one of claim 17 to 20, it is characterised in that the processing implement body is used In：

    When the corresponding VNF of objective network section example includes exclusive VNF, instruction manages the EM of the exclusive VNF The management to terminate to the exclusive VNF.
22. 22. according to the network equipment described in claim 21, it is characterised in that the virtual network function management equipment includes VIM With virtual network function management equipment VNFM, the processor is specifically used for：

    Indicate the VNFM terminations exclusive VNF；

    Indicate that the VIM is closed and the exclusive relevant network connections of VNF, and/or release and the relevant nets of the 2nd VNF Network resource.
23. 23. the network equipment according to claim 21, it is characterised in that the virtual network function management equipment includes NFVO, the processor are specifically used for：

    It is relevant with the shared VNF with the exclusive relevant network connections of VNF, and/or release to indicate that the NFVO is closed Internet resources.
24. 24. the network equipment according to claim 16, it is characterised in that the processor is specifically used for：

    When the management request message is used to delete the objective network section, delete each in the objective network section Example corresponding virtual network function VNF and/or physical network function PNF.
25. 25. the network equipment according to claim 24, it is characterised in that the processor is specifically used for：

    The each example corresponding VNF and/or PNF to terminate in objective network section.
26. 26. the network equipment according to claim 24 or 25, it is characterised in that the processor is specifically used for：

    After determining that whole examples in the objective network section all terminate, instruction memory Repository deletes the mesh Mark the section template of network section.
27. 27. the network equipment according to any one of claim 24 to 26, it is characterised in that the processing implement body is used In：

    Whether the transmitting terminal Sender that the management request message is initiated in verification there is the network cut into slices to the objective network to cut The authority of piece management.
28. A kind of 28. network equipment, it is characterised in that including：

    Transceiver,

    Memory, for storing instruction；

    Processor is respectively connected with the memory and the transceiver, for performing the described instruction of the memory storage, To perform following steps when performing described instruction：

    The management request message of the objective network section is sent with composer NSM＆O to network section management, the management please Message is asked to be used to asking the NSM＆O to delete the objective network section or the objective network section example that terminates；

    The management completion message that the NSM＆O is sent is received, the management completion message is used to determine that the NSM＆O is completed to institute State the deletion of target network section or the termination to objective network section example.
29. A kind of 29. network equipment, it is characterised in that including：

    Transceiver,

    Memory, for storing instruction；

    Processor is respectively connected with the memory and the transceiver, for performing the described instruction of the memory storage, To perform following steps when performing described instruction：

    Network section management and the verification message of composer NSM＆O are received, wherein, the verification message, which is used to verify, initiates network Whether the transmitting terminal Sender of section management request, which has to cut into slices to objective network, carries out the authority of network section management；

    Whether had to cut into slices to the objective network according to Sender described in the verification information authentication and carry out network section management Authority.
30. 30. the network equipment according to claim 29, it is characterised in that the processor is specifically used for：

    Verification completion message is returned to the NSM＆O, the verification completion message is used to notify that Sender described in the NSM＆O is It is no to carry out the authority of network section management to cutting into slices with the objective network；

    When the Sender does not possess network section administration authority or the objective network section to objective network section Example when being not present, the verification feedback message is used to inform that Sender described in the NSM＆O does not have to the target network Network section carries out the authority of network section management；Or

    When the Sender possesses, and administration authority is cut into slices to the network of objective network section, the verification feedback message is used The authority of network section management is carried out in informing that Sender described in the NSM＆O has to cut into slices to the objective network.