WO2018082491A1 - Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau - Google Patents

Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau Download PDF

Info

Publication number
WO2018082491A1
WO2018082491A1 PCT/CN2017/107625 CN2017107625W WO2018082491A1 WO 2018082491 A1 WO2018082491 A1 WO 2018082491A1 CN 2017107625 W CN2017107625 W CN 2017107625W WO 2018082491 A1 WO2018082491 A1 WO 2018082491A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network device
extended
request
nsi
Prior art date
Application number
PCT/CN2017/107625
Other languages
English (en)
Chinese (zh)
Inventor
陆伟
杨水根
孙文琦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018082491A1 publication Critical patent/WO2018082491A1/fr

Links

Images

Classifications

    • 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/18—Network planning tools
    • 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]

Definitions

  • the present application relates to the field of communications, and more particularly, to a method, network device, and network architecture for extending a network slice instance in the field of communications.
  • Network slicing is a combination of logical network functions that support the needs of a particular use case communication service.
  • 5G fifth generation mobile communication
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • uMTC Ultra-reliable Machine Type Communication
  • the entire 5G system can be composed of a large number of network slice instances that satisfy different connection capabilities.
  • the unified network platform utilizes dynamic and secure network slice instances to support different functions and QoS connection communication services, and is one of the basic capabilities of the 5G network.
  • the existing network management solution does not support management and orchestration of network slice instances, and implements management of network slice instances, especially for network slice instances, which is an urgent problem to be solved.
  • the method, network device, and network architecture of the network slice instance extension provided by the embodiment of the present invention can expand the network function of the network slice instance and improve the user experience.
  • a method for network segment instance extension comprising: a first network device acquiring an extension request of a target network slice instance NSI, the extension request being used to request to extend network function of the target NSI
  • the first network device sends a configuration request to the second network device according to the extension request, where the configuration request is used to request to configure a network function to be extended for the target NSI; the first network device receives the The configuration response message sent by the second network device according to the configuration request, the configuration response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes: the first network device Determining the to be expanded The network function of the exhibition is the target NSI-specific network function; or the first network device determines that the network function to be extended is the target NSI and the associated NSI shared network function, and the associated NSI is the target The NSI uses the NSI of the shared network function in common.
  • the method further includes: when the first network device determines that the network function to be extended is the target NSI and the associated NSI sharing network function And the first network device is associated with the NSLD of the associated NSI, so that the network function to be extended meets the requirement of the associated NSI; and the first network device determines the running information of the associated NSI.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes: if the to-be-expanded The network function is a physical network function, and the first network device determines the configuration request according to the extension request, where the configuration request includes configuring configuration information of the network function to be extended.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes: if the to-be-expanded The network function is a virtual network function, and the first network device sends an extended notification message to the third network device and/or the fourth network device, where the extended notification message is used to indicate the third network device and/or the fourth network
  • the device extends the VNF that implements the virtual network function to be extended; the first network device receives an extended response message sent by the third network device and/or the fourth network device, where the extended response message is used to indicate the The third network device and/or the fourth network device completes extending the VNF.
  • the first network device receives the third network before the first network device receives the extended response message sent by the third network device The device checks the feasibility check message sent according to the extended notification message, and the feasibility check message includes a feasibility check result that extends the VNF.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes: the first network device Sending a resource allocation request to the fifth network device according to the feasibility check message, where the resource allocation request is used to request to allocate a virtual resource for the virtual network function to be extended; and the first network device receives the fifth network And a resource allocation response message sent by the device, where the resource allocation response message is used to instruct the fifth network device to complete the allocation of the virtual resource.
  • the method before the first network device receives the extended response message sent by the third network device, the method further includes: the first network device according to the The resource allocation response message is sent to the third network device, where the first notification message is used to instruct the fifth network device to complete the allocation of the virtual resource, and the first network device receives the third network device to send
  • the extended response message includes: the first network device receiving an extended response message sent by the third network device according to the first notification message.
  • the first network device sends a configuration request to the second network device according to the extension request, including: the first network device according to the extended response message And the extension request sends a configuration request to the second network device, where the configuration request includes configuration information that implements the virtual network function to be extended.
  • the method before the first network device sends a resource allocation request to the fifth network device according to the feasibility check message, the method further includes: A network device sends a first resource reservation request to the fifth network device, where the first resource reservation request is used to request to reserve resources for the network function to be extended.
  • the method before the first network device sends the extended notification message to the fourth network device, the method further includes: the first network device The fourth network device sends a second resource reservation request, where the second resource reservation request is used to request to reserve resources for the network function to be extended.
  • the method before the first network device sends an extension processing request to the second network device, the method further includes: the first network device to the sixth network The device sends a second notification message, where the second network message is used to indicate that the first network device performs an extension process on the network function to be extended; and the first network device receives the sixth network device according to the The second notification confirmation message sent by the second notification message.
  • the method before the first network device sends the second notification message to the fourth network device, the method further includes: the first network device The sixth network device sends a query message, where the query message is used to query a network function that has been generated by the fourth network device, and the first network device receives a query response message sent by the sixth network device, where the query response is The message is used to feed back the configuration information of the network function that has been generated by the sixth network device; the first network device sends the second notification message to the sixth network device, including: the first network device according to the query response message Sending a second notification message to the sixth network device.
  • the method further includes: The network device sends the network function configuration completion message to be extended to the sixth network device, where the network function configuration completion message includes configuration parameters of the network function to be extended.
  • the method further includes: The first network device updates the information of the target NSI stored in the memory according to the configuration response message.
  • a second aspect provides a method for extending an instance of a network slice, the method comprising: receiving, by a second network device, a configuration request sent by a first network device, where the configuration request is for requesting to be extended for a target network slice instance NSI The network function is configured; the second network device configures a network function to be extended of the target NSI according to the configuration request; the second network device sends a configuration response message to the first network device, where the configuration The response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method further includes: if the network function to be extended is a virtual network function, the second network device receives a management request sent by the third network device The message, the management request message is used to request the second network device to manage a virtual network function VNF that implements the network function to be extended.
  • the method further includes: the second network device receiving the And a notification message sent by the first network device, where the notification message is used to instruct the second network device to open a port of the VNF serving the network function to be extended.
  • a third aspect provides a network device that extends an instance of a network slice, where the network device includes: an obtaining module, configured to acquire an extension request of a target network slice instance NSI, where the extension request is used to request a network for the target NSI The function is extended; the sending module is configured to send a configuration request to the second network device according to the extension request, where the configuration request is used to request configuration of a network function to be extended for the target NSI; and a receiving module, configured to receive The configuration response message sent by the second network device according to the configuration request, where the configuration response message is used to indicate the The second network device has completed the configuration of the network function to be extended.
  • a network device for extending a network slice includes: a receiving module, configured to receive a configuration request sent by a first network device, where the configuration request is used to request a target network slice instance NSI to be configured And the processing module is configured to configure, according to the configuration request, the network function to be extended of the target NSI, and the sending module, configured to send a configuration response message to the first network device, where the configuration The response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • a network device for extending a network slice instance comprising: a transceiver, a memory, a processor, and a bus system.
  • the transceiver, the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory to control the transceiver to receive signals and/or transmit signals, and
  • 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.
  • a network device for extending a network slice instance comprising: a transceiver, a memory, a processor, and a bus system.
  • the transceiver, the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory to control the transceiver to receive signals and/or transmit signals, and
  • 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.
  • a seventh aspect a system for extending an instance of a network slice, the system comprising any one of the network device, the fourth aspect, or the fourth aspect in any one of the foregoing possible aspects of the third aspect or the third aspect A network device in a possible implementation.
  • 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 ninth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or the second aspect of the second aspect.
  • a network architecture comprising:
  • At least one first network device and management device At least one first network device and management device
  • the at least one first network device is the network device according to any one of claims 13 to 21, and the management device is configured to manage a network slice instance NSI by using the at least one first network device.
  • the management device is specifically configured to:
  • FIG. 1 is a schematic diagram of a network management architecture in the prior art
  • FIG. 2 is a schematic structural diagram of an NSM&O module according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a network architecture of an extended slice instance in an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a network architecture of an extended network slice instance in another embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a network architecture of an extended network slice instance according to still another embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a network architecture of an extended network slice instance in still another embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for extending a network slice instance in an embodiment of the present invention.
  • FIG. 8 is a hierarchical structure diagram of an NSM&O according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of a method for expanding an instance of a network slice in another embodiment of the present invention.
  • FIG. 10 is a flowchart of a method for extending an instance of a network slice in still another embodiment of the present invention.
  • FIG. 11 is a flowchart of a method for extending an instance of a network slice in still another embodiment of the present invention.
  • FIG. 12 is a flowchart of a method for extending an instance of a network slice in still another embodiment of the present invention.
  • FIG. 13 is a schematic block diagram of a network device according to an embodiment of the present invention.
  • FIG. 14 is a schematic block diagram of a network device according to an embodiment of the present invention.
  • FIG. 15 is a schematic block diagram of a network device according to another embodiment of the present invention.
  • FIG. 16 is a schematic block diagram of a network device according to another embodiment of the present invention.
  • 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 invention relate to network slicing techniques.
  • the network slicing technology logically abstracts the network into one or more isolated network slices, each of which contains a series of logical network functions to specifically meet the differentiated requirements of different service types.
  • 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 a plurality of independent parallel network slice instances according to the scene requirements. Each network segment instance 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 instance 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 slice lifecycle management is a key issue to consider.
  • Network slice lifecycle management includes the creation, composition, update, and deletion of network slice instances.
  • the extension of the network function of the network sharding instance involves the physical network function to be configured, the computing, storage and other resources of the virtual network function and the increase of the virtual network function.
  • Network slicing is a concept that refers to physical or virtual network infrastructure, depending on the The service requirements are customized to different logical networks.
  • 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, which defines the functional behavior and interface.
  • the network function can be implemented as a dedicated hardware or a software running on a dedicated hardware, or on a general hardware platform.
  • the implementation of virtual functions Therefore, from the perspective of implementation, network functions can be divided into 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 in the prior art.
  • 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 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 (GW).
  • MME Mobility Management Entity
  • GW 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.
  • Network element It can be the smallest physical unit that can be monitored and managed in the network management architecture.
  • the NE may be a base station or a Mobility Management Entity (MME), and the NE may also be referred to as a Physical Network Function (PNF) module.
  • MME Mobility Management Entity
  • PNF Physical 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, for example, 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 invention.
  • Network manager A network-level management module that provides network management functions and management equipment exchanges.
  • NM can be responsible for the distribution, configuration, control, and monitoring of network resources, and 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 in the prior art can manage physical network functions and virtual network functions. However, it is not capable of managing and orchestrating network slices. Therefore, the network management architecture in the prior art cannot meet the requirements of the network slicing technology application in the future communication system, that is, the network slicing cannot be managed and arranged flexibly. In the prior art, the physical network element and the virtualized network element will coexist for a long time and flexibly constitute a network slice for the purpose of reducing deployment cost and the like. Therefore, there is a need for a network management system that enables the organization and management of physical and virtual network functions or network resources to implement network slicing applications.
  • the central idea of the embodiment of the present invention is to introduce a network slice manager and orchestrator (NSM&O) in the network management architecture 100, and manage the creation process of the network slice instance through NSM&O to implement the network slice instance. Automated creation to improve the efficiency of managing network slicing instances.
  • the network management architecture of the embodiment of the present invention is described below.
  • the embodiment of the present invention introduces an NSM&O module based on the existing network management architecture 100.
  • the structure diagram of the NSM&O module is shown in Figure 2. Its main functions include:
  • Service conversion receiving service description information of a network slice instance sent by a sender device through an interface (for example, an Application Programming Interface (API)), and converting the service description information 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 may be a device that sends a 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.
  • the network management architecture may further include a storage device, where the storage device may be used to record information of the generated network slice instance.
  • This memory can be interfaced with NSM&O.
  • FIG. 3 to FIG. 6 respectively illustrate four network management architectures that can be applied in the embodiments of the present invention.
  • the NSM&O modules are included.
  • the network architectures of FIG. 3 to FIG. 6 are hereinafter referred to as the first network management architecture 300, the second network management architecture 400, and the third network management architecture. 500, fourth network management architecture 600.
  • FIG. 3 is a first network management architecture 300 applied to an embodiment of the present invention.
  • the first network management architecture is a network management architecture that is enhanced and modified based on the existing network management architecture 100.
  • the first network management architecture 300 does not include an NM module, but the NSM&O module performs the functions performed by the NM module in the network management architecture 100. That is to say, 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 communicate with the EM through the communication structure to manage the network functions corresponding to the network slice instance. Among them, 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 implement resource scheduling management of the NFVI module and implement VNF generation and expansion by using the NFVO module to implement network function expansion of the network slice instance. .
  • FIG. 4 illustrates another network management architecture 400 to which an embodiment of the present invention is applied.
  • the network management architecture 400 is also a network management architecture that is enhanced and modified based on the network management architecture 100.
  • the network management architecture 400 is different from the network management architecture 300 in that the network management architecture 400 does not include an entity of the NFVO module.
  • the functionality of the NFVO module is implemented by the NSM&O module. In other words, the functionality of the NSM&O module also includes the orchestration management of virtual network resources.
  • 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 initializes expansion, contraction, termination, etc.; transmits VNF-related events, status information, and so on.
  • 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 the virtual network functions and the VNF life cycle through the VNFM. Therefore, it is possible to uniformly manage and orchestrate physical and virtual network resources and functions, and optimize resources from a global perspective.
  • FIG. 5 illustrates another network management architecture 500 to which an embodiment of the present invention is applied.
  • the NM module is reserved in the network management architecture 500, 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 NSM&O module and the NM module.
  • Negotiation information between blocks for example, the NSM&O module queries the generated VNF of the NM module; the NM module feeds back the generated VNF information to the NSM&O module, and confirms that the NSM&O module is allowed to modify the VNF information; the NSM&O module notifies the NM module which PNF/VNF is to be used. Modifications; the NSM&O module notifies the NM module of specific modifications to the PNF/VNF.
  • the NSM&O module and the NFVO module can perform the following interactions through the NG4 interface: the NSM&O module participates in the lifecycle management of the VNF through the NG4 interface, for example, notifying the NFVO module extension, creating a new VNF, etc.; the NSM&O module queries the NFVO module for the operation information of the VNF and the NFVI; The NFVO module feeds back the operational information of the VNF and NFVI to the NSM&O module; the policy management, the NSM&O module can send a policy to the NFVO module, indicating the need for VNF deployment; the NSM&O module performs VNF cluster management through the NG4 interface.
  • 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 various physical modules in the prior art.
  • 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 illustrates another network management architecture 600 to which an embodiment of the present invention is applied.
  • the NM module is also retained in the network management architecture 600.
  • the NSM&O module and the NM module are also independent of each other.
  • the network management architecture 600 differs from the third network management architecture 500 in that the entity of the NFVO module is not included in the network management architecture 600.
  • 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.
  • there is a communication interface between the NSM&O module and the VNFM module there is a communication interface between the NSM&O module and the VNFM module.
  • 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 various physical modules in the prior art.
  • NSM&O modules can orchestrate and manage virtual resources and participate in VNF lifecycle management through VNFM and VIM. Since the NSF&O module and the NM module can directly manage the PNF, for the management of the PNF, the NSM&O module and the NM module can be coordinated through communication. And because the NSM&O module incorporates the functions of the NFVO 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.
  • FIG. 3 to FIG. 6 are only for facilitating the understanding of the embodiments of the present invention, and the embodiments of the present invention 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.
  • the first network device mentioned herein may be a device including an NSM&O module (hereinafter referred to as "NSM&O")
  • the second network device may be a device including an EM module (hereinafter referred to as "EM")
  • the third network device may be a device including a VNFM module (hereinafter referred to as "VNFM”)
  • the fourth network device may include a device of the NFVO module (hereinafter referred to as "NFVO”)
  • the fifth network device may be a device including the VIM module.
  • VIM VIM module
  • the sixth network device may be a device including an NM module (hereinafter referred to as "NM”).
  • the system may implement the first network device, the second network device, the third network device, the fourth network device, the fifth network device, and the sixth network device. Corresponding functions to achieve flexible management of network slicing instances.
  • first network device, the second network device, the third network device, the fourth network device, the fifth network device, and the sixth network device may be specifically network management devices, and are used for monitoring network elements in network operation and maintenance. Management, and maintenance, but embodiments of the present invention are not limited thereto.
  • FIG. 7 shows an extended method 700 for a network sharding instance according to an embodiment of the present invention.
  • the method 700 can be applied to the network management architecture 300 shown in FIG. 3, which can be applied to the network management architecture 400 shown in FIG.
  • the network management architecture 500 shown in FIG. 5 can also be applied to the network management architecture 600 shown in FIG. 6, which is not limited in this embodiment of the present invention.
  • the first network device acquires an extension request of the target network slice instance NSI, where the extension request is used to request to extend the network function of the target NSI.
  • the first network device sends a configuration request to the second network device according to the extension request, where the configuration request is used to request to configure the to-be-expanded network function of the target NSI.
  • the second network device configures, according to the configuration request, a network function to be extended of the target NSI.
  • the second network device sends a configuration response message to the first network device, where the configuration response message is used to indicate that the second network device completes the configuration of the network function to be extended.
  • the first network device may be an NSM&O
  • the second network device may be an EM.
  • the NSM&O is used as the first network device
  • the EM is described as the second network device, but the embodiment of the present invention is not limited thereto. .
  • the NSM&O can obtain the extension request of the target network slice instance NSI in multiple implementation manners.
  • the NSM&O can receive the extension request sent by the sender.
  • the sender may be an operator and/or a tenant who rents the target NSI, which is not limited in this embodiment of the present invention.
  • the sending end may send the extended request to the NSM&O through an Application Programming Interface (API), where the extended request is used to request to extend the network function to be extended of the target NSI.
  • API Application Programming Interface
  • the sender may be an operator, a third-party tenant, an application that has the right to extend the network slice instance, or any entity in the service provider domain that may send a request to the NSM&O.
  • NSM&O can trigger the expansion of the target NSI through other internal mechanisms. Exhibition request.
  • the performance management mechanism inside NSM&O can trigger the extension request of the target NSI.
  • a configuration request may be sent to the EM, where the configuration request is used to request to configure the to-be-expanded network function of the target NSI to enable the target NSI to be served.
  • the NSM&O can control the EM to configure the network slice of the target network slice.
  • the NSM&O determines that the network function to be extended is implemented by the PNF
  • the NSM&O controls the EM to configure the PNF by configuring the request
  • the NSM&O determines to implement The network function to be extended is implemented by the VNF
  • the NSM&O controls the EM to configure the VNF by configuring the request.
  • the NSM&O also needs to expand and/or create a new VNF through NFVO or VNFM.
  • the NSM&O after the NSM&O receives the extension request sent by the sender, the NSM&O authenticates and authenticates the sender through the storage device.
  • the NSM&O performs the information exchange with the storage device, and the identity of the sender is authenticated by the storage device, and the integrity of the parameter in the request is verified.
  • the identifier format of the NSM&O verification target NSI is correct, for the network function to be extended.
  • the description format of the service and / or function is correct.
  • NSM&O checks whether the target network slice instance exists and the target network slice instance runs, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.
  • the NSLD of the target NSI can be associated with the NSLD.
  • the NSM&O can associate the description of the network function to be extended to the virtual network function and/or the physical network in the target NSI. In the function, it is thus determined whether the sender has the right to extend the network function of the target NSI to be extended. If the sender does not have the network function to be extended to the target NSI, the NSM&O may send a feedback message to the sender, where the feedback message is used to indicate the extension request error of the sender.
  • the NSM&O may associate the NSLD of the target NSI to verify whether the target NSI can be extended.
  • NSM&O combines the NSLD to determine the virtual network function and/or physical network function to be extended in the target NSI.
  • the NSM&O provides insufficient performance feedback to the operator and/or the tenant.
  • the method before the NSM&O sends the configuration request to the EM according to the extension request, the method further includes:
  • the NSM&O determines that the network function to be extended is a network function exclusive to the target NSI;
  • the NSM&O determines that the network function to be extended is a network function shared by the target NSI and the associated NSI, and the associated NSI is an NSI that uses the shared network function in common with the target NSI.
  • the shared physical network function may also be referred to as a general physical network function
  • the shared virtual network function may also be referred to as a general virtual network function.
  • the dedicated network function refers to the function of the target network slice exclusive, and is not shared with other network slice instances
  • the shared network function refers to the physical network function that multiple network slice instances can share.
  • the method further includes: if the NSM&O determines that the network function to be extended is a shared network function of the target NSI, the NSM&O associates the NSLD of the associated NSI, so that the network function to be extended conforms to the associated NSI.
  • the NSM&O determines the running information of the associated NSI according to the NSLD of the associated NSI.
  • the EM configures the network function to be extended of the target NSI according to the configuration request.
  • the NSM&O determines configuration information for implementing the network function to be extended according to the extension request, and sends a configuration request to the EM, requesting the EM to be the The network function to be extended is configured.
  • the EM configures the network function to be extended
  • the EM sends a configuration response message to the NSM&O to indicate that the extension of the network function to be extended of the target NSI has been completed. Therefore, the extended method of the network sharding instance of the embodiment of the present invention can extend the network function of the network sharding instance to be extended, realize the network function expansion of the network splicing instance, and improve the user experience.
  • the EM configures the PNF according to the configuration request of the NSM&O; when the network function to be extended is the VNF, the EM configures the VNF according to the configuration request of the NSM&O.
  • the EM here may be an EM that only manages the PNF, or an EM that manages both the PNF and the VNF, that is, when the extended network function is implemented by the PNF, the NSM&O can only interact with the EM managing the PNF.
  • the EM that manages the PNF and the VNF can also be interacted with each other, which is not limited in this embodiment of the present invention.
  • the sending end may be an NSM&O management device.
  • the NSM&O management device may manage the first NSM&O, the second NSM&O, and the third NSM&O.
  • the NSM&O may be at least one of the first NSM&O, the second NSM&O, and the third NSM&O, that is, the NSM&O management device may separately manage each NSM&O, and send an extension request to each NSM&O.
  • the process of expanding the network slicing instance managed by the first NSM&O, the second NSM&O, and the third NSM&O respectively is the foregoing method 700.
  • the three NSM&Os may be separately extended in order, or may be performed in parallel. The embodiment of the present invention does not limit this.
  • the NSM&O management device is a total control orchestrator that manages the NSM&O for each domain.
  • a network slice instance may be composed of a core network sub-slice instance and an access network sub-slice instance; or a network slice instance may be divided into sub-slice instances provided by multiple different carrier devices.
  • Each subnet slice instance is managed by NSM&O for each domain.
  • the NSM&O management device can determine which sub-network slice instances the target NSI needs to be extended, and then directly notify the corresponding NSM&O to expand.
  • the method before the NSM&O sends the configuration request to the EM according to the extension request, the method further includes:
  • the NSM&O determines a configuration request determined according to the extension request, and the configuration request includes configuration information for configuring the network function to be extended.
  • the PNF that implements the network function to be extended may be specifically configured into the following four cases.
  • the NSM&O determines that the PNF implementing the network function to be extended is a PNF shared by the multi-slice instance, and the NSM&O arranges the result according to the extension request to use more resources for the existing PNF configuration for the target NSI and the associated NSI service. Then, the NSM&O sends a configuration request to the EM, and the EM configures more resources according to the configuration request for the existing PNF that implements the network function to be extended.
  • the NSM&O determines that the PNF that implements the network function to be extended is a PNF shared by the multi-slice instance, and the NSM&O schedules the result according to the extension request to add a PNF to implement the network function to be extended, the NSM&O sends the configuration to the EM. Request, the configuration request is used to request the EM to configure the newly added PNF.
  • the configuration request may include an identifier of the target NSI, an identifier of the associated NSI, detection and reporting information of the target NSI and the associated NSI, operation parameters and policy information of the target NSI, network connection of the target NSI and other shared network functions, and target NSI exclusive
  • the network connection of the network function, the network connection of the NSI-specific network function, and the like are not limited in this embodiment of the present invention.
  • NSM&O determines that the PNF that implements the network function to be extended is the target NSI-specific PNF, and NSM&O arranges the result according to the extension request to use more resources for the existing PNF configuration as the target NSI service, then the NSM&O direction
  • the EM sends a configuration request, and the EM configures more resources for the existing PNF that implements the network function to be extended according to the configuration request.
  • the NSM&O determines that the PNF that implements the network function to be extended is the target NSI-specific PNF, and the NSM&O schedules the result according to the extension request to add a PNF to implement the network function to be extended, the NSM&O sends a configuration request to the EM, The configuration request is used to request the EM to configure the newly added PNF.
  • the configuration request may include an identifier of the target NSI, an identifier of the associated NSI, detection and reporting information of the target NSI and the associated NSI, operation parameters and policy information of the target NSI, network connection of the target NSI and other shared network functions, and target NSI exclusive
  • the network connection of the network function, the network connection of the NSI-specific network function, and the like are not limited in this embodiment of the present invention.
  • the first network device may send a physical resource reservation request to the second network device, where the physical resource reservation request is used to request the second network device to reserve physical resources for the network function to be extended.
  • the second network device may feed back the insufficient resource to the first network device, and the first network device may feed back the extension failure to the sending end, and may further indicate that the expansion fails.
  • Reason no resources.
  • the method before the first network device sends the configuration request to the second network device according to the extension request, the method further includes:
  • the first network device sends an extended notification message to the third network device, where the extended notification message includes an extended parameter of the virtual network function to be extended;
  • the first network device receives a feasibility check message sent by the third network device according to the extended notification message, where the feasibility check message includes a feasibility check result of the third network device extending the virtual network function to be extended.
  • the third network device may be a VNFM, and after the VNFM receives the extended notification message sent by the NSM&O, check whether the virtual network function of the NSM&O is feasible according to the extended parameter and the like included in the extended notification message. For example, the VNFM can verify that the NSM&O is eligible to extend the virtual network function based on the extended notification message and check if the extended parameters are compliant. The VNFM can then send a feasibility check message to NSM&O, which is used to indicate whether NSM&O can further extend the virtual network function. If the VNFM determines that the NSM&O has extended rights, it may modify the parameters of the extended network function of the NSM&O according to the extended parameters in the extended notification message sent by the NSM&O, and the specific resources required to expand the network function.
  • the VNFM may modify the parameters of the extended network function of the NSM&O according to the extended parameters in the extended notification message sent by the NSM&O, and the specific resources required to expand the network function.
  • the VNFM sends a feasibility check message to the NSM&O.
  • the feasibility check message may further include an extended parameter that is modified by the VNFM according to the extended parameter included in the extended notification message sent by the NSM&O, and/or a specific resource that the NSM&O needs to use to extend the virtual resource.
  • the first network device may further send a first resource reservation request to the fifth network device, where the first resource reservation request is used to request the network function to be extended to reserve a virtual resource.
  • the fifth network device may be a VIM.
  • the NSM&O may send a resource allocation request to the VIM.
  • the VIM checks the virtual resource to determine the feasibility of the resource and reserves the resource.
  • resources may include computing resources, storage resources, or network resources.
  • the VIM may send a feedback message to the NSM&O to indicate that the VIM has completed reserving virtual network resources for the virtual network function.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes:
  • the first network device sends a resource allocation request to the fifth network device according to the feasibility check message, where the resource allocation request is used to request to allocate a virtual resource for the virtual network function to be extended;
  • the first network device receives the resource allocation response message sent by the fifth network device, where the resource allocation response message is used to instruct the fifth network device to complete the allocation of the virtual resource.
  • the NSM&O sends a resource allocation request to the VIM according to the feasibility check message sent by the VNFM, and requests the VIM to allocate resources for the virtual network function to be extended, where the resource may be reserved by the VIM according to the resource reservation request of the NSM&O.
  • Resources for example, computing resources, storage resources, or network resources.
  • the NSM&O may also send an internal connection request to the VIM, and the internal connection request is added to the VNF internal structure for the newly created virtual machine, or establishes a connection with other network functions for the newly added VNF.
  • VIM can be divided into four situations according to resource allocation requests and internal connection requests to implement virtual network function expansion or new VNF.
  • the VIM adds resources to the existing VNF according to the resource allocation request sent by the NSM&O, for example, adding computing resources, storage resources, etc. to the existing VNF. In this case, since only resources are added to the existing VNF, it is not necessary to establish an additional network connection.
  • the VIM joins the network and allocates resources for the newly created virtual machine according to the resource allocation request and the internal connection request sent by the NSM&O.
  • VIM uses the allocated resources to establish a virtual machine and establish a network connection according to the NSM&O resource allocation request and the internal connection request. Make it a dedicated network function service for the target NSI.
  • the VIM When NSM&O determines that the result of the orchestration is that the VNF is the shared network function for the target NSI, the VIM establishes a virtual machine according to the resource allocation request of the NSM&O, establishes a connection with other shared network functions according to the internal connection request, and establishes a dedicated NSI with the target. Connections between network functions and establishing connections to associated NSI-specific network functions.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes:
  • the first network device sends a first notification message to the third network device according to the resource response message, where the first notification message is used to instruct the fifth network device to complete the allocation of the virtual resource;
  • the VIM sends a resource allocation response message to the NSM&O after completing the capacity expansion and/or adding the resource allocation and/or network connection of the VNF according to the resource allocation request of the NSM&O and the internal connection request.
  • the NSM&O After receiving the resource allocation response message, the first notification message is sent to the VNFM to indicate that the VIM has completed the resource allocation and/or internal connection of the VNF.
  • the VNFM can start to configure lifecycle parameters, deployment parameters, and the like for the expansion and/or the newly added VNF, for example, adding the identity of the VNF.
  • the VNFM may also send a management request message to the EM.
  • the EM may add the newly added VNF to the managed device of the EM.
  • the sending, by the first network device, the configuration request to the second network device according to the extension request includes:
  • the first network device sends a configuration request to the second network device according to the extended response message and the extension request, where the configuration request includes configuration information of a network function to be extended that implements the target NSI.
  • the NSM&O sends a configuration request to the EM, where the configuration request may be used to perform a VNF that specifically implements the network function of the target NSI to be extended.
  • Configuration When the network function to be extended of the target NSI is implemented by expanding the existing VNF, the EM configures the execution parameters and related parameters of the operation policy adjustment.
  • the EM configures the target NSI and related parameters of the associated NSI, for example, the identity of the target NSI, and the running parameters that need to be detected and reported. Specific execution functions and operational strategies.
  • the EM configures the relevant parameters of the target NSI, for example, the identity of the target NSI, the running parameters to be detected and reported, and the specific functions to be performed. And running strategies, etc.
  • the EM here may be an EM that only manages the VNF, or an EM that manages both the PNF and the VNF, that is, when the extended network function is implemented by the VNF, the NSM&O can only interact with the EM managing the VNF.
  • the EM that manages the PNF and the VNF can also be interacted with each other, which is not limited in this embodiment of the present invention.
  • network function management module for managing the PNF network function management module and the management VNF may be different modules or integrated in the same module, which is not limited in this embodiment of the present invention.
  • the NSM&O may further send a notification message to the EM, where the notification message is used to notify the EM to open the virtual port of the VNF,
  • the target NSI provides services.
  • the method before the first network device sends a configuration request to the second network device according to the extension request, the method further includes:
  • the first network device sends an extended notification message to the fourth network device, where the extended notification message is used to indicate that the fourth network device extends the virtual network function to be extended.
  • the first network device receives an extended response message sent by the fourth network device, where the extended response message is used to indicate that the fourth network device completes expanding the virtual network function to be extended.
  • the fourth network device may be an NFVO.
  • the NSM&O may send a second extension request to the NFVO for requesting NFVO expansion and/or creating a new VNF, thereby implementing the network function of the target NSI to be extended.
  • the NFVO After receiving the second extension request of the NSM&O, the NFVO performs the expansion or/and the addition of the VNF.
  • the NFVO may send an extension response message to the NSM&O to indicate that the NFVO has completed the extension. Virtual network capabilities.
  • the method for the NSM&O to send the second extension request message to the NFVO can be applied to FIG.
  • the network management architecture 300 can also be applied to the network management architecture 500 shown in FIG. 5.
  • the method for sending the first extension request message to the VNFM for the NSM&O can be applied to the network management architecture 400 shown in FIG.
  • the method before the first network device sends the extended notification message to the fourth network device, the method further includes:
  • the first network device sends a second resource reservation request to the fourth network device, where the second resource reservation request is used to request to reserve resources for the network function to be extended.
  • the NSM&O sends a second resource reservation request to the NFVO, requesting the NFVO to reserve resources for the network function to be extended.
  • the method before the first network device sends the extended processing request to the second network device, the method further includes:
  • the first network device sends a second notification message to the sixth network device, where the second notification message is used to indicate that the first network device performs the extension processing on the network function to be extended;
  • the first network device receives a second acknowledgement message sent by the sixth network device according to the second notification message.
  • the sixth network device may be an NM.
  • NSM&O and NM can manage physical network functions and virtual network functions. Therefore, in order to avoid configuration conflicts, coordination between NSM&O and NM is required.
  • the NSM&O may notify the network function to be extended by the second notification message, and configure after receiving the third response message fed back by the NM.
  • the NSM&O may also configure the generated VNF in the NM to implement the network function to be extended.
  • the NSM&O may send an adjustment request to the NFVO for adjusting the network connection of the generated VNF connection target NSI in the NM.
  • NSM&O configures the generated VNF in the NM through EM.
  • the first network device sends a query message to the sixth network device, where the query message is used to query a network function that the fourth network device has generated;
  • the first network device sends a second notification message to the sixth network device, including:
  • the first network device sends a second notification message to the sixth network device according to the query response message.
  • the NSM&O can query the NM for the network function generated by the NM, mainly a virtual network function, because the physical network function can be directly managed by the NSM&O, and part of the configuration of the virtual network function may be stored only in the NM, and the NFVO stores Not completely. Therefore, the NSM&O needs to query the NM for existing network functions, and configure according to the feedback of the NM to avoid conflict with the NM.
  • the method further includes:
  • the first network device updates the information of the target NSI stored in the memory according to the configuration response message.
  • the NSM&O stores information of the PNF and/or VNF of the network function to be extended of the target NSI, and updates the VNF and/or PNF information of the target NSI in the memory, and simultaneously updates the PNF and the associated NSI. / or VNF information.
  • the method further includes: NSM&O The network function to be extended that feeds back the target NSI to the transmitting end is successfully extended.
  • FIG. 9 shows another method 900 for network slice instance extension according to an embodiment of the present invention.
  • the method 900 can be applied to the network management architecture 400 shown in FIG. 4, but the embodiment of the present invention is not limited thereto.
  • the NSM&O acquires an extension request of the network function of the target NSI to be extended, and the extension request expands the network function of the target NSI.
  • the NSM&O can receive an extension request of the network function to be extended of the target NSI sent by the sender.
  • the extension request may carry the identity of the sender, the service and/or function description of the network function to be extended, and the like.
  • the sender may be an operator, a third party client, an application involved in the communication service, or any other network entity that may send an extension request to the NSM&O.
  • the internal mechanism of the NSM&O can trigger an extension request of the network function of the target NSI to be extended.
  • NSM&O acts as a management and orchestration module for a network slice instance, and its internal management mechanism can trigger an extension request for the target NSI.
  • the NSM&O sends a first query request message to the storage device according to the extended request message, where the first query request message is used to query the storage device for the NSM&O to extend the right of the network function to be extended of the target NSI.
  • the NSM&O can also verify the identity of the sender device through the memory, and verify the integrity of the extended parameter in the extension request, for example, whether the target NSI format is correct, for the to-be-expanded
  • the service and/or function description format of the network function is correct.
  • the extension parameter included in the extension request sent by the sender device is incorrect or the network slice instance format is incorrect.
  • the NSM&O can feed back the extension failure message to the sender.
  • NSM&O can also check whether the target network slice instance exists and the target network slice instance running, or NSM&O checks whether the NSLD corresponding to the target network slice exists and the current state of the target network slice.
  • the NSM&O After the NSM&O obtains the extension request of the target NSI, the NSM&O associates the NSLD of the target NSI, and in conjunction with the NSLD, the NSM&O maps the function and/or service description in the target NSI to the VNF and/or PNF of the target NSI, and verifies the target. Whether NSI can be extended. If the target NSI does not exist, the NSM&O feeds back to the sender that the target NSI does not exist.
  • the NSM&O may not extend the target NSI to the sender device; if the target NSI can be extended, the NSM&O verifies whether the sender has the authority to perform the extension of the network function of the target NSI through the memory, and if the verification fails, NSM&O can feed back the extension failure to the sender.
  • the extension request is triggered by the NSM&O internal mechanism, the NSM&O associates with the NSLD of the target NSI and combines the NSLD to determine the VNF and/or PNF that the target NSI needs to extend. If the target NSI cannot be extended, NSM&O can feed back the network performance to the sender device.
  • the storage device sends a first verification response message to the NSM&O.
  • the verification response message is used to indicate whether the extension request sent by the sender device can pass.
  • NSM&O feeds back the expansion failure result to the sender.
  • the NSM&O determines whether the sending end has the right to extend the network function of the target NSI by performing authentication and authentication verification on the sending end, and if the extended request verification sent by the sending end fails, Then NSM&O fails to feed back the extension to the sender.
  • the extension request is triggered by the NSM&O internal mechanism, NSM&O determines whether the extension request of the target NSI can be extended. If the network function of the target NSI cannot be extended, Then, the NSM&O feeds back the extension failure to the sender device, and feeds back the network performance to the sender device.
  • step execution is to be S904, the entire expansion process ends, and the expansion fails.
  • the NSM&O determines the arrangement result of the network function of the target NSI to be extended according to the extension request.
  • the NSM&O determines the VNF and/or the PNF to be extended according to the extension request. For example, the NSM&O may determine whether to expand the VNF, add a VNF, extend the PNF, or add a PNF. Therefore, the configuration request of the network function to be extended is determined, including configuring a VNF, a new VNF, an extended VNF, or a new PNF.
  • the NSM&O can determine that the network function to be extended is a common network function that belongs to the target NSI and other slice instances, or belongs to the target NSI-specific network function.
  • step S906 is performed; if the NSM&O determines that the network function to be extended is the dedicated network function of the target NSI, step S906 may not be performed.
  • the NSM&O association shares the NSLD of the network slice instance other than the target NSI of the network function. It should be understood that other network slice instances where network functions are shared with the target NSI may be referred to as associated NSIs. After the NSM&O is combined with the NSLD of the associated NSI, it is determined whether the associated NSI is operating normally according to the content of the NSLD associated with the NSI.
  • the NSM&O sends a resource reservation request to the EM and/or VIM according to the orchestration result.
  • the NSM&O determines that the network function to be extended is a physical network function according to the scheduling result
  • the NSM&O sends a resource reservation request to the EM
  • the EM reserves resources for the physical network function to be extended according to the resource reservation request.
  • the NSM&O determines that the network function to be extended is a virtual network function according to the scheduling result
  • the NSM&O sends a resource reservation request to the VIM.
  • the VIM reserves resources for the virtual network function to be extended according to the resource reservation request, for example, computing resources. , storage resources or network resources.
  • the EM or the VIM receives the reservation request message, reserves network resources according to actual conditions, and feeds back the reservation result to the NSM&O.
  • the NSM&O sends a notification message to the sender according to the resource reservation result of the EM or the VIM. If the reservation fails, the notification message is used to indicate that the extension fails. Further, the notification message may also be carried. The reason for the expansion failure is that there is no resource.
  • step S908 the entire expansion process ends and the expansion result fails.
  • the NSM&O orchestration determines that the network function to be extended of the target NSI is implemented by the PNF, the NSM&O sends a configuration request to the EM, where the configuration request is used to configure the network function to be extended of the target NSI. .
  • the EM After receiving the configuration request sent by the NSM&O, the EM starts to perform configuration on the PNF that implements the network function to be extended.
  • the EM can be classified into four cases according to the NSM&O to configure the extended network function.
  • the EM is based on The NSM&O configuration request allows the PNF to allocate more resources to serve the target NSI and associated NSI.
  • the EM requests the configuration according to the NSM&O.
  • Added PNF configuration which can include target NSI and associated NSI. Parameters such as target NSI and associated NSI identification information, NSI monitoring information, and/or reporting information.
  • the configuration content may also include operating parameters of the target NSI and/or associated NSI, policy information, network connections of dedicated network functions of the associated NSI and/or target NSI, and the like.
  • the EM allocates more resources to the PNF according to the configuration request of the NSM&O. Used to serve the target NSI.
  • the EM configures the new PNF according to the NSM&O configuration request, the configuration
  • the content may include parameters of the target NSI, for example, identification information of the target NSI, monitoring information of the target NSI, and/or reporting information, and the like.
  • the configuration content may further include an operation parameter of the target NSI, policy information, a network connection of the target NSI-specific network function, and the like.
  • the EM may send a configuration response message to the NSM&O to indicate that the EM has completed the configuration of the network function to be extended.
  • step S911 the entire process of completing the entire target NSI to be extended network function is performed in step S911, and S923 to S925 may be directly executed. If the target NSI still has other network functions implemented. If the PNF is not configured, steps S909 to S911 are repeatedly executed.
  • the NSM&O sends an extension notification message to the VNFM, where the extension notification message includes an extended parameter of the VNF to be extended.
  • the NSM&O determines the scheduling result, which is to implement the virtual network function to be extended, including the VNF shared by the target NSI and the associated NSI, the VNF dedicated to the target NSI, the newly added VNF, or the newly added VNF.
  • the extended notification message sent by the NSM&O is used to notify the VNFM to implement the extended VNF instance, where the extended notification message includes the identity information of the VNF to be extended, the VNF characteristic parameter information, and other extended parameters, for example, the performance required to extend the VNF, Reserved resources, new or expanded virtual machine versions, etc.
  • the VNFM performs a feasibility check of the VNF extension according to the extension notification message.
  • the VNFM can verify whether the NSM&O is eligible to extend the VNF and check whether the extended parameters of the extended VNF sent by the NSM&O conform to the specification. Further, the VNFM can also modify the extended parameters sent by the NSM&O according to the check result, and feed back to the NSM&O, and the VNFM can also authorize the start of the VNF life cycle change.
  • the VNFM sends a feasibility check message to the NSM&O according to the check result, and the feasibility check message includes a feasibility check result of the extended VNF.
  • the VNFM can also feed back the VNF modified parameters to be extended to the NSM&O through the feasibility check message, and expand the specific resources required by the VNF.
  • the NSM&O sends a resource allocation request to the VIM according to the feasibility check message sent by the VNFM, and the resource allocation request is used to request to allocate a virtual resource for the virtual network function to be extended.
  • the NSM&O may obtain the parameter of the VNF instance to be extended by the VNFM to be extended in the feasibility check message, and the NSM&O sends a resource allocation request to the VIM according to the updated parameter of the VNFM. Allocate the required resources for capacity expansion or new VNF. It should be understood that the resources allocated for the VNF to be extended may be resources reserved for the network function to be extended in step S907, for example, computing resources, storage resources, network resources, and the like.
  • the VIM can also receive an internal connection request sent by the SNM&O to adjust the internal connection for the new VNF.
  • This internal connection can be added to the VNF internal structure for the newly created virtual machine, or the new VNF can be connected to other network functions.
  • the VIM performs resource allocation for the network function to be extended.
  • the VIM performs resource allocation for the network function to be extended, and can be classified into the following four cases.
  • the VIM allocates resources for expanding the VNF according to the resource allocation request of the NSM&O.
  • the VIM can first configure the internal network connection, then use the allocated resources to establish a virtual machine, and join the newly created virtual machine to the network.
  • the VIM uses the allocated resources to establish a virtual machine, and establishes a network connection for the virtual machine to join the dedicated network of the target NSI. .
  • the VIM uses the allocated resources to establish a virtual machine, in which case the VIM not only establishes the virtual machine.
  • the connection with other shared network functions may also establish a connection of the target NSI-specific network function.
  • the VIM may also need to establish a connection with the associated NSI-specific network function, which is not limited in this embodiment of the present invention.
  • the VIM sends a resource allocation response message to the NSM&O, where the resource allocation response message is used to indicate the VIM to complete the allocation of the virtual resource.
  • the VIM when the VIM adds a virtual machine to an existing VNF or creates a new VNF, the VIM also establishes a network connection for the newly created virtual machine.
  • the NSM&O sends a first notification message to the VNFM, the first notification message is used to indicate that the VIM has completed the allocation of the virtual resource.
  • the SNM&O notifies the VNFM that the VIM has completed the allocation of the virtual resources through the first notification message, and establishes an internal network connection.
  • the VNFM After receiving the first notification message to be sent by the NBSM&O, the VNFM starts to configure a lifecycle parameter for the newly created VIM or the expanded VNF, and deploys parameters for the newly created VNF or the expanded VNF, such as the identity of the VNF.
  • the VNFM sends a management request to the EM to request the EM to manage the newly created VNF.
  • the VNFM sends an extension response message to the NSM&O, the extended response message being used to notify the extended VNF of completion.
  • NSM&O sends a configuration request to the EM for configuring the VNF.
  • the EM After receiving the configuration request sent by the NSM&O, the EM starts to execute the application parameter for configuring the VNF.
  • the configuration of the VNF according to the configuration request of the NSM&O can be classified into the following three cases:
  • the EM performs the work for the VNF.
  • the configuration can be configured with the operation policy adjustment, but the embodiment of the present invention is not limited thereto.
  • the EM configures relevant parameters of the target NSI and the associated NSI, for example, the identity of the target NSI and the associated NSI, the operational parameters to be monitored and reported, and the VNF. Specifically executed functions, operation strategies, and the like, but the embodiment of the present invention is not limited thereto.
  • the EM configures parameters related to the target NSI, for example, the identity of the target NSI, the operational parameters to be monitored and reported, and the functions and operations performed by the VNF. Strategy and the like, but the embodiment of the invention is not limited thereto.
  • the EM may send a configuration response message to the NSM&O to indicate that the EM has completed the configuration of the network function to be extended.
  • the NSM&O sends an activation port request to the EM to request the EM to open the virtual port of the newly added VNF, which is to be extended.
  • Network features provide services.
  • the NSM&O may also send an update request to the storage device for requesting the memory update to implement the VNF and/or PNF information of the target NSI to be extended network function.
  • the storage device updates the VNF information of the target NSI in the memory according to the update request of the NSM&O. Further, if the shared network function is to be extended, the storage device simultaneously updates the VNF and/or PNF information in the associated NSI.
  • the NSM&O feeds back to the sending end that the network function extension of the target NSI to be extended is successful.
  • FIG. 10 is a method 1000 of another network slice instance extension according to an embodiment of the present invention.
  • the method 1000 may be applied to the network architecture 300 of FIG. 3, but the embodiment of the present invention is not limited thereto.
  • NFVO exists in the network architecture 300. Therefore, when the network function to be extended is implemented by the VNF, the NSM&O can interact with the NFVO, that is, the NSM&O can request NFVO to expand or newly implement the network function to be extended. VNF instance.
  • the method flow for implementing the network function to be extended by the PNF is the same as the method 900. Therefore, steps S1001 to S1006 are the same as S901 to S906 in the method 900, and steps S1008 to S1011 are the same as S908 and S911 in the method 900. For the sake of brevity of the application file, details are not described herein again.
  • the NSM&O sends a resource reservation request to the EM and/or NFVO according to the arrangement result.
  • the NSM&O determines that the network function to be extended is a physical network function according to the scheduling result
  • the NSM&O sends a resource reservation request to the EM
  • the EM reserves resources for the physical network function to be extended according to the resource reservation request.
  • the NSM&O determines that the network function to be extended is a virtual network function according to the scheduling result
  • the NSM&O sends a resource reservation request to the NFVO, and accordingly, the NFVO reserves resources for the virtual network function to be extended according to the resource reservation request, for example, computing resources. , storage resources or network resources.
  • the EM or the NFVO receives the reservation request message, reserves network resources according to actual conditions, and feeds back the reservation result to the NSM&O.
  • NFVO acts as a network function virtualization orchestrator, responsible for network services, VNF lifecycle management and optimizing network resources from a global perspective.
  • the NSM&O sends an extension notification message to the NFVO, the extension notification message is used to notify the NFVO to extend the virtual network function to be extended.
  • the NFVO performs an extension to implement the VNF that implements the network function to be extended.
  • the NFVO sends an extension response message to the NSM&O, the extended response message is used to indicate that the NFVO completes the VNF that extends the network function to be extended.
  • S1015 is the same as S920 in the method 900, and S1016 to S1020 are the same as S922 to S926 in the method 900.
  • S1016 to S1020 are the same as S922 to S926 in the method 900.
  • FIG. 11 is a method 1100 of another network slice instance extension according to an embodiment of the present invention.
  • the method 1100 can be applied to the network architecture 500 shown in FIG. 5, but the embodiment of the present invention is not limited thereto.
  • the NSM&O sends a query message to the NM, where the query message is used to query the network function that the NM has generated.
  • the NSM&O can query the network function generated by the NM by sending a query message to the NM.
  • the network function here can be a VNF, because the NSM&O can directly manage the PNF, and some configurations of the VNF managed by the NM are only Stored in NM, that is, the information stored by NFVO does not contain parameters of the network function at the functional level.
  • NSM&O may also query the availability of network functions that have been generated in the NM and reserve the network functionality. It should be understood that the network function here is mainly a VNF that has been generated by the NM. When the NSM&O determines that the generated VNF in the NM is available, the NM can be notified to reserve the VNF.
  • the NM sends a query response message to the NSM&O to notify the network function that has been generated in the NM.
  • Step S1109 is the same as S907 in the method 900.
  • Step S1109 is the same as S907 in the method 900.
  • the NSM&O sends a second notification message to the NM, the second notification being used to notify the NSM&O to configure the network function to be extended.
  • the NM sends a second notification confirmation message to the NSM&O.
  • NM and NSM&O can be prevented from configuring the extended network functions at the same time to avoid conflicts.
  • Steps S1113 to S1115 are the same as S909 to S911 in the method 900.
  • details are not described herein again.
  • the NSM&O sends an existing VNF request in the configuration NM to the NFVO.
  • the VNF generated in the NM can be utilized in the NM.
  • the NSM&O sends an existing VNF request in the configuration NM to the NFVO, and the NFVO adjusts and/or creates a network connection of the VNF connection target NSI according to the request.
  • step S1121 may be performed, NSM&O to EM
  • the configuration request is sent, and the request is configured for the newly added VNF.
  • the configuration content is the same as that in S922 in the method 900, and details are not described herein again.
  • the NSM&O can also expand and/or create the VNF by using the NFVO.
  • the specific implementation steps S1117 to S1119 are the same as the S1012 to S1014 in the method 1000, and details are not described herein again.
  • S1120 to S1122 are the same as S920 to S922 in the method 900, and S1125 to S1126 are the same as S925 to S926 in the method 900, and are not described herein again.
  • the NSM&O sends a configuration completion notification message to the NM to notify the NM that the NSM&O is configured to implement the specific content of the network function to be extended.
  • FIG. 12 is a method 1200 of another network slice instance extension according to an embodiment of the present invention.
  • the method 1200 may be applied to the network architecture 600 shown in FIG. 6, but the embodiment of the present invention is not limited thereto.
  • S1201 to S1208 in the method 1200 are the same as the S901 to S908 in the method 900, and are not described here.
  • Steps S1209 to S1210 are the same as S1111 to S1112 in the method 1100, and are not described herein again;
  • S1211 to S1213 and S900 in the method 900 S911 is the same, and is not described here.
  • S1215 to S1229 are the same as S912 to S926 in the method 900, and are not described here.
  • the NSM&O sends a configuration completion notification message to the NM, and the configuration completion notification message is used to notify the NM that the NSM&O completes the configuration of the PNF. Further, the NSM&O can notify the NMS&O through the configuration completion notification message that the configuration content of the PNF that implements the network function to be extended is specifically.
  • FIG. 13 is a schematic block diagram of a network device 1300 according to an embodiment of the present invention. It should be understood that the network device 130 is capable of performing the various steps performed by the NSM&O in the methods of FIGS. 1 through 12, and to avoid repetition, will not be described in detail herein.
  • Network device 1300 includes:
  • the obtaining unit 1310 is configured to acquire an extension request of the target slice instance NSI, where the extension request is used to request to extend the network function of the target NSI;
  • the sending module 1320 is configured to send, according to the extension request, a configuration request to the second network device, where the configuration request is used to request to configure a network function to be extended for the target NSI;
  • the receiving module 1330 is configured to receive a configuration response message sent by the second network device according to the configuration request, where the configuration response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method for extending the network splicing instance provided by the embodiment of the present invention can realize the expansion of the function of the network sharding instance by the unified management of the physical resource and the virtual resource, and further improve the resource utilization efficiency and the overall network. performance.
  • the network device further includes: a determining module, configured to determine, before the sending module sends the configuration request to the second network device, that the network function to be extended is the target NSI-specific network function ;
  • the network function to be extended is the target NSI and the associated NSI shared network function
  • the associated NSI is an NSI that uses the shared network function together with the target NSI.
  • the network device further includes: an association module, configured to associate, when the determining module determines that the network function to be extended is the target NSI and the associated NSI shared network function Associate the NSI NSLD so that the network function to be extended complies with the requirements of the associated NSI;
  • the determining module of the network device is further configured to determine, according to the NSLD of the associated NSI, operation information of the associated NSI.
  • the determining module of the network device is specifically configured to: if the network function to be extended is a physical network function, determine the configuration request according to the extension request, where the configuration request includes configuration Configuration information of the network function to be extended.
  • the sending module of the network device is further configured to: if the network function to be extended is a virtual network function, send an extended notification message to the third network device and/or the fourth network device, The extended notification message is used to instruct the third network device and/or the fourth network device to extend the VNF that implements the virtual network function to be extended;
  • the receiving module is further configured to: before the receiving module receives the extended response message sent by the third network device, receive the feasibility of sending, by the third network device, according to the extended notification message. Checking the message, the feasibility check message includes a feasibility check result of expanding the VNF.
  • the sending module of the network device is specifically configured to: send, according to the feasibility check message, a resource allocation request to the fifth network device, where the resource allocation request is used for the request to be extended Virtual network function allocates virtual resources;
  • the receiving module is specifically configured to: receive a resource allocation response message sent by the fifth network device, where the resource allocation response message is used to instruct the fifth network device to complete the allocation of the virtual resource.
  • the sending module of the network device is further configured to: send, according to the resource allocation response message, a first notification message to the third network device, where the first notification message is used to indicate the Five network devices complete the allocation of the virtual resources;
  • the receiving module is further configured to: receive an extended response message that is sent by the third network device according to the first notification message.
  • the sending module of the network device is further configured to: send, to the fifth network device, a first resource reservation request, where the first resource reservation request is used for the request Extended network features reserve resources.
  • the sending module of the network device is further configured to send, after the sending module sends the extended notification message, a second resource reservation request to the fourth network device, where The second resource reservation request is used to request to reserve resources for the network function to be extended.
  • the sending module of the network device is further configured to: send a second notification message to the sixth network device, where the second notification message is used to indicate that the first network device is to The network function to be extended is extended;
  • the receiving module is further configured to: receive a second notification confirmation message that is sent by the sixth network device according to the second notification message.
  • the sending module of the network device is further configured to: send a query message to the sixth network device, where the query message is used to query a network function that the fourth network device has generated;
  • the receiving module is further configured to: receive a query response message sent by the sixth network device, where the query response message is used to feed back configuration information of a network function that has been generated by the sixth network device;
  • the sending module is specifically configured to: send, according to the query response message, a second notification message to the sixth network device.
  • the sending module of the network device is further configured to: send, to the sixth network device, the network function configuration complete message to be extended, where the network function configuration complete message includes the to-be-expanded Configuration parameters for the network function.
  • the network device further includes: an update module, configured to update information of the target NSI stored in the memory according to the configuration response message.
  • FIG. 14 is a schematic structural block diagram of a network device 1400 according to an embodiment of the present invention. It should be understood that the network device 1400 can perform the various steps performed by the EM in the methods of FIGS. 1 through 12, and to avoid repetition, it will not be described in detail herein.
  • Network device 1400 includes:
  • the receiving module 1410 is configured to receive a configuration request sent by the first network device, where the configuration request is used to request to configure a network function to be extended for the target network slice instance NSI.
  • the processing module 1420 is configured to configure, according to the configuration request, a network function to be extended of the target NSI.
  • the sending module 1430 is configured to send a configuration response message to the first network device, where the configuration response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method for managing network slicing provided by the embodiment of the present invention can realize the expansion of the network slicing instance and improve the resource utilization efficiency and the overall network performance by the unified management of the physical resource and the virtual resource.
  • the sending module of the network device is further configured to: if the network function to be extended is a virtual network function, receive a management request message sent by the third network device, where the management request message is used by The second network device is requested to manage a virtual network function VNF that implements the network function to be extended.
  • the receiving module of the network device is further configured to: receive a notification message sent by the first network device, where the notification message is used to indicate that the second network device is turned on for the The extended network function serves the port of the VNF.
  • FIG. 15 is a schematic structural block diagram of a network device 1500 according to another embodiment of the present invention. It should be understood that the network device 1500 can perform the various steps performed by the NSM&O in the methods of FIGS. 1 through 12, and to avoid repetition, it will not be described in detail herein.
  • Network device 1500 includes:
  • a memory 1530 configured to store a program
  • a transceiver 1520 configured to communicate with other devices
  • the processor 1510 is configured to execute a program in the memory 1530, and the processor 1510 is respectively connected to the memory 1530 and the transceiver 1520 for executing the instruction stored by the memory 1530.
  • the processor 1510 is configured to acquire an extension request of the target slice instance NSI, where the extension request is used to request to extend the network function of the target NSI;
  • the transceiver 1520 is configured to send, according to the extension request, a configuration request to the second network device, where the configuration request is used to request to configure a network function to be extended for the target NSI;
  • the transceiver is further configured to receive a configuration response message sent by the second network device according to the configuration request, where the configuration response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method for extending a network slice instance provided by the embodiment of the present invention by using physical resources and virtual resources Unified management can extend the function of the network slicing instance and further improve the resource utilization efficiency and overall network performance.
  • the processor of the network device is further configured to: before the sending module sends the configuration request to the second network device, determine that the network function to be extended is the target NSI-specific network function; Or determining that the network function to be extended is the target NSI and the associated NSI shared network function, and the associated NSI is an NSI that uses the shared network function together with the target NSI.
  • the processor of the network device is further configured to associate the association if the determining module determines that the network function to be extended is the target NSI and the associated NSI shared network function NSI's NSLD, so that the network functions to be extended meet the requirements of the associated NSI;
  • the processor of the network device is further configured to determine, according to the NSLD of the associated NSI, operation information of the associated NSI.
  • the processor of the network device is specifically configured to: if the network function to be extended is a physical network function, determine the configuration request according to the extension request, where the configuration request includes configuration Configuration information of the network function to be extended.
  • the transceiver of the network device is further configured to: if the network function to be extended is a virtual network function, send an extended notification message to the third network device and/or the fourth network device, where The extended notification message is used to instruct the third network device and/or the fourth network device to extend the VNF that implements the virtual network function to be extended;
  • the transceiver is further configured to: receive an extended response message sent by the third network device and/or the fourth network device, where the extended response message is used to indicate that the third network device and/or the fourth network device complete the extension Said VNF.
  • the transceiver of the network device is further configured to: before the receiving module receives the extended response message sent by the third network device, receive, by the third network device, according to the extended notification message.
  • the feasibility check message includes the feasibility check result of expanding the VNF.
  • the transceiver of the network device is specifically configured to: send, according to the feasibility check message, a resource allocation request to the fifth network device, where the resource allocation request is used for the request to be extended Virtual network function allocates virtual resources;
  • the transceiver is specifically configured to: receive a resource allocation response message sent by the fifth network device, where the resource allocation response message is used to instruct the fifth network device to complete the allocation of the virtual resource.
  • the transceiver of the network device is further configured to: send, according to the resource allocation response message, a first notification message to the third network device, where the first notification message is used to indicate the Five network devices complete the allocation of the virtual resources;
  • the transceiver is further configured to: receive an extended response message that is sent by the third network device according to the first notification message.
  • the transceiver of the network device is further configured to: send, to the fifth network device, a first resource reservation request, where the first resource reservation request is used for the request Extended network features reserve resources.
  • the transceiver of the network device is further configured to: after the sending module sends the extended notification message, send a second resource reservation request to the fourth network device, where The second resource reservation request is used to request to reserve resources for the network function to be extended.
  • the transceiver of the network device is further configured to: send the second pass to the sixth network device.
  • the second notification message is used to indicate that the first network device performs an extension process on the network function to be extended;
  • the transceiver is further configured to: receive a second notification confirmation message that is sent by the sixth network device according to the second notification message.
  • the transceiver of the network device is further configured to: send a query message to the sixth network device, where the query message is used to query a network function that the fourth network device has generated;
  • the transceiver is further configured to: receive a query response message sent by the sixth network device, where the query response message is used to feed back configuration information of a network function that has been generated by the sixth network device;
  • the transceiver is specifically configured to send a second notification message to the sixth network device according to the query response message.
  • the transceiver of the network device is further configured to: send, to the sixth network device, the network function configuration completion message to be extended, where the network function configuration completion message includes the to-be-expanded Configuration parameters for the network function.
  • the processor of the network device is further configured to: update the information of the target NSI stored in the memory according to the configuration response message.
  • FIG. 16 is a schematic structural block diagram of a network device 1600 according to an embodiment of the present invention. It should be understood that the network device 1600 is capable of performing the various steps performed by the EM in the methods of FIGS. 1 through 12, and to avoid repetition, will not be described in detail herein.
  • Network device 1600 includes:
  • a memory 1630 configured to store a program
  • a transceiver 1620 configured to communicate with other devices
  • the processor 1610 is configured to execute a program in the memory 1630, and the processor 1610 is coupled to the memory 1630 and the transceiver 1620, respectively, for executing the instructions stored by the memory 1630.
  • the transceiver 1620 is configured to receive a configuration request sent by the first network device, where the configuration request is used to request to configure a network function to be extended for the target network slice instance NSI.
  • the processor 1610 is configured to configure, according to the configuration request, a network function to be extended of the target NSI.
  • the transceiver 1620 is further configured to send a configuration response message to the first network device, where the configuration response message is used to indicate that the second network device has completed configuration of the network function to be extended.
  • the method for managing network slicing provided by the embodiment of the present invention can realize the expansion of the network slicing instance and improve the resource utilization efficiency and the overall network performance by the unified management of the physical resource and the virtual resource.
  • the transceiver of the network device is further configured to: if the network function to be extended is a virtual network function, receive a management request message sent by the third network device, where the management request message is used by The second network device is requested to manage a virtual network function VNF that implements the network function to be extended.
  • the transceiver of the network device is further configured to: receive a notification message sent by the first network device, where the notification message is used to indicate that the second network device is turned on for the The extended network function serves the port of the VNF.
  • the processor of the foregoing network device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration.
  • the general purpose processor can be a microprocessor or the processor can also Is any conventional processor, etc.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or performed by a combination of hardware and software units in the processor.
  • the software unit can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the disclosed system, network device, and method may be implemented in other manners.
  • the network device embodiments described above are only 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 it can be integrated 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, network 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 invention.
  • 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, may be stored in a computer readable storage medium.
  • the storage medium includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • 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)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Selon des modes de réalisation, la présente invention concerne un procédé d'extension d'une tranche de réseau, des dispositifs de réseau, et une architecture de réseau. Le procédé consiste : en ce qu'un premier dispositif de réseau obtient une requête d'extension d'une instance de tranche de réseau (NSI) cible, la requête de configuration servant à demander l'extension d'une fonction de réseau de la NSI cible ; en ce que le premier dispositif de réseau envoie une requête de configuration à un deuxième dispositif de réseau en fonction de la requête d'extension, la requête d'extension servant à demander la configuration d'une fonction de réseau à étendre de la NSI cible ; en ce que le premier dispositif de réseau reçoit un message de réponse de configuration envoyé par le deuxième dispositif de réseau en fonction de la requête de configuration, le message de réponse de configuration servant à indiquer que le deuxième dispositif de réseau a terminé la configuration de la fonction de réseau à étendre. Le procédé d'extension d'une instance de tranche de réseau et les dispositifs de réseau selon les modes de réalisation de la présente invention peuvent mettre en œuvre l'extension d'une fonction de réseau d'une instance de tranche de réseau au moyen d'une programmation et d'une gestion unifiées sur des ressources physiques et des ressources virtuelles, améliorant ainsi l'ergonomie et économisant des ressources de réseau.
PCT/CN2017/107625 2016-11-03 2017-10-25 Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau WO2018082491A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610954059.3 2016-11-03
CN201610954059.3A CN108024255A (zh) 2016-11-03 2016-11-03 扩展网络切片实例的方法和网络设备

Publications (1)

Publication Number Publication Date
WO2018082491A1 true WO2018082491A1 (fr) 2018-05-11

Family

ID=62070080

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107625 WO2018082491A1 (fr) 2016-11-03 2017-10-25 Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau

Country Status (2)

Country Link
CN (1) CN108024255A (fr)
WO (1) WO2018082491A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557270B (zh) * 2018-05-31 2021-10-22 华为技术有限公司 一种网络切片的管理方法及装置
CN110572272B (zh) 2018-06-06 2020-11-06 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排系统
US11750447B2 (en) 2018-06-15 2023-09-05 Telefonaktiebolaget Lm Ericsson (Publ) Configuring a network slice
CN110769458B (zh) * 2018-07-27 2021-09-07 华为技术有限公司 通信方法、接入网设备和终端设备
CN109005233B (zh) * 2018-08-10 2021-08-03 北京邮电大学 服务链建立方法
CN111404704B (zh) * 2019-01-02 2023-05-09 中国移动通信有限公司研究院 Vnf扩缩容方法及装置、网元及存储介质
CN110750327A (zh) * 2019-09-05 2020-02-04 中移（杭州）信息技术有限公司 虚拟网络功能的管理方法及系统、代理装置、存储介质
CN112671549A (zh) * 2019-10-16 2021-04-16 华为技术有限公司 一种数据处理方法、设备及系统
CN115211159A (zh) * 2020-03-04 2022-10-18 上海诺基亚贝尔股份有限公司 网络切片的分配资源
CN111555910B (zh) * 2020-04-22 2023-01-03 北京思特奇信息技术股份有限公司 一种基于网络切片的自愈自运维方法和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650437A (zh) * 2013-06-28 2014-03-19 华为技术有限公司 任播服务注册、实现方法及装置、交换设备和系统
US20140351780A1 (en) * 2013-05-24 2014-11-27 Nvidia Corporation System and method for configuring a channel
CN105391568A (zh) * 2014-09-05 2016-03-09 华为技术有限公司 一种软件定义网络sdn的实现方法、装置和系统
CN105471954A (zh) * 2014-09-11 2016-04-06 北京智梵网络科技有限公司 基于sdn网络的分布式控制系统与用户流量优化方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812171B (zh) * 2014-12-31 2019-06-11 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备
US10491525B2 (en) * 2015-03-10 2019-11-26 Huawei Technologies Co., Ltd. Traffic engineering feeder for packet switched networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140351780A1 (en) * 2013-05-24 2014-11-27 Nvidia Corporation System and method for configuring a channel
CN103650437A (zh) * 2013-06-28 2014-03-19 华为技术有限公司 任播服务注册、实现方法及装置、交换设备和系统
CN105391568A (zh) * 2014-09-05 2016-03-09 华为技术有限公司 一种软件定义网络sdn的实现方法、装置和系统
CN105471954A (zh) * 2014-09-11 2016-04-06 北京智梵网络科技有限公司 基于sdn网络的分布式控制系统与用户流量优化方法

Also Published As

Publication number Publication date
CN108024255A (zh) 2018-05-11

Similar Documents

Publication Publication Date Title
WO2018082491A1 (fr) Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
CN108632058B (zh) 网络切片的管理方法和装置
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
EP3648401B1 (fr) Procédé, dispositif, système et support de stockage lisible par ordinateur de gestion de tranche de réseau
WO2018001066A1 (fr) Procédé et appareil de gestion de tranche de réseau
WO2018082477A1 (fr) Procédé et dispositif de gestion d'instance de tranche de réseau
CN109417719B (zh) 一种网络资源的管理方法、装置及系统
WO2018058579A1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
WO2018171465A1 (fr) Procédé, appareil et système pour gérer une instance de tranche de réseau
CN109314696B (zh) 管理网络切片的方法及其装置
WO2017181875A1 (fr) Procédé de déploiement de réseau virtualisé et système de déploiement
JP2017517170A (ja) Ｎｆｖシステムにおけるサービス実装のための方法および通信ユニット
WO2016007813A1 (fr) Délégation de serveur de gestion en couches
WO2018082487A1 (fr) Procédé, dispositif et système de gestion de tranches de réseau
CN107222321B (zh) 一种配置报文发送方法及装置
WO2018090191A1 (fr) Procédé de gestion, unité et système de gestion destinés à une fonction de réseau
WO2018082545A1 (fr) Procédé, appareil et système de rétraction d'instance de tranche de réseau
US20230232228A1 (en) Method and apparatus for establishing secure communication
WO2019100924A1 (fr) Procédé et dispositif de garantie de performance de réseau
WO2018107480A1 (fr) Procédé et système de planification de service
WO2018000393A1 (fr) Procédé, dispositif, et système de gestion de tranche de réseau

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: 17868090

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17868090

Country of ref document: EP

Kind code of ref document: A1