WO2020249080A1 - 一种虚拟网络功能vnf部署方法及装置 - Google Patents

一种虚拟网络功能vnf部署方法及装置 Download PDF

Info

Publication number
WO2020249080A1
WO2020249080A1 PCT/CN2020/095804 CN2020095804W WO2020249080A1 WO 2020249080 A1 WO2020249080 A1 WO 2020249080A1 CN 2020095804 W CN2020095804 W CN 2020095804W WO 2020249080 A1 WO2020249080 A1 WO 2020249080A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
parameters
vnfd
value
parameter
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/095804
Other languages
English (en)
French (fr)
Inventor
李世涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20823574.7A priority Critical patent/EP3972196B1/en
Publication of WO2020249080A1 publication Critical patent/WO2020249080A1/zh
Priority to US17/548,839 priority patent/US11683222B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058—Service discovery by the service manager
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Definitions

  • This application relates to the field of network function virtualization, and in particular to a method and device for deploying a virtual network function VNF.
  • Network function virtualization (NFV) technology is the use of virtualization technology to virtualize the functions of special equipment in traditional networks into independent applications, which can be flexibly deployed on standard-based computing hardware, storage hardware, network hardware and other equipment Built on a unified infrastructure platform.
  • VNF virtual network function
  • the party that initiates the virtual network function (virtual network function, VNF) request can be referred to as the virtual service requester.
  • the party that receives the instantiation VNF request and deploys the VNF according to the instantiated VNF request may be referred to as the virtualization service provider.
  • VNF descriptor, VNFD VNF template
  • the VNFD includes input parameters required to deploy the VNF
  • the instantiating VNF request includes the values of the input parameters.
  • the VNF is deployed according to the updated VNFD.
  • the European Telecommunications Standards Institute (ETSI) NFV standard stipulates that the service-related special parameters in the input parameters are uniformly defined as modified The attribute (modifiable_attributes) parameter, and the value of the modified attribute parameter is notified to the virtualization service provider by modifying the VNF information (ModifyVnfInfo) request.
  • ETSI European Telecommunications Standards Institute
  • the request to instantiate the VNF includes modifying the attribute parameters and the values of the common parameters related to all VNFs.
  • the virtualization service provider can learn the value of the modified attribute parameter through the modify VNF information request, the traditional technology does not propose how to use the value of the modified attribute parameter included in the modify VNF information request to modify the attribute parameter in the VNFD The scheme of assignment. Therefore, the virtualization service provider can only assign values to the general parameters in the VNFD by using the values of the general parameters included in the instantiation VNF request, and the modified attribute parameters in the VNFD are not assigned values, resulting in a failure to deploy the VNF.
  • This application provides a method and device for deploying a virtual network function VNF, which solves the problem of how to assign values to modified attribute parameters in the VNFD.
  • the present application provides a VNF deployment method, which can be applied to an application deployment server, or the method can be applied to a communication device that can support the application deployment server to implement the method, for example, the communication device includes a chip system.
  • the application deployment server may be a VNF manager (VNF manager, VNFM).
  • the method includes: after receiving the VNF information modification request, obtaining the VNFD of the first VNF, and assigning the N dedicated parameters and the value of each dedicated parameter to the modified attribute parameter in the VNFD according to the second assignment instruction, to obtain The first updated VNFD, where the request to modify the VNF information includes modifying the attribute parameter, the modified attribute parameter includes N dedicated parameters and the value of each dedicated parameter, and the value of the N dedicated parameters and each dedicated parameter is instantiated
  • the parameters required by the first VNF N is an integer, N ⁇ 1;
  • the VNFD of the first VNF includes M general parameters, modified attribute parameters, M first assignment instructions and one second assignment instruction, and one first assignment instruction
  • the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider, M is an integer, and M ⁇ 1; then, after receiving After the VNF instantiation request, the values of the M general parameters are assigned to the corresponding general parameters in the first updated VNFD according
  • this application provides a VNF deployment method, which can be applied to an application deployment server, or the method can be applied to a communication device that can support the application deployment server to implement the method, for example, the communication device includes a chip system.
  • the application deployment server may be a VNFM.
  • the method includes: after receiving the VNF information modification request and the VNF instantiation request, obtaining the VNFD of the first VNF, and assigning the values of M general parameters to the corresponding general parameters in the VNFD according to the first assignment instruction, and Assign the N dedicated parameters and the value of each dedicated parameter to the modified attribute parameter in the VNFD according to the second assignment instruction to obtain the first updated VNFD, and deploy the first VNF according to the first updated VNFD.
  • the request for modifying VNF information includes modifying attribute parameters.
  • the modified attribute parameters include N dedicated parameters and the value of each dedicated parameter.
  • the N dedicated parameters and the value of each dedicated parameter are the parameters required to instantiate the first VNF.
  • N is an integer, N ⁇ 1;
  • the VNF instantiation request includes M general parameters and the value of each general parameter, M general parameters and the value of each general parameter are the parameters needed to instantiate the first VNF, M is an integer, M ⁇ 1;
  • the VNFD of the first VNF includes M general parameters, modified attribute parameters, M first assignment indications and a second assignment indication.
  • a first assignment indication is used to indicate the value of a common parameter Obtained from the virtualization service requester, and the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider.
  • indication information is set for the general parameters and the special parameters respectively, indicating the source of the value of the general parameter and the source of the value of the special parameter included in the input parameter, and the application deployment server pairs
  • the application deployment server can assign values to the general parameters in the VNFD according to the first assignment instruction, and assign values to the modified attribute parameters in the VNFD according to the second assignment instruction, so that all input parameters in the VNFD can be assigned Assign value and successfully deploy VNF.
  • the virtualization service requester is an NFV orchestrator (NFV orchestrator, NFVO) or an operation-support system/business support system (OSS/BSS).
  • NFV orchestrator NFV orchestrator
  • OSS/BSS operation-support system/business support system
  • the virtualization service requester may be user equipment.
  • the virtualization service provider is VNFM.
  • the virtualization service provider may be an application deployment server.
  • the method before receiving the request to modify the VNF information, further includes: after receiving the VNF instance identification request sent by NFVO, creating the instance identification of the first VNF, and establishing the first VNF The corresponding relationship between the instance ID and the VNFD ID of the first VNF, and the instance ID of the first VNF is sent to the NFVO.
  • the request for creating a VNF instance identifier includes the VNFD identifier of the first VNF.
  • obtaining the VNFD of the first VNF includes: sending a VNFD obtaining request to NFVO, the VNFD obtaining request including the VNFD identifier of the first VNF; receiving the VNFD response request sent by NFVO, the VNFD response request including The VNFD of the first VNF.
  • the request for modifying the VNF information also includes the instance identifier of the first VNF
  • the VNF instantiation request also includes the instance identifier of the first VNF.
  • the method further includes: determining the identifier of the VNFD of the first VNF associated with the instance identifier of the first VNF; and determining the VNFD of the first VNF according to the identifier of the VNFD of the first VNF.
  • the method further includes: creating a VNF information storage space, where the VNF information storage space is used to store the N dedicated parameters and the value of each dedicated parameter. Therefore, the application deployment server can obtain the value of the modified attribute parameter from the VNF information storage space, and assign the value of the modified attribute parameter in the VNFD, so as to assign all the input parameters in the VNFD and successfully deploy the VNF.
  • this application provides a VNF deployment method, which can be applied to user equipment, or the method can be applied to a communication device that can support the user equipment to implement the method, for example, the communication device includes a chip system.
  • the user equipment may be NFVO.
  • the method includes: sending a request for modifying VNF information, the request for modifying VNF information includes modifying an attribute parameter, the modifying attribute parameter includes N dedicated parameters and the value of each dedicated parameter, the N dedicated parameters and the value of each dedicated parameter Parameters required to instantiate the first VNF, N is an integer, N ⁇ 1; send the VNFD of the first VNF, the VNFD of the first VNF includes M general parameters, modified attribute parameters, M first assignment instructions and a second Assignment indication, the first assignment indication is used to indicate that the value of a common parameter is obtained from the virtualization service requester, and the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider; sending a VNF instantiation request , The VNF instantiation request includes M general parameters and the value of each general parameter, the value of M general parameters and each general parameter is the parameter required to instantiate the first VNF, M is an integer, and M ⁇ 1.
  • this application provides a VNF deployment method, which can be applied to user equipment, or the method can be applied to a communication device that can support the user equipment to implement the method, for example, the communication device includes a chip system.
  • the user equipment may be NFVO.
  • the method includes: sending a request for modifying VNF information, the request for modifying VNF information includes modifying an attribute parameter, the modifying attribute parameter includes N dedicated parameters and the value of each dedicated parameter, the N dedicated parameters and the value of each dedicated parameter
  • the parameters required to instantiate the first VNF, N is an integer, N ⁇ 1; send a VNF instantiation request, the VNF instantiation request includes M common parameters and the value of each common parameter, M common parameters and each common parameter
  • the value of the parameter is the parameter required to instantiate the first VNF, M is an integer, M ⁇ 1; the VNFD of the first VNF is sent, and the VNFD of the first VNF includes M general parameters, modified attribute parameters, and M first assignments Indication and a second assignment indication, the first assignment indication is used to indicate that the value of a general parameter is obtained from the virtualization service requester, and the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider.
  • indication information is set for the general parameters and the special parameters respectively, indicating the source of the value of the general parameter and the source of the value of the special parameter included in the input parameter, and the application deployment server pairs
  • the application deployment server can assign values to the general parameters in the VNFD according to the first assignment instruction, and assign values to the modified attribute parameters in the VNFD according to the second assignment instruction, so that all input parameters in the VNFD can be assigned Assign value and successfully deploy VNF.
  • the virtualization service requester is NFVO or OSS/BSS.
  • the virtualization service requester may be user equipment.
  • the virtualization service provider is VNFM.
  • the virtualization service provider may be an application deployment server.
  • the method when the first assignment indication is used to indicate that the value of a general parameter is obtained from NFVO, before NFVO sends the VNF instantiation request, the method further includes: NFVO setting the value of the general parameter value.
  • the method before sending the request to modify the VNF information, further includes: sending an instance identification request for creating a VNF, receiving the instance identification of the first VNF, and saving the instance identification of the first VNF.
  • the request for creating a VNF instance identifier includes the VNFD identifier of the first VNF.
  • the method before sending the VNFD of the first VNF, includes: after receiving the VNFD acquisition request including the VNFD identifier of the first VNF, acquiring according to the VNFD identifier of the first VNF VNFD of the first VNF, and send a VNFD response request, and the VNFD response request includes the VNFD of the first VNF.
  • this application also provides a communication device for implementing the method described in the first or second aspect.
  • the communication device is an application deployment server or a communication device that supports the application deployment server to implement the method described in the first aspect or the second aspect.
  • the communication device includes a chip system.
  • the communication device includes: a receiving unit and a processing unit.
  • the receiving unit is configured to receive a request for modifying VNF information.
  • the request for modifying VNF information includes modifying attribute parameters.
  • the modified attribute parameters include N dedicated parameters and the value of each dedicated parameter, N dedicated parameters and the value of each dedicated parameter.
  • the value is a parameter required to instantiate the first VNF, N is an integer, and N ⁇ 1; the receiving unit is also used to obtain a virtual network function template VNFD of the first VNF.
  • the VNFD of the first VNF includes M general parameters, Modify attribute parameters, M first assignment instructions, and one second assignment instruction.
  • a first assignment instruction is used to indicate that the value of a general parameter is obtained from the virtualization service requester, and the second assignment instruction is used to indicate that the attribute parameter is modified
  • the value is obtained from the virtualization service provider, M is an integer, and M ⁇ 1;
  • the processing unit is configured to assign the N dedicated parameters and the value of each dedicated parameter to the modified attribute in the VNFD according to the second assignment instruction Parameters to obtain the first updated VNFD;
  • the receiving unit is also used to receive a VNF instantiation request.
  • the VNF instantiation request includes M common parameters and the value of each common parameter, M common parameters and each common parameter
  • the value of the parameter is a parameter required to instantiate the first VNF; the processing unit is further configured to assign the values of the M general parameters to the corresponding general parameters in the first updated VNFD according to the first assignment instruction, Obtain the second updated VNFD; the processing unit is further configured to deploy the first VNF according to the second updated VNFD.
  • the processing unit is configured to assign the values of the M general parameters to the corresponding general parameters in the VNFD according to the first assignment instruction, and assign the N special parameters and the value of each special parameter according to the second assignment instruction The value is assigned to the modified attribute parameter in the VNFD to obtain the first updated VNFD; the processing unit is further configured to deploy the first VNF according to the first updated VNFD.
  • the communication device may further include a sending unit configured to send the instance identifier of the first VNF to the NFVO.
  • the sending unit is further configured to send a VNFD acquisition request to the NFVO, where the VNFD acquisition request includes the identifier of the VNFD of the first VNF.
  • this application also provides a communication device for implementing the method described in the third or fourth aspect.
  • the communication device is a user equipment or a communication device that supports the user equipment to implement the method described in the third aspect or the fourth aspect, for example, the communication device includes a chip system.
  • the communication device includes: a sending unit.
  • the sending unit is used to send a request for modifying VNF information.
  • the request for modifying VNF information includes modifying attribute parameters.
  • the modified attribute parameters include N dedicated parameters and the value of each dedicated parameter, N dedicated parameters and the value of each dedicated parameter.
  • the value is a parameter required to instantiate the first VNF, N is an integer, and N ⁇ 1; the sending unit is also used to send the virtual network function template VNFD of the first VNF.
  • the VNFD of the first VNF includes M general parameters, Modify attribute parameters, M first assignment instructions, and a second assignment instruction.
  • the first assignment instruction is used to indicate that the value of a general parameter is obtained from the virtualization service requester, and the second assignment instruction is used to indicate that the attribute parameter is modified.
  • the value is obtained from the virtualization service provider; the sending unit is also used to send a VNF instantiation request.
  • the VNF instantiation request includes M common parameters and the value of each common parameter, M common parameters and each common parameter The value of is a parameter required to instantiate the first VNF, M is an integer, and M ⁇ 1.
  • the communication device may further include a processing unit for setting the value of the general parameter.
  • indication information is respectively set for the general parameters and the special parameters, indicating the source of the value of the general parameter and the source of the value of the special parameter included in the input parameter.
  • the communication device can assign values to the general parameters in the VNFD according to the first assignment instruction, and assign values to the modified attribute parameters in the VNFD according to the second assignment instruction, so as to assign all the input parameters in the VNFD and successfully deploy the VNF .
  • the virtualization service requester is NFVO or OSS/BSS.
  • the virtualization service requester may be user equipment.
  • the virtualization service provider is VNFM.
  • the virtualization service provider may be an application deployment server.
  • the functional modules of the fifth aspect and the sixth aspect described above can be implemented by hardware, or implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the transceiver is used to complete the functions of the receiving unit and the transmitting unit
  • the processor is used to complete the function of the processing unit
  • the memory is used for the processor to process the program instructions of the method of the present application.
  • the processor, the transceiver, and the memory are connected through a bus and communicate with each other.
  • the present application also provides a communication device for implementing the method described in the first aspect or the second aspect.
  • the communication device is an application deployment server or a communication device that supports the application deployment server to implement the method described in the first aspect or the second aspect, for example, the communication device includes a chip system.
  • the communication device includes a processor, configured to implement the functions in the method described in the first aspect or the second aspect.
  • the communication device may also include a memory for storing program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute program instructions stored in the memory to implement the functions in the method described in the first aspect or the second aspect.
  • the communication device may further include a communication interface, and the communication interface is used for the communication device to communicate with other devices. Exemplarily, if the communication device is an application deployment server, the other equipment is user equipment.
  • the communication interface may be a transceiver.
  • the processor is configured to assign the values of the M general parameters to the corresponding general parameters in the VNFD according to the first assignment instruction, and assign the N special parameters and the value of each special parameter to the VNFD according to the second assignment instruction To obtain the first updated VNFD; and deploy the first VNF according to the first updated VNFD.
  • the present application also provides a communication device for implementing the method described in the third or fourth aspect.
  • the communication device is a user equipment or a communication device that supports the user equipment to implement the method described in the third aspect or the fourth aspect, for example, the communication device includes a chip system.
  • the communication device includes a processor, configured to implement the functions in the method described in the third aspect or the fourth aspect.
  • the communication device may also include a memory for storing program instructions and data. The memory is coupled with the processor, and the processor can call and execute program instructions stored in the memory to implement the functions in the method described in the third aspect or the fourth aspect.
  • the communication device may further include a communication interface, and the communication interface is used for the communication device to communicate with other devices. Exemplarily, if the communication device is a user equipment, the other equipment is an application deployment server.
  • the communication interface may be a transceiver.
  • the transceiver is used to send a request to modify VNF information.
  • the request for modifying VNF information includes modifying attribute parameters.
  • the modified attribute parameters include N dedicated parameters and the value of each dedicated parameter, and the value of N dedicated parameters and each dedicated parameter
  • the parameters required to instantiate the first VNF, N is an integer, N ⁇ 1; send a VNF instantiation request, the VNF instantiation request includes M common parameters and the value of each common parameter, M common parameters and each common parameter
  • the value of the parameter is the parameter required to instantiate the first VNF, M is an integer, M ⁇ 1; the VNFD of the first VNF is sent, and the VNFD of the first VNF includes M general parameters, modified attribute parameters, and M first assignments Indication and a second assignment indication, the first assignment indication is used to indicate that the value of a general parameter is obtained from the virtualization service requester, and the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained
  • the present application also provides a computer-readable storage medium, including: computer software instructions; when the computer software instructions are executed in a communication device, the communication device is caused to execute any one of the first to fourth aspects above The method described.
  • the present application also provides a computer program product containing instructions, when the computer program product runs in a communication device, the communication device executes the method described in any one of the first to fourth aspects.
  • the present application provides a chip system that includes a processor and may also include a memory for implementing the functions of the application deployment server or user equipment in the above method.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • the present application also provides a communication system that includes the application deployment server described in the fifth aspect or a communication device that supports the application deployment server to implement the method described in the first aspect, and the sixth aspect is described User equipment or a communication device that supports the user equipment to implement the method described in the third aspect;
  • the communication system includes the application deployment server described in the fifth aspect or a communication device that supports the application deployment server to implement the method described in the second aspect, and the user equipment described in the sixth aspect or supports the user equipment to implement the method described in the fourth aspect Method of communication device;
  • the communication system includes the application deployment server described in the seventh aspect or a communication device that supports the application deployment server to implement the method described in the first aspect, and the user equipment described in the eighth aspect or supports the user equipment to implement the method described in the third aspect Method of communication device;
  • the communication system includes the application deployment server described in the seventh aspect or a communication device that supports the application deployment server to implement the method described in the second aspect, and the user equipment described in the eighth aspect or supports the user equipment to implement the method described in the fourth aspect Method of communication device.
  • the names of the application deployment server, user equipment, and communication device do not limit the device itself. In actual implementation, these devices may appear under other names. As long as the function of each device is similar to that of this application, it falls within the scope of the claims of this application and equivalent technologies.
  • FIG. 1 is an example diagram of an NFV system architecture provided by an embodiment of the application
  • FIG. 2 is a flowchart of a VNF deployment method provided by this application.
  • FIG. 3 is a flowchart of another VNF deployment method provided by this application.
  • FIG. 5 is a schematic diagram of the composition of another communication device provided by this application.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • the traditional telecommunications system is composed of various dedicated hardware devices, and different hardware devices are used for different functions.
  • telecommunication systems are becoming more and more complex, which brings many challenges. For example, the development and launch of new services, system operation and maintenance, and resource utilization.
  • IT Internet
  • software defined network and open flow world conference software defined network and open flow world conference
  • NFV network function virtualization
  • ETSI European Telecommunications Standards Institute
  • ISG industry specific group
  • NFV technology uses virtualization technology to pool and virtualize the resources of infrastructure hardware devices (such as computing devices, storage devices, and network devices), provide virtual resources for upper-layer applications, and realize software and hardware decoupling.
  • infrastructure hardware devices such as computing devices, storage devices, and network devices
  • VNF independent applications
  • NFV technology utilizes cloud computing technology to achieve elastic scaling of applications and match virtual resources with business loads. This not only improves the utilization efficiency of virtual resources, but also improves the response rate of the NFV system.
  • FIG. 1 is an example diagram of an NFV system architecture provided by an embodiment of the application.
  • the NFV system can be used in various networks, such as a data center network, operator network or local area network.
  • NFV system includes a NFV management and orchestration system (NFV management and orchestration, NFV MANO) 101, NFV infrastructure layer (NFV infrastructure, NFVI) 102, multiple virtual network functions (Virtual Network Function, VNF) 103, multiple network elements Management (element management, EM) 104 and operation-support system/business support system (OSS/BSS) 105.
  • NFV management and orchestration NFV management and orchestration
  • NFV MANO NFV management and orchestration
  • NFV infrastructure layer NFV infrastructure layer
  • VNF Virtual Network Function
  • EM multiple network elements Management
  • OSS/BSS operation-support system/business support system
  • NFV MANO 101 is used to monitor and manage NFVI 102 and VNF 103.
  • the NFV management and orchestration system 101 includes an NFV orchestrator (NFVO) 1011, one or more VNF managers (VNF Manager, VNFM) 1012, and a virtualized infrastructure manager (VIM) 1013.
  • NFVO NFV orchestrator
  • VNF Manager VNF Manager
  • VIM virtualized infrastructure manager
  • NFVO 1011 is mainly responsible for handling the life cycle management of virtualized services, virtual infrastructure and the allocation and scheduling of virtual resources in NFVI.
  • NFVO 1011 can also execute resource-related requests from one or more VNFM 1012 (e.g. request to obtain VNFD), send configuration information (e.g. VNFD, VNF information modification request and VNF instantiation request) to VNFM 1012, and collect VNF 103 Status information.
  • VNFD can be stored on NFVO or in a database managed by NFVO, so that NFVO can obtain VNFD and feed back VNFD to VNFM, and VNFM deploys VNF according to VNFD.
  • NFVO can store VNFD of VNF with multiple functions.
  • NFVO 1011 can communicate with VIM 1013 to realize resource allocation and/or reservation and exchange configuration and status information of virtualized hardware resources.
  • VNFM 1012 is mainly responsible for the life cycle management of one or more VNF 103. For example, instantiating (instantiating), updating (updating), query, elastic scaling (scaling), terminating (terminating) VNF 103, etc.
  • the VNFM 1012 can communicate with the VNF 103 to complete the life cycle management of the VNF 103 and exchange configuration and status information.
  • the VIM 1013 can perform resource management functions, such as managing the allocation of infrastructure resources (such as adding resources to virtual containers) and operating functions (such as collecting NFVI fault information).
  • VNFM 1012 and VIM 1013 can communicate with each other for resource allocation and exchange configuration and status information of virtualized hardware resources. For example, it controls and manages the interaction of VNF 103 with computing hardware 1021, storage hardware 1022, network hardware 1023, virtual computing 1024, virtual storage 1025, and virtual network 1026.
  • NFVI 102 includes a hardware resource layer, a virtualization layer (virtualization layer), and a virtual resource layer.
  • NFVI102 includes hardware resources, software resources or a combination of both to complete the deployment of a virtualized environment.
  • the hardware resources and the virtualization layer are used to provide virtualized resources, for example, as virtual machines and other forms of virtual containers for the VNF 103.
  • the hardware resource layer includes computing hardware 1021, storage hardware 1022, and network hardware 1023.
  • the computing hardware 1021 may be off-the-shelf hardware on the market and/or user-customized hardware to provide processing and computing resources.
  • the storage hardware 1022 may be the storage capacity provided in the network or the storage capacity resident in the storage hardware 1022 itself (local storage in the server).
  • the resources of the computing hardware 1021 and the storage hardware 1022 may be centralized.
  • the network hardware 1023 may be a switch, a router, and/or any other network device configured to have a switching function.
  • the network hardware 1023 may span multiple domains, and may include multiple networks interconnected by one or more transmission networks.
  • the virtualization layer in NFVI 102 can abstract hardware resources from the physical layer and decouple the VNF 103, so as to provide virtualization resources to the VNF 103.
  • the virtual resource layer includes virtual computing 1024, virtual storage 1025, and virtual network 1026.
  • the virtual computing 1024 and the virtual storage 1025 may be provided to the VNF 103 in the form of a virtual machine and/or other virtual containers.
  • one or more VNFs 103 may be deployed on a virtual machine (virtual machine, VM).
  • the virtualization layer abstracts the network hardware 1023 to form a virtual network 1026.
  • the virtual network 1026 may include a virtual switch (virtual switch), and the virtual switch is used to provide connections between virtual machines and other virtual machines.
  • the transmission network in the network hardware 1023 can be virtualized using a centralized control plane and a separate forwarding plane (such as a software-defined network).
  • computing hardware 1021, storage hardware 1022, and network hardware 1023 may include multiple chassis, multiple racks, or even multiple computer rooms.
  • the VNF 103 may be configured to virtualize at least one network function performed by one physical network device.
  • the equipment management system (EM) 104 is a system used to configure and manage equipment in traditional networks. In the NFV system, EM 104 can also be used to configure and manage the VNF 103, and initiate a new VNF 103 to the VNFM 1012 Lifecycle management operations such as instantiation of
  • Operation Support System (Operations Support System and Business Support System, OSS/BSS) 105 supports various end-to-end telecommunication services.
  • the management functions supported by OSS include: network configuration, service provision, fault management, etc.
  • BSS handles orders, payments, income, etc., and supports product management, order management, revenue management and customer management.
  • the virtualized network service can be an IP multimedia subsystem (IMS) network service, or a next-generation mobile core network (Evolved Packet Core, EPC) network Service etc.
  • IMS IP multimedia subsystem
  • EPC Evolved Packet Core
  • One NS can contain several VNFs.
  • the virtualization service provider needs to obtain the description information of the service from the virtualization service requester, that is, the network service template (Network Service Descriptor, NSD).
  • the NSD mainly describes the topological structure information of the service and the description information of each VNF included, that is, the VNF template (VNF descriptor, VNFD).
  • VNF descriptor VNF descriptor
  • VNFD virtual link descriptor
  • VLD virtual link descriptor
  • the VNFD includes information such as a virtual deployment unit (Virtualization Deployment Unit, VDU), a connection point (CP), and a virtual connection (virtual link, VL).
  • VDU can represent a virtual machine with application software installed, and the description of the VDU will include a description of all virtual resources of the virtual machine.
  • CP represents the connection information on the virtual machine, for example, it can be virtual network card information, which can be represented by an IP address or a MAC address.
  • VL is a virtual connection connecting multiple VDUs within a VNF, which can be represented by information such as connection type and bandwidth.
  • TOSCA Topicology and Orchestration Specification for Cloud Applications
  • OASIS Advanced Open Standards for the Information Society
  • the information required to deploy an application may be described in the application deployment package.
  • the application deployment package contains at least one application deployment description file with a suffix of ste.
  • the *.ste application deployment description file can describe the deployment information of the application in XML language.
  • the root element of the *.ste application deployment description file is the application template ( Service Template). That is to say, the application template can be used in the embodiment of the present application to completely describe the information of the application to be deployed.
  • the sub-elements of the *.ste application deployment description file include topology template (TopologyTemplate), node type (NodeType), node template (NodeTemplate), relationship type (RelationshipType), relationship template (RelationshipTemplate), boundary definitions (BoundaryDefinitions), etc.
  • the input parameters defined in inputs are dynamic parameters.
  • the values of these input parameters can only be determined during deployment, for example, they can be carried in the VNF instantiation request.
  • the input parameters included in the VNFD corresponding to different VNFs are different.
  • the ETSI NFV standard stipulates that service-related special parameters in the input parameters are uniformly defined as modified attributes (modifiable_attributes) parameters.
  • the so-called dedicated parameters are service-related parameters.
  • the dedicated parameters can be completely different or partially different. Therefore, the input parameters include common parameters and modified attribute parameters related to all VNFs.
  • flavour and instantiation_level are common parameters.
  • the value of the general parameter may be carried in the instantiation VNF request, and notified to the virtualization service provider by the virtualization service requester.
  • the VNF instantiation request only needs to carry the value of the general parameter and the modified attribute parameter.
  • the modified attribute parameters include service-related dedicated parameters, such as vcpe_image_name, public_net_id, and vgw_name_0 in the above example.
  • the VNF information modification request can be used to assign or modify the dedicated parameters, and the virtualization service requester will notify the virtualization service provider.
  • the virtualization service provider can learn the value of the modified attribute parameter through the modify VNF information request, the traditional technology does not propose how to use the value of the modified attribute parameter included in the modify VNF information request to modify the attribute parameter in the VNFD The scheme of assignment. Therefore, the virtualization service provider can only assign values to the general parameters in the VNFD by using the values of the general parameters included in the instantiation VNF request, and the modified attribute parameters in the VNFD are not assigned values, resulting in a failure to deploy the VNF.
  • the embodiment of the application provides a VNF deployment method, the method includes: in the VNFD, setting indication information for general parameters and special parameters respectively, indicating the source of the value of the general parameter included in the input parameter and the value of the special parameter Source:
  • the virtualization service provider assigns values to the general parameters and the special parameters, the value of the general parameter is obtained according to the indication information of the general parameter, and the value of the special parameter is obtained according to the indication information of the special parameter.
  • the virtualization service provider can assign values to the general parameters and modified attribute parameters in the VNFD, so as to assign all the input parameters in the VNFD and successfully deploy the VNF.
  • the virtualization service requester may be user equipment.
  • the virtualization service requester can be NFVO or OSS/BSS.
  • the virtualization service provider may be an application deployment server.
  • the virtualization service provider may be a VNFM.
  • Fig. 2 is a flowchart of a VNF deployment method provided by an embodiment of the application. As shown in Fig. 2, the method may include:
  • the NFVO sends a VNF creation instance identification request to the VNFM.
  • the VNF instance ID request is used to request the creation of an instance ID for a VNF that needs to be deployed.
  • the VNFM receives an instance identification request for creating a VNF sent by NFVO.
  • the VNFM After the VNFM receives the VNF instance identification request sent by NFVO, it can send a reception response to NFVO to inform NFVO that it has successfully received the VNF instance identification request. In addition, the VNFM performs S203 and S204.
  • the VNFM creates an instance identifier of the first VNF.
  • the VNFM After the VNFM receives the VNF instance ID request sent by the NFVO, it creates the instance ID of the first VNF.
  • This VNF creation instance identification request includes the VNFD identification of the first VNF.
  • the VNFM may also establish a correspondence between the instance identifier of the first VNF and the VNFD identifier of the first VNF.
  • the VNFM creates a VNF information storage space.
  • the VNF information storage space is used to store information related to the deployment of the VNF.
  • the relevant information about the deployment of the VNF may include the input parameters of the VNF (such as passing parameters and modifying attribute parameters), VLD, VDU, CP, VL, and so on.
  • a VNF information storage space corresponding to the instance identifier of the first VNF can be created to store relevant information for deploying the first VNF.
  • the VNFM sends the instance identifier of the first VNF to the NFVO.
  • sequence of the steps of the VNF deployment method provided in the embodiments of this application can be adjusted appropriately, and the steps can also be increased or decreased according to the situation.
  • sequence of S204 to S205 can be interchanged, namely Perform S205, and then perform S204. Any person skilled in the art can easily think of a method of change within the technical scope disclosed in this application, which should be covered by the protection scope of this application, so it will not be repeated.
  • the NFVO receives the instance identifier of the first VNF sent by the VNFM.
  • the NFVO After receiving the instance ID of the first VNF sent by the VNFM, the NFVO stores the instance ID of the first VNF, and can send a reception response to the VNFM to inform the VNFM that the instance ID of the first VNF has been successfully received.
  • the NFVO sends a VNF information modification request to the VNFM.
  • the request for modifying VNF information includes modifying attribute parameters.
  • the modified attribute parameter includes N dedicated parameters and the value of each dedicated parameter.
  • the value of N dedicated parameters and each dedicated parameter is a parameter required to instantiate the first VNF, N is an integer, and N ⁇ 1.
  • this application provides a description example of modifying attribute parameters:
  • the modified attribute parameter includes 3 special parameters and the value of each special parameter.
  • the three dedicated parameters are vcpe_image_name, public_net_id and vgw_name_0.
  • the value of vcpe_image_name is image123.
  • the value of public_net_id is 123456.
  • the value of vgw_name_0 is vgw123.
  • the request for modifying the VNF information also includes the instance identifier of the first VNF, so that the VNFM stores the N dedicated parameters and the value of each dedicated parameter in the VNF corresponding to the instance identifier of the first VNF according to the instance identifier of the first VNF.
  • Information storage space. The instance identifier of the first VNF is notified to NFVO in advance by the VNFM.
  • the VNFM receives the VNF information modification request sent by the NFVO.
  • the VNFM After the VNFM receives the VNF information modification request sent by the NFVO, it can store the N dedicated parameters and the value of each dedicated parameter included in the modified attribute parameter in the VNF information storage space corresponding to the instance identifier of the first VNF. At the same time, VNFM can send a receiving response to NFVO to inform NFVO that it has successfully received the request to modify VNF information.
  • the VNFM obtains the VNFD of the first VNF.
  • the VNFM may send a VNFD acquisition request to the NFVO.
  • the VNFD acquisition request includes the identification of the VNFD of the first VNF, and the identification of the VNFD of the first VNF is notified to the VNFM in advance by the NFVO.
  • NFVO stores VNFDs of VNFs with different functions. After NFVO receives the VNFD obtaining request, NFVO can obtain the VNFD of the first VNF according to the VNFD identifier of the first VNF, and send a VNFD response request to the VNFM.
  • the VNFD response request includes the first VNFD.
  • the VNFM sends a reception response to the NFVO, so as to inform the NFVO that the VNFD of the first VNF has been successfully received.
  • the VNFD of the first VNF includes M general parameters, modified attribute parameters, M first assignment instructions, and one second assignment instruction.
  • a first assignment indication is used to indicate that the value of a general parameter is obtained from the virtualization service requester.
  • the M first assignment indications indicate the source of the values of the M general parameters.
  • the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider.
  • M is an integer, M ⁇ 1.
  • an example of a topology template in a VNFD of a first VNF provided in this application:
  • the first assignment indication may be "source: user".
  • the "source: user” in the general parameter "flavour” is used to indicate that the value of "flavour” is obtained from the virtualization service requester (for example, the requesting user (user)).
  • the “source: user” in the general parameter “instantiation_level” is used to indicate that the value of the "instantiation_level” is obtained from the virtualization service requester (such as the requesting user (user)).
  • the requesting user can be OSS/BSS.
  • the virtualization service request sends a VNF instantiation request to the virtualization service provider, and the VNF instantiation request carries the common parameters and the values of the common parameters.
  • the VNFM can obtain the value of "flavour” from the VNF instantiation request and assign the value of "flavour”.
  • the VNFM can obtain the value of "instantiation_level” from the VNF instantiation request and assign the value of "instantiation_level”.
  • the virtualization service requester may also be NFVO.
  • the first assignment indication may be "source:NFVO”.
  • an example of a topology template in a VNFD of another first VNF provided in this application:
  • the "source:NFVO" in the general parameter "vimConnectionInfo” is used to indicate to obtain the value of "vimConnectionInfo” from the virtualization service requester (NFVO).
  • the VNFM may obtain the value of "vimConnectionInfo” from the VNF instantiation request and assign the value of vimConnectionInfo.
  • the second assignment indication may be "source: VNFM".
  • the "source:VNFM" in the modified attribute parameter is used to instruct to obtain the value of the modified attribute parameter from the virtualization service provider (such as VNFM).
  • the VNFM may obtain the value of the modified attribute parameter from the request for modifying the VNF information.
  • first assignment indication and the second assignment indication may be set when the VNFD is designed. After receiving the VNFD, the NFVO and VNFM can determine whether to assign a value to the corresponding parameter according to the first assignment instruction and the second assignment instruction.
  • the VNFD of the first VNF may also include other information related to the deployment of the first VNF, such as VDU, CP, VL, etc.
  • VDU the deployment of the first VNF
  • CP the deployment of the first VNF
  • VL the deployment of the first VNF
  • the VNFM assigns the N dedicated parameters and the value of each dedicated parameter to the modified attribute parameter in the VNFD according to the second assignment instruction to obtain the first updated VNFD.
  • the VNFM After the VNFM obtains the VNFD of the first VNF, it parses the VNFD of the first VNF, and determines according to the first assignment instruction that the value source of the common parameters in the VNFD of the first VNF is NFVO or OSS/BSS. At this time, the VNFM has not been obtained yet Therefore, it is impossible to assign a value to the common parameter, and there is no need to update the VNFD of the first VNF. Further, it is determined according to the second assignment instruction that the value source of the modified attribute parameter in the VNFD of the first VNF is the VNFM.
  • the VNFM Since the VNFM pre-stores the N dedicated parameters included in the modified attribute parameters and the value of each dedicated parameter, the VNFM obtains the N dedicated parameters and the value of each dedicated parameter from the VNF information storage space corresponding to the instance identifier of the first VNF. The value of the N dedicated parameters and the value of each dedicated parameter are assigned to the modified attribute parameter in the VNFD of the first VNF to obtain the first updated VNFD.
  • the modified attribute parameters stored in the VNF information storage space corresponding to the instance identifier of the first VNF include the following special parameters and the values of the special parameters: vcpe_image_name, public_net_id, vgw_name_0, vcpe_image_name value image123, public_net_id value 123456 ,
  • the value of vgw_name_0 is vgw123.
  • the VNFM assigns vcpe_image_name, public_net_id, vgw_name_0, vcpe_image_name values image123, public_net_id value 123456, and vgw_name_0 value vgw123 to the modified attribute parameters in the VNFD of the first VNF according to the second assignment instruction to obtain the first updated VNFD .
  • the modified attribute parameters stored in the VNF information storage space corresponding to the instance identifier of the first VNF are as follows:
  • the VNFD after the first update is as follows:
  • the VNFM can determine whether all the input parameters in the first updated VNFD are assigned. If all the input parameters in the first updated VNFD are not assigned, the VNFM first saves the first updated VNFD.
  • the VNFM can also convert the VNFD file after assigning modified attribute parameters to any other file suitable for machine processing, such as JSON, XML, and other formats for saving, which is not limited in this application.
  • the NFVO sends a VNF instantiation request to the VNFM.
  • the VNF instantiation request includes the instance identifier of the first VNF, M general parameters, and the value of each general parameter.
  • the instance identifier of the first VNF is notified to NFVO in advance by the VNFM.
  • the M general parameters and the value of each general parameter are parameters required to instantiate the first VNF.
  • the VNF instantiation request includes 2 general parameters and the value of each general parameter.
  • the two general parameters can be flavour and instantiation_level respectively.
  • the value of flavour is flavour-1.
  • the value of instantiation_level is level-1.
  • the value of the general parameter may be assigned to it by OSS/BSS.
  • the NFVO may also assign a suitable value to the general parameter of the VNFD whose source is NFVO, and carry it in the VNF instantiation request.
  • the source of vimConnectionInfo in the input parameter is NFVO, and NFVO needs to be assigned to vimConnectionInfo.
  • NFVO assigns a value of 10.2.2.2 to vimConnectionInfo. Therefore, the content carried in the VNF instantiation request at this time includes the values of flavour, instantiation_level, vimConnectionInfo, and flavour values of flavour-1, instantiation_level values of level-1 and vimConnectionInfo. Take the value 10.2.2.2.
  • the VNFM receives the VNF instantiation request sent by the NFVO.
  • VNFM After VNFM receives the VNF instantiation request sent by NFVO, it can send a reception response to NFVO to inform NFVO that it has successfully received the VNF information modification request.
  • the VNFM assigns the values of the M general parameters to the corresponding general parameters in the first updated VNFD according to the first assignment instruction, to obtain the second updated VNFD.
  • the VNFM may first query the instance ID of the first VNF to determine the correspondence between the instance ID of the VNF and the ID of the VNFD of the VNF, and determine the ID of the VNFD of the first VNF associated with the instance ID of the first VNF, and then according to the VNFD of the first VNF
  • the identification of the first VNF determines the VNFD of the first VNF, and then, the VNFM determines that the value source of the common parameters in the VNFD of the first VNF is the requesting user (OSS/BSS) or/and NFVO according to the first assignment instruction.
  • the VNFM sets M common parameters The value of is assigned to the corresponding general parameter in the VNFD of the first VNF, and the second updated VNFD is obtained.
  • the content carried by the VNF instantiation request includes the value of flavour, instantiation_level, the value of flavour-1, and the value of instantiation_level of level-1.
  • the value level-1 of instantiation_level is assigned to the instantiation_level in the VNFD of the first VNF.
  • the topology template in the second updated VNFD is as follows:
  • the content carried by the VNF instantiation request includes flavour, instantiation_level, vimConnectionInfo, flavour-1, instantiation_level level-1, and vimConnectionInfo 10.2.2.2.
  • the source of vimConnectionInfo is NFVO, and NFVO needs to be assigned 10.2.2.2 to vimConnectionInfo. Therefore, the VNFM assigns the value of flavour to flavour-1 in the VNFD of the first VNF, assigns the value level-1 of instantiation_level to the instantiation_level of the VNFD of the first VNF, and assigns the value 10.2.2.2 of vimConnectionInfo to the first VNF. VimConnectionInfo in the VNFD of a VNF.
  • the topology template in the second updated VNFD is as follows:
  • the VNFM can deploy the first VNF by parsing the VNFD file. Go to S214.
  • the VNFM deploys the first VNF according to the second updated VNFD.
  • the VNFM can determine whether all the input parameters in the second updated VNFD are assigned, if all the input parameters in the second updated VNFD are assigned, the first VNF is deployed according to the second updated VNFD.
  • the value of input parameters can be assigned to specific parameters using the get_input function. For example, as follows:
  • the value of networkName here is equal to the value of the input parameter public_net_id, and the VNF instantiation request will carry the value of the public_net_id parameter.
  • flavour_id is equal to the value of the input parameter flavour
  • value of the flavour parameter is carried in the VNF instantiation request.
  • value of modifiable_attributes is equal to the value of the input parameter modifiable_attributes, and the modification VNF information request will carry the value of the modifiable_attributes parameter.
  • the VNF deployment method provided in the embodiments of the present application enables the virtualization service provider to obtain the value of the modified attribute parameter from the VNF information storage space, and assign the modified attribute parameter in the VNFD, so as to assign all the input parameters in the VNFD. Successfully deployed VNF.
  • the VNFM may also obtain the VNFD after receiving the VNF instantiation request, so as to avoid storing the VNFD after only assigning values to the modified attribute parameters, thereby saving storage resource overhead.
  • Fig. 3 is a flowchart of a VNF deployment method provided by an embodiment of the application. As shown in Fig. 3, the method may include:
  • the NFVO sends a VNF creation instance identification request to the VNFM.
  • the VNFM receives an instance identification request for creating a VNF sent by NFVO.
  • the VNFM creates an instance identifier of the first VNF.
  • the VNFM creates a VNF information storage space.
  • the VNFM sends the instance identifier of the first VNF to the NFVO.
  • the NFVO receives the instance identifier of the first VNF sent by the VNFM.
  • the NFVO sends a VNF information modification request to the VNFM.
  • the VNFM receives the VNF information modification request sent by the NFVO.
  • the NFVO sends a VNF instantiation request to the VNFM.
  • the VNF instantiation request includes the instance identifier of the first VNF, M general parameters, and the value of each general parameter.
  • the instance identifier of the first VNF is notified to NFVO in advance by the VNFM.
  • the M general parameters and the value of each general parameter are parameters required to instantiate the first VNF.
  • the VNF instantiation request includes 2 general parameters and the value of each general parameter.
  • the two general parameters are flavour and instantiation_level.
  • the value of flavour is flavour-1.
  • the value of instantiation_level is level-1.
  • the value of the common parameter may be allocated by OSS/BSS for others.
  • the NFVO may also assign a suitable value to the general parameter of the VNFD whose source is NFVO, and carry it in the VNF instantiation request.
  • the source of vimConnectionInfo in the input parameter is NFVO, and NFVO needs to be assigned to vimConnectionInfo.
  • NFVO assigns a value of 10.2.2.2 to vimConnectionInfo. Therefore, the content carried in the VNF instantiation request at this time includes the values of flavour, instantiation_level, vimConnectionInfo, and flavour values of flavour-1, instantiation_level values of level-1 and vimConnectionInfo. Take the value 10.2.2.2.
  • the VNFM receives the VNF instantiation request sent by the NFVO.
  • VNFM After VNFM receives the VNF instantiation request sent by NFVO, it can send a reception response to NFVO to inform NFVO that it has successfully received the VNF information modification request.
  • the VNFM obtains the VNFD of the first VNF.
  • the VNFM may send a VNFD acquisition request to the NFVO.
  • the VNFD acquisition request includes the identification of the VNFD of the first VNF, and the identification of the VNFD of the first VNF is notified to the VNFM in advance by the NFVO.
  • the NFVO acquires the VNFD of the first VNF according to the identifier of the VNFD of the first VNF, and sends a VNFD response request to the VNFM.
  • the VNFD response request includes the VNFD of the first VNF.
  • the VNFM sends a reception response to the NFVO, so as to inform the NFVO that the VNFD of the first VNF has been successfully received.
  • the VNFD of the first VNF includes M general parameters, modified attribute parameters, M first assignment instructions and second assignment instructions.
  • a first assignment indication is used to indicate that the value of a general parameter is obtained from the virtualization service requester.
  • the M first assignment indications indicate the source of the values of the M general parameters.
  • the second assignment indication is used to indicate that the value of the modified attribute parameter is obtained from the virtualization service provider.
  • M is an integer, M ⁇ 1.
  • an example of a topology template in a VNFD of a first VNF provided in this application:
  • the first assignment indication may be "source: user".
  • the "source: user” in the general parameter "flavour” is used to indicate that the value of "flavour” is obtained from the virtualization service requester (for example, the requesting user (user)).
  • the “source: user” in the general parameter “instantiation_level” is used to instruct to obtain the value of "instantiation_level” from the virtualization service requester (such as requesting a user (user)).
  • the requesting user can be OSS/BSS.
  • the virtualization service request sends a VNF instantiation request to the virtualization service provider, and the VNF instantiation request carries the common parameters and the values of the common parameters.
  • the VNFM can obtain the value of "flavour” from the VNF instantiation request and assign the value of "flavour”.
  • the VNFM can obtain the value of "instantiation_level” from the VNF instantiation request and assign the value of "instantiation_level”.
  • the virtualization service requester may also be NFVO.
  • the first assignment indication may be "source:NFVO”.
  • an example of a topology template in a VNFD of another first VNF provided in this application:
  • the "source:NFVO" in the general parameter "vimConnectionInfo” is used to indicate to obtain the value of "vimConnectionInfo” from the virtualization service requester (NFVO).
  • the VNFM may obtain the value of "vimConnectionInfo” from the VNF instantiation request and assign the value of "vimConnectionInfo”.
  • the second assignment indication may be "source: VNFM".
  • the "source:VNFM" in the modified attribute parameter is used to instruct to obtain the value of the modified attribute parameter from the virtualization service provider (such as VNFM).
  • the VNFM may obtain the value of the modified attribute parameter from the request for modifying the VNF information.
  • first assignment indication and the second assignment indication may be set when the VNFD is designed. After receiving the VNFD, the NFVO and VNFM can determine whether to assign a value to the corresponding parameter according to the first assignment instruction and the second assignment instruction.
  • the VNFD of the first VNF may also include other information related to the deployment of the first VNF, such as VDU, CP, VL, etc.
  • VDU the deployment of the first VNF
  • CP the deployment of the first VNF
  • VL the deployment of the first VNF
  • the VNFM assigns the values of the M general parameters to the corresponding general parameters in the first updated VNFD according to the first assignment instruction, and assigns the N special parameters and the value of each special parameter according to the second assignment instruction Give the modified attribute parameters in the VNFD to obtain the first updated VNFD.
  • the VNFM parses the VNFD of the first VNF, and determines, according to the first assignment instruction, that the value source of the common parameter in the VNFD of the first VNF is the requesting user (OSS/BSS) or/and NFVO.
  • the VNFM takes the value of the M common parameters The corresponding general parameters in the VNFD assigned to the first VNF.
  • the second assignment instruction it is determined that the value source of the modified attribute parameter in the VNFD of the first VNF is the VNFM. Since the VNFM pre-stores the N dedicated parameters included in the modified attribute parameters and the value of each dedicated parameter, the VNFM obtains the N dedicated parameters and the value of each dedicated parameter from the VNF information storage space corresponding to the instance identifier of the first VNF.
  • the value of the N dedicated parameters and the value of each dedicated parameter are assigned to the modified attribute parameter in the VNFD of the first VNF to obtain the first updated VNFD.
  • the content carried by the VNF instantiation request includes the value of flavour, instantiation_level, the value of flavour-1, and the value of instantiation_level of level-1.
  • the VNFM assigns the value of flavour to the flavour in the VNFD of the first VNF, and assigns the value of level-1 of instantiation_level to the instantiation_level of the VNFD of the first VNF.
  • the modified attribute parameters stored in the VNF information storage space corresponding to the instance identifier of the first VNF include the following dedicated parameters and the values of the dedicated parameters: vcpe_image_name, public_net_id, vgw_name_0, vcpe_image_name value image123, public_net_id value 123456 ,
  • the value of vgw_name_0 is vgw123.
  • the VNFM assigns vcpe_image_name, public_net_id, vgw_name_0, vcpe_image_name values image123, public_net_id value 123456, and vgw_name_0 value vgw123 to the modified attribute parameters in the VNFD of the first VNF according to the second assignment instruction to obtain the first updated VNFD .
  • the modified attribute parameters stored in the VNF information storage space corresponding to the instance identifier of the first VNF are as follows:
  • the VNFD after the first update is as follows:
  • the vimConnectionInfo parameter is included in the VNFD.
  • the content carried in the VNF instantiation request also includes the values 10.2.2.2 of vimConnectionInfo and vimConnectionInfo.
  • the VNFM also needs to assign the value 10.2.2.2 of vimConnectionInfo to vimConnectionInfo in the VNFD of the first VNF.
  • the source of vimConnectionInfo is NFVO
  • the value of vimConnectionInfo is 10.2.2.2 when NFVO is assigned to vimConnectionInfo.
  • the VNFD after the first update is as follows:
  • the VNFM deploys the first VNF according to the first updated VNFD.
  • the VNFM can determine whether all the input parameters in the first updated VNFD are assigned. If all the input parameters in the first updated VNFD are assigned, the first VNF is deployed according to the first updated VNFD. For specific explanation, please refer to the explanation of S214, which will not be repeated.
  • the VNF deployment method provided in the embodiments of the present application enables the virtualization service provider to obtain the value of the modified attribute parameter from the VNF information storage space, and assign the modified attribute parameter in the VNFD, so as to assign all the input parameters in the VNFD. Successfully deployed VNF.
  • VNFM nodes
  • NFVO nodes
  • the VNFM and NFVO include corresponding hardware structures and/or software modules for performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the function modules of VNFM and NFVO according to the foregoing method examples.
  • each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 4 shows a schematic diagram of a possible composition of the communication device involved in the above and the embodiment, and the communication device can execute any method in the method embodiments of this application.
  • the communication device may include: a receiving unit 401, a processing unit 402, and a sending unit 403.
  • the communication device is a VNFM or a communication device that supports the VNFM to implement the method provided in the embodiment, for example, the communication device may be a chip system.
  • the receiving unit 401 is configured to support the communication device to execute the method described in the embodiment of the present application.
  • the receiving unit 401 is configured to perform or support the communication device to perform S202, S208, and S212 in the method shown in FIG. 2 and S302, S308, and S310 in the method shown in FIG. 3.
  • the processing unit 402 is configured to execute or support the communication device to execute S203, S204, S210, S213, and S214 in the method shown in FIG. 2, and S303, S304, S312, and S313 in the method shown in FIG. 3.
  • the sending unit 403 is configured to perform or support the communication device to perform S205 in the method shown in FIG. 2 and S305 in the method shown in FIG. 3.
  • the communication device When the communication device is NFVO or a communication device supporting NFVO to implement the method provided in the embodiment, for example, the communication device may be a chip system.
  • the receiving unit 401 is configured to support the communication device to execute the method described in the embodiment of the present application.
  • the receiving unit 401 is configured to perform or support the communication device to perform S206 in the method shown in FIG. 2 and S306 in the method shown in FIG. 3.
  • the sending unit 403 is configured to execute or support the communication device to execute S201, S207 and S211 in the method shown in FIG. 2 and S301, S307 and S309 in the method shown in FIG. 3.
  • the communication device provided in the embodiment of the present application is used to execute the method of any of the foregoing embodiments, and therefore can achieve the same effect as the method of the foregoing embodiment.
  • a communication device 500 provided by an embodiment of this application is used to implement the function of the VNFM in the above method.
  • the communication device 500 may be a VNFM or a device in the VNFM.
  • the communication device 500 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 500 is used to implement the function of NFVO in the above method.
  • the communication device 500 may be NFVO or a device in NFVO.
  • the communication device 500 may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication device 500 includes at least one processor 501, configured to implement the function of the VNFM or NFVO in the method provided in the embodiment of the present application.
  • the processor 501 may be configured to assign the N dedicated parameters and the value of each dedicated parameter to the modified attribute parameter in the VNFD, etc. according to the second assignment instruction. For details, refer to the detailed description in the method example, here Do not repeat it.
  • the communication device 500 may also include at least one memory 502 for storing program instructions and/or data.
  • the memory 502 and the processor 501 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 501 may cooperate with the memory 502.
  • the processor 501 may execute program instructions stored in the memory 502. At least one of the at least one memory may be included in the processor.
  • the communication device 500 may further include a communication interface 503 for communicating with other devices through a transmission medium, so that the device used in the communication device 500 can communicate with other devices.
  • a communication interface 503 for communicating with other devices through a transmission medium, so that the device used in the communication device 500 can communicate with other devices.
  • the communication device is a VNFM
  • the other equipment is an NFVO.
  • the communication device is NFVO
  • the other equipment is VNFM.
  • the processor 501 uses the communication interface 503 to send and receive data, and is used to implement the method executed by the VNFM or NFVO described in the embodiments corresponding to FIGS. 2 to 3.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 503, the processor 501, and the memory 502.
  • the communication interface 503, the processor 501, and the memory 502 are connected by a bus 504 in FIG. 5.
  • the bus is represented by a thick line in FIG. 5, and the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in FIG. 5 to represent, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or Perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), for example Random-access memory (random-access memory, RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be It can be combined or integrated into another device, or some features can be omitted or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate parts may or may not be physically separate.
  • the parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, SSD).

