WO2020135517A1 - 部署虚拟化网络功能的方法和装置 - Google Patents

部署虚拟化网络功能的方法和装置 Download PDF

Info

Publication number
WO2020135517A1
WO2020135517A1 PCT/CN2019/128356 CN2019128356W WO2020135517A1 WO 2020135517 A1 WO2020135517 A1 WO 2020135517A1 CN 2019128356 W CN2019128356 W CN 2019128356W WO 2020135517 A1 WO2020135517 A1 WO 2020135517A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
value
request message
parameter
nfvo
Prior art date
Application number
PCT/CN2019/128356
Other languages
English (en)
French (fr)
Inventor
李世涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19901817.7A priority Critical patent/EP3893437B1/en
Publication of WO2020135517A1 publication Critical patent/WO2020135517A1/zh
Priority to US17/361,181 priority patent/US20210326306A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/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/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/5045—Making service definitions prior to deployment
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the computer field, and more specifically, to a method and apparatus for deploying virtualized network functions in the computer field.
  • Network function virtualization uses general hardware equipment and virtualization technology to carry the functions of special equipment in the traditional network, which can reduce the cost of deploying special equipment.
  • network function virtualization can use cloud computing to achieve resource sharing, and also to quickly and automatically deploy new services based on business needs. And when deploying services, it can achieve elastic scaling, fault isolation, and self-healing.
  • the virtualized network service (NS) in NFV may be an IP multimedia subsystem network service (IP) network (IMS) network or a next-generation core packet network evolution (EPC) network.
  • IP IP multimedia subsystem network service
  • EPC next-generation core packet network evolution
  • An NS may include one or more virtual network function (virtual network function, VNF) modules.
  • VNF virtual network function
  • the service requester needs to provide the description information (NSD) of the network service to the service provider, also known as NS.
  • NSD mainly describes the topology of network services and contains description information (VNFD, VNFD) of each VNF.
  • VNFD is also called VNF.
  • a VNFD consists of multiple files, including a main file and one or more auxiliary files, where the main file is the first file to parse VNFD, mainly including the type, properties, and requirements of the VNF ) And other parameters.
  • Each auxiliary file represents the corresponding deployment preference (deployment, flavour) of the VNF.
  • Each auxiliary file can independently deploy a VNF. When instantiating the VNF, determine which auxiliary file is used to deploy the VNF according to the value of the deployment preference.
  • the input parameters required by each auxiliary file are different, but how to set the input parameters of each auxiliary file is a problem that needs to be considered. At present, the programmer manually enters the input parameters of the auxiliary file. This situation has a low degree of automation and requires programmers. It is relatively high, which leads to greater interference of human factors, which affects the performance of network services.
  • This application provides a method and device for deploying virtualized network functions, which can improve the performance of network services.
  • a method for deploying VNF includes: a virtual network function manager VNFM acquiring a first VNFD, the first VNFD being composed of a main file and one or more auxiliary files, the main file and the one Each auxiliary file in the multiple auxiliary files has a mapping relationship.
  • the main file includes deployment parameters of each auxiliary file and a first association relationship, where the first association relationship is used to indicate the value of the preference parameter of the VNF and the auxiliary file.
  • the deployment parameters of the file are related;
  • the VNFM deploys the first VNF according to the first VNFD.
  • the first VNFD is description information of the first VNF.
  • the main file includes the deployment parameters of each auxiliary file and a first association relationship, where the first association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameters of the auxiliary file.
  • the deployment parameter of the auxiliary file corresponding to the value of the preference parameter of the first VNF may be determined according to the first association relationship, so that the program personnel may be prevented from determining the value of the first VNF
  • the deployment parameter of the auxiliary file corresponding to the value of the preference parameter can reduce the degree of participation of the program personnel, thereby improving the degree of automation and helping to improve the performance of the system.
  • the primary file may determine the deployment parameter value corresponding to the preference parameter value of the first VNF as the deployment parameter value of the auxiliary file through a mapping relationship.
  • the value of the preference parameter of a VNF corresponds to an auxiliary file.
  • the first association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameter of the auxiliary file, that is, by entering the value of the preference parameter of a VNF, the preference of the VNF can be obtained according to the first association relationship The deployment parameter corresponding to the value of the parameter.
  • obtaining the first VNFD by the VNFM includes: receiving the first request message by the VNFM, where the first request message includes the identifier of the first VNF and the value of the preference parameter of the first VNF 1.
  • the value of the preference parameter of the first VNF corresponds to the value of the deployment parameter;
  • the VNFM determines the first VNFD according to the identifier of the first VNF; wherein the VNFM deploying the first VNF according to the first VNFD includes:
  • the VNFM determines the target file in the first or more auxiliary files according to the value of the preference parameter of the first VNF;
  • the VNFM deploys the first VNF according to the first association relationship and the mapping relationship between the main file and the target file.
  • the first request message may also include the instantiation level, for example, it may be level.
  • deploying the first VNF according to the first association relationship and the mapping relationship between the main file and the target file by the VNFM includes: the VNFM according to the first association relationship And the value of the preference parameter of the first VNF determines the deployment parameter of the target file in the deployment parameter of each auxiliary file included in the main file; the VNFM corresponds the value of the preference parameter of the first VNF The value of the deployment parameter of is determined as the value of the deployment parameter of the target file; the VNFM uses the mapping relationship between the main file and the target file to input the value of the deployment parameter of the target file to the In the target file, the first VNF is deployed using the value of the deployment parameter of the target file.
  • the method before the VNFM receives the first request message, the method further includes: the VNFM receives a second request message sent by the network function virtualization orchestrator NFVO, and the second request message It is used to request to create the identifier of the first VNF; the VNFM creates the identifier of the first VNF according to the second request message; the VNFM sends the identifier of the first VNF to the NFVO; wherein, Said VNFM receiving the first request message includes: the VNFM receiving the first request message sent by the NFVO.
  • the method before the VNFM receives the first request message, the method further includes: the VNFM receives a second request message sent by an operating support system and a business support system OSS/BSS, the second request The message is used to request to create the identifier of the first VNF; the VNFM creates the identifier of the first VNF according to the second request message; the VNFM sends the identifier of the first VNF to the OSS/BSS;
  • the VNFM receiving the first request message includes: the VNFM receiving the first request message sent by the OSS/BSS through a device management system EMS.
  • the method before the VNFM determines the first VNFD according to the identifier of the first VNF, the method further includes: the VNFM sends a third request message to the NFVO, and the third request message Including the identifier of the first VNF, and the third request message is used to request the first VNFD from the NFVO;
  • the VNFM determining the first VNFD according to the identifier of the first VNF includes: the VNFM receiving the first VNFD sent by the NFVO according to the third request message.
  • a method for deploying VNF including: an operation support system and a business support system OSS/BSS sending a fourth request message to the network function virtualization orchestrator NFVO, the fourth request message including the first VNF The value of the first VNFD logo and the preference parameter of the first VNF;
  • the OSS/BSS receives the deployment parameter corresponding to the value of the first VNF preference parameter sent by the NFVO, wherein the deployment parameter corresponding to the value of the first VNF preference parameter is based on the first VNFD
  • the identifier and the value of the preference parameter of the first VNF are determined.
  • the method before the OSS/BSS sends a fourth request message to the network function virtualization orchestrator NFVO, the method further includes:
  • the OSS/BSS sends a fifth request message to the NFVO, the fifth request message includes an identifier of the network service and a value of a preference parameter of the network service, the network service is composed of one or more VNFs, the One or more VNFs include the first VNF;
  • the OSS/BSS receives the value of the preference parameter of each VNF sent by the NFVO, and the value of the preference parameter of each VNF is the value of the NFVO according to the network service identifier and the network service The value of the preference parameter is determined.
  • the method further includes the OSS/BSS sending a sixth request message to the NFVO, where the sixth request message includes the identifier of the second VNFD and the value of the preference parameter of the second VNF ;
  • the OSS/BSS receives the deployment parameter corresponding to the value of the preference parameter of the second VNF sent by the NFVO, wherein the deployment parameter corresponding to the value of the preference parameter of the second VNF is based on the second VNFD And the value of the preference parameter of the second VNF is determined, the one or more VNFs include the second VNF;
  • the OSS/BSS sends a seventh request message to the NFVO, where the seventh request message includes the value of the preference parameter of the network service and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF
  • the value and the value of the preference parameter of the second VNF correspond to the value of the deployment parameter.
  • the method further includes: the OSS/BSS sends a second request message to the virtual network function manager NFVM, the second The request message is used to request to create the identifier of the first VNF;
  • the OSS/BSS receives the identifier of the first VNF sent by the NFVM according to the second request message;
  • the OSS/BSS sends a first request message to the NFVM through the device management system EMS, the first request message includes the identifier of the first VNF, the value of the preference parameter of the first VNF, and the first The value of the preference parameter of a VNF corresponds to the value of the deployment parameter.
  • a method for deploying VNF including: a network function virtualization orchestrator NFVO receives a fourth request message sent by an operation support system and a business support system OSS/BSS, the fourth request message including the first VNF The identifier of the first VNFD and the value of the preference parameter of the first VNF;
  • the NFVO determines the first VNFD according to the identifier of the first VNFD
  • the NFVO determines the deployment parameter corresponding to the value of the preference parameter of the first VNF in the first VNFD according to the value of the preference parameter of the first VNF;
  • the NFVO sends the deployment parameter corresponding to the value of the preference parameter of the first VNF to the OSS/BSS.
  • the main file includes deployment parameters of each auxiliary file, in this way, the deployment corresponding to the value of the first VNF preference parameter can be determined according to the value of the first VNF preference parameter and the first association relationship parameter.
  • mapping relationship between the main file and each of the one or more auxiliary files.
  • the first VNFD is composed of a main file and one or more auxiliary files.
  • the main file includes deployment parameters of each auxiliary file and a first association relationship.
  • the first association relationship is used to The value of the preference parameter indicating the VNF is associated with the deployment parameter of the auxiliary file;
  • the NFVO determines the deployment parameter corresponding to the value of the first VNF preference parameter in the first VNFD according to the value of the first VNF preference parameter, including:
  • the NFVO determines the deployment parameter corresponding to the value of the first VNF preference parameter in the master file according to the value of the first VNF preference parameter and the first association relationship.
  • the method before the NFVO receives the fourth request message sent by the OSS/BSS, the method further includes:
  • the NFVO receives a fifth request message sent by the OSS/BSS.
  • the fifth request message includes an identifier of a network service and a value of a preference parameter of the network service.
  • the network service is composed of one or more VNFs.
  • the one or more VNFs include the first VNF;
  • the NFVO determines the network service according to the identifier of the network service, and the network service is composed of a main file and one or more auxiliary files;
  • the NFVO determines the target file of the network service in the one or more auxiliary files constituting the network service according to the value of the preference parameter of the network service;
  • the NFVO determines the value of the preference parameter corresponding to each VNF in the one or more VNFs in the target file of the network service
  • the NFVO sends the OSS/BSS the value of the preference parameter corresponding to each VNF.
  • the method further includes:
  • the NFVO receives a sixth request message sent by the OSS/BSS, where the sixth request message includes the identifier of the second VNFD and the value of the preference parameter of the second VNF;
  • the NFVO determines the template of the second VNF according to the identifier of the second VNFD, the second VNFD is composed of a main file and one or more auxiliary files, and the main file includes deployment parameters of each auxiliary file and A second association relationship, where the second association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameter of the auxiliary file;
  • the NFVO determines the deployment parameter corresponding to the value of the preference parameter of the first VNF in the main file of the second VNFD according to the value of the preference parameter of the second VNF and the second association relationship;
  • the NFVO sends the deployment parameter corresponding to the value of the preference parameter of the second VNF to the OSS/BSS;
  • the NFVO receives a seventh request message sent by the OSS/BSS, where the seventh request message includes the value of the preference parameter of the network service and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF The value of the deployment parameter corresponding to the value of the preference parameter of the second VNF.
  • the method further includes:
  • the NFVO sends a second request message to the VNFM, where the second request message is used to request the identifier of the first VNF;
  • the NFVO receives the identifier of the first VNF sent by the VNFM according to the second request message
  • the NFVO sends a first request message to the VNFN, where the first request message includes the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the preference parameter of the first VNF The value of the deployment parameter corresponding to the value.
  • an apparatus for deploying a virtualized network function for performing the method in the first aspect or any possible implementation manner of the first aspect.
  • the apparatus includes a unit for performing the method in the first aspect or any possible implementation manner of the first aspect.
  • an apparatus for deploying a virtualized network function for performing the method in the second aspect or any possible implementation manner of the second aspect.
  • the apparatus includes a unit for performing the method in the second aspect or any possible implementation manner of the second aspect.
  • an apparatus for deploying a virtualized network function for performing the method in the third aspect or any possible implementation manner of the third aspect.
  • the apparatus includes a unit for performing the method in the third aspect or any possible implementation manner of the third aspect.
  • the present application provides a computer-readable storage medium that stores computer instructions, and when the computer instructions run on a computer, causes the computer to perform the first aspect or any of the first aspect Possible implementation methods.
  • the present application provides a computer-readable storage medium that stores computer instructions, and when the computer instructions run on a computer, causes the computer to perform the second aspect or any of the second aspect Possible implementation methods.
  • the present application provides a computer-readable storage medium that stores computer instructions, and when the computer instructions run on a computer, causes the computer to perform the third aspect or any of the third aspects Possible implementation methods.
  • the present application provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a network device installed with the chip performs the first aspect And methods in any possible implementation of the first aspect.
  • the present application provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the network device installed with the chip executes the second Method in any possible implementation of the aspect and its second aspect.
  • the present application provides a chip, including a memory and a processor.
  • the memory is used to store a computer program.
  • the processor is used to call and run the computer program from the memory, so that the network device installed with the chip executes the third Method in any possible implementation of the aspect and its third aspect.
  • the present application provides a computer program product, the computer program product comprising computer program code, when the computer program code runs on a computer, the computer is caused to perform the first aspect and any possible implementation of the first aspect The way in the way.
  • the present application provides a computer program product, the computer program product comprising computer program code, when the computer program code runs on a computer, causing the computer to perform the second aspect and any possible implementation of the second aspect The way in the way.
  • the present application provides a computer program product, the computer program product including computer program code, when the computer program code runs on a computer, causing the computer to perform the third aspect and any possible implementation of the third aspect The way in the way.
  • the present application provides an apparatus for deploying virtualized network functions, including a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, so that the network device executes the method in the first aspect and any possible implementation manner of the first aspect.
  • this application provides an apparatus for deploying a virtualized network function, including a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, so that the network device executes the method in the second aspect and any possible implementation manner of the second aspect.
  • the present application provides an apparatus for deploying virtualized network functions, including a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, so that the network device executes the method in the third aspect and any possible implementation manner of the third aspect.
  • the present application provides a system for deploying a virtualized network function, the system including the apparatus in the first aspect and any possible implementation manner of the first aspect, and the second aspect and any possible implementation of the second aspect The device in the manner and the device in the third aspect and any possible implementation manner of the third aspect; or
  • the system includes the device in the sixteenth aspect and any possible implementation manner of the sixteenth aspect, the device in the seventeenth aspect and any possible implementation manner of the seventeenth aspect and the eighteenth aspect and the tenth aspect The device in any possible implementation manner of the eight aspects.
  • FIG. 1 shows a schematic diagram of a system architecture applied in an embodiment of the present application.
  • FIG. 2 shows a schematic flowchart of an existing method for deploying a virtualized network function.
  • FIG. 3 shows a schematic flowchart of a method for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 4 shows a schematic flowchart of another method for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 5 shows a schematic flowchart of still another method for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 6 shows a schematic flowchart of still another method for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 7 shows a schematic block diagram of an apparatus for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 8 shows a schematic block diagram of another apparatus for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 9 shows a schematic block diagram of another apparatus for deploying a virtualized network function provided by an embodiment of the present application.
  • FIG. 10 shows a schematic block diagram of another apparatus for deploying a virtualized network function provided by an embodiment of the present application.
  • Figure 1 shows a schematic diagram of the architecture of an NFV system, including a network function virtualization orchestration (NFVO) 102, a virtual network function manager (virtual network function function manager, VNFM) 104, an operation support system, and services Support system (operations support system and business support system (OSS/BSS) 124.
  • the system also includes a virtual infrastructure manager (virtualized infrastructure manager, VIM) 106, a network function virtualization infrastructure (network functions virtual infrastructure, NFVI), and an equipment management system (equipment management system, EMS) 110. At least one.
  • NFVO102 is mainly responsible for handling the life cycle management of virtualization services, as well as the allocation and scheduling of virtual resources in the infrastructure layer (NFV infrastructure, VFVI) of network function virtualization.
  • NFVO 102 can communicate with one or more VNFM 104 to perform resource related requests and send configuration information to VNFM 104. Collect the status information of VNF108.
  • NFVO102 can also communicate with VIM106, perform resource allocation, and/or reservation, and exchange virtualized hardware resource configuration and status information.
  • VNFM04 is responsible for the lifecycle management of one or more VNF108, such as instantiating, updating, querying, elastic scaling, and terminating VNF108.
  • VNFM104 can communicate with VNF108 to complete VNF lifecycle management and exchange configuration and status information.
  • VIM 106 controls and manages the interaction of VNF 108 with computing hardware 112, storage hardware 114, network hardware 116, virtual computing 118, virtual storage 120, and virtual network 122.
  • VIM 106 performs resource management functions, including managing infrastructure resources, allocating (such as adding resources to virtual containers), and running functions (such as collecting NFVI failure information).
  • VNFM104 and VIM106 can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.
  • Network functions virtualization infrastructure is the NFV infrastructure layer, which includes hardware components, software components, or a combination of the two to establish a virtualized environment, deploy, manage, and implement VNF108.
  • the hardware resources and virtualization layer are used to provide VNF108 with virtualization resources, such as virtual machines and other forms of virtual containers.
  • the hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. As an embodiment, the resources of the computing hardware 112 and the storage hardware 114 may be centralized.
  • the virtualization layer in NFVI can abstract hardware resources and decouple VNF108 from the underlying physical network layer.
  • EM110 is a system used to configure and manage devices in traditional telecommunications systems. In the NFV architecture, EM110 can also be used to configure and manage VNFs, and initiate new VNF instantiation lifecycle management operations to VNFM. .
  • OSS/BSS124 supports various end-to-end telecommunications services.
  • the management functions supported by OSS include: network configuration, service provision, and fault management.
  • BSS processes orders, payment, revenue, etc., supports product management, order management, revenue management and customer management.
  • the NFV is a VNFD model based on the TOSCA language as an example for description.
  • the embodiments of the present application are not limited thereto, and may be VNFD models in other languages.
  • a VNFD is composed of multiple TOSCA service templates (service), mainly composed of a top-level service template (top level service template) and one or more low-level service templates (low level service template), the top service template is to parse the VNFD
  • the first file also known as the main file, mainly contains the node_template description of the VNF, and the VNF node template contains parameters such as the type, properties, and requirements of the VNF, as described below.
  • the low-level service template may contain multiple TOSCA service templates, also known as auxiliary files. Each represents a deployment preference of a VNF.
  • Each low-level service template is a service template that can be independently deployed and is instantiated.
  • VNF In VNF, according to the value of flavour_id in the instantiation request, decide which low level service template to deploy. Different deployment preferences correspond to different resource requirements for VNF deployment, so the composition of service templates corresponding to different deployment preferences may be different.
  • the flavour described in VNF_DF2.yaml in the above example may be aimed at more users.
  • two VDU resources, VDU_1 and VDU_2 are required to jointly provide services;
  • VNF_DF1.yaml describes a scenario where a small number of users access, and only one VDU_1 needs to be deployed to provide services.
  • Each low level service template is associated with the top_level service template through substitution_mapping, specifically, the type defined in substitution_mapping and the value of flavour_id in properties are associated with top level service template.
  • the deployment flavour indicated in the VNF instantiation request is flavour 1
  • the flavour_id in the VNF1node template in the top level service template gets the value of flavour in the request through get_input(flavour), that is, flavour 1
  • the top level service template Via type:tosca.nodes.nfv.exampleVNF and flavour_id: flavour1 are associated with the VNF_DF1.yaml in the low-level service template, that is, the VNF_DF1.yaml is used to deploy the VNF of the deployment preference (specifically, including the deployment of the service included in the service template VDU, VL and CP resources).
  • top level service template (top level service template) is as follows, for example, VNFD_yaml.
  • VNF_DF1.yaml VNF_DF2.yaml
  • VNF_DF1.yaml and VNF_DF2.yaml The input parameters required for the template corresponding to each low level service template during instantiation may also be different.
  • the input parameters defined in VNF_DF1.yaml are:
  • VNF_DF2.yaml The input parameters defined in VNF_DF2.yaml are:
  • the parameter values of different low-level service templates need to be carried by the requester in the instantiation request, but the input parameters required by different low-level service templates are different.
  • the existing technology is that the program personnel need to have a certain discriminating ability.
  • the recognition of low-level service templates so that the value of the input parameter is sent to the provider in the instantiation request. For example, if the current preference parameter value is flavour 1, the programmer must know that the input parameter defined in VNF_DF1.yaml is:
  • the programmer will assign values to these parameters and send the values of these parameters to the provider in the instantiation request. Assuming that the programmer's cognitive ability is insufficient, assuming that the current preference parameter value is flavour 2, it is possible to provide these parameters to the provider:
  • flavour 2 the input parameter of VNF_DF2.yaml corresponding to flavour 2 is
  • the following describes the existing method 200 for deploying VNF with reference to FIG. 2, including:
  • OSS/BSS sends NSD to NFVO, and stores NSD in NFVO or in a database that NFVO can access.
  • NFVO creates an instance ID of NS according to the NSD uploaded by OSS/BSS.
  • an NSD can be composed of multiple service templates. For example, it can also be composed of a top-level service template (top level service template) and one or more low-level service templates (low level service template). Main files, low-level service templates can also be called auxiliary files.
  • NSD consists of NSD.yaml (main file), NS-DF1.yaml (auxiliary file), and NS_DF2.yaml (auxiliary file).
  • the deployment file corresponding to the preference parameter flavour1 is NS-DF1.yaml
  • the deployment file corresponding to the preference parameter flavour2 is NS_DF2.yaml.
  • NSD.yaml The description of NSD.yaml is as follows:
  • NS_DF2.yaml The description of NS_DF2.yaml is as follows:
  • NFVO sends the created instance ID of the NS to OSS/BSS.
  • the OSS/BSS sends a request message for instantiating the NS to the NFVO.
  • the request message carries the instance identifier of the NS, the value of the preference parameter of the NS, and the value of the deployment parameter of the VNF included in the NS.
  • NFVO determines which auxiliary file is used to deploy the NS according to the value of the preference parameter of the NS. Assuming that the preference value of the NS is flavour 1, NFVO determines to deploy the NS using NS_DF1.yaml.
  • the auxiliary file describes the VNF included in the corresponding NS deployment preference (favourment), virtual connection
  • VNF resource information contains deployment preference (deployment) flavour information during VNF deployment, such as flavour_id:flavour1 information in the properties of VNF_1.
  • the preference parameter of NS is flavour 1
  • the request message of S240 is sent to NFVO.
  • the deployment parameters of the foregoing VNF_1 are: private_net_id and private_net_cidr, and the programmer needs to assign values to these two parameters.
  • the requirements for programmers are relatively high, requiring programmers to be familiar with NSD, the VNF in each NSD auxiliary file, and the deployment parameters of each VNF.
  • NFVO obtains the NSD file according to the instance identifier of the NS.
  • the NSD file may also be described based on TOSCA, and the VNFD information contained in the NSD is obtained from the NSD.
  • the NFVO Before instantiating the VNF request, the NFVO sends a create request message to the VNFM, and the create request message is used to request to create a VNF instance identifier.
  • the VNFM creates a VNF instance identifier according to the request message, and returns the created VNF instance identifier to the NFVO.
  • NFVO sends an instantiated VNF request message to the VNFM.
  • the instantiated VNF request message includes the VNF instance identifier obtained in section S270, and the deployment Vfl deployment flag included in NS_DF1.yaml.
  • VNFM instantiates the VNF according to the parameters carried in the instantiate VNF request.
  • the secondary file of an NS is composed of one or more VNFDs. Assume that the secondary file of an NS is composed of multiple VNFDs. Each VNFD executes S260-S280 once, and multiple VNFDs execute S260-S280 multiple times. The deployment of NS was completed.
  • FIG. 3 describes a method 300 for deploying VNF provided by an embodiment of the present application, including:
  • the VNFM obtains a first VNFD of the first VNF, where the first VNFD is composed of a main file and one or more auxiliary files, and there is a mapping relationship between the main file and each auxiliary file in the one or more auxiliary files,
  • the main file includes a deployment parameter of each auxiliary file and a first association relationship, where the first association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameter of the auxiliary file.
  • the main file may be the aforementioned top service template (top level service template), and the auxiliary file may be the aforementioned low level service template (low level service template).
  • the first VNFD may be composed of a top-level service template and one or more low-level service templates, such as VNFD.yaml, VNF_DF1.yaml, and VNF_DF2.yaml, which will be described below.
  • mapping relationship between the main file and each auxiliary file in the one or more auxiliary files
  • the main file can use the mapping relationship to deploy deployment parameters corresponding to the value of the preference parameter of the first VNF
  • the value is determined as the value of the deployment parameter of the auxiliary file.
  • the mapping relationship may be that there is some connection between the main file and the auxiliary file.
  • the VNFM deploys the first VNF according to the first VNFD.
  • the main file includes deployment parameters of each auxiliary file and a first association relationship
  • the first association relationship is used to indicate the value of the preference parameter of the VNF and the auxiliary file Associated with the deployment parameters.
  • the virtual network function manager obtains the value of the preference parameter of the first VNF, it can determine the deployment parameter of the auxiliary file corresponding to the value of the preference parameter of the first VNF according to the first association relationship, so as to avoid the program personnel from determining
  • the deployment parameter of the auxiliary file corresponding to the value of the preference parameter of the first VNF can reduce the degree of participation of the program personnel, thereby improving the degree of automation and helping to improve the performance of the system.
  • S310 includes: the VNFM receives a first request message, the first request message includes an identifier of the first VNF, a value of a preference parameter of the first VNF, and the first VNF The value of the preference parameter corresponds to the value of the deployment parameter;
  • the VNFM determines the first VNFD according to the identifier of the first VNF
  • S320 includes: the VNFM determining a target file in the first or more auxiliary files according to the value of the preference parameter of the first VNF;
  • the VNFM deploys the first VNF according to the first association relationship and the mapping relationship between the main file and the target file.
  • the first request message may also include the instantiation level, for example, it may be level.
  • the method before the VNFM determines the first VNFD according to the identifier of the first VNF, the method further includes:
  • the VNFM sends a third request message to the NFVO, the third request message includes the identifier of the first VNF, and the third request message is used to request the first VNFD from the NFVO;
  • the VNFM determining the first VNFD according to the identifier of the first VNF includes: the VNF manager receiving the first VNFD sent by the NFVO according to the third request message.
  • the first VNFD may be stored in the NFVO.
  • the VNFM uses the identifier of the first VNF to request the first VNFD from the NFVO.
  • deploying the first VNF according to the first association relationship and the mapping relationship between the main file and the target file includes:
  • the VNFM determines the deployment parameters of the target file from the deployment parameters of each auxiliary file included in the main file according to the first association relationship and the value of the preference parameter of the first VNF;
  • the VNFM determines the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF as the value of the deployment parameter of the target file;
  • the VNFM uses the mapping relationship between the main file and the target file to input the value of the deployment parameter of the target file into the target file, and deploys the location using the value of the deployment parameter of the target file
  • the first VNF is described.
  • the VNF identifier may also be referred to as the VNF instance identifier.
  • each VNF has a one-to-one correspondence with each VNFD.
  • the first VNFD may be determined according to the first VNF identifier, for example, using the first VNF identifier Request the first VNFD from NFVO, so that VNFM can use the first VNFD to deploy the first VNFD.
  • the value of one preference parameter corresponds to one auxiliary file.
  • the auxiliary file corresponding to the value of the preference parameter of the first VNF can be determined in one or more auxiliary files
  • the target file for example, in the foregoing description, when the value of the preference parameter of the first VNF is flavour 1, it can be determined that the target file is VNF_DF1.yaml.
  • the VNFM can determine the target according to the value of the first preference parameter File deployment parameters, so that the value of the deployment parameter corresponding to the preference parameter of the first VNF carried in the first request message is the value of the deployment parameter of the target file, and finally, the target file can be deployed
  • the value of the parameter is input into the target file through the mapping relationship between the main file and the target file, and the VNFM uses the target file to deploy the first VNF.
  • VNFD model based on the TOSCA language is not limited to this, and may also be a VNFD model in other languages.
  • the description of the main file is as follows, for example, the main file is VNFD.yaml:
  • the auxiliary files may be VNF_DF1.yaml and VNF_DF2.yaml, for example:
  • VNF_DF1.yaml The description of VNF_DF1.yaml is as follows:
  • the first request message carries VNF1_id (the identifier of the first VNF, which may also be referred to as the instance identifier of the first VNF), flavour 1 (the preference parameter of the first VNF Value), private_net_id: net1234567 (the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF) and private_net_cidr: 192.168.0.0/24 (the deployment of the value of the preference parameter of the first VNF Parameter value).
  • VNFM sends a third request message to NFVO.
  • the third request message carries VNF1_id.
  • VNFVO determines VNFD1 according to VNF1_id in the third request message, and sends VNFD1 to VNFM.
  • VNFD1 includes the above VNFD.yaml, VNF_DF1.yaml, and VNF_DF2.yaml, where the auxiliary file corresponding to flavour 1 is VNF_DF1.yaml, and the auxiliary file corresponding to flavour 2 is VNF_DF2.yaml.
  • VNFM determines the target file as VNF_DF1.yaml according to flavour 1.
  • VNFM learns that the preference value of the first VNF is flavour 1
  • VNFD.yaml associated with the deployment parameter of VNF_DF1.yaml, such as type:concat:['inst_info_',get_input in VNFD.yaml (flavour)]Associate flavour 1 with private_net_id:type:string private_net_cidr:type:string so that VNFM can determine the deployment parameter corresponding to the value of the first VNF preference parameter carried in the first request message
  • the value is the value of private_net_id and private_net_cidr, and then private_net_id: net1234567 and private_net_cidr: 192.168.0.0/24 can be determined as the value of the deployment parameter of VNF_DF1.yaml.
  • Instantiate_input:get_input(additional_parameters) in VNFD.yaml can be called the mapping relationship between the main file and the target file.
  • VNFM can input private_net_id:net1234567 and private_net_cidr:192.168.0.0/24 through instantiate_input:get_input(additional_parameters) into VNF_DF1.yaml , VNFM uses VNF_DF1.yaml to deploy the first VNF. Assuming that when deploying an NS, an NSD consists of two VNFDs, the process needs to be repeated more than twice.
  • the following describes the VNFM receiving the second request message in two aspects.
  • the second request message is used to request the creation of the identifier of the first VNF.
  • the first aspect is that the VNFM receives the second request message from NFVO
  • the second aspect is that the VNFM receives the second request message.
  • OSS/BSS second request message when an NS needs to be deployed, since an NSD consists of one or more VNFDs, NFVO needs to request VMFM multiple times to create the first VNF ID, one VNFD needs to be requested once, and multiple VNFDs need to be requested multiple times.
  • the OSS/BSS may directly request the VNFM to create a VNF identifier, and there is no need to send the second request message through NFVO.
  • the two aspects are described in detail below.
  • the method before the VNFM receives the first request message, the method further includes:
  • the VNFM receives a second request message sent by the network function virtualization orchestrator NFVO, and the second request message is used to request to create an identifier of the first VNF;
  • the VNFM creates the identifier of the first VNF according to the second request message
  • the VNFM sends the identifier of the first VNF to the NFVO;
  • the receiving of the first request message by the VNFM includes: receiving the first request message sent by the NFVO by the VNFM.
  • the first request message may also be called an instantiation request message, that is, in this manner, the first request message received by the VNFM is from NFVO.
  • the method before the VNFM receives the first request message, the method further includes: the VNFM receives a second request message sent by an operation support system and a service support system OSS/BSS, and the second request message is used for Request to create the identifier of the first VNF;
  • the VNFM creates the identifier of the first VNF according to the second request message
  • the VNFM sends the identifier of the first VNF to the OSS/BSS;
  • the VNFM receiving the first request message includes: the VNFM receiving the first request message sent by the OSS/BSS through a device management system EMS.
  • the first request message may also be called an instantiation request message, that is, in this manner, the first request message received by the VNFM is from the OSS/BSS.
  • the method for deploying VNF provided by the embodiment of the present application can use the first association relationship in the VNFD and the mapping relationship between the main file and the target file to correspond to the value of the preference parameter of the first VNF carried in the first request message
  • the values of the deployment parameters are entered into the target file, so that the VNF can be deployed.
  • the program personnel can be avoided from determining the deployment parameters of the auxiliary file corresponding to the value of the first VNF preference parameter, which can reduce the participation of the program personnel, thereby Can improve the degree of automation, help improve the performance of the system.
  • FIG. 4 shows a method 400 for OSS/BSS deployment VNF provided by an embodiment of the present application, including:
  • the operation support system and the business support system OSS/BSS send a fourth request message to the network function virtualization orchestrator NFVO, and the NFVO receives the fourth request message sent by the OSS/BSS.
  • the fourth request message includes the first VNF A VNFD identifier and the value of the first VNF preference parameter.
  • the NFVO determines the first VNFD according to the identifier of the first VNFD.
  • the NFVO determines deployment parameters corresponding to the value of the preference parameter of the first VNF in the first VNFD according to the value of the preference parameter of the first VNF;
  • the first VNFD is composed of a main file and one or more auxiliary files; the main file includes deployment parameters of each auxiliary file and a first association relationship, and the first association relationship is used to The value of the preference parameter indicating the VNF is associated with the deployment parameter of the auxiliary file.
  • S430 includes: the NFVO determines the deployment parameter corresponding to the value of the first VNF preference parameter in the main file according to the value of the first VNF preference parameter and the first association relationship.
  • the NFVO can determine the deployment parameters corresponding to the value of the first VNF preference parameter according to the value of the first VNF preference parameter and the first association relationship.
  • VNFD_id identity of the first VNFD
  • flavour 1 first VNF carried in the fourth request message Value of preference parameter
  • NFVO determines VNFD according to VNFD_id, which is composed of VNFD.yaml, VNF_DF1.yaml and VNF_DF2.yaml in method 300, of which VNFD.yaml is the main file, VNF_DF1.yaml and VNF_DF2.yaml Supplementary documents.
  • the auxiliary file corresponding to flavour 1 is VNF_DF1.yaml
  • the auxiliary file corresponding to flavour 2 is VNF_DF2.yaml.
  • the NFVO learns from the fourth request message that the preference value of the first VNF is flavour 1
  • there is flavour 1 in VNFD.yaml associated with the deployment parameter of VNF_DF1.yaml, such as type:concat in VNFD.yaml: ['inst_info_',get_input(flavour)] associate flavour1 with private_net_id:type:string private_net_cidr:type:string, so that NFVO can determine the value of the preference parameter of the first VNF and the deployment parameter corresponding to private_net_id :type:string private_net_cidr:type:string, and then send private_net_id:type:string private_net_cidr:type:string to OSS/BSS.
  • mapping relationship between the main file and each of the one or more auxiliary files.
  • the NFVO can determine the first VNFD according to the identifier of the first VNFD in the fourth request message, for example, the identifier of the first VNFD can be a template Identity (ID).
  • ID a template Identity
  • the first VNFD is composed of a main file and one or more auxiliary files.
  • Each preference parameter value corresponds to an auxiliary file, which can be based on the first VNF in the fourth request message.
  • the value of the preference parameter determines the target file in one or more auxiliary files, and then uses the deployment parameter in the target file as the deployment parameter corresponding to the value of the preference parameter of the first VNF, and finally returns it to the OSS/BSS.
  • NFVO may store VNFD and/or NSD, or VNFD and/or NSD may be stored in a database accessible to NFVO.
  • the embodiment of the present application uniformly describes obtaining VNFD from NFVO And/or NSD, whether the specific NFVO stores the VNFD and/or NSD itself, or whether the NFVO stores the VNFD and/or NSD in a database accessible by the NFVO, which is not limited in the embodiments of the present application.
  • the NFVO sends the deployment parameter corresponding to the value of the preference parameter of the first VNF to the OSS/BSS, and the OSS/BSS receives the value of the preference parameter of the first VNF sent by the NFVO Corresponding deployment parameters.
  • the method further includes: the OSS/BSS sends a second request message to the virtual network function manager NFVM, where the second request message is used to request the creation of the first VNF Identification; the OSS/BSS receives the identification of the first VNF sent by the NFVM according to the second request message; the OSS/BSS sends a first request message to the NFVM through the device management system EMS, so The first request message includes the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF.
  • NFVO can send the deployment parameters corresponding to the determined preference parameter values to OSS/BSS, so that OSS/BSS can carry the deployment when sending the first request message Parameters, so that programmers are not required to determine the deployment parameters corresponding to the value of the preference parameter, which can reduce the degree of interference of programmers, thereby improving the degree of automation and helping to improve system performance.
  • the fourth request message passed by OSS/BSS requests the NFVO to deploy the deployment parameters of the VNF.
  • the OSS/BSS sends a fifth request message to the NFVO
  • the NFVO receives the fifth request message sent by the OSS/BSS
  • the fifth request message includes the network A service identifier and a value of a preference parameter of a network service.
  • the network service is composed of one or more VNFs, and the one or more VNFs include the first VNF.
  • the NFVO determines the network service according to the identifier of the network service, and the network service is composed of a main file and one or more auxiliary files.
  • the network service is composed of a main file and one or more auxiliary files; the NFVO is composed according to the preference value of the network service
  • the target file of the network service is determined in the one or more auxiliary files of the network service; the NFVO determines the corresponding file of each of the one or more VNFs in the target file of the network service
  • the network service ID can be the ID of a network service.
  • a network service ID corresponds to a network service.
  • a network service consists of a main file and one or more auxiliary files. Each auxiliary file includes one or more VNF preferences.
  • NFVO can determine a secondary file as the target file according to the value of the preference parameter of the network service in the fifth request message, the target file includes a Or the value of preference parameters of multiple VNFs, etc., NFVO sends the value of the preference parameter corresponding to each VNF in the target file to the OSS/BSS, for example, including the value of the preference parameter of the first VNF.
  • the OSS/BSS may carry the value of the preference parameter of the first VNF in the fourth request message in S410.
  • the NSD is composed of NSD.yaml (main file), NS-DF1.yaml (auxiliary file), and NS_DF2 .yaml (auxiliary file), the deployment file corresponding to the preference parameter flavour1 is NS-DF1.yaml, and the deployment file corresponding to the deployment preference parameter flavour2 is NS_DF2.yaml.
  • NSD.yaml The description of NSD.yaml is as follows:
  • NS_DF2.yaml The description of NS_DF2.yaml is as follows:
  • NFVO determines that the target file is NS_DF1.yaml, and the preference parameter value of VNF_1 included in NS_DF1.yaml Is flavour 1, and the value of the preference parameter of VNF_2 is flavour 2, then NFVO sends VNF_1: flavour 1 to OSS/BSS; VNF_2: flavour 1.
  • the OSS/BSS requests the NFVO for the deployment parameter corresponding to the preference parameter value of the first VNF through the fourth request message
  • the network service also includes the second VNF
  • the following describes the OSS /BSS requests the NFVO for deployment parameters corresponding to the value of the preference parameter of the second VNF through the sixth request message.
  • the OSS/BSS sends a sixth request message to the NFVO, and the NFVO receives a sixth request message sent by the OSS/BSS, where the sixth request message includes the identifier of the second VNFD and the second VNF.
  • the NFVO determines the template of the second VNF according to the identifier of the second VNFD;
  • the second VNFD is composed of a main file and one or more auxiliary files.
  • the main file includes deployment parameters of each auxiliary file and a second association relationship, and the second association relationship is used to indicate the preference of the VNF.
  • the value is associated with the deployment parameters of the auxiliary file;
  • the NFVO determines the deployment parameter corresponding to the value of the preference parameter of the first VNF in the main file of the second VNFD according to the value of the preference parameter of the second VNF and the second association relationship;
  • the NFVO sends the deployment parameter corresponding to the value of the preference parameter of the second VNF to the OSS/BSS, and the OSS/BSS receives the value of the preference parameter of the second VNF sent by the NFVO Deployment parameters.
  • OSS/BSS when OSS/BSS obtains the deployment parameter corresponding to the value of the preference parameter of the first VNF and the deployment parameter corresponding to the value of the preference parameter of the second VNF, OSS/BSS sends the seventh Request message, the NFVO receives a seventh request message sent by the OSS/BSS, the seventh request message includes the value of the preference parameter of the network service and the value of the preference parameter of the first VNF The value of the deployment parameter and the value of the preference parameter of the second VNF correspond to the value of the deployment parameter.
  • the value of the preference parameter of the network service the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF and the value of the deployment parameter corresponding to the value of the preference parameter of the second VNF The value of can be determined according to the current deployment requirements.
  • the method further includes: the NFVO sends a second request message to the VNFM, the second request The message is used to request the identifier of the first VNF; the NFVO receives the identifier of the first VNF sent by the VNFM according to the second request message; the NFVO sends the first request message to the VNFN.
  • the first request message includes the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF.
  • VNFD is composed of a main file and one or more auxiliary files; the network service is also composed of a main file and one or more auxiliary files, and the main file of VNF is different from the main file of the network service, the same auxiliary file Not the same; deploying a network service requires deploying one or more VNFs.
  • the main file is the main file of the network service, when describing the VNFD, the main file is the main file of the VNFD; when describing the network service, the auxiliary file is The auxiliary file of the network service, when describing VNFD, the auxiliary file is the auxiliary file of VNFD.
  • the value of the preference parameter of the network service in the fifth request message may be determined according to the current deployment requirements, and the value of the preference parameter of the first VNF in the first request message corresponds to the deployment The value of the parameter can also be determined according to the current deployment requirements.
  • the seventh request message includes the value of the preference parameter of the network service, the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF, and the value of the preference parameter of the second VNF
  • the values of deployment parameters can also be determined according to the current deployment requirements.
  • the following describes a method 500 for deploying VNF in an embodiment of the present application with reference to FIG. 5, including:
  • the OSS/BSS sends a fifth request message to the NFVO, where the fifth request message includes the network service identifier (NS ID) and the value of the network service preference parameter (for example, NS flavour 1).
  • NS ID network service identifier
  • NS flavour the value of the network service preference parameter
  • the NFVO determines the network service according to the identifier of the network service in the fifth request message.
  • NFVO can determine the network service in the file saved by itself or in the database that NFVO can access according to the network service identification.
  • the NFVO determines the target file in one or more auxiliary files that constitute the network service according to the preferences of the network service.
  • the network service consists of a main file and one or more auxiliary files.
  • the network service may be composed of NSD.yaml, NS-DF1.yaml, and NS_DF2.yaml in the foregoing method 400, where NSD.yaml is the main file of the network service, and NS-DF1.yaml and NS_DF2.yaml are The two auxiliary files of the network service, the deployment file corresponding to the preference parameter flavour1 is NS-DF1.yaml, and the deployment file corresponding to the deployment preference parameter flavour2 is NS_DF2.yaml. It is assumed that the preference value of the aforementioned network service is flavour1. Then NFVO can determine that the target file is NS-DF1.yaml.
  • NFVO determines the value of the preference parameter of each VNF in the target file.
  • the target file includes two VNFs, namely VNF_1 and VNF_2, where the preference parameter of VNF_1 has a value of flavour 1, and the preference parameter of VNF_2 has a value of flavour 1.
  • NFVO sends the value of each VNF preference parameter to OSS/BSS.
  • NFVO returns VNF_1: flavour 1, VNF_2: flavour 1, to the OSS/BSS.
  • the OSS/BSS sends a fourth request message to the NFVO, where the fourth request message includes the identifier of the first VNFD and the value of the preference parameter of the first VNF.
  • the fourth request message may carry the VNFD_id (the identifier of the first VNFD) and flavour 1 (the value of the preference parameter of the first VNF) corresponding to VNF_1.
  • the NFVO determines the first VNFD according to the identifier of the first VNFD, that is, the VNFD stored in the VNFD saved by the NFVO or a database accessible to the first VNFD determines the first VNFD.
  • Each VNFD is composed of a main file and one or more auxiliary files.
  • the main file includes deployment parameters and an association relationship of each auxiliary file.
  • the first association relationship is used to indicate the value of preference parameters of the VNF and the deployment of auxiliary files The parameters are related.
  • the NFVO determines the deployment parameter corresponding to the value of the first VNF preference parameter in the master file according to the value of the first VNF preference parameter and the first association relationship.
  • NFVO determines the VNFD corresponding to VNFD_id.
  • the main file of the VNFD is VNFD.yaml in the method 300.
  • flavour1 in VNFD.yaml is associated with the deployment parameters of VNF_DF1.yaml, such as type:concat:['inst_info_', get_input(flavour) in VNFD.yaml )] (The first association relationship) associates flavour 1 with private_net_id:type:string private_net_cidr:type:string.
  • NFVO can determine that the deployment parameter corresponding to the value of the preference parameter of the first VNF is private_net_id:type:string private_net_cidr:type:string.
  • NFVO sends the deployment parameters corresponding to the value of the preference parameter of the first VNF to OSS/BSS.
  • VNF needs to execute S509-S511 once; multiple VNFs can execute S509-S511 multiple times. For example, for the aforementioned VNF_1:flavour1 and VNF_2:flavour1, you need to execute S509-S511 twice.
  • the OSS/BSS sends a seventh request message to the NFVO, and the VNFO receives the seventh request message sent by the OSS/BSS.
  • the seventh request message includes the value of the preference parameter of the network service and the preference parameter of each VNF The value of the corresponding deployment parameter value.
  • the seventh request message includes the value of the preference parameter of the network service and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF and the value of the preference parameter of the second VNF The value of the deployment parameter.
  • the seventh request message includes the value of the deployment parameter corresponding to the value of the preference parameter of each VNF in the multiple VNFs. The following uses only one VNF as an example for description.
  • the seventh request message includes: NS flavour 1, the value of the deployment parameter for VNF_1: flavour1: private_net_id: net1234567, private_net_cidr: 192.168.0.0/24.
  • NFVO sends a second request message to VNFM, and VNFM receives the second request message sent by NFVO, where the second request message is used to request to create the identifier of the first VNF.
  • the VNFM creates the identifier of the first VNF according to the second request message according to the second request message.
  • the second request message includes the identifier of the first VNFD.
  • the VNFM creates the identifier of the first VNF according to the identifier of the first VNFD.
  • the identifier of the first VNF may be called an instance identifier of the VNF.
  • the identifier of the first VNF is VNF1_id
  • the VNFM sends the identifier of the first VNF to NFVO.
  • the NFVO sends a first request message to the VNFM.
  • the first request message includes: the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the preference parameter of the first VNF.
  • the value of the deployment parameter includes: the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the preference parameter of the first VNF.
  • the first request message includes: the values of the deployment parameters corresponding to VNF1_id, flavour 1, and flavour 1, private_net_id: net1234567, private_net_cidr: 192.168.0.0/24.
  • the programmer may give the value of the preference parameter of the first VNF and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF according to the current demand of the demand side Assignment.
  • the VNFM sends a third request message to the NFVO.
  • the third request message includes the identifier of the first VNF.
  • the third request message is used to request the first VNFD and the first VNFD from the NFVO. It is composed of a main file and one or more auxiliary files.
  • the main file has a mapping relationship with each auxiliary file in the one or more auxiliary files.
  • the main file includes the deployment parameters of each auxiliary file and the first association relationship The first association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameter of the auxiliary file.
  • NFVO returns the first VNFD to VNFM.
  • the VNFM determines a target file in the first or more auxiliary files according to the value of the preference parameter of the first VNF.
  • the main file of the first VNF is VNFD.yaml in the method 300.
  • the auxiliary files are VNF_DF1.yaml and VNF_DF2.yaml in method 300, wherein the auxiliary file corresponding to flavour 1 is VNF_DF1.yaml, and the auxiliary file corresponding to flavour 2 is VNF_DF2.yaml, then the VNFM determines that the target file is VNF_DF1 according to flavour 1. .yaml.
  • the VNFM determines the deployment parameters of the target file from the deployment parameters of each auxiliary file included in the main file according to the first association relationship and the value of the preference parameter of the first VNF.
  • the VNFM determines the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF as the value of the deployment parameter of the target file.
  • the VNFM uses the mapping relationship between the main file and the target file to input the value of the deployment parameter of the target file into the target file, and deploys the location using the value of the deployment parameter of the target file The first VNF is described.
  • the first association relationship is type:concat:['inst_info_', get_input(flavour)] (first association relationship), and the first association relationship is flavour1 and private_net_id:type:stringprivate_net_cidr :type:string is related.
  • the VNFM can determine that the deployment parameter corresponding to the value of the preference parameter of the first VNF is private_net_id:type:string private_net_cidr:type:string.
  • private_net_id: net1234567 and private_net_cidr: 192.168.0.0/24 in the first request message are the values of private_net_id and string private_net_cidr.
  • VNFM successfully uses the mapping relationship between the main file and the target file as: instantiate_input:get_input(additional_parameters) to successfully enter private_net_id:net1234567 and private_net_cidr:192.168.0.0/24 into VNF_DF1.yaml.
  • VNFM uses VNF_DF1.yaml to deploy VNF_1.
  • a network service includes multiple VNFs in S513, one VNF executes S514-S521 once, and multiple VNFs need to execute S514-S521 multiple times.
  • S514-S521 is executed multiple times, a network service can be deployed.
  • the method 600 for deploying a VNF in an embodiment of the present application will be described below with reference to FIG. 6.
  • the difference between the method 500 and the method 600 is that the method 500 is a process of deploying a network service, and the network service is composed of one or more VNFs.
  • the network service needs to deploy the one or more VNFs.
  • the method 600 is a process of deploying only one VNF.
  • the method 600 takes the first VNF in the method 500 example as VNF1 for example.
  • the method 600 specifically includes:
  • OSS/BSS uploads a VNF package (VNF package) to NFVO.
  • VNF package includes VNFD.
  • OSSBSS stores the VNFD in NFVO or a database that NFVO can access.
  • the OSS/BSS sends a first request message to the VNFM, where the first request message includes: the identifier of the first VNF, the value of the preference parameter of the first VNF, and the value of the preference parameter of the first VNF The value of the corresponding deployment parameter.
  • the first request message includes: the values of the deployment parameters corresponding to VNF1_id, flavour 1, and flavour 1, private_net_id: net1234567, private_net_cidr: 192.168.0.0/24.
  • the programmer may give the value of the preference parameter of the first VNF and the value of the deployment parameter corresponding to the value of the preference parameter of the first VNF according to the current demand of the demand side Assignment.
  • FIG. 7 shows a schematic block diagram of an apparatus 700 for deploying VNF provided by an embodiment of the present application.
  • the apparatus 700 may correspond to the virtual network function manager described in the above method 300, or may correspond to a chip or component of the virtual network function manager.
  • each module or unit in the apparatus 800 may be used to perform various actions or processing procedures performed by the virtual network function manager in the above method 300.
  • the apparatus 700 for deploying VNF may include a transceiver unit 710 ⁇ processing unit 720.
  • the transceiver unit 710 is configured to obtain a first VNFD of the first VNF, where the first VNFD is composed of a main file and one or more auxiliary files, and the main file and each of the one or more auxiliary files exist Mapping relationship, the main file includes deployment parameters of each auxiliary file and a first association relationship, and the first association relationship is used to indicate that the value of the preference parameter of the VNF is associated with the deployment parameter of the auxiliary file;
  • the processing unit 720 is configured to deploy the first VNF according to the first VNFD.
  • the transceiver unit 710 is specifically configured to: receive a first request message, where the first request message includes an identifier of the first VNF, a value of a preference parameter of the first VNF, and the first The value of the preference parameter of a VNF corresponds to the value of the deployment parameter;
  • the processing unit 720 is further configured to: determine the first VNFD according to the identifier of the first VNF;
  • the processing unit 720 is specifically configured to: determine a target file in the first or more auxiliary files according to the value of the preference parameter of the first VNF; based on the first association relationship and the main file and The mapping relationship of the target file deploys the first VNF.
  • the processing unit 720 is specifically configured to: in the deployment parameters of each auxiliary file included in the main file according to the first association relationship and the value of the preference parameter of the first VNF Determining the deployment parameters of the target file; determining the deployment parameter value corresponding to the preference parameter value of the first VNF as the deployment parameter value of the target file;
  • mapping relationship between the main file and the target file input the value of the deployment parameter of the target file into the target file, and deploy the first using the value of the deployment parameter of the target file VNF.
  • the transceiver unit 710 is also used to:
  • the processing unit 720 is further configured to: create the identifier of the first VNF according to the second request message;
  • the transceiver unit 710 is further configured to: send the identifier of the first VNF to the NFVO;
  • the transceiver unit 720 is specifically configured to: receive the first request message sent by the NFVO.
  • the transceiving unit 710 is further configured to: before the receiving the first request message, receive a second request message sent by an operation support system and a service support system OSS/BSS, the second request message An identifier for requesting creation of the first VNF;
  • the processing unit 720 is further configured to: create the identifier of the first VNF according to the second request message;
  • the transceiver unit 710 is further configured to: send the identifier of the first VNF to the OSS/BSS;
  • the transceiver unit 710 is specifically configured to receive the first request message sent by the OSS/BSS through a device management system EMS.
  • the transceiver unit 710 is further configured to: before the identifier of the first VNF determines the first VNFD, send a third request message to the NFVO, where the third request message includes the first A VNF identifier, the third request message is used to request the first VNFD from the NFVO;
  • the transceiver unit 710 is specifically configured to receive the first VNFD sent by the NFVO according to the third request message.
  • FIG. 8 shows a schematic block diagram of an apparatus 800 for deploying VNF provided by an embodiment of the present application.
  • the apparatus 800 may correspond to the operation support system and business support system described in the above method 400, and may also correspond to the operation support system and business support system. Chips or components, and each module or unit in the device 800 can be used to perform various actions or processes performed by the operation support system and the business support system in the above method 400, as shown in FIG. 8, the deployment of VNF
  • the device 800 may include a sending unit 810 and a receiving unit 820.
  • the sending unit 810 is configured to send a fourth request message to the network function virtualization orchestrator NFVO, where the fourth request message includes the identifier of the first VNFD of the first VNF and the value of the preference parameter of the first VNF;
  • the receiving unit 820 is configured to receive the deployment parameter corresponding to the value of the preference parameter of the first VNF sent by the NFVO, where the deployment parameter corresponding to the value of the preference parameter of the first VNF is based on the first VNFD And the value of the preference parameter of the first VNF is determined.
  • the sending unit 810 is further configured to: before sending the fourth request message to the network function virtualization orchestrator NFVO, send a fifth request message to the NFVO, where the fifth request message includes A network service identifier and a value of a network service preference parameter, the network service is composed of one or more VNFs, and the one or more VNFs include the first VNF;
  • the receiving unit 820 is further configured to receive the value of the preference parameter of each VNF sent by the NFVO, and the value of the preference parameter of each VNF is the ID and the value of the NFVO according to the network service. The value of the preference parameter of the network service is determined.
  • the sending unit 810 is further configured to: send a sixth request message to the NFVO, where the sixth request message includes the identifier of the second VNFD and the value of the preference parameter of the second VNF ;
  • the receiving unit 820 is further configured to receive the deployment parameter corresponding to the value of the preference parameter of the second VNF sent by the NFVO, wherein the deployment parameter corresponding to the value of the preference parameter of the second VNF is based on The identifier of the second VNFD and the value of the preference parameter of the second VNF are determined, and the one or more VNFs include the second VNF;
  • the sending unit 810 is further configured to: send a seventh request message to the NFVO, where the seventh request message includes the value of the preference parameter of the network service and the value of the preference parameter of the first VNF
  • the value of the deployment parameter and the value of the preference parameter of the second VNF correspond to the value of the deployment parameter.
  • the sending unit 810 is further configured to:
  • a second request message is sent to the virtual network function manager NFVM, where the second request message is used to request the creation of the identifier of the first VNF;
  • the receiving unit 820 is further configured to: receive the identifier of the first VNF sent by the NFVM according to the second request message;
  • the sending unit 810 is further configured to send a first request message to the NFVM through the device management system EMS, where the first request message includes the identifier of the first VNF and the value of the preference parameter of the first VNF 1.
  • the value of the preference parameter of the first VNF corresponds to the value of the deployment parameter.
  • FIG. 9 shows a schematic block diagram of an apparatus 900 for deploying VNF provided by an embodiment of the present application.
  • the apparatus 900 may correspond to the network function virtualization orchestrator described in the above method 400, or may correspond to a chip of the network function virtualization orchestrator. Or components, and each module or unit in the apparatus 900 may be used to perform various actions or processes performed by the network function virtualization orchestrator in the above method 400, as shown in FIG. 9, the apparatus 900 for deploying VNF may The transceiver unit 910 and the processing unit 920 are included.
  • the transceiver unit 910 is configured to receive a fourth request message sent by the operation support system and the service support system OSS/BSS, where the fourth request message includes the identifier of the first VNFD of the first VNF and the preference parameter of the first VNF Value
  • the processing unit 920 is configured to determine the first VNFD according to the identifier of the first VNFD;
  • the processing unit 920 is further configured to determine the deployment parameter corresponding to the value of the first VNF preference parameter in the first VNFD according to the value of the first VNF preference parameter;
  • the transceiver unit 910 is further configured to send the deployment parameter corresponding to the value of the preference parameter of the first VNF to the OSS/BSS.
  • the device 700 of the above solution has the function of implementing the corresponding steps performed by the virtual network function manager in the above method
  • the device 800 of the above solution has the function of implementing the corresponding steps of the operation support system and the business support system of the above method.
  • 900 has a function of implementing the corresponding steps performed by the network function virtualization orchestrator in the above method; the function may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the sending unit may be replaced by a transmitter, the receiving unit may be replaced by a receiver, and other units, such as a determination unit, etc. may be replaced by processors, respectively executed The sending and receiving operations and related processing operations in each method embodiment.
  • the processor may be used for, for example, but not limited to, baseband related processing
  • the transceiver may be used for, for example, but not limited to, radio frequency transceiver.
  • the above-mentioned devices may be respectively arranged on independent chips, or may be arranged at least partly or completely on the same chip.
  • the processor may be further divided into an analog baseband processor and a digital baseband processor, where the analog baseband processor and the transceiver may be integrated on the same chip, and the digital baseband processor may be provided on an independent chip.
  • SOC system chip
  • an embodiment of the present application provides a schematic block diagram of a device 1000 for deploying VNF.
  • the device 1000 includes a processor 1010, a transceiver 1020, and a memory 1030.
  • the processor 1010, the transceiver 1020 and the memory 1030 communicate with each other through an internal connection path.
  • the memory 1030 is used to store instructions.
  • the processor 1010 is used to execute the instructions stored in the memory 1030 to control the transceiver 1020 to send signals and /Or receive signals.
  • the transceiver 1020 is used to obtain a first VNFD of a first VNF
  • the first VNFD is composed of a main file and one or more auxiliary files Composition
  • the main file includes deployment parameters of each auxiliary file and a first association relationship
  • the first association relationship is used for
  • the value of the preference parameter indicating the VNF is associated with the deployment parameter of the auxiliary file
  • the processor 1010 is configured to deploy the first VNF according to the first VNFD.
  • the transceiver 1020 is used to send a fourth request message to the network function virtualization orchestrator NFVO, where the fourth request message includes the first The identifier of the first VNFD of a VNF and the value of the preference parameter of the first VNF; the transceiver 1020 is further configured to receive deployment parameters corresponding to the value of the preference parameter of the first VNF sent by the NFVO, wherein , The deployment parameter corresponding to the value of the preference parameter of the first VNF is determined according to the identifier of the first VNFD and the value of the preference parameter of the first VNF
  • the transceiver 1020 is used to receive a fourth request message sent by an operating support system and a business support system OSS/BSS, the fourth request The message includes the identifier of the first VNFD of the first VNF and the value of the preference parameter of the first VNF; the processor 1010 is used to determine the first VNFD according to the identifier of the first VNFD; the processor 1010 is also used to Determining deployment parameters corresponding to the value of the preference parameter of the first VNF in the first VNFD according to the value of the preference parameter of the first VNF; the transceiver 1020 is also used to send the OSS/BSS Sending deployment parameters corresponding to the value of the preference parameter of the first VNF.
  • the apparatus in FIG. 7 or the apparatus in FIG. 8 or the apparatus in FIG. 9 of the embodiment of the present application may be implemented by the apparatus 1000 in FIG. 10 and may be used to perform the virtual network function manager in the above method embodiment , Operation support system and business support system and the corresponding steps and/or processes of the network function virtualization orchestrator.
  • the present application also provides a computer program product, the computer program product comprising: computer program code, when the computer program code runs on the computer, the computer is caused to perform the method in the above embodiment .
  • the various embodiments in this application can also be combined with each other.
  • the present application also provides a computer readable medium, the computer readable interpretation stores program codes, and when the program codes run on the computer, the computer is caused to execute the method in the above embodiments .
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an existing programmable gate array (Field programmable gate array (FPGA)), or other available Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory may be a random access memory (random access memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate Synchronous dynamic random access memory double data SDRAM, DDR SDRAM
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • direct memory bus random access Take the memory (direct RAMbus, RAM, DR).
  • the computer program product may include one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, 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 from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • 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, a data center, or the like that includes one or more available medium integrations.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic disk), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), or the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic disk
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (SSD)
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, 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 components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional 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 function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供了一种部署虚拟化网络功能VNF的方法和装置。该方法包括：VNFM获取第一VNFD，该第一VNFD由主文件以及一个或多辅文件组成，该主文件与所述一个或多个辅文件中每个辅文件存在映射关系，该主文件包括每个辅文件的部署参数和第一关联关系，该第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；该VNFM可以根据第一关联关系确定第一VNF的喜好参数的取值对应的辅文件的部署参数，这样，可以避免程序人员确定第一VNF的喜好参数的取值对应的辅文件的部署参数，可以降低程序人员的参与程度，从而可以提高自动化程度，有助于提高系统的性能。

