WO2018082502A1 - 管理网络切片实例的方法、装置和系统 - Google Patents
管理网络切片实例的方法、装置和系统 Download PDFInfo
- Publication number
- WO2018082502A1 WO2018082502A1 PCT/CN2017/107963 CN2017107963W WO2018082502A1 WO 2018082502 A1 WO2018082502 A1 WO 2018082502A1 CN 2017107963 W CN2017107963 W CN 2017107963W WO 2018082502 A1 WO2018082502 A1 WO 2018082502A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- slice instance
- function
- network device
- network function
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/827—Aggregation of resource allocation or reservation requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/22—Traffic shaping
- H04L47/225—Determination of shaping rate, e.g. using a moving window
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/29—Flow control; Congestion control using a combination of thresholds
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Definitions
- the present application relates to the field of communications, and in particular, to a method, apparatus, and system for managing network slice instances.
- Network slicing technology refers to the logical abstraction of a network into one or more network slices, where each network slice contains a series of logical network functions, and a network slice can satisfy the connection communication service requirements of a certain class or a use case.
- the next generation mobile communication system can be composed of a large number of network slices that satisfy different connection capabilities.
- network function virtualization is a key enabling technology that reduces the complexity and cost of network slicing
- physical network elements and virtualized network elements will coexist for a long time and flexibly form a network slice for the purpose of reducing deployment costs and recovering investment. . Therefore, in order to provide differentiated communication requirements quickly and flexibly, operators need an automated slicing operation and maintenance system that can simultaneously manage and orchestrate physical network functions and virtualized network functions.
- prior art network management architectures eg, the 3rd Generation Partnership Project (3GPP) telecommunications network management architecture
- 3GPP 3rd Generation Partnership Project
- the embodiment of the present application provides a method, an apparatus, and a system for managing a network slice instance, so as to implement management of a network slice instance.
- a method for managing a network slice instance comprising the steps of: a first network device receiving a network slice instance creation request from a sender device, the network slice instance creation request for requesting to create a target network slice instance,
- the network slice instance creation request includes description information of the target network slice instance;
- the first network device sends network function configuration indication information to the second network device according to the description information, where the network function configuration indication information is used by
- the first network device receives the network function configuration response information sent by the second network device, where the network function configuration response information indicates The network function configuration of the target network slice instance is completed;
- the first network device sends network slice instance creation response information to the sender device, and the network slice instance creation response information indicates that the target network slice instance creation is completed.
- the first network device performs the network function of the network segment instance by instructing the second network device Configuration to manage the creation process of network slicing instances, which can automatically create network slicing instances and improve the efficiency of managing network slicing instances.
- the sender may be an operator, a third-party client, an application involved in the service, or any entity in the service provider domain that may send a request to the NSM&O, which is not limited in this embodiment of the present application.
- the network function of the target network slice instance includes at least one of the following network functions: a physical network function and a virtual network function.
- the network function included in the network slice instance may be either a physical network function or a virtual network function, or both a physical network function and a virtual network function. This makes it possible to flexibly schedule and manage the network functions of network slice instances as needed.
- the identifier of the target network slice instance is included in the network function configuration indication information.
- the method further includes: the first network device sending a network resource extension indication to the fourth network device, where The network resource extension indication is used to instruct the fourth network device to allocate network resources for a shared network function of the target network slice instance.
- the method further includes: the first network device sending resource reservation indication information to the fourth network device, where the resource reservation indication information is used to indicate that the fourth network device is the target The network slice instance reserves network resources.
- the method further includes: the first network device sending a virtual network function creation request to the third network device, where a virtual network function creation request for instructing the third network device to create a virtual network function of the target network slice instance; the first network device receiving virtual network function creation response information sent by the third network device, The virtual network function creation response information indicates that the virtual network function creation of the target network slice instance is completed.
- the method further includes: the first network device sends a resource allocation request to the fourth network device, where the allocated resource request is used to request the fourth network device to allocate the target network slice instance a network resource corresponding to the virtual network function; the first network device receives the allocated resource response information sent by the fourth network device, where the allocated resource response information is used to indicate a network corresponding to the virtual network function of the target network slice instance The resource allocation is completed.
- the method further includes: the first network device sending a resource allocation to the third network device And a confirmation information, where the resource allocation confirmation information is used to indicate that the network resource allocation corresponding to the virtual network function of the target network slice instance is completed.
- the method before the first network device sends the resource allocation request to the fourth network device, the method further includes: the first network device receiving, by the third network device, the allowed resource allocation indication information And the allowed resource allocation indication information is used to indicate that the third network device allows the network resource corresponding to the virtual network function to be allocated to the target network slice instance.
- the method further includes: the first network device sending network function notification information to the fifth network device, where the network function notification information is used to indicate a network function to be configured by the first network device.
- the method further includes: receiving, by the first network device, the fifth network device
- the network function response information is used to indicate that the fifth network device has determined a network function to be configured by the first network device.
- the method further includes: the first network device sends network function query information to the fifth network device, where the network function query information is used to request to query the network function that the fifth network device has generated.
- the first network device receives the network function feedback information sent by the fifth network device, where the network function feedback information is used to indicate the network function that the fifth network device has generated.
- the description information includes at least one of the following information: description information of a service requirement of the target network slice instance and configuration parameter information of a network slice template of the target network slice instance.
- the method further includes: the first network device sending legality verification information to the storage device, where the legality verification information is used to request to query whether the network slice instance creation request is legal; Receiving, by the network device, the legality verification response information sent by the storage device, where the legality verification response information is used to indicate whether the network slice instance creation request is legal; the first network device according to the description information And the second network device sends the network function configuration indication information to the second network device according to the description information, where the legality verification response information indicates that the network slice instance creation request is legal. Send network function configuration instructions.
- the method further includes: the first network device sending a network slice instance activation indication to the storage device The network slice instance activation indication sets the target network slice instance to an active state.
- the method further includes: the first network device sending a network function port activation indication to the second network device, where the network function port activation indicates a network used to activate the target network slice instance Functional port.
- the method further includes: the first network device sending an update network slice instance indication to the storage device, where the update network slice instance indication is used to indicate that parameter information of the target network slice instance is stored The storage device.
- a method for managing an instance of a network slice including: receiving, by a second network device, network slice configuration information sent by a first network device, where the network slice configuration information is used to indicate the second network device configuration a network function of the target network slice; the second network device sends the network slice configuration response information to the first network device, where the network slice configuration response information indicates that the network function configuration corresponding to the target network slice is completed.
- the second network device performs the network function configuration of the network sharding instance by receiving the indication of the first network device, thereby managing the process of creating the network snippet instance, and implementing the automatic creation of the network sharding instance and improving Manage the efficiency of network tile instances.
- the network function of the target network slice includes at least one of the following network functions: a physical network function and a virtual network function.
- the method further includes: the second network device receiving, by the first network device, a network function port activation indication, where the network function port activation indication is used to indicate that the target network slice instance is activated.
- the port of the network function is used to indicate that the target network slice instance is activated.
- the method further includes: the second network device receiving an add virtual network function request sent by the third network device, where the adding the virtual network function request is used to request to add the target network slice instance Proposed network function.
- a third aspect provides a method for managing a network sharding instance, including: receiving, by a third network device, a virtual network function creation request sent by a first network device, where the virtual network function creation request is used to indicate the third network device Creating a virtual network function of the target network slice instance; the third network device sends virtual network function creation response information to the first network device, the virtual network function creation response information indicating that the virtual network function of the target network slice instance is created .
- the third network device by receiving the indication of the first network device, manages the process of creating the network slice instance, and can automatically create the network slice instance, and improve the efficiency of managing the network slice instance.
- the method further includes: the third network device sends, to the first network device, permission to allocate resource indication information, where the permission to allocate resource indication information is used to indicate that the third network device allows
- the target network slice implements a network resource corresponding to the virtual network function.
- the method further includes: receiving, by the third network device, resource allocation confirmation information sent by the first network device, where the resource allocation confirmation information is used to indicate a virtual network of the target network slice instance The functional network resource allocation is completed.
- the method further includes: the third network device sending the adding virtual network function to the second network device The request, the add virtual network function request is used to request to add a virtual network function of the target network slice instance.
- a fourth aspect provides a method for managing a network splicing instance, including: receiving, by a fourth network device, an allocation resource request sent by a first network device, where the allocating resource request is used to request the fourth network device to be a target network
- the slice instance allocates network resources corresponding to the virtual network function; the fourth network device sends the allocated resource response information to the first network device, where the allocated resource response information is used to indicate that the virtual network function of the target network slice instance corresponds to The network resource allocation is completed.
- the fourth network device by receiving the indication of the first network device, manages the process of creating the network slice instance, and can automatically create the network slice instance, and improve the efficiency of managing the network slice instance.
- the method further includes: receiving, by the fourth network device, a network resource extension indication sent by the first network device, where the network resource extension indication is used to indicate that the fourth network device is The shared network function of the target network slice instance allocates network resources.
- the method further includes: receiving, by the fourth network device, resource reservation indication information that is sent by the first network device, where the resource reservation indication information is used to indicate that the fourth network device is The target network slice instance reserves network resources.
- a method for managing a network sharding instance including: receiving, by a fifth network device, network function notification information sent by a first network device, where the network function notification information is used to indicate that the first network device is to be a configured network function; the fifth network device sends network function response information to the first network device, where the network function response information is used to confirm that the fifth network device has determined that the first network device is to be configured Internet function.
- the fifth network device by receiving the indication of the first network device, manages the process of creating the network slice instance, and can automatically create the network slice instance, and improve the efficiency of managing the network slice instance.
- the method further includes: the fifth network device receives the network function query information sent by the first network device, where the network function query information is used to request that the fifth network device has been generated network of The fifth network device sends the network function feedback information to the first network device, where the network function feedback information is used to indicate the network function that the fifth network device has generated.
- an apparatus for managing a network slice instance for performing the method of any of the first aspect or the first aspect of the first aspect.
- the apparatus comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
- a seventh aspect there is provided another apparatus for managing an instance of a network slice for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
- the apparatus comprises means for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
- the apparatus comprises means for performing the method of any of the possible implementations of the third aspect or the third aspect described above.
- the apparatus comprises means for performing the method of any of the above-described fourth or fourth aspects of the fourth aspect.
- the apparatus comprises means for performing the method of any of the possible implementations of the fifth or fifth aspect above.
- an apparatus for managing an instance of a network slice comprising: a communication interface, a memory, a processor, and a bus system.
- the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
- an apparatus for managing an instance of a network slice comprising: a communication interface, a memory, a processor, and a bus system.
- the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
- an apparatus for managing an instance of a network slice comprising: a communication interface, a memory, a processor, and a bus system.
- the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the third aspect or the third aspect.
- an apparatus for managing an instance of a network slice comprising: a communication interface, a memory, a processor, and a bus system.
- the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the fourth aspect or the fourth aspect.
- an apparatus for managing an instance of a network slice comprising: a communication interface, a memory, a processor, and a bus system.
- the communication interface, the memory and the processor are connected by the bus system, and the storage a memory for storing instructions for executing the memory stored instructions to control the communication interface to receive signals and/or transmit signals, and when the processor executes the memory stored instructions, the executing causes the processor to execute A method in any of the possible implementations of the fifth aspect or the fifth aspect.
- a sixteenth aspect a system for managing an instance of a network slice, the system comprising any one of the apparatus, the seventh aspect, or the seventh aspect of any of the possible implementations of the sixth aspect or the sixth aspect A device in a possible implementation, and a device in any of the possible implementations of the eighth or eighth aspect, the device in any one of the foregoing possible implementations of the ninth or ninth aspect, the tenth aspect or a device in any of the possible implementations of the tenth aspect; or
- the system includes the apparatus of any one of the eleventh or eleventh aspects, and the apparatus of any one of the twelfth or twelfth aspects of the possible implementation, the thirteenth aspect Or the device of any one of the possible implementations of the thirteenth aspect, the device of any of the possible implementations of the fourteenth aspect or the fourteenth aspect, the fifteenth aspect or the fifteenth aspect The device in the implementation.
- a seventeenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
- a computer readable medium for storing a computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
- a nineteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the third aspect or any of the possible implementations of the third aspect.
- a computer readable medium for storing a computer program comprising instructions for performing the method of any of the fourth aspect or any of the possible implementations of the fourth aspect.
- a twenty-first aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the fourth aspect or any of the possible implementations of the fourth aspect.
- FIG. 1 is a schematic diagram of a network management architecture according to an embodiment of the present application.
- FIG. 2 is a structural diagram of an NSM&O according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a network management architecture applied in an embodiment of the present application.
- FIG. 4 is a schematic diagram of another network management architecture applied in the embodiment of the present application.
- FIG. 5 is a schematic diagram of another network management architecture applied in the embodiment of the present application.
- FIG. 6 is a schematic diagram of another network management architecture applied in the embodiment of the present application.
- FIG. 7 is a schematic flowchart of a method for managing a network slice instance according to an embodiment of the present application.
- FIG. 8 is a schematic flowchart of another method for managing a network slice instance according to an embodiment of the present application.
- FIG. 9 is a schematic flowchart of another method for managing a network slice instance according to an embodiment of the present application.
- FIG. 10 is a schematic flowchart of another method for managing a network slice instance according to an embodiment of the present application.
- FIG. 11 is a schematic flowchart of another method for managing a network slice instance according to an embodiment of the present application.
- FIG. 12 is a hierarchical structure diagram of NSM&O provided by an embodiment of the present application.
- FIG. 13 is a schematic flowchart of applying to NSM&O according to an embodiment of the present application.
- FIG. 14 is a schematic block diagram of an apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 15 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 16 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 17 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 18 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 19 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 20 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 21 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 22 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- FIG. 23 is a schematic block diagram of another apparatus for managing a network slice instance according to an embodiment of the present application.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- FDD Frequency Division Duplex
- TDD Time Division Duplex
- UMTS Universal Mobile Telecommunication System
- WiMAX Worldwide Interoperability for Microwave Access
- Embodiments of the present application relate to network slicing technology.
- the network slicing technology logically abstracts the network into one or more network slices, where each network slice contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
- network slicing is an on-demand networking, which enables operators to adjust to changing user demands and quickly meet new application requirements. New service.
- the network slicing technology abstracts the 5G network physical infrastructure resources into multiple network slices according to the scene requirements. Each network slice performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model.
- a network slice can be thought of as an instantiated 5G network.
- Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.
- Network slicing is a concept that refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
- Network Slice Instance A real-world logical network.
- Network Slice Template A method of generating a network slice instance to provide a reference for generating a network slice instance.
- the network slice template specifies how the network slice instance should be generated.
- the network slicing module can indicate which network functions are included in the network slice, and Key Performance Indicators (KPI) indicators that should be achieved.
- KPI Key Performance Indicators
- Network function It is a processing function in the network that defines functional behaviors and interfaces.
- Network functions can be As a dedicated hardware, software implementations can also be run on a dedicated hardware or as virtual functions on a common hardware platform. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple network slice instances, different network functions can be used independently. This network function is called a dedicated network function. It is also possible to share the same network function, which is called a shared network function.
- FIG. 1 illustrates a network management architecture 100.
- the network management architecture 100 of FIG. 1 may be a 3GPP public land mobile network (PLMN) that incorporates a Network Function Virtualized (NFV) Management and Orchestration (MANO) module. ) Network management architecture.
- PLMN 3GPP public land mobile network
- NFV Network Function Virtualized
- MANO Management and Orchestration
- the network management architecture 100 includes modules for managing physical network functions and virtual network functions. The modules in the network management architecture 100 are described in turn below.
- PNF Physical network function
- the physical network function module may be a network element (NE) in a traditional 3GPP network management architecture, that is, a physical network element.
- the NE may be a base station, a Mobility Management Entity (MME), or a Serving Gateway (SGW).
- MME Mobility Management Entity
- SGW Serving Gateway
- VNF Virtualized network function
- the VNF module can create virtual network functions and perform some parameter configuration on the basis of NFVI to implement a certain network function.
- Element manager A network module for managing network elements.
- EM can be used to manage physical network functions (ie PNF modules) or to manage virtual network functions (ie VNF modules).
- the network management architecture may include one EM module or multiple EM modules.
- each of the plurality of EM modules is used to manage a corresponding virtual network function or a physical network function, or a single EM module can simultaneously manage corresponding virtual network functions and physics. Internet function.
- DM Domain manager
- the DM can manage one or more EMs.
- the DM can be a vendor's management system.
- EM and DM are different in definition. EM directly manages the same type of network equipment. For example, EM manages a series of base stations. DM manages a network device belonging to a vendor and provides domain management. Functional, DM is more manageable than EM. Typically, EM devices are used to perform configuration of network functions. However, the possibility that the DM performs the process performed by the EM is not excluded in the embodiment of the present application.
- Network manager is a management module at the network level. It mainly provides related functions such as network management functions and management equipment exchange. For example, NM can be responsible for the distribution, configuration, control, and monitoring of network resources. NM is supported by EM or DM.
- Network function virtualized infrastructure (NFVI) module used to deploy virtual network functions (VNF), which can be a set of operating environments consisting of software and hardware, including virtual layers and abstract hardware resources. .
- VNF virtual network functions
- NFV-MANO system module It has an interface with NFVI module, VNF module, EM module and NM module for managing virtual network functions at the network level, including the following three modules:
- NFVO Network function virtualization orchestrator
- VNFM Virtualized network function manager
- VIM Virtualized Infrastructure Manager
- the network management architecture 100 can manage physical network functions and virtual network functions. However, it is not capable of managing and orchestrating network slices. Therefore, the network management architecture 100 cannot meet the requirements of the network slicing technology application in the future communication system, that is, the network slicing cannot be managed and arranged flexibly.
- the physical network element and the virtualized network element will coexist for a long time and flexibly form a network slice. Therefore, there is a need for a network management system that enables the organization and management of physical and virtual network functions or network resources to implement network slicing applications.
- Embodiments of the present application provide a method, apparatus, and system for managing a network slice instance.
- the central idea is to introduce the Network Slice Manager and orchestrator (NSM&O) module in the network management architecture, and manage the creation process of the network slice instance through the NSM&O module to realize the automatic creation of the network slice instance and improve Manage the efficiency of network tile instances.
- NSM&O Network Slice Manager and orchestrator
- the network management architecture of the embodiment of the present application is described below.
- the embodiment of the present application introduces an NSM&O module based on the existing network management architecture.
- the structure diagram of the NSM&O module is shown in Figure 2. Its main functions include:
- the service description information sent by the sender device is received through an interface (for example, may be an Application Programming Interface (API)), and the service description information is converted into a requirement for the network.
- API Application Programming Interface
- Network Slice Design Describes the composition of the network slice based on the results of the service transformation.
- it can be a Design Network Slice Descriptor (NSLD).
- NSLD Design Network Slice Descriptor
- Network Slice Management Strategy Design a management strategy for network slices. For example, it may be a network slice instantiation, a network slice scaling, a network slice update, a network slice termination, a network slice deletion, and the like.
- Network Slice Orchestration Used to specifically determine the network functions and network resources used by the network slice instance.
- Monitoring Status parameters used to detect and report network slice instances. For example, you can monitor Key Performance Indicators (KPI) parameters for network slicing instances.
- KPI Key Performance Indicators
- the above-mentioned sender device can also be called sender (English).
- the sender device is the device that sends the request to the NSM&O module.
- the sender device may be an operator, a third party client, an application involved in the communication service, or any other physical device that may send a request to the NSM&O module.
- the network management architecture in the embodiment of the present application may further include a storage device, where the storage device may be used to record information of the generated network slice instance.
- FIG. 3 to FIG. 6 are only for facilitating the understanding of the embodiments of the present application, and the embodiments of the present application are not limited to the specific numerical values or specific scenarios illustrated. It will be obvious to those skilled in the art that various modifications and changes can be made without departing from the scope of the embodiments of the present invention.
- FIG. 3 to FIG. 6 respectively illustrate four network management architectures of the embodiments of the present application.
- all four network management architectures Includes NSM&O modules.
- the network management architectures of FIG. 3 to FIG. 6 are hereinafter referred to as a first network management architecture, a second network management architecture, a third network management architecture, and a fourth network management architecture.
- FIG. 3 shows a schematic structural diagram of a first network management architecture.
- the first network management architecture is a network management architecture that is enhanced and modified based on the network management architecture 100.
- the first network management architecture does not include the NM module, but the NSM&O module performs the functions performed by the NM module in the network management architecture 100.
- the NSM&O module can include all the functions of the NM module in addition to the functions shown in FIG. 2.
- the NSM&O module can interact with the EM through a communication interface to implement management of network functions corresponding to the network slice instance.
- the management of the network function includes the management of the PNF module and the VNF module.
- the NSM&O module can also receive status information of the VNF module from the NFVO module via the communication interface, and send instructions to the NFVO via the communication interface.
- the NSM&O module can directly manage the physical network functions, and can utilize the NFVO module to implement resource management of the NFVI module and implement VNF generation.
- FIG. 4 is a schematic structural diagram of a second network management architecture according to an embodiment of the present application.
- the second network management architecture is also a network management architecture that is enhanced and modified based on the network management architecture 100.
- the second network management architecture is different from the first network management architecture in that the entity of the second network management architecture does not include the NFVO module.
- the functionality of the NFVO module is implemented by the NSM&O module.
- the NSM&O module's capabilities include the management of virtual network resources and VNF lifecycle management.
- the interface can be referred to as an NG2 interface.
- the NSM&O module and the VNFM module can perform the following interactions through the NG1 interface: support authorization, reservation, allocation, and release of NFVI resources by the VNF; query running status information, such as VNF instance query; VNF initialization update, scaling, Ending, etc.; transmitting VNF related events, status information, etc.
- the NSM&O module and the VIM module can perform the following interactions through the NG2 interface: NFVI resource reservation, allocation, release, etc.; VNF software image (image) addition, deletion, update, etc.; transmission of NFVI-related configuration information, events, measurement results, upgrades Record and so on.
- the NSM&O module can also manage virtual network functions and the VNF life cycle. Therefore, it is possible to uniformly manage and orchestrate physical and virtual network resources and functions, and optimize resources from a global perspective.
- FIG. 5 is a schematic structural diagram of a third network management architecture according to an embodiment of the present application.
- the NM module is reserved in the third network management architecture, and the NSM&O module and the NM module are independent of each other.
- the communication interface can be referred to as an NG3 interface.
- the communication interface can be referred to as an NG4 interface.
- the communication interface can be referred to as an NG4 interface.
- the communication interface can be referred to as an NG5 interface.
- the NSM&O module and the NM module can perform the following interactions through the NG3 interface: transmitting the negotiation information between the NSM&O module and the NM module, for example, the NSM&O module queries the VNF that has been generated by the NM module; and the NM module feeds back the generated VNF information to the NSM&O module. And confirm that the NSM&O module is allowed to modify the VNF information; the NSM&O module notifies the NM module which PNF/VNF will be modified; the NSM&O module notifies the NM module of the specific modification of the PNF/VNF.
- the NSM&O module and the EM module can communicate with each other through the NG5 interface: the NSM&O module communicates with the EM module through the NG5 interface to manage the PNF and VNF (if the EM supports the management of the VNF).
- the NSM&O module uses a new communication interface to interact with the various physical modules in the third network management architecture.
- NSM&O modules can be used to orchestrate and manage virtual resources through NFVO modules and participate in VNF lifecycle management.
- NSM&O modules and NM modules can directly manage PNF.
- NSM&O modules and NM modules can manage VNF through NFVO modules or EM modules. Therefore, for the management of PNF and VNF, the NSM&O module and the NM module can be coordinated through communication.
- FIG. 6 is a schematic structural diagram of a fourth network management architecture according to an embodiment of the present application.
- the NM module is also retained in the fourth network management architecture.
- the NSM&O module and the NM module are also independent of each other.
- the fourth network management architecture differs from the third network management architecture in that the entity of the fourth network management architecture does not include the NFVO module.
- the functionality of the NFVO module is implemented by the NSM&O module.
- the NSM&O module's capabilities include the management of virtual network resources and VNF lifecycle management.
- the communication interface can be referred to as an NG1 interface.
- the communication interface can be referred to as an NG2 interface.
- the communication interface can be referred to as an NG5 interface.
- the NG1 interface, the NG2 interface, and the NG5 interface the same or similar contents in FIG. 4 and FIG. 5 can be referred to. For the sake of brevity, it will not be repeated here.
- the NSM&O module uses a new communication interface to interact with the various physical modules in the fourth network management architecture.
- NSM&O modules can be used to orchestrate and manage virtual resources through NFVO modules and participate in VNF lifecycle management.
- NSM&O modules and NM modules can directly manage PNF. Therefore, for the management of the PNF, the NSM&O module and the NM module can be coordinated by communication.
- the NSM&O module incorporates the functionality of the NSFO module, the NSM&O module can also directly manage virtual network resources and participate in VNF lifecycle management.
- the NM module does not manage virtual network resources and VNFs.
- the network management architecture of the present embodiment is described above in conjunction with FIGS. 1 through 6.
- the method for managing a network sharding instance in the embodiment of the present application is described below.
- the method for managing a network sharding instance may be applied to the first network management architecture to the fourth network management architecture in the embodiment of the present application.
- the method for managing the network sharding instance can be applied to other similar network management architectures, which is not limited in this embodiment of the present application.
- the first network device may be an NSM&O module in the network management architecture in the embodiment of the present application
- the second network device may be an EM module in the network management architecture
- the third The network device may be a VNFM module or an NFVO module in a network management architecture
- the fourth network device may be a VIM module in a network management architecture
- the fifth network device may be an NM module in a network management architecture.
- the foregoing first to fifth network devices may be other physical devices that have corresponding functions in the network management architecture, which is not limited in this embodiment of the present application.
- FIG. 7 shows a method 700 for managing a network slice instance according to an embodiment of the present application.
- the method 700 includes:
- the first network device receives a network slice instance creation request from the sender device, where the network slice instance creation request is used to request to create a target network slice instance, where the network slice instance creation request includes the target network slice Description information of the slice instance.
- the network slice corresponding to the target network slice instance needs to be designed according to the description information of the target network slice instance.
- the way network slicing is designed includes at least two.
- One of the methods is that a network slice template can be preset, and the network slice template can be designed according to different service types. In other words, multiple network slice templates can exist for multiple service types.
- the first network device may determine the configuration parameters of the corresponding network slice template and the network slice template according to the description information of the network slice instance.
- the first network device may also modify the network slice template according to the description information of the network slice instance to design a network function corresponding to the network slice instance; in another mode of network slice design, The network slice template may not be set in advance, and the first network device directly designs the network function of the network slice according to the description information of the network slice instance.
- the foregoing description information may include at least one of the following information: description information of the service requirement of the target network slice instance and configuration parameter information of the network slice template of the target network slice instance.
- the first network device may convert the information to the network network slice instance according to the description information of the service requirement. And design network slices according to network requirements. For example, directly describe the composition of the target network slice instance. Or, according to the network requirement, determining configuration parameter information of the network slice template corresponding to the target network slice instance.
- the description of the service requirement may be Mobile Broadband (MBB)/Ultra-reliable low-latency communication (URLLC)/Machine Type communication (MTC) that meets certain KPI requirements. )business.
- MBB Mobile Broadband
- URLLC Ultra-reliable low-latency communication
- MTC Machine Type communication
- the configuration parameter information of the network slice template may be determined according to the description information of the target network slice instance, thereby completing the design of the target network slice instance.
- the configuration parameter information of the network slice template may be an input parameter of the network slice template.
- a network slice template of an MTC service already exists in the NSM&O module, and the sender device can describe the required information in the description information in the network slice instance creation request according to the configurable parameter opened by the network slice target.
- Configuration parameter information of the network slice instance of the MTC service may include information such as the number of connections.
- the first network device sends network function configuration indication information to the second network device according to the description information, where the network function configuration indication information is used to indicate that the second network device configures the target network slice instance. Internet function.
- the network function may include at least one of a physical network function and a virtual network function.
- the network function included in the network slice instance may be either a physical network function or a virtual network function, or both a physical network function and a virtual network function. This makes it possible to flexibly schedule and manage the network functions of network slice instances as needed. For example, when the virtual network function cannot support a certain network function, you can select a physical network element to implement the network function.
- the network function included in the network slice instance may be a shared network function or a dedicated network function.
- the shared network function refers to a network function that can be commonly used by multiple network slice instances.
- a dedicated network function can be a network function used by a separate network tile instance.
- multiple network slice instances can be created, and multiple network slice instances can use several shared network functions simultaneously, and each network slice instance can contain proprietary network functions that are only used by itself.
- configuring the network slice instance includes multiple cases.
- the network function of the network slice instance is a dedicated network function, and the network function is a physical network function
- the second case is that the network function of the network slice instance is a dedicated network function
- the network function is a virtual network function.
- the network function of the network slicing embodiment is a shareable network function.
- the sharable network function means that the network function can be shared by multiple network slice instances, and the shareable network function includes two situations: one case is that the network function is being shared by multiple network slice instances.
- One case is that only one network slice instance is currently in use, ie it is still a dedicated network function, but can be shared by other network slice instances in the future.
- the sharable network function can be either a physical network function or a virtual network function.
- the first branch is that the sharable network function does not start running
- the second branch is that the sharable network function has started to run.
- the shareable network function has been used by other network slice instances. The process of configuring the network slice instance will be described below for these three cases.
- the network function includes a dedicated physical network function
- the PNF module is a physical network element
- the PNF module is a real existing module, and there is no concept of generating a PNF module. Therefore, only the second network device is required to configure the physical network function of the target network slice instance to enable the configured physical network function to serve the target network slice instance.
- the VNF module is a module that performs the virtual network function, so the first network device needs to determine whether the VNF module corresponding to the target network slice instance has been created or generated.
- the third network device module is responsible for creating or generating a VNF module.
- the first network device may directly instruct the second network device to configure the corresponding virtual network function for the VNF module.
- the first network device may instruct the third network device to generate the VNF module. The second network device is then instructed to perform a corresponding virtual network function configuration on the generated VNF module.
- the first network device may instruct the second network device to configure sharing.
- Network function which can be a physical network function or a virtual network function.
- the configuration of the shared network function is the same as or similar to the above configuration of the dedicated network function. For example, for a shared virtual network feature that is not generated, a new virtual network feature can be created to support the new network tile instance.
- the shared network function since the shared network function currently only serves the newly created network slice instance and is not shared by other network slice instances, the shared network function and the dedicated network function are currently similar, and only serve a single network slice instance. However, this shared network feature can be shared by other network tile instances in the future. That is, the shared network function can be configured in the future so that it can serve other network slice instances at the same time. For example, the configured shared network function can be identified, the identifier is used to indicate that the shared network function currently serves the target network slice instance, but the network function can be shared with other network slice instances in the future.
- the shareable network function has started running, or if the shareable network function has been used by other network slice instances.
- the first network device needs to instruct the second network device to configure the shared network function such that the target network slice instance can share network functions with other network slice instances.
- the running shareable network function may be a network function that has been used by one network slice instance, or a function that has been used by multiple network slice instances.
- the sharable network function may be a dedicated network in an initial state. A feature that reconfigures this proprietary network feature to become a shared network feature.
- the first network device can interact with the third network device and the fourth network device to cooperatively configure the shared network function.
- the first network device may send a network resource extension indication to the fourth network device, where the network resource extension indication is used to instruct the fourth network device to allocate network resources for the shared network function of the target network slice instance.
- the foregoing network function configuration indication information includes configuration information required to configure a network function of the target network slice instance.
- the foregoing configuration information may include, but is not limited to, related parameters of the network slice instance: an identifier of the network slice instance, a type of the network slice instance, and other parameters that need to be monitored and reported.
- the traditional operating parameters such as the Mobility Management Entity Code (MMEC), the MME pool (Pool), and the like are included.
- the network function configuration indication information may further include information about the shared network function included in the network slice instance or other network sharing the network function.
- the configuration information of the slice instance For example, in a case where the shared network function is a non-access stratum (NAS) message routing network function, configuration information of a network slice instance sharing the network function needs to be acquired, so as to determine how to use the NAS information. Route to the corresponding network slice instance.
- NAS non-access stratum
- the identifier of the target network slice instance may be included in the network function configuration indication information.
- the configuration of the shared network function in the network function configuration indication information includes a plurality of situations compared to the dedicated network function. For example, if a newly created network tile instance is going to use an existing shared network feature that is being used by other network tile instances.
- the content that needs to be configured at this time includes: a) providing information such that the shared network function can serve the newly generated network slice instance.
- the network slice selection function as an example, if the function is a shared network function, the newly generated network slice instance needs to be aware of the existence of other network slice instances sharing the network function, so that the appropriate network slice instance can be selected. Therefore, for the Network Slice Selection feature or other network features, you need to configure an identifier for the newly generated target network slice instance.
- the network function configuration indication information may include multiple network slice instances indicating the shared network function and the shared network function. Mapping relationship.
- the function can be a shared network function under normal circumstances. This function is mainly used to forward the NAS message received by the Mobility Management (MM) function to the session management function corresponding to the correct network slice instance.
- MM Mobility Management
- the path of the above functions is MM function (shared)->NAS routing function (shared)->SM function (exclusive). Therefore, the NAS routing function needs to know the mapping relationship between the newly generated network slice instance identifier and the SM function identifier. In other words, the mapping relationship between the NAS routing function and the SM functions of multiple network sharding instances needs to be configured in the network sharding instance.
- This configuration is typically in a shared network function that interfaces with proprietary network functions to enable shared network functionality to transmit messages to the correct network slice instances in multiple network tile instances.
- more powerful processing power may be required as the shared network functionality will serve the newly generated network tile instance. Therefore, more computing resources, storage resources, or network resources need to be added to the shared network function.
- the network function MM function that can be shared its main function is to need to track The location of the user within the slice, so when the MM supports more network slice instances, more computational and storage resources may be needed.
- the first network device receives the network function configuration response information sent by the second network device, where the network function configuration response information indicates that the network function configuration of the target network slice instance is completed.
- the first network device receives the network function configuration response information sent by the second network device, to indicate that the second network device configures the network function of the target network slice instance. .
- the network function configuration response information may also indicate that the network function configuration of the target network slice instance fails, so that the first network device re-establishes the target network slice instance. Management and orchestration strategy.
- the first network device sends network slice instance creation response information to the sending end device, where the network slice instance creation response information indicates that the target network slice instance creation is completed.
- the first network device may send the network slice instance creation response information to the sending end device, to indicate that the network slice instance is created. result.
- the network slice instance creation response information indicates to the sender device that the network slice instance is successfully created; in a case that the network function configuration of the target network slice instance fails, the network The slice instance creation response information may indicate to the source device that the network slice instance creation failed.
- the first network device by instructing the second network device to perform the network function configuration of the network splicing instance, to manage the process of creating the network sharding instance, can automatically create the network sharding instance, and improve the management network slice. The efficiency of the instance.
- the method 700 further includes: the first network device The third network device sends a virtual network function creation request, the virtual network function creation request is used to instruct the third network device to create a virtual network function of the target network slice instance.
- the third network device may be a VNFM module in the second network management architecture or the fourth network management architecture, or may be an NVFO module in the first network management architecture or the third network management architecture.
- the fourth network device is required to allocate corresponding network resources for the virtual network function.
- the fourth network device may receive a resource allocation request from the NVFO module and allocate corresponding network resources.
- the third network device may send a resource allocation request to the fourth network device to request the fourth network device to allocate the network resource corresponding to the virtual network function to the target network slice instance. .
- the first network device further includes a function of the NVFO module, so the first network device sends a resource allocation request to the fourth network device. Therefore, the method 700 further includes: the first network device sends an allocation resource request to the fourth network device, where the allocation resource request is used to request the fourth network device to allocate the network resource corresponding to the virtual network function for the target network slice instance.
- the method 700 further includes: the first network device receiving the allocated resource response information sent by the fourth network device, where the resource response is allocated The information is used to indicate that the network resource allocation corresponding to the virtual network function of the target network slice instance is completed.
- the allocated resource The response information may be used to indicate an allocation result of the network resource corresponding to the virtual network function of the target network slice instance.
- the allocated resource response information may indicate that the network resource allocation corresponding to the virtual network function of the target network slice instance fails.
- the method 700 further includes: the first network device receiving virtual network function creation response information sent by the third network device, where the virtual network The function creation response information indicates that the virtual network function creation of the target network slice instance is completed.
- the virtual network function creation response information may be used to indicate a result of virtual network function creation of the target network slice.
- the virtual network function creation response information may indicate that the virtual network function creation of the target network slice instance fails.
- the method 700 further includes: the first network device sending the resource allocation confirmation information to the third network device,
- the resource allocation confirmation information is used to indicate that the network resource allocation corresponding to the virtual network function of the target network slice instance is completed.
- the first network device sends the resource allocation confirmation information to the fourth network device, so that the third network device configures the virtual network function of the target network slice instance after determining that the network resource allocation is completed.
- the third network device may send a request for adding the virtual network function module to the second network device, to The generated virtual network function module is added as a management device of the second network device.
- the NSM&O module and the NM module can configure network functions. Therefore, the NSM&O module and the NM module can interact with the state of the network function configuration to facilitate coordination of the network function configuration. Therefore, the method 700 further includes: the first network device transmitting, to the fifth network device, network function notification information, where the network function notification information is used to indicate a network function to be configured by the first network device. Thereby, the network function configuration can be coordinated between the first network device and the fifth network device, thereby improving the efficiency of managing the network slice.
- the network functions to be configured above may include physical network functions as well as virtual network functions.
- the method 700 further includes: the first network device receiving network function response information sent by the fifth network device, where the network function response information is used to confirm that the fifth network device has determined the first The network function that the network device will be configured with.
- the method 700 further includes: the first network device sends network function query information to the fifth network device, where the network function query information is used to request to query the network function that the fifth network device has generated;
- the first network device receives the network function feedback information sent by the fifth network device, where the network function feedback information is used to indicate the network function that the fifth network device has generated, so as to facilitate the first network.
- the device coordinates the network function configuration.
- the network function that needs to be queried may be a virtual network function.
- the NSM&O module can directly manage the physical network function modules, but the configuration parameters of the NM module to the virtual network module may only be stored in the NM module.
- the NSM&O module needs to query the NM module for the virtual network function generated by the NM module, so that the NSM&O module can manage and arrange the network functions.
- the above generated networks include two types: the first type is a running network function; the second type is a network function that has been generated but not yet running.
- the NSM&O module can configure the network functions that the NM module has generated. To improve the efficiency of the use of resources.
- the first network device may verify the network slice real Whether the creation request is legal. Therefore, the method 700 further includes: the first network device sending legality verification information to the storage device, where the legality verification information is used to request to query whether the network slice instance creation request is legal; the first network device receiving The validity verification response information sent by the storage device is used to indicate whether the network slice instance creation request is legal.
- the first network device may not perform the network function configuration operation of the target network slice instance. If the legality verification response information indicates that the legality is valid, the first network device may perform a corresponding network function configuration operation.
- the first network device sends the network function configuration indication information to the second network device according to the description information, including: if the legality verification response information indicates that the network slice instance creation request is legal And the first network device sends the network function configuration indication information to the second network device according to the description information.
- the foregoing storage device may be a distributed memory, or may be other types of storage.
- the storage device can be used to store information for signing for verifying the legitimacy of the network tile instance creation request.
- the first network device may interact with the second network device, the third network device, and the fourth network device by using the communication interface, to query the running status of the current network function, the network resource. Occupation.
- network resources can be reserved for the target network slice instance.
- the first network device may send resource reservation indication information to the fourth network device, where the resource reservation indication information is used to instruct the fourth network device to reserve network resources for the target network slice instance.
- the first network device may send, to the sending device, failure feedback information indicating that the network resource is insufficient.
- the first network device may set the state of the network slice instance to an active state.
- the method 700 further includes the first network device transmitting a network slice instance activation indication to the storage device, the network slice instance activation indication setting the target network slice instance to an active state.
- the method 700 further includes: the first network device may send a network function port activation indication to the second network device, the network function port activation indication for activation The port of the network function of the target network slice instance.
- the first network device may instruct the storage device to store configuration parameters of the newly generated network slice instance into the storage device.
- the method 700 further includes the first network device transmitting an update network slice instance indication to the storage device, the update network slice instance indication for indicating that the parameter information of the target network slice instance is stored in the storage device.
- the parameter information of the target network slice instance stored in the storage device may include a shared network function or a shareable network slice instance type or the like.
- FIG. 8 to FIG. 11 are only for facilitating the understanding of the embodiments of the present application, and the embodiments of the present application are not limited to the specific numerical values or specific scenarios illustrated. A person skilled in the art will be able to make various modifications or changes in the embodiments according to the examples of FIG. 8 to FIG. 11 which are within the scope of the embodiments of the present application.
- FIG. 8 is a schematic flowchart diagram of a method 800 for managing a network slice instance according to an embodiment of the present application.
- Method 800 can Used in the second network management architecture shown in FIG.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be a VNFM module
- the fourth network device may be a VIM module.
- the portion S807 is an execution method when the shared network function has been run.
- Sections S808 through S821 are implementation methods that require newly generated network functions.
- the newly generated network functions described above can be either shared network functions or dedicated network functions.
- the S808 part and the S809 part are execution methods when the newly generated network function is a physical network function.
- Sections S810 through S821 are methods of execution when the newly generated network function is a virtual network function.
- Method 800 includes:
- the NSM&O module receives a network slice instance creation request from the sender device.
- This network slice instance creation request can be used to request the creation of a target network slice instance.
- the description information of the target network slice instance may be carried in the network slice instance creation request.
- the foregoing description information may be description information of a service requirement of a target network slice instance and configuration parameter information of a network slice template of a target network slice instance.
- the NSM&O module interacts with the storage device to verify whether the network slice instance creation request is legal.
- the NSM&O module may send legality verification information to the storage device, where the legality verification information may include description information or other information of the target network slice instance.
- the user subscribes to the information stored in the storage device.
- the storage device can verify whether the creation request of the target network slice instance is legal according to the information signed by the user, and return the legality verification response information to the NSM&O module. If legal, the validity verification response information indicates that the network slice instance creation request is legal. If it is not legal, the validity verification response information indicates that the network slice instance creation request is invalid.
- the NMS&O module sends a network slice instance creation response message to the sending end device, where the network layer instance creation response information may indicate that the target network slice creation fails, if the legality verification response information indicates that the network slice instance creation request is invalid. This process ends. Further, the network slice instance creation response information may carry the reason for the creation failure, that is, no permission.
- the NSM&O module performs network function and resource scheduling, and determines whether the target network slice instance uses the shared network function.
- the universal function of the network function and the resource may include determining the location of the network function of the target network slice in the physical network or the virtual network, and determining the required network resources and the like.
- the NSM&O module interacts with the EM module, the VNFM module, and the VIM module to query the running status of the current network function and the occupation of network resources. And instruct the VIM module to reserve network resources for the target network slice instance.
- the NSM&O module sends the network slice instance creation response information to the sending end device to indicate that the target network slice instance is created. Failure. This process ends. Further, the network slice instance creation response information may carry the reason for the creation failure, that is, the network resource is insufficient.
- the NSM&O module sends the network slice instance configuration information to the EM module to instruct the EM module to configure the shared network.
- the shared network function can be a virtual network function or a physical network function.
- the NSM&O module can interact with the EM module, the VNFM module, and the VIM module, respectively, to configure the shared network function for the target network slice instance, so that the shared network function supports the newly created target network slice instance.
- the configured information may include, but is not limited to: a) parameters related to the network slice instance.
- the net The identifier of the network slice instance, the type of the network slice instance, and the network function information included in the network slice instance (for example, in the case where the shared network function is a NAS route network function, configuration information of the network slice instance that needs to acquire the shared network function)
- the shared network function is a NAS route network function, configuration information of the network slice instance that needs to acquire the shared network function
- parameters that the network slice instance needs to monitor and report In order to determine how to route NAS information to the corresponding network slice instance, parameters that the network slice instance needs to monitor and report.
- Other traditional operating parameters are examples of the network slice instance.
- the NSM&O module instructs the EM module to configure the physical network function (ie, PNF). That is, the NSM&O module sends network slice instance configuration information to the EM module to instruct the EM module to configure the physical network function.
- the information that needs to be configured may include, but is not limited to: a) parameters related to the network slice instance. For example, the identifier of the network slice instance and the parameters of the network slice instance that need to be monitored and reported. b) Traditional operating parameters. For example, the Internet Protocol (IP) address of the gateway, the tunnel identifier, and the like.
- IP Internet Protocol
- the information that needs to be configured may include, but is not limited to, an identifier of the network slice instance, a type of the network slice instance, and information about a network function included in the network slice instance (for example, may be The newly generated shared network function is identified to indicate that the shared network function currently serves the target network slice instance, which may be shared with other specified types of network slice instances in the future, and parameters that the network slice instance needs to monitor and report.
- other legacy operational parameters may be included in addition to the parameters associated with the network slice instance. For example, MMEC, MME pool, and the like.
- the EM module sends a network slice instance creation response message to the NSM&O module to indicate that the target network slice instance is created.
- the NSM&O module receives the network slice instance creation response information sent by the EM module.
- the NSM&O module sends a virtual network function creation request to the VNFM module to instruct the VNFM module to create the virtual network function.
- the virtual network function creation request may carry configuration parameters of the virtual network function.
- the configuration parameter may include feedback information of reserved network resources in the S804 portion.
- the configuration parameters may also include parameters describing virtual network functional characteristics, such as virtual machine versions or computing resource requirements, and the like.
- the VNFM module After receiving the virtual network function creation request, the VNFM module checks the correctness of the configuration parameters of the virtual network function, and authorizes the lifecycle management action of starting the virtual network function.
- the VNFM module sends an allow resource allocation indication information to the NSM&O module to indicate that the NSM&O module is allowed to allocate resources. Further, the VNFM module may modify the configuration parameters of the virtual network function, and carry the modified configuration parameters in the allowed resource allocation indication information.
- the NSM&O module sends a resource allocation request to the VIM module, where the resource allocation request is used to request the VIM module to allocate a network resource corresponding to the virtual network function to the target network slice instance. Further, if the S112 part allows the allocated resource indication information to carry the modified configuration parameter for the virtual network function, the NSM&O module needs to modify the virtual network function according to the modification instruction, and then send the resource allocation request to the VIM module.
- the VIM module performs a resource allocation process according to the resource allocation request of the NSM&O module.
- the VIM module sends the resource allocation response information to the NSM&O module to indicate that the network resource allocation corresponding to the virtual network function is completed.
- the NSM&O module receives the allocated resource response information.
- the NSM&O module After receiving the allocated resource response information, the NSM&O module sends the resource allocation confirmation information to the VNFM module to indicate that the VNFM module network resource allocation is completed, so that the VNFM performs the configuration process of the virtual network function.
- the VNFM module receives the allocated resource response information.
- the VNFM module After receiving the resource allocation confirmation information, the VNFM module configures parameters for deployment of the virtual network function. For example, configure the IP address of the virtual network function, the identity of the virtual network function, and the like.
- the VNFM module After configuring the deployment parameters of the virtual network function, the VNFM module sends a request for adding a virtual network function to the EM module to request the EM module to add the configured virtual network function as the managed device.
- the EM module receives the virtual network function request and adds the virtual network function to the managed device.
- the VNFM module After configuring the deployment parameters of the virtual network function, the VNFM module sends a virtual network function creation response message to the NSM&O module to indicate that the virtual network function of the target network slice instance is created.
- the NSM&O module receives the virtual network function creation response information.
- the NSM&O module can learn that the virtual network function has been created, so the NSM&O module can configure the parameters related to the target network slice instance of the virtual network function.
- the NSM&O module sends network function configuration indication information to the EM module to indicate that the virtual network function is configured.
- the information that needs to be configured may include, but is not limited to: a) parameters related to the network slice instance. For example, the identifier of the network slice instance and the parameters of the network slice instance that need to be monitored and reported. b) Traditional operating parameters. For example, the Internet Protocol ("IP”) address of the gateway, the tunnel identifier, and the like.
- IP Internet Protocol
- the information that needs to be configured may include, but is not limited to, an identifier of the network slice instance, a type of the network slice instance, and information about a network function included in the network slice instance (for example, may be The newly generated shared network function is identified to indicate that the shared network function currently serves the target network slice instance, which may be shared with other specified types of network slice instances in the future, and parameters that the network slice instance needs to monitor and report.
- other legacy operational parameters may be included in addition to the parameters associated with the network slice instance. For example, MMEC, MME pool, and the like.
- the EM module may send a network function configuration response message to the NSM&O module to indicate that the virtual network function configuration is completed.
- the NSM&O module receives the network function configuration response information.
- the NSM&O module sends a network slice instance activation indication to the storage device to indicate that the target network slice instance is set to an active state.
- the NSM&O module sends a network function port activation indication to the EM module to activate a port of the network function of the target network slice instance, so that the virtual network function or the port related to the physical network function starts to send or receive data.
- the NSM&O module interacts with the storage device to store parameter information of the newly generated target network slice instance into the storage device.
- the parameter information described above may include a shared network function of the target network slice instance or a type of network slice instance that may share the network function with the target network slice instance.
- S825 The NSM&O module sends a network slice instance creation response message to the sending end device to indicate that the network slice instance is created. This process ends. Alternatively, if the target network slice only contains the shared network function and the shared network function is already running, the S825 portion may be executed after S807. If the network function included in the target network slice is a newly generated network function and the network function is a physical network function, the S825 portion may be executed after S809.
- FIG. 8 a process of creating a network slice instance in a second network management architecture is shown, wherein the NSM&O module can flexibly arrange and manage network functions and network resources of the network slice instance, and improve management network slice instances. effectiveness.
- FIG. 9 is a schematic flowchart of a method 900 for managing a network slice instance according to still another embodiment of the present application.
- Method 900 can be applied to the first network management architecture shown in FIG.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be an NVFO module
- the fourth network device may be a VIM module.
- the same or similar contents as in FIG. 8 in the method of FIG. 9 are not described herein again for the sake of brevity.
- the first network management architecture applied by the method of FIG. 9 includes an NFVO module, that is, the NFVO module and the NSM&O module in FIG. 9 are independent of each other, and the method in FIG. 8 applies the NSM&O module in the second network management architecture.
- NFVO module NFVO module
- the interaction process between the NSM&O module and the VNFM module and the VIM module in the method 800 is specifically performed by the NSM&O module in the method 900.
- Method 900 includes:
- Parts S901 to S909 are the same as or similar to parts S801 to S809 in Fig. 8, and are not described herein again.
- the NSM&O module sends a virtual network function creation request to the NFVO module.
- the NFVO module receives a virtual network function creation request.
- the NFVO module interacts with the VNFM module and the VIM module to complete the creation of the virtual network function.
- the NFVO module sends a request for adding a virtual network function to the EM module to request the EM module to add the configured virtual network function as the managed device.
- the EM module receives the virtual network function request and adds the virtual network function to the managed device.
- the NFVO module sends a virtual network function creation response message to the NSM&O module to indicate that the virtual network function of the target network slice instance is created.
- the NSM&O module receives the virtual network function creation response information.
- the NSM&O module After receiving the virtual network function creation response information, the NSM&O module sends network function configuration indication information to the EM module to indicate that the virtual network function is configured.
- the EM module may send a network function configuration response message to the NSM&O module to indicate that the virtual network function configuration is completed.
- the NSM&O module receives the network function configuration response information.
- the NSM&O module sends a network slice instance activation indication to the storage device to indicate that the target network slice instance is set to an active state.
- the NSM&O module sends a network function port activation indication to the EM module to activate a port of the network function of the target network slice instance, so that the virtual network function or the port related to the physical network function starts to send or receive data.
- the NSM&O module interacts with the storage device to store parameter information of the newly generated target network slice instance into the storage device.
- the parameter information described above may include a shared network function of the target network slice instance or a type of network slice instance that may share the network function with the target network slice instance.
- S919 The NSM&O module sends a network slice instance creation response message to the sending end device to indicate that the network slice instance creation is completed. This process ends. Alternatively, if the target network slice only contains the shared network function and the shared network function has been run, the S919 portion may be executed after S907. If the target network slice contains a network function that is a newly generated network function and the network function is a physical network function, the S919 portion may be executed after S909.
- parts S914 to S919 are the same as or similar to parts S820 to S825 in Fig. 8, and a part of the description is omitted for the sake of brevity.
- FIG. 9 a process of creating a network slice instance in the first network management architecture is shown, wherein the NSM&O module can flexibly arrange and manage the network function and network resources of the network slice instance, and improve the management network slice instance. effectiveness.
- FIG. 10 is a schematic flowchart of a method 1000 for managing a network slice instance according to still another embodiment of the present application.
- Method 1000 can be applied to the third network management architecture shown in FIG.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be an NVFO module
- the fourth network device may be a VIM module
- the fifth network device may be an NM. Module.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be an NVFO module
- the fourth network device may be a VIM module
- the fifth network device may be an NM. Module.
- the difference between the third network management architecture applied by the method of FIG. 10 and the first network management architecture applied by the method of FIG. 9 is that the NSM&O module in the first network management architecture includes the functions of the NM module, and the third network management
- the NSM&O modules in the architecture are independent of the NM modules. Therefore, the NSM&O module and the NM module in FIG. 10 can manage physical network functions, and both the NSM&O module and the NM module can manage virtual network functions through the NFVO module. Therefore, in order to avoid configuration conflicts.
- the configuration process of the network function needs to be coordinated between the NSM&O module and the NM module.
- the S1007 part to the S1010 part and the S1024 part of the method 1000 are processes for coordinating the configuration of the network function.
- the S1014 part and the S1015 part are processes for the NSM&O module to configure the virtual network function that has been generated by the NM module.
- Method 1000 includes:
- the S1001 part to the S1006 part is the same as or similar to the S801 part to the S806 part in FIG. 8 . Please refer to the corresponding content in the method of FIG. 8 , and details are not described herein again.
- the NSM&O module sends network function query information to the NM module to query the network function that the NM module has generated.
- the network function may be a virtual network function.
- the NM module receives the network function query information.
- the above generated networks include two types: the first type is a running network function; the second type is a network function that has been generated but not yet running.
- the physical network function can be directly managed by the NSM&O module, and the configuration parameters of the NM module for the network layer of the virtual network function may be stored only in the NM module. Therefore, it is necessary to query the NM for the configuration state of the virtual network function.
- the NM module sends network function feedback information to the NSM&O module to indicate the network function and related parameters generated by the NM module, so that the NSM&O performs coordinated configuration of the network function.
- the NSM&O module receives network function feedback information.
- the NSM&O module can configure the network functions that the NM module has generated. To improve the efficiency of the use of resources.
- the NSM&O module sends a network function notification message to the NM module to indicate the network function to be configured by the NSM&O module.
- This network function can include physical network functions or virtual network functions. To prevent the NM module and the NSM&O module from configuring the network functions at the same time, conflicts occur.
- the NM module receives the network function notification information.
- the NM module sends a network function response message to the NSM&O module to indicate that the NM module has confirmed the network function to be configured by the NSM&O module.
- the NSM&O module receives the network function response information.
- the NSM&O module After determining, in part 1004, that the network function of the target network slice includes a shared network function, and the shared network function is currently running, the NSM&O module sends the network slice instance configuration information to the EM module to instruct the EM module to configure the shared network.
- the shared network function can be a virtual network function or a physical network function. can.
- the NSM&O module can interact with the EM module and the NFVO module, respectively, to configure the shared network function for the target network slice instance, so that the shared network function supports the newly created target network slice instance.
- the configured information may include, but is not limited to: a) parameters related to the network slice instance.
- the identifier of the network slice instance, the type of the network slice instance, and the network function information included in the network slice instance (for example, in the case where the shared network function is a NAS route network function, the network slice instance of the shared network function needs to be acquired) Configuration information to determine how to route NAS information to the corresponding network slice instance), parameters that the network slice instance needs to monitor and report. b) Other traditional operating parameters.
- the NSM&O module instructs the EM module to configure the physical network function (ie, PNF). That is, the NSM&O module EM module sends network slice instance configuration information to instruct the EM module to configure the physical network function.
- PNF physical network function
- the EM module sends a network slice instance creation response message to the NSM&O module to indicate that the target network slice instance is created.
- the NSM&O module receives the network slice instance creation response information sent by the EM module.
- the NSM&O module sends network function configuration indication information to the EM module to instruct the EM module to configure by using the virtual network function that the NM module has generated.
- the content of the specific configuration is the same as the portion of S820 in FIG. Further, the NSM&O module can interact with the NFVO module to modify and configure the generated virtual network functionality.
- the NSM&O module receives the network function configuration response information sent by the EM module, to indicate that the configuration of the generated virtual network function of the target network slice instance is completed.
- the NSM&O module sends a virtual network function creation request to the NFVO module.
- the NFVO module receives a virtual network function creation request.
- the NFVO module interacts with the VNFM module and the VIM module to complete the creation of the virtual network function.
- the NFVO module sends a request for adding a virtual network function to the EM module to request the EM module to add the configured virtual network function as the managed device.
- the EM module receives the virtual network function request and adds the virtual network function to the managed device.
- the NFVO module sends a virtual network function creation response message to the NSM&O module to indicate that the virtual network function of the target network slice instance is created.
- the NSM&O module receives the virtual network function creation response information.
- the NSM&O module can configure parameters related to the target network slice instance of the virtual network function.
- the NSM&O module sends network function configuration indication information to the EM module to indicate that the virtual network function is configured.
- the EM module may send network function configuration response information to the NSM&O module to indicate that the virtual network function configuration is completed.
- the NSM&O module receives the network function configuration response information.
- the NSM&O module sends a network slice instance activation indication to the storage device to indicate that the target network slice instance is set to an active state.
- the NSM&O module sends a network function port activation indication to the EM module.
- the NSM&O module sends a network function configuration feedback notification message to the NM module to indicate the specific content of the network function configuration of the NSM&O module.
- the NSM&O module interacts with the storage device to store parameter information of the newly generated target network slice instance into the storage device.
- S1026 The NSM&O module sends a network slice instance creation response message to the sender device to indicate that the network slice instance is created. This process ends.
- the parts S1016 to S1026 are the same as or similar to the parts S910 to S919 in Fig. 9, and a part of the description is omitted for the sake of brevity.
- a process of creating a network slice instance in a third network management architecture is shown, wherein the NSM&O module can flexibly arrange and manage the network function and network resources of the network slice instance, and improve the management network slice instance. effectiveness.
- FIG. 11 is a schematic flowchart of a method 1100 for managing a network slice instance according to still another embodiment of the present application.
- Method 1100 can be applied to the fourth network management architecture shown in FIG.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be an NVFO module
- the fourth network device may be a VIM module
- the fifth network device may be an NM. Module.
- the first network device may be an NSM&O module
- the second network device may be an EM module
- the third network device may be an NVFO module
- the fourth network device may be a VIM module
- the fifth network device may be an NM. Module.
- the difference between the fourth network management architecture applied by the method of FIG. 11 and the second network management architecture applied by the method of FIG. 8 is that the NSM&O module in the second network management architecture includes the functions of the NM module, and the fourth network management
- the NSM&O modules in the architecture are independent of the NM modules. Therefore, the NSM&O module and the NM module in Figure 11 can manage physical network functions. Therefore, in order to avoid configuration conflicts.
- the configuration process of the physical network function needs to be coordinated between the NSM&O module and the NM module.
- the S1107 part, the S1108 part, and the S1112 part of the method 1100 are contents for coordinating physical network functions.
- the NSM&O module in the fourth network management architecture is also responsible for managing virtual network functions, and the NM module does not need to manage virtual network functions.
- Method 1100 includes:
- the S1101 part to the S1106 part is the same as or similar to the S801 part to the S806 part in FIG. 8. Please refer to the corresponding content in the method of FIG. 8, and details are not described herein again.
- the NSM&O module sends a network function notification message to the NM module to indicate the network function to be configured by the NSM&O module.
- This network function can include physical network functions.
- the NM module receives the network function notification information.
- the NM module sends a network function response message to the NSM&O module to indicate that the NM module has confirmed the network function to be configured by the NSM&O module.
- the NSM&O module receives the network function response information.
- the NSM&O module sends the network slice instance configuration information to the EM module to instruct the EM module to configure the shared network.
- the shared network function can be a virtual network function or a physical network function.
- the NSM&O module can interact with the EM module and the NFVO module, respectively, to configure the shared network function for the target network slice instance, so that the shared network function supports the newly created target network slice instance.
- the configured information may include, but is not limited to: a) parameters related to the network slice instance.
- the identifier of the network slice instance, the type of the network slice instance, and the network function information included in the network slice instance (for example, in the case where the shared network function is a NAS route network function, the network slice instance of the shared network function needs to be acquired) Configuration information to determine how to route NAS information to the corresponding network slice instance), parameters that the network slice instance needs to monitor and report. b) Other traditional operating parameters.
- the NSM&O module instructs the EM module to configure the physical network function (ie, PNF). That is, the NSM&O module EM module sends network slice instance configuration information to instruct the EM module to configure the physical network function.
- PNF physical network function
- the EM module After the physical network function of the target network slice instance is configured, the EM module sends a network slice instance creation response message to the NSM&O module to indicate that the target network slice instance is created. The NSM&O module receives the network slice instance creation response information sent by the EM module.
- the NSM&O module sends a network function configuration feedback notification message to the NM to indicate the specific content of the physical network function configuration of the NSM&O module.
- the NSM&O module sends a virtual network function creation request to the VNFM module to instruct the VNFM module to create the virtual network function.
- the VNFM module After receiving the virtual network function creation request, the VNFM module checks the correctness of the configuration parameters of the virtual network function, and authorizes the lifecycle management action of starting the virtual network function.
- VNFM module In the case that the VNFM module authorizes the lifecycle management action of the virtual network function, the VNFM module sends an allow resource allocation indication information to the NSM&O module to indicate that the NSM&O module is allowed to allocate resources.
- the NSM&O module sends a resource allocation request to the VIM module, where the resource allocation request is used to request the VIM module to allocate a network resource corresponding to the virtual network function to the target network slice instance.
- the VIM module performs a resource allocation process according to the resource allocation request of the NSM&O module.
- the VIM module sends the allocated resource response information to the NSM&O module to indicate that the network resource allocation corresponding to the virtual network function is completed.
- the NSM&O module receives the allocated resource response information.
- the NSM&O module After receiving the allocated resource response information, the NSM&O module sends the resource allocation confirmation information to the VNFM module to indicate that the VNFM module network resource allocation is completed, so that the VNFM performs the configuration process of the virtual network function.
- the VNFM module receives the allocated resource response information.
- the VNFM module After receiving the resource allocation confirmation information, the VNFM module configures parameters for deployment of the virtual network function. For example, configure the IP address of the virtual network function, the identity of the virtual network function, and the like.
- the VNFM module After configuring the deployment parameters of the virtual network function, the VNFM module sends a request for adding a virtual network function to the EM module to request the EM module to add the configured virtual network function as the managed device.
- the EM module receives the virtual network function request and adds the virtual network function to the managed device.
- the VNFM module After configuring the deployment parameters of the virtual network function, the VNFM module sends a virtual network function creation response message to the NSM&O module to indicate that the virtual network function of the target network slice instance is created.
- the NSM&O module receives the virtual network function creation response information.
- the NSM&O module After receiving the virtual network function creation response information, the NSM&O module can learn that the virtual network function has been created, so the NSM&O module can configure the parameters related to the target network slice instance of the virtual network function.
- the NSM&O module sends network function configuration indication information to the EM module to indicate that the virtual network function is configured.
- the EM module may send a network function configuration response message to the NSM&O module to indicate that the virtual network function configuration is completed.
- the NSM&O module receives the network function configuration response information.
- the NSM&O module sends a network slice instance activation indication to the storage device to indicate that the target network slice instance is set to an active state.
- the NSM&O module sends a network function port activation indication to the EM module to activate the target network slice.
- the port of the network function of the instance so that the virtual network function or the port associated with the physical network function starts to send or receive data.
- the NSM&O module interacts with the storage device to store parameter information of the newly generated target network slice instance into the storage device.
- S1128 The NSM&O module sends a network slice instance creation response message to the sending end device to indicate that the network slice instance is created. This process ends.
- the parts from S1113 to S1128 are the same as or similar to the parts from S810 to S825 in FIG. 9, and a part of the description is omitted for the sake of brevity.
- a process of creating a network slice instance in a fourth network management architecture is shown, wherein the NSM&O module can flexibly arrange and manage the network function and network resources of the network slice instance, and improve the management network slice instance. effectiveness.
- the method for creating a network slice instance in multiple network management architectures of the embodiments of the present application is described above.
- the NSM&O module in the foregoing network management architecture may be either an entity module or multiple entity modules having a hierarchical structure.
- FIG. 12 shows a schematic structural diagram of an NSM&O module according to still another embodiment of the present application.
- the NSM&O module can include a multi-way NSM&O module as a general control orchestration module that can manage sub-NSM&O modules for multiple domains.
- the network slice instance creation request may be analyzed, and the entire network slice instance is divided into multiple sub-network slice instances.
- a network slice instance can be divided into a core network sub-slice instance and a Radio Access Network (RAN) sub-slice instance.
- RAN Radio Access Network
- a network slice instance may be divided into sub-network slice instances provided by a plurality of different vendor devices.
- the multi-way NSM&O module can notify each sub-NSM&O module to generate a corresponding sub-network slice instance.
- the description information of the sub-network slice instance is the same as or similar to the description information of the entire network slice instance.
- the description information may include network functions, connection relationships between network functions, KPI indices, operational parameters to be monitored, and the like. It is also possible not to include such specific information, but only to send the service requirements of the sub-network slice instance to the sub-NSM&O module, and how to generate the sub-network slice is determined by the sub-NSM&O module.
- the sub-NSM&O module can interact with the multi-way NSM&O module during the process of generating the sub-network slice instance.
- Figure 13 shows the interaction process between the multi-way NSM&O module and the sub-NSM&O module. Among them, FIG. 13 includes three sub-NSM&O modules: a first sub-NSM&O module, a second sub-NSM&O module, and a third sub-NSM&O module.
- S1301 The multi-path NSM&O module divides the network slice instance into multiple sub-network slice instances.
- the multi-path NSM&O module separately sends a sub-network slice instance creation request to multiple sub-NSM&O modules to create a corresponding sub-network slice instance.
- Multiple sub-NSM&O modules receive sub-network slice instance creation requests.
- S1303 The multiple sub-NSM&O modules send sub-network slice instance creation response information to the multi-path NSM&O module to indicate that the corresponding sub-network slice instance creation is completed.
- the NSM&O module may be a hierarchical structure, and an entire network slice instance may be divided into multiple sub-network slice instances for management, and can flexibly adapt to the characteristics of multi-domain and multi-operator in network management.
- a method for managing a network slice instance according to an embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 13, and an apparatus for managing a network slice instance according to an embodiment of the present application will be described in detail below with reference to FIG. 14 to FIG.
- FIG. 14 shows an apparatus 1400 for managing a network slice instance provided by an embodiment of the present application.
- the apparatus 1400 may be a first network device, and the apparatus 1400 includes: a processing unit 1410 and a communication unit 1420.
- the processing unit 1410 is configured to receive, by the communication unit 1420, a network slice instance creation request from a sending end device, where the network slice instance creation request is used to request to create a target network slice instance, where the network slice instance creation request includes the Descriptive information of the target network slice instance; and transmitting network function configuration indication information to the second network device by using the communication unit 1420 according to the description information, where the network function configuration indication information is used to indicate the second network device configuration a network function of the target network slice instance; and receiving, by the communication unit 1420, network function configuration response information sent by the second network device, where the network function configuration response information indicates network function configuration of the target network slice instance Completing; and transmitting, by the communication unit 1420, network slice instance creation response information to the sender device, the network slice instance creation response information indicating that the target network slice instance creation is completed.
- the first network device by instructing the second network device to perform the network function configuration of the network splicing instance, to manage the process of creating the network sharding instance, can automatically create the network sharding instance, and improve the management network slice. The efficiency of the instance.
- the apparatus 1400 herein is embodied in the form of a functional unit.
- the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
- the device 1400 may be specifically the first network device in the foregoing embodiment, and the device 1400 may be used to perform various processes corresponding to the first network device in the foregoing method embodiment. / or steps, in order to avoid repetition, will not repeat them here.
- FIG. 15 shows another apparatus 1500 for managing a network slice instance provided by an embodiment of the present application.
- the apparatus 1500 may be a second network device, where the apparatus 1500 includes: a processing unit 1510 and a communication unit 1520.
- the processing unit 1510 is configured to receive, by using the communication unit 1520, network slice configuration information that is sent by the first network device, where the network slice configuration information is used to indicate that the second network device configures a network function of the target network slice.
- the second network device performs the network function configuration of the network sharding instance by receiving the indication of the first network device, thereby managing the process of creating the network snippet instance, and implementing the automatic creation of the network sharding instance and improving Manage the efficiency of network tile instances.
- the apparatus 1500 herein is embodied in the form of a functional unit.
- the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
- ASIC application specific integrated circuit
- the device 1500 may be specifically the second network device in the foregoing embodiment, and the device 1500 may be configured to perform various processes corresponding to the second network device in the foregoing method embodiment. / or steps, in order to avoid repetition, will not repeat them here.
- FIG. 16 shows another apparatus 1600 for managing a network slice instance provided by an embodiment of the present application.
- the device 1600 can include a processing unit 1610 and a communication unit 1620.
- the processing unit 1610 is configured to receive, by the communication unit 1620, a virtual network function creation request sent by the first network device, where the virtual network function creation request is used to instruct the third network device to create a virtual network of the target network slice instance.
- the third network device by receiving the indication of the first network device, manages the process of creating the network slice instance, and can automatically create the network slice instance, and improve the efficiency of managing the network slice instance.
- the apparatus 1600 herein is embodied in the form of a functional unit.
- the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
- ASIC application specific integrated circuit
- the device 1600 may be specifically the third network device in the foregoing embodiment, where the device 1600 may be used to perform various processes corresponding to the third network device in the foregoing method embodiment. / or steps, in order to avoid repetition, will not repeat them here.
- FIG. 17 shows another apparatus 1700 for managing a network sharding instance provided by an embodiment of the present application.
- the apparatus 1700 may be a fourth network device, where the apparatus 1700 includes: a processing unit 1710 and a communication unit 1720.
- the processing unit 1710 is configured to receive, by the sum communication unit 1720, a virtual network function creation request sent by the first network device, where the virtual network function creation request is used to instruct the third network device to create a virtual network of the target network slice instance.
- Internet function ;
- the fourth network device by receiving the indication of the first network device, manages the process of creating the network slice instance, and can automatically create the network slice instance, and improve the efficiency of managing the network slice instance.
- the apparatus 1700 herein is embodied in the form of a functional unit.
- the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
- ASIC application specific integrated circuit
- the device 1700 may be specifically the fourth network device in the foregoing embodiment, where the device 1700 may be used to perform various processes corresponding to the fourth network device in the foregoing method embodiment. / or steps, in order to avoid repetition, will not repeat them here.
- FIG. 18 shows another apparatus 1800 for managing a network slice instance provided by an embodiment of the present application.
- the apparatus 1800 may be a fifth network device, where the apparatus 1800 includes: a processing unit 1810 and a communication unit 1820.
- the processing unit 1810 is configured to receive, by using the communication unit 1820, network function notification information that is sent by the first network device, where the network function notification information is used to indicate a network function that the first network device is to be configured;
- the fifth network device receives the first network device indication to the network slice instance.
- the creation process is managed to enable automatic creation of network slicing instances and improve the efficiency of managing network slicing instances.
- the device 1800 herein is embodied in the form of a functional unit.
- the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
- ASIC application specific integrated circuit
- the device 1800 may be specifically the fifth network device in the foregoing embodiment, and the device 1800 may be configured to perform various processes corresponding to the fifth network device in the foregoing method embodiment. / or steps, in order to avoid repetition, will not repeat them here.
- FIG. 19 shows another apparatus 1900 for managing a network slice instance provided by an embodiment of the present application.
- the apparatus 1900 includes a processor 1910, a communication interface 1920, a memory 1930, and a bus system 1940.
- the processor 1910, the communication interface 1920, and the memory 1930 are connected by a bus system 1940 for storing instructions.
- the processor 1910 is configured to execute instructions stored by the memory 1930 to control the communication interface 1920 to send signals and/or Or receive a signal.
- the processor 1910 is configured to receive, by using the communication interface 1920, a network slice instance creation request, where the network slice instance creation request is used to request to create a target network slice instance, where the network slice instance creation request includes the target And the network function configuration indication information is sent to the second network device by using the communication interface 1920, where the network function configuration indication information is used to indicate that the second network device configures the And a network function configuration response information sent by the second network device by using the communication interface 1920, where the network function configuration response information indicates that the network function configuration of the target network slice instance is completed; And sending the network slice instance creation response information to the sending end device by using the communication interface 1920, where the network slice instance creation response information indicates that the target network slice instance creation is completed.
- the device 1900 may be specifically the first network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the first network device in the foregoing method embodiments.
- the memory 1930 can include read only memory and random access memory and provides instructions and data to the processor.
- a portion of the memory may also include a non-volatile random access memory.
- the memory can also store information of the device type.
- the processor 1910 can be configured to execute instructions stored in a memory, and when the processor 1910 executes an instruction stored in the memory, the processor 1910 is configured to perform the steps of the method embodiment corresponding to the first network device And / or process.
- FIG. 20 shows another apparatus 2000 for managing a network slice instance provided by an embodiment of the present application.
- the device 2000 includes a processor 2010, a communication interface 2020, a memory 2030, and a bus system 2040.
- the processor 2010, the communication interface 2020, and the memory 2030 are connected by a bus system 2040.
- the memory 2030 is configured to store instructions for executing the instructions stored by the memory 2030 to control the communication interface 2020 to send signals and/or Or receive a signal.
- the processor 2010 is configured to receive the network slice configuration information sent by the first network device by using the communication interface 2020, where the network slice configuration information is used to indicate that the second network device configures a network function of the target network slice;
- the network slice configuration response information is sent to the first network device by using the communication interface 2020, where the network slice configuration response information indicates that the network function configuration corresponding to the target network slice is completed.
- the device 2000 may be specifically the second network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the second network device in the foregoing method embodiments.
- the memory 2030 can Includes read-only memory and random access memory, and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
- the memory can also store information of the device type.
- the processor 2010 can be configured to execute instructions stored in a memory, and when the processor 2010 executes an instruction stored in a memory, the processor 2010 is configured to perform the various steps of the method embodiment corresponding to the second network device And / or process.
- FIG. 21 shows another apparatus 2100 for managing a network slice instance provided by an embodiment of the present application.
- the device 2100 includes a processor 2110, a communication interface 2120, a memory 2130, and a bus system 2140.
- the processor 2110, the communication interface 2120, and the memory 2130 are connected by a bus system 2140.
- the memory 2130 is configured to store an instruction
- the processor 2110 is configured to execute the instruction stored by the memory 2130 to control the communication interface 2120 to send a signal and/or Or receive a signal.
- the processor 2110 is configured to receive, by using the communication interface 2020, a virtual network function creation request sent by the first network device, where the virtual network function creation request is used to instruct the third network device to create a virtual target network slice instance. a network function; and transmitting, by the communication interface 2020, virtual network function creation response information to the first network device, the virtual network function creation response information indicating that the virtual network function creation of the target network slice instance is completed.
- the device 2100 may be specifically the third network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the third network device in the foregoing method embodiment.
- the memory 2130 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
- the memory can also store information of the device type.
- the processor 2110 can be configured to execute instructions stored in a memory, and when the processor 2110 executes an instruction stored in the memory, the processor 2110 is configured to perform the steps of the method embodiment corresponding to the third network device And / or process.
- FIG. 22 shows another apparatus 2200 for managing a network slice instance provided by an embodiment of the present application.
- the device 2200 includes a processor 2210, a communication interface 2220, a memory 2230, and a bus system 2240.
- the processor 2210, the communication interface 2220, and the memory 2230 are connected by a bus system 2240 for storing instructions.
- the processor 2210 is configured to execute instructions stored by the memory 2230 to control the communication interface 2220 to send signals and/or Or receive a signal.
- the processor 2210 is configured to receive, by using the communication interface 2220, an allocation resource request sent by the first network device, where the allocation resource request is used to request the fourth network device to allocate a virtual network function corresponding to the target network slice instance.
- Internet resources ;
- the device 2200 may be specifically the third network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the third network device in the foregoing method embodiment.
- the memory 2230 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
- the memory can also store information of the device type.
- the processor 2210 can be configured to execute instructions stored in a memory, and when the processor 2210 executes instructions stored in the memory, the processor 2210 is configured to perform the various steps of the method embodiment corresponding to the third network device And / or process.
- FIG. 23 shows another apparatus 2300 for managing a network slice instance provided by an embodiment of the present application.
- the device 2300 includes a processor 2310, a communication interface 2320, a memory 2330, and a bus system 2340.
- the processor 2310, the communication interface 2320, and the memory 2330 are connected by a bus system 2340, where the memory 2330 is configured to store an instruction.
- the processor 2310 is configured to execute instructions stored by the memory 2330 to control the communication interface 2320 to transmit signals and/or receive signals.
- the processor 2310 is configured to receive, by using the communication interface 2320, network function notification information that is sent by the first network device, where the network function notification information is used to indicate a network function to be configured by the first network device.
- the device 2300 may be specifically the fifth network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the fifth network device in the foregoing method embodiment.
- the memory 2330 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
- the memory can also store information of the device type.
- the processor 2310 can be configured to execute instructions stored in the memory, and when the processor 2310 executes the instructions stored in the memory, the processor 2310 is configured to perform the steps of the method embodiment corresponding to the fifth network device And / or process.
- the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
- the implementation process constitutes any limitation.
- system and “network” are used interchangeably herein.
- the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
- the character "/" in this article generally indicates that the contextual object is an "or" relationship.
- B corresponding to A means that B is associated with A, and B can be determined according to A.
- determining B according to A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application. of.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
- the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
- the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请实施例提供了一种管理网络切片实例的方法、装置和系统,能够提高管理网络切片实例的效率。包括:第一网络设备从发送端设备接收网络切片实例创建请求,以请求创建目标网络切片实例,网络切片实例创建请求包含目标网络切片实例的描述信息;第一网络设备根据描述信息,向第二网络设备发送网络功能配置指示信息,以指示第二网络设备配置目标网络切片实例的网络功能;第一网络设备接收第二网络设备发送的网络功能配置响应信息,以指示目标网络切片实例的网络功能配置完成;第一网络设备向发送端设备发送网络切片实例创建响应信息,以指示目标网络切片实例创建完成。
Description
本申请要求于2016年11月03日提交中国专利局、申请号为201610974264.6、发明名称为“管理网络切片实例的方法、装置和系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信领域,尤其涉及一种管理网络切片实例的方法、装置和系统。
随着移动通信的高速发展,未来的移动通信系统需要满足多样化的业务需求,例如,增强型移动宽带,大规模机器类通信、超高可靠与低延迟的通信等。因此在下一代移动通信系统中提出了网络切片的概念。网络切片技术是指将网络在逻辑上抽象为一个或者多个网络切片,其中每个网络切片包含一系列的逻辑网络功能,一个网络切片可以满足某一类或一个用例的连接通信服务需求。下一代移动通信系统可以由满足不同连接能力的大量网络切片组成。
虽然网络功能虚拟化是降低网络切片实现复杂度和成本的关键使能技术,但是出于降低部署成本和收回投资的目的,物理网元和虚拟化的网元将长期共存并共同灵活构成网络切片。因此,为快速、灵活地提供差异化的通讯需求,运营商需要一个能够同时管理和编排物理网络功能和虚拟化网络功能的自动化切片运维系统。但是,现有技术的网络管理架构(例如,第三代合作伙伴计划(3rd Generation Partnership Project,3GPP)电信网络管理架构)不能灵活地管理和编排网络切片。
发明内容
本申请实施例提供了一种管理网络切片实例的方法、装置和系统,以期实现对对网络切片实例的管理。
第一方面,提供了一种管理网络切片实例的方法,包括如下步骤:第一网络设备从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切片实例的描述信息;所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能;所述第一网络设备接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成;所述第一网络设备向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
本申请实施例中,第一网络设备通过指示第二网络设备进行网络切片实例的网络功能
配置,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,该发送端可以是运营商、第三方客户、业务涉及的应用或服务提供商域内的任意可能给NSM&O发送请求的实体,本申请实施例对此不作限定。
在一种可能的实现方式中,所述目标网络切片实例的网络功能包括以下网络功能中的至少一种:物理网络功能和虚拟网络功能。
在本申请实施例中,网络切片实例包括的网络功能既可以是物理网络功能,也可以是虚拟网络功能,或者同时包括物理网络功能和虚拟网络功能。从而可以按需灵活地编排和管理网络切片实例的网络功能。
在一种可能的实现方式中,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述网络功能配置指示信息中包括所述目标网络切片实例的标识符。
在一种可能的实现方式中,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,还包括:所述第一网络设备向第四网络设备发送网络资源扩展指示,所述网络资源扩展指示用于指示所述第四网络设备为所述目标网络切片实例的共享网络功能分配网络资源。
在一种可能的实现方式中,还包括:所述第一网络设备向第四网络设备发送资源预留指示信息,所述资源预留指示信息用于指示所述第四网络设备为所述目标网络切片实例预留网络资源。
在一种可能的实现方式中,在所述目标网络切片实例的网络功能包括虚拟网络功能的情况下,还包括:所述第一网络设备向第三网络设备发送虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建所述目标网络切片实例的虚拟网络功能;所述第一网络设备接收所述第三网络设备发送的虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
在一种可能的实现方式中,还包括:所述第一网络设备向第四网络设备发送分配资源请求,所述分配资源请求用于请求所述第四网络设备为所述目标网络切片实例分配虚拟网络功能对应的网络资源;所述第一网络设备接收所述第四网络设备发送的分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
在一种可能的实现方式中,在所述第一网络设备接收所述第四网络设备发送的分配资源响应信息之后,还包括:所述第一网络设备向所述第三网络设备发送资源分配确认信息,所述资源分配确认信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
在一种可能的实现方式中,在所述第一网络设备向第四网络设备发送分配资源请求之前,还包括:所述第一网络设备接收所述第三网络设备发送的允许分配资源指示信息,所述允许分配资源指示信息用于指示所述第三网络设备允许为所述目标网络切片实例分配虚拟网络功能对应的网络资源。
在一种可能的实现方式中,还包括:所述第一网络设备向第五网络设备发送网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能。
在一种可能的实现方式中,还包括:所述第一网络设备接收所述第五网络设备发送的
网络功能响应信息,所述网络功能响应信息用于指示所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
在一种可能的实现方式中,还包括:所述第一网络设备向第五网络设备发送网络功能查询信息,所述网络功能查询信息用于请求查询所述第五网络设备已生成的网络功能;所述第一网络设备接收所述第五网络设备发送的网络功能反馈信息,所述网络功能反馈信息用于指示所述第五网络设备已生成的网络功能。
在一种可能的实现方式中,所述描述信息包括以下信息中的至少一种:所述目标网络切片实例的服务需求的描述信息和所述目标网络切片实例的网络切片模板的配置参数信息。
在一种可能的实现方式中,还包括:所述第一网络设备向存储设备发送合法性验证信息,所述合法性验证信息用于请求查询所述网络切片实例创建请求是否合法;所述第一网络设备接收所述存储设备发送的合法性验证响应信息,所述合法性验证响应信息用于指示所述网络切片实例创建请求是否合法;所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息,包括:在所述合法性验证响应信息指示所述网络切片实例创建请求合法的情况下,所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息。
在一种可能的实现方式中,在所述第一网络设备接收所述第二网络设备发送的网络功能配置响应信息之后,还包括:所述第一网络设备向存储设备发送网络切片实例激活指示,所述网络切片实例激活指示将所述目标网络切片实例设置为激活态。
在一种可能的实现方式中,还包括:所述第一网络设备向所述第二网络设备发送网络功能端口激活指示,所述网络功能端口激活指示用于激活所述目标网络切片实例的网络功能的端口。
在一种可能的实现方式中,还包括:所述第一网络设备向存储设备发送更新网络切片实例指示,所述更新网络切片实例指示用于指示将所述目标网络切片实例的参数信息存入所述存储设备。
第二方面,提供了另一种管理网络切片实例的方法,包括:第二网络设备接收第一网络设备发送的网络切片配置信息,所述网络切片配置信息用于指示所述第二网络设备配置目标网络切片的网络功能;所述第二网络设备向所述第一网络设备发送网络切片配置响应信息,所述网络切片配置响应信息指示所述目标网络切片对应的网络功能配置完成。
在本申请实施例中,第二网络设备通过接收第一网络设备的指示,进行网络切片实例的网络功能配置,从而对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
在一种可能的实现方式中,所述目标网络切片的网络功能包括以下网络功能中的至少一种:物理网络功能和虚拟网络功能。
在一种可能的实现方式中,还包括:所述第二网络设备接收所述第一网络设备发送的网络功能端口激活指示,所述网络功能端口激活指示用于指示激活所述目标网络切片实例的网络功能的端口。
在一种可能的实现方式中,还包括:所述第二网络设备接收第三网络设备发送的添加虚拟网络功能请求,所述添加虚拟网络功能请求用于请求添加所述目标网络切片实例的虚
拟网络功能。
第三方面,提供了一种管理网络切片实例的方法,包括:第三网络设备接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;第三网络设备向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
在本申请实施例中,第三网络设备通过接收第一网络设备指示,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
在一种可能的实现方式中,还包括:所述第三网络设备向所述第一网络设备发送允许分配资源指示信息,所述允许分配资源指示信息用于指示所述第三网络设备允许为所述目标网络切片实施分配虚拟网络功能对应的网络资源。
在一种可能的实现方式中,还包括:所述第三网络设备接收所述第一网络设备发送的资源分配确认信息,所述资源分配确认信息用于指示所述目标网络切片实例的虚拟网络功能的网络资源分配完成。
在一种可能的实现方式中,在所述第三网络设备接收所述第一网络设备发送的资源分配确认信息之后,还包括:所述第三网络设备向第二网络设备发送添加虚拟网络功能请求,所述添加虚拟网络功能请求用于请求添加所述目标网络切片实例的虚拟网络功能。
第四方面,提供了另一种管理网络切片实例的方法,包括:第四网络设备接收第一网络设备发送的分配资源请求,所述分配资源请求用于请求所述第四网络设备为目标网络切片实例分配虚拟网络功能对应的网络资源;所述第四网络设备向所述第一网络设备发送分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
在本申请实施例中,第四网络设备通过接收第一网络设备指示,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
在一种可能的实现方式中,还包括:所述第四网络设备接收所述第一网络设备发送的网络资源扩展指示,所述网络资源扩展指示用于指示所述第四网络设备为所述目标网络切片实例的共享网络功能分配网络资源。
在一种可能的实现方式中,还包括:所述第四网络设备接收所述第一网络设备发送的资源预留指示信息,所述资源预留指示信息用于指示所述第四网络设备为所述目标网络切片实例预留网络资源。
第五方面,提供了另一种管理网络切片实例的方法,包括:第五网络设备接收第一网络设备发送的网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;所述第五网络设备向所述第一网络设备发送网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
在本申请实施例中,第五网络设备通过接收第一网络设备指示,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
在一种可能的实现方式中,还包括:所述第五网络设备接收所述第一网络设备发送的网络功能查询信息,所述网络功能查询信息用于请求查询所述第五网络设备已生成的网络
功能;所述第五网络设备向所述第一网络设备发送网络功能反馈信息,所述网络功能反馈信息用于指示所述第五网络设备已生成的网络功能。
第六方面,提供了一种管理网络切片实例的装置,用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地,该装置包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第七方面,提供了另一种管理网络切片实例的装置,用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地,该装置包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第八方面,提供了另一种管理网络切片实例的装置,用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。具体地,该装置包括用于执行上述第三方面或第三方面的任意可能的实现方式中的方法的单元。
第九方面,提供了另一种管理网络切片实例的装置,用于执行上述第四方面或第四方面的任意可能的实现方式中的方法。具体地,该装置包括用于执行上述第四方面或第四方面的任意可能的实现方式中的方法的单元。
第十方面,提供了另一种管理网络切片实例的装置,用于执行上述第五方面或第五方面的任意可能的实现方式中的方法。具体地,该装置包括用于执行上述第五方面或第五方面的任意可能的实现方式中的方法的单元。
第十一方面,提供了一种管理网络切片实例的装置,该装置包括:通信接口、存储器、处理器和总线系统。其中,该通信接口、该存储器和该处理器通过该总线系统相连,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第十二方面,提供了一种管理网络切片实例的装置,该装置包括:通信接口、存储器、处理器和总线系统。其中,该通信接口、该存储器和该处理器通过该总线系统相连,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第十三方面,提供了一种管理网络切片实例的装置,该装置包括:通信接口、存储器、处理器和总线系统。其中,该通信接口、该存储器和该处理器通过该总线系统相连,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第三方面或第三方面的任意可能的实现方式中的方法。
第十四方面,提供了一种管理网络切片实例的装置,该装置包括:通信接口、存储器、处理器和总线系统。其中,该通信接口、该存储器和该处理器通过该总线系统相连,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第四方面或第四方面的任意可能的实现方式中的方法。
第十五方面,提供了一种管理网络切片实例的装置,该装置包括:通信接口、存储器、处理器和总线系统。其中,该通信接口、该存储器和该处理器通过该总线系统相连,该存
储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第五方面或第五方面的任意可能的实现方式中的方法。
第十六方面,提供了一种管理网络切片实例的系统,该系统包括第六方面或第六方面中的任一种可能实现方式中的装置、第七方面或第七方面中的任一种可能实现方式中的装置以及第八方面或第八方面中的任一种可能实现方式中的装置、上述第九方面或第九方面的任一种可能实现方式中的装置、上述第十方面或第十方面的任一种可能实现方式中的装置;或者
该系统包括第十一方面或第十一方面中的任一种可能实现方式中的装置以及第十二方面或第十二方面中的任一种可能实现方式中的装置、上述第十三方面或第十三方面的任一种可能实现方式中的装置、第十四方面或第十四方面的任一种可能实现方式中的装置、第十五方面或第十五方面的任一种可能实现方式中的装置。
第十七方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十八方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十九方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。
第二十方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第四方面或第四方面的任意可能的实现方式中的方法的指令。
第二十一方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第四方面或第四方面的任意可能的实现方式中的方法的指令。
图1是本申请实施例的网络管理架构的示意图。
图2是本申请实施例NSM&O的架构图。
图3是本申请实施例应用的网络管理架构的示意图。
图4是本申请实施例应用的另一网络管理架构的示意图。
图5是本申请实施例应用的另一网络管理架构的示意图。
图6是本申请实施例应用的另一网络管理架构的示意图。
图7是本申请实施例提供的管理网络切片实例的方法的示意性流程图。
图8是本申请实施例提供的另一管理网络切片实例的方法的示意性流程图。
图9是本申请实施例提供的另一管理网络切片实例的方法的示意性流程图。
图10是本申请实施例提供的另一管理网络切片实例的方法的示意性流程图。
图11是本申请实施例提供的另一管理网络切片实例的方法的示意性流程图。
图12是本申请实施例提供的NSM&O的层次结构图。
图13是本申请实施例提供的应用于NSM&O的示意性流程图。
图14是本申请实施例提供的管理网络切片实例的装置的示意性框图。
图15是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图16是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图17是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图18是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图19是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图20是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图21是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图22是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
图23是本申请实施例提供的另一管理网络切片实例的装置的示意性框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。
应理解,本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、LTE频分双工(Frequency Division Duplex,FDD)系统、LTE时分双工(Time Division Duplex,TDD)、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)或全球互联微波接入(Worldwide Interoperability for Microwave Access,WiMAX)通信系统等。
本申请实施例涉及网络切片技术。网络切片技术是将网络在逻辑上抽象为一个或者多个网络切片,其中每个网络切片包含一系列的逻辑网络功能,针对性地满足不同业务类型的差异化需求。例如在第五代移动通信(The 5th Generation,5G)网络中,网络切片是一种按需组网的方式,为运营商带来能根据不断变化的用户需求进行调整,并快速满足新型应用需求的新服务。
网络切片技术将5G网络物理基础设施资源根据场景需求抽象为多个网络切片。每个网络切片按照业务场景的需要和业务模型进行网络功能的定制裁剪及相应网络功能的编排管理。一个网络切片可以视为一个实例化的5G网络。这样的网络结构允许运营商将网络作为一种服务提供给用户,并可以根据速率、容量、覆盖性、延迟、可靠性、安全性和可用性等指标对实体网络进行自由组合,从而满足不同用户的要求。
需要说明的是,本文中的术语“网络管理架构”“网络系统”、“系统”等可以互相替换。为了便于理解,先介绍本文中出现的一些术语:
网络切片:网络切片是一个概念,指在物理或者虚拟的网络基础设施之上,根据不同的服务需求定制化不同的逻辑网络。
网络切片实例:是一个真实运行的逻辑网络。
网络切片模板:是指生成网络切片实例的一种方式,用于给生成网络切片实例提供一个参考。网络切片模板规定了网络切片实例应该如何生成。例如,网络切片模块可以指示网络切片包含哪些网络功能,应达到的关键绩效指标(Key Performance Indicators,KPI)指标等。
网络功能:是网络中的一种处理功能,定义了功能性的行为和接口,网络功能可以在
作为一个专用硬件,也可以在一个专用硬件上运行软件实现,也可以在通用的硬件平台上以虚拟功能的形式实现。因此,从实现的角度,可以将网络功能分为物理网络功能和虚拟网络功能。而从使用的角度,网络功能可以分为专属网络功能和共享网络功能,具体地,对于多个网络切片实例而言,可以独立地使用不同的网络功能,这种网络功能称为专属网络功能,也可以共享同一个网络功能,这种网络功能称为共享网络功能。
为了便于理解本申请实施例,首先介绍图1的网络管理架构。图1示出了一种网络管理架构100。作为一个示例,图1的网络管理架构100可以是融合了网络功能虚拟化(Network function virtualized,NFV)管理与编排(Management and orchestration,MANO)模块的3GPP公共陆地移动网络(Public Land Mobile Network,PLMN)网络管理架构。具体而言,网络管理架构100同时包含了管理物理网络功能和虚拟网络功能的模块。下面依次介绍网络管理架构100中的模块。
物理网络功能(Physical network function,PNF)模块:是一个物理设备提供固定的网络功能。例如,物理网络功能模块可以是传统的3GPP网络管理架构中的网元(Network element,NE),也就是说一个物理网元。例如,NE可以是基站、移动管理实体(Mobility management entity,MME)或服务网关(Serving Gateway,简称为“SGW”)等。
虚拟网络功能(Virtualized network function,VNF)模块:可以是网络管理架构中可以监视和管理的最小虚拟单位。VFN与下文所述的NFVI模块之间存在通信接口。VNF模块可以在NFVI的基础上,创建虚拟网络功能并做一些参数配置,实现某一个网络功能。
网元管理器(Element manager,EM):用于管理网元的网络模块。EM即可以用于管理物理网络功能(即PNF模块),也可以用于管理虚拟网络功能(即VNF模块)。网络管理架构中可以包括一个EM模块,也可以包括多个EM模块。在EM模块为多个EM模块的情况下,多个EM模块中的每个EM模块用于管理对应的虚拟网络功能或物理网络功能,或者单个EM模块也可以同时管理对应的虚拟网络功能和物理网络功能。
域管理器(Domain manager,DM):比EM的管理范围更大一级的管理系统模块。DM可以管理一个或多个EM。例如,DM可以是厂商的管理系统。
需要说明的是,EM和DM在定义上是不同的,EM是直接管理同一类型的网络设备,比如EM管理一系列的基站,DM是管理一个属于运营商(vendor)的网络设备,提供域管理功能的,DM比EM的管理范围更大。通常情况下,EM设备用于执行网络功能的配置。但本申请实施例中不排除DM执行EM所执行的流程的可能性。
网络管理器(Network manager,NM):是网络层面的管理模块。主要提供网络管理功能、管理设备之间的交换等相关功能。例如,NM可以负责网络资源的分布、配置、控制和监控等。NM由EM或DM提供支持。
网络功能虚拟基础设施(Network function virtualized infrastructure,NFVI)模块:用于对虚拟网络功能(即VNF)进行部署,其可以是一组由软件和硬件组成的运行环境,包括虚拟层和抽象硬件资源等。
NFV-MANO系统模块:其与NFVI模块、VNF模块、EM模块以及NM模块之间存在接口,以用于在网络层面管理虚拟网络功能,包含了以下三个模块:
网络功能虚拟化编排(Network function virtualization orchestrator,NFVO)模块:用于进行网络服务、VNF的生命周期管理,并从NFVI全局的角度优化网络资源。
虚拟网络功能管理模块(Virtualized network function manager,VNFM)模块:用于在网络层面管理VNF模块。
虚拟基础设施管理器(Virtualized infrastructure manager,VIM):与NFVI、VNF之间存在接口,用于管理NFVI的计算、存储以及网络资源的分配等。
由上述对网络管理架构100的介绍可知,网络管理架构100虽然能够对物理网络功能和虚拟网络功能进行管理。但是其并不能够进行网络切片的管理和编排。所以网络管理架构100不能满足未来通信系统中的网络切片技术应用的需求,即不能灵活地管理和编排网络切片。
出于降低部署成本等考虑,物理网元和虚拟化网元将长期共存并灵活构成网络切片。因此,需要一种网络管理系统,能够实现对物理和虚拟的网络功能或网络资源进行编排和管理,以实现网络切片的应用。
本申请实施例提供了一种管理网络切片实例的方法、装置和系统。其中心思想是在网络管理架构中引入网络切片管理与编排(Network slice manager and orchestrator,NSM&O)模块,并通过NSM&O模块对网络切片实例的创建过程进行管理,以实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
下文介绍本申请实施例的网络管理架构。本申请实施例在现有的网络管理架构的基础上,引入了NSM&O模块。其中NSM&O模块的结构示意图如图2所示,其主要功能包括:
服务转换:通过接口(例如,可以是应用程序编程接口(Application Programming Interface,API))接收发送端设备发送的服务描述信息,并将服务描述信息转换为对网络的需求。
网络切片设计:根据服务转换的结果,描述网络切片的组成。例如,可以是设计网络切片模板(Network Slice Descriptor,NSLD)。
网络切片管理策略:设计网络切片的管理策略。例如,可以是网络切片实例化、网络切片缩放、网络切片更新、网络切片终结、网络切片删除等策略。
网络切片编排:用于具体确定网络切片实例所包含的网络功能和使用的网络资源。
监测:用于检测和报告网络切片实例的状态参数。例如,可以监测网络切片实例的关键绩效指标(Key Performance Indicators,KPI)参数。
上述发送端设备也可以称为sender(英文)。发送端设备是向NSM&O模块发送请求的设备。例如,发送端设备可以是运营商、第三方客户、通信业务涉及的应用或其他任意可能向NSM&O模块发送请求的实体设备。
可选地,本申请实施例中的网络管理架构中还可以包括存储设备,存储设备可以用于记录已生成的网络切片实例的信息。
为了更好地理解本申请实施例中的网络管理架构。下文将结合图3至图6,介绍本申请实施例中的网络管理架构的具体示例。本领域技术人员能够理解,图3至图6的例子仅仅是为了帮助本领域技术人员理解本申请实施例,而非要将本申请实施例限于所例示的具体数值或具体场景。本领域技术人员根据所给出的图3至图6的例子,显然可以进行各种等价的修改或变化,这样的修改或变化也落入本申请实施例的范围内。
图3至图6分别介绍了本申请实施例的四种网络管理架构。该四种网络管理架构中都
包括NSM&O模块。为了方便区分,下文将图3至图6的网络管理架构依次称为第一网络管理架构、第二网络管理架构、第三网络管理架构和第四网络管理架构。
图3示出了第一网络管理架构的结构示意图。如图3所示,第一网络管理架构是在网络管理架构100基础上进行增强和修改得到的网络管理架构。其中,第一网络管理架构并不包含NM模块,而是由NSM&O模块执行网络管理架构100中NM模块执行的功能。换句话说,NSM&O模块除包含图2所示的功能之外,还可以包含NM模块的全部功能。NSM&O模块可以通过通信接口与EM进行交互,以实现对网络切片实例对应的网络功能的管理。其中,对网络功能的管理包括对PNF模块和对VNF模块的管理。NSM&O模块还可以通过通信接口从NFVO模块接收VNF模块的状态信息,以及通过通信接口向NFVO发送指令。
对于第一网络管理架构,NSM&O模块能够直接管理物理网络功能,并可以利用NFVO模块实现对NFVI模块的资源编排管理以及实现VNF的生成。
图4是本申请实施例的第二网络管理架构的结构示意图。如图4所示,第二网络管理架构也是在网络管理架构100的基础上进行增强和修改得到的网络管理架构。其中,第二网络管理架构与第一网络管理架构的不同之处在于:第二网络管理架构中不包含NFVO模块的实体。NFVO模块的功能由NSM&O模块实现。换句话说,NSM&O模块的功能还包括虚拟网络资源的编排管理以及VNF生命周期管理。NSM&O模块与VNFM模块之间存在通信接口。在图4中,该接口可以称为NG1接口。NSM&O模块与VIM模块之间存在通信接口。在图4中,该接口可以称为NG2接口。
其中,NSM&O模块与VNFM模块可以通过NG1接口进行以下交互:支持VNF所做的NFVI资源的授权、预留、分配和释放等;查询运行态的信息,例如VNF实例查询;VNF初始化更新、缩放、终结等;传输VNF有关的事件、状态信息等。
NSM&O模块与VIM模块可以通过NG2接口进行以下交互:NFVI资源预留、分配、释放等;VNF软件映像(image)增加、删除、更新等;传输与NFVI相关的配置信息、事件、测量结果、升级记录等。
对于第二网络管理架构,NSM&O模块除了能够直接管理物理网络功能之外,还可以对虚拟网络功能以及VNF生命周期进行管理。从而能够统一地管理和编排物理、虚拟网络资源和功能,利于从全局化的角度优化资源。
图5是本申请实施例的第三网络管理架构的结构示意图。如图5所示,在第三网络管理架构中保留了NM模块,NSM&O模块与NM模块相互独立。并且,NSM&O模块与NM模块之间存在通信接口。在图5中,该通信接口可以称为NG3接口。NSM&O模块与NFVO模块之间也存在通信接口。在图5中,该通信接口可以称为NG4接口。NSM&O模块与EM模块之间也存在通信接口。在图5中,该通信接口可以称为NG5接口。
其中,NSM&O模块与NM模块可以通过NG3接口进行以下交互:传输NSM&O模块和NM模块之间的协商信息,例如如NSM&O模块查询NM模块已生成的VNF;NM模块向NSM&O模块反馈已生成的VNF信息,并确认允许NSM&O模块修改VNF信息;NSM&O模块通知NM模块将要对哪些PNF/VNF进行修改;NSM&O模块通知NM模块针对PNF/VNF的具体修改内容。
NSM&O模块与NFVO模块之间可以通过NG4接口进行以下交互:NSM&O模块通
过NG4接口参与VNF的生命周期管理,例如通知NFVO模块生成、更新、删除一个VNF等;NSM&O模块向NFVO模块查询VNF、NFVI的运行信息;NFVO模块向NSM&O模块反馈VNF、NFVI的运行信息;策略管理,NSM&O模块可以向NFVO模块发送策略,指出对VNF部署的需求;NSM&O模块通过NG4接口进行VNF包(package)管理。
NSM&O模块和EM模块之间可以通过NG5接口进行以下交互:NSM&O模块通过NG5接口与EM模块进行通信,以管理PNF和VNF(若EM支持对VNF的管理)。
对于第三网络管理架构,NSM&O模块采用了新的通信接口与第三网络管理架构中的各实体模块进行交互。NSM&O模块可以通过NFVO模块编排和管理虚拟资源以及参与VNF的生命周期管理NSM&O模块和NM模块都可以直接管理PNF。并且NSM&O模块和NM模块都可以通过NFVO模块或EM模块管理VNF。因此,对于PNF和VNF的管理,NSM&O模块和NM模块之间可以通过通信进行协调。
图6是本申请实施例的第四网络管理架构的结构示意图。如图6所示,第四网络管理架构中也保留了NM模块。NSM&O模块与NM模块也是相互独立的。第四网络管理架构与第三网络管理架构的不同之处在于:第四网络管理架构中不包含NFVO模块的实体。NFVO模块的功能由NSM&O模块实现。换句话说,NSM&O模块的功能还包括虚拟网络资源的编排管理以及VNF生命周期管理。其中,NSM&O模块与VNFM模块之间存在通信接口。在图6中,该通信接口可以称为NG1接口。NSM&O模块与VIM模块之间存在通信接口。在图6中,该通信接口可以称为NG2接口。NSM&O模块与EM模块之间存在通信接口。在图6中,该通信接口可以称为NG5接口。关于NG1接口、NG2接口以及NG5接口的具体功能可以参见图4和图5中的相同或相似的内容。为了简洁,此处不再赘述。
对于第四网络管理架构,NSM&O模块采用了新的通信接口与第四网络管理架构中的各实体模块进行交互。NSM&O模块可以通过NFVO模块编排和管理虚拟资源以及参与VNF的生命周期管理NSM&O模块和NM模块都可以直接管理PNF。因此,对于PNF的管理,NSM&O模块和NM模块之间可以通过通信进行协调。并且由于NSM&O模块合并了NSFO模块的功能,所以NSM&O模块还可以直接编排管理虚拟网络资源和参与VNF的生命周期管理。NM模块则不管理虚拟网络资源和VNF。
上文结合图1至图6,介绍了本发实施例的网络管理架构。下文将结合示图,介绍本申请实施例的管理网络切片实例的方法,该管理网络切片实例的方法可以应用于本申请实施例中的第一网络管理架构至第四网络管理架构。或者,该管理网络切片实例的方法也可以应用于其他类似的网络管理架构中,本申请实施例对此不作限制。在下文所述的管理的网络切片实例的方法中,第一网络设备可以为本申请实施例中的网络管理架构中的NSM&O模块,第二网络设备可以为网络管理架构中的EM模块,第三网络设备可以为网络管理架构中的VNFM模块或NFVO模块,第四网络设备可以为网络管理架构中的VIM模块,第五网络设备可以为网络管理架构中的NM模块。或者,上述第一网络设备至第五网络设备也可以为网络管理架构中具有相应功能的其他实体装置,本申请实施例对此不作限制。
图7示出了本申请实施例的管理网络切片实例的方法700,该方法700包括:
S701,第一网络设备从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切
片实例的描述信息。
可选地,在接收到网络切片实例创建请求之后,需要根据目标网络切片实例的描述信息,对目标网络切片实例对应的网络切片进行设计。网络切片设计的方式包括至少两种。其中一种方式是可以预先设置网络切片模板,该网络切片模板可以是根据不同业务类型设计的。换句话说,多种业务类型可以存在多种网络切片模板。第一网络设备可以根据网络切片实例的描述信息,确定对应的网络切片模板以及网络切片模板的配置参数。或者,第一网络设备也可以根据网络切片实例的描述信息,在网络切片模板的基础上进行修改,以设计网络切片实例对应的网络切片的网络功能;在网络切片设计的另一种方式中,也可以不预先设置网络切片模板,第一网络设备根据网络切片实例的描述信息,直接设计网络切片的网络功能。
可选地,上述描述信息可以包括以下信息中的至少一种:目标网络切片实例的服务需求的描述信息和目标网络切片实例的网络切片模板的配置参数信息。
其中,在目标网络切片实例的描述信息为服务需求的描述信息的情况下,第一网络设备可以根据服务需求的描述信息,将其转换为目标网络切片实例对网络的需求。并根据网络需求,设计网络切片。例如,直接描述目标网络切片实例的组成。或者,根据网络需求,确定目标网络切片实例对应的网络切片模板的配置参数信息。例如,服务需求的描述信息可以是满足一定KPI需求的移动宽带(Mobile Broadband,MBB)/超可靠低延时通信(Ultra-reliable low-latency communication,URLLC)/机器类型通信(Machine Type communication,MTC)业务。
在目标网络切片实例的描述信息为网络切片模板的配置参数信息的情况下,可以根据目标网络切片实例的描述信息,确定网络切片模板的配置参数信息,进而完成对目标网络切片实例的设计。其中,网络切片模板的配置参数信息可以是网络切片模板的输入参数。作为一个具体实例,例如,NSM&O模块中已经存在一个MTC业务的网络切片模板,发送端设备可以根据网络切片目标所开放的可配置参数,在网络切片实例创建请求中的描述信息中描述所需的MTC业务的网络切片实例的配置参数信息。例如,配置参数信息可以包括连接数等信息。
S702,所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能。
可选地,上述网络功能可以包括物理网络功能和虚拟网络功能中的至少一种。
在本申请实施例中,网络切片实例包括的网络功能既可以是物理网络功能,也可以是虚拟网络功能,或者同时包括物理网络功能和虚拟网络功能。从而可以按需灵活地编排和管理网络切片实例的网络功能。例如在虚拟网络功能无法支持某种网络功能时,可以选择一个物理网元,实现该网络功能。
可选地,在本申请实施例中,网络切片实例所包含的网络功能既可以是共享网络功能,也可以是专属网络功能。其中,共享网络功能是指可以由多个网络切片实例共同使用的网络功能。专属网络功能可以是由单独的网络切片实例使用的网络功能。例如,可以创建多个网络切片实例,上述多个网络切片实例可以同时使用若干共享网络功能,每个网络切片实例又可以包含只被它自己使用的专属网络功能。
可选地,在本申请实施例中,对网络切片实例配置的包括多种情况。第一种情况是,网络切片实例的网络功能是专属网络功能,且网络功能是物理网络功能;第二种情况是网络切片实例的网络功能是专属网络功能,且网络功能是虚拟网络功能。第三种情况是网络切片实施例的网络功能是可共享的网络功能。其中,可共享的网络功能是指该网络功能是可以被多个网络切片实例共享的,可共享的网络功能又包含两种情况:一种情况是网络功能正在被多个网络切片实例共享了,一种情况是目前只有一个网络切片实例在使用,即当前仍是专属网络功能,但是未来可以被其它网络切片实例共享。。可共享的网络功能既可以是物理网络功能也可以是虚拟网络功能。
在第三种情况中,还存在两个分支,第一分支是该可共享的网络功能未开始运行,第二分支是该可共享的网络功能已经开始运行。或者说,该可共享的网络功能已经被其他网络切片实例使用。下文将针对这三种情况,对网络切片实例配置的过程进行说明。
在第一种情况中,即网络功能包含专属的物理网络功能的情况下,由于PNF模块是物理网元,PNF模块是真实存在的模块,不存在生成PNF模块的概念。因此仅需要第二网络设备对目标网络切片实例的物理网络功能进行配置,以使配置的物理网络功能服务于目标网络切片实例。
在第二种情况中,即网络功能包含专属的虚拟网络功能的情况下,VNF模块是执行虚拟网络功能的模块,所以第一网络设备需要确定目标网络切片实例对应的VNF模块是否已经创建或生成。其中,在本申请实施例中,第三网络设备模块负责创建或生成VNF模块。在VNF模块已经生成的情况下,第一网络设备可以直接指示第二网络设备对VNF模块进行配置相应的虚拟网络功能。在VNF模块未生成的情况下,第一网络设备可以指示第三网络设备生成VNF模块。然后指示第二网络设备对生成的VNF模块进行相应的虚拟网络功能配置。
在第三种情况的第一分支中,即可共享的网络功能未开始运行的情况下,或者说该共享网络功能还未被配置的情况下,第一网络设备可以指示第二网络设备配置共享网络功能,该共享网络功能可以是物理网络功能或虚拟网络功能。对该共享网络功能的配置方式与上述对专属网络功能的配置方式相同或相似。例如,对于未生成的共享的虚拟网络功能,可以新创建虚拟网络功能,以支持新的网络切片实例。
应理解,由于该共享网络功能当前只服务于新创建的网络切片实例,并未被其他网络切片实例共享,所以当前该共享网络功能和专属网络功能类似,只服务于单个网络切片实例。但是,该共享网络功能未来可以被其他网络切片实例共享。即未来可以对该共享网络功能进行配置,使其可以同时服务于其他网络切片实例。例如,可以对该配置的共享网络功能进行标识,该标识用于指示该共享网络功能当前服务于目标网络切片实例,但未来可以与其他网络切片实例共享该网络功能。
在第三种情况的第二分支中,即可共享的网络功能已开始运行的情况下,或者说该可共享的网络功能已经被其他网络切片实例使用的情况下。第一网络设备需要指示第二网络设备配置共享网络功能,以使目标网络切片实例可以与其他网络切片实例共享网络功能。可选地,该正在运行的可共享的网络功能可以是已经被一个网络切片实例使用的网络功能,也可以是已经被多个网络切片实例使用的功能。在该可共享的网络功能已经被一个网络切片实例使用的网络功能的情况下,该可共享的网络功能在初始状态时可以是专属网络
功能,可以对该专属网络功能进行重配置使其成为共享网络功能。可选地,第一网络设备可以与第三网络设备、第四网络设备进行交互,协同配置共享网络功能。
例如,在多个网络切片实例共享网络资源的情况下,共享网络功能对应的网络资源可能需要扩展,以支持新生成的网络切片实例。因此,第一网络设备可以向第四网络设备发送网络资源扩展指示,该网络资源扩展指示用于指示第四网络设备为目标网络切片实例的共享网络功能分配网络资源。
可选地,上述网络功能配置指示信息包含配置目标网络切片实例的网络功能所需的配置信息。例如,上述配置信息可以包括但不局限于:网络切片实例的相关参数:网络切片实例的标识、网络切片实例的类型以及其他需要监测和上报的参数。另外,除了与网络切片实例的相关参数外,还包括传统的运行参数,例如移动管理实体码(Mobility Management Entity Code,MMEC)、MME池(Pool)等。
需要说明的是,当网络切片实例的网络功能包括共享网络功能的情况下,可选地,网络功能配置指示信息还可以包括网络切片实例所包含的共享网络功能的信息或者共享网络功能的其他网络切片实例的配置信息。例如,在共享网络功能为非接入层(Non-access Stratum,NAS)消息路由(routing)网络功能的情况下,需要获取共享网络功能的网络切片实例的配置信息,以便于确定如何将NAS信息路由至对应的网络切片实例。
可选地,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述网络功能配置指示信息中可以包括所述目标网络切片实例的标识符。
可选地,与专属网络功能相比,网络功能配置指示信息中对共享网络功能的配置包含很多种情况。例如,若新创建的网络切片实例将要使用一个已存在的、正在被其他网络切片实例使用的共享网络功能。此时需要配置的内容包括:a).提供信息,使得该共享网络功能能够服务于新生成的网络切片实例。以“网络切片选择功能”为例,如果该功能是共享网络功能,则该新生成的网络切片实例需要感知其他共享网络功能的网络切片实例的存在,才能够选择合适的网络切片实例。因此,对于“网络切片选择功能”或其他网络功能,需要为其配置新生成的目标网络切片实例的标识符。
可选地,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述网络功能配置指示信息中可以包括指示所述共享网络功能与共享网络功能的多个网络切片实例的映射关系。
在一个具体示例中,以NAS消息路由功能为例,该功能在通常情况下可以为共享网络功能。该功能主要用于将移动性管理(Mobility Management,MM)功能接收到的NAS消息转发至正确的网络切片实例对应的会话管理(Session Management)功能当中。上述功能的路径为MM功能(共享)->NAS路由功能(共享)->SM功能(专属)。因此NAS路由功能需要知道新生成的网络切片实例标识符到SM功能标识符之间的映射关系。或者说,需要在网络切片实例中配置NAS路由功能到多个网络切片实例的SM功能之间的映射关系。该配置通常处于与专属网络功能的交界的共享网络功能中,以使共享网络功能能够将消息传输至多个网络切片实例中的正确网络切片实例中。
可选地,在一个具体示例中,由于共享网络功能将要服务于新生成的网络切片实例,可能需要更强大的处理能力。因此,需要为该共享网络功能增加更多的计算资源、存储资源或网络资源。例如,对于可以共享的网络功能MM功能来说,其主要功能是需要跟踪
切片内用户的位置,因此当MM支持更多的网络切片实例时,可能需要更多的计算和存储资源。
S703,所述第一网络设备接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成。
在第二网络设备配置目标网络切片实例的网络功能完成之后,第一网络设备将接收第二网络设备发送的网络功能配置响应信息,以指示第二网络设备配置目标网络切片实例的网络功能的结果。
可选地,若第二网络设备配置目标网络切片实例的网络功能失败,该网络功能配置响应信息也可以指示目标网络切片实例的网络功能配置失败,以便于第一网络设备重新制定目标网络切片实例的管理和编排策略。
S704,所述第一网络设备向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
可选地,在本申请实施例中,在接收第二网络设备发送的网络功能配置响应信息之后,第一网络设备可以向发送端设备发送网络切片实例创建响应信息,以指示网络切片实例创建的结果。可选地,在目标网络切片实例的网络功能配置完成的情况下,网络切片实例创建响应信息向发送端设备指示网络切片实例创建成功;在目标网络切片实例的网络功能配置失败的情况下,网络切片实例创建响应信息可以向发送端设备指示网络切片实例创建失败。
在本申请实施例中,第一网络设备通过指示第二网络设备进行网络切片实例的网络功能配置,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
可选地,在所述目标网络切片实例的网络功能包括虚拟网络功能的情况下,并且该目标网络切片实例的虚拟网络功能未创建的情况下,方法700还包括:所述第一网络设备向第三网络设备发送虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建所述目标网络切片实例的虚拟网络功能。
其中,上述第三网络设备可以是第二网络管理架构中或第四网络管理架构中的VNFM模块,也可以是第一网络管理架构或第三网络管理架构中的NVFO模块。
可选地,在创建虚拟网络功能的情况下,需要第四网络设备为该虚拟网络功能分配对应的网络资源。第四网络设备可以从NVFO模块接收分配资源请求,并分配相应的网络资源。作为一个示例,在第三网络设备为NVFO模块的情况下,第三网络设备可以向第四网络设备发送分配资源请求,以请求第四网络设备为目标网络切片实例分配虚拟网络功能对应的网络资源。
可选地,在第三网络设备为VNFM模块的情况下,则第一网络设备还包含了NVFO模块的功能,所以由第一网络设备向第四网络设备发送分配资源请求。因此方法700还包括:第一网络设备向第四网络设备发送分配资源请求,所述分配资源请求用于请求所述第四网络设备为所述目标网络切片实例分配虚拟网络功能对应的网络资源。
可选地,在第一网络设备向第四网络设备发送分配资源请求之后,方法700还包括:所述第一网络设备接收所述第四网络设备发送的分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。该分配资源
响应信息可以用于指示目标网络切片实例的虚拟网络功能对应的网络资源的分配结果。可选地,若第四网络设备为完成网络资源的分配,该分配资源响应信息可以指示目标网络切片实例的虚拟网络功能对应的网络资源分配失败。
可选地,在第三网络设备配置目标网络切片的虚拟网络功能之后,方法700还包括:所述第一网络设备接收所述第三网络设备发送的虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。可选地,上述虚拟网络功能创建响应信息可以用于指示目标网络切片的虚拟网络功能创建的结果。可选地,在第三网络设备创建虚拟网络功能失败的情况下,该虚拟网络功能创建响应信息可以指示该目标网络切片实例的虚拟网络功能创建失败。
可选地,在所述第一网络设备接收所述第四网络设备发送的分配资源响应信息之后,方法700还包括:所述第一网络设备向所述第三网络设备发送资源分配确认信息,所述资源分配确认信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。第一网络设备向第四网络设备发送资源分配确认信息,以便于第三网络设备在确定网络资源分配完成之后,对目标网络切片实例的虚拟网络功能进行配置。
可选地,第三网络设备在虚拟网络功能配置完成之后,以及在向第一网络设备发送上述虚拟网络功能配置响应信息之前,可以向第二网络设备发送添加虚拟网络功能模块请求,以将所生成的虚拟网络功能模块添加为第二网络设备的管理设备。
可选地,在第三网络管理架构或第四网络管理架构中,NSM&O模块与NM模块都可以配置网络功能。所以NSM&O模块与NM模块之间可以对网络功能配置的状态进行交互,以便于对网络功能配置进行协调。因此,方法700还包括:第一网络设备向第五网络设备发送网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能。从而第一网络设备和第五网络设备之间可以对网络功能配置进行协调,提高了管理网络切片的效率。上述将要配置的网络功能可以包括物理网络功能,也可以包括虚拟网络功能。
可选地,方法700还包括:所述第一网络设备接收所述第五网络设备发送的网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
可选地,方法700还包括:所述第一网络设备向第五网络设备发送网络功能查询信息,所述网络功能查询信息用于请求查询所述第五网络设备已生成的网络功能;可选地,所述第一网络设备接收所述第五网络设备发送的网络功能反馈信息,所述网络功能反馈信息用于指示所述第五网络设备已生成的网络功能,以便于所述第一网络设备对网络功能配置进行协调。其中上述需要查询的网络功能可以为虚拟网络功能。例如,对于第三网络管理架构,NSM&O模块可以直接管理物理网络功能模块,但是NM模块对虚拟网络模块的配置参数可能只在NM模块中存储。因此,NSM&O模块需要向NM模块查询NM模块所生成的虚拟网络功能,以便于NSM&O模块进行网络功能的管理和编排。上述已生成的网络包括两种类型:第一种类型是正在运行的网络功能;第二种类型是已经生成但还没有运行的网络功能。可选地,NSM&O模块可以对NM模块已生成的网络功能进行配置。以提高利用资源的效率。
可选地,第一网络设备在接收到网络切片实例创建请求之后,可以验证该网络切片实
例创建请求是否合法。因此,方法700还包括:所述第一网络设备向存储设备发送合法性验证信息,所述合法性验证信息用于请求查询所述网络切片实例创建请求是否合法;所述第一网络设备接收所述存储设备发送的合法性验证响应信息,所述合法性验证响应信息用于指示所述网络切片实例创建请求是否合法。
若合法性验证响应信息指示不合法,则第一网络设备可以不执行目标网络切片实例的网络功能配置操作。若合法性验证响应信息指示合法,则第一网络设备可以执行相应的网络功能配置操作。
作为一个示例,所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息,包括:在所述合法性验证响应信息指示所述网络切片实例创建请求合法的情况下,所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息。
可选地,上述存储设备可以是分布式存储器,也可以是其他类型的存储器。该存储设备可以用于存储用于签约的信息,以用于验证网络切片实例创建请求的合法性。
可选地,第一网络设备在接收网络切片实例创建请求之后,可以通过通信接口向第二网络设备、第三网络设备和第四网络设备进行交互,以查询当前网络功能的运行情况,网络资源的占用情况。或者,还可以为目标网络切片实例预留网络资源。例如,所述第一网络设备可以向第四网络设备发送资源预留指示信息,所述资源预留指示信息用于指示所述第四网络设备为所述目标网络切片实例预留网络资源。
可选地,若第一网络设备查询到当前网络资源不够用于运行目标网络切片实例时,第一网络设备可以向发送端设备发送指示网络资源不足的失败反馈信息。
可选地,在所述第一网络设备接收所述第二网络设备发送的网络功能配置响应信息之后,第一网络设备可以将网络切片实例的状态设置为激活态。作为一个示例,方法700还包括:所述第一网络设备向存储设备发送网络切片实例激活指示,所述网络切片实例激活指示将所述目标网络切片实例设置为激活态。
可选地,在确定将目标网络切片实例激活之后,方法700还包括:所述第一网络设备可以向所述第二网络设备发送网络功能端口激活指示,所述网络功能端口激活指示用于激活所述目标网络切片实例的网络功能的端口。
可选地,在激活目标网络切片实例之后,第一网络设备可以指示存储设备将新生成的网络切片实例的配置参数存入存储设备。方法700还包括:所述第一网络设备向存储设备发送更新网络切片实例指示,所述更新网络切片实例指示用于指示将所述目标网络切片实例的参数信息存入所述存储设备。其中,作为一个示例,存入存储设备的目标网络切片实例的参数信息可以包括共享网络功能或可共享的网络切片实例类型等。
上文结合图7,介绍了本申请实施例的管理网络切片实例的方法。下文将结合图8至图11中的具体例子,分别介绍在上述四种网络管理架构中管理网络切片实例的具体流程。应注意,图8至图11的例子仅仅是为了帮助本领域技术人员理解本申请实施例,而非要将本申请实施例限于所例示的具体数值或具体场景。本领域技术人员根据所给出的图8至图11的例子,显然可以进行各种等价的修改或变化,这样的修改或变化也落入本申请实施例的范围内。
图8是本申请实施例的管理网络切片实例的方法800的流程示意图。方法800可以应
用于图4所示的第二网络管理架构之中。在图8的方法中,第一网络设备可以为NSM&O模块,第二网络设备可以为EM模块,第三网络设备可以为VNFM模块,第四网络设备可以为VIM模块。应理解,在方法800中,S807部分是当共享网络功能已经运行时的执行方法。S808部分至S821部分是需要新生成网络功能的执行方法。上述新生成的网络功能既可以是共享网络功能也可以是专属网络功能。其中,S808部分和S809部分是新生成的网络功能为物理网络功能时的执行方法。S810部分至S821部分是新生成的网络功能为虚拟网络功能时的执行方法。方法800包括:
S801,NSM&O模块从发送端设备接收网络切片实例创建请求。
该网络切片示例创建请求可以用于请求创建目标网络切片实例。可选地,网络切片实例创建请求中可以携带目标网络切片实例的描述信息。上述描述信息可以是目标网络切片实例的服务需求的描述信息和目标网络切片实例的网络切片模板的配置参数信息。
S802,NSM&O模块与存储设备进行交互,以验证网络切片实例创建请求是否合法。
具体地,NSM&O模块可以向存储设备发送合法性验证信息,该合法性验证信息中可以包含目标网络切片实例的描述信息或其他信息。存储设备中预先存储有用户签约的信息。存储设备可以根据用户签约的信息验证目标网络切片实例的创建请求是否合法,并向NSM&O模块返回合法性验证响应信息。若合法,则合法性验证响应信息指示该网络切片实例创建请求合法。若不合法,则合法性验证响应信息指示该网络切片实例创建请求不合法。
S803,在合法性验证响应信息指示该网络切片实例创建请求不合法的情况下,NSM&O模块向发送端设备发送网络切片实例创建响应信息,该网络切片实例创建响应信息可以指示目标网络切片创建失败。本次流程结束。进一步地,网络切片实例创建响应信息中可以携带创建失败的原因,即无权限。
S804,在合法性验证响应信息指示该网络切片实例创建请求合法的情况下,NSM&O模块进行网络功能和资源编排,并确定目标网络切片实例是否使用共享网络功能。其中,网络功能和资源普遍拍可以包括确定目标网络切片的网络功能在物理网络或虚拟网络中的位置,以及确定所需要网络资源等。
S805,NSM&O模块与EM模块、VNFM模块以及VIM模块进行交互,查询当前网络功能的运行情况,以及网络资源的占用情况。并指示VIM模块为目标网络切片实例预留网络资源。
S806,在S805的部分预留资源失败的情况下,并且不能够通过调整的方式支持新的网络切片实例,则NSM&O模块向发送端设备发送网络切片实例创建响应信息,以指示目标网络切片实例创建失败。本次流程结束。进一步地,网络切片实例创建响应信息中可以携带创建失败的原因,即网络资源不足。
S807,在S804部分确定目标网络切片的网络功能包含共享网络功能,并且该共享网络功能当前已经在运行的情况下,NSM&O模块向EM模块发送网络切片实例配置信息,以指示EM模块配置该共享网络功能。该共享网络功能可以是虚拟网络功能或物理网络功能。更进一步地,NSM&O模块可以分别与EM模块、VNFM模块、VIM模块进行交互,以为目标网络切片实例配置该共享网络功能,使该共享网络功能支持新创建的目标网络切片实例。例如,配置的信息可以包括但不限于:a)与网络切片实例相关的参数。例如,网
络切片实例的标识、网络切片实例的类型、网络切片实例所包含的网络功能的信息(例如,在共享网络功能为NAS路由网络功能的情况下,需要获取共享网络功能的网络切片实例的配置信息,以便于确定如何将NAS信息路由至对应的网络切片实例)、网络切片实例需要监测和上报的参数。b)其他传统运行参数。
S808,在目标网络切片的网络功能包含物理网络功能的情况下,NSM&O模块指示EM模块对物理网络功能(即PNF)进行配置。即NSM&O模块向EM模块发送网络切片实例配置信息,以指示EM模块配置该物理网络功能。其中,当物理网络功能为专属网络功能的情况下,需要配置的信息可以包括但不局限于:a)与网络切片实例相关的参数。例如,网络切片实例的标识、网络切片实例需要监测和上报的参数。b)传统的运行参数。例如网关的互联网协议(Internet Protocol,IP)地址、隧道标识等。当物理网络功能为共享网络功能的情况下,需要配置的信息可以包括但不局限于:网络切片实例的标识、网络切片实例的类型、网络切片实例所包含的网络功能的信息(例如,可以对新生成的共享网络功能进行标识,以指示该共享网络功能当前服务于目标网络切片实例,未来可以与其他指定类型的网络切片实例共享)、网络切片实例需要监测和上报的参数。另外,除了与网络切片实例相关的参数之外,还可以包括其他传统运行参数。例如MMEC、MME池等。
S809,在配置完目标网络切片实例的物理网络功能之后,EM模块向NSM&O模块发送网络切片实例创建响应信息,以指示目标网络切片实例创建完成。NSM&O模块接收EM模块发送的网络切片实例创建响应信息。
S810,在目标网络切片实例的网络功能为虚拟网络功能的情况下,NSM&O模块向VNFM模块发送虚拟网络功能创建请求,以指示VNFM模块创建该虚拟网络功能。其中,虚拟网络功能创建请求中可以携带虚拟网络功能的配置参数。例如,该配置参数可以包括S804部分中预留网络资源的反馈信息。例如,虚拟机标识等。该配置参数还可以包括描述虚拟网络功能特性的参数,例如,虚拟机版本或者计算资源要求等。
S811,VNFM模块在接收到虚拟网络功能创建请求之后,检查虚拟网络功能的配置参数的正确性,并授权开始虚拟网络功能的生命周期管理动作。
S812,在VNFM模块授权开始虚拟网络功能的生命周期管理动作的情况下,VNFM模块向NSM&O模块发送允许分配资源指示信息,以指示允许NSM&O模块分配资源。进一步地,VNFM模块可以修改虚拟网络功能的配置参数,并在允许分配资源指示信息中携带修改后的配置参数。
S813,NSM&O模块向VIM模块发送分配资源请求,该分配资源请求用于请求VIM模块为目标网络切片实例分配虚拟网络功能对应的网络资源。进一步地,若S112部分允许分配资源指示信息中携带对虚拟网络功能的修改后的配置参数,NSM&O模块需要根据修改指示,对虚拟网络功能进行修改之后,再向VIM模块发送分配资源请求。
S814,VIM模块根据NSM&O模块的分配资源请求,执行资源分配过程。
S815,在完成资源分配之后,VIM模块向NSM&O模块发送分配资源响应信息,以指示虚拟网络功能对应的网络资源分配完成。NSM&O模块接收该分配资源响应信息。
S816,NSM&O模块在接收该分配资源响应信息之后,向VNFM模块发送资源分配确认信息,以指示VNFM模块网络资源分配完毕,以便于VNFM执行虚拟网络功能的配置过程。VNFM模块接收该分配资源响应信息。
S817,在接收资源分配确认信息之后,VNFM模块对虚拟网络功能配置部署方面的参数。例如,配置虚拟网络功能的IP地址、虚拟网络功能的标识等。
S818,在配置完虚拟网络功能的部署参数之后,VNFM模块向EM模块发送添加虚拟网络功能请求,以请求EM模块将配置好的虚拟网络功能添加为被管理设备。EM模块接收该虚拟网络功能请求,并添加该虚拟网络功能为被管理设备。
S819,在配置完虚拟网络功能的部署参数之后,VNFM模块向NSM&O模块发送虚拟网络功能创建响应信息,以指示目标网络切片实例的虚拟网络功能创建完成。NSM&O模块接收该虚拟网络功能创建响应信息。
S820,在接收虚拟网络功能创建响应信息之后,NSM&O模块可以获知虚拟网络功能已经创建完成,所以NSM&O模块可以配置虚拟网络功能与目标网络切片实例相关的参数。NSM&O模块向EM模块发送网络功能配置指示信息,以指示对该虚拟网络功能进行配置。具体地,对于专属网络功能,需要配置的信息可以包括但不局限于:a)与网络切片实例相关的参数。例如,网络切片实例的标识、网络切片实例需要监测和上报的参数。b)传统的运行参数。例如网关的互联网协议(Internet Protocol,简称“IP”)地址、隧道标识等。当物理网络功能为共享网络功能的情况下,需要配置的信息可以包括但不局限于:网络切片实例的标识、网络切片实例的类型、网络切片实例所包含的网络功能的信息(例如,可以对新生成的共享网络功能进行标识,以指示该共享网络功能当前服务于目标网络切片实例,未来可以与其他指定类型的网络切片实例共享)、网络切片实例需要监测和上报的参数。另外,除了与网络切片实例相关的参数之外,还可以包括其他传统运行参数。例如MMEC、MME池等。
S821,在配置完虚拟网络功能之后,EM模块可以向NSM&O模块发送网络功能配置响应信息,以指示虚拟网络功能配置完成。NSM&O模块接收该网络功能配置响应信息。
S822,NSM&O模块向存储设备发送网络切片实例激活指示,以指示将目标网络切片实例设置为激活态。
S823,NSM&O模块向EM模块发送网络功能端口激活指示,以激活目标网络切片实例的网络功能的端口,以便于虚拟网络功能或物理网络功能相关的端口开始发送或接收数据。
S824,NSM&O模块与存储设备进行交互,以将新生成的目标网络切片实例的参数信息存入该存储设备。例如,上述参数信息可以包括目标网络切片实例的共享网络功能或者可与目标网络切片实例共享网络功能的网络切片实例的类型。
S825,NSM&O模块向发送端设备发送网络切片实例创建响应信息,以指示网络切片实例创建完成。本次流程结束。可选地,若目标网络切片只包含共享网络功能且共享网络功能已运行,S825部分可以在S807之后执行。若目标网络切片包含的网络功能为新生成的网络功能,且该网络功能为物理网络功能,则S825部分可以在S809之后执行。
应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
图8的实施例中,展示了在第二网络管理架构中,创建网络切片实例的过程,其中NSM&O模块能够灵活地编排和管理网络切片实例的网络功能和网络资源,提高了管理网络切片实例的效率。
图9是本申请又一实施例的管理网络切片实例的方法900的流程示意图。方法900可以应用于图3所示的第一网络管理架构之中。但本申请实施例不限于此。在图9的方法中,第一网络设备可以为NSM&O模块,第二网络设备可以为EM模块,第三网络设备可以为NVFO模块,第四网络设备可以为VIM模块。图9的方法中与图8相同或相似的内容,为了简洁,此处不再赘述。
图9的方法所应用的第一网络管理架构包含NFVO模块,即图9中的NFVO模块与NSM&O模块之间是相互独立的,而图8中的方法所应用第二网络管理架构中的NSM&O模块包含了NFVO模块的功能,属于同一模块。所以方法900与方法800的区别之处在于S910部分中NSM&O模块不再向VNFM模块发送虚拟网络功能创建请求,而是向NFVO模块发送虚拟网络功能创建请求,然后由NFVO模块负责创建虚拟网络功能的过程。并且,方法800中NSM&O模块与VNFM模块以及VIM模块之间的交互过程,在方法900中由NSM&O模块指示NVFO模块具体执行。方法900包括:
S901部分至S909部分与图8中的S801部分至S809部分相同或相似,此处不再赘述。
S910,NSM&O模块向NFVO模块发送虚拟网络功能创建请求。NFVO模块接收虚拟网络功能创建请求。
S911,NFVO模块与VNFM模块、VIM模块进行交互,以完成虚拟网络功能的创建。
S912,NFVO模块向EM模块发送添加虚拟网络功能请求,以请求EM模块将配置好的虚拟网络功能添加为被管理设备。EM模块接收该虚拟网络功能请求,并添加该虚拟网络功能为被管理设备。
S913,NFVO模块向NSM&O模块发送虚拟网络功能创建响应信息,以指示目标网络切片实例的虚拟网络功能创建完成。NSM&O模块接收该虚拟网络功能创建响应信息。
S914,在接收虚拟网络功能创建响应信息之后,NSM&O模块向EM模块发送网络功能配置指示信息,以指示对该虚拟网络功能进行配置。
S915,在配置完虚拟网络功能之后,EM模块可以向NSM&O模块发送网络功能配置响应信息,以指示虚拟网络功能配置完成。NSM&O模块接收该网络功能配置响应信息。
S916,NSM&O模块向存储设备发送网络切片实例激活指示,以指示将目标网络切片实例设置为激活态。
S917,NSM&O模块向EM模块发送网络功能端口激活指示,以激活目标网络切片实例的网络功能的端口,以便于虚拟网络功能或物理网络功能相关的端口开始发送或接收数据。
S918,NSM&O模块与存储设备进行交互,以将新生成的目标网络切片实例的参数信息存入该存储设备。例如,上述参数信息可以包括目标网络切片实例的共享网络功能或者可与目标网络切片实例共享网络功能的网络切片实例的类型。
S919,NSM&O模块向发送端设备发送网络切片实例创建响应信息,以指示网络切片实例创建完成。本次流程结束。可选地,若目标网络切片只包含共享网络功能且共享网络功能已运行,S919部分可以在S907之后执行。若目标网络切片包含的网络功能为新生成的网络功能,且该网络功能为物理网络功能,则S919部分可以在S909之后执行。
其中,S914部分至S919部分与图8中的S820部分至S825部分相同或相似,为了简洁的目的,省略部分描述内容。
应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
图9的实施例中,展示了在第一网络管理架构中,创建网络切片实例的过程,其中NSM&O模块能够灵活地编排和管理网络切片实例的网络功能和网络资源,提高了管理网络切片实例的效率。
图10是本申请又一实施例的管理网络切片实例的方法1000的流程示意图。方法1000可以应用于图5所示的第三网络管理架构中。但本申请实施例不限于此。在图10的方法中,第一网络设备可以为NSM&O模块,第二网络设备可以为EM模块,第三网络设备可以为NVFO模块,第四网络设备可以为VIM模块,第五网络设备可以为NM模块。图10的方法中与图8或图9相同或相似的内容,为了简洁,请参考图8或图9相应部分的内容,此处不再赘述。
图10的方法所应用的第三网络管理架构与图9的方法所应用的第一网络管理架构的区别在于,第一网络管理架构中的NSM&O模块包含了NM模块的功能,而第三网络管理架构中的NSM&O模块与NM模块相互独立。因此图10中的NSM&O模块与NM模块都可以管理物理网络功能,并且NSM&O模块和NM模块都可以通过NFVO模块管理虚拟网络功能。因此,为了避免配置的冲突。方法1000中,NSM&O模块和NM模块之间需要对网络功能的配置过程进行协调。其中,方法1000中的S1007部分至S1010部分、S1024部分为对网络功能的配置进行协调的过程。S1014部分和S1015部分为NSM&O模块利用NM模块已生成的虚拟网络功能进行配置的过程。方法1000包括:
S1001部分至S1006部分与图8中的S801部分至S806部分相同或相似,请参考图8的方法中的相应内容,此处不再赘述。
S1007,NSM&O模块向NM模块发送网络功能查询信息,以查询NM模块已生成的网络功能,该网络功能可以是虚拟网络功能。NM模块接收该网络功能查询信息。上述已生成的网络包括两种类型:第一种类型是正在运行的网络功能;第二种类型是已经生成但还没有运行的网络功能。其中,由于物理网络功能可以由NSM&O模块直接进行管理,而NM模块对虚拟网络功能的网络层面的配置参数可能只存储于NM模块之中,所以需要向NM查询关于虚拟网络功能的配置状态。
S1008,NM模块向NSM&O模块发送网络功能反馈信息,以指示NM模块生成的网络功能以及相关参数,以便于NSM&O进行网络功能的协调配置。NSM&O模块接收网络功能反馈信息。可选地,NSM&O模块可以对NM模块已生成的网络功能进行配置。以提高利用资源的效率。
S1009,NSM&O模块向NM模块发送网络功能通知信息,以指示NSM&O模块将要配置的网络功能。该网络功能可以包含物理网络功能或虚拟网络功能。以避免NM模块和NSM&O模块同时对网络功能进行配置,产生冲突。NM模块接收该网络功能通知信息。
S1010,NM模块向NSM&O模块发送网络功能响应信息,以指示NM模块已确认NSM&O模块将要配置的网络功能。NSM&O模块接收该网络功能响应信息。
S1011,在1004部分确定目标网络切片的网络功能包含共享网络功能,并且该共享网络功能当前已经在运行的情况下,NSM&O模块向EM模块发送网络切片实例配置信息,以指示EM模块配置该共享网络功能。该共享网络功能可以是虚拟网络功能或物理网络功
能。更进一步地,NSM&O模块可以分别与EM模块、NFVO模块进行交互,以为目标网络切片实例配置该共享网络功能,使该共享网络功能支持新创建的目标网络切片实例。例如,配置的信息可以包括但不限于:a)与网络切片实例相关的参数。例如,网络切片实例的标识、网络切片实例的类型、网络切片实例所包含的网络功能的信息(例如,在共享网络功能为NAS路由网络功能的情况下,需要获取共享网络功能的网络切片实例的配置信息,以便于确定如何将NAS信息路由至对应的网络切片实例)、网络切片实例需要监测和上报的参数。b)其他传统运行参数。
S1012,在目标网络切片的网络功能包含物理网络功能的情况下,NSM&O模块指示EM模块对物理网络功能(即PNF)进行配置。即NSM&O模块EM模块发送网络切片实例配置信息,以指示EM模块配置该物理网络功能。
S1013,在配置完目标网络切片实例的物理网络功能之后,EM模块向NSM&O模块发送网络切片实例创建响应信息,以指示目标网络切片实例创建完成。NSM&O模块接收EM模块发送的网络切片实例创建响应信息。
S1014,NSM&O模块向EM模块发送网络功能配置指示信息,以指示EM模块利用NM模块已生成的虚拟网络功能进行配置。具体配置的内容与图8中的S820部分相同。进一步地,NSM&O模块可以与NFVO模块进行交互,以对该已生成的虚拟网络功能进行修改和配置。
S1015,NSM&O模块接收EM模块发送的网络功能配置响应信息,以指示目标网络切片实例的对上述已生成的虚拟网络功能的配置完成。
S1016,在目标网络切片实例的网络功能为虚拟网络功能的情况下,NSM&O模块向NFVO模块发送虚拟网络功能创建请求。NFVO模块接收虚拟网络功能创建请求。
S1017,NFVO模块与VNFM模块、VIM模块进行交互,以完成虚拟网络功能的创建。
S1018,NFVO模块向EM模块发送添加虚拟网络功能请求,以请求EM模块将配置好的虚拟网络功能添加为被管理设备。EM模块接收该虚拟网络功能请求,并添加该虚拟网络功能为被管理设备。
S1019,NFVO模块向NSM&O模块发送虚拟网络功能创建响应信息,以指示目标网络切片实例的虚拟网络功能创建完成。NSM&O模块接收该虚拟网络功能创建响应信息。
S1020,在接收虚拟网络功能创建响应信息之后,所以NSM&O模块可以配置虚拟网络功能与目标网络切片实例相关的参数。NSM&O模块向EM模块发送网络功能配置指示信息,以指示对该虚拟网络功能进行配置。
S1021,在配置完虚拟网络功能之后,EM模块可以向NSM&O模块发送网络功能配置响应信息,以指示虚拟网络功能配置完成。NSM&O模块接收该网络功能配置响应信息。
S1022,NSM&O模块向存储设备发送网络切片实例激活指示,以指示将目标网络切片实例设置为激活态。
S1023,NSM&O模块向EM模块发送网络功能端口激活指示。
S1024,NSM&O模块向NM模块发送网络功能配置反馈通知信息,以指示NSM&O模块对网络功能配置的具体内容。
S1025,NSM&O模块与存储设备进行交互,以将新生成的目标网络切片实例的参数信息存入该存储设备。
S1026,NSM&O模块向发送端设备发送网络切片实例创建响应信息,以指示网络切片实例创建完成。本次流程结束。
其中,S1016部分至S1026部分与图9中的S910部分至S919部分相同或相似,为了简洁的目的,省略部分描述内容。
应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
图10的实施例中,展示了在第三网络管理架构中,创建网络切片实例的过程,其中NSM&O模块能够灵活地编排和管理网络切片实例的网络功能和网络资源,提高了管理网络切片实例的效率。
图11是本申请又一实施例的管理网络切片实例的方法1100的流程示意图。方法1100可以应用于图6所示的第四网络管理架构中。但本申请实施例不限于此。在图11的方法中,第一网络设备可以为NSM&O模块,第二网络设备可以为EM模块,第三网络设备可以为NVFO模块,第四网络设备可以为VIM模块,第五网络设备可以为NM模块。图11的方法中与图8至图10的方法相同或相似的内容,为了简洁,请参考图8至图10相应部分的内容,此处不再赘述。
图11的方法所应用的第四网络管理架构与图8的方法所应用的第二网络管理架构的区别在于,第二网络管理架构中的NSM&O模块包含了NM模块的功能,而第四网络管理架构中的NSM&O模块与NM模块相互独立。因此图11中的NSM&O模块与NM模块都可以管理物理网络功能。因此,为了避免配置的冲突。方法1100中,NSM&O模块和NM模块之间需要对物理网络功能的配置过程进行协调。其中,方法1100中的S1107部分、S1108部分以及S1112部分为对物理网络功能进行协调的内容。此外,第四网络管理架构中的NSM&O模块还负责管理虚拟网络功能,NM模块则无需管理虚拟网络功能。方法1100包括:
S1101部分至S1106部分与图8中的S801部分至S806部分相同或相似,请参考图8的方法中的相应内容,此处不再赘述。
S1107,NSM&O模块向NM模块发送网络功能通知信息,以指示NSM&O模块将要配置的网络功能。该网络功能可以包含物理网络功能。NM模块接收该网络功能通知信息。
S1108,NM模块向NSM&O模块发送网络功能响应信息,以指示NM模块已确认NSM&O模块将要配置的网络功能。NSM&O模块接收该网络功能响应信息。
S1109,在1104部分确定目标网络切片的网络功能包含共享网络功能,并且该共享网络功能当前已经在运行的情况下,NSM&O模块向EM模块发送网络切片实例配置信息,以指示EM模块配置该共享网络功能。该共享网络功能可以是虚拟网络功能或物理网络功能。更进一步地,NSM&O模块可以分别与EM模块、NFVO模块进行交互,以为目标网络切片实例配置该共享网络功能,使该共享网络功能支持新创建的目标网络切片实例。例如,配置的信息可以包括但不限于:a)与网络切片实例相关的参数。例如,网络切片实例的标识、网络切片实例的类型、网络切片实例所包含的网络功能的信息(例如,在共享网络功能为NAS路由网络功能的情况下,需要获取共享网络功能的网络切片实例的配置信息,以便于确定如何将NAS信息路由至对应的网络切片实例)、网络切片实例需要监测和上报的参数。b)其他传统运行参数。
S1110,在目标网络切片的网络功能包含物理网络功能的情况下,NSM&O模块指示EM模块对物理网络功能(即PNF)进行配置。即NSM&O模块EM模块发送网络切片实例配置信息,以指示EM模块配置该物理网络功能。
S1111,在配置完目标网络切片实例的物理网络功能之后,EM模块向NSM&O模块发送网络切片实例创建响应信息,以指示目标网络切片实例创建完成。NSM&O模块接收EM模块发送的网络切片实例创建响应信息。
S1112,NSM&O模块向NM发送网络功能配置反馈通知信息,以指示NSM&O模块对物理网络功能配置的具体内容。
S1113,在目标网络切片实例的网络功能为虚拟网络功能的情况下,NSM&O模块向VNFM模块发送虚拟网络功能创建请求,以指示VNFM模块创建该虚拟网络功能。
S1114,VNFM模块在接收到虚拟网络功能创建请求之后,检查虚拟网络功能的配置参数的正确性,并授权开始虚拟网络功能的生命周期管理动作。
S1115,在VNFM模块授权开始虚拟网络功能的生命周期管理动作的情况下,VNFM模块向NSM&O模块发送允许分配资源指示信息,以指示允许NSM&O模块分配资源。
S1116,NSM&O模块向VIM模块发送分配资源请求,该分配资源请求用于请求VIM模块为目标网络切片实例分配虚拟网络功能对应的网络资源。
S1117,VIM模块根据NSM&O模块的分配资源请求,执行资源分配过程。
S1118,在完成资源分配之后,VIM模块向NSM&O模块发送分配资源响应信息,以指示虚拟网络功能对应的网络资源分配完成。NSM&O模块接收该分配资源响应信息。
S1119,NSM&O模块在接收该分配资源响应信息之后,向VNFM模块发送资源分配确认信息,以指示VNFM模块网络资源分配完毕,以便于VNFM执行虚拟网络功能的配置过程。VNFM模块接收该分配资源响应信息。
S1120,在接收资源分配确认信息之后,VNFM模块对虚拟网络功能配置部署方面的参数。例如,配置虚拟网络功能的IP地址、虚拟网络功能的标识等。
S1121,在配置完虚拟网络功能的部署参数之后,VNFM模块向EM模块发送添加虚拟网络功能请求,以请求EM模块将配置好的虚拟网络功能添加为被管理设备。EM模块接收该虚拟网络功能请求,并添加该虚拟网络功能为被管理设备。
S1122,在配置完虚拟网络功能的部署参数之后,VNFM模块向NSM&O模块发送虚拟网络功能创建响应信息,以指示目标网络切片实例的虚拟网络功能创建完成。NSM&O模块接收该虚拟网络功能创建响应信息。
S1123,在接收虚拟网络功能创建响应信息之后,NSM&O模块可以获知虚拟网络功能已经创建完成,所以NSM&O模块可以配置虚拟网络功能与目标网络切片实例相关的参数。NSM&O模块向EM模块发送网络功能配置指示信息,以指示对该虚拟网络功能进行配置。
S1124,在配置完虚拟网络功能之后,EM模块可以向NSM&O模块发送网络功能配置响应信息,以指示虚拟网络功能配置完成。NSM&O模块接收该网络功能配置响应信息。
S1125,NSM&O模块向存储设备发送网络切片实例激活指示,以指示将目标网络切片实例设置为激活态。
S1126,NSM&O模块向EM模块发送网络功能端口激活指示,以激活目标网络切片
实例的网络功能的端口,以便于虚拟网络功能或物理网络功能相关的端口开始发送或接收数据。
S1127,NSM&O模块与存储设备进行交互,以将新生成的目标网络切片实例的参数信息存入该存储设备。
S1128,NSM&O模块向发送端设备发送网络切片实例创建响应信息,以指示网络切片实例创建完成。本次流程结束。
其中,S1113部分至S1128部分与图9中的S810部分至S825部分相同或相似,为了简洁的目的,省略部分描述内容。
应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
图11的实施例中,展示了在第四网络管理架构中,创建网络切片实例的过程,其中NSM&O模块能够灵活地编排和管理网络切片实例的网络功能和网络资源,提高了管理网络切片实例的效率。
上文介绍了本申请实施例的多种网络管理架构中创建网络切片实例的方法。其中,上述网络管理架构中的NSM&O模块既可以是一个实体模块,也可以是具有层次结构的多个实体模块。例如,图12示出了本申请又一实施例的NSM&O模块的结构示意图。如图12所示,NSM&O模块可以包括一个多路NSM&O模块作为一个总的控制编排模块,其可以管理多个域的子NSM&O模块。在多路NSM&O模块从发送端设备接收网络切片实例创建请求的情况下,可以对该网络切片实例创建请求进行分析,将整个网络切片实例分为多个子网络切片实例。例如,一个网络切片实例可以切分为核心网子切片实例和无线接入网(Radio Access Network,RAN)子切片实例。或者,一个网络切片实例可以划分为多个不同运行商(vendor)设备提供的子网络切片实例。多路NSM&O模块可以通知各子NSM&O模块生成相应的子网络切片实例。子网络切片实例的描述信息与整个网络切片实例的描述信息相同或相似。例如,描述信息可以包含网络功能、网络功能之间的连接关系、KPI指数、需要监控的运行参数等。也可以不包含这些具体信息,只需向子NSM&O模块发送子网络切片实例的服务需求,具体如何生成子网络切片由子NSM&O模块决定。
子NSM&O模块在生成子网络切片实例的过程中,可以与多路NSM&O模块进行信息的交互。图13示出了多路NSM&O模块与子NSM&O模块之间的交互过程。其中,图13中包括三个子NSM&O模块:第一子NSM&O模块、第二子NSM&O模块以及第三子NSM&O模块。
S1301,多路NSM&O模块将网络切片实例切分为多个子网络切片实例。
S1302,多路NSM&O模块分别向多个子NSM&O模块发送子网络切片实例创建请求,以创建相应的子网络切片实例。多个子NSM&O模块接收子网络切片实例创建请求。
S1303,多个子NSM&O模块向多路NSM&O模块发送子网络切片实例创建响应信息,以指示相应的子网络切片实例创建完成。
在本申请实施例中,NSM&O模块可以是层次结构,一个整个的网络切片实例可以分为多个子网络切片实例来进行管理,可以灵活地适应网络管理中多域、多运行商的特性。
上文中结合图1至图13,详细描述了根据本申请实施例的管理网络切片实例的方法,下面将结合图14至图23,详细描述根据本申请实施例的管理网络切片实例的装置。
图14示出了本申请实施例提供的管理网络切片实例的装置1400,该装置1400可以为第一网络设备,该装置1400包括:处理单元1410和通信单元1420,
所述处理单元1410用于通过所述通信单元1420从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切片实例的描述信息;以及根据所述描述信息通过所述通信单元1420,向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能;以及通过所述通信单元1420接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成;以及通过所述通信单元1420向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
在本申请实施例中,第一网络设备通过指示第二网络设备进行网络切片实例的网络功能配置,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,这里的装置1400以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置1400可以具体为上述实施例中的第一网络设备,装置1400可以用于执行上述方法实施例中与第一网络设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图15示出了本申请实施例提供的另一管理网络切片实例的装置1500,该装置1500可以为第二网络设备,该装置1500包括:处理单元1510和通信单元1520,
所述处理单元1510用于通过所述通信单元1520接收第一网络设备发送的网络切片配置信息,所述网络切片配置信息用于指示所述第二网络设备配置目标网络切片的网络功能;
以及通过所述通信单元1520向所述第一网络设备发送网络切片配置响应信息,所述网络切片配置响应信息指示所述目标网络切片对应的网络功能配置完成。
在本申请实施例中,第二网络设备通过接收第一网络设备的指示,进行网络切片实例的网络功能配置,从而对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,这里的装置1500以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置1500可以具体为上述实施例中的第二网络设备,装置1500可以用于执行上述方法实施例中与第二网络设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图16示出了本申请实施例提供的另一管理网络切片实例的装置1600,该装置1600
可以为第三网络设备,该装置1600包括:处理单元1610和通信单元1620,
所述处理单元1610用于通过所述通信单元1620接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;
以及通过所述通信单元1620向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
在本申请实施例中,第三网络设备通过接收第一网络设备指示,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,这里的装置1600以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置1600可以具体为上述实施例中的第三网络设备,装置1600可以用于执行上述方法实施例中与第三网络设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图17示出了本申请实施例提供的另一管理网络切片实例的装置1700,该装置1700可以为第四网络设备,该装置1700包括:处理单元1710和通信单元1720,
所述处理单元1710用于通过所述和通信单元1720接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;
以及通过所述和通信单元1720向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
在本申请实施例中,第四网络设备通过接收第一网络设备指示,以对网络切片实例的创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,这里的装置1700以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置1700可以具体为上述实施例中的第四网络设备,装置1700可以用于执行上述方法实施例中与第四网络设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图18示出了本申请实施例提供的另一管理网络切片实例的装置1800,该装置1800可以为第五网络设备,该装置1800包括:处理单元1810和通信单元1820,
所述处理单元1810用于通过所述通信单元1820接收第一网络设备发送的网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;
以及通过所述通信接口向所述第一网络设备发送网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
在本申请实施例中,第五网络设备通过接收第一网络设备指示,以对网络切片实例的
创建过程进行管理,能够实现网络切片实例的自动化创建,提高管理网络切片实例的效率。
应理解,这里的装置1800以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置1800可以具体为上述实施例中的第五网络设备,装置1800可以用于执行上述方法实施例中与第五网络设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图19示出了本申请实施例提供的另一管理网络切片实例的装置1900。该装置1900包括处理器1910、通信接口1920、存储器1930和总线系统1940。其中,处理器1910、通信接口1920和存储器1930通过总线系统1940相连,该存储器1930用于存储指令,该处理器1910用于执行该存储器1930存储的指令,以控制该通信接口1920发送信号和/或接收信号。
其中,该处理器1910用于通过通信接口1920从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切片实例的描述信息;根据所述描述信息,通过所述通信接口1920向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能;以及通过所述通信接口1920接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成;以及通过所述通信接口1920向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
应理解,装置1900可以具体为上述实施例中的第一网络设备,并且可以用于执行上述方法实施例中与第一网络设备对应的各个步骤和/或流程。可选地,该存储器1930可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。该处理器1910可以用于执行存储器中存储的指令,并且当该处理器1910执行存储器中存储的指令时,该处理器1910用于执行上述与该第一网络设备对应的方法实施例的各个步骤和/或流程。
图20示出了本申请实施例提供的另一管理网络切片实例的装置2000。该装置2000包括处理器2010、通信接口2020、存储器2030和总线系统2040。其中,处理器2010、通信接口2020和存储器2030通过总线系统2040相连,该存储器2030用于存储指令,该处理器2010用于执行该存储器2030存储的指令,以控制该通信接口2020发送信号和/或接收信号。
其中,该处理器2010用于通过所述通信接口2020接收第一网络设备发送的网络切片配置信息,所述网络切片配置信息用于指示所述第二网络设备配置目标网络切片的网络功能;以及通过所述通信接口2020向所述第一网络设备发送网络切片配置响应信息,所述网络切片配置响应信息指示所述目标网络切片对应的网络功能配置完成。
应理解,装置2000可以具体为上述实施例中的第二网络设备,并且可以用于执行上述方法实施例中与第二网络设备对应的各个步骤和/或流程。可选地,该存储器2030可以
包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。该处理器2010可以用于执行存储器中存储的指令,并且当该处理器2010执行存储器中存储的指令时,该处理器2010用于执行上述与该第二网络设备对应的方法实施例的各个步骤和/或流程。
图21示出了本申请实施例提供的另一管理网络切片实例的装置2100。该装置2100包括处理器2110、通信接口2120、存储器2130和总线系统2140。其中,处理器2110、通信接口2120和存储器2130通过总线系统2140相连,该存储器2130用于存储指令,该处理器2110用于执行该存储器2130存储的指令,以控制该通信接口2120发送信号和/或接收信号。
其中,该处理器2110用于通过所述通信接口2020接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;以及通过所述通信接口2020向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
应理解,装置2100可以具体为上述实施例中的第三网络设备,并且可以用于执行上述方法实施例中与第三网络设备对应的各个步骤和/或流程。可选地,该存储器2130可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。该处理器2110可以用于执行存储器中存储的指令,并且当该处理器2110执行存储器中存储的指令时,该处理器2110用于执行上述与该第三网络设备对应的方法实施例的各个步骤和/或流程。
图22示出了本申请实施例提供的另一管理网络切片实例的装置2200。该装置2200包括处理器2210、通信接口2220、存储器2230和总线系统2240。其中,处理器2210、通信接口2220和存储器2230通过总线系统2240相连,该存储器2230用于存储指令,该处理器2210用于执行该存储器2230存储的指令,以控制该通信接口2220发送信号和/或接收信号。
其中,该处理器2210用于通过所述通信接口2220接收第一网络设备发送的分配资源请求,所述分配资源请求用于请求所述第四网络设备为目标网络切片实例分配虚拟网络功能对应的网络资源;
以及通过所述通信接口2220向所述第一网络设备发送分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
应理解,装置2200可以具体为上述实施例中的第三网络设备,并且可以用于执行上述方法实施例中与第三网络设备对应的各个步骤和/或流程。可选地,该存储器2230可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。该处理器2210可以用于执行存储器中存储的指令,并且当该处理器2210执行存储器中存储的指令时,该处理器2210用于执行上述与该第三网络设备对应的方法实施例的各个步骤和/或流程。
图23示出了本申请实施例提供的另一管理网络切片实例的装置2300。该装置2300包括处理器2310、通信接口2320、存储器2330和总线系统2340。其中,处理器2310、通信接口2320和存储器2330通过总线系统2340相连,该存储器2330用于存储指令,该
处理器2310用于执行该存储器2330存储的指令,以控制该通信接口2320发送信号和/或接收信号。
其中,该处理器2310用于通过所述通信接口2320接收第一网络设备发送的网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;
以及通过所述通信接口2320向所述第一网络设备发送网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
应理解,装置2300可以具体为上述实施例中的第五网络设备,并且可以用于执行上述方法实施例中与第五网络设备对应的各个步骤和/或流程。可选地,该存储器2330可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。该处理器2310可以用于执行存储器中存储的指令,并且当该处理器2310执行存储器中存储的指令时,该处理器2310用于执行上述与该第五网络设备对应的方法实施例的各个步骤和/或流程。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
另外,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请实施例中,“与A相应的B”表示B与A相关联,根据A可以确定B。但还应理解,根据A确定B并不意味着仅仅根据A确定B,还可以根据A和/或其他信息确定B。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、计算机软件或者二者的结合来实现,为了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其他的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,该单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另外,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接,也可以是电的,机械的或其他的形式连接。
该作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目
的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分,或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例该方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上某一实施例中的技术特征和描述,为了使申请文件简洁清楚,可以理解适用于其他实施例,在其他实施例不再一一赘述。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到各种等效的修改或替换,这些修改或替换都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以权利要求的保护范围为准。
Claims (34)
- 一种管理网络切片实例的方法,其特征在于,包括:第一网络设备从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切片实例的描述信息;所述第一网络设备根据所述描述信息,向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能;所述第一网络设备接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成;所述第一网络设备向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
- 如权利要求1所述的方法,其特征在于,所述目标网络切片实例的网络功能包括以下网络功能中的至少一种:物理网络功能和虚拟网络功能。
- 如权利要求1或2所述的方法,其特征在于,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述网络功能配置指示信息中包括所述目标网络切片实例的标识符。
- 如权利要求1至3中任一项所述的方法,其特征在于,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述方法还包括:所述第一网络设备向第四网络设备发送网络资源扩展指示,所述网络资源扩展指示用于指示所述第四网络设备为所述目标网络切片实例的共享网络功能分配网络资源。
- 如权利要求1至4中任一项所述的方法,其特征在于,所述方法还包括:所述第一网络设备向第四网络设备发送资源预留指示信息,所述资源预留指示信息用于指示所述第四网络设备为所述目标网络切片实例预留网络资源。
- 如权利要求1至5中任一项所述的方法,其特征在于,在所述目标网络切片实例的网络功能包括虚拟网络功能的情况下,所述方法还包括:所述第一网络设备向第三网络设备发送虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建所述目标网络切片实例的虚拟网络功能;所述第一网络设备接收所述第三网络设备发送的虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
- 如权利要求6所述的方法,其特征在于,所述方法还包括:所述第一网络设备向第四网络设备发送分配资源请求,所述分配资源请求用于请求所述第四网络设备为所述目标网络切片实例分配虚拟网络功能对应的网络资源;所述第一网络设备接收所述第四网络设备发送的分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 如权利要求7所述的方法,其特征在于,在所述第一网络设备接收所述第四网络设备发送的分配资源响应信息之后,所述方法还包括:所述第一网络设备向所述第三网络设备发送资源分配确认信息,所述资源分配确认信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 如权利要求1至8中任一项所述的方法,其特征在于,所述方法还包括:所述第一网络设备向第五网络设备发送网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;所述第一网络设备接收所述第五网络设备发送的网络功能响应信息,所述网络功能响应信息用于指示所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
- 如权利要求1至9中任一项所述的方法,其特征在于,所述方法还包括:所述第一网络设备向第五网络设备发送网络功能查询信息,所述网络功能查询信息用于请求查询所述第五网络设备已生成的网络功能;所述第一网络设备接收所述第五网络设备发送的网络功能反馈信息,所述网络功能反馈信息用于指示所述第五网络设备已生成的网络功能。
- 如权利要求1至10中任一项所述的方法,其特征在于,所述描述信息包括以下信息中的至少一种:所述目标网络切片实例的服务需求的描述信息和所述目标网络切片实例的网络切片模板的配置参数信息。
- 一种管理网络切片实例的方法,其特征在于,包括:第二网络设备接收第一网络设备发送的网络切片配置信息,所述网络切片配置信息用于指示所述第二网络设备配置目标网络切片的网络功能;所述第二网络设备向所述第一网络设备发送网络切片配置响应信息,所述网络切片配置响应信息指示所述目标网络切片对应的网络功能配置完成。
- 一种管理网络切片实例的方法,其特征在于,所述方法包括:第三网络设备接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;第三网络设备向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
- 一种管理网络切片实例的方法,其特征在于,包括:第四网络设备接收第一网络设备发送的分配资源请求,所述分配资源请求用于请求所述第四网络设备为目标网络切片实例分配虚拟网络功能对应的网络资源;所述第四网络设备向所述第一网络设备发送分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 一种管理网络切片实例的方法,其特征在于,包括:第五网络设备接收第一网络设备发送的网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;所述第五网络设备向所述第一网络设备发送网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
- 一种管理网络切片实例的装置,其特征在于,所述装置为第一网络设备,包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指 令,以在执行所述指令时执行如下步骤:通过所述通信接口从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求用于请求创建目标网络切片实例,所述网络切片实例创建请求包含所述目标网络切片实例的描述信息;根据所述描述信息,通过所述通信接口向第二网络设备发送网络功能配置指示信息,所述网络功能配置指示信息用于指示所述第二网络设备配置所述目标网络切片实例的网络功能;以及通过所述通信接口接收所述第二网络设备发送的网络功能配置响应信息,所述网络功能配置响应信息指示所述目标网络切片实例的网络功能配置完成;以及通过所述通信接口向所述发送端设备发送网络切片实例创建响应信息,所述网络切片实例创建响应信息指示所述目标网络切片实例创建完成。
- 如权利要求16所述的装置,其特征在于,所述目标网络切片实例的网络功能包括以下网络功能中的至少一种:物理网络功能和虚拟网络功能。
- 如权利要求16或17所述的装置,其特征在于,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述网络功能配置指示信息中包括所述目标网络切片实例的标识符。
- 如权利要求16至18中任一项所述的装置,其特征在于,在所述目标网络切片实例的网络功能包含可共享的网络功能的情况下,所述处理器还用于通过所述通信接口向第四网络设备发送网络资源扩展指示,所述网络资源扩展指示用于指示所述第四网络设备为所述目标网络切片实例的共享网络功能分配网络资源。
- 如权利要求16至19中任一项所述的装置,其特征在于,所述处理器还用于通过所述通信接口向第四网络设备发送资源预留指示信息,所述资源预留指示信息用于指示所述第四网络设备为所述目标网络切片实例预留网络资源。
- 如权利要求16至20中任一项所述的装置,其特征在于,在所述目标网络切片实例的网络功能包括虚拟网络功能的情况下,所述处理器还用于通过所述通信接口向第三网络设备发送虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建所述目标网络切片实例的虚拟网络功能;以及通过所述通信接口接收所述第三网络设备发送的虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
- 如权利要求21所述的装置,其特征在于,所述处理器还用于通过所述通信接口向第四网络设备发送分配资源请求,所述分配资源请求用于请求所述第四网络设备为所述目标网络切片实例分配虚拟网络功能对应的网络资源;以及通过所述通信接口接收所述第四网络设备发送的分配资源响应信息,所述分配资源响应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 如权利要求22所述的装置,其特征在于,在接收所述第四网络设备发送的分配资源响应信息之后,所述处理器还用于通过所述通信接口向所述第三网络设备发送资源分配确认信息,所述资源分配确认信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 如权利要求16至23中任一项所述的装置,其特征在于,所述处理器还用于通过 所述通信接口向第五网络设备发送网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;以及通过所述通信接口接收所述第五网络设备发送的网络功能响应信息,所述网络功能响应信息用于指示所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
- 如权利要求16至24中任一项所述的装置,其特征在于,所述处理器还用于通过所述通信接口向第五网络设备发送网络功能查询信息,所述网络功能查询信息用于请求查询所述第五网络设备已生成的网络功能;以及通过所述通信接口接收所述第五网络设备发送的网络功能反馈信息,所述网络功能反馈信息用于指示所述第五网络设备已生成的网络功能。
- 如权利要求16至25中任一项所述的装置,其特征在于,所述描述信息包括以下信息中的至少一种:所述目标网络切片实例的服务需求的描述信息和所述目标网络切片实例的网络切片模板的配置参数信息。
- 一种管理网络切片实例的装置,其特征在于,所述装置为第二网络设备,包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:通过所述通信接口接收第一网络设备发送的网络切片配置信息,所述网络切片配置信息用于指示所述第二网络设备配置目标网络切片的网络功能;以及通过所述通信接口向所述第一网络设备发送网络切片配置响应信息,所述网络切片配置响应信息指示所述目标网络切片对应的网络功能配置完成。
- 一种管理网络切片实例的装置,其特征在于,所述装置为第三网络设备,所述装置包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:通过所述通信接口接收第一网络设备发送的虚拟网络功能创建请求,所述虚拟网络功能创建请求用于指示所述第三网络设备创建目标网络切片实例的虚拟网络功能;以及通过所述通信接口向所述第一网络设备发送虚拟网络功能创建响应信息,所述虚拟网络功能创建响应信息指示所述目标网络切片实例的虚拟网络功能创建完成。
- 一种管理网络切片实例的装置,其特征在于,所述装置为第四网络设备,包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:通过所述通信接口接收第一网络设备发送的分配资源请求,所述分配资源请求用于请求所述第四网络设备为目标网络切片实例分配虚拟网络功能对应的网络资源;以及通过所述通信接口向所述第一网络设备发送分配资源响应信息,所述分配资源响 应信息用于指示所述目标网络切片实例的虚拟网络功能对应的网络资源分配完成。
- 一种管理网络切片实例的装置,其特征在于,所述装置为第五网络设备,包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:通过所述通信接口接收第一网络设备发送的网络功能通知信息,所述网络功能通知信息用于指示所述第一网络设备将要配置的网络功能;以及通过所述通信接口向所述第一网络设备发送网络功能响应信息,所述网络功能响应信息用于确认所述第五网络设备已确定所述第一网络设备将要配置的网络功能。
- 一种管理网络切片实例的方法,其特征在于,包括:第一网络设备从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求包括网络切片实例的描述信息;所述第一网络设备将待创建的网络切片实例分为多个子网络切片实例;所述第一网络设备分别向多个子第一网络设备发送所述多个子网络切片实例对应的子网络切片实例创建请求。
- 一种管理网络切片实例的方法,其特征在于,包括:子第一网络设备从第一网络设备接收子网络切片实例创建请求;所述子第一网络设备根据所述子网络切片实例请求,生成子网络切片实例。
- 一种管理网络切片实例的装置,其特征在于,所述装置包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:从发送端设备接收网络切片实例创建请求,所述网络切片实例创建请求包括网络切片实例的描述信息;将待创建的网络切片实例分为多个子网络切片实例;分别向多个子第一网络设备发送所述多个子网络切片实例对应的子网络切片实例创建请求。
- 一种管理网络切片实例的装置,其特征在于,所述装置包括:通信接口,存储器,用于存储指令,处理器,与所述存储器和所述通信接口分别相连,用于执行所述存储器存储的所述指令,以在执行所述指令时执行如下步骤:从第一网络设备接收子网络切片实例请求;根据所述子网络切片实例请求,生成子网络切片实例。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17868232.4A EP3525397B1 (en) | 2016-11-03 | 2017-10-27 | Methods and device for managing network slice instance |
US16/400,687 US11032214B2 (en) | 2016-11-03 | 2019-05-01 | Method, apparatus, and system for managing network slice instance |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610974264.6A CN108023757B (zh) | 2016-11-03 | 2016-11-03 | 管理网络切片实例的方法、装置和系统 |
CN201610974264.6 | 2016-11-03 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/400,687 Continuation US11032214B2 (en) | 2016-11-03 | 2019-05-01 | Method, apparatus, and system for managing network slice instance |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018082502A1 true WO2018082502A1 (zh) | 2018-05-11 |
Family
ID=62076624
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/107963 WO2018082502A1 (zh) | 2016-11-03 | 2017-10-27 | 管理网络切片实例的方法、装置和系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11032214B2 (zh) |
EP (1) | EP3525397B1 (zh) |
CN (1) | CN108023757B (zh) |
WO (1) | WO2018082502A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020093963A1 (en) * | 2018-11-09 | 2020-05-14 | Huawei Technologies Co., Ltd. | Method and system of performance assurance with conflict management in provisioning a network slice service |
US11265210B2 (en) * | 2017-03-24 | 2022-03-01 | Huawei Technologies Co., Ltd. | Network slice configuration method, apparatus, and system |
EP3925331A4 (en) * | 2019-02-13 | 2022-11-16 | Nokia Technologies Oy | MANAGING A SERVICE-BASED ARCHITECTURE |
US12081401B2 (en) * | 2017-03-16 | 2024-09-03 | Apple Inc. | Supporting SON functions on network slice instances |
Families Citing this family (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10700946B2 (en) * | 2017-08-08 | 2020-06-30 | Amdocs Development Limited | System, method, and computer program for automatically certifying a virtual network function (VNF) for use in a network function virtualization (NFV) based communication network |
US11171905B1 (en) | 2016-10-17 | 2021-11-09 | Open Invention Network Llc | Request and delivery of additional data |
US10735275B2 (en) * | 2017-06-16 | 2020-08-04 | Cisco Technology, Inc. | Releasing and retaining resources for use in a NFV environment |
CN109560952B (zh) * | 2017-09-27 | 2021-04-09 | 华为技术有限公司 | 一种网络切片管理方法及设备 |
CN107888425B (zh) * | 2017-11-27 | 2019-12-06 | 北京邮电大学 | 移动通信系统的网络切片部署方法和装置 |
GB2573283B (en) * | 2018-04-26 | 2020-04-29 | Metaswitch Networks Ltd | Improvements relating to network functions virtualization |
US11240135B1 (en) * | 2018-05-23 | 2022-02-01 | Open Invention Network Llc | Monitoring VNFCs that are composed of independently manageable software modules |
CN110572272B (zh) | 2018-06-06 | 2020-11-06 | 大唐移动通信设备有限公司 | 一种网络切片的创建方法及管理编排系统 |
CN110581775B (zh) * | 2018-06-08 | 2021-01-29 | 华为技术有限公司 | 网络切片的管理服务实例的管理方法和装置 |
CN110650454B (zh) * | 2018-06-27 | 2021-10-15 | 华为技术有限公司 | V2x通信方法、装置及系统 |
EP3834379B1 (en) | 2018-08-28 | 2023-07-12 | Huawei Technologies Co., Ltd. | Inter-slice sharing in 5g core networks |
CN110875827B (zh) * | 2018-08-31 | 2021-05-18 | 华为技术有限公司 | 一种网络切片管理方法及装置 |
US12008389B2 (en) * | 2018-11-13 | 2024-06-11 | Marvell Asia Pte, Ltd. | Flexible resource assignment to physical and virtual functions in a virtualized processing system |
CN111200859A (zh) * | 2018-11-19 | 2020-05-26 | 华为技术有限公司 | 一种网络切片的选择方法、网络设备及终端 |
CN111263373B (zh) * | 2018-11-30 | 2021-08-27 | 华为技术有限公司 | 数据处理方法、控制器和转发设备 |
WO2020164747A1 (en) * | 2019-02-12 | 2020-08-20 | Telefonaktiebolaget L M Ericsson (Publ) | Amf node, nssf node, target smf node and methods performed in a communications network |
US10958517B2 (en) | 2019-02-15 | 2021-03-23 | At&T Intellectual Property I, L.P. | Conflict-free change deployment |
CN112152832B (zh) * | 2019-06-28 | 2023-01-13 | 中国移动通信有限公司研究院 | 管理对象的处理方法、装置、相关设备及存储介质 |
CN112449315B (zh) * | 2019-08-27 | 2022-05-24 | 华为技术有限公司 | 一种网络切片的管理方法及相关装置 |
WO2021089172A1 (en) * | 2019-11-08 | 2021-05-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Code activation management method for network slicing solutions, and corresponding entity, server and computer program |
WO2021102915A1 (zh) * | 2019-11-29 | 2021-06-03 | Oppo广东移动通信有限公司 | 物联网设备的配置方法、装置及存储介质 |
CN110868720A (zh) * | 2019-12-24 | 2020-03-06 | 西安闻泰电子科技有限公司 | 基站消息的识别方法、装置、移动终端和存储介质 |
CN115211159A (zh) * | 2020-03-04 | 2022-10-18 | 上海诺基亚贝尔股份有限公司 | 网络切片的分配资源 |
US11696184B2 (en) * | 2020-05-06 | 2023-07-04 | Accenture Global Solutions Limited | Quality of service manager for network slices of a network |
CN113902501A (zh) * | 2020-07-06 | 2022-01-07 | 中移物联网有限公司 | 网络切片处理方法、订购平台、管理平台及电子设备 |
CN114051279A (zh) * | 2020-07-23 | 2022-02-15 | 华为技术有限公司 | 一种业务处理方法及网络设备 |
WO2022022639A1 (zh) * | 2020-07-31 | 2022-02-03 | 华为技术有限公司 | 一种通信方法及装置 |
CN116419176A (zh) * | 2021-12-31 | 2023-07-11 | 华为技术有限公司 | 一种网络资源管理方法及通信装置 |
CN118214657A (zh) * | 2022-12-15 | 2024-06-18 | 中兴通讯股份有限公司 | 传送网络切片的配置方法、电子设备及存储介质 |
WO2024144113A1 (en) * | 2022-12-25 | 2024-07-04 | Samsung Electronics Co., Ltd. | Method and apparatus for managing network slices in a wireless communication system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090205046A1 (en) * | 2008-02-13 | 2009-08-13 | Docomo Communications Laboratories Usa, Inc. | Method and apparatus for compensating for and reducing security attacks on network entities |
CN105813195A (zh) * | 2016-05-13 | 2016-07-27 | 电信科学技术研究院 | 一种按需为终端选择移动性管理机制的方法及装置 |
CN106060900A (zh) * | 2016-05-13 | 2016-10-26 | 宇龙计算机通信科技(深圳)有限公司 | 网络切片的接入控制方法及装置、终端化小区和sdn控制器 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8171485B2 (en) * | 2007-03-26 | 2012-05-01 | Credit Suisse Securities (Europe) Limited | Method and system for managing virtual and real machines |
US8484355B1 (en) * | 2008-05-20 | 2013-07-09 | Verizon Patent And Licensing Inc. | System and method for customer provisioning in a utility computing platform |
US8893009B2 (en) * | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
US8615585B2 (en) * | 2010-05-28 | 2013-12-24 | International Business Machines Corporation | Ontology based resource provisioning and management for services |
US10225323B2 (en) * | 2012-09-07 | 2019-03-05 | Oracle International Corporation | System and method for providing java cloud services for use with a cloud computing environment |
US9621435B2 (en) * | 2012-09-07 | 2017-04-11 | Oracle International Corporation | Declarative and extensible model for provisioning of cloud based services |
US20150081837A1 (en) * | 2013-09-13 | 2015-03-19 | Google Inc. | Provisioning a plurality of computing devices |
CN105429780B (zh) * | 2015-10-30 | 2019-04-23 | 南京优速网络科技有限公司 | 一种虚拟化网络服务业务自动生成和动态监控的方法 |
US10129108B2 (en) * | 2015-11-13 | 2018-11-13 | Huawei Technologies Co., Ltd. | System and methods for network management and orchestration for network slicing |
CN110691429B (zh) | 2016-05-13 | 2021-02-12 | 华为技术有限公司 | Rrc状态的控制方法和装置 |
US20170339688A1 (en) * | 2016-05-17 | 2017-11-23 | Industrial Technology Research Institute | Method of network slicing and related apparatuses using the same |
US10149193B2 (en) * | 2016-06-15 | 2018-12-04 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamically managing network resources |
US10454836B2 (en) * | 2016-11-01 | 2019-10-22 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamically adapting a software defined network |
-
2016
- 2016-11-03 CN CN201610974264.6A patent/CN108023757B/zh active Active
-
2017
- 2017-10-27 WO PCT/CN2017/107963 patent/WO2018082502A1/zh unknown
- 2017-10-27 EP EP17868232.4A patent/EP3525397B1/en active Active
-
2019
- 2019-05-01 US US16/400,687 patent/US11032214B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090205046A1 (en) * | 2008-02-13 | 2009-08-13 | Docomo Communications Laboratories Usa, Inc. | Method and apparatus for compensating for and reducing security attacks on network entities |
CN105813195A (zh) * | 2016-05-13 | 2016-07-27 | 电信科学技术研究院 | 一种按需为终端选择移动性管理机制的方法及装置 |
CN106060900A (zh) * | 2016-05-13 | 2016-10-26 | 宇龙计算机通信科技(深圳)有限公司 | 网络切片的接入控制方法及装置、终端化小区和sdn控制器 |
Non-Patent Citations (2)
Title |
---|
"Study on Management and Orchestration of Network Slicing for Next Generation Network (Release 14", 3GPP TR 28.801 V 0.2. 0, 20 September 2016 (2016-09-20), XP055482560 * |
See also references of EP3525397A4 |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US12081401B2 (en) * | 2017-03-16 | 2024-09-03 | Apple Inc. | Supporting SON functions on network slice instances |
US11265210B2 (en) * | 2017-03-24 | 2022-03-01 | Huawei Technologies Co., Ltd. | Network slice configuration method, apparatus, and system |
US20220150116A1 (en) * | 2017-03-24 | 2022-05-12 | Huawei Technologies Co., Ltd. | Network slice configuration method, apparatus, and system |
US11750453B2 (en) | 2017-03-24 | 2023-09-05 | Huawei Technologies Co., Ltd. | Network slice configuration method, apparatus, and system |
US12113667B2 (en) | 2017-03-24 | 2024-10-08 | Huawei Technologies Co., Ltd. | Network slice configuration method, apparatus, and system |
WO2020093963A1 (en) * | 2018-11-09 | 2020-05-14 | Huawei Technologies Co., Ltd. | Method and system of performance assurance with conflict management in provisioning a network slice service |
US11026106B2 (en) | 2018-11-09 | 2021-06-01 | Huawei Technologies Co., Ltd. | Method and system of performance assurance with conflict management in provisioning a network slice service |
CN112970228A (zh) * | 2018-11-09 | 2021-06-15 | 华为技术有限公司 | 提供网络切片服务时具有冲突管理的性能保证方法和系统 |
CN112970228B (zh) * | 2018-11-09 | 2022-10-25 | 华为技术有限公司 | 提供网络切片服务时具有冲突管理的性能保证方法和系统 |
US11528621B2 (en) | 2018-11-09 | 2022-12-13 | Huawei Technologies Co., Ltd. | Method and system of performance assurance with conflict management in provisioning a network slice service |
EP3925331A4 (en) * | 2019-02-13 | 2022-11-16 | Nokia Technologies Oy | MANAGING A SERVICE-BASED ARCHITECTURE |
Also Published As
Publication number | Publication date |
---|---|
CN108023757A (zh) | 2018-05-11 |
EP3525397B1 (en) | 2022-07-20 |
US20190260690A1 (en) | 2019-08-22 |
EP3525397A4 (en) | 2019-10-23 |
EP3525397A1 (en) | 2019-08-14 |
CN108023757B (zh) | 2020-04-28 |
US11032214B2 (en) | 2021-06-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018082502A1 (zh) | 管理网络切片实例的方法、装置和系统 | |
WO2018082491A1 (zh) | 扩展网络切片实例的方法、网络设备和网络构架 | |
WO2018082477A1 (zh) | 用于管理网络切片实例的方法和装置 | |
EP3552419B1 (en) | System and method for programming and/or management of core network slices | |
EP3455728B1 (en) | Orchestrator for a virtual network platform as a service (vnpaas) | |
CN109417719B (zh) | 一种网络资源的管理方法、装置及系统 | |
EP3461087B1 (en) | Network-slice resource management method and apparatus | |
US11005722B2 (en) | End-to-end network service designer tool | |
WO2018058579A1 (zh) | 网络切片的管理方法及管理单元 | |
WO2018001066A1 (zh) | 用于管理网络切片的方法和装置 | |
WO2017181875A1 (zh) | 虚拟化网络的部署方法和部署系统 | |
JP2017517170A (ja) | Nfvシステムにおけるサービス実装のための方法および通信ユニット | |
WO2018171465A1 (zh) | 管理网络切片实例的方法、装置和系统 | |
CN109314696B (zh) | 管理网络切片的方法及其装置 | |
WO2018082487A1 (zh) | 管理网络切片的方法、设备和系统 | |
WO2019056954A1 (zh) | 管理网络切片的方法和装置 | |
WO2019062634A1 (zh) | 通信方法及装置 | |
CN108024256B (zh) | 一种收缩网络切片实例的方法、装置和系统 | |
CA3206693A1 (en) | Ric sdk | |
WO2019141151A1 (zh) | 一种配置基站的方法及装置 | |
CN109417501A (zh) | 网络资源的编排方法和设备 | |
EP3625931B1 (en) | Method for using context awareness for the coordination of management and mobile network service operation planes | |
Chang et al. | Closing in on 5G control apps: enabling multiservice programmability in a disaggregated radio access network | |
WO2018127068A1 (zh) | 网络管理方法和装置 | |
CN113596910A (zh) | 用于处理数据流的方法和通信装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17868232 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017868232 Country of ref document: EP Effective date: 20190507 |