WO2019184967A1 - 一种网络切片的部署方法及装置 - Google Patents

一种网络切片的部署方法及装置 Download PDF

Info

Publication number
WO2019184967A1
WO2019184967A1 PCT/CN2019/080026 CN2019080026W WO2019184967A1 WO 2019184967 A1 WO2019184967 A1 WO 2019184967A1 CN 2019080026 W CN2019080026 W CN 2019080026W WO 2019184967 A1 WO2019184967 A1 WO 2019184967A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
nsd
deployment
service
service requirement
Prior art date
Application number
PCT/CN2019/080026
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to EP19774607.6A priority Critical patent/EP3720050B1/en
Priority to KR1020207018552A priority patent/KR102409142B1/ko
Priority to JP2020554359A priority patent/JP7074880B2/ja
Priority to BR112020013497-0A priority patent/BR112020013497A2/pt
Publication of WO2019184967A1 publication Critical patent/WO2019184967A1/zh
Priority to US16/901,195 priority patent/US11283684B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time

Definitions

  • the present application relates to the field of information technology, and in particular, to a method and an apparatus for deploying a network slice.
  • Network function virtualization refers to the use of common hardware devices and virtualization technologies to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive cost of deploying dedicated devices.
  • the software is not tied to proprietary hardware, making network device functionality no longer dependent on dedicated hardware.
  • the characteristics of cloud computing are utilized, so that resources can be fully and flexibly shared, real-time development and deployment of new services, and automatic deployment, elastic scaling, fault isolation, and self-healing based on actual business requirements.
  • the party that receives the instantiation request and instantiates the corresponding service according to the request is called a virtualization service provider (referred to as a service provider), and the party that initiates the instantiation request is called Business requester.
  • the virtualized network service (NS) in the NFV may be an internet protocol multimedia subsystem (IMS) network service, or an evolved packet core (EPC). service.
  • An NS can contain several virtualized network function (VNF) modules, also called virtualized network elements.
  • VNF virtualized network function
  • the service requester first needs to submit the network service descriptor (NSD) to the service provider.
  • the description of the network service is also called the NS deployment template, which mainly includes describing the network.
  • the virtual link descriptor (VLD) is used in the topology information to describe the connection between the VNFs.
  • VNFD is a description of the VNF, also known as the deployment template of the VNF.
  • NST network slice template
  • DF NS deployment preferences
  • each NS DF corresponds to a service application type.
  • the VNFD can also contain several deployment preferences, each VNFD DF corresponding to the attributes of the network function.
  • NST's alternative creation options are theoretically possible combinations of all of the above NS DFs and all VNFD DFs. These combination options are listed in the NST for deployment of the slice instance. We call this NSD. DF.
  • the corresponding NSDs include multiple NS DFs.
  • each network element has multiple VNFD DFs. This will result in a very large number of NSD DFs in the NST, which makes the design of the NST very complicated and difficult to maintain.
  • the embodiment of the present application provides a method for deploying a network slice, which is used to solve the technical problem that the design of the NST is complicated and difficult to maintain.
  • the NSD DF involved in the embodiment of the present application may refer to various differentiated network features that are selectively implemented when using NSD for NFV deployment.
  • the differences in the network characteristics may be reflected in the network functions of the network, the topological relationships between the network functions (such as the connection relationship, the connection attribute information), and the number and requirements of the network functions, which are not limited.
  • the embodiment of the present application provides a method for deploying a network slice, which can be performed by an NSMF network element, where the method includes:
  • Obtaining network slice requirement information where the network slice requirement information includes a service requirement that the network slice instance NSI to be deployed needs to bear;
  • the network function information corresponding to the service requirement includes any one or any combination of the following: one or more network functions corresponding to the service requirement The connection relationship of the plurality of network functions corresponding to the service requirement, the connection attribute information of the plurality of network functions corresponding to the service requirement, and the requirement of one or more network functions corresponding to the service requirement;
  • a rule that the network service instantiation needs to satisfy includes any one or any combination of the following: an identifier of one or more virtualized network function VNFs included in the NSD, and multiple VNFs included in the NSD.
  • the NFV network element generates an NFV deployment policy according to the network slice requirement information, and the deployment preference that meets the customer order is directly selected from all deployment preferences of the NSD listed in the NST.
  • the NST it is not necessary to associate all the deployment preferences of the NSD with the parameter combinations in the customer order, thereby eliminating the coupling with the NSD deployment preference and the deployment preference of the VNFD in the NST, which greatly simplifies the NST. Difficult to design and maintain.
  • the determining the identifier and network function information of the NSD corresponding to the service requirement includes:
  • NST Determining a network slice template NST that matches the service requirement, where the NST includes an NSD corresponding to the service requirement or an identifier of the NSD, and network function information corresponding to the service requirement;
  • the NSD corresponding to the service requirement and the NST matching the service requirement may be respectively determined, where the NST includes network function information corresponding to the service requirement, in which case, in the NST The NSD corresponding to the service requirement or the identifier of the NSD may not be included.
  • the identifier of the one or more VNFs included in the NSD is obtained according to one or more network functions corresponding to the service requirement, and the connection relationship between the multiple VNFs included in the NSD is Obtaining, according to the connection relationship of the multiple network functions corresponding to the service requirement, the connection attribute information between the multiple VNFs included in the NSD is obtained according to the connection attribute information of the multiple network functions corresponding to the service requirement.
  • the rules that need to be met in each parameter of the VNFD used by each VNF of the one or more VNFs included in the NSD are obtained according to requirements of one or more network functions corresponding to the service requirements.
  • the identifier of the one or more VNFs included in the NSD is obtained according to one or more network functions corresponding to the service requirement, that is, one or more corresponding to the service requirements in the NST.
  • Network function identifies the identity of one or more VNFs used in network virtualization deployment.
  • the identifier of the VNF may be determined according to a connection endpoint (ie, a certain network function) included in the connection relationship information of multiple network functions corresponding to the service requirement.
  • connection relationship between the multiple VNFs included in the NSD is obtained according to the connection relationship of multiple network functions corresponding to the service requirement, that is, corresponding to the service requirement in the NST.
  • connection attribute information between the multiple VNFs included in the NSD is obtained according to the connection attribute information of multiple network functions corresponding to the service requirement, that is, in order to satisfy the service in the NST.
  • the service connection attribute between multiple network functions corresponding to the requirement requires that the network connection between the VNFs that need to be established during network virtualization deployment should have attributes.
  • the connection attribute information between the multiple VNFs may also be determined according to the requirement of the network function according to the service requirement, for example, determining the connection attribute information between the deployed VNF according to the performance and capacity requirements of the two network functions as the connection endpoint. .
  • the NSF includes a rule that needs to be met in each parameter of the VNFD used by each VNF of the one or more VNFs, that is, in order to deploy the NST corresponding to the service requirement.
  • deploying VNF is a parameter that should be used.
  • the method further includes:
  • the requirement of one or more network functions corresponding to the service requirement is sent to the network function management function NFMF network element.
  • the NSMF network element may not have the function of the NFMF network element, that is, in the specific implementation, the NSMF network element and the NFMF network element are respectively set.
  • the method further includes:
  • a deployment preference that satisfies a rule that the network service instantiation needs to satisfy is selected from the deployment preferences of the NSD.
  • the NSMF network element directly selects the deployment preference of the NFV deployment policy from the deployment preference of the obtained NSD according to the NFV deployment policy.
  • the NSMF network element has both the PAP and the PF functions.
  • the method further includes:
  • the NFV deployment policy is sent to the policy function network element.
  • the NSMF network element has the function of the PAP, and the generated NFV deployment policy sends the policy function network element, and the policy function network element implements the PF function.
  • an embodiment of the present application provides a method for deploying a network slice, where the method includes:
  • the satisfied rule includes any one or any combination of the following: an identifier of one or more virtualized network function VNFs included in the NSD, a connection relationship between a plurality of VNFs included in the NSD, and the NSD include Connection attribute information between a plurality of VNFs, rules required to satisfy various parameters in the VNFD used by each of the one or more VNFs included in the NSD.
  • a deployment preference that satisfies a rule that the network service instantiation needs to satisfy is selected from the deployment preferences of the NSD.
  • the NFV network element generates an NFV deployment policy according to the network slice requirement information, and sends the NFV deployment policy to the policy function network element.
  • the policy function network element can select the deployment preference according to the NFV deployment policy; compared to the prior art.
  • the embodiment of the present application provides a method for deploying a network slice, where the method includes:
  • a VNF deployment policy is generated according to the requirements of the one or more network functions, and the VNF deployment policy includes rules that need to be met by parameters in the VNFD used by each VNF of one or more VNFs.
  • the parameters of each parameter in the VNFD used by each VNF of one or more VNFs need to be met, that is, the parameters of the VNFD used to deploy the requirements of the one or more network functions need to be met. rule. That is, the one or more VNFs correspond to the one or more network functions.
  • the method further includes:
  • a deployment preference that satisfies a rule that needs to be met by the parameters is selected from deployment preferences of the VNFD used by each VNF.
  • the embodiment of the present application provides a method for deploying a network slice, where the method includes:
  • VNF deployment policy includes a rule that needs to be met in each parameter of the VNFD used by each VNF of one or more VNFs;
  • a deployment preference that satisfies a rule that needs to be met by the parameters is selected from deployment preferences of the VNFD used by each VNF.
  • the embodiment of the present application provides an NSMF network element, where the network slice management function network element includes:
  • An acquiring module configured to acquire network slice requirement information, where the network slice requirement information includes a service requirement that the network slice instance NSI to be deployed needs to bear;
  • a determining module configured to determine a network service deployment template NSD and network function information corresponding to the service requirement, where the network function information corresponding to the service requirement includes any one or any combination of the following: one corresponding to the service requirement Or a plurality of network functions, a connection relationship of the plurality of network functions corresponding to the service requirement, connection attribute information of the plurality of network functions corresponding to the service requirement, and a requirement of one or more network functions corresponding to the service requirement;
  • a processing module configured to generate an NFV deployment policy for performing network function virtualization NFV deployment on the NSI, where the NFV deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and performing network service according to the NSD Authenticating a rule that needs to be satisfied; the rule that the network service instantiation needs to satisfy includes any one or a combination of any one of the following: an identifier of one or more virtualized network function VNFs included in the NSD, the NSD includes The connection relationship between the plurality of VNFs, the connection attribute information between the plurality of VNFs included in the NSD, and the parameters of the VNFD used by each of the one or more VNFs included in the NSD are required to be satisfied. the rule of.
  • the determining module is specifically configured to:
  • Determining a network slice template NST that matches the service requirement where the NST includes an NSD corresponding to the service requirement or an identifier of the NSD, and network function information corresponding to the service requirement.
  • the identifier of the one or more VNFs included in the NSD is obtained according to one or more network functions corresponding to the service requirement, and the connection relationship between the multiple VNFs included in the NSD is Obtaining, according to the connection relationship of the multiple network functions corresponding to the service requirement, the connection attribute information between the multiple VNFs included in the NSD is obtained according to the connection attribute information of the multiple network functions corresponding to the service requirement.
  • the rules that need to be met in each parameter of the VNFD used by each VNF of the one or more VNFs included in the NSD are obtained according to requirements of one or more network functions corresponding to the service requirements.
  • the NSMF network element further includes a transceiver module
  • the transceiver module is configured to send a requirement of one or more network functions corresponding to the service requirement to a network function management function NFMF network element.
  • processing module is further configured to:
  • a deployment preference that satisfies a rule that the network service instantiation needs to satisfy is selected from the deployment preferences of the NSD.
  • the NSMF network element further includes a transceiver module
  • the transceiver module is configured to send the NFV deployment policy to a policy function network element.
  • the embodiment of the present application provides a policy function network element, where the policy function network element includes:
  • a transceiver module configured to receive an NFV deployment policy sent by the NSMF network element, where the NFV deployment policy includes an identifier of the NSD or the NSD, and a rule that needs to be satisfied according to the NSD for performing network service instantiation; the network service instantiation
  • the rule to be satisfied includes any one or any combination of the following: an identifier of one or more virtualized network function VNFs included in the NSD, a connection relationship between a plurality of VNFs included in the NSD, the NSD The connection attribute information between the plurality of VNFs included, and the rules of the VNFD used by each VNF of the one or more VNFs included in the NSD.
  • a processing module configured to obtain, according to the identifier of the NSD or the NSD, a deployment preference of the NSD; and, according to a rule that the network service instantiation needs to meet, select, from the deployment preferences of the NSD, that the Network services instantiate the deployment preferences of the rules that need to be met.
  • a further aspect of the embodiments of the present application provides a network slice management function NSMF network element, where the NSMF network element includes:
  • a memory for storing a software program
  • a processor configured to execute a software program in the memory, to enable the NSMF network element to perform the method for deploying a network slice according to the above first aspect.
  • a further aspect of the embodiments of the present application provides a policy function network element, where the policy function network element includes:
  • a memory for storing a software program
  • a processor configured to execute a software program in the memory, so that the policy function network element performs the network slice deployment method described in the second aspect above.
  • the device includes: a processor, a transceiver, and a memory; the memory is used to store a computer to execute instructions, and the transceiver is configured to implement the device and other communication.
  • the entity is in communication, the processor is coupled to the memory via the bus, and when the device is in operation, the processor executes the computer-executable instructions stored in the memory to cause the apparatus to perform the operations described in the first to fourth aspects above The method of deploying network slices.
  • Yet another aspect of an embodiment of the present application provides a computer storage medium storing a software program that implements the above first to fourth aspects when read and executed by one or more processors A method of deploying a network slice as described in any aspect.
  • a further aspect of the present application provides a network function virtualization NFV system, where the NFV system includes: a network slice management function NSMF network element and a policy function network element;
  • the NSMF network element is configured to: acquire network slice requirement information, where the network slice requirement information includes a service requirement that the network slice instance NSI to be deployed needs to be carried; determine a network service deployment template NSD and network function information corresponding to the service requirement.
  • the network function information corresponding to the service requirement includes any one or a combination of any one of the following: one or more network functions corresponding to the service requirement, a connection relationship of multiple network functions corresponding to the service requirement, and a The connection attribute information of the plurality of network functions corresponding to the service requirement and the requirement of the one or more network functions corresponding to the service requirement; generating an NFV deployment policy for performing network function virtualization NFV deployment on the NSI, the NFV deployment
  • the policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and a rule that needs to be satisfied according to the NSD for performing network service instantiation; and the rule that the network service instantiation needs to satisfy includes any one or any of the following: Combination of:
  • the policy function network element is configured to: receive an NFV deployment policy sent by the NSMF network element, obtain a deployment preference of the NSD according to the identifier of the NSD or the NSD, and select a satisfaction from the deployment preference of the NSD. Describe the deployment preferences of the rules that the network service instantiation needs to satisfy.
  • a further aspect of an embodiment of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the deployment of the network slice of any of the above first or second aspects method.
  • FIG. 1a is a schematic diagram of an overall architecture of an NFV system to which an embodiment of the present application is applied;
  • Figure 1b is a schematic diagram of the architecture and interface of the network slice management function and the NFV MANO;
  • FIG. 2 is a diagram showing an example of deployment of an NS
  • Figure 3 is a schematic diagram of NSD corresponding to two services
  • VNF-a is a schematic diagram of deployment preferences of VNF-a and VNF-b;
  • FIG. 5 is a schematic structural diagram of a device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a method for deploying a network slice according to Embodiment 1 of the present application.
  • FIG. 7 is a schematic flowchart of a method for deploying a network slice according to Embodiment 2 of the present application.
  • FIG. 8 is a schematic flowchart of a method for deploying a network slice according to Embodiment 3 of the present application.
  • FIG. 9 is a schematic flowchart of a method for deploying a network slice according to Embodiment 4 of the present application.
  • FIG. 10 is a schematic structural diagram of an NSMF network element according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a policy function network element according to an embodiment of the present disclosure.
  • the fifth-generation mobile communication (the 5th-generation, 5G) system introduces the concept of network slicing to cope with different The difference in the demand for network performance of communication services.
  • Network slicing refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including terminal equipment, access network, transmission network, core network and application server, which can provide complete communication service and has certain network capabilities.
  • the network slice can also be any combination of a terminal device, an access network, a transport network, a core network, and an application server.
  • Network slicing can be created through a variety of technologies, such as network function virtualization (NFV) and software defined network (SDN).
  • NFV network function virtualization
  • SDN software defined network
  • FIG. 1a is a schematic diagram of an overall architecture of an NFV system according to an embodiment of the present application.
  • the NFV system 100 includes: a NFV management and orchestration (MANO) network element 101, an NFV infrastructure (NFVI) layer 130, and a plurality of VNFs 108 (VNF1, VNF2, and VNF3). ), a network function management function (NFMF) network element 122, and an operation-support system/business support system (OSS/BSS) 124.
  • the NFV MANO 101 includes an NFV orchestrator (NFVO) 102, one or more VNF managers (VNFM) 104, and a virtualized infrastructure manager (VIM) 106.
  • NFVO NFV orchestrator
  • VNFM VNF managers
  • VIP virtualized infrastructure manager
  • the OSS/BSS 124 may include a communication service management function (CSMF) network element, a network slice management function (NSMF) network element, and a network slice subnet management function.
  • Function, NSSMF Function
  • An end-to-end network slice includes various parts such as a radio access network and a core network, and each part is called a subnet slice.
  • the NSSMF function is responsible for managing subnet slices.
  • the NSMF is responsible for managing end-to-end slicing. NSSMF is similar to NSMF except that it accepts the subnet's business requirements and creates subnet slice instances. If all subnets are provided by one vendor, NSSMF can be used to create a radio access network and a core network directly from NSMF.
  • the NFVI 130 includes computing hardware 112, storage hardware 114, network hardware 116, virtualization layer, virtual computing 110, virtual storage 118, and virtual network 120.
  • the NSMF network element may also directly manage the NF, that is, the related function of the NFMF network element, and may not be separate at this time.
  • the NFMF network element 122 is set.
  • the network element in the embodiment of the present application may be a physical entity network element or a virtual network element, which is not limited herein.
  • NFV MANO NFV MANO
  • NFVO102 is mainly responsible for handling the lifecycle management of virtualized services, as well as the allocation and scheduling of virtual resources in virtual infrastructure and NFVI.
  • the NFVO 102 can communicate with one or more VNFMs 104 to perform resource related requests, send configuration information to the VNFM 104, and collect status information for the VNF 108.
  • NFVO 102 can also communicate with VIM 106, perform resource allocation, and/or reserve, exchange virtualized hardware resource configuration and status information.
  • VNFM104 is mainly responsible for lifecycle management of one or more VNFs, such as instantiating, updating, querying, scaling, and terminating VNF108.
  • the VNFM 104 can communicate with the VNF 108 to complete VNF lifecycle management and exchange configuration and status information.
  • the VIM 106 controls and manages the interaction of the VNF 108 with the computing hardware 112, the storage hardware 114, the network hardware 116, the virtual computing 110, the virtual storage 118, and the virtual network 120.
  • the VIM 106 performs resource management functions, including managing infrastructure resources, allocating (eg, adding resources to virtual containers), and running functions (eg, collecting NFVI failure information).
  • the VNFM 104 and the VIM 106 can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.
  • NFVI 130 is the infrastructure layer of NFV, which contains hardware components, software components, or a combination of both to establish a virtualized environment, deploy, manage, and implement VNF108.
  • the hardware resources and virtualization layer are used to provide virtualized resources for the VNF 108, such as virtual machines and other forms of virtual containers.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. As an embodiment, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • the virtualization layer in NFVI abstracts hardware resources and decouples VNF 108 from the underlying physical network layer.
  • Each VNF 108 runs in one or more virtual containers, corresponding to a set of network functions belonging to one or more physical devices.
  • OSS/BSS124 supports various end-to-end telecom services.
  • the management functions supported by OSS include: network configuration, service provision, fault management, etc.; BSS processes orders, payment, revenue, etc., supports product management, order management, revenue management and Customer management.
  • NFV MANO101 is used to allocate the infrastructure resources required for network slicing according to the NFV deployment requirements of the network slicing management function, and complete the deployment of virtual network functions on the virtualized infrastructure and complete the network connection between the network functional entities. .
  • the CSMF is responsible for sending a network slice order request to the network slice management function according to the communication service requirement of the customer. After the network slice instance is created, it is also responsible for managing the communication service carried by the network slice instance.
  • NSMF is responsible for the entire lifecycle management of network slice instances creation, activation, operation, deactivation, and deletion.
  • NSMF accepts the customer's network slicing order and creates a network slicing instance based on the stored network slicing template-driven virtualization orchestration and management functional entity and slice control functional entity.
  • NFMF 122 can indirectly manage these network function entities through various vendors' NFMF network elements.
  • the NSMF network element implements NFV deployment of the network slice instance through the interface with the NFVO network element of the NFV MANO.
  • Figure 1b shows the architecture and interface of the network slice management function and NFV MANO.
  • NSMF network elements and NFMF network elements may not be independent entities, but are all part of the Operation and Maintenance Support System (OSS).
  • the NSMF network element and the NFMF network element may be collectively referred to as a policy management network element, and the policy management network element is mainly responsible for generating an NFV deployment policy; the NFVO network element and the VNFM network element (optional) may be collectively referred to as Policy function network element, the policy function network element is mainly responsible for selecting a deployment preference that satisfies the rule from the deployment preferences of the NSD according to the NFV deployment policy.
  • the policy management network element may also be referred to as a policy management point (PAP) or other name, and is not limited.
  • the policy function network element may also be referred to as a policy function (PF) entity or other name. The specifics are not limited.
  • the NSMF or NSSMF network element may be used as the PAP, the NSSMF network element or the NFMF network element as the PF; or the NSMF or the NSSMF may have the functions of the PAP and the PF; or, the NFV MANO directly follows
  • the deployment preference of the NSD determined by the method in the embodiment of the present application performs the NFV deployment; or the NSMF or the NSSMF performs the NFV deployment according to the deployment preference of the NSD determined by the method in the embodiment of the present application.
  • the embodiment of the present application is not specifically limited.
  • a network element when a network element has the functions of PAP and/or PF, it can be considered as the PAP and/or PF by the network element.
  • NSI is a real-world logical network that can meet certain network characteristics or service requirements.
  • the NSI can be instantiated by the NST.
  • the NST is a pre-designed template for creating a network slice instance.
  • the NST can include an NSD or NSD ID used to create an NSI for NFV deployment.
  • a complete NSI can provide complete end-to-end network services.
  • the NSI can include several network slice subnet instances (NSSIs) and/or several network functions (NFs).
  • NSST network slice subnet template
  • a method flow for deploying a network slice instance is: CSMF receives a customer's service requirement, converts the service requirement into a network slice requirement, and sends the network slice request to the NSMF; the NSMF will receive The network slicing requirements are translated into network slicing subnet requirements and the network slicing subnet requirements are sent to the NSSMF; the NSSMF converts the network slicing subnet requirements to the network functional instance requirements that need to be deployed, and sends the network functional instance requirements to the NFV MANO NFV MANO allocates resources on the NFVI according to deployment requirements and deploys the corresponding VNF instances in the network slice and connects the VNF instances.
  • the NSMF sends the service configuration script to the NFMF, and the NFMF executes the relevant service configuration command on the VNF of the network slice according to the script, so that the service required by the customer order can be normally run on the slice. This will successfully deploy a network slice instance.
  • the NFV MANO needs to deploy a network service (NS) instance according to the requirements of the NSMF network element.
  • a network service virtualized in NFV is called an NS, and an NS is composed of multiple VNFs and a link between them.
  • the NS When the NS is deployed on the NFVI, it allocates a certain CPU, hard disk, and memory to the virtual machine, and runs the software image of the VNF on the virtual machine to form a VNF instance.
  • the corresponding network link is allocated, and the VNF instances are configured according to each other. The description of the NSD is connected and eventually forms an NS instance.
  • the NS example includes three VNFs of VNF1, VNF2, and VNF3, and a connection point (CP) 1, CP2, CP3, CP4, and CP5.
  • connection point (CP) 1 CP2, CP3, CP4, and CP5.
  • CP6 connection point 1, CP2, CP3, CP4, and CP5.
  • VL virtual link
  • CP4 and CP6 are connected to the external network through Ext1 and Ext2 as external connection points.
  • the NS can support nesting, that is, some sets of VNFs form an NS, and then form a larger NS with other NSs or VNFs.
  • the NSD identifier (ie, NSD ID) of the nested NS can be indexed within the NSD.
  • the NSD includes several NS deployment preferences.
  • NS DF information about which types of VNFs the NS includes, the network connections of the VNFs, and the number of VNFs can be described.
  • the standard structure definition of NS DF can be found in Table 1.
  • NST supports two types of similar business applications.
  • Figure 3 shows the NSD diagrams for these two services. When supporting service 1, four network functions of VNF-a to VNF-d are required; when supporting service 2, five network functions of VNF-a to VNF-e are required.
  • VNFD also contains several DFs.
  • VNFD DF you can describe which modules VNF is composed of, the network connection between modules, the number of deployments of various modules, the deployment requirements of various modules, and the software image of various modules. And version and so on.
  • the standard structure definition of VNFD DF can be seen in Table 2.
  • VNF-a in Figure 3 has three types of DFs supporting different service capacities (flavour-x, flavour-y, and flavour-z)
  • VNF-b has two types of DFs that support different service capacities (flavour).
  • -m, flavour-n the virtual CPUs of the other VNFs from the minimum capacity to the maximum capacity have the same amount of virtual CPU, virtual memory and virtual disk storage, so only one type of DF is sufficient.
  • FIG. 4 it is a schematic diagram of deployment preferences of VNF-a and VNF-b.
  • the NSD DFs in the above example are listed, and it is determined that these NSD DFs can respectively satisfy which parameter combination ranges in the customer network slice order, and then combine them with the parameters in the customer order.
  • the DF-12 can meet the access of 1 million narrow-band fixed IoT terminals
  • the DF-6 can meet the broadband mobile IoT terminal access of 200,000 times per hour and below 100km/h, so the DF-6 and DF-12 will be placed with the order.
  • the range of parameter combinations in the corresponding ones are listed, and it is determined that these NSD DFs can respectively satisfy which parameter combination ranges in the customer network slice order, and then combine them with the parameters in the customer order.
  • the DF-12 can meet the access of 1 million narrow-band fixed IoT terminals
  • the DF-6 can meet the broadband mobile IoT terminal access of 200,000 times per hour and below 100km/h, so the DF-6 and DF-12 will be placed with the order.
  • NSMF can select the NSD ID and NSD DF that meet the customer order requirements from the NST according to the network slicing order issued by the user, and carry it in the deployment request sent to the NFV MANO, NFV MANO will The deployment is done in accordance with NS DF and VNFD DF.
  • listing the correspondence of all NSD DFs and the combination of parameters in the customer order in the NST will make the design of the NST very complicated and difficult to maintain.
  • the embodiment of the present application provides a method for deploying a network slice, which is used to solve the technical problem that the design of the NST becomes very complicated and difficult to maintain.
  • an apparatus 500 provided by an embodiment of the present application includes at least one processor 51, a communication bus 52, a memory 53, and at least one communication interface 54.
  • the device 500 can be any one of the functional network elements in the embodiment of the present application.
  • the device 500 can be used to perform the method for deploying the network slice provided by the embodiment of the present application.
  • the processor 51 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 52 can include a path for communicating information between the components described above.
  • the communication interface 54 using any type of transceiver, is used to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), WALN, and the like.
  • RAN Radio Access Network
  • WALN Wireless Local Area Network
  • the memory 53 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed by the device, but is not limited thereto.
  • the memory can exist independently and be connected to the processor via a bus. The memory can also be integrated with the processor.
  • the memory 53 is used to store application code for executing the solution of the present application, and is controlled by the processor 51 for execution.
  • processor 51 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • the apparatus 500 can include a plurality of processors, such as the processor 51 and the processor 55 of FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the apparatus shown in FIG. 5 may be a component of a policy management network element or a policy management network element, and one or more software modules are stored in a memory of the apparatus shown in FIG. 5.
  • the apparatus shown in FIG. 5 can implement the method for deploying network slices executed by the policy management network element in the embodiments of the present application by executing the program code in the memory by the processor.
  • the device shown in FIG. 5 may be a component of a policy function network element or a policy function network element, and one or more software modules are stored in the memory of the device shown in FIG. 5.
  • the apparatus shown in FIG. 5 can implement the method for deploying network slices executed by the policy function network element in the embodiments of the present application by executing the program code in the memory by the processor.
  • step numbers are merely for convenience of description, and there is no strict execution relationship between the steps.
  • FIG. 6 is a schematic flowchart of a method for deploying a network slice according to Embodiment 1 of the present application. As shown in FIG. 6, the method includes:
  • Step 601 The NSMF network element obtains the network slice requirement information, where the network slice requirement information includes the service requirement that the NSI to be deployed needs to be carried, and the NSD and network function information corresponding to the service requirement.
  • the one or more network functions corresponding to the service requirement, the connection relationship of the plurality of network functions corresponding to the service requirement, the connection attribute information of the plurality of network functions corresponding to the service requirement, and the service requirement The need for one or more network features.
  • the NSMF network element receives an order to deploy the NSI and obtains network slice demand information according to the order.
  • the service requirements that the NSI needs to carry may include one or more requirements information.
  • the service requirements that the NSI needs to carry may include any one or any combination listed in Table 4.
  • the service requirement that the NSI needs to carry may be provided by the operator to the network slice product, and the parameters listed in the NST are provided to the user to be selected or specified within a certain range. In this way, the service requirements that the NSI needs to carry can match an NST.
  • the order requires communication services for 20,000 shared bicycles in a certain area. Therefore, it can be seen that the service requirements that the NSI needs to carry include the service type (Internet of Things) and the regional capacity of the service (20,000).
  • the service requirements contained in NST1, NST2, and NST3 are shown in Table 5, respectively.
  • the service types included in NST1, NST2, and NST3 are all Internet of Things.
  • the area capacity of services included in NST1 includes two levels, which are 10,000 to 12,000 and 12,000 to 15,000 respectively.
  • the NST2 includes The regional capacity of the service includes three levels, ranging from 15,000 to 16,000, 16,000 to 17,000, and 17,000 to 18,000.
  • the regional capacity of the services included in the NST3 includes two levels, ranging from 18,000 to 21,000. 21,000 ⁇ 24,000. In this way, it can be determined that the NST in the foregoing three NSTs that matches the service requirements that the NSI needs to bear is NST3.
  • the NST may further include an identifier of the NSD or the NSD corresponding to the service requirement, and network function information corresponding to the service requirement.
  • the NSMF network element can determine the NSD and network function information corresponding to the service requirement according to the NST that matches the service requirement.
  • the NSMF network element may also determine, according to the service requirement, an NSD corresponding to the service requirement, and an NST matching the service requirement, where the NST includes the service requirement.
  • the network function information in this case, the identifier of the NSD or NSD corresponding to the service requirement may not be included in the NST.
  • NST3 the content included in NST3 is further enumerated below.
  • Table 6 is only shown by including all the contents listed above in NST3 as an example.
  • the NSD or NSD identifier corresponding to the service requirement and the network function information corresponding to the service requirement are obtained from the NST according to the service requirements that the NSI needs to bear.
  • the one or more network functions corresponding to the service requirement may refer to a radio access network (RAN), a user plane function (UPF) network element, access, and mobility management.
  • RAN radio access network
  • UPF user plane function
  • AMF Access and mobility management function
  • SMF session management function
  • AS application service
  • connection of multiple network functions corresponding to the service requirement The relationship is used to describe whether there is a link connection between multiple network functions, for example, whether there is a link connection between the RAN and the UPF; the connection attribute information of the multiple network functions corresponding to the service requirement is used to describe multiple network functions.
  • connection attribute information is required to be described using the attributes of the connection point and the link; the requirements of the one or more network functions corresponding to the service requirement are The number of instances that need to be met, the performance indicator parameters, and the protection required to describe the NS instance or VNF instance. One or more of the number and resource requirements in specific is not limited.
  • NST describes the need to establish a data connection between the VNF-a type network function supporting the type of service and the VNF-d type network function, VNF-
  • Step 602 The NSMF network element generates an NFV deployment policy for performing NFV deployment on the NSI, where the NFV deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and needs to perform network service instantiation according to the NSD.
  • a rule that is satisfied; the rule that the network service instantiation needs to satisfy includes any one or any combination of the following: an identifier of one or more virtualized network function VNFs included in the NSD, and multiple The connection relationship between the VNFs, the connection attribute information between the plurality of VNFs included in the NSD, and the rules to be satisfied in each parameter of the VNFD used by each of the one or more VNFs included in the NSD.
  • the NFV deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, that is, an identifier of an NSD or an NSD to be used when performing NFV deployment on the NSI.
  • the NST that matches the service requirement that the NSI needs to bear includes one or more network functions corresponding to the service requirement, and a connection of multiple network functions corresponding to the service requirement. Relationship, the connection attribute information of the plurality of network functions corresponding to the service requirement, and the requirement of one or more network functions corresponding to the service requirement. Therefore, the NSMF network element can obtain the network function according to the one or more network functions corresponding to the service requirement.
  • the connection attribute information of the function is obtained by the connection attribute information between the plurality of VNFs included in the NSD, and each of the one or more VNFs included in the NSD is obtained according to the requirement of one or more network functions corresponding to the service requirement.
  • the NSMF network element can obtain the VNF identifier included in the NSD as VNFa (corresponding to RAN), VNFb (corresponding to AMF), VNFc (corresponding to SMF), and VNFd (corresponding to UPF).
  • VNFa corresponding to RAN
  • VNFb corresponding to AMF
  • VNFc corresponding to SMF
  • VNFd corresponding to UPF.
  • the service requirements described above the service type is the Internet of Things, the area capacity of the service is 20,000
  • the RAN is connected to the AMF
  • the SMF and the UPF are connected to each other.
  • VNFa in VNF contained in NSD can be linked to VNFb and VNFd, VNFb and VNFc, VNFc and VNFd.
  • the NSMF network element obtains, according to the requirement of one or more network functions corresponding to the service requirement, a specific implementation process of a rule that needs to be met in each parameter of the VNFD used by each VNF of the one or more VNFs included in the NSD.
  • the NSMF network element may determine, according to the requirements of one or more network functions and the implementation specifications of the network function in the NST, the rules that need to be met in the parameters of the VNFD used by the corresponding VNF.
  • the implementation specifications of the network function in the NST may be obtained according to actual specifications of network functions of various vendors.
  • the NSMF network element can determine the VNF version number according to the service function requirement, and include the VNF component (VNF component), which VNFC corresponds to which virtualization deployment unit (VDU), and can also be determined according to the requirements of the NF. The number of individual VDUs in the VNF, and so on.
  • VNF component VNF component
  • VDU virtualization deployment unit
  • Step 603 The NSMF network element sends the NFV deployment policy to the policy function network element.
  • Step 604 The policy function network element receives the NFV deployment policy sent by the NSMF network element.
  • Step 605 The policy function network element obtains the deployment preference of the NSD according to the identifier of the NSD or the NSD, and selects the rule that meets the rule from the deployment preferences of the NSD according to the rule that the network service instantiation needs to meet.
  • Deployment preferences refers to all deployment preferences obtained after considering the deployment preference of the NS (see the description of FIG. 3) and the deployment preference of the VNF (see the description of FIG. 4), that is, the meaning shown in Table 3. 12 deployment preferences.
  • the policy function network element may include the NFVO network element and the VNFM network element.
  • the NSMF network element may send the NFV deployment policy to the NFVO network element.
  • step 604 the NFVO network element receives the NFV deployment policy.
  • the identifier of the NSD or NSD to be used for the NFV deployment of the NSI, the identifier of one or more VNFs included in the NSD, and the connection relationship between multiple VNFs included in the NSD The information such as the connection attribute information between the multiple VNFs included in the NSD is used for the deployment of the NS. Therefore, the information may be referred to as an NS deployment policy. Since the parameters of the VNFD used by each VNF of one or more VNFs corresponding to the one or more network functions need to be satisfied for the deployment of the VNF, it may be referred to as a VNF deployment strategy. .
  • step 605 can include: Step 605a, the NFVO network element selects an alternate deployment preference from the deployment preferences of the NSD according to the NS deployment policy. Specifically, the NFVO network element may obtain the deployment preference of the NSD according to the identifier of the NSD or the NSD (such as 12 deployment preferences indicated in Table 3), and according to the NSD included in the NFV deployment policy.
  • the deployment preference is selected from the deployment preferences of the NSD, specifically, the selected deployment preference is NSD DF-1 to NSD DF-6 . Since the deployment preference selected from the NSD deployment preferences may be multiple at this time, the deployment preference of the VNFD selected by the VNFM network element may be further obtained to obtain the final deployment preference. Therefore, for convenience of description, the current deployment preference may be The selected deployment preferences are referred to as alternative deployment preferences.
  • the NFVO may find the NSD DF that satisfies the rule by filtering various parameters of the flavour key and the flavour content in the deployment preferences of the NS.
  • the step 605 further includes: Step 605b: The NFVO network element sends, to the VNFM network element, a rule that the parameters of the VNFD used by each VNF of the one or more VNFs of the NSD are required to be met, that is, the VNF deployment policy.
  • Step 605c The VNFM network element selects a deployment preference that satisfies the rule from the deployment preferences of the VNFD used by each VNF according to rules that need to be met in each parameter of the VNFD used by each VNF.
  • each VNFD can describe the VNF version, service function, performance and other attributes, as well as the VNFC type and the corresponding VDU number.
  • other possible attributes may also be described, and are not specifically limited.
  • the VNFM network element may select the first deployment preference according to the order of deployment preference in the VNFD. If the deployment preference of the VNFD that satisfies the rule cannot be selected, the VNFM network element can use the default deployment preference (default DF).
  • Step 606 The VNFM network element sends the selected deployment preference of the VNFD used by each VNF to the NFVO network element.
  • the NFVO network element may first request the VNFM network element to select the deployment preference of the VNFD used by each VNF. Further, the VNFM network element uses the selected VNF according to the request of the NFVO network element. The deployment preferences of the VNFD are sent to the NFVO network element.
  • Step 607 The NFVO network element determines the final deployment preference according to the candidate deployment preference selected in step 605a and the deployment preference of the VNFD used by each VNF selected by the VNFM network element, and according to the determined deployment preference. NSI is deployed.
  • the candidate deployment preferences selected in step 605a are NSD DF-1 to NSD DF-6, and the deployment preferences of the VNFD used by each VNF selected by the VNFM network element are: flavour-x, flavour-m, Flavour-c, flavour-d, to determine the final deployment preference is NSD DF-1.
  • the NFVO network element can directly deploy the NSI according to the selected alternative deployment preference.
  • the NFVO network element can directly deploy the NSI according to the selected alternative deployment preference.
  • the priority of the deployment preference the highest priority of the default deployment preference
  • the selected deployment preference the highest priority of the default deployment preference
  • the specific deployment process may be: the NFVO network element commands the VIM network element to perform virtual resource allocation and NFV deployment on the NFVI according to the result returned by the VNFM (ie, the selected deployment preference of the VNFD used by each VNF).
  • the NFVO network element commands the VIM network element to perform virtual resource allocation and NFV deployment on the NFVI according to the result returned by the VNFM (ie, the selected deployment preference of the VNFD used by each VNF).
  • the VNFM network element after the VNFM network element selects the deployment preference of the VNFD used by each VNF, it may not be sent to the NFVO network element, but the VNFM network element directly commands the VIM network element to follow the deployment preference on the NFVI. Perform virtual resource allocation and NFV deployment.
  • the specific deployment manner is not limited in the embodiment of the present application.
  • the rule that the network service instantiation needs to be satisfied includes: an identifier of one or more VNFs included in the NSD, a connection relationship between multiple VNFs included in the NSD, and the The connection attribute information between the plurality of VNFs included in the NSD, the rules in the VNFD used by each VNF of the one or more VNFs included in the NSD, and the rules to be satisfied in other possible embodiments.
  • the rules that the network service instantiation needs to satisfy may also include only part of the information.
  • the NSD required for NFV deployment of the NSI has two deployment preferences, as illustrated in Figure 3 (where each VNF included in the NSD has only one deployment preference). Since there are differences in the identifiers of the VNFs included in the two deployment preferences, that is, there is no VNFe in the first deployment preference, and the second deployment preference includes VNFe. Therefore, the two deployment preferences can be distinguished according to the identifier of the VNF. In this case, the rules for the network service instantiation need to be satisfied include only the NSD or the identifier of the NSD that needs to be used for the NFV deployment of the NSI, and the identifier of one or more VNFs included in the NSD.
  • the NFVO network element may obtain the foregoing two deployment preferences of the NSD according to the NSD or the NSD identifier to be used when performing the NFV deployment on the NSI, and further, according to the identifier of one or more VNFs included in the NSD. Select the deployment preferences that satisfy the rule from the two deployment preferences. For example, the VNF is not present in the identifier of the VNF included in the NSD, and therefore, the first deployment preference can be used as a deployment preference that satisfies the rule. At this time, since each VNF included in the NSD has only one deployment preference, the VNFD used by each VNF of the one or more VNFs included in the NSD is not required in the rule that the network service instantiation needs to be satisfied. There are rules that need to be met for each parameter, and there is no need to perform the process of selecting the deployment preferences of VNFD.
  • the content included in the rule that the network service instantiation needs to be met in the embodiment of the present application may have multiple possibilities, and is not limited.
  • the rule that the network service instantiation needs to be satisfied is obtained according to the network function information corresponding to the service requirement, that is, the identifier of one or more VNFs included in the NSD is corresponding according to the service requirement.
  • the connection relationship between the plurality of VNFs included in the NSD is obtained according to the connection relationship of the plurality of network functions corresponding to the service requirement, and the plurality of VNFs included in the NSD are obtained by the one or more network functions.
  • the connection attribute information is obtained according to the connection attribute information of the plurality of network functions corresponding to the service requirement, and each parameter of the VNFD used by each VNF of the one or more VNFs included in the NSD needs to be satisfied. rule.
  • the content included in the network function information corresponding to the service requirement may correspondingly have multiple possibilities.
  • the content included in the network function information corresponding to the service requirement may be more than or equal to the content included in the rule that the network service instantiation needs to satisfy.
  • the corresponding rule that the corresponding network service instantiation needs to satisfy only includes: The identifier of one or more VNFs included in the NSD.
  • the network function information corresponding to the service requirement includes a plurality of network functions corresponding to the service requirement and a connection relationship between the plurality of network functions, and at this time, the corresponding rule that the network service instantiation needs to be satisfied is obtained.
  • the identifier may include only the identifiers of the plurality of VNFs included in the NSD, or may include the identifiers of the plurality of VNFs included in the NSD and the connection relationship between the multiple VNFs.
  • the NFV network element generates an NFV deployment policy according to the network slice requirement information, and sends the NFV deployment policy to the policy function network element.
  • the policy function network element can select the deployment preference according to the NFV deployment policy; compared to the prior art.
  • one or more network functions corresponding to the service requirements may also be in the form of a network function set, such as a next generation-radio access network. NG-RAN), a fifth-generation core network (5 th Generation core network, 5GC ) and the like.
  • the content included in the NST is: an identifier of the NSD or the NSD corresponding to the service requirement, one or more network function sets corresponding to the service requirement, and a corresponding amount of the service requirement.
  • the NSMF network element can obtain the nested NSD (nested NSD) required for deploying the network function set included in the NSD according to the content included in the NST for one or more network function sets corresponding to the service requirement.
  • the identifier is obtained according to the connection relationship between the network function sets corresponding to the service requirement: between the nested NS instances deployed between the network service instantiations and the other VNF instances according to the nested NSDs included in the NSD.
  • connection relationship is obtained according to the connection attribute information between the plurality of network function sets corresponding to the service requirement: the nested NS instances deployed after the network service instantiation is performed according to the nested NSD included in the NSD or with other VNFs
  • the connection attribute information between the instances is obtained according to the requirements of the one or more network function sets corresponding to the service requirements, and the required features of the nested NS instance, the number of VNF instances included, the performance indicator parameters, the guarantee parameters, and the resources. Demand, etc.
  • the NSMF network element can directly manage the NF, that is, the related function of the NFMF network element.
  • the NFMF network element does not need to be separately set.
  • the NSMF network element may not have the related function of the NFMF network element.
  • the NFMF network element needs to be separately set. The following description will be made in conjunction with the second embodiment.
  • FIG. 7 is a schematic flowchart of a method for deploying a network slice according to Embodiment 2 of the present application. As shown in FIG. 7, the method includes:
  • Step 701 The NSMF network element acquires network slice requirement information, where the network slice requirement information includes a service requirement to be carried by the NSI to be deployed, and determining NSD and network function information corresponding to the service requirement.
  • the network function information includes any one or a combination of any one of the following: one or more network functions corresponding to the service requirement, a connection relationship of multiple network functions corresponding to the service requirement, and the service requirement. Corresponding multiple network function connection attribute information and requirements of one or more network functions corresponding to the service requirement.
  • Step 702 The NSMF network element generates an NS deployment policy, where the NS deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and a combination of any one or any of the following: one or the NSD includes The identifier of the plurality of virtualized network functions VNF, the connection relationship between the plurality of VNFs included in the NSD, and the connection attribute information between the plurality of VNFs included in the NSD.
  • Step 703 The NSMF network element sends the NS deployment policy to the NFVO network element.
  • Step 704 The NFVO network element receives the NS deployment policy, and selects an alternative deployment preference according to the NS deployment policy.
  • the NSMF network element may further perform step 705 if the network function information includes the requirement of the one or more network functions.
  • Step 705 The NSMF network element sends the requirement of one or more network functions corresponding to the service requirement to the NFMF network element.
  • the requirement of one or more network functions is the requirement of one or more network functions corresponding to the service requirements that the NSI needs to bear according to the network slice requirement information.
  • Step 706 The NFMF network element receives the requirement of one or more network functions, and according to the requirements of the one or more network functions, each parameter of the VNFD used by each VNF of the one or more VNFs needs to be satisfied. Rules (ie VNF deployment strategy).
  • the NFMF network element can determine the rules that need to be met in the VNFD used to deploy the corresponding VNF according to the requirements of one or more network functions and the implementation specifications of the network functions in the NST, and generate a VNF. Deployment strategy.
  • the implementation specifications of the network function in the NST may be obtained according to actual specifications of network functions of various vendors.
  • the NFMF network element can determine the VNF version number according to the service function requirement, and include the VNF component (VNF component), which VNFC corresponds to which virtualization deployment unit (VDU), and can also be determined according to the requirements of the NF.
  • VNF component VNF component
  • VDU virtualization deployment unit
  • UP_VDU.instace_number> 4] and use it as a VNF deployment strategy.
  • Step 707 The NFMF network element sends the VNF deployment policy to the VNFM network element, where the VNF deployment policy includes a rule that needs to be met in each parameter of the VNFD used by each VNF of the one or more VNFs.
  • the unified VNFD identifier may be pre-configured on the NFMF network element. Therefore, the message sent by the NFMF network element to the VNFM may also carry the identifier of the VNFD.
  • Step 708 The VNFM network element selects a deployment preference of the VNFD that satisfies the rule from the deployment preferences of the VNFD used by each VNF according to rules that need to be met in each parameter of the VNFD used by each VNF.
  • the VNFM network element may select a deployment preference of the VNFD that satisfies the rule by filtering various parameters of the flavour key and the flavour content in the deployment preference of the VNFD.
  • Step 709 The VNFM network element sends the selected deployment preference of the VNFD used by each VNF to the NFVO network element.
  • Step 710 The NFVO network element determines the final deployment preference according to the deployment preference of the VNFD used by each VNF selected by the VNFM network element, and deploys the NSI according to the determined deployment preference.
  • the difference between the second embodiment and the first embodiment is that, in the first embodiment, the NSMF network element performs related functions of the NFMF network element, and in the second embodiment, the NFMF network element separately performs related functions;
  • the second embodiment and the first embodiment can be referred to each other.
  • FIG. 8 is a schematic flowchart of a method for deploying a network slice according to Embodiment 3 of the present application, as shown in FIG.
  • Step 801 The NSMF network element acquires the network slice requirement information, where the network slice requirement information includes the service requirement that the NSI to be deployed needs to be carried, and the NSD and network function information corresponding to the service requirement.
  • the one or more network functions corresponding to the service requirement, the connection relationship of the plurality of network functions corresponding to the service requirement, the connection attribute information of the plurality of network functions corresponding to the service requirement, and the service requirement The need for one or more network features.
  • Step 802 The NSMF network element generates an NFV deployment policy, where the NFV deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and a rule that needs to be met according to the NSD to perform network service instantiation; the network service
  • the rules to be satisfied by the instantiation include any one or a combination of any one of the following: an identifier of one or more virtualized network function VNFs included in the NSD, a connection relationship between multiple VNFs included in the NSD, and a The connection attribute information between the plurality of VNFs included in the NSD, and the rules required to satisfy the parameters in the VNFD used by each of the one or more VNFs included in the NSD.
  • Step 803 The NSMF network element selects a deployment preference that satisfies the rule from the deployment preferences of the NSD according to a rule that the network service instantiation needs to satisfy.
  • the NSMF network element may select an alternative deployment preference from the NSD deployment preferences according to the NS deployment policy, for example, the selected candidate deployment preference is NSD DF-1 to NSD DF-6; and the deployment strategy according to the VNF
  • the deployment preferences satisfying the rules are selected from the deployment preferences of the VNFD used by each VNF.
  • the deployment preferences of the selected VNFD for each VNF are: flavour-x, flavour-m, flavour -c, flavour-d;
  • the NSMF network element may determine that the deployment preference of the rule that satisfies the network service instantiation needs to be NSD DF-1.
  • step 804 the NSMF network element sends the selected deployment preference to the NFVO network element.
  • step 805 the NFVO network element deploys the NSI according to the received deployment preference.
  • the difference between the third embodiment and the first embodiment is that, in the first embodiment, after the NSMF network element generates the NFV deployment policy, the NFV deployment policy is sent to the NFVO network element, and then the NFVO network element selects an alternative deployment preference. And deploying the VNFD deployment preference by the VNFM network element, and deploying the NSI according to the selected candidate deployment preference and the selected VNFD deployment preference; and in the third embodiment, after the NSMF network element generates the NFV deployment policy, directly According to the NFV deployment strategy, the NSMF network selects the deployment preference that satisfies the rule from the deployment preferences of the NSD, and then sends the NFVO network element to deploy the NSI.
  • the third embodiment and the first embodiment can be referred to each other.
  • FIG. 9 is a schematic flowchart of a method for deploying a network slice according to Embodiment 4 of the present application. As shown in FIG. 9, the method includes:
  • Step 901 The NSMF network element acquires network slice requirement information, where the network slice requirement information includes a service requirement to be carried by the NSI to be deployed, and determining NSD and network function information corresponding to the service requirement.
  • the network function information includes any one or a combination of any one of the following: one or more network functions corresponding to the service requirement, a connection relationship of multiple network functions corresponding to the service requirement, and the service requirement. Corresponding multiple network function connection attribute information and requirements of one or more network functions corresponding to the service requirement.
  • Step 902 The NSMF network element generates an NS deployment policy, where the NS deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and a combination of any one or any of the following: the NSD includes one or The identifier of the plurality of virtualized network functions VNF, the connection relationship between the plurality of VNFs included in the NSD, and the connection attribute information between the plurality of VNFs included in the NSD.
  • step 903 the NSMF network element selects an alternative deployment preference according to the NS deployment policy.
  • Step 904 The NSMF network element sends the selected candidate deployment preference to the NFVO network element.
  • the NSMF network element may further perform step 905 if the network function information includes the requirement of the one or more network functions.
  • Step 905 The NSMF network element sends the requirement of one or more network functions corresponding to the service requirement to the NFMF network element.
  • Step 906 The NFMF network element generates, according to the requirements of the one or more network functions, a rule that needs to be met in each parameter of the VNFD used by each VNF of one or more VNFs.
  • Step 907 The NFMF network element selects, according to the rules of the VNFD used by each VNF, the parameters of the VNFD used by each VNF to meet the parameters of each VNFD used by each VNF.
  • the deployment preferences of the satisfied rules are the rules of the VNFD used by each VNF.
  • step 908 the NFMF network element sends the deployment preference of the selected VNFD to the VNFM network element.
  • Step 909 The VNFM network element sends the selected deployment preference of the VNFD to the NFVO network element.
  • Step 910 The NFVO network element determines the final deployment preference according to the candidate deployment preference and the deployment preference of the VNFD selected by the VNFM network element, and deploys the NSI according to the determined deployment preference.
  • the difference between the fourth embodiment and the second embodiment is that, in the second embodiment, after the NSMF network element generates the NFV deployment policy, the NSMF network element sends the NS deployment policy to the NFVO network element, and then the NFVO network element is based on the NS.
  • the deployment strategy selects an alternative deployment preference from the deployment preferences of the NSD, and sends the VNF deployment policy to the VNFM network element by the NFMF network element, and the VNFM network element selects the deployment preference of the VNFD according to the VNF deployment policy.
  • the NSMF network element After the NSMF network element generates the NFV deployment policy, the NSMF network element directly selects the candidate deployment preference from the NSD deployment preference according to the NS deployment policy.
  • the NFMF network element After the NFMF network element generates the VNF deployment policy, the NFMF network element directly selects the VNF deployment policy according to the VNF deployment policy. Out of VNFD deployment preferences.
  • the fourth embodiment and the second embodiment can be referred to each other.
  • the embodiment of the present application further provides an NSMF network element and a policy function network element.
  • NSMF network element For the specific implementation of the NSMF network element and the policy function network element, refer to the foregoing method flow.
  • FIG. 10 is a schematic structural diagram of an NSMF network element, where the NSMF network element is used to implement the corresponding process in FIG. 6 to FIG. 9 , where the NSMF network element 1000 includes: a processing module 801 and a transceiver module 802.
  • the NSMF network element 1000 includes:
  • the obtaining module 1001 is configured to obtain network slice requirement information, where the network slice requirement information includes a service requirement that the network slice instance NSI to be deployed needs to bear;
  • the determining module 1002 is configured to determine the network service deployment template NSD and the network function information corresponding to the service requirement, where the network function information corresponding to the service requirement includes any one or any combination of the following: the service requirement corresponds to One or more network functions, a connection relationship of a plurality of network functions corresponding to the service requirements, connection attribute information of a plurality of network functions corresponding to the service requirements, and requirements of one or more network functions corresponding to the service requirements ;
  • the processing module 1003 is configured to generate an NFV deployment policy for performing network function virtualization NFV deployment on the NSI, where the NFV deployment policy includes an NSD corresponding to the service requirement or an identifier of the NSD, and performing network according to the NSD
  • the service instantiation needs to meet the rules; the rules for the network service instantiation to be satisfied include any one or any combination of the following: the identifier of the one or more virtualized network function VNFs included in the NSD, the NSD
  • the connection relationship between the plurality of included VNFs, the connection attribute information between the plurality of VNFs included in the NSD, and the parameters of the VNFD used by each of the one or more VNFs included in the NSD are required Satisfied rules.
  • the determining module 1002 is specifically configured to:
  • Determining a network slice template NST that matches the service requirement where the NST includes an NSD corresponding to the service requirement or an identifier of the NSD, and network function information corresponding to the service requirement.
  • the identifier of the one or more VNFs included in the NSD is obtained according to one or more network functions corresponding to the service requirement, and the connection relationship between the multiple VNFs included in the NSD is Obtaining, according to the connection relationship of the multiple network functions corresponding to the service requirement, the connection attribute information between the multiple VNFs included in the NSD is obtained according to the connection attribute information of the multiple network functions corresponding to the service requirement.
  • the NSD includes rules for each parameter in the VNFD used by each of the one or more VNFs.
  • the NSMF network element further includes a transceiver module 1004;
  • the transceiver module 1004 is configured to send a requirement of one or more network functions corresponding to the service requirement to a network function management function NFMF network element.
  • processing module 1003 is further configured to:
  • a deployment preference that satisfies a rule that the network service instantiation needs to satisfy is selected from the deployment preferences of the NSD.
  • the NSMF network element further includes a transceiver module 1004;
  • the transceiver module 1004 is configured to send the NFV deployment policy to a policy function network element.
  • FIG. 11 is a schematic structural diagram of a policy function network element according to an embodiment of the present application.
  • the policy function network element may be used to implement the corresponding process in the foregoing FIG. 6 to FIG. 9.
  • the policy function network element 1100 includes:
  • the transceiver module 1101 is configured to receive an NFV deployment policy sent by the NSMF network element, where the NFV deployment policy includes an identifier of the NSD or the NSD, and a rule that needs to be satisfied according to the NSD for performing network service instantiation; the network service instance
  • the rules to be satisfied include any one or any combination of the following: an identifier of one or more virtualized network function VNFs included in the NSD, a connection relationship between a plurality of VNFs included in the NSD, the The connection attribute information between the plurality of VNFs included in the NSD, and the rules required to satisfy the parameters in the VNFD used by each of the one or more VNFs included in the NSD.
  • the processing module 1102 is configured to obtain, according to the identifier of the NSD or the NSD, a deployment preference of the NSD; and, according to the rule that the network service instantiation needs to be met, select a satisfaction from the deployment preferences of the NSD.
  • the deployment preferences of the rules are configured to obtain, according to the identifier of the NSD or the NSD, a deployment preference of the NSD; and, according to the rule that the network service instantiation needs to be met, select a satisfaction from the deployment preferences of the NSD.
  • the deployment preferences of the rules are configured to obtain, according to the identifier of the NSD or the NSD, a deployment preference of the NSD; and, according to the rule that the network service instantiation needs to be met, select a satisfaction from the deployment preferences of the NSD.
  • the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • the functional units in the embodiments 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 computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种网络切片的部署方法及装置。该方法包括NSMF网元获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；确定所述业务需求对应的网络服务部署模板NSD和网络功能信息，以及生成对所述NSI进行网络功能虚拟化部署的NFV部署策略。采用上述方式，在网络切片模板NST中无需将NSD的所有部署偏好与客户订单中的参数组合对应起来，从而在NST中消除了和NSD的部署偏好以及虚拟网络功能描述文件VNFD的部署偏好的耦合，大大简化了NST的设计和维护难度。