Description

部署虚拟化网络功能的方法和装置
本申请要求于2018年12月26日提交中国专利局、申请号为201811597995.9、申请名称为“部署虚拟化网络功能的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机领域，并且更具体地，涉及计算机领域中部署虚拟化网络功能的方法和装置。
背景技术
网络功能虚拟化(network function virtualization，NFV)采用通用的硬件设备及虚拟化技术承载传统网络中专用设备的功能，这样可以降低部署专用设备的成本。具体来说，网络功能虚拟化利用云计算可以实现资源共享，也能实现基于业务需求快速自动部署新的业务。并且在部署业务时能够做到弹性伸缩、故障隔离和自愈等。
NFV中虚拟化的网络服务(network service，NS)可以是一个IP多媒体子系统网络服务(IP multimedia subsystem，IMS)网络，也可以是下一代核心分组网演进(evolved packet core，EPC)网络。一个NS可以包括一个或多个虚拟化网络功能(virtual network function，VNF)模块。在部署NS时，业务请求方需要向业务提供方提供网络服务的描述信息(NS descriptor，NSD)，也称为NS的。NSD主要描述了网络服务的拓扑结构以及包含每个VNF描述信息(VNF descriptor，VNFD)，VNFD也称作VNF的。
一个VNFD由多个文件组成，包括一个主文件和一个或多个辅文件，其中，主文件是解析VNFD的第一个文件，主要包括VNF的类型(type)，属性(properties)，需求(requirement)等参数。每个辅文件表示VNF的相应的部署喜好(deployment flavour)，每个辅文件都可以独立部署一个VNF，在实例化VNF时，根据部署喜好的值确定采用哪个辅文件部署VNF，但是有可能每个辅文件要求的输入参数不同，但是如何设置每个辅文件的输入参数是需要考虑的问题，目前是程序员手动输入辅文件的输入参数，这种情况自动化程度低，而且对程序人员的要求比较高，导致人为因素干扰比较大，从而影响网络服务的性能。
发明内容
本申请提供一种部署虚拟化网络功能的方法和装置，可以提高网络服务的性能。
第一方面，提供了一种部署VNF的方法，包括：虚拟网络功能管理器VNFM获取第一VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
所述VNFM根据所述第一VNFD部署所述第一VNF。
需要说明的是，所述第一VNFD为所述第一VNF的描述信息。
因此，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。当VNFM获取到第一VNF的喜好参数的取值时，可以根据第一关联关系确定第一VNF的喜好参数的取值对应的辅文件的部署参数，这样，可以避免程序人员确定第一VNF的喜好参数的取值对应的辅文件的部署参数，可以降低程序人员的参与程度，从而可以提高自动化程度，有助于提高系统的性能。
可选地，所述主文件可以通过映射关系将第一VNF的喜好参数的取值对应的部署参数取值确定为辅文件的部署参数的取值。
可选地，一个VNF的喜好参数的取值对应一个辅文件。
具体地，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联，即输入一个VNF的喜好参数的取值就可以根据第一关联关系得到该VNF的喜好参数的取值对应的部署参数。
在某些实现方式中，所述VNFM获取第一VNFD，包括：所述VNFM接收第一请求消息，所述第一请求消息包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值；
所述VNFM根据所述第一VNF的标识确定所述第一VNFD；其中，所述VNFM根据所述第一VNFD部署所述第一VNF，包括：
所述VNFM根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件；
所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF。
可选地，第一请求消息还可以包括实例化级别，例如可以是level。
在某些实现方式中，所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF，包括：所述VNFM根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数；所述VNFM将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值；所述VNFM利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
在某些实现方式中，在所述VNFM接收第一请求消息之前，所述方法还包括：所述VNFM接收所述网络功能虚拟化编排器NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；所述VNFM根据所述第二请求消息创建所述第一VNF的标识；所述VNFM向所述NFVO发送所述第一VNF的标识；其中，所述VNFM接收第一请求消息，包括：所述VNFM接收所述NFVO发送的所述第一请求消息。
在某些实现方式中，在所述VNFM接收第一请求消息之前，所述方法还包括：所述VNFM接收运营支持系统和业务支持系统OSS/BSS发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；所述VNFM根据所述第二请求消息创建所述第 一VNF的标识；所述VNFM向所述OSS/BSS发送所述第一VNF的标识；其中，所述VNFM接收第一请求消息，包括：所述VNFM接收所述OSS/BSS通过设备管理系统EMS发送的所述第一请求消息。
在某些实现方式中，在所述VNFM根据所述第一VNF的标识确定所述第一VNFD之前，所述方法还包括：所述VNFM向NFVO发送第三请求消息，所述第三请求消息包括所述第一VNF的标识，所述第三请求消息用于向所述NFVO请求所述第一VNFD；
其中，所述VNFM根据所述第一VNF的标识确定所述第一VNFD，包括：所述VNFM接收所述NFVO根据所述第三请求消息发送的所述第一VNFD。
第二方面，提供了一种部署VNF的方法，包括：运营支持系统和业务支持系统OSS/BSS向网络功能虚拟化编排器NFVO发送第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和第一VNF的喜好参数的取值；
所述OSS/BSS接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数，其中，所述第一VNF的喜好参数的取值对应的部署参数根据所第一VNFD的标识和所述第一VNF的喜好参数的取值确定的。
在某些实现方式中，在所述OSS/BSS向网络功能虚拟化编排器NFVO发送第四请求消息之前，所述方法还包括：
所述OSS/BSS向所述NFVO发送第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
所述OSS/BSS接收所述NFVO发送的所述每个VNF的喜好参数的取值，所述每个VNF的喜好参数的取值为所述NFVO根据所述网络服务的标识和所述网络服务的喜好参数的取值确定的。
在某些实现方式中，所述方法还包括：所述OSS/BSS向所述NFVO发送第六请求消息，所述第六请求消息包括第二VNFD的标识和第二VNF的喜好参数的取值；
所述OSS/BSS接收所述NFVO发送的所述第二VNF的喜好参数的取值对应的部署参数，其中，所述第二VNF的喜好参数的取值对应的部署参数根据所述第二VNFD的标识和所述第二VNF的喜好参数的取值确定的，所述一个或多个VNF包括所述第二VNF；
所述OSS/BSS向所述NFVO发送第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。
在某些实现方式中，在所述OSS/BSS向NFVO发送第四请求消息之后，所述方法还包括：所述OSS/BSS向虚拟网络功能管理器NFVM发送第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述OSS/BSS接收所述NFVM根据所述第二请求消息发送的所述第一VNF的标识；
所述OSS/BSS通过设备管理系统EMS向所述NFVM发送第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值。
第三方面，提供了一种部署VNF的方法，包括：网络功能虚拟化编排器NFVO接收运营支持系统和业务支持系统OSS/BSS发送的第四请求消息，所述第四请求消息包括第 一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值；
所述NFVO根据所述第一VNFD的标识确定所述第一VNFD；
所述NFVO根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；
所述NFVO向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数。
可选地，由于主文件中包括每个辅文件的部署参数，这样，可以根据第一VNF的喜好参数取值，以及第一关联关系，确定该第一VNF的喜好参数的取值对应的部署参数。
可选地，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系。
在某些实现方式中，所述第一VNFD由主文件和一个或多个辅文件组成，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
所述NFVO根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数，包括：
所述NFVO根据所述第一VNF的喜好参数的取值和所述第一关联关系在所述主文件中确定所述第一VNF的喜好参数的取值对应的部署参数。
在某些实现方式中，在所述NFVO接收OSS/BSS发送的第四请求消息之前，所述方法还包括：
所述NFVO接收所述OSS/BSS发送的第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
所述NFVO根据所述网络服务的标识确定所述网络服务的，所述网络服务的由主文件以及一个或多个辅文件组成；
所述NFVO根据所述网络服务的喜好参数的取值在组成所述网络服务的的所述一个或多个辅文件中确定所述网络服务的目标文件；
所述NFVO在所述网络服务的目标文件中确定所述一个或多个VNF中每个VNF对应的喜好参数的取值；
所述NFVO向所述OSS/BSS发送所述每个VNF对应的喜好参数的取值。
在某些实现方式中，在所述NFVO向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数之后，所述方法还包括：
所述NFVO接收所述OSS/BSS发送的第六请求消息，所述第六请求消息包括第二VNFD的标识和所述第二VNF的喜好参数的取值；
所述NFVO根据所述第二VNFD的标识确定所述第二VNF的模板，所述第二VNFD由主文件和一个或多个辅文件组成，所述主文件包括每个辅文件的部署参数和第二关联关系，所述第二关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
所述NFVO根据所述第二VNF的喜好参数的取值和所述第二关联关系在所述第二VNFD的主文件中确定所述第一VNF的喜好参数的取值对应的部署参数；
所述NFVO向所述OSS/BSS发送所述第二VNF的喜好参数的取值对应的部署参数；
所述NFVO接收所述OSS/BSS发送的第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值和所 述第二VNF的喜好参数的取值对应的部署参数的取值。
在某些实现方式中，在所述NFVO接收所述OSS/BSS向发送的第七请求消息之后，所述方法还包括：
所述NFVO向所述VNFM发送第二请求消息，所述第二请求消息用于请求所述第一VNF的标识；
所述NFVO接收所述VNFM根据所述第二请求消息发送的所述第一VNF的标识；
所述NFVO向所述VNFN发送第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值。
第四方面，提供了一种部署虚拟化网络功能的装置，用于执行上述第一方面或第一方面的任一可能的实现方式中的方法。具体地，该装置包括用于执行上述第一方面或第一方面的任一可能的实现方式中的方法的单元。
第五方面，提供了一种部署虚拟化网络功能的装置，用于执行上述第二方面或第二方面的任一可能的实现方式中的方法。具体地，该装置包括用于执行上述第二方面或第二方面的任一可能的实现方式中的方法的单元。
第六方面，提供了一种部署虚拟化网络功能的装置，用于执行上述第三方面或第三方面的任一可能的实现方式中的方法。具体地，该装置包括用于执行上述第三方面或第三方面的任一可能的实现方式中的方法的单元。
第七方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机指令，当该计算机指令在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第八方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机指令，当该计算机指令在计算机上运行时，使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第九方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机指令，当该计算机指令在计算机上运行时，使得计算机执行上述第三方面或第三方面的任意可能的实现方式中的方法。
第十方面，本申请提供一种芯片，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片的网络设备执行上述第一方面及其第一方面的任意可能的实现方式中的方法。
第十一方面，本申请提供一种芯片，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片的网络设备执行上述第二方面及其第二方面的任意可能的实现方式中的方法。
第十二方面，本申请提供一种芯片，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片的网络设备执行上述第三方面及其第三方面的任意可能的实现方式中的方法。
第十三方面，本申请提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行上述第一方面及其第一方面的任意可能的实现方式中的方法。
第十四方面，本申请提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行上述第二方面及其第二方面的任意可能的实现方式中的方法。
第十五方面，本申请提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行上述第三方面及其第三方面的任意可能的实现方式中的方法。
第十六方面，本申请提供一种部署虚拟化网络功能的装置，包括收发器、处理器和存储器。处理器用于控制收发器收发信号，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，使得网络设备执行第一方面及其第一方面任意可能的实现方式中的方法。
第十七方面，本申请提供一种部署虚拟化网络功能的装置，包括收发器、处理器和存储器。处理器用于控制收发器收发信号，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，使得网络设备执行第二方面及其第二方面任意可能的实现方式中的方法。
第十八方面，本申请提供一种部署虚拟化网络功能的装置，包括收发器、处理器和存储器。处理器用于控制收发器收发信号，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，使得网络设备执行第三方面及其第三方面任意可能的实现方式中的方法。
第十九方面，本申请提供一种部署虚拟化网络功能的系统，该系统包括第一方面及其第一方面任意可能的实现方式中的装置，第二方面及其第二方面任意可能的实现方式中的装置以及第三方面及第三方面任意可能的实现方式中的装置；或者
包括：该系统包括第十六方面及其第十六方面任意可能的实现方式中的装置，第十七方面及其第十七方面任意可能的实现方式中的装置以及第十八方面及第十八方面任意可能的实现方式中的装置。
附图说明
图1示出了本申请实施例应用的系统架构示意图。
图2示出了现有的部署虚拟化网络功能的方法示意性流程图。
图3示出了本申请实施例提供的部署虚拟化网络功能的方法示意性流程图。
图4示出了本申请实施例提供的另一部署虚拟化网络功能的方法示意性流程图。
图5示出了本申请实施例提供的又一部署虚拟化网络功能的方法示意性流程图。
图6示出了本申请实施例提供的又一部署虚拟化网络功能的方法示意性流程图。
图7示出了本申请实施例提供的部署虚拟化网络功能的装置示意性框图。
图8示出了本申请实施例提供的另一部署虚拟化网络功能的装置示意性框图。
图9示出了本申请实施例提供的另一部署虚拟化网络功能的装置示意性框图。
图10示出了本申请实施例提供的另一部署虚拟化网络功能的装置示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1示出了一种NFV系统的架构示意图，包括网络功能虚拟化编排器(network function virtualization orchestration，NFVO)102、虚拟网络功能管理器(virtual network function manager，VNFM)104、运营支持系统和业务支持系统(operations support system and business support system，OSS/BSS)124。可选地，该系统还包括虚拟基础设施管理器(virtualized infrastructure manager,VIM)106、网络功能虚拟化基础设施(network functions virtualization infrastructure，NFVI)和设备管理系统(equipment management system，EMS)110中的至少一种。
NFVO102主要负责处理虚拟化业务的生命周期管理，以及网络功能虚拟化的基础设施层(NFV infrastructure，VFVI)中虚拟资源的分配和调度等。NFVO102可以与一个或多个VNFM104通信，以执行资源相关请求，发送配置信息给VNFM104。收集VNF108的状态信息。另外，NFVO102也可与VIM106通信，执行资源分配，和/或预留，交换虚拟化硬件资源配置和状态信息。
VNFM04，负责一个或多个VNF108的生命周期管理，比如实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF108。VNFM104可以与VNF108通信以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM104可以有多个，负责对不同类型的VNF进行生命周期管理。
VIM106，控制和管理VNF108与计算硬件112，存储硬件114，网络硬件116，虚拟计算(virtual computing)118，虚拟存储120，虚拟网络122的交互。例如VIM106执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM104及VIM106可以相互通信，请求资源分配，交换虚拟化硬件资源配置和状态信息。
网络功能虚拟化基础设施(network functions virtualization infrastructure，NFVI)即NFV的基础设施层，包含硬件部件，软件部件或两者组合，以建立虚拟化环境，部署，管理及实现VNF108。硬件资源和虚拟化层用于为VNF108提供虚拟化资源，如虚拟机和其他形式的虚拟容器。硬件资源包括计算(computing)硬件112，存储硬件114，网络硬件116。作为一种实施方式，计算硬件112和存储硬件114的资源可以集中在一起。NFVI中的虚拟化层可以抽象硬件资源，解耦VNF108与底层的物理网络层。
EM110，是传统电信系统中用于对设备进行配置，管理的系统，在NFV架构中，EM110也可以用于对VNF进行配置和管理，以及向VNFM发起新的VNF的实例化等生命周期管理操作。
OSS/BSS124，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
在本申请实施例中都以NFV是基于TOSCA语言的VNFD模型为例进行说明，但是本申请实施例不限于此，还可以是其他语言的VNFD模型。
为了便于理解本申请，在介绍本申请提供的部署虚拟化网络功的方法之前，首先对本申请涉及的概念做简要介绍。
VNFD，一个VNFD由多个TOSCA服务模板(service temple)构成，主要由一个顶级服务模板(top level service template)和一个或多个低级服务模板(low level service  template)，顶级服务模板是解析该VNFD的第一个文件，也称为主文件，其中主要包含该VNF的node_template描述，该VNF node template包含该VNF的type，properties，requirement等参数，如下面的描述。低级服务模板可能包含有多个TOSCA service template，也称为辅文件，每个表示一个VNF的部署喜好(deployment flavour)，每个low level的service template都是可以独立部署的service template，在实例化VNF的时候，根据实例化请求中flavour_id的值，决定选择哪个low level service template进行部署。不同的部署喜好对应VNF部署时的对资源的不同需求，所以不同部署喜好对应的service template的构成有可能是不同的，比如在上例中VNF_DF2.yaml描述的flavour可以是针对更多用户接入的场景，此时需要VDU_1和VDU_2两种VDU资源共同提供服务；VNF_DF1.yaml描述的是小用户量接入的场景，此时只需要部署一个VDU_1提供服务即可。每个low level service template中都通过substitution_mapping和top level service template关联，具体地，通过substitution_mapping中定义的type和properties中flavour_id的值同top level service template关联。比如当VNF实例化请求中指示的部署flavour是flavour 1时，在top level service template中VNF1node template中的flavour_id通过get_input(flavour)获取请求中flavour的值，即flavour 1，此时该top level service template通过type:tosca.nodes.nfv.exampleVNF和flavour_id：flavour 1关联到低级服务模板中的VNF_DF1.yaml,即通过该VNF_DF1.yaml部署该部署喜好的VNF(具体地，包括部署该service template中包含的VDU，VL和CP等资源)。
例如，顶级服务模板(top level service template)的描述如下，例如，VNFD_yaml。
Figure PCTCN2019128356-appb-000001
两个低级服务模板(low level service template)描述如下，例如，VNF_DF1.yaml和VNF_DF2.yaml：
VNF_DF1.yaml的描述:
Figure PCTCN2019128356-appb-000002
Figure PCTCN2019128356-appb-000003
VNF_DF2.yaml的描述:
Figure PCTCN2019128356-appb-000004
Figure PCTCN2019128356-appb-000005
通过上面的VNF_DF1.yaml和VNF_DF2.yaml可以看出：每个low level service template对应的模板在实例化时需要的输入参数也可能不同，比如，VNF_DF1.yaml中定义的input参数为：
Figure PCTCN2019128356-appb-000006
在VNF_DF2.yaml中定义的input参数为：
Figure PCTCN2019128356-appb-000007
不同的低级服务模板的参数的取值需要在请求方在实例化请求中携带，但是不同的低级服务模板需要的输入参数不同，现有技术是程序人员需要有一定的判别能力，根据程序员对低级服务模板的认知，从而将输入参数的取值在实例化请求中向提供方发送。例如，假设当前的喜好参数的取值为flavour 1，则程序员必须知道VNF_DF1.yaml中定义的input参数为：
Figure PCTCN2019128356-appb-000008
程序员才会给这些参数赋值，并在实例化请求中将这些参数的取值发送给提供方。假设程序员的认知能力不足，假设当前的喜好参数的取值为flavour 2，有可能将这些参数被提供给提供方：
Figure PCTCN2019128356-appb-000009
但实际上，flavour 2对应的VNF_DF2.yaml的输入参数为
Figure PCTCN2019128356-appb-000010
例如，下面结合图2描述现有的部署VNF的方法200，包括：
S210，OSS/BSS向NFVO发送NSD，将NSD保存在NFVO中或者NFVO能够访问到的数据库中。
S220，NFVO根据OSS/BSS上传的NSD，创建NS的实例标识。
需要说明的是，一个NSD可以有多个服务模板组成，例如，也可以是由一个顶级服务模板(top level service template)和一个或多个低级服务模板(low level service template)顶级服务模板也称为主文件，低级服务模板也可以称为辅文件。举例来说，下面的描述NSD由NSD.yaml(主文件)、NS-DF1.yaml(辅文件)以及NS_DF2.yaml(辅文件)组成，喜好参数flavour 1对应的部署文件为NS-DF1.yaml，喜好参数flavour 2对应的部署文件为NS_DF2.yaml。
NSD.yaml的描述如下：
Figure PCTCN2019128356-appb-000011
Figure PCTCN2019128356-appb-000012
NS-DF1.yaml的描述如下：
Figure PCTCN2019128356-appb-000013
Figure PCTCN2019128356-appb-000014
NS_DF2.yaml的描述如下：
Figure PCTCN2019128356-appb-000015
Figure PCTCN2019128356-appb-000016
S230，NFVO将创建好的NS的实例标识发送给OSS/BSS。
S240，OSS/BSS向NFVO发送实例化NS的请求消息，该请求消息中携带NS的实例标识、NS的喜好参数(flavour)的取值以及该NS中包括的VNF的部署参数的取值。
NFVO根据NS的喜好参数的取值确定采用哪个辅文件部署该NS，假设NS的喜好参数的取值为flavour 1，则NFVO确定采用NS_DF1.yaml部署该NS。
辅文件中描述了对应的NS部署喜好(deployment flavour)包含的VNF，虚拟连接
(virtual link，VL)等资源信息，其中在VNF的资源信息中包含有VNF部署时的部署喜好(deployment flavour)信息，比如VNF_1的properties中的flavour_id:flavour 1信息。
作为一个专业的程序员，当获知NS的喜好参数的取值为flavour 1，则需要知道NS_DF1中VNF_1的喜好参数的取值(flavour 1)对应的部署参数，并将这些部署参数赋值，携带在S240的请求消息中向NFVO发送，例如前述VNF_1的部署参数为：private_net_id和private_net_cidr，程序员需要给这两个参数赋值。这时对程序员的要求比较高，需要程序员熟悉NSD，以及每个NSD的辅文件中的VNF，以及每个VNF的部署参数。
S250，NFVO根据NS的实例标识获取NSD文件，例如，该NSD文件也可以是基于TOSCA描述的，从NSD中获取包含的VNFD信息。
例如，获取NS_DF1中VNF1的模板信息如下
Figure PCTCN2019128356-appb-000017
S260，在实例化VNF请求前，NFVO向VNFM发送创建请求消息，该创建请求消息用于请求创建VNF实例标识。
S270，VNFM根据请求消息创建VNF实例标示，并将创建好的VNF实例标识返回给NFVO。
S280，NFVO向VNFM发送实例化VNF请求消息，该实例化VNF请求消息中包括第S270中获取的VNF实例标识，NS_DF1.yaml中包含的部署VNF的deployment flavour标示
(flavour_id)和S240中的该NS中包括的VNF的部署参数的取值等信息。
S290，VNFM根据实例化VNF请求中携带的参数实例化VNF。
需要说明的是，一个NS的辅文件由一个或多个VNFD组成，假设一个NS的辅文件由多个VNFD组成，每个VNFD执行一次S260-S280，多个VNFD执行多次S260-S280，这样才完成NS的部署。
由上述可知，这种方式的人为因素干扰比较大，会导致需求方提供的输入参数出现偏差，甚至会导致整个实例化过程无法进行，从而会影响系统的性能。并且这种方式的人力成本较高。因此，面对这种情况，需要一种降低对程序员的依赖程度的方法，期望能够自动识别每个VNF的部署参数，在本申请实施例中，提供了一种部署VNF的方法，能够降低人为因素的干扰，从而有助于提高系统性能。
下面结合附图描述本申请实施例提供的部署VNF的方法。
图3描述了本申请实施例提供的部署VNF的方法300，包括：
S310，VNFM获取第一VNF的第一VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。
例如，主文件可以是前述的顶级服务模板(top level service template)，辅文件可以是前述的低级服务模板(low level service template)。例如，所述第一VNFD可以是顶级服务模板和一个或多个低级服务模板组成的，如可以是下面将要描述的VNFD.yaml、VNF_DF1.yaml以及VNF_DF2.yaml组成的。
应理解，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，可以理解为所述主文件可以通过映射关系将第一VNF的喜好参数的取值对应的部署参数取值确定为辅文件的部署参数的取值。例如，该映射关系可以是主文件与辅文件之间存在着某种联系。
S320，所述VNFM根据所述第一VNFD部署所述第一VNF。
因此，本申请实施例提供的部署VNF的方法，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。当虚拟网络功能管理器获取到第一VNF的喜好参数的取值时，可以根据第一关联关系确定第一VNF的喜好参数的取值对应的辅文件的部署参数，这样，可以避免程序人员确定第一VNF的喜好参数的取值对应的辅文件的部署参数，可以降低程序人员的参与程度，从而可以提高自动化程度，有助于提高系统的性能。
作为一个可选实施例，S310，包括：所述VNFM接收第一请求消息，所述第一请求消息包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值；
所述VNFM根据所述第一VNF的标识确定所述第一VNFD；
其中，S320，包括：所述VNFM根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件；
所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF。
可选地，第一请求消息还可以包括实例化级别，例如可以是level。
作为一个可选实施例，在所述VNFM根据所述第一VNF的标识确定所述第一VNFD之前，所述方法还包括：
所述VNFM向NFVO发送第三请求消息，所述第三请求消息包括所述第一VNF的标识，所述第三请求消息用于向所述NFVO请求所述第一VNFD；
其中，所述VNFM根据所述第一VNF的标识确定所述第一VNFD，包括：所述VNF管理器接收所述NFVO根据所述第三请求消息发送的所述第一VNFD。
具体来说，第一VNFD可以保存在NFVO，当VNFM需要部署第一VNF时，VNFM利用第一VNF的标识向NFVO请求第一VNFD。
作为一个可选实施例，所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF，包括：
所述VNFM根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数；
所述VNFM将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值；
所述VNFM利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
可选的，VNF的标识也可以称为VNF的实例标识。
具体来说，每个VNF的标识与每个VNFD一一对应，首先，当VNFM获取到虚拟第一VNF的标识之后，可以根据第一VNF的标识确定第一VNFD，例如利用第一VNF的标识向NFVO请求第一VNFD，这样VNFM就可以利用第一VNFD部署第一VNF。一个喜好参数的取值对应一个辅文件，其次，当获取到第一VNF的喜好参数的取值时，可以在一个或多个辅文件中确定第一VNF的喜好参数的取值对应的辅文件作为目标文件，例如，前面的描述中，当第一VNF的喜好参数的取值为flavour 1，则可以确定目标文件为VNF_DF1.yaml。再次，当获取到第一VNF的喜好参数的取值之后，主文件中存在VNF的喜好参数的取值与辅文件的部署参数的相关联关系，VNFM可以根据第一喜好参数的取值确定目标文件的部署参数，这样就可以确定第一请求消息中携带的第一VNF的喜好参数对应的部署参数的取值即为所述目标文件的部署参数的取值，最后，可以将目标文件的部署参数的取值通过主文件与目标文件的映射关系输入到目标文件中，VNFM利用目标文件部署第一VNF。
下面进行举例说明。还是以NFV是基于TOSCA语言的VNFD模型为例进行说明，但是本申请实施例不限于此，还可以是其他语言的VNFD模型。
例如，主文件的描述如下，例如主文件为VNFD.yaml：
Figure PCTCN2019128356-appb-000018
Figure PCTCN2019128356-appb-000019
辅文件例如可以为VNF_DF1.yaml和VNF_DF2.yaml：
VNF_DF1.yaml的描述如下：
Figure PCTCN2019128356-appb-000020
Figure PCTCN2019128356-appb-000021
VNF_DF2.yaml的描述
Figure PCTCN2019128356-appb-000022
Figure PCTCN2019128356-appb-000023
结合上述例子中的主文件和辅文件的描述，假设第一请求消息中携带VNF1_id(第一VNF的标识，也可以称为第一VNF的实例标识)、flavour 1(第一VNF的喜好参数的取值)、private_net_id:net1234567(所述第一VNF的喜好参数的取值对应的部署参数的取值)和private_net_cidr:192.168.0.0/24(所述第一VNF的喜好参数的取值对应的部署参数的取 值)。VNFM向NFVO发送第三请求消息，第三请求消息中携带VNF1_id，NFVO根据第三请求消息中的VNF1_id确定VNFD1，并将VNFD1发送给VNFM。例如，VNFD1包括上面的VNFD.yaml、VNF_DF1.yaml以及VNF_DF2.yaml，其中，flavour 1对应的辅文件为VNF_DF1.yaml，flavour 2对应的辅文件为VNF_DF2.yaml。VNFM根据flavour 1确定目标文件为VNF_DF1.yaml。当VNFM获知第一VNF的喜好参数的取值为flavour 1时，VNFD.yaml中存在flavour 1与VNF_DF1.yaml的部署参数相关联，如VNFD.yaml中的type:concat:[‘inst_info_’,get_input(flavour)]将flavour 1与private_net_id:type:string private_net_cidr:type:string相关联起来，这样VNFM就可以确定第一请求消息中携带的所述第一VNF的喜好参数的取值对应的部署参数的取值即为private_net_id和private_net_cidr的取值，然后可以将private_net_id:net1234567和private_net_cidr:192.168.0.0/24确定为VNF_DF1.yaml的部署参数的取值。VNFD.yaml中的instantiate_input:get_input(additional_parameters)可以称为主文件与目标文件的映射关系，VNFM可以将private_net_id:net1234567和private_net_cidr:192.168.0.0/24通过instantiate_input:get_input(additional_parameters)输入到VNF_DF1.yaml中，VNFM利用VNF_DF1.yaml部署第一VNF。假设部署一个NS时，一个NSD由两个VNFD组成，则需要重复执行两次以上的流程。
下面分两方面描述VNFM接收到第二请求消息，第二请求消息用于请求创建所述第一VNF的标识，第一方面为VNFM接收来自NFVO的第二请求消息，第二方面为VNFM接收来自OSS/BSS的第二请求消息。第一方面应用在需要部署一个NS时，由于一个NSD由一个或多个VNFD组成，因此需要NFVO向VMFM多次请求创建第一VNF的标识，一个VNFD需要请求一次，多个VNFD需要请求多次。第二方面应该在需要部署一个VNF时，则OSS/BSS直接向VNFM请求创建VNF的标识即可，不需要通过NFVO来发送第二请求消息。下面具体描述这两方面。
第一方面，在所述VNFM接收第一请求消息之前，所述方法还包括：
所述VNFM接收所述网络功能虚拟化编排器NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述VNFM根据所述第二请求消息创建所述第一VNF的标识；
所述VNFM向所述NFVO发送所述第一VNF的标识；
其中，所述VNFM接收第一请求消息，包括：所述VNFM接收所述NFVO发送的所述第一请求消息。第一请求消息也可以称为实例化请求消息，即在这种方式下，VNFM接收到的第一请求消息是来自NFVO的。
第二方面，在所述VNFM接收第一请求消息之前，所述方法还包括：所述VNFM接收运营支持系统和业务支持系统OSS/BSS发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述VNFM根据所述第二请求消息创建所述第一VNF的标识；
所述VNFM向所述OSS/BSS发送所述第一VNF的标识；
其中，所述VNFM接收第一请求消息，包括：所述VNFM接收所述OSS/BSS通过设备管理系统EMS发送的所述第一请求消息。第一请求消息也可以称为实例化请求消息，即在这种方式下，VNFM接收到的第一请求消息是来自OSS/BSS的。
应理解，本申请实施例在需要部署一个VNF时，执行一次上述方法中的步骤，当需要部署多个VNF时，则需要执行多次上述方法中的步骤。当需要部署一个NS，并且该NS的由多个VNFD组成，则需要执行多次上述方法中的步骤才能完成该NS的部署。
因此，本申请实施例提供的部署VNF的方法，利用VNFD中的第一关联关系以及主文件与目标文件的映射关系，可以将第一请求消息中携带的第一VNF的喜好参数的取值对应的部署参数的取值输入到目标文件中，从而可以部署VNF，这样，可以避免程序人员确定第一VNF的喜好参数的取值对应的辅文件的部署参数，可以降低程序人员的参与程度，从而可以提高自动化程度，有助于提高系统的性能。
上面描述了VNFM部署VNF的方法，下面结合附图描述OSS/BSS和NFVO部署VNF的方法。
图4示出了本申请实施例提供的OSS/BSS部署VNF的方法400，包括：
S410，运营支持系统和业务支持系统OSS/BSS向网络功能虚拟化编排器NFVO发送第四请求消息，NFVO接收OSS/BSS发送的第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值。
S420，所述NFVO根据所述第一VNFD的标识确定所述第一VNFD。
S430，所述NFVO根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；
作为一个可选实施例，所述第一VNFD由主文件和一个或多个辅文件组成；所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。S430包括：所述NFVO根据所述第一VNF的喜好参数的取值和所述第一关联关系在所述主文件中确定所述第一VNF的喜好参数的取值对应的部署参数。
由于主文件中包括每个辅文件的部署参数，这样，NFVO可以根据第一VNF的喜好参数取值，以及第一关联关系，确定该第一VNF的喜好参数的取值对应的部署参数。
举例来说，假设，主文件为方法300中的VNFD.yaml，当NFVO接收到第四请求消息时，该第四请求消息中携带的VNFD_id(第一VNFD的标识)、flavour 1(第一VNF的喜好参数的取值)，则NFVO根据VNFD_id确定VNFD，VNFD由方法300中的VNFD.yaml、VNF_DF1.yaml以及VNF_DF2.yaml组成，其中，VNFD.yaml为主文件，VNF_DF1.yaml和VNF_DF2.yaml为辅文件。其中，flavour 1对应的辅文件为VNF_DF1.yaml，flavour 2对应的辅文件为VNF_DF2.yaml。当NFVO从第四请求消息中获知第一VNF的喜好参数的取值为flavour 1时，VNFD.yaml中存在flavour 1与VNF_DF1.yaml的部署参数相关联，如VNFD.yaml中的type:concat:[‘inst_info_’,get_input(flavour)]将flavour 1与private_net_id:type:string private_net_cidr:type:string相关联起来，这样NFVO就可以确定所述第一VNF的喜好参数的取值对应的部署参数为private_net_id:type:string private_net_cidr:type:string，然后将private_net_id:type:string private_net_cidr:type:string发送给OSS/BSS。
可选地，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系。
需要说明的是，方法400中的第一VNFD描述参考方法300中的描述。
NFVO中保存着多个VNFD或者NFVO能够访问到的数据库中保存着多个VNFD，NFVO可以根据第四请求消息中的第一VNFD的标识确定第一VNFD，例如第一VNFD的标 识可以为模板的身份标识(identity，ID)。当NFVO确定了第一VNFD之后，该第一VNFD由一个主文件和一个或多个辅文件组成，每个喜好参数的取值对应一个辅文件，可以根据第四请求消息中的第一VNF的喜好参数的取值在一个或多个辅文件中确定目标文件，然后将目标文件中的部署参数作为第一VNF的喜好参数取值对应的部署参数，最后返回给OSS/BSS。
可选地，在本申请实施例中，NFVO可以保存VNFD和/或NSD，或者VNFD和/或NSD可以保存在NFVO能够访问到的数据库，本申请实施例为了避免赘述，统一描述从NFVO获取VNFD和/或NSD，具体NFVO是自身保存VNFD和/或NSD，还是在NFVO能够访问到的数据库中保存VNFD和/或NSD，本申请实施例对此不作限制。
S440，所述NFVO向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数，所述OSS/BSS接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数。
作为一个可选实施例，在S410之后，所述方法还包括：所述OSS/BSS向虚拟网络功能管理器NFVM发送第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；所述OSS/BSS接收所述NFVM根据所述第二请求消息发送的所述第一VNF的标识；所述OSS/BSS通过设备管理系统EMS向所述NFVM发送第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值。具体描述参考方法300。
因此，本申请实施例提供的部署VNF的方法，NFVO可以将确定的喜好参数的取值对应的部署参数发送给OSS/BSS，这样，OSS/BSS可以在发送第一请求消息时，携带该部署参数，这样就不需要程序员去确定该喜好参数的取值对应的部署参数，从而可以降低程序员的干扰程度，从而提高自动化程度，有助于提高系统性能。
前面的描述是，当需要部署一个VNF时，在方法400中，OSS/BSS通过的第四请求消息向NFVO请求部署该VNF的部署参数，下面描述当需要部署一个NS时，部署该NS需要部署一个或多个VNF。下面描述当需要部署NS时，OSS/BSS与NFVO的交互流程。
作为一个可选实施例，在S410之前，所述OSS/BSS向所述NFVO发送第五请求消息，所述NFVO接收所述OSS/BSS发送的第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF。所述NFVO根据所述网络服务的标识确定所述网络服务的，所述网络服务的由主文件和一个或多个辅文件组成。所述NFVO根据所述网络服务的标识确定所述网络服务的，所述网络服务的由主文件以及一个或多个辅文件组成；所述NFVO根据所述网络服务的喜好参数的取值在组成所述网络服务的的所述一个或多个辅文件中确定所述网络服务的目标文件；所述NFVO在所述网络服务的目标文件中确定所述一个或多个VNF中每个VNF对应的喜好参数的取值；所述NFVO向所述OSS/BSS发送所述每个VNF对应的喜好参数的取值。
具体来说，NFVO中保存了多个网络服务的，或者NFVO能够访问到的数据库中保存了多个网络服务的模板，NFVO需要根据第五请求消息中的网络服务的标识确定网络服务的，例如网络服务的标识可以是网络服务的ID，一个网络服务的标识对应一个网络服务的，一个网络服务的由主文件以及一个或多个辅文件组成，每个辅文件包括一个或多个VNF的喜好参数的取值等，一个网络服务的喜好参数的取值对应一个辅文件，NFVO可以根据第五 请求消息中网络服务的喜好参数的取值确定一个辅文件作为目标文件，该目标文件中包括一个或多个VNF的喜好参数的取值等，NFVO将该目标文件中的每个VNF对应的喜好参数的取值发送给OSS/BSS，例如，包括第一VNF的喜好参数的取值。这样，OSS/BSS就可以在S410中的第四请求消息中携带该第一VNF的喜好参数的取值。
举例来说，假设NFVO根据所述第五请求消息包括网络服务的标识确定的网络服务的为下面的描述，该NSD由NSD.yaml(主文件)、NS-DF1.yaml(辅文件)以及NS_DF2.yaml(辅文件)组成，喜好参数flavour 1对应的部署文件为NS-DF1.yaml，部署喜好参数flavour2对应的部署文件为NS_DF2.yaml。
NSD.yaml的描述如下：
Figure PCTCN2019128356-appb-000024
NS-DF1.yaml的描述如下：
Figure PCTCN2019128356-appb-000025
Figure PCTCN2019128356-appb-000026
NS_DF2.yaml的描述如下：
Figure PCTCN2019128356-appb-000027
Figure PCTCN2019128356-appb-000028
根据上面的NSD的描述，假设当第五请求消息中的网络服务的喜好参数的取值为flavour 1，则NFVO确定目标文件为NS_DF1.yaml，NS_DF1.yaml中包括的VNF_1的喜好参数的取值为flavour 1，VNF_2的喜好参数的取值为flavour 2，则NFVO向OSS/BSS发送VNF_1：flavour 1；VNF_2:flavour 1。
前面只描述了网络服务包括第一VNF时，OSS/BSS通过第四请求消息向NFVO请求第一VNF的喜好参数的取值对应的部署参数，而网络服务还包括第二VNF时，下面描述OSS/BSS通过第六请求消息向NFVO请求第二VNF的喜好参数的取值对应的部署参数。
所述OSS/BSS向所述NFVO发送第六请求消息，所述NFVO接收所述OSS/BSS发送的第六请求消息，所述第六请求消息包括第二VNFD的标识和所述第二VNF的喜好参数的取值；
所述NFVO根据所述第二VNFD的标识确定所述第二VNF的模板；
所述第二VNFD由主文件和一个或多个辅文件组成，所述主文件包括每个辅文件的部署参数和第二关联关系，所述第二关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
所述NFVO根据所述第二VNF的喜好参数的取值和所述第二关联关系在所述第二VNFD的主文件中确定所述第一VNF的喜好参数的取值对应的部署参数；
所述NFVO向所述OSS/BSS发送所述第二VNF的喜好参数的取值对应的部署参数，所述OSS/BSS接收所述NFVO发送的所述第二VNF的喜好参数的取值对应的部署参数。
作为一个可选实施例，当OSS/BSS获取到第一VNF的喜好参数的取值对应的部署参数和第二VNF的喜好参数的取值对应的部署参数时，OSS/BSS向NFVO发送第七请求消息，所述NFVO接收所述OSS/BSS发送的第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。需要说明的是，所述网络服务的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值可以是根据当前的部署需求确定的。
作为一个可选实施例，在所述NFVO接收所述OSS/BSS向发送的第七请求消息之后，所述方法还包括：所述NFVO向所述VNFM发送第二请求消息，所述第二请求消息用于请求所述第一VNF的标识；所述NFVO接收所述VNFM根据所述第二请求消息发送的所述第一VNF的标识；所述NFVO向所述VNFN发送第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值。具体描述参见方法300的描述。
应理解，VNFD由主文件以及一个或多个辅文件组成；网络服务的也由主文件以及一个或多个辅文件组成，并且VNF的主文件与网络服务的的主文件不同，同样的辅文件也不相同；部署一个网络服务需要部署一个或多个VNF。在本申请实施例中，当描述网络服务的时，主文件即为网络服务的的主文件，当描述VNFD时，主文件即为VNFD的主文件；当描述网络服务的时，辅文件即为网络服务的的辅文件，当描述VNFD时，辅文件即为VNFD的辅文件。
需要说明的是，本申请实施例中，第五请求消息中的网络服务的喜好参数的取值可以是根据当前部署需求确定，第一请求消息中第一VNF的喜好参数的取值对应的部署参数的 取值也可以根据当前部署需求确定。所述第七请求消息包括所述网络服务的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值也可以根据当前部署需求确定。
下面结合图5描述本申请实施例中的部署VNF的方法500，包括：
S501-S503，同S210-S230。
S504，OSS/BSS向NFVO发送第五请求消息，该第五请求消息包括网络服务的标识(NS ID)和网络服务的喜好参数的取值(例如，NS flavour 1)。
S505，NFVO根据第五请求消息中网络服务的标识确定网络服务。
即网络服务的标识与网络服务的一一对应，NFVO可以根据网络服务的标识在自身保存的文件中或者NFVO能够访问到的数据库中确定网络服务。
S506，NFVO根据网络服务的喜好参数在组成所述网络服务的的一个或多个辅文件中确定目标文件。其中，网络服务的由主文件和一个或多个辅文件组成。
例如，网络服务的可以是前述方法400中的NSD.yaml、NS-DF1.yaml和NS_DF2.yaml组成，其中，NSD.yaml为网络服务的的主文件，NS-DF1.yaml和NS_DF2.yaml为网络服务的的两个辅文件，喜好参数flavour 1对应的部署文件为NS-DF1.yaml，部署喜好参数flavour 2对应的部署文件为NS_DF2.yaml。假设前述网络服务的喜好参数的取值为flavour 1。则NFVO可以确定目标文件为NS-DF1.yaml。
S507，NFVO在所述目标文件中确定每个VNF的喜好参数的取值。
例如，根据S506中的例子，目标文件中包括两个VNF分别为VNF_1和VNF_2，其中，VNF_1的喜好参数的取值为flavour 1，VNF_2的喜好参数的取值为flavour 1。
S508，NFVO将每个VNF的喜好参数的取值发送给OSS/BSS。
例如，根据S506和S507中的例子，NFVO向OSS/BSS返回VNF_1:flavour 1,VNF_2:flavour 1。
S509，OSS/BSS向NFVO发送第四请求消息，该第四请求消息包括第一VNFD的标识和所述第一VNF的喜好参数的取值。
例如，根据S506-S508中的例子，第四请求消息可以携带与VNF_1对应的VNFD_id(第一VNFD的标识)和flavour 1(所述第一VNF的喜好参数的取值)。
S510，NFVO根据所述第一VNFD的标识确定所述第一VNFD，即NFVO在自身保存的VNFD中或者能够访问到的数据库中保存的VNFD确定第一VNFD。
其中，每个VNFD由主文件和一个或多个辅文件组成，主文件包括每个辅文件的部署参数和关联关系，第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。
S511，所述NFVO根据所述第一VNF的喜好参数的取值和所述第一关联关系在所述主文件中确定所述第一VNF的喜好参数的取值对应的部署参数。
例如，根据S506-S509中的例子，NFVO确定VNFD_id对应的VNFD。例如，该VNFD的主文件为方法300中的VNFD.yaml。则所述NFVO根据flavour 1和所述第一关联关系，VNFD.yaml中存在flavour 1与VNF_DF1.yaml的部署参数相关联，如VNFD.yaml中的type:concat:[‘inst_info_’，get_input(flavour)](第一关联关系)将flavour 1与private_net_id:type:string private_net_cidr:type:string相关联起来。这样NFVO就可以确定所 述第一VNF的喜好参数的取值对应的部署参数为private_net_id:type:string private_net_cidr:type:string。
S512，NFVO将所述第一VNF的喜好参数的取值对应的部署参数发送给OSS/BSS。
需要说明的是，一个VNF需要执行一次S509-S511；多个VNF可以执行多次S509-S511，例如，前述VNF_1:flavour 1,VNF_2:flavour 1，则需要执行两次S509-S511。
S513，OSS/BSS向NFVO发送第七请求消息，VNFO接收OSS/BSS发送的第七请求消息，该第七请求消息包括所述网络服务的喜好参数的取值和所述每个VNF的喜好参数的取值对应的部署参数的取值。例如：第七请求消息包括所述网络服务的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。若网络服务由多个VNF组成，则第七请求消息中包括多个VNF中每个VNF的喜好参数的取值对应的部署参数的取值，下面仅以一个VNF为例进行描述。
例如，根据S506-S512中的例子，第七请求消息包括：NS flavour 1、针对VNF_1:flavour1的部署参数的取值：private_net_id:net1234567、private_net_cidr:192.168.0.0/24。
S514，NFVO向VNFM发送第二请求消息，VNFM接收NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识。
S515，VNFM根据第二请求消息根据所述第二请求消息创建所述第一VNF的标识。
例如，第二请求消息中包括第一VNFD的标识。这样VNFM根据第一VNFD的标识创建第一VNF的标识，例如第一VNF的标识可以称为VNF的实例标识。
根据前述的例子，例如第一VNF的标识为VNF1_id
S516，VNFM向NFVO发送所述第一VNF的标识。
S517，NFVO向VNFM发送第一请求消息，该第一请求消息包括：包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值。
例如，根据S506-S513中的例子，第一请求消息包括：VNF1_id、flavour 1、flavour 1对应的部署参数的取值private_net_id:net1234567、private_net_cidr:192.168.0.0/24。
需要说明的是，在S517中，程序员可以根据当前的需求方的需求给所述第一VNF的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值赋值。
S518，VNFM向NFVO发送第三请求消息，所述第三请求消息包括所述第一VNF的标识，所述第三请求消息用于向所述NFVO请求所述第一VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联。
S519，NFVO向VNFM返回所述第一VNFD。
S520，所述VNFM根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件。
例如，根据S506-S517中的例子，该述第一VNF的主文件为方法300中的VNFD.yaml。辅文件为方法300中的VNF_DF1.yaml和VNF_DF2.yaml，其中flavour 1对应的辅文件为VNF_DF1.yaml，flavour 2对应的辅文件为VNF_DF2.yaml，则所述VNFM根据flavour 1确定目标文件为VNF_DF1.yaml。
S521，所述VNFM根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数。所述VNFM将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值。所述VNFM利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
例如，根据S506-S520中的例子，第一关联关系为type:concat:[‘inst_info_’，get_input(flavour)](第一关联关系)，第一关联关系将flavour 1与private_net_id:type:string private_net_cidr:type:string相关联起来。这样VNFM就可以确定所述第一VNF的喜好参数的取值对应的部署参数为private_net_id:type:string private_net_cidr:type:string。则第一请求消息中private_net_id:net1234567和private_net_cidr:192.168.0.0/24即为private_net_id和string private_net_cidr的取值。VNFM利用所述主文件与所述目标文件的映射关系如：instantiate_input:get_input(additional_parameters)成功将private_net_id:net1234567和private_net_cidr:192.168.0.0/24输入到VNF_DF1.yaml。VNFM利用VNF_DF1.yaml部署VNF_1。
若在S513中一个网络服务包括多个VNF，一个VNF执行一次S514-S521，多个VNF需要执行多次S514-S521，当执行完多次S514-S521时，则可以完成部署一个网络服务。
下面结合图6描述本申请实施例中的部署VNF的方法600，方法500与方法600的区别在于，方法500为部署一个网络服务的过程，该网络服务由一个或多个VNF组成，则部署一个网络服务需要部署该一个或多个VNF，方法600为只部署一个VNF的过程，方法600以方法500举例中的第一VNF为VNF1为例进行说明，方法600具体包括：
S601，OSS/BSS向NFVO上传VNF包(VNF package)，VNF包包括VNFD，OSSBSS将VNFD保存在NFVO中或者NFVO能够访问到的数据库中。
S602，同S509。
S603，同S510。
S604，同S511。
S605，同S512。
S606，OSS/BSS向VNFM发送第一请求消息，该第一请求消息包括：包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值。
例如，根据S506-S513中的例子，第一请求消息包括：VNF1_id、flavour 1、flavour 1对应的部署参数的取值private_net_id:net1234567、private_net_cidr:192.168.0.0/24。
需要说明的是，在S517中，程序员可以根据当前的需求方的需求给所述第一VNF的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值赋值。
S607，同S518。
S608，同S519。
S609，同S520。
S610，同S521。
以上结合图1至图6，详细得描述了本申请实施例提供的部署VNF的方法，下面结合图7至图10，详细描述本申请实施例提供的部署VNF的装置。
图7示出了本申请实施例提供的部署VNF的装置700的示意性框图，该装置700可以对应上述方法300中描述虚拟网络功能管理器，也可以对应虚拟网络功能管理器的芯片或者组件，并且，该装置800中各个模块或者单元分别可以用于执行上述方法300中虚拟网络功能管理器所执行的各动作或处理过程，如图7所示，该部署VNF的装置700可以包括收发单元710和处理单元720。
收发单元710，用于获取第一VNF的第一VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
处理单元720，用于根据所述第一VNFD部署所述第一VNF。
作为一个可选实施例，所述收发单元710具体用于：接收第一请求消息，所述第一请求消息包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值；
所述处理单元720还用于：根据所述第一VNF的标识确定所述第一VNFD；
所述处理单元720具体用于：根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件；根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF。
作为一个可选实施例，所述处理单元720具体用于：根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数；将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值；
利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
作为一个可选实施例，所述收发单元710还用于：
在所接收第一请求消息之前，接收所述网络功能虚拟化编排器NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述处理单元720还用于：根据所述第二请求消息创建所述第一VNF的标识；
所述收发单元710还用于：向所述NFVO发送所述第一VNF的标识；
所述收发单元720具体用于：接收所述NFVO发送的所述第一请求消息。
作为一个可选实施例，所述收发单元710还用于：在所述接收第一请求消息之前，接收运营支持系统和业务支持系统OSS/BSS发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述处理单元720还用于：根据所述第二请求消息创建所述第一VNF的标识；
所述收发单元710还用于：向所述OSS/BSS发送所述第一VNF的标识；
所述收发单元710具体用于：接收所述OSS/BSS通过设备管理系统EMS发送的所述第一请求消息。
作为一个可选实施例，所述收发单元710还用于：在所述第一VNF的标识确定所述第一VNFD之前，向NFVO发送第三请求消息，所述第三请求消息包括所述第一VNF的标识，所述第三请求消息用于向所述NFVO请求所述第一VNFD；
所述收发单元710具体用于：接收所述NFVO根据所述第三请求消息发送的所述第一VNFD。
应理解，装置700中各单元执行上述相应步骤的具体过程请参照前文中结合图3的方法实施例的描述，为了简洁，这里不加赘述。
图8示出了本申请实施例提供的部署VNF的装置800的示意性框图，该装置800可以对应上述方法400中描述的运营支持系统和业务支持系统，也可以对应运营支持系统和业务支持系统的芯片或者组件，并且，该装置800中各个模块或者单元分别可以用于执行上述方法400中运营支持系统和业务支持系统所执行的各动作或处理过程，如图8所示，该部署VNF的装置800可以包括发送单元810和接收单元820。
发送单元810，用于向网络功能虚拟化编排器NFVO发送第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值；
接收单元820，用于接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数，其中，所述第一VNF的喜好参数的取值对应的部署参数根据所第一VNFD的标识和所述第一VNF的喜好参数的取值确定的。
作为一个可选实施例，所述发送单元810还用于：在所向网络功能虚拟化编排器NFVO发送第四请求消息之前，向所述NFVO发送第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
所述接收单元820还用于：接收所述NFVO发送的所述每个VNF的喜好参数的取值，所述每个VNF的喜好参数的取值为所述NFVO根据所述网络服务的标识和所述网络服务的喜好参数的取值确定的。
作为一个可选实施例，所述发送单元810还用于：向所述NFVO发送第六请求消息，所述第六请求消息包括第二VNFD的标识和所述第二VNF的喜好参数的取值；
所述接收单元820还用于：接收所述NFVO发送的所述第二VNF的喜好参数的取值对应的部署参数，其中，所述第二VNF的喜好参数的取值对应的部署参数根据所第二VNFD的标识和所述第二VNF的喜好参数的取值确定的，所述一个或多个VNF包括所述第二VNF；
所述发送单元810还用于：向所述NFVO发送第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。
作为一个可选实施例，所述发送单元810还用于：
在所述向NFVO发送第四请求消息之后，向虚拟网络功能管理器NFVM发送第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
所述接收单元820还用于：接收所述NFVM根据所述第二请求消息发送的所述第一VNF的标识；
所述发送单元810还用于：通过设备管理系统EMS向所述NFVM发送第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值。
应理解，装置800中各单元执行上述相应步骤的具体过程请参照前文中结合图4的方 法实施例的描述，为了简洁，这里不加赘述。
图9示出了本申请实施例提供的部署VNF的装置900的示意性框图，该装置900可以对应上述方法400中描述的网络功能虚拟化编排器，也可以对应网络功能虚拟化编排器的芯片或者组件，并且，该装置900中各个模块或者单元分别可以用于执行上述方法400中网络功能虚拟化编排器所执行的各动作或处理过程，如图9所示，该部署VNF的装置900可以包括收发单元910和处理单元920。
收发单元910，用于接收运营支持系统和业务支持系统OSS/BSS发送的第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值；
处理单元920，用于根据所述第一VNFD的标识确定所述第一VNFD；
所述处理单元920还用于根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；
所述收发单元910还用于向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数。
应理解，装置900中各单元执行上述相应步骤的具体过程请参照前文中结合图4的方法实施例的描述，为了简洁，这里不加赘述。
上述方案的装置700具有实现上述方法中虚拟网络功能管理器执行的相应步骤的功能，上述方案的装置800具有实现上述方法中运营支持系统和业务支持系统执行的相应步骤的功能，上述方案的装置900具有实现上述方法中网络功能虚拟化编排器执行的相应步骤的功能；所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如发送单元可以由发射机替代，接收单元可以由接收机替代，其它单元，如确定单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
在具体实现过程中，处理器可用于进行，例如但不限于，基带相关处理，收发器可用于进行，例如但不限于，射频收发。上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。例如，处理器可以进一步划分为模拟基带处理器和数字基带处理器，其中模拟基带处理器可以与收发器集成在同一块芯片上，数字基带处理器可以设置在独立的芯片上。随着集成电路技术的不断发展，可以在同一块芯片上集成的器件越来越多，例如，数字基带处理器可以与多种应用处理器(例如但不限于图形处理器，多媒体处理器等)集成在同一块芯片之上。这样的芯片可以称为系统芯片(system on chip，SOC)。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的具体需要。本申请实施例对上述器件的具体实现形式不做限定。
可以理解的是，对于前述实施例中所涉及的处理器可以通过具有处理器和通信接口的硬件平台执行程序指令来分别实现其在本申请前述实施例中任一设计中涉及的功能，基于此，如图10所示，本申请实施例提供了一种部署VNF的装置1000的示意性框图，所述装置1000包括：处理器1010、收发器1020和存储器1030。其中，处理器1010、收发器1020和存储器1030通过内部连接通路互相通信，该存储器1030用于存储指令，该处理器1010用于执行该存储器1030存储的指令，以控制该收发器1020发送信号和/或接收信 号。
其中，在一种可能的实现方式中，若该装置1000为虚拟网络功能管理器，收发器1020用于获取第一VNF的第一VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；处理器1010用于根据所述第一VNFD部署所述第一VNF。
在另外一种可能的实现方式中，若该装置1000为运营支持系统和业务支持系统，收发器1020用于向网络功能虚拟化编排器NFVO发送第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值；收发器1020还用于接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数，其中，所述第一VNF的喜好参数的取值对应的部署参数根据所第一VNFD的标识和所述第一VNF的喜好参数的取值确定的
在另外一种可能的实现方式中，若该装置1000为网络功能虚拟化编排器，收发器1020用于接收运营支持系统和业务支持系统OSS/BSS发送的第四请求消息，所述第四请求消息包括第一VNF的第一VNFD的标识和所述第一VNF的喜好参数的取值；处理器1010用于根据所述第一VNFD的标识确定所述第一VNFD；处理器1010还用于根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；所述收发器1020还用于向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数。
应理解，本申请实施例图7中的装置或图8中的装置或图9中的装置可以通过图10中的装置1000来实现，并且可以用于执行上述方法实施例中虚拟网络功能管理器、运营支持系统和业务支持系统和网络功能虚拟化编排器对应的各个步骤和/或流程。
可以理解的是，本申请实施例描述的各种设计涉及的方法，流程，操作或者步骤，能够以一一对应的方式，通过计算机软件，电子硬件，或者计算机软件和电子硬件的结合来一一对应实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件，比如，考虑通用性好成本低软硬件解耦等方面，可以采纳执行程序指令的方式来实现，又比如，考虑系统性能和可靠性等方面，可以采纳使用专用电路来实现。普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，此处不做限定。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述实施例中的方法。本申请中的各个实施例也可以互相结合。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读解释存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述实施例中的方法。
在本申请实施例中，应注意，本申请实施例上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(Field  programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。RAM有多种不同的类型，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本申请中出现的术语“第一”、“第二”等仅是为了区分不同的对象，“第一”、“第二”本身并不对其修饰的对象的实际顺序或功能进行限定。本申请中被描述为“示例性的”，“示例”，“例如”，“可选地”或者“在某些实现方式中”的任何实施例或设计方案都不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用这些词旨在以具体方式呈现相关概念。
在本申请中可能出现的对各种消息/信息/设备/网元/系统/装置/操作/等各类客体进行了赋名，可以理解的是，这些具体的名称并不构成对相关客体的限定，所赋名称可随着场景，语境或者使用习惯等因素而变更，对本申请中技术术语的技术含义的理解，应主要从其在技术方案中所体现/执行的功能和技术效果来确定。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用 介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种部署虚拟化网络功能VNF的方法，其特征在于，包括：
    虚拟网络功能管理器VNFM获取第一VNF的第一虚拟化网络功能描述信息VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
    所述VNFM根据所述第一VNFD部署所述第一VNF。
  2. 根据权利要求1所述的方法，其特征在于，所述VNFM获取第一VNFD，包括：
    所述VNFM接收第一请求消息，所述第一请求消息包括所述第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值；
    所述VNFM根据所述第一VNF的标识确定所述第一VNFD；
    其中，所述VNFM根据所述第一VNFD部署所述第一VNF，包括：
    所述VNFM根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件；
    所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF。
  3. 根据权利要求2所述的方法，其特征在于，所述VNFM根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF，包括：
    所述VNFM根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数；
    所述VNFM将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值；
    所述VNFM利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
  4. 根据权利要求2或3所述的方法，其特征在于，在所述VNFM接收第一请求消息之前，所述方法还包括：
    所述VNFM接收所述网络功能虚拟化编排器NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
    所述VNFM根据所述第二请求消息创建所述第一VNF的标识；
    所述VNFM向所述NFVO发送所述第一VNF的标识；
    其中，所述VNFM接收第一请求消息，包括：
    所述VNFM接收所述NFVO发送的所述第一请求消息。
  5. 根据权利要求2或3所述的方法，其特征在于，在所述VNFM接收第一请求消息之前，所述方法还包括：
    所述VNFM接收运营支持系统和业务支持系统OSS/BSS发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
    所述VNFM根据所述第二请求消息创建所述第一VNF的标识；
    所述VNFM向所述OSS/BSS发送所述第一VNF的标识；
    其中，所述VNFM接收第一请求消息，包括：
    所述VNFM接收所述OSS/BSS通过设备管理系统EMS发送的所述第一请求消息。
  6. 根据权利要求2至4中任一项所述的方法，其特征在于，在所述VNFM根据所述第一VNF的标识确定所述第一VNFD之前，所述方法还包括：
    所述VNFM向NFVO发送第三请求消息，所述第三请求消息包括所述第一VNF的标识，所述第三请求消息用于向所述NFVO请求所述第一VNFD；
    其中，所述VNFM根据所述第一VNF的标识确定所述第一VNFD，包括：
    所述VNFM接收所述NFVO根据所述第三请求消息发送的所述第一VNFD。
  7. 一种部署虚拟化网络功能VNF的方法，其特征在于，包括：
    运营支持系统和业务支持系统OSS/BSS向网络功能虚拟化编排器NFVO发送第四请求消息，所述第四请求消息包括第一VNF的第一虚拟化网络功能描述信息VNFD的标识和所述第一VNF的喜好参数的取值；
    所述OSS/BSS接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数，其中，所述第一VNF的喜好参数的取值对应的部署参数根据所述第一VNFD的标识和所述第一VNF的喜好参数的取值确定的。
  8. 根据权利要求7所述的方法，其特征在于，在所述OSS/BSS向NFVO发送第四请求消息之前，所述方法还包括：
    所述OSS/BSS向所述NFVO发送第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
    所述OSS/BSS接收所述NFVO发送的所述每个VNF的喜好参数的取值，所述每个VNF的喜好参数的取值为所述NFVO根据所述网络服务的标识和所述网络服务的喜好参数的取值确定的。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述OSS/BSS向所述NFVO发送第六请求消息，所述第六请求消息包括第二VNFD的标识和所述第二VNF的喜好参数的取值；
    所述OSS/BSS接收所述NFVO发送的所述第二VNF的喜好参数的取值对应的部署参数，其中，所述第二VNF的喜好参数的取值对应的部署参数根据所第二VNFD的标识和所述第二VNF的喜好参数的取值确定的，所述一个或多个VNF包括所述第二VNF；
    所述OSS/BSS向所述NFVO发送第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。
  10. 一种部署虚拟化网络功能VNF的方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收运营支持系统和业务支持系统OSS/BSS发送的第四请求消息，所述第四请求消息包括第一VNF的第一虚拟化网络功能描述信息VNFD的标识和第一VNF的喜好参数的取值；
    所述NFVO根据所述第一VNFD的标识确定所述第一VNFD；
    所述NFVO根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；
    所述NFVO向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数。
  11. 根据权利要求10所述的方法，其特征在于，所述第一VNFD由主文件和一个或多个辅文件组成，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
    所述NFVO根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数，包括：
    所述NFVO根据所述第一VNF的喜好参数的取值和所述第一关联关系在所述主文件中确定所述第一VNF的喜好参数的取值对应的部署参数。
  12. 根据权利要求10或11所述的方法，其特征在于，在所述NFVO接收OSS/BSS发送的第四请求消息之前，所述方法还包括：
    所述NFVO接收所述OSS/BSS发送的第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
    所述NFVO根据所述网络服务的标识确定所述网络服务的，所述网络服务的由主文件以及一个或多个辅文件组成；
    所述NFVO根据所述网络服务的喜好参数的取值在组成所述网络服务的的所述一个或多个辅文件中确定所述网络服务的目标文件；
    所述NFVO在所述网络服务的目标文件中确定所述一个或多个VNF中每个VNF对应的喜好参数的取值；
    所述NFVO向所述OSS/BSS发送所述每个VNF对应的喜好参数的取值。
  13. 一种部署虚拟化网络功能VNF的装置，其特征在于，包括：
    收发单元，用于获取第一VNF的第一虚拟化网络功能描述信息VNFD，所述第一VNFD由主文件以及一个或多辅文件组成，所述主文件与所述一个或多个辅文件中每个辅文件存在映射关系，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
    处理单元，用于根据所述第一VNFD部署所述第一VNF。
  14. 根据权利要求13所述的装置，其特征在于，所述收发单元具体用于：
    接收第一请求消息，所述第一请求消息包括第一VNF的标识、所述第一VNF的喜好参数的取值、所述第一VNF的喜好参数的取值对应的部署参数的取值；
    所述处理单元还用于：根据所述第一VNF的标识确定所述第一VNFD；
    所述处理单元具体用于：
    根据所述第一VNF的喜好参数的取值在所述第一个或多个辅文件中确定目标文件；
    根据所述第一关联关系以及所述主文件与所述目标文件的映射关系，部署所述第一VNF。
  15. 根据权利要求14所述的装置，其特征在于，所述处理单元具体用于：
    根据所述第一关联关系以及所述第一VNF的喜好参数的取值在所述主文件包括的每个辅文件的部署参数中确定目标文件的部署参数；
    将所述第一VNF的喜好参数的取值对应的部署参数的取值确定为所述目标文件的部署参数的取值；
    利用所述主文件与所述目标文件的映射关系，将所述目标文件的部署参数的取值输入到所述目标文件中，并利用所述目标文件的部署参数的取值部署所述第一VNF。
  16. 根据权利要求14或15所述的装置，其特征在于，所述收发单元还用于：
    在所接收第一请求消息之前，接收所述网络功能虚拟化编排器NFVO发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
    所述处理单元还用于：根据所述第二请求消息创建所述第一VNF的标识；
    所述收发单元还用于：向所述NFVO发送所述第一VNF的标识；
    所述收发单元具体用于：接收所述NFVO发送的所述第一请求消息。
  17. 根据权利要求14或15所述的装置，其特征在于，所述收发单元还用于：
    在所述接收第一请求消息之前，接收运营支持系统和业务支持系统OSS/BSS发送的第二请求消息，所述第二请求消息用于请求创建所述第一VNF的标识；
    所述处理单元还用于：
    根据所述第二请求消息创建所述第一VNF的标识；
    所述收发单元还用于：向所述OSS/BSS发送所述第一VNF的标识；
    所述收发单元具体用于：接收所述OSS/BSS通过设备管理系统EMS发送的所述第一请求消息。
  18. 根据权利要求14至16中任一项所述的装置，其特征在于，所述收发单元还用于：
    在所述第一虚拟化网络功能的标识确定所述第一虚拟化网络功能的之前，向NFVO发送第三请求消息，所述第三请求消息包括所述第一虚拟化网络功能的标识，所述第三请求消息用于向所述NFVO请求所述第一虚拟化网络功能的；
    所述收发单元具体用于：
    接收所述NFVO根据所述第三请求消息发送的所述VNFD。
  19. 一种部署虚拟化网络功能VNF的装置，其特征在于，包括：
    发送单元，用于向网络功能虚拟化编排器NFVO发送第四请求消息，所述第四请求消息包括第一VNF的第一虚拟化网络功能描述信息VNFD的标识和所述第一VNF的喜好参数的取值；
    接收单元，用于接收所述NFVO发送的所述第一VNF的喜好参数的取值对应的部署参数，其中，所述第一VNF的喜好参数的取值对应的部署参数根据所第一VNFD的标识和所述第一VNF的喜好参数的取值确定的。
  20. 根据权利要求19所述的装置，其特征在于，所述发送单元还用于：
    在所向网络功能虚拟化编排器NFVO发送第四请求消息之前，向所述NFVO发送第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
    所述接收单元还用于：接收所述NFVO发送的所述每个VNF的喜好参数的取值，所述每个VNF的喜好参数的取值为所述NFVO根据所述网络服务的标识和所述网络服务的喜好参数的取值确定的。
  21. 根据权利要求20所述的装置，其特征在于，所述发送单元还用于：
    向所述NFVO发送第六请求消息，所述第六请求消息包括第二VNFD的标识和所述第二VNF的喜好参数的取值；
    所述接收单元还用于：
    接收所述NFVO发送的所述第二VNF的喜好参数的取值对应的部署参数，其中，所述第二VNF的喜好参数的取值对应的部署参数根据所第二VNFD的标识和所述第二VNF的喜好参数的取值确定的，所述一个或多个VNF包括所述第二VNF；
    所述发送单元还用于：向所述NFVO发送第七请求消息，所述第七请求消息包括所述网络服务的喜好参数的取值和所述第一VNF的喜好参数的取值对应的部署参数的取值和所述第二VNF的喜好参数的取值对应的部署参数的取值。
  22. 一种部署虚拟化网络功能VNF的装置，其特征在于，包括：
    收发单元，用于接收运营支持系统和业务支持系统OSS/BSS发送的第四请求消息，所述第四请求消息包括第一VNF的第一虚拟化网络功能描述信息VNFD的标识和所述第一VNF的喜好参数的取值；
    处理单元，用于根据所述第一VNFD的标识确定所述第一VNFD；
    所述处理单元还用于根据所述第一VNF的喜好参数的取值在所述第一VNFD中确定所述第一VNF的喜好参数的取值对应的部署参数；
    所述收发单元还用于向所述OSS/BSS发送所述第一VNF的喜好参数的取值对应的部署参数。
  23. 根据权利要求22所述的装置，其特征在于，所述第一VNFD由主文件和一个或多个辅文件组成，所述主文件包括每个辅文件的部署参数和第一关联关系，所述第一关联关系用于指示VNF的喜好参数的取值与辅文件的部署参数相关联；
    所述处理单元具体用于：
    根据所述第一VNF的喜好参数的取值和所述第一关联关系在所述主文件中确定所述第一VNF的喜好参数的取值对应的部署参数。
  24. 根据权利要求22或23所述的装置，其特征在于，所述收发单元还用于：
    在所述接收OSS/BSS发送的第四请求消息之前，接收所述OSS/BSS发送的第五请求消息，所述第五请求消息包括网络服务的标识和网络服务的喜好参数的取值，所述网络服务由一个或多个VNF组成，所述一个或多个VNF包括所述第一VNF；
    所述处理单元还用于：
    根据所述网络服务的标识确定所述网络服务的，所述网络服务的由主文件以及一个或多个辅文件组成；
    根据所述网络服务的喜好参数的取值在组成所述网络服务的的所述一个或多个辅文件中确定所述网络服务的目标文件；
    在所述网络服务的目标文件中确定所述一个或多个VNF中每个VNF对应的喜好参数的取值；
    所述收发单元还用于：向所述OSS/BSS发送所述每个VNF对应的喜好参数的取值。
  25. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求1至6中任一项所述的方法被执行。
  26. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求7至9中任一项所述的方法被执行。
  27. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合，所述存储器用于存储计算机程序或指令，所述处理器用于执行存储器中的所述计算机程序或指令，使得权利要求10至12中任一项所述的方法被执行。
  28. 一种计算机可读存储介质，其特征在于，存储有用于实现权利要求1至6中任一项所述的方法的程序或者指令。
  29. 一种计算机可读存储介质，其特征在于，存储有用于实现权利要求7至9中任一项所述的方法的程序或者指令。
  30. 一种计算机可读存储介质，其特征在于，存储有用于实现权利要求10至12中任一项所述的方法的程序或者指令。
PCT/CN2019/128356 2018-12-26 2019-12-25 部署虚拟化网络功能的方法和装置 WO2020135517A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19901817.7A EP3893437B1 (en) 2018-12-26 2019-12-25 Method and device for deploying virtual network function
US17/361,181 US20210326306A1 (en) 2018-12-26 2021-06-28 Method and apparatus for deploying virtualised network function

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811597995.9A CN111371578B (zh) 2018-12-26 2018-12-26 部署虚拟化网络功能的方法和装置
CN201811597995.9 2018-12-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/361,181 Continuation US20210326306A1 (en) 2018-12-26 2021-06-28 Method and apparatus for deploying virtualised network function

Publications (1)

Publication Number Publication Date
WO2020135517A1 true WO2020135517A1 (zh) 2020-07-02

Family

ID=71128744

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128356 WO2020135517A1 (zh) 2018-12-26 2019-12-25 部署虚拟化网络功能的方法和装置

Country Status (4)

Country Link
US (1) US20210326306A1 (zh)
EP (1) EP3893437B1 (zh)
CN (2) CN111371578B (zh)
WO (1) WO2020135517A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110661641B (zh) * 2018-06-29 2021-07-16 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
CN115037788A (zh) * 2021-03-04 2022-09-09 华为技术有限公司 一种创建网络服务ns的方法及相关装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105790976A (zh) * 2014-12-23 2016-07-20 中国电信股份有限公司 实现虚拟网络功能描述文件自动更新的方法和系统
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
US20180309646A1 (en) * 2016-08-18 2018-10-25 Telefonaktiebolaget L M Ericsson (Publ) A Network Service Design and Deployment Process for NFV Systems

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9830177B1 (en) * 2013-11-12 2017-11-28 Vce Company, Llc Computer implemented method and system, and computer program product, for determining compliance with a configuration parameter before deployment of a virtual appliance into a network appliance
CN105656646B (zh) * 2014-11-10 2019-02-05 中国移动通信集团公司 一种虚拟网元的部署方法及装置
JP6463509B2 (ja) * 2015-05-07 2019-02-06 ホアウェイ・テクノロジーズ・カンパニー・リミテッド 動的仮想化ネットワーク機能記述子管理のためのシステムおよび方法
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
CN105072140A (zh) * 2015-06-30 2015-11-18 浪潮(北京)电子信息产业有限公司 一种部署虚拟化平台的方法和装置
CN105429780B (zh) * 2015-10-30 2019-04-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
CN105955824B (zh) * 2016-04-21 2019-07-19 华为技术有限公司 一种虚拟资源配置方法以及装置
CN107689882B (zh) * 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105790976A (zh) * 2014-12-23 2016-07-20 中国电信股份有限公司 实现虚拟网络功能描述文件自动更新的方法和系统
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
US20180309646A1 (en) * 2016-08-18 2018-10-25 Telefonaktiebolaget L M Ericsson (Publ) A Network Service Design and Deployment Process for NFV Systems

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20210326306A1 (en) 2021-10-21
CN114157573A (zh) 2022-03-08
CN111371578B (zh) 2021-11-30
CN111371578A (zh) 2020-07-03
EP3893437B1 (en) 2024-04-24
EP3893437A4 (en) 2022-01-26
EP3893437A1 (en) 2021-10-13

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
EP3291499B1 (en) Method and apparatus for network service capacity expansion
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US11301303B2 (en) Resource pool processing to determine to create new virtual resource pools and storage devices based on currebt pools and devices not meeting SLA requirements
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
EP3471345B1 (en) Sla-based resource allocation method and nfvo
WO2018006381A1 (zh) 一种网络资源的管理方法、装置及系统
US10397132B2 (en) System and method for granting virtualized network function life cycle management
US10924966B2 (en) Management method, management unit, and system
WO2017181875A1 (zh) 虚拟化网络的部署方法和部署系统
WO2019174000A1 (zh) 用于业务管理的方法和装置
US20210289435A1 (en) Virtualization management method and apparatus
US20230261950A1 (en) Method of container cluster management and system thereof
JP2019512193A (ja) ネットワークバーチャル化シナリオにおけるリソース配置制御
WO2021185083A1 (zh) Vnf实例化方法及装置
WO2021088444A1 (zh) 实例化ns的方法及nfvo
US20210326306A1 (en) Method and apparatus for deploying virtualised network function
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
US20230105269A1 (en) Virtualized network service deployment method and apparatus
US20230409371A1 (en) Method for creating network service ns and related apparatus
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv系统
WO2021129868A1 (zh) 网络服务实例化的方法及网络功能虚拟化编排器
WO2024104311A1 (zh) 部署虚拟化网络功能的方法和通信装置
CN118118348A (zh) 一种虚拟化网络功能vnf的实例化方法及装置
CN116841689A (zh) 一种部署vnf的方法、装置及设备

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

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

Country of ref document: EP

Effective date: 20210707