WO2015149600A1 - Procédé et dispositif de déploiement de service de réseau virtuel - Google Patents

Procédé et dispositif de déploiement de service de réseau virtuel Download PDF

Info

Publication number
WO2015149600A1
WO2015149600A1 PCT/CN2015/073413 CN2015073413W WO2015149600A1 WO 2015149600 A1 WO2015149600 A1 WO 2015149600A1 CN 2015073413 W CN2015073413 W CN 2015073413W WO 2015149600 A1 WO2015149600 A1 WO 2015149600A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf instance
determined
vnf
vnfd
information
Prior art date
Application number
PCT/CN2015/073413
Other languages
English (en)
Chinese (zh)
Inventor
冯爱娟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2015149600A1 publication Critical patent/WO2015149600A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present invention relates to the field of network function virtualization technologies, and in particular, to a virtual network service deployment method and device.
  • the network deployed by network operators is composed of a variety of physical devices. Different network services require different physical devices. Each time a new network service is developed, a new type of physical device needs to be added, but the spatial location of the newly added physical device and the power supply line become more and more as the network service increases. Difficulties, this severely inhibited the deployment of new network services.
  • Network Function Virtualization refers to running network functions on general physical devices.
  • the common form is: deploying virtual machines on physical devices. .
  • the current NFV architecture includes the Operational and Support System/Business Support System (OSS/BSS), the service, the virtualized network function, and the basic device description unit (Service, VNF (Virtual Network Function) and Infrastructure. Description), Network Function Virtualization Management and Orchestration (NFV Management and Orchestration).
  • OSS/BSS Operational and Support System/Business Support System
  • VNF Virtual Network Function
  • Infrastructure Infrastructure. Description
  • NFV Management and Orchestration Network Function Virtualization Management and Orchestration
  • the OSS/BSS interacts with the Orchestrator for the operation and maintenance of the network for the virtualized application.
  • the service, virtualized network function and basic device description unit include an NS information model description template (NSD, NS Descriptor), a VNF information model description template (VNFD, VNF Descriptor), Virtual link description template (VLD, Virtual Link Descriptor), VNF software image, and so on.
  • NSD NS information model description template
  • VNFD VNF information model description template
  • VLD Virtual Link Descriptor
  • VNF software image VNF software image
  • the NSD is planned by the operator or the integrator, and the network information includes a VNFD list, a supported network service (NS, Network Service) capacity, and a VNF instance list and a VLD list corresponding to different NS capacities.
  • NS Network Service
  • the VNFD is provided by a Virtual Network Function (VNF) provider, which includes VNF functions, a list of capacities supported by the VNF, a list of virtual machines required for different capacity, deployment software information of each virtual machine, and outgoing ports. .
  • VNF Virtual Network Function
  • the VLD is used to describe the link requirements of the VNF instance.
  • the two ends of the link are represented by the connection point (CP, Connect Point) of the VNF instance type (for example, VNF_CP identifier).
  • Orchestrator is the NS lifecycle management (for example: deployment/expansion/downline, etc.) and NFVI resource orchestration for at least one data center. It mainly uses NSD to complete network planning for NS and decomposes the requirements of each VNF. The VNFD and VNF capacity requirements are sent to the VNF management system (VNFM, NFV Manager), and the VNFM is deployed by the VNFM.
  • VNFM VNF management system
  • NFM NFV Manager
  • the Orchestrator when receiving the NS instantiation request sent by the OSS, the Orchestrator obtains the NSD corresponding to the NSD index according to the NSD index carried in the NS instantiation request, and obtains a list of VNF instances that need to be instantiated from the obtained NSD; According to the VNF instance in the obtained VNF instance list, the VNFD index that satisfies the VNF instance is selected, and the VNFD corresponding to the VNFD index is used for instantiation operation.
  • the capacity of the different VNF instances deployed in the same NS is the same as the NS capacity in the NSD.
  • the Orchestrator deploys the VNF instantiation, the Orchestrator deploys the capacity of each VNF instance according to the total NS capacity (that is, the capacity of each VNF instance is the same as the total NS capacity), and there is a problem of waste of resources.
  • the embodiment of the present invention provides a virtual network service deployment method and device, which is used to solve the current deployment of each VNF according to the total capacity of the NS when the Orchestrator deploys the VNF instance.
  • the capacity of the instance has a problem of wasted resources.
  • a virtual network service deployment method including:
  • the NSD information includes at least one NS deployment parameter, and each NS deployment The parameter includes at least a capacity of the NS, at least one VNF instance type, a VNF information model description template VNFD information corresponding to each VNF instance type, and a proportional parameter of the VNF instance corresponding to each VNF instance type;
  • the same VNF instance type corresponds to at least one VNF instance, and the VNFD information corresponding to different VNF instances is different.
  • the VNFD information difference includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • VNFD information corresponding to the determined VNF instance is obtained, and the resources required by the determined VNF instance are obtained, including:
  • the resource reservation request includes a capacity of the VNF instance determined by the VNFM according to the determined VNF instance, and the determined VNF instance
  • the corresponding VNFD information determines the resources required by the VNF instance.
  • the VNF information model description template VNFD information corresponding to each VNF instance type includes a VNFD index
  • the resources required by the determined VNF instance including:
  • VNFD For the VNFD, according to the determined capacity of the VNF instance, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources, software resources, and ports corresponding to each VDU.
  • the NSD information further includes common Common information, where the Common information includes a VNFD index, and the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier;
  • the obtained instance resources required by the VNF instance including:
  • VNFD index in the Common information from the acquired NSD information according to the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance;
  • VNFD For the VNFD, according to the determined capacity of the VNF instance, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources, software resources, and ports corresponding to each VDU.
  • determining, from the acquired NSD information, A VNF instance capable of satisfying the capacity requirement of the NS to be instantiated carried in the received NS instantiation request of the network service including:
  • the NS deployment parameter that satisfies the capacity requirement of the NS to be instantiated carried in the received NS instantiation request of the network service is obtained from the obtained NSD information;
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the same VNF instance type.
  • the network service NS instantiation request further carries a VNF instance corresponding to the instantiated VNF instance type.
  • the determining the VNF instance that has not been instantiated includes:
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared.
  • the identifier of the VNF instance and the identifier of the VNF instance corresponding to the type of the VNF instance that has been instantiated in the network service NS instantiation request If the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter is different from the identifier of the VNF instance corresponding to the VNF instance type that is instantiated in the network service NS instantiation request,
  • the VNF instance corresponding to one VNF instance type included in the NS deployment parameter is determined to be a VNF instance that has not been instantiated.
  • VIM virtualized infrastructure management system
  • the VNFM and the VIM are instructed to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual link VL of the determined VNF instance.
  • the NSD information further includes an isolation and an affinity parameter
  • VIM virtualized infrastructure management system
  • the determined VNF instance is established Virtual link VL, including:
  • the virtual link VL establishment information is sent to the VIM, where the VL establishment information includes a virtual link description template VLD index, indicating that the VIM is The VLD index, the VLD information corresponding to the VLD index is obtained, and the VL of the determined VNF instance is established by using the connection point CP corresponding to each VL of the VLD information, where each VL of the VLD information corresponds to The connection point CP contains a CP for connecting the determined VNF instance;
  • a virtual network service deployment device including:
  • An acquiring module configured to acquire, according to the NS information model description template NSD index carried in the received NS instantiation request, the NSD information corresponding to the NSD index, where the NSD information includes at least one NS deployment parameter
  • Each NS deployment parameter includes at least a capacity of the NS, at least one VNF instance type, a VNF information model description template VNFD information corresponding to each VNF instance type, and a proportional parameter of the VNF instance corresponding to each VNF instance type.
  • a capacity determining module configured to determine, from the NSD information acquired by the acquiring module, a VNF instance that can satisfy a capacity requirement of an NS to be instantiated carried in the received NS instantiation request, and according to the determined Calculating a capacity of the determined VNF instance by using a ratio parameter of the VNF instance and a capacity of the NS to be instantiated;
  • a resource determining module configured to obtain, according to the capacity of the VNF instance determined by the capacity determining module and the VNFD information corresponding to the determined VNF instance, the resources required by the determined VNF instance;
  • a deployment module configured to perform virtual network service deployment on the determined VNF instance according to the resource determined by the resource determining module.
  • the same VNF instance type corresponds to at least one VNF instance, and different VNFD information corresponding to different VNF instances are different.
  • the VNFD information difference includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • the resource determining module is specifically used to The capacity of the VNF instance determined by the capacity determining module and the VNFD information corresponding to the determined VNF instance are sent to the VNF management system VNFM;
  • the resource reservation request includes a VNF instance determined by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance. Resources needed.
  • the VNF information model description template VNFD information corresponding to each VNF instance type includes a VNFD index
  • the resource determining module is configured to acquire a VNFD corresponding to the VNFD index according to the VNFD index corresponding to the determined VNF instance;
  • the NSD information further includes common Common information, where the Common information includes a VNFD index, and the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier;
  • the resource determining module is configured to: select, according to the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance, from the NSD information acquired by the acquiring module, select Common information. VNFD index;
  • VNFD For the VNFD, according to the determined capacity of the VNF instance, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources, software resources, and ports corresponding to each VDU.
  • the VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request of the network service includes:
  • the NS deployment parameter that satisfies the capacity requirement of the NS to be instantiated carried in the received NS instantiation request of the network service is obtained from the obtained NSD information;
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the same VNF instance type.
  • the network service NS instantiation request further carries a VNF instance corresponding to the instantiated VNF instance type.
  • the determining the VNF instance that has not been instantiated specifically includes:
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared. Whether the identifier of the VNF instance is the same as the identifier of the VNF instance corresponding to the type of the VNF instance that is to be instantiated in the NS instantiation request, and is the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter.
  • VNF instance determining that the VNF instance corresponding to the VNF instance type included in the NS deployment parameter belongs to an instance that is not yet performed when the identifier of the VNF instance corresponding to the VNF instance type that is instantiated is different from the network service NS instantiation request. VNF instance.
  • the deployment module specifically And the method for sending the received resource reservation request to the virtualized infrastructure management system (VIM), so that the VIM reserves resources required by the determined VNF instance according to the determined resource;
  • VIM virtualized infrastructure management system
  • the VNFM and the VIM are instructed to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual link VL of the determined VNF instance.
  • the NSD information further includes an isolation and an affinity parameter
  • VIM virtualized infrastructure management system
  • the establishing the determining The virtual link VL of the VNF instance including:
  • the virtual link VL establishment information is sent to the VIM, where the VL establishment information includes a virtual link description template VLD index, indicating that the VIM is The VLD index, the VLD information corresponding to the VLD index is obtained, and the VL of the determined VNF instance is established by using the connection point CP corresponding to each VL of the VLD information, where each VL of the VLD information corresponds to The connection point CP includes a CP for connecting the determined VNF instance; receiving the VL instantiation completion information sent by the VIM.
  • the NSD information corresponding to the NSD index is obtained according to the NS information model description template NSD index carried in the received NS instantiation request, where the NSD information includes at least one NS deployment parameter.
  • Each NS deployment parameter includes at least a capacity of the NS, at least one VNF instance type, a VNF information model description template VNFD information corresponding to each VNF instance type, and a proportional parameter of the VNF instance corresponding to each VNF instance type;
  • the capacity of the determined VNF instance is calculated, and the resources required by the determined VNF instance are obtained according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance;
  • FIG. 1 is a schematic flowchart of a virtual network service deployment method according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic flowchart of a virtual network service deployment method according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic structural diagram of an NS instantiated by the solution according to the first embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for deploying a virtual network service according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic structural diagram of a virtual network service deployment device according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of a virtual network service deployment device according to Embodiment 6 of the present invention.
  • An embodiment of the present invention provides a method and a device for deploying a virtual network service, which acquires an NSD index corresponding to the NSD index according to the NS information model description template NSD index carried in the NS instantiation request of the received network service, where
  • the NSD information includes at least one NS deployment parameter, and each NS deployment parameter includes at least NS capacity, at least one VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • VNF instance of the VNF instance corresponding to the type; determining, from the obtained NSD information, a VNF instance that satisfies the capacity requirement of the NS to be instantiated carried in the received network service NS instantiation request, and determining according to the The ratio of the VNF instance and the capacity of the NS to be instantiated, calculating the capacity of the determined VNF instance; obtaining the location according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance Determining a resource required by the determined VNF instance; performing virtual network industry on the determined VNF instance according to the determined resource
  • the deployment of the VNF multi-instance and the capacity of the deployed VNF instance can be automatically adjusted according to the requirements.
  • the capacity of the deployed VNF instance does not match the capacity of the required VNF instance, resulting in wasted resources, effectively saving virtual resources. .
  • the embodiment of the present invention is applied to a network architecture including an OSS operation support system, an Orchestrator management unit, and a Catalog (NFV data warehouse).
  • the VNFD template and the software package are registered in the catalog. Each VNFD template corresponds to a VNFD index.
  • the NSD template and the VLD template are also registered.
  • Each NSD template corresponds to an NSD index
  • each VLD template corresponds to a VLD index.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 1 is a schematic flowchart diagram of a virtual network service deployment method according to Embodiment 1 of the present invention. The method can be as follows.
  • Step 101 Obtain the NSD index corresponding to the NSD index according to the NS information model description template NSD index carried in the received NS instantiation request.
  • the NSD information includes at least one NS deployment parameter.
  • Each NS deployment parameter includes at least NS capacity, at least one VNF instance type, at least one VNF instance corresponding to each VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • the same VNF instance type corresponds to at least one VNF instance, and the VNFD information corresponding to the different VNF instances is different, wherein the VNFD information is different, at least one or more of different Vendor identifiers and different VNFD indexes.
  • Step 102 Determine, from the obtained NSD information, a VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request.
  • step 102 the NS deployment parameter that meets the capacity requirement of the NS to be instantiated carried in the received network service NS instantiation request is searched for from the obtained NSD information.
  • the VNF instance that has not been instantiated is determined, including:
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared. Whether the identifier of the VNF instance is the same as the identifier of the VNF instance corresponding to the type of the VNF instance that is to be instantiated in the NS instantiation request, and is the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter.
  • VNF instance determining that the VNF instance corresponding to the VNF instance type included in the NS deployment parameter belongs to an instance that is not yet performed when the identifier of the VNF instance corresponding to the VNF instance type that is instantiated is different from the network service NS instantiation request. VNF instance.
  • the identifier of the VNF instance may be the number of the VNF instance, or other information, which is not limited herein.
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instances that have not been instantiated belong to the VNF instance corresponding to the same VNF instance type.
  • Step 103 According to the determined proportional parameter of the VNF instance and the NS to be instantiated The capacity of the determined VNF instance is calculated.
  • step 103 a product of the determined VNF instance proportional parameter and the capacity of the NS to be instantiated is used as the capacity of the determined VNF instance.
  • Step 104 Obtain a resource required by the determined VNF instance according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resource includes at least a virtual resource, a software resource, and a port.
  • step 104 according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance, the resources required by the determined VNF instance are obtained, including:
  • the resource reservation request includes a VNF instance determined by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance. Resources needed.
  • VNFD information corresponding to each VNF instance type includes a VNFD index
  • VNFD index corresponding to the determined VNF instance
  • the VNFD obtains a virtual deployment unit VDU list corresponding to the determined VNF instance according to the determined capacity of the VNF instance, and obtains virtual resources, software resources, and ports corresponding to each VDU by using the VDU list.
  • the Common information includes a VNFD index, where the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier, according to the Determining the Vendor identifier corresponding to the VNF instance and the VNF instance type corresponding to the determined VNF instance, selecting the VNFD index in the Common information from the obtained NSD information, and acquiring the VNFD according to the selected VNFD index Indexing a VNFD corresponding to the VNFD, obtaining a virtual deployment unit VDU list corresponding to the determined VNF instance according to the determined capacity of the VNF instance; and using the VDU list to obtain virtual resources and software corresponding to each VDU Resources and ports.
  • VNFD index where the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier, according to the Determining the Vendor identifier corresponding to the VNF instance and the VNF instance type corresponding to the determined VNF instance, selecting the VNFD index in the Common information from
  • Step 105 Perform virtual network service deployment on the determined VNF instance according to the determined resource.
  • performing virtual network service deployment on the determined VNF instance includes resource deployment and virtual link deployment.
  • the received resource reservation request is sent to the virtualized infrastructure management system (VIM), so that the VIM reserves the determined VNF instance according to the determined resource. resource of.
  • VIM virtualized infrastructure management system
  • the NSD information when the resource is deployed, the NSD information further includes an isolation and an affinity parameter, and the isolation and affinity parameters corresponding to the determined VNF instance are obtained from the obtained NSD information; Carrying the isolation and affinity parameters in the resource reservation request to the virtualization infrastructure management system VIM, so that the VIM is allocated according to the determined resource and the isolation and affinity parameters. Different levels of resources are given to the determined VNF instance.
  • the VNFM and the VIM are instructed to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual link VL of the determined VNF instance.
  • the virtual link VL establishment information is sent to the VIM, and the VL instantiation completion information sent by the VIM is received.
  • the VL establishment information includes a virtual link description template VLD index, and the VIM is configured to acquire VLD information corresponding to the VLD index according to the VLD index, and use each VL corresponding to the VLD information.
  • the connection point CP establishes a VL of the determined VNF instance, wherein the connection point CP corresponding to each VL of the VLD information includes a CP for connecting the determined VNF instance.
  • the VNF multi-instance deployment and the capacity of the deployed VNF instance can be automatically adjusted according to requirements, and the problem that the capacity of the deployed VNF instance does not match the capacity of the required VNF instance causes waste of resources. Effectively save virtual resources.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 2 is a schematic flowchart diagram of a virtual network service deployment method according to Embodiment 2 of the present invention. The method can be as follows.
  • Step 201 The Orchestrator obtains the NSD index corresponding to the NSD index according to the NS information model description template NSD index carried in the received NS instantiation request.
  • the NSD information includes at least one NS deployment parameter.
  • Each VNF deployment parameter includes at least NS capacity, at least one VNF instance type, at least one VNF instance corresponding to each VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • step 201 when the operator purchases the VNF from the equipment vendor, the equipment provider needs to provide the VNFD template and the VNF software package that the Orchestrator can correctly interpret, and the operator registers the VNFD template and the VNF software package through the open interface of the OSS or the Orchestrator. Go to the Catalog and get the VNFD index for each VNFD template.
  • the system integrator or the operator When the operator plans the network, the system integrator or the operator completes the network planning according to the business needs, and completes the NSD template and VLD template construction according to the format supported by the Orchestrator, and opens the constructed NSD template and VLD template through OSS or Orchestrator.
  • the interface is registered in the Catalog, and the NSD index corresponding to each NSD template and the VLD index corresponding to each VLD template are obtained.
  • the NS needs to be instantiated, including but not limited to:
  • the OSS initiates an NS instantiation request to the Orchestrator.
  • the instantiation request carries the capacity of the NS and the NSD (NS Descriptor, NS Descriptor) index.
  • the Orchestrator obtains the NSD template corresponding to the NSD index from the catalog according to the NSD index carried in the NS instantiation request.
  • the NSD template includes at least one NS deployment parameter.
  • Each NS deployment parameter includes at least NS capacity, at least one VNF instance type, at least one VNF instance corresponding to each VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • the VNFD information corresponding to each VNF instance type may be a VNFD index, or may be a Vendor (operator) identifier and a VNFD index, which are not limited herein.
  • the same VNF instance type corresponds to at least one VNF instance.
  • the VNFD information corresponding to different VNF instances may be the same or different.
  • the VNFD information corresponding to different VNF instances includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • Vendor logos means that the carrier identifiers are different.
  • the solution of the embodiment of the present invention can implement different Vendor products of different VNF instances corresponding to the same VNF instance type, and ensure the compatibility of each carrier product.
  • At least two NS deployment parameters included in an NSD template as shown in Table 1 (where the VNFD information corresponding to the VNF instance type includes a VNFD index):
  • the VNF instance type and the VNFD index corresponding to the VNF instance type and the scale parameter of the VNF instance can be determined.
  • the VNF instance corresponding to the same VNF instance type may be one or more.
  • the VNF instance corresponding to the same VNF instance type is multiple VNF instances, multiple VNF instances corresponding to the same VNF instance type are used.
  • the VNFD index corresponding to the different VNF instances may be the same or different.
  • the VNF corresponding to the same VNFD index may be distinguished by the instance number.
  • the 2*VNF C instance corresponds to two VNF instances
  • the VNDF index corresponding to the two VNF instances is VNFD 4.
  • the two VNF instances corresponding to the 2*VNF C instance can be distinguished by No_4 and No_5.
  • At least two NS deployment parameters included in an NSD template as shown in Table 2 (wherein the VNFD information corresponding to the VNF instance type includes the Vendor identifier and the VNFD index in the common Common information in the NSD):
  • the VNF instance type, and the Vendor identifier corresponding to the VNF instance type and the scale parameter of the VNF instance can be determined.
  • the VNF instance corresponding to the same VNF instance type may be one or more.
  • the Vendor identifiers of different VNF instances may be the same or different.
  • the VNFs corresponding to the same VNFD index can be distinguished by instance numbers.
  • the 2*VNF C instance corresponds to two VNF instances
  • the Vendor identifier corresponding to each VNF instance is Vendor D.
  • two VNF instances corresponding to the 2*VNF C instance can be distinguished by No_4 and No_5.
  • Step 202 The Orchestrator determines, from the obtained NSD information, a VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request.
  • step 202 it is assumed that the capacity of the NS to be instantiated in the received NS instantiation request is 500 Kcaps, and the NSD information obtained in step 101 is the same as the capacity of the NS to be instantiated 500Kcaps.
  • NS deployment parameter that is, NS deployment parameter 1.
  • At least the instantiation that needs to be established in the NS deployment parameter 1 includes a 1*VNF A instance, a 2*VNF B instance, and a 2*VNF C instance.
  • the NS deployment parameter that meets the capacity requirement of the NS to be instantiated carried in the received NS instantiation request is searched for from the obtained NSD information.
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the same VNF instance type.
  • the network service NS instantiation request carries the VNF instance class that has been instantiated
  • the identifier of the VNF instance corresponding to the type, and the VNF instance that has not been instantiated is determined, including:
  • Each VNF instance type included in the found NS deployment parameter is compared with the VNF instance type that is instantiated in the network service NS instantiation request.
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared. Whether the identifier of the VNF instance is the same as the identifier of the VNF instance corresponding to the type of the VNF instance that is to be instantiated in the NS instantiation request, and is the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter.
  • VNF instance determining that the VNF instance corresponding to the VNF instance type included in the NS deployment parameter belongs to an instance that is not yet performed when the identifier of the VNF instance corresponding to the VNF instance type that is instantiated is different from the network service NS instantiation request. VNF instance.
  • Step 203 The Orchestrator calculates the capacity of the determined VNF instance according to the determined proportional parameter of the VNF instance and the capacity of the NS to be instantiated.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • step 203 assuming that the capacity of the VNF instance of NO_1 corresponding to the 1*VNF A instance is calculated, the proportion of the VNF instance corresponding to the NO_1 corresponding to the 1*VNF A instance in the VNF deployment parameter 1 is found in the NSD template obtained in step 202.
  • the parameter is 100%, and according to the capacity of the NS to be instantiated, 500Kcaps, the capacity of the VNF instance of NO_1 corresponding to the 1*VNF A instance is calculated to be 500Kcaps.
  • the capacity of the VNF instance of NO_2 corresponding to the 2*VNF B instance is calculated, then from step 202 In the obtained NSD template, the ratio of the VNF instance of the NO 2 corresponding to the 2*VNF B instance in the VNF deployment parameter 1 is 50%, and then the 2*VNF A instance corresponding to the NS capacity to be instantiated is calculated.
  • the capacity of the VNF instance of NO_2 is 250Kcaps.
  • the calculated capacity of the VNF instance corresponding to each VNF instance type may be the same as or different from the NS capacity, and the system resources are saved compared with the current capacity of the NS capacity as the VNF instance.
  • Step 204 The Orchestrator obtains the resources required by the determined VNF instance according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resource includes at least a virtual resource, a software resource, and a port.
  • step 204 the Orchestrator sends the determined VNF instance capacity and the VNFD information corresponding to the determined VNF instance to the VNFM, and the VNFM determines the capacity of the VNF instance according to the determined VNF instance and the determined VNF instance. Corresponding VNFD information, the resources required by the determined VNF instance are obtained.
  • the Orchestrator receives the resource reservation request sent by the VNFM.
  • the resource reservation request includes resources required by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resources required by the determined VNF instance are obtained according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance, including:
  • VNFD information corresponding to each VNF instance type includes a VNFD index
  • the VNFD corresponding to the VNFD index is obtained according to the VNFD index corresponding to the determined VNF instance; and the VNFD is determined according to the determined VNF instance.
  • VDU virtual deployment unit
  • the VNFM obtains the VNFD corresponding to the VNFD index from the catalog according to the VNFD index.
  • the VNFD index of the NO_1 corresponding to the 1*VNF A instance is VNFD1
  • the VNFD corresponding to the VNFD1 is obtained according to the VNFD1
  • the VDU list corresponding to the determined VNF instance is obtained from the obtained VNFD according to the determined capacity of the VNF instance.
  • the VNFD index of the NO_2 corresponding to the 2*VNF B instance is VNFD2, and obtaining the VNFD corresponding to the VNFD2 according to the VNFD2, and determining from the acquired VNFD
  • the capacity of the VNF instance is obtained, and the VDU list corresponding to the determined VNF instance is obtained, and the VDU list is used to obtain the software resources and ports corresponding to each VDU;
  • VNFD corresponding to VNFD1 is different from the VNFD corresponding to VNFD2.
  • the NSD information further includes public Common information, where the Common information includes a VNFD index.
  • the VNFD information corresponding to each VNF instance type includes a Vendor identifier, according to the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance, from the obtained NSD information, And selecting, in the common information, a VNFD index that meets the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance; and acquiring, according to the selected VNFD index, a VNFD corresponding to the VNFD index;
  • the VNFD is configured to obtain a VDU list corresponding to the determined VNF instance according to the determined capacity of the VNF instance, and obtain the virtual resource, the software resource, and the port corresponding to each VDU by using the VDU list.
  • the Vendor identifier of NO_1 corresponding to the 1*VNF A instance is Vendor A; the Vendor identifier of NO_2 corresponding to the 2*VNF B instance is Vendor B; the Vendor identifier of NO_3 corresponding to the 2*VNF B instance is Vendor C; and so on.
  • VNFD1 that satisfies VendorA and VNF A from the Common information
  • VNFD corresponding to VNFD1 the VNFD1
  • the VNFD obtains a VDU list corresponding to the determined VNF instance according to the determined capacity of the VNF instance, and obtains a virtual resource, a software resource, and a port corresponding to each VDU by using the VDU list.
  • the virtual resource includes a virtual machine, a virtual link, a virtual memory, and the like;
  • the software resource includes a software image, and the like;
  • the port includes an external port, a port on the virtual machine, and the like.
  • the VNFD index obtained corresponds to the list information of the VNFD:
  • the virtual deployment unit VDU list includes 1*VDU_1 instance, 1*VDU_2 instance, and 1*VDU_3.
  • the software resources corresponding to the 1*VDU_1 instance include the software image xx.image, the storage resource requirement X1, the computing resource requirement Y1, the memory resource requirement Z1, and the like; the ports CP1 and CP2.
  • VNFM will read out the resources required for each VNF instance that needs to be instantiated.
  • Step 205 The Orchestrator performs virtual network service deployment on the determined VNF instance according to the determined resource.
  • step 205 the virtual network service deployment is performed on the determined VNF instance according to the determined resource, including:
  • the first step the Orchestrator sends the received resource reservation request sent by the VNFM to the virtual infrastructure management system (VIM), so that the VIM reserves the determination according to the determined resource.
  • VIM virtual infrastructure management system
  • the resource reservation request includes isolation and affinity parameters.
  • the NSD information includes isolation and affinity parameters.
  • the Orchestrator And obtaining, by the Orchestrator, the isolation and affinity parameters corresponding to the determined VNF instance, and carrying the isolation and affinity parameters in the resource reservation request to the VIM, so that the The VIM allocates resources of different levels to the determined VNF instance according to the determined instance resource and the isolation and affinity parameter.
  • the different levels of resources include at least a data center (Date Center), a site (Site), a host (Host), and the like.
  • the isolation and affinity parameters included in the NSD information are used to represent the geographical location deployment relationship between at least two VNF instances.
  • the second step when the resource reservation is successful, the Orchestrator instructs the VNFM and the VIM to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish the virtuality of the determined VNF instance.
  • Link VL, Virtual Link
  • the VIM sends VL setup information.
  • the VL establishment information includes a virtual link description (VLD) index, and the VIM information is obtained by the VIM according to the VLD index, and the VLD information is used by the VLD information.
  • VLD virtual link description
  • the connection point CP corresponding to each VL in each of them establishes the VL of the determined VNF instance.
  • connection point CP corresponding to each VL of the VLD information includes a CP for connecting the determined VNF instance.
  • the VLD information list corresponding to the VLD index is obtained according to the VLD index:
  • the established VL link illustrates the VL link between different VNF instances deployed.
  • Step 3 The Orchestrator receives the VL instantiation completion information sent by the VIM.
  • the Orchestrator sends instantiation completion information to the OSS.
  • FIG. 3 it is a schematic structural diagram of an NS instantiated by the solution described in Embodiments 1 to 2 of the present invention.
  • the VNF multi-instance deployment and the capacity of the deployed VNF instance can be automatically adjusted according to requirements, and the problem that the capacity of the deployed VNF instance does not match the capacity of the required VNF instance causes waste of resources. Effectively save virtual resources.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 4 is a schematic flowchart of a method for deploying a virtual network service according to Embodiment 3 of the present invention.
  • each VNF instance type included in the NS deployment parameter corresponds to
  • the VNFD information includes a VNFD index as an example, and the method can be as follows.
  • Step 301 The Orchestrator obtains the NSD index corresponding to the NSD index according to the NS information model description template NSD index carried in the received NS instantiation request.
  • the NSD information includes at least one NS deployment parameter.
  • Each VNF deployment parameter includes at least NS capacity, at least one VNF instance type, at least one VNF instance corresponding to each VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • step 301 the Orchestrator receives the network service NS instantiation request sent by the OSS.
  • At least two NS deployment parameters included in an NSD template as shown in Table 5 (where the VNFD information corresponding to the VNF instance type includes a VNFD index):
  • the VNF instance type and the VNFD index corresponding to the VNF instance type and the scale parameter of the VNF instance can be determined.
  • the VNF instance corresponding to the same VNF instance type may be one or more.
  • the VNF instance corresponding to the same VNF instance type is multiple VNF instances, multiple VNF instances corresponding to the same VNF instance type are used.
  • the VNFD index corresponding to the different VNF instances may be the same or different.
  • the VNF corresponding to the same VNFD index may be distinguished by the instance number.
  • the 2*VNF C instance corresponds to two VNF instances
  • the VNDF index corresponding to the two VNF instances is VNFD 4.
  • the two VNF instances corresponding to the 2*VNF C instance can be distinguished by No_4 and No_5.
  • Step 302 The Orchestrator determines, from the obtained NSD information, a VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request.
  • step 302 in the third embodiment of the present invention is the same as the embodiment of step 302 in the second embodiment of the present invention, and details are not described herein.
  • Step 303 The Orchestrator calculates the capacity of the determined VNF instance according to the determined proportional parameter of the VNF instance and the capacity of the NS to be instantiated.
  • the embodiment of the method in the third embodiment of the present invention is the same as the embodiment of the step 203 in the second embodiment of the present invention, and details are not described herein.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • Step 304 The Orchestrator obtains the resources required by the determined VNF instance according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resource includes at least a virtual resource, a software resource, and a port.
  • step 304 the Orchestrator sends the determined VNF instance capacity and the VNFD information corresponding to the determined VNF instance to the VNFM, and the VNFM determines the capacity of the VNF instance according to the determined VNF instance and the determined VNF instance. Corresponding VNFD information, the resources required by the determined VNF instance are obtained.
  • the Orchestrator receives the resource reservation request sent by the VNFM.
  • the resource reservation request includes resources required by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resources required by the determined VNF instance are obtained according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance, including:
  • the VDU list obtains software resources and ports corresponding to each VDU.
  • the VNFM obtains the VNFD corresponding to the VNFD index from the catalog according to the VNFD index.
  • the VNFD index of the NO_1 corresponding to the 1*VNF A instance is VNFD1
  • the VNFD corresponding to the VNFD1 is obtained according to the VNFD1
  • the VDU list corresponding to the determined VNF instance is obtained from the obtained VNFD according to the determined capacity of the VNF instance.
  • the VNFD index of the NO_2 corresponding to the 2*VNF B instance is VNFD2, and obtaining the VNFD corresponding to the VNFD2 according to the VNFD2, and determining from the acquired VNFD
  • the capacity of the VNF instance is obtained, and the VDU list corresponding to the determined VNF instance is obtained, and the VDU list is used to obtain the software resources and ports corresponding to each VDU;
  • VNFD corresponding to VNFD1 is different from the VNFD corresponding to VNFD2.
  • the VNFM will read out the resources required for each VNF instance that needs to be instantiated.
  • Step 305 The Orchestrator sends the resource reservation request sent by the received VNFM to the VIM, so that the VIM reserves the resources required by the determined VNF instance according to the determined resource.
  • the resource reservation request includes isolation and affinity parameters.
  • the NSD information includes isolation and affinity parameters.
  • the Orchestrator And obtaining, by the Orchestrator, the isolation and affinity parameters corresponding to the determined VNF instance, and carrying the isolation and affinity parameters in the resource reservation request to the VIM, so that the The VIM allocates resources of different levels to the determined VNF instance according to the determined instance resource and the isolation and affinity parameter.
  • the different levels of resources include at least a data center (Date Center), a site (Site), a host (Host), and the like.
  • the isolation and affinity parameters included in the NSD information are used to represent the geographical location deployment relationship between at least two VNF instances.
  • Step 306 When the resource reservation is successful, the Orchestrator instructs the VNFM and the VIM to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual chain of the determined VNF instance.
  • Road VL, Virtual Link
  • step 306 after determining the virtual machine required to allocate the determined VNF instance, the VL setup information is sent to the VIM.
  • the VL establishment information includes a virtual link description (VLD) index, and the VIM information is obtained by the VIM according to the VLD index, and the VLD information is used by the VLD information.
  • VLD virtual link description
  • the connection point CP corresponding to each VL in each of them establishes the VL of the determined VNF instance.
  • connection point CP corresponding to each VL of the VLD information includes a CP for connecting the determined VNF instance.
  • Step 307 The Orchestrator receives the VL instantiation completion information sent by the VIM.
  • the Orchestrator sends instantiation completion information to the OSS.
  • the instance type can implement the use of different carrier products, and the VNF multi-instance deployment and the capacity of the deployed VNF instance can be automatically adjusted according to requirements, and the capacity of the deployed VNF instance does not match the capacity of the required VNF instance, resulting in waste of resources.
  • the problem is that virtual resources are effectively saved, and virtual links are also established between deployed VNF instances.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • a flowchart of a method for deploying a virtual network service according to Embodiment 4 of the present invention is described in the fourth embodiment of the present invention, where the VNFD information corresponding to each VNF instance type included in the NS deployment parameter includes a Vender identifier as an example.
  • the method can be as follows.
  • the first step the Orchestrator obtains the NSD index corresponding to the NSD index according to the NS information model of the received NS information request.
  • the NSD information includes at least one NS deployment parameter.
  • Each VNF deployment parameter includes at least NS capacity, at least one VNF instance type, at least one VNF instance corresponding to each VNF instance type, VNF information model description template VNFD information corresponding to each VNF instance type, and each VNF instance.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • the VNFD information corresponding to each VNF instance type may be a Vendor identifier and a VNFD index, which are not limited herein.
  • the same VNF instance type corresponds to at least one VNF instance.
  • the VNFD information corresponding to different VNF instances may be the same or different.
  • the VNFD information corresponding to different VNF instances includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • the solution of the embodiment of the present invention can implement different Vendor products of different VNF instances corresponding to the same VNF instance type, and ensure the compatibility of each carrier product.
  • At least two NS deployment parameters included in an NSD template as shown in Table 6 (where The VNFD information corresponding to the VNF instance type includes the Vendor identifier and the VNFD index in the common Common information in the NSD):
  • the VNF instance type and the Vendor identifier corresponding to the VNF instance type and the scale parameter of the VNF instance can be determined.
  • the VNF instance corresponding to the same VNF instance type may be one or more.
  • the Vendor identifiers of different VNF instances may be the same or different.
  • the VNFs corresponding to the same VNFD index can be distinguished by instance numbers.
  • the 2*VNF C instance corresponds to two VNF instances
  • the Vendor identifier corresponding to each VNF instance is Vendor D.
  • two VNF instances corresponding to the 2*VNF C instance can be distinguished by No_4 and No_5.
  • Step 2 The Orchestrator determines, from the obtained NSD information, a VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request.
  • the embodiment of the second step in the fourth embodiment of the present invention is the same as the embodiment of the step 202 in the second embodiment of the present invention, and details are not described herein.
  • the third step the Orchestrator calculates the capacity of the determined VNF instance according to the determined proportional parameter of the VNF instance and the capacity of the NS to be instantiated.
  • the ratio parameter is used to represent the ratio of the capacity of the VNF instance to the NS capacity, and may be a number, a percentage, or a text description, and is not limited herein.
  • the embodiment of the third step in the fourth embodiment of the present invention is the same as the embodiment of step 203 in the second embodiment of the present invention, and details are not described herein.
  • the fourth step the Orchestrator obtains the resources required by the determined VNF instance according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resource includes at least a virtual resource, a software resource, and a port.
  • the Orchestrator sends the determined VNF instance capacity and the VNFD information corresponding to the determined VNF instance to the VNFM, and the VNFM determines the VNF based on the capacity of the VNF instance and the determined VNF.
  • the VNFD information corresponding to the instance obtains the resources required by the determined VNF instance.
  • the Orchestrator receives the resource reservation request sent by the VNFM.
  • the resource reservation request includes resources required by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance.
  • the resources required by the determined VNF instance are obtained according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance, including:
  • the common information is also included in the NSD information.
  • the Common Information includes a VNFD index.
  • the VNF instance corresponding to the determined VNF instance And obtaining, according to the selected VNFD index, a VNFD corresponding to the VNFD index, and obtaining, according to the determined capacity of the VNF instance, a VDU list corresponding to the determined VNF instance, and using the VNFD index;
  • the VDU list obtains virtual resources, software resources, and ports corresponding to each VDU.
  • the Vendor identifier of NO_1 corresponding to the 1*VNF A instance is Vendor A; the Vendor identifier of NO_2 corresponding to the 2*VNF B instance is Vendor B; the Vendor identifier of NO_3 corresponding to the 2*VNF B instance is Vendor C; and so on.
  • VNFD1 that satisfies VendorA and VNF A from the Common information
  • VNFD corresponding to VNFD1 the VNFD1
  • the VNFD obtains a VDU list corresponding to the determined VNF instance according to the determined capacity of the VNF instance, and obtains a virtual resource, a software resource, and a port corresponding to each VDU by using the VDU list.
  • the VNFM will read out the resources required for each VNF instance that needs to be instantiated.
  • Step 5 The Orchestrator performs virtual network service deployment on the determined VNF instance according to the determined resource.
  • the virtual network service deployment is performed on the determined VNF instance according to the determined resource, including:
  • the Orchestrator sends the received resource reservation request sent by the VNFM to the virtual infrastructure management system (VIM), so that the VIM reserves the determined according to the determined resource.
  • VIM virtual infrastructure management system
  • the resource reservation request includes isolation and affinity parameters.
  • the NSD information includes isolation and affinity parameters.
  • the Orchestrator And obtaining, by the Orchestrator, the isolation and affinity parameters corresponding to the determined VNF instance, and carrying the isolation and affinity parameters in the resource reservation request to the VIM, so that the Said VIM according to said determined instance resource and said isolation and pro And the degree parameter, allocating resources of different levels to the determined VNF instance.
  • the different levels of resources include at least a data center (Date Center), a site (Site), a host (Host), and the like.
  • the isolation and affinity parameters included in the NSD information are used to represent the geographical location deployment relationship between at least two VNF instances.
  • the Orchestrator instructs the VNFM and the VIM to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual chain of the determined VNF instance.
  • Road VL, Virtual Link
  • the VL setup information is sent to the VIM.
  • the VL establishment information includes a virtual link description (VLD) index, and the VIM information is obtained by the VIM according to the VLD index, and the VLD information is used by the VLD information.
  • VLD virtual link description
  • the connection point CP corresponding to each VL in each of them establishes the VL of the determined VNF instance.
  • connection point CP corresponding to each VL of the VLD information includes a CP for connecting the determined VNF instance.
  • the established VL link illustrates the VL link between different VNF instances deployed.
  • the Orchestrator receives the VL instantiation completion information sent by the VIM.
  • the Orchestrator sends instantiation completion information to the OSS.
  • the VNF multi-instance deployment not only the same VNF instance type can be used to implement different carrier products, but also the VNF multi-instance deployment and the deployed VNF instance capacity can be automatically adjusted according to requirements.
  • the capacity mismatch of the required VNF instance causes a waste of resources, effectively saving virtual resources, and establishing a virtual link between deployed VNF instances.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 5 it is a schematic structural diagram of a virtual network service deployment device according to Embodiment 5 of the present invention.
  • the deployment device includes the functions of performing the first embodiment of the present invention to the fourth embodiment of the present invention, where the deployment device includes: The acquisition module 11, the capacity determination module 12, the resource determination module 13 and the deployment module 14, wherein:
  • the obtaining module 11 is configured to obtain the NSD index corresponding to the NSD index according to the NS information model description template NSD index carried in the received network service NS instantiation request, where the NSD information includes at least one NS deployment
  • the parameter, each NS deployment parameter includes at least a capacity of the NS, at least one VNF instance type, a VNF information model description template VNFD information corresponding to each VNF instance type, and a proportional parameter of the VNF instance corresponding to each VNF instance type;
  • the capacity determining module 12 is configured to determine, from the NSD information acquired by the acquiring module 11, a VNF instance that can satisfy the capacity requirement of the NS to be instantiated carried in the received NS instantiation request, and according to the Calculating a ratio of the VNF instance and a capacity of the NS to be instantiated, and calculating a capacity of the determined VNF instance;
  • the resource determining module 13 is configured to obtain, according to the capacity of the VNF instance determined by the capacity determining module 12 and the VNFD information corresponding to the determined VNF instance, the resource required by the determined VNF instance, where the resource includes at least Virtual resources, software resources and ports;
  • the deployment module 14 is configured to perform virtual network service deployment on the determined VNF instance according to the resource determined by the resource determining module 13.
  • the same VNF instance type corresponds to at least one VNF instance, and the VNFD information corresponding to different VNF instances is different.
  • the VNFD information difference includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • the resource determining module 13 is specifically configured to send the capacity of the VNF instance determined by the capacity determining module 12 and the VNFD information corresponding to the determined VNF instance to the VNF management system VNFM;
  • the resource reservation request includes a VNF instance determined by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance. Resources needed.
  • the VNF information model description template VNFD information corresponding to each VNF instance type includes a VNFD index
  • the resource determining module 13 is configured to acquire, according to the determined VNFD index corresponding to the VNF instance, the VNFD corresponding to the VNFD index;
  • VNFD For the VNFD, according to the capacity of the VNF instance determined by the capacity determining module 12, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources and software resources corresponding to each VDU. And port.
  • the NSF information further includes public Common information, where the Common information includes a VNFD index, and the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier;
  • the resource determining module 13 is configured to select a VNFD index in the Common information from the acquired NSD information according to the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance. ;
  • VNFD For the VNFD, according to the determined capacity of the VNF instance, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources, software resources, and ports corresponding to each VDU.
  • the VNF instance that is used to obtain the capacity requirement of the NS to be instantiated, which is carried in the network service NS instantiation request, is determined by the method, and includes:
  • the NS deployment parameter that meets the capacity requirement of the NS to be instantiated carried in the received network service NS instantiation request is searched out from the NSD information obtained by the obtaining module 11;
  • the VNF instance that has not been instantiated is determined by the VNF instance that has not been instantiated, and the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instances that have not been instantiated belong to the VNF instance corresponding to the same VNF instance type.
  • the network service NS instantiation request carries an identifier of a VNF instance corresponding to the VNF instance type that has been instantiated;
  • the determining the VNF instance that has not been instantiated specifically includes:
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared. Whether the identifier of the VNF instance is the same as the identifier of the VNF instance corresponding to the type of the VNF instance that is to be instantiated in the NS instantiation request, and is the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter.
  • VNF instance determining that the VNF instance corresponding to the VNF instance type included in the NS deployment parameter belongs to an instance that is not yet performed when the identifier of the VNF instance corresponding to the VNF instance type that is instantiated is different from the network service NS instantiation request. VNF instance.
  • the deployment module 14 is configured to send the received resource reservation request to the virtualized infrastructure management system (VIM), so that the VIM reserves the foregoing according to the determined resource.
  • VIM virtualized infrastructure management system
  • the VNFM and the VIM are instructed to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual link VL of the determined VNF instance.
  • the NSD information further includes isolation and affinity parameters
  • VIM virtualized infrastructure management system
  • the establishing the virtual link VL of the determined VNF instance includes:
  • the virtual link VL establishment information is sent to the VIM, where the VL establishment information includes a virtual link description template VLD index, indicating that the VIM is The VLD index, the VLD information corresponding to the VLD index is obtained, and the VL of the determined VNF instance is established by using the connection point CP corresponding to each VL of the VLD information, where each VL of the VLD information corresponds to The connection point CP includes a CP for connecting the determined VNF instance; receiving the VL instantiation completion information sent by the VIM.
  • the device according to the fifth embodiment of the present invention may be implemented by using a hardware, or may be implemented by using a software, or may be a combination of the Orchestrator and the VNFM, which is not limited herein.
  • VNF multi-instance deployment not only can the same VNF instance type be used with different carrier products, but also the VNF multi-instance deployment and the deployed VNF instance capacity can be automatically adjusted according to the needs, without the same capacity as the NS, effectively Virtual resources are saved while virtual links are established between deployed VNF instances.
  • FIG. 6 is a schematic structural diagram of a virtual network service deployment device according to Embodiment 6 of the present invention.
  • the deployment device has the functions of performing the first embodiment of the present invention to the fourth embodiment of the present invention.
  • the deployment device may adopt a general computer system structure, and the computer system may be a processor-based computer.
  • the deployment processing entity includes at least one processor 21, a communication bus 22, a memory 23, and at least one communication interface 24.
  • the processor 21 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 invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 22 can include a path for transferring information between the components.
  • the communication interface 24 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the computer system includes one or more memories 23, which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or Other types of dynamic storage devices that can store information and instructions, or can be electrically erasable programmable read-only memory (EEPROM), CD-ROM (Compact Disc Read-Only Memory, CD-ROM) ) or other disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or capable of carrying or storing in the form of instructions or data structures.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 23 is used to store application code for executing the solution of the present invention, and the application code for executing the solution of the present invention is stored in a memory and controlled by the processor 21.
  • the processor 21 is configured to execute an application stored in the memory 23.
  • the NSD information includes at least one NS deployment parameter, and each NS deployment The parameter includes at least a capacity of the NS, at least one VNF instance type, a VNF information model description template VNFD information corresponding to each VNF instance type, and a proportional parameter of the VNF instance corresponding to each VNF instance type;
  • the same VNF instance type corresponds to at least one VNF instance, and the VNFD information corresponding to different VNF instances is different.
  • the VNFD information difference includes at least one or more of different Vendor identifiers and different VNFD indexes.
  • the processor 21 is specifically configured to perform:
  • the resource reservation request includes a VNF instance determined by the VNFM according to the determined capacity of the VNF instance and the VNFD information corresponding to the determined VNF instance. Resources needed.
  • the VNF information model description template VNFD information corresponding to each VNF instance type includes a VNFD index
  • the processor 21 is specifically configured to perform:
  • VNFD For the VNFD, according to the capacity of the VNF instance determined by the capacity determining module 12, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources and software resources corresponding to each VDU. And port.
  • the NSF information further includes public Common information, where the Common information includes a VNFD index, and the VNF information model description template VNFD corresponding to each VNF instance type includes a Vendor identifier;
  • the processor 21 is specifically configured to perform:
  • VNFD index in the Common information from the acquired NSD information according to the Vendor identifier corresponding to the determined VNF instance and the VNF instance type corresponding to the determined VNF instance;
  • VNFD For the VNFD, according to the determined capacity of the VNF instance, obtain a virtual deployment unit VDU list corresponding to the determined VNF instance; and use the VDU list to obtain virtual resources, software resources, and ports corresponding to each VDU.
  • the processor 21 is specifically configured to perform:
  • the NS deployment parameter that satisfies the capacity requirement of the NS to be instantiated carried in the received NS instantiation request of the network service is obtained from the obtained NSD information;
  • the VNF instance that has not been instantiated is determined by the VNF instance that has not been instantiated, and the VNF instance that has not been instantiated belongs to the VNF instance corresponding to the different VNF instance type.
  • the VNF instances that have not been instantiated belong to the VNF instance corresponding to the same VNF instance type.
  • the network service NS instantiation request carries an identifier of a VNF instance corresponding to the VNF instance type that has been instantiated;
  • the processor 21 is specifically configured to perform:
  • Each VNF instance type included in the found NS deployment parameter and the network service The NS instantiation request carries the VNF instance type that has been instantiated for comparison;
  • the comparison result is that the VNF instance type included in the NS deployment parameter is different from the VNF instance type that is instantiated in the network service NS instantiation request, it is determined that the VNF instance type included in the NS deployment parameter corresponds to The VNF instance belongs to a VNF instance that has not been instantiated;
  • the VNF instance type included in the NS deployment parameter is the same as the type of the VNF instance that is included in the NS deployment request
  • the VNF instance type included in the NS deployment parameter is further compared. Whether the identifier of the VNF instance is the same as the identifier of the VNF instance corresponding to the type of the VNF instance that is to be instantiated in the NS instantiation request, and is the identifier of the VNF instance corresponding to the VNF instance type included in the NS deployment parameter.
  • VNF instance determining that the VNF instance corresponding to the VNF instance type included in the NS deployment parameter belongs to an instance that is not yet performed when the identifier of the VNF instance corresponding to the VNF instance type that is instantiated is different from the network service NS instantiation request. VNF instance.
  • the processor 21 is specifically configured to perform:
  • VIM virtualized infrastructure management system
  • the VNFM and the VIM are instructed to allocate the virtual machine required by the determined VNF instance according to the reserved resource, and establish a virtual link VL of the determined VNF instance.
  • the NSD information further includes isolation and affinity parameters
  • the processor 21 is specifically configured to perform:
  • the processor 21 is specifically configured to perform:
  • the virtual link VL establishment information is sent to the VIM, where the VL establishment information includes a virtual link description template VLD index, indicating that the VIM is The VLD index, the VLD information corresponding to the VLD index is obtained, and the VL of the determined VNF instance is established by using the connection point CP corresponding to each VL of the VLD information, where each VL of the VLD information corresponds to The connection point CP includes a CP for connecting the determined VNF instance; receiving the VL instantiation completion information sent by the VIM.
  • the deployment device provided in this embodiment can solve the problem of waste of resources when the existing operator deploys the virtual network service.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • 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 device is implemented in a flow or a flow chart The functions specified in a block or blocks of a flow and/or block diagram.
  • 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un dispositif de déploiement de service de réseau virtuel. Le procédé consiste à : conformément à un index de NSD véhiculé dans une demande d'instanciation de service de réseau (NS) reçue, acquérir des informations de NSD correspondant à l'index de NSD ; déterminer une instance de VNF satisfaisant à des exigences de capacité d'un NS à faire l'objet d'une instanciation, véhiculée dans la demande d'instanciation de service de réseau (NS) reçue, à partir des informations de NSD acquises ; et, conformément à un paramètre de proportion de l'instance de VNF déterminée et à la capacité du NS à faire l'objet d'une instanciation, calculer la capacité de l'instance de VNF déterminée ; conformément à la capacité de l'instance de VNF déterminée et aux informations de VNFD correspondant à l'instance de VNF déterminée, obtenir une ressource requise par l'instance de VNF déterminée ; et, conformément à la ressource déterminée, effectuer un déploiement de service de réseau virtuel sur l'instance de VNF déterminée, ce qui permet de réaliser le déploiement de multiples instances de VNF et l'ajustement automatique de la capacité des instances de VNF déployées, et d'économiser efficacement des ressources virtuelles.