Description

一种网络切片的部署方法及装置
本申请要求于2018年3月29日提交中国国家知识产权局、申请号为201810274372.1、发明名称为“一种网络切片的部署方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及信息技术领域，特别涉及一种网络切片的部署方法及装置。
背景技术
网络功能虚拟化(network function virtualization，NFV)指通过使用通用的硬件设备及虚拟化技术，来承载传统网络中专用设备的功能，从而降低部署专用设备带来的昂贵成本。软件不与专有硬件绑定，使网络设备功能不再依赖于专用硬件。同时利用云计算的特点，使资源可以充分灵活共享，现实新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。在NFV的架构中，接收实例化请求，并根据请求对相应业务进行实例化处理(部署业务)的一方，称为虚拟化业务提供方(简称业务提供方)，发起实例化请求的一方称为业务请求方。
NFV中虚拟化的网络服务(network service，NS)，举例来说，可以是一个IP多媒体子***(internet protocol multimedia subsystem，IMS)网络服务，或一个演进型分组核心网(evolved packet core，EPC)服务。一个NS中可以包含若干个虚拟化网络功能(virtualized network function，VNF)模块，也称为虚拟化网元。一个NS在进行虚拟化部署时，业务请求方首先需要向业务提供方提交该网络服务的描述信息(network service descriptor，NSD)，网络服务的描述信息也称作NS部署模板，主要包括描述该网络服务的拓扑结构信息以及该网络服务包含的各个VNF的描述信息(VNF descriptor，VNFD)。其中在拓扑结构信息中使用虚拟化连接信息(virtual link descriptor，VLD)来描述VNF之间的连接。VNFD是一个VNF的描述信息，也称作VNF的部署模板。
现有技术中，客户订购网络切片实例(network slice instance，NSI)时，网络切片管理功能实体会提前准备网络切片模板(network slice template，NST)。为了支持某类业务应用，同时满足不同客户在一定范围内的差异化需求，NST也提供一些创建选项，在创建NSI时以供选择。比如，同一个NST可以支持若干种类型相近的业务应用，则对应的NSD中包含若干个NS部署偏好(deployment flavour，DF)，每一种NS DF和业务应用类型对应，类似的，NSD中的VNFD也可以包含若干个部署偏好，每一个VNFD DF和网络功能的属性对应。在部署一个网络切片实例时，NST的可供选择的创建选项理论上就是上述所有NS DF和所有VNFD DF的可能组合，这些组合选项会列在NST中供部署切片实例时选择，我们称为NSD DF。
采用上述方法，NST中需要列出对应的NSD的所有DF。然而，如果NST支持多种类型相近的业务应用，则对应的NSD中会包括多种NS DF，进一步地，如果网络中网元的数量比较多，每一种网元又有多个VNFD DF，则会导致NST中NSD DF的数量非常多，进而 使得NST的设计变得非常复杂，维护难度较大。
发明内容
本申请实施例提供一种网络切片的部署方法，用于解决NST的设计复杂，维护难度较大的技术问题。
本申请实施例中所涉及的NSD DF可以是指使用NSD进行NFV部署时，可供选择实现的各种差异化的网络特征。其中，网络特征的差异可以体现在组成网络的网络功能、网络功能之间的拓扑关系(比如连接关系、连接属性信息)，以及网络功能的数量和需求等，具体不做限定。
第一方面，本申请实施例提供一种网络切片的部署方法，可以由NSMF网元执行，所述方法包括：
获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；
确定所述业务需求对应的网络服务部署模板NSD和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；
生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
根据上述内容可知，由NSMF网元根据所述网络切片需求信息生成NFV部署策略，相比于现有技术中需要直接从NST所列出的NSD的所有部署偏好中选择出符合客户订单的部署偏好来说，采用上述方式，在NST中无需将NSD的所有部署偏好与客户订单中的参数组合对应起来，从而在NST中消除了和NSD的部署偏好以及VNFD的部署偏好的耦合，大大简化了NST的设计和维护难度。
在一种可能的设计中，所述确定所述业务需求对应的NSD的标识和网络功能信息，包括：
确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络功能信息；
或者，也可以是分别确定出所述业务需求对应的NSD和与所述业务需求匹配的NST，所述NST中包括所述业务需求对应的网络功能信息，在这种情况下，所述NST中可以不包括所述业务需求对应的NSD或所述NSD的标识。
在一种可能的设计中，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连 接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则是根据所述业务需求对应的一个或多个网络功能的需求得到的。
在一种可能的设计中，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，即NST中与所述业务需求对应的一个或多个网络功能进行网络虚拟化部署时所使用的一个或多个VNF的标识。上述VNF的标识还可以根据业务需求对应的多个网络功能的连接关系信息中包含的连接端点(即某个网络功能)来确定。
在一种可能的设计中，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，即为了承载NST中与所述业务需求对应的多个网络功能之间的业务连接，在网络虚拟化部署时所需要建立的VNF之间的网络连接。
在一种可能的设计中，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，即为了满足NST中与所述业务需求对应的多个网络功能之间的业务连接属性要求，在网络虚拟化部署时所需要建立的VNF之间的网络连接应该具备属性。上述多个VNF之间的连接属性信息还可以根据所述业务需求对应网络功能的需求来确定，比如根据作为连接端点的两个网络功能的性能和容量需求确定部署后VNF之间的连接属性信息。
在一种可能的设计中，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则，即为了部署出NST中与所述业务需求对应的具有特定容量、性能、功能特性等属性的网络功能，部署VNF是所应该使用的各项参数。
在一种可能的设计中，所述方法还包括：
将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
如此，NSMF网元可以不具备NFMF网元的功能，即在具体实施中，分别设置NSMF网元和NFMF网元。
在一种可能的设计中，所述生成NFV部署策略之后，还包括：
根据所述业务需求对应的NSD或所述NSD的标识，得到所述NSD的部署偏好；
根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
如此，NSMF网元在确定出NFV部署策略后，直接根据NFV部署策略从得到的NSD的部署偏好中选择满足NFV部署策略的部署偏好，此时，NSMF网元同时具备的PAP和PF的功能。
在一种可能的设计中，所述生成NFV部署策略之后，还包括：
将所述NFV部署策略发送给策略功能网元。
如此，NSMF网元具备PAP的功能，并将生成的NFV部署策略发送策略功能网元，由策略功能网元来实现PF的功能。
第二方面，本申请实施例提供一种网络切片的部署方法，所述方法包括：
接收网络切片管理功能NSMF网元发送的NFV部署策略，所述NFV部署策略包括NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络 服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好；
根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
根据上述内容可知，由NSMF网元根据所述网络切片需求信息生成NFV部署策略，并发送给策略功能网元，如此，策略功能网元可以根据NFV部署策略选择部署偏好；相比于现有技术中需要直接从NST所列出的NSD的所有部署偏好中选择出符合客户订单的部署偏好来说，采用上述方式，在NST中无需将NSD的所有部署偏好与客户订单中的参数组合对应起来，从而在NST中消除了和NSD的部署偏好以及VNFD的部署偏好的耦合，大大简化了NST的设计和维护难度。
第三方面，本申请实施例提供一种网络切片的部署方法，其特征在于，所述方法包括：
接收NSMF网元发送的一个或多个网络功能的需求；
根据所述一个或多个网络功能的需求，生成VNF部署策略，所述VNF部署策略包括一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则。
此处，一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则，即为：部署所述一个或多个网络功能的需求所使用的VNFD中各项参数需要满足的规则。也就是说，所述一个或多个VNF是与所述一个或多个网络功能相对应的。
在一种可能的设计中，所述生成VNF部署策略之后，还包括：
将所述VNF部署策略发送给策略功能网元；或者，
根据所述VNF部署策略，从所述每个VNF所使用的VNFD的部署偏好中选择出满足所述各项参数需要满足的规则的部署偏好。
第四方面，本申请实施例提供一种网络切片的部署方法，其特征在于，所述方法包括：
接收NFMF网元发送的VNF部署策略，所述VNF部署策略包括一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则；
根据所述VNF部署策略，从所述每个VNF所使用的VNFD的部署偏好中选择出满足所述各项参数需要满足的规则的部署偏好。
第五方面，本申请实施例提供一种NSMF网元，所述网络切片管理功能网元包括：
获取模块，用于获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；
确定模块，用于确定所述业务需求对应的网络服务部署模板NSD和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；
处理模块，用于生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD 进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
在一种可能的设计中，所述确定模块具体用于：
确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络功能信息。
在一种可能的设计中，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则是根据所述业务需求对应的一个或多个网络功能的需求得到的。
在一种可能的设计中，所述NSMF网元还包括收发模块；
所述收发模块，用于将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
在一种可能的设计中，所述处理模块还用于：
根据所述业务需求对应的NSD或所述NSD的标识，得到所述NSD的部署偏好；
根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
在一种可能的设计中，所述NSMF网元还包括收发模块；
所述收发模块，用于将所述NFV部署策略发送给策略功能网元。
第六方面，本申请实施例提供一种策略功能网元，所述策略功能网元包括：
收发模块，用于接收NSMF网元发送的NFV部署策略，所述NFV部署策略包括NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
处理模块，用于根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好；以及，根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
本申请实施例的又一方面提供了一种网络切片管理功能NSMF网元，所述NSMF网元包括：
存储器，用于存储软件程序；
处理器，用于执行所述存储器中的软件程序，以使得所述NSMF网元执行上述第一方面所述的网络切片的部署方法。
本申请实施例的又一方面提供了一种策略功能网元，所述策略功能网元包括：
存储器，用于存储软件程序；
处理器，用于执行所述存储器中的软件程序，以使得所述策略功能网元执行上述第二方面中所述的网络切片的部署方法。
本申请实施例的又一方面提供一种装置，该装置具有实现上述第一至第四方面中所描述的网络切片的部署方法的功能。该功能可以通过硬件执行相应的软件实现，在一种可能的设计中，该装置包括：处理器、收发器、存储器；该存储器用于存储计算机执行指令，该收发器用于实现该装置与其他通信实体进行通信，该处理器与该存储器通过该总线连接，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行上述第一方面至第四方面中所描述的网络切片的部署方法。
本申请实施例的又一方面提供一种计算机存储介质，所述存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时实现上述第一方面至第四方面中任一方面所描述的网络切片的部署方法。
本申请实施例的又一方面提供一种网络功能虚拟化NFV***，所述NFV***包括：网络切片管理功能NSMF网元和策略功能网元；
所述NSMF网元用于：获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；确定所述业务需求对应的网络服务部署模板NSD和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则；以及，将所述NFV部署策略发送给策略功能网元；
所述策略功能网元用于：接收NSMF网元发送的NFV部署策略，根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好，并从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
本申请实施例的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面中任意一项所述的网络切片的部署方法。
附图说明
图1a为本申请实施例适用的一种NFV***的整体架构示意图；
图1b为网络切片管理功能与NFV MANO的架构和接口示意图；
图2为一个NS的部署实例图；
图3为两种业务对应的NSD示意图；
图4为VNF-a和VNF-b的部署偏好示意图；
图5为本申请实施例提供的一种装置的结构示意图；
图6为本申请实施例一提供的网络切片的部署方法对应的流程示意图；
图7为本申请实施例二提供的网络切片的部署方法对应的流程示意图；
图8为本申请实施例三提供的网络切片的部署方法对应的流程示意图；
图9为本申请实施例四提供的网络切片的部署方法对应的流程示意图；
图10为本申请实施例提供的一种NSMF网元的结构示意图；
图11为本申请实施例提供的一种策略功能网元的结构示意图。
具体实施方式
下面结合说明书附图对本申请进行具体说明，方法实施例中的具体操作方法也可以应用于装置实施例中。
随着多种多样的通信业务的不断涌现，不同的通信业务对网络性能的需求存在显著的区别，第五代移动通信(the 5th-generation，5G)***引入了网络切片的概念，以应对不同通信业务对网络性能的需求的差异。网络切片是指在物理或者虚拟的网络基础设施上，根据不同的服务需求定制化不同的逻辑网络。网络切片可以是一个包括终端设备、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的通信服务，具有一定网络能力。网络切片也可以是终端设备、接入网、传输网、核心网和应用服务器的任意组合。
网络切片可以通过多种技术来创建，比如网络功能虚拟化(network function virtualization，NFV)和软件定义网络(software defined network，SDN)。本申请实施例中仅基于通过网络功能虚拟化创建网络切片来进行描述。
图1a为本申请实施例适用的一种NFV***的整体架构示意图。如图1a所示，所述NFV***100包括：NFV管理和编排(management and orchestration，MANO)网元101、NFV基础设施(NFV infrastructure，NFVI)层130、多个VNF 108(VNF1、VNF2和VNF3)、网络功能管理功能(network function management function，NFMF)网元122，以及业务支持管理***(operation-support system/business support system，OSS/BSS)124。其中，NFV MANO 101包括NFV编排器(NFV orchestrator，NFVO)102，一个或多个VNF管理器(VNF manager，VNFM)104和虚拟化基础设施管理器(virtualized infrastructure manager，VIM)106。
进一步地，OSS/BSS124中可以包括通信业务管理功能(communication service management function，CSMF)网元、网络切片管理功能(network slice management function，NSMF)网元和网络子网切片管理功能(network slice subnet management function，NSSMF)网元。一个端到端的网络切片包括无线接入网、核心网等各个部分，每一部分我们称为子网切片。NSSMF功能负责管理子网切片。NSMF负责管理端到端的切片。NSSMF和NSMF类似，只不过是接受子网的业务需求，并创建子网切片实例。如果所有子网都是一个厂商提供的，可以不需要NSSMF，直接由NSMF创建无线接入网和核心网。因此，本申请实施 例中的方法对于NSMF和NSSMF都是适用的，也就是说，本申请实施例中所有NSMF相关的描述，也适用于NSSMF，不做具体限定。NFVI 130包括计算硬件112、存储硬件114、网络硬件116、虚拟化层(virtualization layer)、虚拟计算110、虚拟存储118和虚拟网络120。
此处需要说明的是，图1a中仅为一种可能的架构示例，在其它可能的实施例中，NSMF网元也可以直接管理NF，即具备NFMF网元的相关功能，此时可不再单独设置NFMF网元122。其中，本申请实施例的上述网元可以是物理上的实体网元，也可以是虚拟的网元，在此不做限定。
为便于描述，NFV***100包括的各个部分下文中均简称为英文字母缩写，比如NFV MANO简称为NFV MANO。
NFVO102，主要负责处理虚拟化业务的生命周期管理，以及虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO102可以与一个或多个VNFM104通信，以执行资源相关请求，发送配置信息给VNFM104，收集VNF108的状态信息。另外，NFVO102也可与VIM106通信，执行资源分配，和/或预留，交换虚拟化硬件资源配置和状态信息。
VNFM104，主要负责一个或多个VNF的生命周期管理，比如实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF108。VNFM104可以与VNF108通信以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型的VNF进行生命周期管理。
VIM106，控制和管理VNF108与计算硬件112，存储硬件114，网络硬件116，虚拟计算(virtual computing)110，虚拟存储118，虚拟网络120的交互。例如VIM106执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM104及VIM106可以相互通信，请求资源分配，交换虚拟化硬件资源配置和状态信息。
NFVI130即NFV的基础设施层，包含硬件部件，软件部件或两者组合，以建立虚拟化环境，部署，管理及实现VNF108。硬件资源和虚拟化层用于为VNF108提供虚拟化资源，如虚拟机和其他形式的虚拟容器。硬件资源包括计算(computing)硬件112，存储硬件114，网络硬件116。作为一种实施方式，计算硬件112和存储硬件114的资源可以集中在一起。NFVI中的虚拟化层可以抽象硬件资源，解耦VNF108与底层的物理网络层。
每个VNF108运行在一个或多个虚拟容器中，对应于一组属于一个或多个物理设备的网络功能。
OSS/BSS124支持各种端到端电信业务，其中，OSS支持的管理功能包括：网络配置，业务提供，故障管理等；BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
NFV MANO101用于根据网络切片管理功能的NFV部署要求，负责网络切片所需的基础设施资源的分配，并完成虚拟网络功能在虚拟化基础设施上的部署，并完成网络功能实体之间的网络连接。
CSMF负责根据客户的通信业务需求向网络切片管理功能发送网络切片订单请求，网络切片实例创建后还负责管理网络切片实例承载的通信业务。
NSMF负责网络切片实例的创建、激活、运行、去活、删除等整个生命周期管理。NSMF 接受客户的网络切片订单，并根据存储的网络切片模板驱动虚拟化编排和管理功能实体和切片控制功能实体创建网络切片实例。
考虑到网络切片内的各个网络功能实体来自不同的厂商，NFMF122可以通过各个厂商NFMF网元间接管理这些网络功能实体。
上述对NFV***的整体架构进行了较为具体的描述。按照第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的相关协议，NSMF网元通过和NFV MANO的NFVO网元之间的接口，实现网络切片实例的NFV部署。图1b为网络切片管理功能与NFV MANO的架构和接口示意图。
具体应用中，NSMF网元和NFMF网元也可能不是独立的实体，而是都作为运维支撑***(OSS)的一部分。本申请实施例中，NSMF网元和NFMF网元(可选)可以统称为策略管理网元，策略管理网元主要负责生成NFV部署策略；NFVO网元和VNFM网元(可选)可以统称为策略功能网元，策略功能网元主要负责根据NFV部署策略从NSD的部署偏好中选择出满足规则的部署偏好。其中，策略管理网元也可以称为策略管理点(policy administration point，PAP)或者其它名称，具体不做限定；策略功能网元也可以称为策略功能(policy function，PF)实体或者其它名称，具体不做限定。
在其它可能的实施例中，也可以是由NSMF或NSSMF网元作为PAP，NSSMF网元或NFMF网元作为PF；或者，NSMF或NSSMF同时具备PAP和PF的功能；又或者，NFV MANO直接按照本申请实施例中所述方法确定的NSD的部署偏好执行NFV部署；又或者，NSMF或NSSMF按照本申请实施例中所述方法确定的NSD的部署偏好执行NFV部署。本申请实施例不做具体限定。
也就是说，本申请实施例中，当某一网元具备PAP和/或PF的功能时，即可认为是由该网元作为PAP和/或PF。
NSI是一个真实运行的逻辑网络，能够满足一定网络特性或服务需求。NSI可以由NST实例化得到，其中，NST是针对某类业务预先设计的用于创建网络切片实例的模板，NST中可以包括创建NSI所需要进行NFV部署时使用的NSD或者NSD ID。一个完整的NSI可以提供完整的端到端的网络服务，NSI可以包括若干个网络切片子网实例(network slice subnet instance，NSSI)和/或若干个网络功能(network function，NF)。NSSI可以由网络切片子网模板(network slice subnet template，NSST)实例化得到。
基于图1a和图1b所示意的架构，一种部署网络切片实例的方法流程为：CSMF接收客户的业务需求，将业务需求转化成网络切片需求，将网络切片需求发送至NSMF；NSMF将接收到的网络切片需求转化为网络切片子网需求，并将网络切片子网需求发送至NSSMF；NSSMF将网络切片子网需求转换为需要部署的网络功能实例需求，并将网络功能实例需求发送至NFV MANO，NFV MANO根据部署需求在NFVI上分配资源并部署网络切片内相应的VNF实例，以及将VNF实例连接起来。然后，NSMF将业务配置脚本发送到NFMF，NFMF根据脚本在网络切片的VNF上执行相关的业务配置命令，使得客户订单要求的业务能够正常的在切片上运行起来。这样便成功部署出网络切片实例。
在上述过程中，NFV MANO需要根据NSMF网元的要求部署网络服务(network service，NS)实例。在NFV中虚拟化的网络服务称为一个NS，一个NS是由多个VNF以及他们之 间的连接(link)构成的。NS在NFVI上部署时，就会为虚拟机分配一定的CPU，硬盘，内存，并在虚拟机上运行VNF的软件镜像，形成VNF实例，另外分配相应的网络链路，将VNF实例之间按照NSD的描述连接起来，最终形成一个NS实例。
图2为一个NS的部署实例图，如图2所示，该NS实例中包括VNF1、VNF2和VNF3共三个VNF，以及连接点(connect point，CP)1、CP2、CP3、CP4、CP5、CP6共6个CP，以及虚拟连接(virtual link，VL)1和VL2共2个VL。其中，CP4和CP6作为外部连接点分别通过Ext1和Ext2与外部网络进行连接。
需要说明的是，NS可以支持嵌套，即一些VNF的集合构成一个NS后，和其它NS或VNF再形成一个更大范围的NS。在存在嵌套NS(nested NS)时，NSD内可以索引嵌套NS的NSD标识(即NSD ID)。
根据不同部署的需求，NSD中包含若干个NS部署偏好，在每个NS DF中，可以描述NS包含哪些类型的VNF，VNF的网络连接，以及各类VNF的数量等信息。NS DF的标准结构定义可参见表1。
表1：NS DF中的标准结构定义
Figure PCTCN2019080026-appb-000001
举个例子，NST支持两种类型相近的业务应用，如图3所示为这两种业务对应的NSD示意图。在支持业务1时，需要VNF-a～VNF-d四种网络功能；在支持业务2时，需要VNF-a～VNF-e五种网络功能。
类似的，VNFD中也包含若干个DF，在VNFD DF中，可以描述VNF由哪些模块组成，模块之间的网络连接，各种模块的部署数量，各种模块的部署要求，各种模块软件镜像和版本等等信息。VNFD DF的标准结构定义可参见表2所示。
表2：VNFD DF的标准结构定义
Figure PCTCN2019080026-appb-000002
举个例子，如果图3中的VNF-a有3种DF分别支持不同的业务容量(flavour-x、flavour-y、flavour-z)，VNF-b有两种DF分别支持不同业务容量(flavour-m、flavour-n)，其它VNF从最小容量到最大容量的虚拟机的虚拟CPU、虚拟内存和虚拟磁盘存储的数量都相同，因此只有一种DF就足够了。如图4所示，为VNF-a和VNF-b的部署偏好示意图。
如此，将上述各个VNF的VNFD DF经过组合后，NSD中共有12种DF，如表3所示。
表3：NSD DF示例
Figure PCTCN2019080026-appb-000003
现有技术中，设计NST时会将上面例子中的所有NSD DF均列出来，并且确定这些NSD DF分别能够满足客户网络切片订单中哪些参数组合范围，然后就将其和客户订单中的参数组合对应起来。比如DF-12可以满足100万窄带固定物联网终端接入，DF-6能够满足20万时速低于100km/h的宽带移动物联网终端接入，于是就将DF-6和DF-12与订单中的参数组合范围对应起来。
通过这种方法，NSMF根据用户下发的网络切片订单，就能够从NST中选择满足客户订单要求的NSD ID和NSD DF，并将其携带在发送到NFV MANO的部署请求中，NFV MANO就会按照NS DF和VNFD DF完成部署。然而，在NST中列出所有NSD DF和客户订单中的参数组合的对应关系，会导致NST的设计变得非常复杂，维护难度较大。
基于此，本申请实施例提供一种网络切片的部署方法，用于解决NST的设计变得非常复杂，维护难度较大的技术问题。
如图5所示，为本申请实施例提供的一种装置500，包括至少一个处理器51，通信总线52，存储器53以及至少一个通信接口54。该装置500可以是本申请实施例中的任何一个功能网元，该装置500可用于执行本申请实施例提供的网络切片的部署方法。
处理器51可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线52可包括一通路，在上述组件之间传送信息。所述通信接口54，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，WALN等。
存储器53可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的 其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由该装置存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器53用于存储执行本申请方案的应用程序代码，并由处理器51来控制执行。
在具体实现中，作为一种实施例，处理器51可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，该装置500可以包括多个处理器，例如图5中的处理器51和处理器55。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
示例性的，图5所示的装置可以为策略管理网元或策略管理网元的组成部分，图5所示的装置的存储器中存储了一个或多个软件模块。图5所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由策略管理网元执行的网络切片的部署方法。
示例性的，图5所示的装置可以为策略功能网元或策略功能网元的组成部分，图5所示的装置的存储器中存储了一个或多个软件模块。图5所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由策略功能网元执行的网络切片的部署方法。
在以下实施例中，步骤编号仅仅是为了方便描述，各步骤之间没有严格的执行先后关系。
实施例一
图6为本申请实施例一提供的网络切片的部署方法对应的流程示意图，如图6所示，包括：
步骤601，NSMF网元获取网络切片需求信息，所述网络切片需求信息包括待部署的NSI需要承载的业务需求，以及确定所述业务需求对应的NSD和网络功能信息。其中，所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求。
此处，在一个示例中，NSMF网元接收部署NSI的订单，并根据订单获取到网络切片需求信息。
其中，NSI需要承载的业务需求可以包括一种或多种需求信息，比如，NSI需要承载的业务需求可以包括表4所列举出的任一项或任意组合。
表4：需求信息示例
Figure PCTCN2019080026-appb-000004
Figure PCTCN2019080026-appb-000005
本申请实施例中，NSI需要承载的业务需求可以为运营商发布网络切片产品时，将NST中列出参数提供给用户在一定范围内选择或指定得到的。如此，NSI需要承载的业务需求可与某一NST相匹配。
举个例子，订单要求在某一区域为2万辆共享单车提供通信服务，如此，可知NSI需要承载的业务需求中包括业务类型(物联网)、业务的区域容量(2万)。NST1、NST2和NST3中包含的业务需求分别如表5所示。
表5：NST1、NST2和NST3中满足的业务需求示例
Figure PCTCN2019080026-appb-000006
Figure PCTCN2019080026-appb-000007
表5中，NST1、NST2和NST3中包含的业务类型均为物联网，NST1中包含的业务的区域容量包括两个级别，分别为1万～1.2万和1.2万～1.5万；NST2中包含的业务的区域容量包括三个级别，分别为1.5万～1.6万、1.6万～1.7万和1.7万～1.8万；NST3中包含的业务的区域容量包括两个级别，分别为1.8万～2.1万和2.1万～2.4万。如此，可确定出上述三个NST中与NSI需要承载的业务需求匹配的NST为NST3。
进一步地，NST中还可以包括所述业务需求对应的NSD或NSD的标识，以及所述业务需求对应的网络功能信息。如此，NSMF网元可根据与业务需求匹配的NST，确定出所述业务需求对应的NSD和网络功能信息。或者，在其它可能的实施例中，NSMF网元也可以直接根据所述业务需求，确定出所述业务需求对应的NSD，以及与所述业务需求匹配的NST，NST中包括所述业务需求对应的网络功能信息；此种情况下，NST中可以不包括所述业务需求对应的NSD或NSD的标识。
基于上述示例，下面进一步列举出NST3中包括的内容。表6仅以NST3中包括上述所列举的所有内容为例进行示意。
表6：NST3包含的内容示例
Figure PCTCN2019080026-appb-000008
根据表6可知，根据NSI需要承载的业务需求，可从NST中得到该业务需求对应的NSD或NSD的标识，以及该业务需求对应的网络功能信息。
具体来说，所述业务需求对应的一个或多个网络功能可以是指无线接入网(radio access network，RAN)、用户面功能(user plane function，UPF)网元、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、应用服务(application service，AS)等网络功能；所述业务需求对应的多个网络功能的连接关系用于描述多个网络功能之间是否存在链路连接，比如，RAN与UPF之间是否存在链路连接；所述业务需求对应的多个网络功能的连接属性信息用于描述多个网络功能之间的连接的属性，比如该连接为用户面连接或控制面连接等，连接属性信息要求使用连接点和链路的属性来描述；所述业务需求对应的一个或多个网络功能的需求用于描述NS实例或VNF实例需要具备的功能单元，需要满足的实例数量，性能指标参数，保障参数和资源需求中的一项或多项，具体不做限定。
基于上述在某一区域为2万辆共享单车提供通信服务的示例，NST中描述支持该类业 务的VNF-a类型的网络功能和VNF-d类型的网络功能之间需要建立数据连接，VNF-d类型的网络功能的最大连接数量不小于2万，即该业务需求对应的VNF-d类型的网络功能的需求为[VNF-d.max_session>＝20000]。
步骤602，NSMF网元生成对所述NSI进行NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
其中，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识即为对所述NSI进行NFV部署时需要使用的NSD或NSD的标识。
进一步地，以上述表6所示意的内容为例，由于与NSI需要承载的业务需求匹配的NST中包括该业务需求对应的一个或多个网络功能、该业务需求对应的多个网络功能的连接关系、该业务需求对应的多个网络功能的连接属性信息、该业务需求对应的一个或多个网络功能的需求，因此，NSMF网元可以根据该业务需求对应的一个或多个网络功能得到所述NSD包含的一个或多个VNF的标识，根据该业务需求对应的多个网络功能的连接关系得到所述NSD中包含的多个VNF之间的连接关系，根据该业务需求对应的多个网络功能的连接属性信息得到所述NSD中包含的多个VNF之间的连接属性信息，根据该业务需求对应的一个或多个网络功能的需求得到所述NSD包含的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则。
比如，上述所描述的业务需求(业务类型为物联网，业务的区域容量为2万)对应的网络功能为RAN、AMF、SMF、UPF，则NSMF网元可得到NSD中包含的VNF的标识为VNFa(对应RAN)、VNFb(对应AMF)、VNFc(对应SMF)和VNFd(对应UPF)。上述所描述的业务需求(业务类型为物联网，业务的区域容量为2万)对应的多个网络功能中RAN分别和AMF、UPF连接，AMF和SMF连接，SMF和UPF连接，则NSMF网元可得到NSD中包含的VNF中VNFa分别和VNFb、VNFd连接，VNFb和VNFc连接，VNFc和VNFd连接。其中，VNFa分别和VNFb、VNFd连接可表示为：[VNF-a in NS.elements_list]and[VNF-d in NS.elements_list]and[VL.connection＝(VNF-a.CP2,VNF-d.CP1)]。
其中，NSMF网元根据该业务需求对应的一个或多个网络功能的需求得到所述NSD包含的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则的具体实现过程可以为：NSMF网元根据一个或多个网络功能的需求，以及NST中的网络功能的实现规格，确定部署对应的VNF所使用的VNFD中各项参数需要满足的规则。其中，NST中的网络功能的实现规格可以是根据各个厂商网络功能的实际规格得到的。
比如，NSMF网元可以根据业务功能需求确定VNF的版本号，以及包含VNF组件(VNF component，VNFC)，这些VNFC对应哪些虚拟化部署单元(virtualization deployment unit，VDU)，还可以根据NF的需求确定VNF中的各个VDU的数量等等。在上面的例子中，NSMF网元根据VNF-d的业务性能规格，按照NST中网络功能的实际规格，将[VNF-d.max_session>＝20000]的需求，转换成[LB_VDU.instace_number>＝2]and [UP_VDU.instace_number>＝4]，并将其作为VNF-d所使用的VNFD中各项参数需要满足的规则。
步骤603，NSMF网元将所述NFV部署策略发送给策略功能网元。
步骤604，策略功能网元接收NSMF网元发送的NFV部署策略。
步骤605，策略功能网元根据所述NSD或NSD的标识，得到所述NSD的部署偏好，并根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述规则的部署偏好。此处，所述NSD的部署偏好是指综合考虑NS的部署偏好(参见图3的描述)和VNF的部署偏好(参见图4的描述)后得到的所有部署偏好，即为表3中所示意出的12种部署偏好。
本申请实施例中，策略功能网元可以包括NFVO网元和VNFM网元，如此，在步骤603中，NSMF网元可以将所述NFV部署策略发送给NFVO网元。
相应地，在步骤604中，NFVO网元接收NFV部署策略。
由于NFV部署策略包括的对所述NSI进行NFV部署时需要使用的NSD或NSD的标识、所述NSD包含的一个或多个VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息等信息均用于进行NS的部署，因此，可以将这些信息称为NS部署策略。由于与所述一个或多个网络功能对应的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则用于进行VNF的部署，因此，可以将其称为VNF部署策略。
相应地，步骤605可包括：步骤605a，NFVO网元根据NS部署策略从所述NSD的部署偏好中选择出备选部署偏好。具体来说，NFVO网元可以根据所述NSD或NSD的标识，得到所述NSD的部署偏好(比如表3所示意出的12种部署偏好)，并根据NFV部署策略中所述NSD包含的一个或多个VNF的标识(VNFa、VNFb、VNFc和VNFd)、所述NSD包含的多个VNF之间的连接关系(VNFa分别和VNFb、VNFd连接，VNFb和VNFc连接，VNFc和VNFd连接)、所述NSD包含的多个VNF之间的连接属性信息(暂未示意出)，从所述NSD的部署偏好中选择部署偏好，具体地，选择出的部署偏好为NSD DF-1至NSD DF-6。由于此时从NSD的部署偏好中选择出的部署偏好可能为多个，后续还需进一步结合VNFM网元选择出的VNFD的部署偏好得到最终的部署偏好，因此，为便于描述，可将此时选择出的部署偏好简称为备选部署偏好。
在其它可能的实施例中，NFVO可以通过过滤NS的部署偏好中的flavour key和flavour内容的各个参数，找到满足规则的NSD DF。参照图3为例，NSD DF“业务1”满足[VNF-a in NS.elements_list]and[VNF-d in NS.elements_list]and[VL.connection＝(VNF-a.CP2,VNF-d.CP1)]，因此NFVO可选择该NS的部署偏好作为备选部署偏好。
进一步地，步骤605还包括：步骤605b，NFVO网元将NSD包含的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则(即VNF部署策略)发送给VNFM网元；步骤605c，VNFM网元根据每个VNF所使用的VNFD中各项参数需要满足的规则，从所述每个VNF所使用的VNFD的部署偏好中选择出满足所述规则的部署偏好。
其中，每个VNFD的部署偏好中可以描述有VNF的版本、业务功能、性能等属性，以及包含的VNFC类型和对应的VDU数量。在其它可能的实施例中，还可以描述有其它可能 的属性，具体不做限定。
具体来说，针对每个VNF，VNFM网元可以通过过滤该VNF所使用的VNFD的部署偏好中的flavour key和flavour内容的各个参数，选择出满足规则的VNFD的部署偏好。比如，VNF-d的flavour-d能够满足[LB_VDU.instace_number>＝2]and[UP_VDU.instace_number>＝4]，则选择出flavour-d；又比如，VNF-a的flavour-x能够满足VNF-a所使用的VNFD中各项参数需要满足的规则，则选择出flavour-x；又比如，VNF-b的flavour-m能够满足VNF-b所使用的VNFD中各项参数需要满足的规则，则选择出flavour-m；如此，可选择出每个VNF的VNFD的部署偏好。
需要说明的是，针对于某个VNF，若满足规则的VNFD的部署偏好有两个或两个以上，则VNFM网元可按照VNFD中的部署偏好的顺序选择最前面的部署偏好。若无法选择出满足规则的VNFD的部署偏好，则VNFM网元可以使用默认的部署偏好(default DF)。
步骤606，VNFM网元将选择出的每个VNF所使用的VNFD的部署偏好发送给NFVO网元。
本申请实施例中，可以是先由NFVO网元请求VNFM网元选择每个VNF所使用的VNFD的部署偏好，进而，VNFM网元根据NFVO网元的请求，将选择出的每个VNF所使用的VNFD的部署偏好发送给NFVO网元。
步骤607，NFVO网元根据步骤605a中选择出的备选部署偏好和VNFM网元选择出的每个VNF所使用的VNFD的部署偏好，确定出最终的部署偏好，并根据确定出的部署偏好对NSI进行部署。
比如，步骤605a中选择出的备选部署偏好为NSD DF-1至NSD DF-6，VNFM网元选择出的每个VNF所使用的VNFD的部署偏好分别为：flavour-x、flavour-m、flavour-c、flavour-d，从而确定出最终的部署偏好为NSD DF-1。
此处，若上述每个VNF都仅有一种部署偏好，则NFVO网元可以直接根据选择出的备选部署偏好对NSI进行部署。此时，若选择出的备选部署偏好有两个或两个以上，则可以按照部署偏好的优先级(默认部署偏好的优先级最高)或顺序选择其中的一个，并根据选择出的部署偏好对NSI进行部署。
具体的部署过程可以为：NFVO网元按照VNFM返回的结果(即选择出的每个VNF所使用的VNFD的部署偏好)命令VIM网元在NFVI上进行虚拟资源分配和NFV部署。该过程可参见现有技术，此处不再赘述。
在其它可能的实施例中，VNFM网元选择出每个VNF所使用的VNFD的部署偏好后，可以不再发送给NFVO网元，而直接由VNFM网元命令VIM网元在NFVI上按照部署偏好进行虚拟资源分配和NFV部署。本申请实施例对具体的部署方式不做限定。
需要说明的是，上述描述中，所述网络服务实例化需要满足的规则包括有所述NSD包含的一个或多个VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则，在其它可能的实施例中，所述网络服务实例化需要满足的规则也可以仅包括其中的部分信息。
举个例子，对所述NSI进行NFV部署时需要使用的NSD有两种部署偏好，如图3所 示意(设NSD所包含的各个VNF均只有一个部署偏好)。由于两种部署偏好中包含的VNF的标识存在差异，即第一种部署偏好中不存在VNFe，第二种部署偏好中包含VNFe，因此，对两种部署偏好可以依据VNF的标识进行区分。此时，所述网络服务实例化需要满足的规则只需包括对所述NSI进行NFV部署时需要使用的NSD或所述NSD的标识，以及所述NSD包含的一个或多个VNF的标识即可，NFVO网元可以根据对所述NSI进行NFV部署时要使用的NSD或所述NSD的标识，得到所述NSD的上述两个部署偏好，进而依据所述NSD包含的一个或多个VNF的标识，从两个部署偏好中选择出满足规则的部署偏好。比如，所述NSD包含的VNF的标识中不存在VNFe，因此，可将第一种部署偏好作为满足所述规则的部署偏好。此时，由于NSD所包含的各个VNF均只有一个部署偏好，因此，所述网络服务实例化需要满足的规则中不需要包括所述NSD包含的一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则，也无需执行选择VNFD的部署偏好的过程。
如此，本申请实施例中所述网络服务实例化需要满足的规则中所包括的内容可以有多种可能，具体不做限定。
可以理解的，由于所述网络服务实例化需要满足的规则是根据所述业务需求对应的网络功能信息得到的，即：所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。因此，所述业务需求对应的网络功能信息中所包括的内容也相应地可以有多种可能。具体实施中，所述业务需求对应的网络功能信息中所包括的内容可以多于或等于所述网络服务实例化需要满足的规则中所包括的内容。
例如1，所述业务需求对应的网络功能信息中仅包括所述业务需求对应的一个或多个网络功能，则此时，对应得到的所述网络服务实例化需要满足的规则中也仅包括：所述NSD包含的一个或多个VNF的标识。
例如2，所述业务需求对应的网络功能信息中包括所述业务需求对应的多个网络功能和多个网络功能的连接关系，则此时，对应得到的所述网络服务实例化需要满足的规则中可以是仅包括：所述NSD包含的多个VNF的标识；或者，也可以是包括所述NSD包含的多个VNF的标识和多个VNF之间的连接关系。
本申请实施例中所扩展的多种可能的情形，可由本领域技术人员在具体实施中根据实际情况进行合理设置。
根据上述内容可知，由NSMF网元根据所述网络切片需求信息生成NFV部署策略，并发送给策略功能网元，如此，策略功能网元可以根据NFV部署策略选择部署偏好；相比于现有技术中需要直接从NST所列出的NSD的所有部署偏好中选择出符合客户订单的部署偏好来说，采用上述方式，在NST中无需将NSD的所有部署偏好与客户订单中的参数组合对应起来，从而在NST中消除了和NSD的部署偏好以及VNFD的部署偏好的耦合，大大简化了NST的设计和维护难度。
需要说明的是，上述在描述NST中所包括的内容时，业务需求对应的一个或多个网络 功能也可以为网络功能集合的形式，比如下一代无线接入技术(next generation-radio access network，NG-RAN)，第五代核心网(5 thGeneration Core network，5GC)等。此种情况下，在一个示例中，NST中包括的内容为：所述业务需求对应的NSD或NSD的标识、所述业务需求对应的一个或多个网络功能集合、所述业务需求对应的多个网络功能集合之间的连接关系、所述业务需求对应的多个网络功能集合之间的连接属性信息、所述业务需求对应的一个或多个网络功能集合的需求。
相应地，NSMF网元可根据NST中包括的内容为所述业务需求对应的一个或多个网络功能集合得到NSD中包含的部署所述网络功能集合所需的嵌套的NSD(nested NSD)的标识，根据所述业务需求对应的网络功能集合之间的连接关系得到：根据NSD中包含的嵌套的NSD进行网络服务实例化后部署出的嵌套NS实例之间或与其它VNF实例之间的连接关系，根据所述业务需求对应的多个网络功能集合之间的连接属性信息得到：根据NSD中包含的嵌套的NSD进行网络服务实例化后部署出的嵌套NS实例之间或与其它VNF实例之间的连接属性信息，根据所述业务需求对应的一个或多个网络功能集合的需求得到嵌套NS实例需要具备的功能特征，包含的VNF实例的数量，性能指标参数，保障参数和资源需求等。
在上述实施例一中，NSMF网元可以直接管理NF，即具有NFMF网元的相关功能，此时无需单独设置NFMF网元。可以理解的，NSMF网元也可以不具有NFMF网元的相关功能，此时需要单独设置NFMF网元。下面结合实施例二进行描述。
实施例二
图7为本申请实施例二提供的网络切片的部署方法对应的流程示意图，如图7所示，包括：
步骤701，NSMF网元获取网络切片需求信息，所述网络切片需求信息包括待部署的NSI需要承载的业务需求，以及确定所述业务需求对应的NSD和网络功能信息。其中，所述网络功能信息包括以下任一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求。
步骤702，NSMF网元生成NS部署策略，所述NS部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息。
步骤703，NSMF网元将NS部署策略发送给NFVO网元。
步骤704，NFVO网元接收NS部署策略，并根据NS部署策略选择出备选部署偏好。
若所述网络功能信息中包括所述一个或多个网络功能的需求，则所述NSMF网元还可以执行步骤705。
步骤705，NSMF网元将所述业务需求对应的一个或多个网络功能的需求发送给NFMF网元。
此处，一个或多个网络功能的需求即为NSMF网元根据网络切片需求信息得到的NSI需要承载的业务需求对应的一个或多个网络功能的需求。比如，在实施例一中所描述的在 某一区域为2万辆共享单车提供通信服务的示例，该业务需求对应的其中一个网络功能的需求为[VNF-d.max_session>＝20000]。
步骤706，NFMF网元接收一个或多个网络功能的需求，并根据所述一个或多个网络功能的需求，生成一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则(即VNF部署策略)。
具体来说，NFMF网元可根据一个或多个网络功能的需求，以及NST中的网络功能的实现规格，确定部署对应的VNF所使用的VNFD中各项参数需要满足的规则，并生成VNF的部署策略。其中，NST中的网络功能的实现规格可以是根据各个厂商网络功能的实际规格得到的。
比如，NFMF网元可以根据业务功能需求确定VNF的版本号，以及包含VNF组件(VNF component，VNFC)，这些VNFC对应哪些虚拟化部署单元(virtualization deployment unit，VDU)，还可以根据NF的需求确定VNF中的各个VDU的数量等等。在上面的例子中，NFMF根据VNF-d的业务性能规格，按照厂商网络功能的实际规格，将[VNF-d.max_session>＝20000]的需求，转换成[LB_VDU.instace_number>＝2]and[UP_VDU.instace_number>＝4]，并将其作为VNF部署策略。
步骤707，NFMF网元将VNF部署策略发送给VNFM网元，其中，VNF部署策略包括一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则。
此处，若每种网络功能对应的VNF都使用统一的VNFD，属性差异甚至厂商差异都以不同VNFD的部署偏好的形式来描述，则还可以将统一的VNFD的标识事先配置到NFMF网元上，如此，NFMF网元发送给VNFM的消息中还可以携带VNFD的标识。
步骤708，VNFM网元根据每个VNF所使用的VNFD中各项参数需要满足的规则，从所述每个VNF所使用的VNFD的部署偏好中选择出满足规则的VNFD的部署偏好。
具体来说，VNFM网元可以通过过滤VNFD的部署偏好中的flavour key和flavour内容的各个参数，选择出满足规则的VNFD的部署偏好。
步骤709，VNFM网元将选择出的每个VNF所使用的VNFD的部署偏好发送给NFVO网元。
步骤710，NFVO网元根据备选部署偏好和VNFM网元选择出的每个VNF所使用的VNFD的部署偏好，确定出最终的部署偏好，并根据确定出的部署偏好对NSI进行部署。
需要说明的是，实施例二与实施例一的差异在于：实施例一中，NSMF网元执行了NFMF网元的相关功能，实施例二中，由NFMF网元单独执行相关功能；除此差异之外的其它内容，实施例二和实施例一可相互参照。
实施例三
图8为本申请实施例三提供的网络切片的部署方法对应的流程示意图，如图8所示，包括：
步骤801，NSMF网元获取网络切片需求信息，所述网络切片需求信息包括待部署的NSI需要承载的业务需求，以及确定所述业务需求对应的NSD和网络功能信息。其中，所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、 所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求。
步骤802，NSMF网元生成NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
步骤803，NSMF网元根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述规则的部署偏好。
具体来说，NSMF网元可以根据NS部署策略从NSD的部署偏好中选择出备选部署偏好，比如，选择出的备选部署偏好为NSD DF-1至NSD DF-6；以及根据VNF部署策略，从每个VNF所使用的VNFD的部署偏好中选择出满足所述规则的部署偏好，比如，选择出的每个VNF所使用的VNFD的部署偏好分别为：flavour-x、flavour-m、flavour-c、flavour-d；进而，NSMF网元可确定出满足所述网络服务实例化需要满足的规则的部署偏好为NSD DF-1。
步骤804，NSMF网元将选择出的部署偏好发送给NFVO网元。
步骤805，NFVO网元根据接收到的部署偏好对NSI进行部署。
需要说明的是，实施例三与实施例一的差异在于：实施例一中，NSMF网元生成NFV部署策略后，将NFV部署策略发送给NFVO网元，进而由NFVO网元选择备选部署偏好，以及由VNFM网元选择VNFD的部署偏好，并根据选择出的备选部署偏好和选择出的VNFD的部署偏好对NSI进行部署；而实施例三中，NSMF网元生成NFV部署策略后，直接由NSMF网根据NFV部署策略，从NSD的部署偏好中选择满足所述规则的部署偏好，进而发给NFVO网元对NSI进行部署。除此之外的其它内容，实施例三和实施例一可相互参照。
实施例四
图9为本申请实施例四提供的网络切片的部署方法对应的流程示意图，如图9所示，包括：
步骤901，NSMF网元获取网络切片需求信息，所述网络切片需求信息包括待部署的NSI需要承载的业务需求，以及确定所述业务需求对应的NSD和网络功能信息。其中，所述网络功能信息包括以下任一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求。
步骤902，NSMF网元生成NS部署策略，所述NS部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息。
步骤903，NSMF网元根据NS部署策略选择出备选部署偏好。
步骤904，NSMF网元将选择出的备选部署偏好发送给NFVO网元。
若所述网络功能信息中包括所述一个或多个网络功能的需求，则所述NSMF网元还可以执行步骤905。
步骤905，NSMF网元将所述业务需求对应的一个或多个网络功能的需求发送给NFMF网元。
步骤906，NFMF网元根据所述一个或多个网络功能的需求，生成一个或多个VNF的每个VNF所使用的VNFD中各项参数需要满足的规则。
步骤907，NFMF网元根据每个VNF所使用的VNFD中各项参数需要满足的规则，从每个VNF所使用的VNFD的部署偏好中选择出满足每个VNF所使用的VNFD中各项参数需要满足的规则的部署偏好。
步骤908，NFMF网元将选择出VNFD的部署偏好发送给VNFM网元。
步骤909，VNFM网元将选择出的VNFD的部署偏好发送给NFVO网元。
步骤910，NFVO网元根据备选部署偏好和VNFM网元选择出的VNFD的部署偏好，确定出最终的部署偏好，并根据确定出的部署偏好对NSI进行部署。
需要说明的是，实施例四与实施例二的差异在于：实施例二中，NSMF网元生成NFV部署策略后，由NSMF网元将NS部署策略发送给NFVO网元，进而NFVO网元根据NS部署策略从NSD的部署偏好中选择出备选部署偏好，以及由NFMF网元将VNF部署策略发送给VNFM网元，进而VNFM网元根据VNF部署策略选择出VNFD的部署偏好；实施例四中，NSMF网元生成NFV部署策略后，直接由NSMF网元根据NS部署策略从NSD的部署偏好中选择出备选部署偏好，NFMF网元生成VNF部署策略后，直接由NFMF网元根据VNF部署策略选择出VNFD的部署偏好。除此之外的其它内容，实施例四和实施例二可相互参照。
针对于上述方方法流程，本申请实施例还提供一种NSMF网元和策略功能网元，该NSMF网元和策略功能网元的具体实现可参见上述方法流程。
图10为本申请实施例提供一种NSMF网元的结构示意图，该NSMF网元可用于实现上述图6至图9中的相应流程，所述NSMF网元1000包括：处理模块801和收发模块802；所述NSMF网元1000包括：
获取模块1001，用于获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；
确定模块1002，用于确定所述业务需求对应的网络服务部署模板NSD和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；
处理模块1003，用于生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意 一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
在一种可能的设计中，所述确定模块1002具体用于：
确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络功能信息。
在一种可能的设计中，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
在一种可能的设计中，所述NSMF网元还包括收发模块1004；
所述收发模块1004，用于将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
在一种可能的设计中，所述处理模块1003还用于：
根据所述业务需求对应的NSD或NSD的标识，得到所述NSD的部署偏好；
根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
在一种可能的设计中，所述NSMF网元还包括收发模块1004；
所述收发模块1004，用于将所述NFV部署策略发送给策略功能网元。
图11为本申请实施例提供一种策略功能网元的结构示意图，该策略功能网元可用于实现上述图6至图9中的相应流程，所述策略功能网元1100包括：
收发模块1101，用于接收NSMF网元发送的NFV部署策略，所述NFV部署策略包括NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
处理模块1102，用于根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好；以及，根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述规则的部署偏好。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产 品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (22)

  1. 一种网络切片的部署方法，其特征在于，所述方法包括：
    获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；
    确定所述业务需求对应的网络服务部署模板NSD的标识和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；
    生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
  2. 根据权利要求1所述的方法，其特征在于，所述确定所述业务需求对应的NSD的标识和网络功能信息，包括：
    确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络功能信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则是根据所述业务需求对应的一个或多个网络功能的需求得到的。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述生成NFV部署策略之后，还包括：
    根据所述业务需求对应的NSD或NSD的标识，得到所述NSD的部署偏好；
    根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述生成NFV部署策略之后，还包括：
    将所述NFV部署策略发送给策略功能网元。
  7. 一种网络切片的部署方法，其特征在于，所述方法包括：
    接收网络切片管理功能NSMF网元发送的网络功能虚拟化NFV部署策略，所述NFV部署策略包括网络服务部署模板NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连 接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则；
    根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好；
    根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
  8. 一种网络切片管理功能NSMF网元，其特征在于，所述NSMF网元包括：
    获取模块，用于获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；
    确定模块，用于确定所述业务需求对应的网络服务部署模板NSD的标识和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；
    处理模块，用于生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
  9. 根据权利要求8所述的NSMF网元，其特征在于，所述确定模块具体用于：
    确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络功能信息。
  10. 根据权利要求8或9所述的NSMF网元，其特征在于，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则是根据所述业务需求对应的一个或多个网络功能的需求得到的。
  11. 根据权利要求8至10中任一项所述的NSMF网元，其特征在于，所述NSMF网元还包括收发模块；
    所述收发模块，用于将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
  12. 根据权利要求8至11中任一项所述的NSMF网元，其特征在于，所述处理模块还用于：
    根据所述业务需求对应的NSD或所述NSD的标识，得到所述NSD的部署偏好；
    根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
  13. 根据权利要求8至11中任一项所述的NSMF网元，其特征在于，所述NSMF网元还包括收发模块；
    所述收发模块，用于将所述NFV部署策略发送给策略功能网元。
  14. 一种策略功能网元，其特征在于，所述策略功能网元包括：
    收发模块，用于接收网络切片管理功能NSMF网元发送的网络功能虚拟化NFV部署策略，所述NFV部署策略包括网络服务部署模板NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则。
    处理模块，用于根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好；以及，根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
  15. 一种网络切片管理功能NSMF网元，其特征在于，所述NSMF网元包括：
    存储器，用于存储软件程序；
    处理器，用于执行所述存储器中的软件程序，以使得所述NSMF网元执行权利要求1至权利要求6中任一项所述的网络切片的部署方法。
  16. 一种策略功能网元，其特征在于，所述策略功能网元包括：
    存储器，用于存储软件程序；
    处理器，用于执行所述存储器中的软件程序，以使得所述策略功能网元执行权利要求7中所述的网络切片的部署方法。
  17. 一种计算机存储介质，其特征在于，所述存储介质中存储软件程序，该软件程序在被一个或多个处理器执行时实现权利要求1至权利要求7中任一项所述的网络切片的部署方法。
  18. 一种网络功能虚拟化NFV***，其特征在于，所述NFV***包括：网络切片管理功能NSMF网元和策略功能网元；
    所述NSMF网元用于：获取网络切片需求信息，所述网络切片需求信息包括待部署的网络切片实例NSI需要承载的业务需求；确定所述业务需求对应的网络服务部署模板NSD的标识和网络功能信息，所述业务需求对应的网络功能信息包括以下任意一项或任意多项的组合：所述业务需求对应的一个或多个网络功能、所述业务需求对应的多个网络功能的连接关系、所述业务需求对应的多个网络功能的连接属性信息和所述业务需求对应的一个或多个网络功能的需求；生成对所述NSI进行网络功能虚拟化NFV部署的NFV部署策略，所述NFV部署策略包括所述业务需求对应的NSD或所述NSD的标识，以及根据所述NSD进行网络服务实例化需要满足的规则；所述网络服务实例化需要满足的规则包括以下任意一项或任意多项的组合：所述NSD包含的一个或多个虚拟化网络功能VNF的标识、所述NSD包含的多个VNF之间的连接关系、所述NSD包含的多个VNF之间的连接属性信息、所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则；以及，将所述NFV部署策略发送给策略功能网元；
    所述策略功能网元用于：接收NSMF网元发送的NFV部署策略，根据所述NSD或所述NSD的标识，得到所述NSD的部署偏好，并从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
  19. 根据权利要求18所述的***，其特征在于，所述NSMF网元，用于确定所述业务需求对应的NSD的标识和网络功能信息，具体为：确定与所述业务需求匹配的网络切片模板NST，所述NST中包括所述业务需求对应的NSD或所述NSD的标识，以及所述业务需求对应的网络 功能信息。
  20. 根据权利要求18或19所述的***，其特征在于，其特征在于，所述NSD包含的一个或多个VNF的标识是根据所述业务需求对应的一个或多个网络功能得到的，所述NSD包含的多个VNF之间的连接关系是根据所述业务需求对应的多个网络功能的连接关系得到的，所述NSD包含的多个VNF之间的连接属性信息是根据所述业务需求对应的多个网络功能的连接属性信息得到的，所述NSD包含的一个或多个VNF中的每个VNF所使用的VNFD中各项参数需要满足的规则是根据所述业务需求对应的一个或多个网络功能的需求得到的。
  21. 根据权利要求18至20中任一项所述的***，其特征在于，所述NSMF网元，还用于将所述业务需求对应的一个或多个网络功能的需求发送给网络功能管理功能NFMF网元。
  22. 根据权利要求18至21中任一项所述的***，其特征在于，所述NSMF网元，还用于：根据所述业务需求对应的NSD或NSD的标识，得到所述NSD的部署偏好；根据所述网络服务实例化需要满足的规则，从所述NSD的部署偏好中选择满足所述网络服务实例化需要满足的规则的部署偏好。