Landscapes

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

Abstract

本申请公开了一种虚拟网络功能VNF部署方法及装置，涉及网络功能虚拟化领域，解决了如何为VNFD中的修改属性参数赋值的问题。所述方法包括：在VNFD中，为通用参数和专用参数分别设置指示信息，指示输入参数中包括的通用参数的取值的来源和专用参数的取值的来源，在虚拟化业务提供方对通用参数和专用参数进行赋值时，根据通用参数的指示信息来获取通用参数的取值，以及根据专用参数的指示信息来获取专用参数的取值。从而，使虚拟化业务提供方能够为VNFD中的通用参数和修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。

Description

一种虚拟网络功能VNF部署方法及装置
本申请要求于2019年06月14日提交国家知识产权局、申请号为201910517265.1、申请名称为“一种虚拟网络功能VNF部署方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络功能虚拟化领域，尤其涉及一种虚拟网络功能VNF部署方法及装置。
背景技术
网络功能虚拟化(network function virtualization，NFV)技术是采用虚拟化技术将传统网络中专用设备的功能虚拟化为独立的应用，灵活地部署在基于标准的计算硬件、存储硬件和网络硬件等其他设备构建的统一基础设施平台上。在NFV系统中，发起实例化虚拟网络功能(virtual network function，VNF)请求的一方可以称为虚拟化业务请求方。接收实例化VNF请求，并根据实例化VNF请求部署VNF的一方可以称为虚拟化业务提供方。在虚拟化业务提供方接收到实例化VNF请求后，还需要获取VNF模板(VNF descriptor，VNFD)。其中，VNFD包括部署VNF所需的输入(inputs)参数，实例化VNF请求包括输入参数的取值。虚拟化业务提供方为输入参数赋值后，根据更新后的VNFD部署VNF。
由于每个VNF的需求不同，对于不同的VNF对应的VNFD包括的输入参数也不相同。为了便于将不同的VNF的输入参数统一适配到实例化VNF请求中，欧洲电信标准协会(europe telecommunications standards institute，ETSI)NFV标准中规定，将输入参数中与业务相关的专用参数统一定义为修改属性(modifiable_attributes)参数，并通过修改VNF信息(ModifyVnfInfo)请求将修改属性参数的取值告知虚拟化业务提供方。这样，实例化VNF请求包括修改属性参数和与所有VNF均相关的通用参数的取值。虽然，虚拟化业务提供方可以通过修改VNF信息请求获知修改属性参数的取值，但是，传统技术中并没有提出如何使用修改VNF信息请求包括的修改属性参数的取值对VNFD中的修改属性参数进行赋值的方案。因此，导致虚拟化业务提供方使用实例化VNF请求包括的通用参数的取值只能对VNFD中的通用参数进行赋值，VNFD中的修改属性参数未赋值，造成部署VNF失败。
发明内容
本申请提供一种虚拟网络功能VNF部署方法及装置，解决了如何为VNFD中的修改属性参数赋值的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请提供了一种VNF部署方法，该方法可应用于应用部署服务器，或者该方法可应用于可以支持应用部署服务器实现该方法的通信装置，例如该通信装置包括芯片系统。在一些实施例中，该应用部署服务器可以是VNF管理器(VNF  manager，VNFM)。所述方法包括：在接收到修改VNF信息请求之后，获取第一VNF的VNFD，并根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD，其中，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取，M为整数，M≥1；然后，在接收到VNF实例化请求之后，根据第一赋值指示将M个通用参数的取值赋予给第一更新后的VNFD中对应的通用参数，得到第二更新后的VNFD，并根据第二更新后的VNFD部署第一VNF。其中，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数。
第二方面，本申请提供了一种VNF部署方法，该方法可应用于应用部署服务器，或者该方法可应用于可以支持应用部署服务器实现该方法的通信装置，例如该通信装置包括芯片系统。在一些实施例中，该应用部署服务器可以是VNFM。所述方法包括：在接收到修改VNF信息请求和VNF实例化请求之后，获取第一VNF的VNFD，并根据第一赋值指示将M个通用参数的取值赋予给VNFD中对应的通用参数，以及根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD，以及根据第一更新后的VNFD部署第一VNF。其中，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数，M为整数，M≥1；第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取。
本申请提供的VNF部署方法，在VNFD中，为通用参数和专用参数分别设置指示信息，指示输入参数中包括的通用参数的取值的来源和专用参数的取值的来源，在应用部署服务器对通用参数和专用参数进行赋值时，能够使应用部署服务器根据第一赋值指示为VNFD中的通用参数赋值，以及根据第二赋值指示为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
在一种可能的实现方式中，虚拟化业务请求方为NFV编排器(NFV orchestrator，NFVO)或运营支持系统/业务支持系统(operation-support system/business support system，OSS/BSS)。虚拟化业务请求方可以是用户设备。虚拟化业务提供方为VNFM。虚拟化业务提供方可以是应用部署服务器。
在另一种可能的实现方式中，在接收修改VNF信息请求之前，方法还包括：在接收到NFVO发送的创建VNF的实例标识请求之后，创建第一VNF的实例标识，并建立第一VNF的实例标识和第一VNF的VNFD的标识的对应关系，并向NFVO发送第一VNF的实例标识。其中，创建VNF的实例标识请求包括第一VNF的VNFD的标识。
在另一种可能的实现方式中，获取第一VNF的VNFD，包括：向NFVO发送VNFD获取请求，VNFD获取请求包括第一VNF的VNFD的标识；接收NFVO发送的VNFD响应请求，VNFD响应请求包括第一VNF的VNFD。
在另一种可能的实现方式中，修改VNF信息请求还包括第一VNF的实例标识，VNF实例化请求还包括第一VNF的实例标识，在对VNFD中的N个通用参数和修改属性参数赋值之前，方法还包括：确定第一VNF的实例标识关联的第一VNF的VNFD的标识；以及根据第一VNF的VNFD的标识确定第一VNF的VNFD。
在另一种可能的实现方式中，创建第一VNF的实例标识之后，方法还包括：创建VNF信息存储空间，VNF信息存储空间用于存储N个专用参数和每个专用参数的取值。从而，能够使应用部署服务器从VNF信息存储空间中获取修改属性参数的取值，为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
第三方面，本申请提供了一种VNF部署方法，该方法可应用于用户设备，或者该方法可应用于可以支持用户设备实现该方法的通信装置，例如该通信装置包括芯片系统。在一些实施例中，该用户设备可以是NFVO。所述方法包括：发送修改VNF信息请求，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；发送第一VNF的VNFD，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取；发送VNF实例化请求，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数，M为整数，M≥1。
第四方面，本申请提供了一种VNF部署方法，该方法可应用于用户设备，或者该方法可应用于可以支持用户设备实现该方法的通信装置，例如该通信装置包括芯片系统。在一些实施例中，该用户设备可以是NFVO。所述方法包括：发送修改VNF信息请求，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；发送VNF实例化请求，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数，M为整数，M≥1；发送第一VNF的VNFD，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取。
本申请提供的VNF部署方法，在VNFD中，为通用参数和专用参数分别设置指示信息，指示输入参数中包括的通用参数的取值的来源和专用参数的取值的来源，在应用部署服务器对通用参数和专用参数进行赋值时，能够使应用部署服务器根据第一赋值指示为VNFD中的通用参数赋值，以及根据第二赋值指示为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
在一种可能的实现方式中，虚拟化业务请求方为NFVO或OSS/BSS。虚拟化业务请求方可以是用户设备。虚拟化业务提供方为VNFM。虚拟化业务提供方可以是应用部署服务器。
在另一种可能的实现方式中，当第一赋值指示用于指示一个通用参数的取值从NFVO获取时，在NFVO发送VNF实例化请求之前，方法还包括：NFVO设置该一个通用参数的取值。
在另一种可能的实现方式中，在发送修改VNF信息请求之前，方法还包括：发送创建VNF的实例标识请求，并接收第一VNF的实例标识，保存第一VNF的实例标识。其中，创建VNF的实例标识请求包括第一VNF的VNFD的标识。
在另一种可能的实现方式中，在发送第一VNF的VNFD之前，所述方法包括：在接收到包括第一VNF的VNFD的标识的VNFD获取请求之后，根据第一VNF的VNFD的标识获取第一VNF的VNFD，并发送VNFD响应请求，VNFD响应请求包括第一VNF的VNFD。
第五方面，本申请还提供了一种通信装置，用于实现上述第一方面或第二方面描述的方法。通信装置为应用部署服务器或支持应用部署服务器实现该第一方面或者第二方面描述的方法的通信装置，例如该通信装置包括芯片系统。例如，该通信装置包括：接收单元和处理单元。所述接收单元，用于接收修改VNF信息请求，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；所述接收单元，还用于获取第一VNF的虚拟网络功能模板VNFD，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取，M为整数，M≥1；所述处理单元，用于根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD；所述接收单元，还用于接收VNF实例化请求，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数；所述处理单元，还用于根据第一赋值指示将M个通用参数的取值赋予给第一更新后的VNFD中对应的通用参数，得到第二更新后的VNFD；所述处理单元，还用于根据第二更新后的VNFD部署第一VNF。可选地，所述处理单元，用于根据第一赋值指示将M个通用参数的取值赋予给VNFD中对应的通用参数，以及根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD；所述处理单元，还用于根据第一更新后的VNFD部署第一VNF。
可选地，通信装置还可以包括发送单元，所述发送单元，用于向NFVO发送第一VNF的实例标识。所述发送单元，还用于向NFVO发送VNFD获取请求，VNFD获取请求包括第一VNF的VNFD的标识。
第六方面，本申请还提供了一种通信装置，用于实现上述第三方面或第四方面描述的方法。通信装置为用户设备或支持用户设备实现该第三方面或第四方面描述的方法的通信装置，例如该通信装置包括芯片系统。例如，通信装置包括：发送单元。所 述发送单元，用于发送修改VNF信息请求，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；所述发送单元，还用于发送第一VNF的虚拟网络功能模板VNFD，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取；所述发送单元，还用于发送VNF实例化请求，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数，M为整数，M≥1。
可选地，通信装置还可以包括处理单元，用于设置通用参数的取值。
本申请提供的通信装置，在VNFD中，为通用参数和专用参数分别设置指示信息，指示输入参数中包括的通用参数的取值的来源和专用参数的取值的来源，在对通用参数和专用参数进行赋值时，能够使通信装置根据第一赋值指示为VNFD中的通用参数赋值，以及根据第二赋值指示为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
在一种可能的实现方式中，虚拟化业务请求方为NFVO或OSS/BSS。虚拟化业务请求方可以是用户设备。虚拟化业务提供方为VNFM。虚拟化业务提供方可以是应用部署服务器。
需要说明的是，上述第五方面和第六方面的功能模块可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，收发器，用于完成接收单元和发送单元的功能，处理器，用于完成处理单元的功能，存储器，用于处理器处理本申请的方法的程序指令。处理器、收发器和存储器通过总线连接并完成相互间的通信。具体的，可以参考第一方面所述的方法至第四方面所述的方法中的应用部署服务器或用户设备的行为的功能。
第七方面，本申请还提供了一种通信装置，用于实现上述第一方面或第二方面描述的方法。所述通信装置为应用部署服务器或支持应用部署服务器实现该第一方面或第二方面描述的方法的通信装置，例如该通信装置包括芯片系统。例如所述通信装置包括处理器，用于实现上述第一方面或第二方面描述的方法中的功能。所述通信装置还可以包括存储器，用于存储程序指令和数据。所述存储器与所述处理器耦合，所述处理器可以调用并执行所述存储器中存储的程序指令，用于实现上述第一方面或第二方面描述的方法中的功能。所述通信装置还可以包括通信接口，所述通信接口用于该通信装置与其它设备进行通信。示例性地，若所述通信装置为应用部署服务器，该其它设备为用户设备。
在一种可能的设备中，该通信接口可以是收发器。处理器，用于根据第一赋值指示将M个通用参数的取值赋予给VNFD中对应的通用参数，以及根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD；以及根据第一更新后的VNFD部署第一VNF。
第八方面，本申请还提供了一种通信装置，用于实现上述第三方面或第四方面描述的方法。所述通信装置为用户设备或支持用户设备实现该第三方面或第四方面描述 的方法的通信装置，例如该通信装置包括芯片系统。例如所述通信装置包括处理器，用于实现上述第三方面或第四方面描述的方法中的功能。所述通信装置还可以包括存储器，用于存储程序指令和数据。所述存储器与所述处理器耦合，所述处理器可以调用并执行所述存储器中存储的程序指令，用于实现上述第三方面或第四方面描述的方法中的功能。所述通信装置还可以包括通信接口，所述通信接口用于该通信装置与其它设备进行通信。示例性地，若所述通信装置为用户设备，该其它设备为应用部署服务器。
在一种可能的设备中，该通信接口可以是收发器。收发器，用于发送修改VNF信息请求，修改VNF信息请求包括修改属性参数，修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；发送VNF实例化请求，VNF实例化请求包括M个通用参数和每个通用参数的取值，M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数，M为整数，M≥1；发送第一VNF的VNFD，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取。
第九方面，本申请还提供了一种计算机可读存储介质，包括：计算机软件指令；当计算机软件指令在通信装置中运行时，使得通信装置执行上述第一方面至第四方面中任一方面所述的方法。
第十方面，本申请还提供了一种包含指令的计算机程序产品，当计算机程序产品在通信装置中运行时，使得通信装置执行上述第一方面至第四方面中任一方面所述的方法。
第十一方面，本申请提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述方法中应用部署服务器或用户设备的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十二方面，本申请还提供了一种通信系统，所述通信系统包括第五方面描述的应用部署服务器或支持应用部署服务器实现该第一方面描述的方法的通信装置，以及第六方面描述的用户设备或支持用户设备实现该第三方面描述的方法的通信装置；
或所述通信系统包括第五方面描述的应用部署服务器或支持应用部署服务器实现该第二方面描述的方法的通信装置，以及第六方面描述的用户设备或支持用户设备实现该第四方面描述的方法的通信装置；
或所述通信系统包括第七方面描述的应用部署服务器或支持应用部署服务器实现该第一方面描述的方法的通信装置，以及第八方面描述的用户设备或支持用户设备实现该第三方面描述的方法的通信装置；
或所述通信系统包括第七方面描述的应用部署服务器或支持应用部署服务器实现该第二方面描述的方法的通信装置，以及第八方面描述的用户设备或支持用户设备实现该第四方面描述的方法的通信装置。
另外，上述任意方面的设计方式所带来的技术效果可参见第一方面和第四方面中不同设计方式所带来的技术效果，此处不再赘述。
本申请中，应用部署服务器、用户设备和通信装置的名字对设备本身不构成限定，在实际实现中，这些设备可以以其他名称出现。只要各个设备的功能和本申请类似，属于本申请权利要求及其等同技术的范围之内。
附图说明
图1为本申请实施例提供的一种NFV系统架构示例图；
图2为本申请提供的一种VNF部署方法的流程图；
图3为本申请提供的另一种VNF部署方法的流程图；
图4为本申请提供的一种通信装置的组成示意图；
图5为本申请提供的另一种通信装置的组成示意图。
具体实施方式
本申请说明书和权利要求书及上述附图中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了下述各实施例的描述清楚简洁，首先给出相关技术的简要介绍：
传统的电信系统是通过各种专用的硬件设备组成，不同的功能采用不同的硬件设备。随着网络规模的增长，电信系统越来越复杂，带来了诸多的挑战。例如，新增业务的开发上线、系统的运维和资源利用率等。为了应对这些挑战及利用互联网(internet technology，IT)业界的虚拟化技术及云计算技术，在2012年10月22日召开的“软件定义网络和开放流世界会议(software defined network and openflow world congress，SDN and OF world congress)”上，全球主要的13个电信运营商联合发布了网络功能虚拟化(network function virtualization，NFV)白皮书，并宣布在欧洲电信标准协会(europe telecommunications standards institute，ETSI)成立NFV行业规范组(industry specific group，ISG)，制定NFV的需求及技术框架，推动NFV的发展。
NFV技术利用虚拟化技术对基础设施硬件设备(如计算设备、存储设备、网络设备)资源池化及虚拟化，对上层应用提供虚拟资源，实现软件和硬件解耦。开发新业务时，不需要单独部署硬件设备，只需要采用虚拟化技术将业务虚拟化为独立的应用(如VNF)，从而，大大缩短新业务上线时间，且使得虚拟资源供给速度大大增加。
NFV技术利用云计算技术，可以实现应用的弹性伸缩，实现虚拟资源与业务负荷相匹配，不仅提升了虚拟资源的利用效率，而且改善了NFV系统的响应速率。
图1为本申请实施例提供的一种NFV系统架构示例图。NFV系统可以在各种网络中使用，例如在一个数据中心网络、运营商网络或局域网来实现。NFV系统包括一个NFV管理和编排系统(NFV management and orchestration，NFV MANO)101、NFV基础设施层(NFV infrastructure，NFVI)102、多个虚拟网络功能(Virtual Network Function，VNF)103、多个网元管理(element management，EM)104和运营支持系统/业务支持系统(operation-support system/business support system，OSS/BSS)105。
其中，NFV MANO 101用于执行对NFVI 102和VNF 103的监视和管理。NFV管 理和编排系统101包括NFV编排器(NFV orchestrator，NFVO)1011，一个或多个VNF管理器(VNF manager，VNFM)1012和虚拟化基础设施管理器(virtualized infrastructure manager，VIM)1013。
NFVO 1011主要负责处理虚拟化业务的生命周期管理、虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO 1011也可以执行来自一个或多个VNFM 1012的资源相关请求(如：请求获取VNFD)，发送配置信息(如：VNFD、修改VNF信息请求和VNF实例化请求)到VNFM 1012，并收集VNF 103的状态信息。VNFD可以存储在NFVO上，也可以存储在NFVO所管理的数据库，以便NFVO可以获取到VNFD，将VNFD反馈给VNFM，VNFM根据VNFD部署VNF。NFVO可以存储多种功能的VNF的VNFD。另外，NFVO 1011可以与VIM 1013通信，以实现资源的分配和/或预留以及交换虚拟化硬件资源的配置和状态信息。
VNFM 1012主要负责一个或多个VNF 103的生命周期管理。比如，实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF 103等。VNFM 1012可以与VNF 103通信以完成VNF 103生命周期管理及交换配置和状态信息。在NFV系统中VNFM 1012可以有多个，负责对不同类型的VNF进行生命周期管理。
VIM 1013可以执行资源管理的功能，例如管理基础设施资源的分配(例如增加资源到虚拟容器)和操作功能(如收集NFVI故障信息)。VNFM 1012和VIM 1013可以相互通信进行资源分配和交换虚拟化硬件资源的配置和状态信息。例如，控制和管理VNF 103与计算硬件1021，存储硬件1022，网络硬件1023，虚拟计算(virtual computing)1024，虚拟存储1025，虚拟网络1026的交互。
NFVI 102包括硬件资源层、虚拟化层(virtualization layer)和虚拟资源层。NFVI102包括的硬件资源、软件资源或两者的组合来完成虚拟化环境的部署。换句话说，硬件资源和虚拟化层用于提供虚拟化的资源，例如作为虚拟机和其它形式的虚拟容器，用于VNF 103。硬件资源层包括计算硬件1021、存储硬件1022和网络硬件1023。计算硬件1021可以是市场上现成的硬件和/或用户定制的硬件，用来提供处理和计算资源。存储硬件1022可以是网络内提供的存储容量或驻留在存储硬件1022本身的存储容量(位于服务器内的本地存储器)。在一个实现方案中，计算硬件1021和存储硬件1022的资源可以被集中在一起。网络硬件1023可以是交换机、路由器和/或配置成具有交换功能的任何其他网络设备。网络硬件1023可以横跨多个域，并且可以包括多个由一个或一个以上传输网络互连的网络。NFVI 102里面的虚拟化层可以从物理层抽象硬件资源和解耦VNF 103，以便向VNF 103提供虚拟化资源。虚拟资源层包括虚拟计算1024、虚拟存储1025和虚拟网络1026。虚拟计算1024和虚拟存储1025可以以虚拟机、和/或其他虚拟容器的形式提供给VNF 103。例如，一个或一个以上的VNF 103可以部署在一个虚拟机(virtual machine，VM)上。虚拟化层抽象网络硬件1023，从而形成虚拟网络1026，虚拟网络1026可以包括虚拟交换机(virtual switch)，虚拟交换机用来提供虚拟机和其他虚拟机之间的连接。此外，网络硬件1023中的传输网络，可以采用集中式控制平面和一个单独的转发平面(如软件定义网络)虚拟化。
硬件上，计算硬件1021、存储硬件1022和网络硬件1023可能包含多个机框，或 多个机架，甚至多个机房。软件上，可能存在一个VIM 1013，也可能存在多个VIM，分别管理不同的硬件资源。
VNF 103可以被配置为通过一个物理网络设备执行的至少一个网络功能的虚拟化。
设备管理系统(EM)104是传统网络中用于对设备进行配置，管理的系统，在NFV系统中，EM 104也可以用于对VNF 103进行配置和管理，以及向VNFM 1012发起新的VNF 103的实例化等生命周期管理操作。
运营支持系统和业务支持系统(Operations Support System and Business Support System，OSS/BSS)105，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
在NFV系统中，虚拟化的网络服务(Network Service，NS)可以是一个IP多媒体子系统(IP multimedia subsystem，IMS)网络服务，或者，是一个下一代移动核心网络(Evolved Packet Core，EPC)网络服务等。一个NS中可以包含若干个VNF。在对一个NS进行虚拟化部署时，虚拟化业务提供方需要从虚拟化业务请求方获取该业务的描述信息，即网络服务模板(Network Service descriptor，NSD)。NSD主要描述了该业务的拓扑结构信息以及包含的每个VNF的描述信息，即VNF模板(VNF descriptor，VNFD)。在拓扑结构信息中，可以使用虚拟化连接模板(virtual link descriptor，VLD)来描述VNF之间的连接。VNFD包含虚拟部署单元(Virtualisation Deployment Unit，VDU)、连接点(connection point，CP)、虚拟连接(virtual link，VL)等信息。VDU可以代表一个安装了应用软件的虚拟机，在VDU的描述中会包含对该虚拟机的所有虚拟资源的需求描述。CP代表虚拟机上的连接信息，比如可以是虚拟网卡信息，可以采用IP地址或MAC地址来表示。VL是VNF内连接多个VDU的虚拟连接，可以用连接类型，带宽等信息来表示。
在本申请中，可以采用云计算应用的拓扑和运维流程(Topology and Orchestration Specification for Cloud Applications，TOSCA)描述VNFD。TOSCA是开源标准组织(Advancing Open Standards for the Information Society，OASIS)制定的描述规范。
在一些实施例中，部署一个应用所需的信息可以在应用部署包中描述。应用部署包至少包含一个后缀为ste的应用部署描述文件，该*.ste的应用部署描述文件可以用XML语言描述应用的部署信息，该*.ste的应用部署描述文件的根元素为应用模板(Service Template)。也就是说本申请实施例中可以用应用模板来完整描述需部署的应用的信息。*.ste的应用部署描述文件的子元素包括拓扑模板(TopologyTemplate)、节点类型(NodeType)、节点模板(NodeTemplate)、关系类型(RelationshipType)、关系模板(RelationshipTemplate)、边界定义(BoundaryDefinitions)等。
示例的，传统技术定义的VNFD中的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000001
Figure PCTCN2020095804-appb-000002
从上述VNFD中可知，定义了一个vCPE业务的部署模板。其中，拓扑模板中，在inputs中定义的输入参数(如：vcpe_image_name、public_net_id和vgw_name_0)是属于动态参数。这些输入参数的取值只有在部署是才能确定，如可以在实例化VNF请求中携带。
但是，由于每个VNF的需求不同，对于不同的VNF对应的VNFD包括的输入参数也不相同。为了便于将不同的VNF的输入参数统一适配到实例化VNF请求中，ETSI NFV标准中规定，将输入参数中与业务相关的专用参数统一定义为修改属性(modifiable_attributes)参数。可理解的，所谓专用参数为与业务相关的参数。对于不同的业务，专用参数可以完全不同，也可以部分不同。因此，输入参数包括与所有VNF均相关的通用参数和修改属性参数。
示例的，传统技术定义的VNFD中的统一定义的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000003
从上述统一定义的拓扑模板可知，flavour和instantiation_level为通用参数。通用参数的取值可以在实例化VNF请求中携带，由虚拟化业务请求方通知给虚拟化业务提供方。这样，实例化VNF请求中只需要携带通用参数的取值和修改属性参数即可。由于每个VNF的需求不同，可以根据不同的VNF的需要，对修改属性参数进行扩展，修改属性参数包括与业务相关的专用参数，例如，上述示例中的vcpe_image_name、public_net_id和vgw_name_0。可以利用修改VNF信息请求对专用参数进行赋值或修改，由虚拟化业务请求方通知给虚拟化业务提供方。
虽然，虚拟化业务提供方可以通过修改VNF信息请求获知修改属性参数的取值，但是，传统技术中并没有提出如何使用修改VNF信息请求包括的修改属性参数的取值对VNFD中的修改属性参数进行赋值的方案。因此，导致虚拟化业务提供方使用实例化VNF请求包括的通用参数的取值只能对VNFD中的通用参数进行赋值，VNFD中的修改属性参数未赋值，造成部署VNF失败。
本申请实施例提供一种VNF部署方法，该方法包括：在VNFD中，为通用参数和专用参数分别设置指示信息，指示输入参数中包括的通用参数的取值的来源和专用参数的取值的来源，在虚拟化业务提供方对通用参数和专用参数进行赋值时，根据通用参数的指示信息来获取通用参数的取值，以及根据专用参数的指示信息来获取专用参数的取值。从而，使虚拟化业务提供方能够为VNFD中的通用参数和修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
在本申请中，虚拟化业务请求方可以是用户设备。例如，虚拟化业务请求方可以为NFVO或OSS/BSS。虚拟化业务提供方可以是应用部署服务器。例如，虚拟化业务提供方可以为VNFM。
下面以虚拟化业务请求方为NFVO，虚拟化业务提供方为VNFM为例，结合附图对本申请实施例的实施方式进行详细描述。
图2为本申请实施例提供的一种VNF部署方法的流程图，如图2所示，该方法可以包括：
S201、NFVO向VNFM发送创建VNF的实例标识请求。
创建VNF的实例标识请求用于请求为一个需要部署的VNF创建一个实例标识。
S202、VNFM接收NFVO发送的创建VNF的实例标识请求。
VNFM接收到NFVO发送的创建VNF的实例标识请求后，可以向NFVO发送一个接收响应，以便于告知NFVO已成功接收到创建VNF的实例标识请求。另外，VNFM执行S203和S204。
S203、VNFM创建第一VNF的实例标识。
VNFM接收到NFVO发送的创建VNF的实例标识请求后，创建第一VNF的实例标识。该创建VNF的实例标识请求包括第一VNF的VNFD的标识。VNFM还可以建立第一VNF的实例标识和第一VNF的VNFD的标识的对应关系。
S204、VNFM创建VNF信息存储空间。
VNF信息存储空间用于存储部署VNF的相关信息。部署VNF的相关信息可以包括VNF的输入参数(如通过参数和修改属性参数)、VLD、VDU、CP、VL等。在本申请中，可以创建一个第一VNF的实例标识对应的VNF信息存储空间，用于存储部署第一VNF的相关信息。
S205、VNFM向NFVO发送第一VNF的实例标识。
需要说明的是，本申请实施例提供的VNF部署方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，示例的，如S204～S205之间的前后顺序可以互换，即执行S205，再执行S204，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本申请的保护范围之内，因此不再赘述。
S206、NFVO接收VNFM发送的第一VNF的实例标识。
NFVO接收到VNFM发送的第一VNF的实例标识后，存储第一VNF的实例标识，可以向VNFM发送一个接收响应，以便于告知VNFM已成功接收到第一VNF的实例标识。
S207、NFVO向VNFM发送修改VNF信息请求。
修改VNF信息请求包括修改属性参数。修改属性参数包含N个专用参数和每个专用参数的取值，N个专用参数和每个专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1。
示例的，本申请提供的一种修改属性参数的描述示例：
Figure PCTCN2020095804-appb-000004
其中，修改属性参数包括3个专用参数和每个专用参数的取值。3个专用参数分别为vcpe_image_name、public_net_id和vgw_name_0。vcpe_image_name的取值为image123。public_net_id的取值为123456。vgw_name_0的取值为vgw123。
进一步的，修改VNF信息请求还包括第一VNF的实例标识，以便于VNFM根据第一VNF的实例标识将N个专用参数和每个专用参数的取值存储到第一VNF的实例标识对应的VNF信息存储空间。第一VNF的实例标识是VNFM预先告知给NFVO的。
S208、VNFM接收NFVO发送的修改VNF信息请求。
VNFM接收到NFVO发送的修改VNF信息请求后，可以将修改属性参数包含的N个专用参数和每个专用参数的取值存储到第一VNF的实例标识对应的VNF信息存储空间。同时，VNFM可以向NFVO发送一个接收响应，以便于告知NFVO已成功接收到修改VNF信息请求。
S209、VNFM获取第一VNF的VNFD。
在一些实施例中，VNFM可以向NFVO发送VNFD获取请求，VNFD获取请求包括第一VNF的VNFD的标识，第一VNF的VNFD的标识是NFVO预先告知VNFM的。NFVO存储有不同功能的VNF的VNFD，在NFVO接收到VNFD获取请求后，NFVO可以根据第一VNF的VNFD的标识获取第一VNF的VNFD，并向VNFM发送VNFD响应请求，该VNFD响应请求包括第一VNF的VNFD。VNFM获取到第一VNF的VNFD之后，向NFVO发送一个接收响应，以便于告知NFVO已成功接收到第一VNF的VNFD。
具体的，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示。一个第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取。M个第一赋值指示指示了M个通用参数的取值的来源。第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取。M为整数，M≥1。
示例的，本申请提供的一种第一VNF的VNFD中的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000005
Figure PCTCN2020095804-appb-000006
从该VNFD中的拓扑模板可知，在修改属性参数和每个通用参数下新增了“source”字段，用于指示输入参数的取值的来源。
例如，第一赋值指示可以是“source:user”。通用参数“flavour”中的“source:user”用于指示从虚拟化业务请求方(如：请求用户(user))获取“flavour”的取值。通用参数“instantiation_level”中的“source:user”用于指示从虚拟化业务请求方(如：请求用户(user))获取“instantiation_level”的取值。请求用户可以是OSS/BSS。在一些设计中，虚拟化业务请求方向虚拟化业务提供方发送VNF实例化请求，该VNF实例化请求中携带有通用参数和通用参数的取值。在本实施例中，VNFM可以从VNF实例化请求中获取“flavour”的取值为“flavour”赋值。VNFM可以从VNF实例化请求中获取“instantiation_level”的取值为“instantiation_level”赋值。
又例如，虚拟化业务请求方还可以是NFVO。第一赋值指示可以是“source:NFVO”。
示例的，本申请提供的另一种第一VNF的VNFD中的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000007
其中，通用参数“vimConnectionInfo”中的“source:NFVO”用于指示从虚拟化业务请求方(NFVO)获取“vimConnectionInfo”的取值。在本实施例中，VNFM可以从VNF实例化请求中获取“vimConnectionInfo”的取值为vimConnectionInfo赋值。
第二赋值指示可以是“source:VNFM”。修改属性参数中的“source:VNFM”用于指示从虚拟化业务提供方(如：VNFM)获取修改属性参数的取值。VNFM可以从修改VNF信息请求中获取修改属性参数的取值为修改属性参数赋值。
需要说明的是，第一赋值指示和第二赋值指示可以是在设计VNFD的时候设置的。NFVO和VNFM收到VNFD后，可以根据第一赋值指示和第二赋值指示来判断是否需要给对应的参数赋值。
另外，第一VNF的VNFD还可以包括与第一VNF部署相关的其他信息，如VDU、CP、VL等，具体解释可以参考现有技术，本申请对此不作限定。
S210、VNFM根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD。
VNFM获取到第一VNF的VNFD之后，解析第一VNF的VNFD，根据第一赋值指示确定第一VNF的VNFD中的通用参数的取值来源是NFVO或OSS/BSS，此时，VNFM还未获取到通用参数的取值，因此，无法未通用参数赋值，无需更新第一VNF的VNFD。进一步的，根据第二赋值指示确定第一VNF的VNFD中的修改属性参数的取值来源是VNFM。由于VNFM预先存储了修改属性参数包括的N个专用参数和每个专用参数的取值，VNFM从第一VNF的实例标识对应的VNF信息存储空间中获取N个专用参数和每个专用参数的取值，并将N个专用参数和每个专用参数的取值赋予给第一VNF的VNFD中的修改属性参数，得到第一更新后的VNFD。
示例的，假设第一VNF的实例标识对应的VNF信息存储空间中存储的修改属性参数包括以下专用参数和专用参数的取值：vcpe_image_name、public_net_id、vgw_name_0、vcpe_image_name的取值image123、public_net_id的取值123456、vgw_name_0的取值vgw123。VNFM根据第二赋值指示将vcpe_image_name、public_net_id、vgw_name_0、vcpe_image_name的取值image123、public_net_id的取值123456、vgw_name_0的取值vgw123赋予给第一VNF的VNFD中的修改属性参数，得到第一更新后的VNFD。保存在第一VNF的实例标识对应的VNF信息存储空间中的修改属性参数如下所示：
Figure PCTCN2020095804-appb-000008
第一更新后的VNFD如下所示：
Figure PCTCN2020095804-appb-000009
Figure PCTCN2020095804-appb-000010
需要说明的是，VNFM可以判断第一更新后的VNFD中的输入参数是否全部赋值完成，若第一更新后的VNFD中的输入参数未全部赋值，VNFM先保存第一更新后的VNFD。可选的，在本申请中，VNFM也可以将对修改属性参数赋值后的VNFD文件转换成其他任何适合机器处理的文件，比如JSON，XML等格式进行保存，本申请对此不作限定。
S211、NFVO向VNFM发送VNF实例化请求。
VNF实例化请求包括第一VNF的实例标识、M个通用参数和每个通用参数的取值。第一VNF的实例标识是VNFM预先告知给NFVO的。M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数。
示例的，VNF实例化请求包括2个通用参数和每个通用参数的取值。2个通用参数分别可以为flavour和instantiation_level。flavour的取值为flavour-1。instantiation_level的取值为level-1。
在一些实施例中，通用参数的取值可以是OSS/BSS为其分配的。
在另一些实施例中，在NFVO向VNFM发送VNF实例化请求之前，NFVO还可以为VNFD中source为NFVO的通用参数分配合适的取值，并携带在VNF实例化请求中。
例如，输入参数中的vimConnectionInfo的source为NFVO，NFVO需要为vimConnectionInfo赋值。比如，NFVO给vimConnectionInfo赋予的取值为10.2.2.2，因此，此时VNF实例化请求携带的内容包括flavour、instantiation_level、vimConnectionInfo、flavour的取值flavour-1、instantiation_level的取值level-1和vimConnectionInfo的取值10.2.2.2。
S212、VNFM接收NFVO发送的VNF实例化请求。
VNFM接收到NFVO发送的VNF实例化请求后，可以向NFVO发送一个接收响应，以便于告知NFVO已成功接收到修改VNF信息请求。
S213、VNFM根据第一赋值指示将M个通用参数的取值赋予给第一更新后的VNFD中对应的通用参数，得到第二更新后的VNFD。
VNFM可以先根据第一VNF的实例标识查询确定VNF的实例标识与VNF的VNFD的标识的对应关系，确定第一VNF的实例标识关联的第一VNF的VNFD的标识，再根据第一VNF的VNFD的标识确定第一VNF的VNFD，然后，VNFM根据第一赋值指示确定第一VNF的VNFD中的通用参数的取值来源是请求用户(OSS/BSS)或/和NFVO，VNFM将M个通用参数的取值赋予给第一VNF的VNFD中对应的通用参数，得到第二更新后的VNFD。
例如，VNF实例化请求携带的内容包括flavour、instantiation_level、flavour的取值flavour-1和instantiation_level的取值level-1。
将flavour的取值flavour-1赋予给第一VNF的VNFD中flavour。instantiation_level 的取值level-1赋予给第一VNF的VNFD中instantiation_level。第二更新后的VNFD中的拓扑模板如下所示：
Figure PCTCN2020095804-appb-000011
又例如，VNF实例化请求携带的内容包括flavour、instantiation_level、vimConnectionInfo、flavour的取值flavour-1、instantiation_level的取值level-1和vimConnectionInfo的取值10.2.2.2。
其中，vimConnectionInfo的source为NFVO，NFVO需要为vimConnectionInfo赋予10.2.2.2。因此，VNFM将flavour的取值flavour-1赋予给第一VNF的VNFD中flavour，将instantiation_level的取值level-1赋予给第一VNF的VNFD中instantiation_level，将vimConnectionInfo的取值10.2.2.2赋予给第一VNF的VNFD中vimConnectionInfo。第二更新后的VNFD中的拓扑模板如下所示：
Figure PCTCN2020095804-appb-000012
此时，便完成了对第一VNF的VNFD中所有输入参数的赋值，VNFM可以通过解析该VNFD文件部署该第一VNF。执行S214。
S214、VNFM根据第二更新后的VNFD部署第一VNF。
VNFM可以判断第二更新后的VNFD中的输入参数是否全部赋值完成，若第二更新后的VNFD中的输入参数全部赋值完成，根据第二更新后的VNFD部署第一VNF。
需要说明的是，在部署第一VNF时，可以利用get_input函数将输入参数(inputs)的取值赋给具体的参数。示例的，如下所示：
Figure PCTCN2020095804-appb-000013
Figure PCTCN2020095804-appb-000014
其中，这里networkName的值就等于输入参数public_net_id的取值，在VNF实例化请求会携带public_net_id参数的取值。
又例如，如下所示：
Figure PCTCN2020095804-appb-000015
其中，flavour_id的值就等于输入参数flavour的取值，在VNF实例化请求会携带flavour参数的取值。modifiable_attributes的值就等于输入参数modifiable_attributes的取值，在修改VNF信息请求会携带modifiable_attributes参数的取值。
关于部署VNF的其他相关步骤，可以参考现有技术的描述，本申请不予赘述。
本申请实施例提供的VNF部署方法，能够使虚拟化业务提供方从VNF信息存储空间中获取修改属性参数的取值，为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
在另一些实施例中，VNFM也可以在接收到VNF实例化请求之后，再获取VNFD，避免存储仅对修改属性参数赋值后的VNFD，从而，节省存储资源的开销。
图3为本申请实施例提供的一种VNF部署方法的流程图，如图3所示，该方法可以包括：
S301、NFVO向VNFM发送创建VNF的实例标识请求。
S302、VNFM接收NFVO发送的创建VNF的实例标识请求。
S303、VNFM创建第一VNF的实例标识。
S304、VNFM创建VNF信息存储空间。
S305、VNFM向NFVO发送第一VNF的实例标识。
S306、NFVO接收VNFM发送的第一VNF的实例标识。
S307、NFVO向VNFM发送修改VNF信息请求。
S308、VNFM接收NFVO发送的修改VNF信息请求。
关于S301～S308的解释可以参考S201～S208的阐述，不予赘述。
S309、NFVO向VNFM发送VNF实例化请求。
VNF实例化请求包括第一VNF的实例标识、M个通用参数和每个通用参数的取值。第一VNF的实例标识是VNFM预先告知给NFVO的。M个通用参数和每个通用参数的取值为实例化第一VNF所需的参数。
示例的，VNF实例化请求包括2个通用参数和每个通用参数的取值。2个通用参数分别为flavour和instantiation_level。flavour的取值为flavour-1。instantiation_level的取值为level-1。
在一些实施例中，通用参数的取值可以是OSS/BSS为其他分配的。
在另一些实施例中，在NFVO向VNFM发送VNF实例化请求之前，NFVO还可以为VNFD中source为NFVO的通用参数分配合适的取值，并携带在VNF实例化请求中。
例如，输入参数中的vimConnectionInfo的source为NFVO，NFVO需要为vimConnectionInfo赋值。比如，NFVO给vimConnectionInfo赋予的取值为10.2.2.2，因此，此时VNF实例化请求携带的内容包括flavour、instantiation_level、vimConnectionInfo、flavour的取值flavour-1、instantiation_level的取值level-1和vimConnectionInfo的取值10.2.2.2。
S310、VNFM接收NFVO发送的VNF实例化请求。
VNFM接收到NFVO发送的VNF实例化请求后，可以向NFVO发送一个接收响应，以便于告知NFVO已成功接收到修改VNF信息请求。
S311、VNFM获取第一VNF的VNFD。
在一些实施例中，VNFM可以向NFVO发送VNFD获取请求，VNFD获取请求包括第一VNF的VNFD的标识，第一VNF的VNFD的标识是NFVO预先告知VNFM的。NFVO接收到VNFD获取请求后，NFVO根据第一VNF的VNFD的标识获取第一VNF的VNFD，并向VNFM发送VNFD响应请求，该VNFD响应请求包括第一VNF的VNFD。VNFM获取到第一VNF的VNFD之后，向NFVO发送一个接收响应，以便于告知NFVO已成功接收到第一VNF的VNFD。
具体的，第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和第二赋值指示。一个第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取。M个第一赋值指示指示了M个通用参数的取值的来源。第二赋值指示用于指示修改属性参数的取值从虚拟化业务提供方获取。M为整数，M≥1。
示例的，本申请提供的一种第一VNF的VNFD中的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000016
从该VNFD中的拓扑模板可知，在修改属性参数和每个通用参数下新增了“source”字段，用于指示输入参数的取值的来源。
例如，第一赋值指示可以是“source:user”。通用参数“flavour”中的“source:user”用于指示从虚拟化业务请求方(如：请求用户(user))获取“flavour”的取值。通用参数“instantiation_level”中的“source:user”用于指示从虚拟化业务请求方(如：请 求用户(user))获取“instantiation_level”的取值。请求用户可以是OSS/BSS。在一些设计中，虚拟化业务请求方向虚拟化业务提供方发送VNF实例化请求，该VNF实例化请求中携带有通用参数和通用参数的取值。在本实施例中，VNFM可以从VNF实例化请求中获取“flavour”的取值为“flavour”赋值。VNFM可以从VNF实例化请求中获取“instantiation_level”的取值为“instantiation_level”赋值。
又例如，虚拟化业务请求方还可以是NFVO。第一赋值指示可以是“source:NFVO”。
示例的，本申请提供的另一种第一VNF的VNFD中的拓扑模板的一个示例：
Figure PCTCN2020095804-appb-000017
其中，通用参数“vimConnectionInfo”中的“source:NFVO”用于指示从虚拟化业务请求方(NFVO)获取“vimConnectionInfo”的取值。在本实施例中，VNFM可以从VNF实例化请求中获取“vimConnectionInfo”的取值为“vimConnectionInfo”赋值。
第二赋值指示可以是“source:VNFM”。修改属性参数中的“source:VNFM”用于指示从虚拟化业务提供方(如：VNFM)获取修改属性参数的取值。VNFM可以从修改VNF信息请求中获取修改属性参数的取值为修改属性参数赋值。
需要说明的是，第一赋值指示和第二赋值指示可以是在设计VNFD的时候设置的。NFVO和VNFM收到VNFD后，可以根据第一赋值指示和第二赋值指示来判断是否需要给对应的参数赋值。
另外，第一VNF的VNFD还可以包括与第一VNF部署相关的其他信息，如VDU、CP、VL等，具体解释可以参考现有技术，本申请对此不作限定。
S312、VNFM根据第一赋值指示将M个通用参数的取值赋予给第一更新后的VNFD中对应的通用参数，并根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数，得到第一更新后的VNFD。
VNFM解析第一VNF的VNFD，并根据第一赋值指示确定第一VNF的VNFD中的通用参数的取值来源是请求用户(OSS/BSS)或/和NFVO，VNFM将M个通用参数 的取值赋予给第一VNF的VNFD中对应的通用参数。根据第二赋值指示确定第一VNF的VNFD中的修改属性参数的取值来源是VNFM。由于VNFM预先存储了修改属性参数包括的N个专用参数和每个专用参数的取值，VNFM从第一VNF的实例标识对应的VNF信息存储空间中获取N个专用参数和每个专用参数的取值，并将N个专用参数和每个专用参数的取值赋予给第一VNF的VNFD中的修改属性参数，得到第一更新后的VNFD。
例如，VNF实例化请求携带的内容包括flavour、instantiation_level、flavour的取值flavour-1和instantiation_level的取值level-1。VNFM将flavour的取值flavour-1赋予给第一VNF的VNFD中flavour，以及将instantiation_level的取值level-1赋予给第一VNF的VNFD中instantiation_level。
进一步的，假设第一VNF的实例标识对应的VNF信息存储空间中存储的修改属性参数包括以下专用参数和专用参数的取值：vcpe_image_name、public_net_id、vgw_name_0、vcpe_image_name的取值image123、public_net_id的取值123456、vgw_name_0的取值vgw123。VNFM根据第二赋值指示将vcpe_image_name、public_net_id、vgw_name_0、vcpe_image_name的取值image123、public_net_id的取值123456、vgw_name_0的取值vgw123赋予给第一VNF的VNFD中的修改属性参数，得到第一更新后的VNFD。保存在第一VNF的实例标识对应的VNF信息存储空间中的修改属性参数如下所示：
Figure PCTCN2020095804-appb-000018
第一更新后的VNFD如下所示：
Figure PCTCN2020095804-appb-000019
在一些实施例中，VNFD中包括vimConnectionInfo参数。VNF实例化请求携带的内容还包括vimConnectionInfo和vimConnectionInfo的取值10.2.2.2。VNFM还需要将vimConnectionInfo的取值10.2.2.2赋予给第一VNF的VNFD中vimConnectionInfo。其中，vimConnectionInfo的source为NFVO，vimConnectionInfo的取值10.2.2.2时NFVO赋予给vimConnectionInfo的。
第一更新后的VNFD如下所示：
Figure PCTCN2020095804-appb-000020
Figure PCTCN2020095804-appb-000021
此时，便完成了对第一VNF的VNFD中所有输入参数的赋值，VNFM可以通过解析该VNFD文件部署该第一VNF。执行S313。S312的其他具体解释可以参考S210和S213的解释，不予赘述。
S313、VNFM根据第一更新后的VNFD部署第一VNF。
VNFM可以判断第一更新后的VNFD中的输入参数是否全部赋值完成，若第一更新后的VNFD中的输入参数全部赋值完成，根据第一更新后的VNFD部署第一VNF。具体解释可以参考S214的解释，不予赘述。
本申请实施例提供的VNF部署方法，能够使虚拟化业务提供方从VNF信息存储空间中获取修改属性参数的取值，为VNFD中的修改属性参数赋值，以便对VNFD中的输入参数全部赋值，成功部署VNF。
上述本申请提供的实施例中，分别从节点(VNFM、NFVO)之间交互的角度对本申请实施例提供的方法进行了介绍。可以理解的是，各个网元，例如VNFM、NFVO为了实现上述本申请实施例提供的方法中的各功能，VNFM、NFVO包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对VNFM、NFVO进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图4示出了上述和实施例中涉及的通信装置的一种可能的组成示意图，该通信装置能执行本申请各方法实施例中任一方法实施例中VNFM、NFVO所执行的步骤。该通信装置可以包括：接收单元401、处理单元402、发送单元403。
当所述通信装置为VNFM或支持VNFM实现实施例中提供的方法的通信装置，例如该通信装置可以是芯片系统。
其中，接收单元401，用于支持通信装置执行本申请实施例中描述的方法。例如，接收单元401，用于执行或用于支持通信装置执行图2所示的方法中的S202、S208和S212，图3所示的方法中的S302、S308和S310。
处理单元402，用于执行或用于支持通信装置执行图2所示的方法中的S203、S204、S210、S213和S214，图3所示的方法中的S303、S304、S312和S313。
发送单元403，用于执行或用于支持通信装置执行图2所示的方法中的S205，图3所示的方法中的S305。
当所述通信装置为NFVO或支持NFVO实现实施例中提供的方法的通信装置，例如该通信装置可以是芯片系统。
其中，接收单元401，用于支持通信装置执行本申请实施例中描述的方法。例如，接收单元401，用于执行或用于支持通信装置执行图2所示的方法中的S206，图3所示的方法中的S306。
发送单元403，用于执行或用于支持通信装置执行图2所示的方法中的S201、S207和S211，图3所示的方法中的S301、S307和S309。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本申请实施例提供的通信装置，用于执行上述任意实施例的方法，因此可以达到与上述实施例的方法相同的效果。
如图5所示为本申请实施例提供的通信装置500，用于实现上述方法中VNFM的功能。该通信装置500可以是VNFM，也可以是VNFM中的装置。其中，该通信装置500可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。或者，通信装置500用于实现上述方法中NFVO的功能。该通信装置500可以是NFVO，也可以是NFVO中的装置。其中，该通信装置500可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置500包括至少一个处理器501，用于实现本申请实施例提供的方法中VNFM或NFVO的功能。示例性地，处理器501可以用于根据第二赋值指示将N个专用参数和每个专用参数的取值赋予给VNFD中的修改属性参数等等，具体参见方法示例中的详细描述，此处不做赘述。
通信装置500还可以包括至少一个存储器502，用于存储程序指令和/或数据。存储器502和处理器501耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器501可能和存储器502协同操作。处理器501可能执行存储器502中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
通信装置500还可以包括通信接口503，用于通过传输介质和其它设备进行通信，从而用于通信装置500中的装置可以和其它设备进行通信。示例性地，若通信装置为VNFM，该其它设备为NFVO。若通信装置为NFVO，该其它设备为VNFM。处理器501利用通信接口503收发数据，并用于实现图2～图3对应的实施例中所述的VNFM或NFVO所执行的方法。
本申请实施例中不限定上述通信接口503、处理器501以及存储器502之间的具体连接介质。本申请实施例在图5中以通信接口503、处理器501以及存储器502之间通过总线504连接，总线在图5中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。 为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、 服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，SSD)等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种虚拟网络功能VNF部署方法，其特征在于，包括：
    虚拟网络功能管理VNFM接收修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述VNFM获取所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个所述第一赋值指示用于指示一个所述通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取，M为整数，M≥1；
    所述VNFM根据所述第二赋值指示将所述N个专用参数和每个专用参数的取值赋予给所述VNFD中的修改属性参数，得到第一更新后的VNFD；
    所述VNFM接收VNF实例化请求，所述VNF实例化请求包括所述M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数；
    所述VNFM根据所述第一赋值指示将所述M个通用参数的取值赋予给所述第一更新后的VNFD中对应的通用参数，得到第二更新后的VNFD；
    所述VNFM根据所述第二更新后的VNFD部署所述第一VNF。
  2. 一种虚拟网络功能VNF部署方法，其特征在于，包括：
    虚拟网络功能管理VNFM接收修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述VNFM接收VNF实例化请求，所述VNF实例化请求包括M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1；
    所述VNFM获取所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个所述第一赋值指示用于指示一个所述通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取；
    所述VNFM根据所述第一赋值指示将所述M个通用参数的取值赋予给所述VNFD中对应的通用参数，以及根据所述第二赋值指示将所述N个专用参数和每个专用参数的取值赋予给所述VNFD中的修改属性参数，得到第一更新后的VNFD；
    所述VNFM根据所述第一更新后的VNFD部署所述第一VNF。
  3. 根据权利要求1或2所述的方法，其特征在于，所述虚拟化业务请求方为网络功能虚拟化编排器NFVO或运营支持系统/业务支持系统OSS/BSS，所述虚拟化业务提供方为虚拟网络功能管理器VNFM。
  4. 根据权利要求3所述的方法，其特征在于，在所述接收修改VNF信息请求之 前，所述方法还包括：
    所述VNFM接收NFVO发送的创建VNF的实例标识请求，所述创建VNF的实例标识请求包括所述第一VNF的VNFD的标识；
    所述VNFM创建所述第一VNF的实例标识，并建立所述第一VNF的实例标识和所述第一VNF的VNFD的标识的对应关系；
    所述VNFM向所述NFVO发送所述第一VNF的实例标识。
  5. 根据权利要求4所述的方法，其特征在于，所述获取所述第一VNF的VNFD，包括：
    所述VNFM向所述NFVO发送VNFD获取请求，所述VNFD获取请求包括所述第一VNF的VNFD的标识；
    所述VNFM接收NFVO发送的VNFD响应请求，所述VNFD响应请求包括所述第一VNF的VNFD。
  6. 根据权利要求4或5所述的方法，其特征在于，所述修改VNF信息请求还包括所述第一VNF的实例标识，所述VNF实例化请求还包括所述第一VNF的实例标识，在对所述VNFD中的N个通用参数和修改属性参数赋值之前，所述方法还包括：
    所述VNFM确定所述第一VNF的实例标识关联的所述第一VNF的VNFD的标识；
    所述VNFM根据所述第一VNF的VNFD的标识确定所述第一VNF的VNFD。
  7. 根据权利要求4-5中任一项所述的方法，其特征在于，所述创建所述第一VNF的实例标识之后，所述方法还包括：
    所述VNFM创建VNF信息存储空间，所述VNF信息存储空间用于存储所述N个专用参数和每个所述专用参数的取值。
  8. 一种虚拟网络功能VNF部署方法，其特征在于，包括：
    网络功能虚拟化编排NFVO发送修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述NFVO发送所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、所述修改属性参数、M个第一赋值指示和一个第二赋值指示，所述第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取；
    所述NFVO发送VNF实例化请求，所述VNF实例化请求包括所述M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1。
  9. 一种虚拟网络功能VNF部署方法，其特征在于，包括：
    网络功能虚拟化编排NFVO发送修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述NFVO发送VNF实例化请求，所述VNF实例化请求包括M个通用参数和每 个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1；
    所述NFVO发送所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括所述M个通用参数、所述修改属性参数、M个第一赋值指示和一个第二赋值指示，所述第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取。
  10. 根据权利要求8或9所述的方法，其特征在于，所述虚拟化业务请求方为网络功能虚拟化编排器NFVO或运营支持系统/业务支持系统OSS/BSS，所述虚拟化业务提供方为虚拟网络功能管理器VNFM。
  11. 根据权利要求10所述的方法，其特征在于，当第一赋值指示用于指示一个所述通用参数的取值从所述NFVO获取时，在所述NFVO发送VNF实例化请求之前，所述方法还包括：
    所述NFVO设置该一个所述通用参数的取值。
  12. 一种通信装置，其特征在于，包括：
    接收单元，用于接收修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述接收单元，还用于获取所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋值指示，一个所述第一赋值指示用于指示一个所述通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取，M为整数，M≥1；
    处理单元，用于根据所述第二赋值指示将所述N个专用参数和每个专用参数的取值赋予给所述VNFD中的修改属性参数，得到第一更新后的VNFD；
    所述接收单元，还用于接收VNF实例化请求，所述VNF实例化请求包括所述M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数；
    所述处理单元，还用于根据所述第一赋值指示将所述M个通用参数的取值赋予给所述第一更新后的VNFD中对应的通用参数，得到第二更新后的VNFD；
    所述处理单元，还用于根据所述第二更新后的VNFD部署所述第一VNF。
  13. 一种通信装置，其特征在于，包括：
    接收单元，用于接收修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述接收单元，还用于接收VNF实例化请求，所述VNF实例化请求包括M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1；
    所述接收单元，还用于获取所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、修改属性参数、M个第一赋值指示和一个第二赋 值指示，一个所述第一赋值指示用于指示一个所述通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取；
    处理单元，用于根据所述第一赋值指示将所述M个通用参数的取值赋予给所述VNFD中对应的通用参数，以及根据所述第二赋值指示将所述N个专用参数和每个专用参数的取值赋予给所述VNFD中的修改属性参数，得到第一更新后的VNFD；
    所述处理单元，还用于根据所述第一更新后的VNFD部署所述第一VNF。
  14. 根据权利要求12或13所述的装置，其特征在于，所述虚拟化业务请求方为网络功能虚拟化编排器NFVO或运营支持系统/业务支持系统OSS/BSS，所述虚拟化业务提供方为虚拟网络功能管理器VNFM。
  15. 根据权利要求14所述的装置，其特征在于，
    所述接收单元，还用于接收NFVO发送的创建VNF的实例标识请求，所述创建VNF的实例标识请求包括所述第一VNF的VNFD的标识；
    所述处理单元，还用于创建所述第一VNF的实例标识，并建立所述第一VNF的实例标识和所述第一VNF的VNFD的标识的对应关系；
    所述装置还包括：
    发送单元，用于向所述NFVO发送所述第一VNF的实例标识。
  16. 根据权利要求15所述的装置，其特征在于，
    所述发送单元，还用于向所述NFVO发送VNFD获取请求，所述VNFD获取请求包括所述第一VNF的VNFD的标识；
    所述接收单元，还用于接收NFVO发送的VNFD响应请求，所述VNFD响应请求包括所述第一VNF的VNFD。
  17. 根据权利要求15或16所述的装置，其特征在于，
    所述处理单元，还用于确定所述第一VNF的实例标识关联的所述第一VNF的VNFD的标识；
    所述处理单元，还用于根据所述第一VNF的VNFD的标识确定所述第一VNF的VNFD。
  18. 根据权利要求15-16中任一项所述的装置，其特征在于，
    所述处理单元，还用于创建VNF信息存储空间，所述VNF信息存储空间用于存储所述N个专用参数和每个所述专用参数的取值。
  19. 一种通信装置，其特征在于，包括：
    发送单元，用于发送修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述发送单元，还用于发送所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括M个通用参数、所述修改属性参数、M个第一赋值指示和一个第二赋值指示，所述第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取；
    所述发送单元，还用于发送VNF实例化请求，所述VNF实例化请求包括所述M 个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1。
  20. 一种通信装置，其特征在于，包括：
    发送单元，用于发送修改VNF信息请求，所述修改VNF信息请求包括修改属性参数，所述修改属性参数包含N个专用参数和每个所述专用参数的取值，所述N个专用参数和每个所述专用参数的取值为实例化第一VNF所需的参数，N为整数，N≥1；
    所述发送单元，还用于发送VNF实例化请求，所述VNF实例化请求包括M个通用参数和每个所述通用参数的取值，所述M个通用参数和每个所述通用参数的取值为实例化所述第一VNF所需的参数，M为整数，M≥1；
    所述发送单元，还用于发送所述第一VNF的虚拟网络功能模板VNFD，所述第一VNF的VNFD包括所述M个通用参数、所述修改属性参数、M个第一赋值指示和一个第二赋值指示，所述第一赋值指示用于指示一个通用参数的取值从虚拟化业务请求方获取，所述第二赋值指示用于指示所述修改属性参数的取值从虚拟化业务提供方获取。
  21. 根据权利要求19或20所述的装置，其特征在于，所述虚拟化业务请求方为网络功能虚拟化编排器NFVO或运营支持系统/业务支持系统OSS/BSS，所述虚拟化业务提供方为虚拟网络功能管理器VNFM。
  22. 根据权利要求21所述的装置，其特征在于，当第一赋值指示用于指示一个所述通用参数的取值从所述NFVO获取时，所述装置还包括：
    处理单元，用于设置该一个所述通用参数的取值。
  23. 一种通信装置，其特征在于，包括：至少一个处理器、存储器、总线和收发器，其中，所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1、3～7中任一项所述的方法、或者权利要求2、3～7中任一项所述的方法、权利要求8、10～11中任一项所述的方法、或者权利要求9、10～11中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，包括：计算机软件指令；
    当所述计算机软件指令在通信装置或内置在通信装置的芯片中运行时，使得所述通信装置执行如权利要求1、3～7中任一项所述的方法、或者权利要求2、3～7中任一项所述的方法、权利要求8、10～11中任一项所述的方法、或者权利要求9、10～11中任一项所述的方法。