PCT/CN2015/073413 2014-03-31 2015-02-28 Procédé et dispositif de déploiement de service de réseau virtuel WO2015149600A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410127072.2A CN104954220B (zh) 2014-03-31 2014-03-31 一种虚拟网络业务部署方法和设备
CN201410127072.2 2014-03-31

Publications (1)

Publication Number Publication Date
WO2015149600A1 true WO2015149600A1 (fr) 2015-10-08

Family

ID=54168593

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/073413 WO2015149600A1 (fr) 2014-03-31 2015-02-28 Procédé et dispositif de déploiement de service de réseau virtuel

Country Status (2)

Country Link
CN (1) CN104954220B (fr)
WO (1) WO2015149600A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017080517A1 (fr) 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de tranche de réseau
EP3285439A4 (fr) * 2015-12-30 2018-05-16 Huawei Technologies Co., Ltd. Procédé et dispositif de gestion de cycle de vie de service réseau
US10200463B2 (en) 2017-05-22 2019-02-05 At&T Intellectual Property I, L.P. Systems and methods to improve the performance of a network by more efficient virtual network resource allocation
CN110401554A (zh) * 2018-04-25 2019-11-01 中移(苏州)软件技术有限公司 Vnf纳管的方法、装置、***、电子设备及存储介质
CN110572272A (zh) * 2018-06-06 2019-12-13 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排***
CN112889247A (zh) * 2018-10-18 2021-06-01 华为技术有限公司 Vnf服务实例化方法及装置
US11304129B2 (en) 2016-01-15 2022-04-12 Apple Inc. Network slice selection in network systems

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3240253A4 (fr) * 2015-01-19 2018-01-24 Huawei Technologies Co., Ltd. Procédé, appareil et système d'association d'un ns à une vnf
CN106603371B (zh) 2015-10-14 2020-11-24 中兴通讯股份有限公司 一种网络功能虚拟化***及网络服务实例化方法
WO2017067567A1 (fr) 2015-10-19 2017-04-27 Nokia Solutions And Networks Oy Unités de déploiement virtuel (vdu) dormants dans un descripteur de fonction de réseau virtuel (vnfd)
WO2017070963A1 (fr) * 2015-10-31 2017-05-04 华为技术有限公司 Procédé, appareil et système pour déployer des ressources virtuelles
CN106685679A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网络服务部署方法和装置
CN105933136B (zh) * 2015-11-30 2019-09-17 ***股份有限公司 一种资源调度方法及***
CN106856438B (zh) * 2015-12-09 2020-02-14 华为技术有限公司 一种网络业务实例化的方法、装置及nfv***
CN106936619B (zh) * 2015-12-31 2020-10-09 华为技术有限公司 部署网络服务的方法和装置
CN105681437B (zh) * 2016-01-28 2019-07-19 华为技术有限公司 一种网络功能的实现方法和装置
EP3402131B1 (fr) * 2016-03-02 2021-05-26 Huawei Technologies Co., Ltd. Procédé de configuration de ressources, gestionnaire virtualisé de fonction de réseau et système de gestion d'élément de réseau
CN107222324B (zh) * 2016-03-22 2021-05-14 华为技术有限公司 网络服务的业务配置方法和装置
WO2017166136A1 (fr) 2016-03-30 2017-10-05 华为技术有限公司 Procédé et dispositif d'allocation de ressource de fonction de réseau virtuelle (vnf)
CN107306201A (zh) * 2016-04-22 2017-10-31 华为技术有限公司 虚拟化网络的部署方法和部署***
CN112165424B (zh) * 2016-04-29 2021-07-13 华为技术有限公司 一种业务部署方法、装置以及网元
CN112256343B (zh) * 2016-05-10 2022-05-10 华为技术有限公司 一种软件加载方法、设备及***
WO2017206092A1 (fr) * 2016-05-31 2017-12-07 华为技术有限公司 Procédé de gestion de cycle de vie et unité de gestion
CN107493184B (zh) * 2016-06-12 2022-06-07 中兴通讯股份有限公司 虚拟化网络功能部署方法及***
BR112018076166A2 (pt) * 2016-06-16 2019-03-26 Huawei Tech Co Ltd método e aparelho de gerenciamento de recursos de fatia da rede
CN109417501B (zh) * 2016-06-30 2020-11-17 华为技术有限公司 网络资源的编排方法和设备
WO2018014356A1 (fr) * 2016-07-22 2018-01-25 华为技术有限公司 Procédé et appaeil de chargement
CN107689882B (zh) 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
CN108011739B (zh) * 2016-10-31 2021-05-04 华为技术有限公司 一种虚拟网络的部署方法、装置及***
CN108156095B (zh) * 2016-12-02 2020-07-14 中兴通讯股份有限公司 资源确定方法及装置、nfvo
CN107147517A (zh) 2017-03-24 2017-09-08 上海交通大学 一种针对虚拟网络功能的自适应计算资源分配方法
CN109032751B (zh) 2017-06-12 2022-02-11 华为技术有限公司 一种虚拟机部署方法及omm虚拟机
CN109213567B (zh) 2017-06-29 2022-05-13 华为技术有限公司 一种管理vnf实例化的方法和设备
CN109218046B (zh) * 2017-06-30 2021-09-14 ***通信有限公司研究院 网络切片的管理方法及***和存储介质
CN109413011B (zh) * 2017-08-18 2021-12-14 华为技术有限公司 公共服务资源申请方法、相关设备及***
CN109600768B (zh) 2017-09-30 2022-06-07 华为技术有限公司 网络切片的管理方法、设备及***
CN109660575B (zh) * 2017-10-10 2022-08-02 中兴通讯股份有限公司 Nfv业务部署的实现方法和装置
CN107948006B (zh) * 2018-01-09 2021-04-16 重庆邮电大学 一种虚拟化网络功能的编排方法及装置
CN110324164B (zh) * 2018-03-29 2020-10-16 华为技术有限公司 一种网络切片的部署方法及装置
CN109379699B (zh) * 2018-11-12 2020-08-25 中国联合网络通信集团有限公司 创建虚拟化转发面网元的方法及装置
CN109688235B (zh) * 2019-03-18 2019-07-05 北京金山云网络技术有限公司 虚拟网络业务处理方法、装置和***，控制器，存储介质
CN112953751B (zh) * 2019-12-11 2023-11-28 ***通信有限公司研究院 一种模板处理方法、装置、设备及计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581325A (zh) * 2013-11-11 2014-02-12 中国联合网络通信集团有限公司 一种云计算资源池***及其实现方法
CN103607349A (zh) * 2013-11-14 2014-02-26 华为技术有限公司 虚拟网络中确定路由的方法及运营商边缘设备
WO2014110453A1 (fr) * 2013-01-11 2014-07-17 Huawei Technologies Co., Ltd. Virtualisation d'une fonction de réseau destinée à un dispositif de réseau

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7561535B2 (en) * 2005-06-24 2009-07-14 Aylus Networks, Inc. System and method for providing dynamic call models for users as function of the user environment in an IMS network
US8023425B2 (en) * 2009-01-28 2011-09-20 Headwater Partners I Verifiable service billing for intermediate networking devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014110453A1 (fr) * 2013-01-11 2014-07-17 Huawei Technologies Co., Ltd. Virtualisation d'une fonction de réseau destinée à un dispositif de réseau
CN103581325A (zh) * 2013-11-11 2014-02-12 中国联合网络通信集团有限公司 一种云计算资源池***及其实现方法
CN103607349A (zh) * 2013-11-14 2014-02-26 华为技术有限公司 虚拟网络中确定路由的方法及运营商边缘设备

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108293004B (zh) * 2015-11-13 2020-07-14 华为技术有限公司 用于网络切片管理的***和方法
US10791040B2 (en) 2015-11-13 2020-09-29 Huawei Technologies Co., Ltd. Systems and methods for network slice management
EP3332509A4 (fr) * 2015-11-13 2018-06-27 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de tranche de réseau
CN108293004A (zh) * 2015-11-13 2018-07-17 华为技术有限公司 用于网络切片管理的***和方法
US10129108B2 (en) 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
WO2017080517A1 (fr) 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de tranche de réseau
US10700947B2 (en) 2015-12-30 2020-06-30 Huawei Technologies Co., Ltd Life cycle management method and device for network service
EP3668009A1 (fr) * 2015-12-30 2020-06-17 Huawei Technologies Co. Ltd. Procédé et dispositif de gestion de cycle de vie de service de réseau
EP3285439A4 (fr) * 2015-12-30 2018-05-16 Huawei Technologies Co., Ltd. Procédé et dispositif de gestion de cycle de vie de service réseau
TWI831454B (zh) * 2016-01-15 2024-02-01 美商蘋果公司 網路系統中的網路切片選擇之技術
US11304129B2 (en) 2016-01-15 2022-04-12 Apple Inc. Network slice selection in network systems
US11950183B2 (en) 2016-01-15 2024-04-02 Apple Inc. Network slice selection in network systems
TWI784936B (zh) * 2016-01-15 2022-12-01 美商蘋果公司 網路系統中的網路切片選擇之技術
US10200463B2 (en) 2017-05-22 2019-02-05 At&T Intellectual Property I, L.P. Systems and methods to improve the performance of a network by more efficient virtual network resource allocation
US10749944B2 (en) 2017-05-22 2020-08-18 Shopify Inc. Systems and methods to improve the performance of a network by more efficient virtual network resource allocation
CN110401554B (zh) * 2018-04-25 2021-11-30 中移(苏州)软件技术有限公司 Vnf纳管的方法、装置、***、电子设备及存储介质
CN110401554A (zh) * 2018-04-25 2019-11-01 中移(苏州)软件技术有限公司 Vnf纳管的方法、装置、***、电子设备及存储介质
US11233699B2 (en) 2018-06-06 2022-01-25 Datang Mobile Communications Equipment Co., Ltd. Network slice creation method and management and orchestration system
CN110572272B (zh) * 2018-06-06 2020-11-06 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排***
CN110572272A (zh) * 2018-06-06 2019-12-13 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排***
CN112889247A (zh) * 2018-10-18 2021-06-01 华为技术有限公司 Vnf服务实例化方法及装置
CN112889247B (zh) * 2018-10-18 2022-05-31 华为技术有限公司 Vnf服务实例化方法及装置