PCT/CN2019/080026 2018-03-29 2019-03-28 一种网络切片的部署方法及装置 WO2019184967A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP19774607.6A EP3720050B1 (en) 2018-03-29 2019-03-28 Method and apparatus for deploying network slice
KR1020207018552A KR102409142B1 (ko) 2018-03-29 2019-03-28 네트워크 슬라이스 배치 방법 및 장치
JP2020554359A JP7074880B2 (ja) 2018-03-29 2019-03-28 ネットワーク・スライスの展開方法および装置
BR112020013497-0A BR112020013497A2 (pt) 2018-03-29 2019-03-28 método e sistema de implantação de fatia de rede, elemento de rede de função e de política, e meio de armazenamento
US16/901,195 US11283684B2 (en) 2018-03-29 2020-06-15 Network slice deployment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810274372.1 2018-03-29
CN201810274372.1A CN110324164B (zh) 2018-03-29 2018-03-29 一种网络切片的部署方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/901,195 Continuation US11283684B2 (en) 2018-03-29 2020-06-15 Network slice deployment method and apparatus

Publications (1)

Publication Number Publication Date
WO2019184967A1 true WO2019184967A1 (zh) 2019-10-03

Family

ID=68060860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/080026 WO2019184967A1 (zh) 2018-03-29 2019-03-28 一种网络切片的部署方法及装置