PCT/CN2020/095804 2019-06-14 2020-06-12 一种虚拟网络功能vnf部署方法及装置 Ceased WO2020249080A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20823574.7A EP3972196B1 (en) 2019-06-14 2020-06-12 Virtual network function (vnf) deployment method and apparatus
US17/548,839 US11683222B2 (en) 2019-06-14 2021-12-13 Virtual network function VNF deployment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910517265.1A CN112087311B (zh) 2019-06-14 2019-06-14 一种虚拟网络功能vnf部署方法及装置
CN201910517265.1 2019-06-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/548,839 Continuation US11683222B2 (en) 2019-06-14 2021-12-13 Virtual network function VNF deployment method and apparatus

Publications (1)

Publication Number Publication Date
WO2020249080A1 true WO2020249080A1 (zh) 2020-12-17

Family

ID=73734091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/095804 Ceased WO2020249080A1 (zh) 2019-06-14 2020-06-12 一种虚拟网络功能vnf部署方法及装置

Country Status (4)

Country Link
US (1) US11683222B2 (zh)
EP (1) EP3972196B1 (zh)
CN (1) CN112087311B (zh)
WO (1) WO2020249080A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110661641B (zh) * 2018-06-29 2021-07-16 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
EP4127925A1 (en) * 2020-03-31 2023-02-08 Telefonaktiebolaget LM ERICSSON (PUBL) Orchestration of virtualization technology and application implementation
CN115695199A (zh) * 2021-07-26 2023-02-03 中国移动通信有限公司研究院 网络功能虚拟化的实例更新方法、设备及存储介质
CN118057772A (zh) * 2022-11-18 2024-05-21 华为技术有限公司 部署虚拟化网络功能的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106161603A (zh) * 2016-06-28 2016-11-23 华为技术有限公司 一种组网的方法、设备及架构
CN106161076A (zh) * 2015-04-22 2016-11-23 华为技术有限公司 虚拟网络功能扩展方法和装置
WO2016197643A1 (zh) * 2016-01-22 2016-12-15 中兴通讯股份有限公司 一种实现vnf部署的方法及装置
CN109522090A (zh) * 2018-11-09 2019-03-26 中国联合网络通信集团有限公司 资源调度方法及装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9806975B2 (en) 2014-06-12 2017-10-31 Futurewei Technologies, Inc. Methods and systems for managing capacity in a virtualized network
WO2016019492A1 (zh) * 2014-08-04 2016-02-11 华为技术有限公司 一种虚拟网管的部署方法、装置和虚拟网络系统
CN105790976B (zh) * 2014-12-23 2018-10-09 中国电信股份有限公司 实现虚拟网络功能描述文件自动更新的方法和系统
EP3249527B1 (en) * 2015-02-16 2022-11-02 Huawei Technologies Co., Ltd. Operation method and device for vnf package
US9769694B2 (en) * 2015-03-13 2017-09-19 Intel IP Corporation MME overload or underload mitigation by MME VNF apparatus and method
WO2016154917A1 (zh) * 2015-03-31 2016-10-06 华为技术有限公司 一种管理虚拟网络功能的方法和装置
CN106576068B (zh) * 2015-04-30 2019-11-19 华为技术有限公司 一种软件安全验证方法、设备及系统
US10671420B2 (en) * 2015-05-07 2020-06-02 Futurewei Technologies, Inc. System and method for dynamic virtualized network function descriptor management
US10148731B2 (en) * 2015-06-30 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for on-boarding virtualized network function (VNF) packages in a network functions virtualization (NFV) system
CN107623578A (zh) * 2016-07-14 2018-01-23 中兴通讯股份有限公司 一种虚拟化网络功能实例化方法及装置
CN107689882B (zh) 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
WO2018033878A1 (en) * 2016-08-18 2018-02-22 Telefonaktiebolaget Lm Ericsson (Publ) A network service design and deployment process for nfv systems
CN108234158B (zh) * 2016-12-14 2021-04-20 中国电信股份有限公司 Vnf的建立方法、nfvo以及网络系统
CN108400998B (zh) * 2017-02-07 2020-03-20 华为技术有限公司 一种部署vnf的方法和系统
CN108462592A (zh) 2017-02-20 2018-08-28 华为技术有限公司 基于sla的资源分配方法和nfvo
US10469317B1 (en) * 2017-03-29 2019-11-05 Juniper Networks, Inc. Virtualized network function descriptors for virtualized network function configuration
US10735275B2 (en) * 2017-06-16 2020-08-04 Cisco Technology, Inc. Releasing and retaining resources for use in a NFV environment
CN107357836B (zh) * 2017-06-22 2020-01-24 浪潮天元通信信息系统有限公司 一种vnf包以及其引用的镜像文件删除方法和设备
CN109391483A (zh) * 2017-08-04 2019-02-26 中国电信股份有限公司 网络实例化方法、网络功能虚拟化编排器和系统
CN109600246B (zh) * 2017-09-30 2021-09-21 华为技术有限公司 网络切片管理方法及其装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106161076A (zh) * 2015-04-22 2016-11-23 华为技术有限公司 虚拟网络功能扩展方法和装置
WO2016197643A1 (zh) * 2016-01-22 2016-12-15 中兴通讯股份有限公司 一种实现vnf部署的方法及装置
CN106161603A (zh) * 2016-06-28 2016-11-23 华为技术有限公司 一种组网的方法、设备及架构
CN109522090A (zh) * 2018-11-09 2019-03-26 中国联合网络通信集团有限公司 资源调度方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Requirements(Release 14)", 3GPP TS 28.525 V1.2.0, 31 January 2017 (2017-01-31), pages 1 - 47, XP051230664, DOI: 20200827170759A *
See also references of EP3972196A4