Also Published As

Publication number Publication date
CN104954220A (zh) 2015-09-30
CN104954220B (zh) 2018-01-16

Similar Documents

Publication Publication Date Title
WO2015149600A1 (fr) Procédé et dispositif de déploiement de service de réseau virtuel
US11960915B2 (en) Method and apparatus for creating virtual machine based on parameter information of a virtual network interface card
US10701139B2 (en) Life cycle management method and apparatus
WO2019184967A1 (fr) Procédé et appareil de déploiement de tranche de réseau
CN105812171B (zh) 一种虚拟化的网络功能vnf控制方法和设备
US20190109768A1 (en) Management of network slices and associated services
AU2015419073B2 (en) Life cycle management method and device for network service
WO2018024059A1 (fr) Procédé et dispositif de déploiement de service dans un réseau virtualisé
US11301303B2 (en) Resource pool processing to determine to create new virtual resource pools and storage devices based on currebt pools and devices not meeting SLA requirements
US10924966B2 (en) Management method, management unit, and system
JP6658882B2 (ja) 制御装置、ｖｎｆ配置先選択方法及びプログラム
WO2016155394A1 (fr) Procédé et dispositif pour établir une liaison entre des fonctions réseau virtualisées
WO2017080391A1 (fr) Procédé et dispositif de déploiement de service de réseau
JP2015056182A5 (fr)
CN110221918A (zh) 一种ns与vnf的关联方法、装置及***
JP6568238B2 (ja) ハードウェアアクセラレーション方法及び関連デバイス
CN108132827B (zh) 一种网络切片资源映射方法、相关设备及***
WO2020103925A1 (fr) Procédé et appareil de déploiement de fonction de réseau virtualisée de mise en conteneur
CN106856438B (zh) 一种网络业务实例化的方法、装置及nfv***
CN109743205B (zh) 一种云平台os网络管理方法、装置及服务器
CN107005427A (zh) 一种资源管理方法及装置
WO2016101639A1 (fr) Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services
WO2020135517A1 (fr) Procédé et dispositif de déploiement d'une fonction de réseau virtuel
WO2017070963A1 (fr) Procédé, appareil et système pour déployer des ressources virtuelles
US20180374110A1 (en) Cost-driven approach to determine inventory layout in cloud computing environments

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase
122 Ep: pct application non-entry in european phase

Ref document number: 15773764

Country of ref document: EP

Kind code of ref document: A1