Country Status (7)

Country Link
US (1) US11283684B2 (zh)
EP (1) EP3720050B1 (zh)
JP (1) JP7074880B2 (zh)
KR (1) KR102409142B1 (zh)
CN (2) CN112187545B (zh)
BR (1) BR112020013497A2 (zh)
WO (1) WO2019184967A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021157934A1 (ko) * 2020-02-07 2021-08-12 삼성전자 주식회사 무선 통신 시스템에서 네트워크 슬라이스를 생성하기 위한 장치 및 방법
WO2021215756A1 (ko) * 2020-04-24 2021-10-28 삼성전자 주식회사 네트워크 슬라이스 자원 할당 및 시각화 방법
WO2021219233A1 (en) * 2020-04-30 2021-11-04 Telefonaktiebolaget Lm Ericsson (Publ) Network management
US11323336B2 (en) * 2017-09-27 2022-05-03 Huawei Technologies Co., Ltd. Network slice management method and device
CN114788241A (zh) * 2019-12-04 2022-07-22 皇家Kpn公司 提供网络管理与切片管理之间的接口
CN116436782A (zh) * 2023-06-09 2023-07-14 中国电信股份有限公司四川分公司 一种体现业务意愿的确定性网络传输方法
EP4178295A4 (en) * 2020-07-23 2024-01-10 Huawei Tech Co Ltd SERVICE PROCESSING METHOD AND NETWORK DEVICE

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110572272B (zh) * 2018-06-06 2020-11-06 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排***
CN110661641B (zh) * 2018-06-29 2021-07-16 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
US10708368B1 (en) * 2019-10-30 2020-07-07 Verizon Patent And Licensing Inc. System and methods for generating a slice deployment description for a network slice instance
US11444851B2 (en) * 2020-04-13 2022-09-13 Verizon Patent And Licensing Inc. Systems and methods of using adaptive network infrastructures
CN111555911B (zh) * 2020-04-23 2022-09-30 北京思特奇信息技术股份有限公司 一种基于产品服务模板的5g网络切片产品快速设计方法
CN111565120B (zh) * 2020-04-27 2022-08-16 北京思特奇信息技术股份有限公司 一种5g网络切片产品配置方法、***及电子设备
FR3111512A1 (fr) * 2020-06-18 2021-12-17 Orange Procédé de configuration d’un dispositif terminal
EP4162362A4 (en) * 2020-06-25 2023-12-13 Samsung Electronics Co., Ltd. METHOD AND SYSTEM FOR LIFECYCLE MANAGEMENT OF AN EDGE CONFIGURATION SERVER (ECS)
CN114158061A (zh) * 2020-09-08 2022-03-08 ***通信有限公司研究院 网络切片管理方法、装置及管理功能实体
CN114258020B (zh) * 2020-09-25 2023-12-12 中移物联网有限公司 专有云部署方法、平台及电子设备
CN114554504A (zh) * 2020-11-24 2022-05-27 华为技术有限公司 网络切片规划的方法以及相关设备
CN115037788A (zh) * 2021-03-04 2022-09-09 华为技术有限公司 一种创建网络服务ns的方法及相关装置
CN115277458B (zh) * 2021-04-30 2023-11-17 阿里巴巴新加坡控股有限公司 服务提供方法、设备及存储介质
CN113596874B (zh) * 2021-07-19 2022-05-24 广州爱浦路网络技术有限公司 切片网络功能服务配置方法、计算机装置和存储介质
WO2023131403A1 (en) * 2022-01-05 2023-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Automated service driven virtual network function dimensioning
WO2024043589A1 (ko) * 2022-08-26 2024-02-29 삼성전자 주식회사 무선 통신 시스템에서, 네트워크 슬라이스를 설정하기 위한 방법 및 장치
US11888699B1 (en) * 2022-09-30 2024-01-30 Verizon Patent And Licensing Inc. Method and system for hybrid network slicing

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104253767A (zh) * 2013-06-27 2014-12-31 华为技术有限公司 一种虚拟分片网络的实现方法及一种交换机
CN105791175A (zh) * 2014-12-26 2016-07-20 电信科学技术研究院 软件定义网络中控制传输资源的方法及设备
WO2017080517A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systems and methods for network slice management

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220B (zh) * 2014-03-31 2018-01-16 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN107210957A (zh) * 2015-01-23 2017-09-26 日本电气株式会社 网络功能虚拟化管理和编排方法、设备和程序
EP3252603A4 (en) * 2015-01-28 2018-10-24 Nec Corporation Virtualization management/orchestration apparatus, virtualization management/orchestration method, and program
US9660929B1 (en) * 2015-01-29 2017-05-23 Amdocs Software Systems Limited System, method, and computer program for segregated policy decision making in the context of network function virtualization orchestration in a communication network
CN106105154B (zh) * 2015-02-15 2019-10-22 华为技术有限公司 数据上载的方法、装置及***
RU2683630C2 (ru) * 2015-02-16 2019-03-29 Хуавэй Текнолоджиз Ко., Лтд. Способ обновления дескриптора сетевой службы nsd и устройство
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
CN106533935B (zh) * 2015-09-14 2019-07-12 华为技术有限公司 一种在云计算***中获取业务链信息的方法和装置
CN106685679A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网络服务部署方法和装置
CN106936619B (zh) * 2015-12-31 2020-10-09 华为技术有限公司 部署网络服务的方法和装置
CN108886473B (zh) * 2016-04-08 2020-09-11 华为技术有限公司 一种管理方法及装置
CN112165424B (zh) * 2016-04-29 2021-07-13 华为技术有限公司 一种业务部署方法、装置以及网元
US20170339688A1 (en) 2016-05-17 2017-11-23 Industrial Technology Research Institute Method of network slicing and related apparatuses using the same
CN107689882B (zh) 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
US10742522B2 (en) * 2016-11-14 2020-08-11 Huawei Technologies Co., Ltd. Creation and modification of shareable slice instances
CN107846313B (zh) * 2017-10-30 2019-04-30 中国联合网络通信集团有限公司 一种网络服务模板生成的方法及网络设备
US11671335B2 (en) * 2017-12-06 2023-06-06 Telefonaktiebolaget Lm Ericsson (Publ) First node, second node, and methods performed thereby for managing a network slice instance
EP3729726B1 (en) * 2017-12-20 2023-11-22 Telefonaktiebolaget LM Ericsson (publ) Methods, devices, and systems for managing a federated network slice
US11601819B2 (en) * 2019-07-19 2023-03-07 Intel Corporation Orchestration and configuration of E2E network slices across 3GPP core network and ORAN

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104253767A (zh) * 2013-06-27 2014-12-31 华为技术有限公司 一种虚拟分片网络的实现方法及一种交换机
CN105791175A (zh) * 2014-12-26 2016-07-20 电信科学技术研究院 软件定义网络中控制传输资源的方法及设备
WO2017080517A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systems and methods for network slice management

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3720050A4

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11323336B2 (en) * 2017-09-27 2022-05-03 Huawei Technologies Co., Ltd. Network slice management method and device
CN114788241A (zh) * 2019-12-04 2022-07-22 皇家Kpn公司 提供网络管理与切片管理之间的接口
CN114788241B (zh) * 2019-12-04 2024-05-03 皇家Kpn公司 提供网络管理与切片管理之间的接口
WO2021157934A1 (ko) * 2020-02-07 2021-08-12 삼성전자 주식회사 무선 통신 시스템에서 네트워크 슬라이스를 생성하기 위한 장치 및 방법
WO2021215756A1 (ko) * 2020-04-24 2021-10-28 삼성전자 주식회사 네트워크 슬라이스 자원 할당 및 시각화 방법
US11902109B2 (en) 2020-04-24 2024-02-13 Samsung Electronics Co., Ltd. Method of network slice resource allocation and visualization
WO2021219233A1 (en) * 2020-04-30 2021-11-04 Telefonaktiebolaget Lm Ericsson (Publ) Network management
US11824708B2 (en) 2020-04-30 2023-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Network management
EP4178295A4 (en) * 2020-07-23 2024-01-10 Huawei Tech Co Ltd SERVICE PROCESSING METHOD AND NETWORK DEVICE
CN116436782A (zh) * 2023-06-09 2023-07-14 中国电信股份有限公司四川分公司 一种体现业务意愿的确定性网络传输方法
CN116436782B (zh) * 2023-06-09 2023-09-29 中国电信股份有限公司四川分公司 一种体现业务意愿的确定性网络传输方法