Also Published As

Publication number Publication date
US11683222B2 (en) 2023-06-20
EP3972196A4 (en) 2022-07-13
CN112087311B (zh) 2022-04-12
EP3972196B1 (en) 2024-09-25
US20220103423A1 (en) 2022-03-31
EP3972196A1 (en) 2022-03-23
CN112087311A (zh) 2020-12-15

Similar Documents

Publication Publication Date Title
EP3291499A1 (en) Method and apparatus for network service capacity expansion
CN111245634B (zh) 一种虚拟化管理方法及装置
US11683222B2 (en) Virtual network function VNF deployment method and apparatus
CN107689882A (zh) 一种虚拟化网络中业务部署的方法和装置
WO2017045471A1 (zh) 一种在云计算系统中获取业务链信息的方法和装置
WO2014169870A1 (zh) 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质
US12056094B2 (en) Method and apparatus for deploying virtualised network function
CN112306625B (zh) 一种部署虚拟机的方法及相关装置
CN113342456B (zh) 一种连接方法、装置、设备和存储介质
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20250293933A1 (en) Instantiation method and apparatus for virtualised network function vnf
CN112889247B (zh) Vnf服务实例化方法及装置
US20230409371A1 (en) Method for creating network service ns and related apparatus
US20230105269A1 (en) Virtualized network service deployment method and apparatus
JP7618042B2 (ja) スケーリング方法および装置
US12592867B2 (en) Method for establishing network connection and apparatus
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置

Legal Events

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

Ref document number: 20823574

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020823574

Country of ref document: EP

Effective date: 20211214