Also Published As

Publication number Publication date
EP3720050A4 (en) 2021-01-20
EP3720050B1 (en) 2022-09-28
US20200313969A1 (en) 2020-10-01
CN112187545B (zh) 2022-04-08
CN110324164B (zh) 2020-10-16
CN110324164A (zh) 2019-10-11
CN112187545A (zh) 2021-01-05
KR102409142B1 (ko) 2022-06-14
EP3720050A1 (en) 2020-10-07
BR112020013497A2 (pt) 2020-12-01
JP7074880B2 (ja) 2022-05-24
KR20200088470A (ko) 2020-07-22
JP2021508997A (ja) 2021-03-11
US11283684B2 (en) 2022-03-22

Similar Documents

Publication Publication Date Title
WO2019184967A1 (zh) 一种网络切片的部署方法及装置
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US20190109768A1 (en) Management of network slices and associated services
EP3291499B1 (en) Method and apparatus for network service capacity expansion
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
EP3723325B1 (en) Network service management method, related device and system
CN111183614B (zh) 5g和非5g管理功能实体间的交互
WO2019174000A1 (zh) 用于业务管理的方法和装置
US20210289435A1 (en) Virtualization management method and apparatus
US11301284B2 (en) Method for managing VNF instantiation and device
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
JP2024501005A (ja) コンテナクラスタのための管理方法および装置
WO2022198524A1 (zh) 服务实例部署方法、节点间的负载均衡方法及***
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv***
WO2019011180A1 (zh) 一种License的发送方法和装置
WO2023155838A1 (zh) 一种虚拟网络功能vnf实例化的方法及装置
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备
WO2023066224A1 (zh) 一种部署容器服务的方法及装置
WO2022141293A1 (zh) 一种弹性伸缩的方法及装置
CN113055211B (zh) 网络服务实例化的方法及网络功能虚拟化编排器
WO2022126389A1 (zh) 建立网络连接的方法及装置
JP2023527929A (ja) 仮想化ネットワーク・サービス配備方法及び装置
CN117201336A (zh) 一种边缘用户服务切片生成方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19774607

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020554359

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20207018552

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019774607

Country of ref document: EP

Effective date: 20200630

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020013497

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020013497

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200701