WO2017114219A1 - 部署网络服务的方法和装置 - Google Patents

部署网络服务的方法和装置 Download PDF

Info

Publication number
WO2017114219A1
WO2017114219A1 PCT/CN2016/110797 CN2016110797W WO2017114219A1 WO 2017114219 A1 WO2017114219 A1 WO 2017114219A1 CN 2016110797 W CN2016110797 W CN 2016110797W WO 2017114219 A1 WO2017114219 A1 WO 2017114219A1
Authority
WO
WIPO (PCT)
Prior art keywords
sub
vnf
deployment
deployed
template
Prior art date
Application number
PCT/CN2016/110797
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 华为技术有限公司
Publication of WO2017114219A1 publication Critical patent/WO2017114219A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time

Definitions

  • the present invention relates to the field of Network Function Virtualization (NFV) and, more particularly, to a method and apparatus for deploying a network.
  • NFV Network Function Virtualization
  • NFV By using versatile hardware such as x86 and virtualization technology, NFV makes network device functions no longer dependent on dedicated hardware, resources can be fully flexibly shared, rapid development and deployment of new services, and automatic deployment based on actual business needs.
  • ETSI European Telecommunications Standards Institute
  • each NS can be configured by a series of virtualized network functions (VNFs). It is composed of physical network function (PNF) network element nodes. Due to the differences in the requirements of different users, the location and performance of the network element nodes to be deployed in each NS may be different.
  • VNF virtualized network functions
  • the existing NFV Management and Orchestration (MANO) system defines the basic framework for automatic deployment of network services. After determining the performance requirements of the network services to be deployed, the deployment location of the VNF required for the entire network service is fixed. Network services cannot be deployed for users distributed in specified locations according to actual network service planning requirements.
  • the embodiments of the present invention provide a method and an apparatus for deploying a network service, which can deploy network services for users distributed in a specified location.
  • the first aspect provides a method for deploying a network service, where the method includes: receiving a deployment request message, where the deployment request message carries identifier information of a network service NS to be deployed, and at least one sub-network service Sub that constitutes the NS to be deployed. Identification information of each Sub-NS in the NS and information about the deployment location of each Sub-NS, where there are different labels The identified Sub-NS corresponds to the virtualized network function VNF of different device types and different performance requirements.
  • the identification information of the NS to be deployed and the identification information of each Sub-NS in the at least one Sub-NS it is determined to deploy the The VNF required by each Sub-NS; the VNF required by each Sub-NS is deployed at the deployment location of each Sub-NS in the at least one Sub-NS.
  • the method for deploying a network service receives a deployment request message, where the deployment request message carries the identification information of the network service NS to be deployed, and each Sub of the at least one sub-network service Sub-NS constituting the to-be-deployed NS - the identification information of the NS and the information about the deployment location of each Sub-NS, wherein the Sub-NSs having different identifiers correspond to the virtualized network function VNF of different device types and different performance requirements; according to the NS to be deployed Identifying information and identification information of each Sub-NS in the at least one Sub-NS, determining a VNF required for deploying each Sub-NS; deploying the deployment location of each Sub-NS in the at least one Sub-NS
  • the VNF required by each Sub-NS can deploy network services for users distributed in specified locations according to actual needs.
  • determining, according to the identifier information of the NS to be deployed and the identifier information of each Sub-NS in the at least one Sub-NS, The VNF required by the Sub-NS includes: determining, according to the identifier information of the NS to be deployed, a network service description NSD template corresponding to the NS, where the NSD template stores a mapping relationship between the identifier of the Sub-NS and the required VNF performance; Determining VNF performance corresponding to the first Sub-NS according to the identification information of the first Sub-NS in the at least one Sub-NS and the NSD template, and satisfying the VNF of the VNF performance corresponding to the first Sub-NS Determine the VNF required to deploy the first Sub-NS.
  • the NSD template is further configured to indicate that the identifier information of the Sub-NS and the virtual network function description VNFD template are
  • the method further includes: determining, according to the identifier information of the first Sub-NS and the NSD template, a VNFD template corresponding to the first Sub-NS, where the VNFD template indicates a VNF performance and a required deployment resource.
  • the VNF required by the Sub-NS includes: deploying the VNF required by the first Sub-NS in the deployment location of the first Sub-NS according to the deployment resources required by the first Sub-NS.
  • the method before determining the NSD template corresponding to the NS according to the identifier information of the NS to be deployed The method further includes: obtaining an NSD template corresponding to the NS, where the NSD template corresponding to the NS is generated according to network planning requirements and operator requirements.
  • the deployment resource includes the following resources At least one of: computing resources, network resources, and storage resources.
  • the method for deploying the network service in the embodiment of the present invention can generate the NSD and the VNFD template in advance according to the network planning requirements and the operator requirements, thereby making the deployment of the network service more flexible.
  • an apparatus for deploying a network service for performing the method of any of the first aspect or the first aspect of the first aspect.
  • the apparatus comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • an apparatus for deploying a network service comprising: a receiver, a transmitter, a memory, a processor, and a bus system.
  • the receiver, the transmitter, the memory and the processor are connected by the bus system, the memory is for storing instructions for executing instructions stored by the memory, and controlling the transmitter to send signals, and when When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • FIG. 1 is a schematic diagram of an NFV system to which an embodiment of the present invention is applied.
  • FIG. 2 is a schematic flowchart of a method for deploying a network service according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a Network Service Descriptor (NSD) template in a method for deploying a network service according to an embodiment of the present invention.
  • NSD Network Service Descriptor
  • FIG. 4 is a schematic flowchart of a method for deploying a network service according to an embodiment of the present invention.
  • FIG. 5 is a schematic block diagram of an apparatus for deploying a network service according to an embodiment of the present invention.
  • FIG. 6 is a schematic block diagram of an apparatus for deploying a network service according to an embodiment of the present invention.
  • FIG. 1 shows an NFV system 100 to which an embodiment of the present invention is applied.
  • the reference architecture of the NFV system 100 consists of the following main functional components:
  • the NFVI Infrastructure (NFVI) 110 provides the virtualization resources needed to support the implementation of NFV, including Commercial Off The Shelf (COTS) hardware, the necessary accelerator components, and virtualization of the underlying hardware. Abstracted software layer.
  • COTS Commercial Off The Shelf
  • NFVI 110 may include computing hardware 111, storage hardware 112, hardware resource layer composed of network hardware 113, virtualization layer, and virtual computing 114 (eg, virtual machine), virtual storage 115, and virtual network (network hardware) 116. Virtual resource layer.
  • the VNF 121 is a software implementation of a Network Function (NF) capable of running on the NFVI, possibly with an Element Management System (EMS) 122 to understand and manage the individual VNFs and their characteristics.
  • NF Network Function
  • EMS Element Management System
  • the VNF is equivalent to the entity of the network node and is expected to be delivered in pure software that is free of hardware dependencies.
  • NFV MANO 140 includes lifecycle management of physical and/or software resources or VNF lifecycle management that orchestrate infrastructure virtualization.
  • the MANO 140 focuses on virtualizing specific management tasks in the NFV framework.
  • the MANO 140 also interacts with an Operation Support System (OSS)/Business Support System (BSS) 130 (external to the NFV) to allow NFV to be integrated into existing network-wide management landscapes.
  • OSS Operation Support System
  • BSS Business Support System
  • the above components interact through defined reference points so that different entities can be clearly decoupled, resulting in an open and innovative NFV ecosystem.
  • the reference point between MANO 140 and VNF121 and NFVI 110 (and between NFV M&O internal entities) handles the management and operation of the NFV system.
  • the way the related components are designed allows reuse of existing solutions (such as cloud management systems) and also interacts with existing OSS/BSS environments that the NFV system needs to connect to.
  • MANO 140 The following functional components are further defined within MANO 140:
  • NFV Orchestrator (NFVO) 143 which is mainly responsible for NS lifecycle management, completes network service orchestration functions, and NFVI resource scheduling across multiple VIMs to complete resource orchestration functions.
  • the VNF Manager (VNFM) 142 is responsible for lifecycle management of VNF instances. Each VNF is assumed to have an associated VNFM. A VNFM can be assigned to manage a single VNF instance or manage multiple identical or dissimilar types. VNF instance.
  • the available capabilities include: VNF instantiation, VNF configuration NFVI resources, VNF instance updates, VNF instance scaling, VNF instance related NFVI performance metrics and event collection, and association with VNF instance related events, VNF instance assisted or automated rehabilitation, VNF Instance termination, VNF instances throughout their lifecycle integrity management, configuration and event reporting between NFVI and EMS assume global coordination and adaptation roles.
  • the Virtualized Infrastructure Manager (VIM) 141 is responsible for controlling and managing the computing, storage, and network resources of the NFVI 110, typically within an operator's infrastructure sub-domain.
  • a VIM 141 can handle certain types of NFVI resources or can manage multiple types of NFVI resources.
  • the available capabilities include: orchestration/upgrade/de-allocation/recycling of NFVI resources, managing the association of virtualized resources with computing, storage, and network resources; managing hardware resources (computing, storage, networking) and software resources (such as hypervisors) Directory; collect and forward performance metrics and events for virtualized resources.
  • NS with specific functions can be implemented through multiple NFs.
  • Traditional network implementation The terminal NS is completely composed of PNF.
  • the end-to-end NS implemented in NFV is generally still PNF at both ends, while the middle is replaced in whole or in part with VNF.
  • the function and external interface implemented by each NF is independent of whether it is a PNF or a VNF.
  • the topological relationship formed by the link between the VNF and the PNF can be described by a VNF Forwarding Graph (VNFFG), and the characteristics of each NF are described by a corresponding Network Function Descriptor (NFD).
  • VNFFG VNF Forwarding Graph
  • NFD Network Function Descriptor
  • VNF needs to be implemented based on virtual resources (including virtual computing, storage, and network resources) provided by NFVI, which virtualize the corresponding physical resources.
  • PNF is directly implemented based on physical resources.
  • NFV introduces virtualization to realize hardware and software decoupling of network devices, so that control of services is mainly reflected in PNF and VNF, and performance control. It is mainly reflected in the NFVI, especially the hardware resource level.
  • the NFVI is connected to the VIM through the Nf-Vi interface
  • the VNF is connected to the VNFM through the Ve-Vnfm interface
  • the VIM is connected to the VNFM through the Vi-Vnfm interface
  • the VIM is connected to the Orchestrator through the Or-Vi interface
  • the VNFM is passed through the Or-
  • the Vnfm interface is connected to the Orchestrator
  • the Orchestrator is connected to the OSS/BSS through the Os-Ma interface.
  • FIG. 2 shows a method 200 for deploying a network service according to an embodiment of the present invention.
  • the method 200 of deploying a network service can be applied to the NFV-MANO system shown in FIG.
  • the NFVO receives the deployment request message sent by the sender, where the deployment request message carries the identifier information of the NS to be deployed, and the identification information of each Sub-NS in the at least one sub-network service Sub-NS of the NS to be deployed Information about the deployment location of Sub-NS, where two Sub-NSs with different identifiers correspond to VNFs of different device types and different performance requirements.
  • the sender can input the identification information of the NS to be deployed to the NFVO through the Os-Ma interface, and form each Sub-NS in the sub-NS of the sub-network serving the NS to be deployed.
  • the identification information and the information about the deployment location of each Sub-NS are the identification information of the network service NS to be deployed, the information of the at least one deployment location, and the performance requirement information corresponding to each of the at least one deployment location.
  • deployment request message may be sent by, for example, the OSS/BSS in the NFV system or other sending devices in the NFV system, which is not limited by the embodiment of the present invention.
  • the NS to be deployed needs to be designed in advance.
  • all VNFs included in the NS to be deployed may be allocated to the N according to the device type and performance requirements of the deployment location.
  • a specified deployment location, N is an integer greater than or equal to one.
  • N is 1, all the VNFs in the NS to be deployed may be deployed in the same location. If N is greater than 1, all VNFs in the NS to be deployed are deployed in N specified locations. And all VNFs on each specified deployment location have connection dependencies when deploying the network.
  • any two deployment locations may be different deployment locations or the same deployment location.
  • the deployment location of each Sub-NS may be divided according to the distribution of the user and the requirements of the operator.
  • deploying device types such that each Sub-NS provides network services to tenants within its deployment location range, in accordance with an embodiment of the present invention Not limited.
  • the performance requirement of the Sub-NS may be a Key Performance Indicator (KPI) of the Sub-NS, for example, the capacity performance of the Sub-NS.
  • KPI Key Performance Indicator
  • the NFVO may perform validity check on the received deployment request message, determine whether the sender has rights, and the validity and validity of the deployment request message sent by the sender.
  • the NFVO determines the NSD template of the NS to be deployed by querying the NS directory (Catalogue) according to the identifier information of the NS to be deployed.
  • the NFVO may determine, according to the identifier of the NS to be deployed, an NSD template that describes the NS to be deployed in the NS Catalogue, where the NSD template may represent a mapping between performance requirements and performance of the required VNF. relationship.
  • the NSD template needs to be established, and the NSD template is uploaded to the NS Catalogue in the NFV-MANO system, so that the NFVO queries and determines the NSD template of the NS to be deployed when the NS is deployed.
  • FIG. 3 is a schematic diagram of an NSD template in a method for deploying a network service according to an embodiment of the present invention.
  • the NS catalogue of the NFV-MANO system includes an NSD template and a virtual link descriptor (Virtual Link Descriptor) template for deploying the NS.
  • the set of templates needed to deploy the NS.
  • the NSD template stores a mapping relationship between the identifier of the at least one Sub-NS that is commonly used when the NS is deployed by the network provider, and the VNF performance required to deploy each Sub-NS in the at least one Sub-NS.
  • two Sub-NSs with different identifiers in the at least one Sub-NS correspond to VNFs of different device types and different performance requirement information, and VNFs of different device types may be VNFs of completely different device types or may For a VNF of a different device type, the embodiment of the present invention does not limit this.
  • a sub-network service of 100,000 users may be deployed through Sub-NS-10 million (w); deployment may also be indicated by Sub-NS-A.
  • a sub-network service of 100,000 users but the embodiment of the present invention is not limited thereto.
  • the Sub-NS when a VNF of a different device type is required for each Sub-NS, the Sub-NS can be deployed by the VNF1 and VNF2 network elements through Sub-NS1; It is indicated that the Sub-NS is deployed by two types of network elements, VNF1 and VNF2, but the embodiment of the present invention is not limited thereto.
  • the NFVO determines, according to the identification information of each Sub-NS in the at least one Sub-NS and the NSD template, the VNF required to deploy each Sub-NS.
  • the VNF performance corresponding to the performance requirement of the identifier information of each Sub-NS may be determined according to the identifier information of each Sub-NS in the at least one Sub-NS and the NSD template, and the The performance of the identification information of each Sub-NS identifies the VNF of the corresponding VNF performance as the VNF required for deploying each Sub-NS.
  • the NSD template is also used to indicate the mapping relationship between the Sub-NS and the VNFD template of the VNF required to deploy each Sub-NS, and the NFVO may also be based on the performance of each Sub-NS in the at least one Sub-NS.
  • Request information and the NSD The template determines a VNFD template required to deploy each Sub-NS in the at least one Sub-NS.
  • a Sub-NS2- is deployed at the B location.
  • 5w where Sub-NS1-10w indicates that the Sub-NS is deployed by the network element identified by VNF1 and VNF2, and Sub-NS2-5w indicates that the Sub-NS is deployed by the network element identified by VNF3 and VNF4.
  • deploying the Sub-NS1-10w requires a VNF1 that can deploy 10w users and a VNF2 that can deploy 20w users.
  • Deploying the Sub-NS5-5w requires a VNF3 that can deploy 5w users and a VNF4 that can deploy 10w users.
  • the NFVO determines, according to the VNFD template required by each Sub-NS, a deployment resource required for deploying each Sub-NS.
  • the VNFD template indicates a mapping relationship between each performance VNF and required deployment resource information.
  • the VNFD template required for deploying each Sub-NS is determined according to the identification information and the NSD template of each Sub-NS in the at least one Sub-NS, and is determined according to the VNFD template of each Sub-NS. Deploy the deployment resource information required by each Sub-NS.
  • the VNFD template needs to be established, and the VNFD template is uploaded to the NS Catalogue in the NFV-MANO system, so that the NFVO queries and determines the deployment resource information of the VNF when the NS is deployed.
  • the network provider in the VNFD template of the embodiment of the present invention provides multiple types and performances of the VNF.
  • the device type of the VNF may be represented by the VNF1 as a Mobility Management Entity Function (MME); or the device type of the VNF may be represented by the VNFa as a service. Gateway (Serving GateWay, SGW), but embodiments of the present invention are not limited thereto.
  • the VNF-5w may indicate that the VNF can deploy 50,000 users; and the VNF-a indicates that the VNF can deploy 50,000 users, but the present invention implements The example is not limited to this.
  • the deployment resource information of the VNF may include a computing resource, a storage resource, and a network resource, but the embodiment of the present invention is not limited thereto.
  • all VNFs may be connected to the network.
  • the NFVO may store related information of the NS to be deployed in a network service record (NSR), and store information about all VNFs in the NS to be deployed to a virtualized network function record (Virtualised Network Function Record, In VNFR), the deployment of this network service is completed.
  • NSR network service record
  • VNFR Virtualised Network Function Record
  • S250 and S260 can be completed by three parts of NFVO, VNFM and VIM.
  • the VNFO may generate deployment identification information of the NS to be deployed and deployment identification information of each Sub-NS in the N Sub-NSs, and deploy the identification information of the NS, the deployment of each Sub-NS.
  • the identification information and deployment location information are stored in the network service record NSR.
  • the NFVO can also generate a deployment identifier of the VNF corresponding to each Sub-NS.
  • the information, and the deployment identifier information of the VNF corresponding to each Sub-NS, the deployment location information of the Sub-NS to which each VNF belongs, and the performance requirement information of each VNF are stored in the VNFR.
  • Each VNF in the VNF and the Sub-NS in each deployment location can be uniquely determined by the deployment identification information in the network, so that the network needs to be expanded or partially redeployed later, so that the deployment of the network service is more flexible.
  • the method for deploying a network service receives a deployment request message, where the deployment request message carries the identification information of the network service NS to be deployed, and each Sub of the at least one sub-network service Sub-NS constituting the to-be-deployed NS - the identification information of the NS and the information about the deployment location of each Sub-NS, wherein the Sub-NSs having different identifiers correspond to the virtualized network function VNF of different device types and different performance requirements; according to the NS to be deployed Identifying information and identification information of each Sub-NS in the at least one Sub-NS, determining a VNF required for deploying each Sub-NS; deploying the deployment location of each Sub-NS in the at least one Sub-NS
  • the VNF required by each Sub-NS can deploy network services for users distributed in specified locations according to actual needs.
  • a method for deploying a network service can generate an NSD and a VNFD template according to the requirements of the network service planning and the requirements of the operator, thereby making the deployment of the network service more flexible.
  • FIG. 4 shows a method 400 for deploying a network service according to an embodiment of the present invention.
  • the method 400 of deploying a network service can be applied to the NFV-MANO system shown in FIG. 1 and executed by NFVO in the NFV-MANO system.
  • S410 Receive a deployment request message, where the deployment request message carries the identifier information of the network service NS to be deployed, and the identifier information of each Sub-NS in the at least one sub-network service Sub-NS constituting the NS to be deployed, and each Sub- Information about the deployment location of the NS, where Sub-NSs with different identifiers correspond to VNFs of different device types and different performance requirements.
  • S410 can refer to the description of S210 in FIG. 2, and to avoid repetition, details are not described herein again.
  • S420 Determine, according to the identifier information of the NS to be deployed and the identifier information of each Sub-NS in the at least one Sub-NS, a VNF required to deploy each Sub-NS.
  • S420 can refer to the description of S220 to S230 in FIG. 2, and details are not described herein again to avoid repetition.
  • the S430 deploys the VNF required by each Sub-NS in a deployment location of each Sub-NS in the at least one Sub-NS.
  • S430 can refer to the descriptions of S240 to S250 in FIG. 2, and to avoid repetition, details are not described herein again.
  • the identification information and the NSD template determine the VNF performance corresponding to the first Sub-NS, and determine the VNF that satisfies the VNF performance corresponding to the first Sub-NS as the VNF required to deploy the first Sub-NS.
  • the NSD template is further used to indicate a mapping relationship between the identifier information of the Sub-NS and the virtual network function description VNFD template.
  • the method further includes: determining, according to the identifier information of the first Sub-NS, the NSD template. , determine the first A VNFD template corresponding to the Sub-NS, the VNFD template indicates a mapping relationship between the VNF performance and the required deployment resource; and the deployment resource required to deploy the first Sub-NS is determined according to the VNFD template corresponding to the first Sub-NS.
  • the deployment location deploys the VNF required by the first Sub-NS.
  • the method before determining the NSD template corresponding to the NS according to the identifier information of the NS to be deployed, the method further includes: acquiring an NSD template corresponding to the NS, where the NSD template corresponding to the NS is according to network planning requirements and operations The request is generated.
  • the deployment resource includes at least one of the following resources: a computing resource, a network resource, and a storage resource.
  • the method for deploying a network service receives a deployment request message, where the deployment request message carries the identification information of the network service NS to be deployed, and each Sub of the at least one sub-network service Sub-NS constituting the to-be-deployed NS - the identification information of the NS and the information about the deployment location of each Sub-NS, wherein the Sub-NSs having different identifiers correspond to the virtualized network function VNF of different device types and different performance requirements; according to the NS to be deployed Identifying information and identification information of each Sub-NS in the at least one Sub-NS, determining a VNF required for deploying each Sub-NS; deploying the deployment location of each Sub-NS in the at least one Sub-NS
  • the VNF required by each Sub-NS can deploy network services for users distributed in specified locations according to actual needs.
  • the method for deploying the network service provided by the embodiment of the present invention can generate the NSD and the VNFD template in advance according to the network planning requirements and the operator requirements,
  • FIG. 5 illustrates an apparatus 500 for deploying a network service in accordance with an embodiment of the present invention.
  • the receiving unit 510 is configured to receive a deployment request message, where the deployment request message carries the identifier information of the NS to be deployed, the identifier information of each Sub-NS in the at least one sub-network service Sub-NS that constitutes the NS to be deployed, and each of the Sub-NS deployment location information, where Sub-NSs with different identifiers correspond to virtualized network functions VNF of different device types and different performance requirements;
  • the determining unit 520 is configured to determine, according to the identifier information of the NS to be deployed received by the receiving unit 510 and the identifier information of each Sub-NS in the at least one Sub-NS, the VNF required to deploy each Sub-NS;
  • the deployment unit 530 is configured to deploy, at a deployment location of each Sub-NS in the at least one Sub-NS, the VNF required by the determining unit 520 for each Sub-NS.
  • the determining unit 520 is specifically configured to: determine, according to the identifier information of the NS to be deployed, a network service description NSD template corresponding to the NS, where the NSD template stores the identifier of the Sub-NS and the required VNF performance. Mapping the relationship; determining the VNF performance corresponding to the first Sub-NS according to the identification information of the first Sub-NS and the NSD template in the at least one Sub-NS, and satisfying the VNF corresponding to the first Sub-NS The VNF of performance is determined as the VNF required to deploy the first Sub-NS.
  • the NSD template is further used to indicate a mapping relationship between the identifier information of the Sub-NS and the virtual network function description VNFD template.
  • the determining unit 520 is specifically configured to use the identifier information of the first Sub-NS and the An NSD template is configured to determine a VNFD template corresponding to the first Sub-NS, where the VNFD template indicates a mapping relationship between the VNF performance and the required deployment resource; and determining to deploy the first Sub according to the VNFD template corresponding to the first Sub-NS
  • the NS needs the deployment resource.
  • the deployment unit 530 is specifically configured to deploy the VNF required by the first Sub-NS in the deployment location of the first Sub-NS according to the deployment resource required by the first Sub-NS.
  • the apparatus 500 further includes: a generating unit, configured to acquire an NSD template corresponding to the NS, and corresponding to the NS, before determining the NSD template corresponding to the NS according to the identifier information of the NS to be deployed.
  • the NSD template is generated according to network planning requirements and carrier requirements.
  • the deployment resource information includes: a computing resource, a network resource, and a storage resource.
  • the apparatus 500 herein is embodied in the form of a functional unit.
  • the term "unit” herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • ASIC application specific integrated circuit
  • the device 500 may be specifically the network device in the foregoing embodiment, and the device 500 may be used to perform various processes and/or steps corresponding to the network device in the foregoing method embodiments. To avoid repetition, we will not repeat them here.
  • FIG. 6 shows an apparatus 600 for deploying a network service in accordance with an embodiment of the present invention.
  • the apparatus 600 includes a processor 610, a transmitter 620, a receiver 630, a memory 640, and a bus system 650.
  • the processor 610, the transmitter 620, the receiver 630 and the memory 640 are connected by a bus system 650 for storing instructions for executing instructions stored in the memory 640 to control the transmitter 620.
  • Send a signal Transmitter 620 and receiver 630 may be communication interfaces, and specific transmitter 620 may be an interface for receiving data and/or instructions, and receiver 630 may be an interface for transmitting data and/or instructions, no longer Specific forms of the transmitter 620 and the receiver 630 are exemplified.
  • the apparatus 600 can be applied to the NFV-MANO system in the above embodiments, and can be used to perform the respective steps and/or processes in the above method embodiments.
  • the memory 640 can include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 610 can be configured to execute instructions stored in a memory, and when the processor executes the instructions, the processor can perform various steps corresponding to the terminal device in the above method embodiments.
  • the processor may be a central processing unit (CPU), and the processor may also be other general purpose processors, digital signal processors (DSPs), and application specific integrated circuits (ASICs). ), off-the-shelf programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a mobile hard disk, and a read-only memory (Read-Only Memory, Abbreviated as "ROM”), random access memory (Random Access Memory (RAM), magnetic disk or optical disk, and other media that can store program codes.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供了一种部署网络服务的方法和装置，该方法包括：接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，能够根据实际需要为分布在指定位置的用户部署网络服务。

Description

部署网络服务的方法和装置
本申请要求于2015年12月31日提交中国专利局、申请号为201511032282.4、发明名称为“部署网络服务的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络功能虚拟化(Network Function Virtualization，NFV)领域，并且更具体地，涉及部署网络的方法和装置。
背景技术
NFV通过使用x86等通用性硬件以及虚拟化技术，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署。
欧洲电信标准协会(European Telecommunications Standards Institute，ETSI)于2012年10月成立了NFV工作组，旨在定义运营商网络功能虚拟化的需求和相关的技术报告，希望通过借鉴IT的虚拟化技术，在通用的高性能服务器、交换机和存储中实现部分网络功能。NFV工作组所指定的NFV架构和基本流程已经被业界作为标准，在各个电信云化项目中进行了实施。
在实际应用的场景中，根据不同用户的需求，需要运营商部署大量的差异化的网络服务(Network Service，NS)，每个NS可以由一系列的虚拟化网络功能(Virtualised Network Function，VNF)和物理网络功能(Physical Network Function，PNF)网元节点组成，由于不同用户的需求的差异性，每个NS要部署的网元节点的位置和性能都会存在差异性。
然而，现有的NFV管理和编制(Management and Orchestration，MANO)系统定义的网络服务自动部署的基本框架，在确定待部署网络服务的性能要求之后，整个网络服务需要的VNF的部署位置就固定生成，不能根据实际网络服务规划需求为分布在指定位置的用户部署网络服务。
发明内容
本发明实施例提供了一种部署网络服务的方法和装置，能够为分布在指定位置的用户部署网络服务。
第一方面，提供了一种部署网络服务的方法，该方法包括：接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标 识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF。
本发明实施例提供的部署网络服务的方法，通过接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，能够根据实际需要为分布在指定位置的用户部署网络服务。
结合第一方面，在第一方面的第一种可能的实现方式中，该根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF，包括：根据该待部署NS的标识信息，确定该NS对应的网络服务描述NSD模板，该NSD模板存储有Sub-NS的标识与需要的VNF性能之间的映射关系；根据该至少一个Sub-NS中的第一Sub-NS的标识信息和该NSD模板，确定与该第一Sub-NS对应的VNF性能，并将满足该第一Sub-NS对应的VNF性能的VNF确定为部署该第一Sub-NS需要的VNF。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该NSD模板还用于表示Sub-NS的标识信息与虚拟化网络功能描述VNFD模板之间的映射关系；该方法还包括：根据该第一Sub-NS的标识信息和该NSD模板，确定该第一Sub-NS对应的VNFD模板，该VNFD模板表示VNF性能与需要的部署资源之间的映射关系；根据该第一Sub-NS对应的VNFD模板，确定部署该第一Sub-NS需要的部署资源；该在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，包括：根据该第一Sub-NS需要的部署资源，在该第一Sub-NS的部署位置部署该第一Sub-NS需要的VNF。
结合第一方面的第一种或第二种可能的实现方式，在第一方面的第三种可能的实现方式中，在该根据该待部署NS的标识信息，确定该NS对应的NSD模板之前，该方法还包括：获取该NS对应的NSD模板，该NS对应的NSD模板是根据网络规划需求和运营商要求生成的。
结合第一方面、第一方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第一方面的第四种可能的实现方式中，该部署资源包括下列资源中的至少一项：计算资源、网络资源和存储资源。
本发明实施例的一种部署网络服务的方法，可以根据网络规划需要和运营商要求提前生成NSD以及VNFD模板，从而使网络服务的部署更加灵活化。
第二方面，提供了一种部署网络服务的装置，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该装置包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第三方面，提供了一种部署网络服务的装置，该装置包括：接收器、发送器、存储器、处理器和总线系统。其中，该接收器、该发送器、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并控制发送器发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例应用的NFV系统的示意图。
图2是本发明实施例提供的部署网络服务的方法的示意性流程图。
图3是本发明实施例提供的部署网络服务的方法中的网络服务描述(Network Service Descriptor，NSD)模板的示意图。
图4是本发明实施例提供的部署网络服务的方法的示意性流程图。
图5是本发明实施例提供的部署网络服务的装置的示意性框图。
图6是本发明实施例提供的部署网络服务的装置的示意性框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1示出了本发明实施例应用的NFV系统100。该NFV系统100的参考架构由以下几个主要功能构件组成：
NFVI基础设施(NFV Infrastructure，NFVI)110提供支撑NFV的执行所需要的虚拟化资源，包括商业现货供应(Commercial Off The Shelf，COTS)的硬件、必要的加速器组件，以及对底层硬件进行虚拟化和抽象化的软件层。
例如，NFVI 110可以包括计算硬件111、存储硬件112、网络硬件113组成的硬件资源层、虚拟化层、以及虚拟计算114(例如，虚拟机)、虚拟存储115和虚拟网络(网络硬件)116组成的虚拟资源层。
VNF 121是能够在NFVI上运行的网络功能(Network Function，NF)的软件实现，可能还附有组件管理系统(Element Management System，EMS)122来理解和管理单独的VNF及其特性。VNF相当于网络节点的实体，被期望以摆脱硬件依赖的纯软件来交付。
NFV MANO 140包含编排、支撑基础设施虚拟化的物理和/或软件资源的生命周期管理、VNF的生命周期管理。MANO 140聚焦于NFV框架中虚拟化特定的管理任务。MANO 140也与(NFV外部的)运营支撑系统(Operation Support System，OSS)/业务支撑系统(Business Support System，BSS)130交互，以允许NFV被集成进已存在的涉及全网范围的管理图景。
上述构件通过定义的参考点进行交互，以便不同实体能够清晰地解耦，从而促成一个开放和创新的NFV生态系统。VNF 121与NFVI 110之间(以及NFVI 110内部实体之间)的参考点处理资源的抽象和虚拟化，以及VNF 121的主机寄宿，以便VNF 121不仅能够在NFVI110中从一个移动到另一个，而且能够确保选择不同的底层硬件成为可能。MANO 140与VNF121和NFVI 110之间(以及NFV M&O内部实体之间)的参考点处理NFV系统的管理和运作。相关构件的设计方式允许重用现有解决方案(例如云管理系统)，并且也与NFV系统需要连接的现有OSS/BSS环境进行交互。
MANO 140之内进一步定义了以下功能构件：
NFV编排器(NFV Orchestrator，NFVO)143，主要负责NS的生命周期管理，完成网络业务编排功能；以及跨多个VIM的NFVI资源编排，完成资源编排功能。
VNF管理器(VNF Manager，VNFM)142，负责VNF实例的生命周期管理，每个VNF都被假定具有一个关联的VNFM，一个VNFM可以被指派管理单一VNF实例或者管理多个相同或相异类型的VNF实例。其可用能力包括：VNF实例化、VNF配置NFVI资源、VNF实例更新、VNF实例缩放、VNF实例相关NFVI性能度量和事件的收集以及与VNF实例相关事件的关联、VNF实例受助或自动康复、VNF实例终止、VNF实例贯穿其生命周期的完整性管理、为NFVI和EMS之间的配置和事件报告担当全局协调和适配的角色等。
虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)141，负责控制和管理NFVI 110的计算、存储和网络资源，通常在一个运营商的基础设施子域内。一个VIM 141可以专门处理某类NFVI资源或者可以管理多种类型的NFVI资源。其可用能力包括：编排NFVI资源的分配/升级/解除分配/回收利用，管理虚拟化资源与计算、存储、网络资源的关联；管理硬件资源(计算、存储、网络)和软件资源(例如管理程序)的目录；收集和转发虚拟化资源的性能度量和事件等。
在上述架构的基础上，可以通过多个NF实现具有特定功能的NS。传统网络实现的端到 端NS是完全由PNF构成的。NFV中实现的端到端NS则一般两端仍为PNF，而中间则全部或部分被替换为VNF。每个NF实现的功能和对外的接口与其是PNF还是VNF无关。VNF和PNF之间链接构成的拓扑关系可以采用VNF转发图(VNF Forwarding Graph，VNFFG)来描述，每个NF的特性由相应的网络功能描述符(Network Function Descriptor，NFD)来描述。
VNF需要基于NFVI提供的虚拟资源(包括虚拟的计算、存储和网络资源)来实现，这些虚拟资源是对相应的物理资源进行虚拟化而来的。PNF则直接是基于物理资源来实现的。不像传统网络中所有控制都集中于软硬件一体化的网络设备上，NFV引入虚拟化实现网络设备的软硬件解耦，使得对业务的控制主要体现在PNF和VNF层面，而对性能的控制则主要体现在NFVI尤其是其中的硬件资源层面。
在上述NFV架构中，NFVI通过Nf-Vi接口与VIM相连，VNF通过Ve-Vnfm接口与VNFM相连，VIM通过Vi-Vnfm接口与VNFM相连，VIM通过Or-Vi接口与Orchestrator相连，VNFM通过Or-Vnfm接口与Orchestrator相连，Orchestrator通过Os-Ma接口与OSS/BSS相连。
图2示出了本发明实施例提供的部署网络服务的方法200。该部署网络服务的方法200可以应用于图1中所示的NFV-MANO系统。
S210，NFVO接收发送者发送的部署请求消息，该部署请求消息携带待部署NS的标识信息，组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的两个Sub-NS对应于不同设备类型的VNF以及不同的性能要求。
具体而言，当部署一个NS的时候，发送者可以通过Os-Ma接口向该NFVO输入待部署NS的标识信息，组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息待部署网络服务NS的标识信息、至少一个部署位置的信息和该至少一个部署位置中每个部署位置对应的性能要求信息。
应理解，该部署请求消息例如可以由NFV系统中的OSS/BSS或者NFV系统中其他发送设备发送，本发明实施例对此不作限定。
还应理解，在部署一个待部署NS之前，需要提前设计该待部署NS，作为一个可选实施例，可以将该待部署NS包括的所有VNF根据部署位置的设备类型以及性能要求，分配到N个指定的部署位置，N为大于或等于一的整数。作为一个可选实施例，若N为1，则该待部署NS中的所有VNF可以部署在同一个位置，若N大于1，则该待部署NS中的所有VNF分别部署在N个指定位置，并且每个指定部署位置上的所有VNF之间在部署网络时具有连接依赖关系。
可选地，任意两个部署位置可以为不同的部署位置，也可以为相同的部署位置，在实际部署时可以根据用户的分布情况和运营商的要求，划分该每个Sub-NS的部署位置和部署设备类型，使得每个Sub-NS为其部署位置范围内的租户提供网络服务，本发明实施例对此 不作限定。
可选地，Sub-NS的性能要求可以为Sub-NS的关键绩效指标(Key Performance Indicator，KPI)，例如可以为Sub-NS的容量性能。
可选地，在S210之后，NFVO可以对接收到的部署请求消息进行有效性检查，确定发送者的是否有权限、以及发送者发送的部署请求消息的合法性和有效性等。
S220，NFVO根据该待部署NS的标识信息，通过查询NS目录(Catalogue)，确定该待部署NS的NSD模板。
具体而言，NFVO可以根据接收到的待部署NS的标识，在NS Catalogue中确定描述该待部署NS的NSD模板，该NSD模板可以该NSD模板表示性能要求与需要的VNF的性能之间的映射关系。
可选地，在S220之前，需要建立NSD模板，并将NSD模板上传至NFV-MANO系统中的NS Catalogue，以便于NFVO在部署NS时查询并确定待部署NS的NSD模板。
图3示出了本发明实施例的部署网络服务的方法中的NSD模板的示意图，在NFV-MANO系统的NS Catalogue中包括了部署该NS的NSD模板和虚链路描述(Virtual Link Descriptor)模板等部署该NS需要的模板集合。
可选地，NSD模板存储有网络供应商提供的部署该NS时常用的至少一个Sub-NS的标识与部署该至少一个Sub-NS中每个Sub-NS需要的VNF性能之间的映射关系，应理解，该至少一个Sub-NS中两个具有不同标识的Sub-NS对应不同的设备类型的VNF以及不同的性能要求信息，不同的设备类型的VNF可以为完全不同的设备类型的VNF或者可以为部分不同的设备类型的VNF，本发明实施例对此不作限定。
作为一个可选实施例，在描述Sub-NS的不同性能要求时，可以通过Sub-NS-10万(w)表示部署一个10万用户的子网络服务；还可以通过Sub-NS-A表示部署一个10万用户的子网络服务，但本发明实施例不限于此。
作为另一个可选实施例，在描述部署每个Sub-NS需要不同设备类型的VNF时，可以通过Sub-NS1表示该Sub-NS由VNF1和VNF2两种网元部署；还可以通过Sub-NSa表示该Sub-NS由VNF1和VNF2两种类型的网元部署，但本发明实施例不限于此。
S230，NFVO根据该至少一个Sub-NS中每个Sub-NS的标识信息和该NSD模板，确定部署该每个Sub-NS需要的VNF。
具体而言，可以根据该至少一个Sub-NS中每个Sub-NS的标识信息和该NSD模板，确定与该每个Sub-NS的标识信息标识的性能要求对应的VNF性能，并将满足该每个Sub-NS的标识信息标识的性能要求对应的VNF性能的VNF确定为部署该每个Sub-NS需要的VNF。
应理解，该NSD模板还用于表示Sub-NS与部署每个Sub-NS需要的VNF的VNFD模板之间的映射关系，NFVO还可以根据该至少一个Sub-NS中每个Sub-NS的性能要求信息和该NSD 模板，确定部署该至少一个Sub-NS中每个Sub-NS需要的VNFD模板。
作为一个实施例，如图3中所示，假如要部署一个标识为LTE001的容量为15万的网络服务，并且需要在A位置部署一个Sub-NS1-10w，在B位置部署一个Sub-NS2-5w，其中，Sub-NS1-10w表示该Sub-NS为由VNF1和VNF2两种标识的网元部署，Sub-NS2-5w表示该Sub-NS为由VNF3和VNF4两种标识的网元部署。根据NSD模板可以确定部署该Sub-NS1-10w需要一个可以部署10w用户的VNF1和一个可以部署20w用户的VNF2。部署该Sub-NS5-5w需要一个可以部署5w用户的VNF3和一个可以部署10w用户的VNF4。
S240，NFVO根据该每个Sub-NS需要的VNFD模板，确定部署该每个Sub-NS需要的部署资源，该VNFD模板表示每种性能的VNF与需要的部署资源信息之间的映射关系。
具体而言，可以根据该至少一个Sub-NS中每个Sub-NS的标识信息和NSD模板，确定部署该每个Sub-NS需要的VNFD模板，并根据该每个Sub-NS的VNFD模板确定部署该每个Sub-NS需要的部署资源信息。
可选地，在S240之前，需要建立VNFD模板，并将VNFD模板上传至NFV-MANO系统中的NS Catalogue，以便于NFVO在部署NS时查询并确定VNF的部署资源信息。
可选地，本发明实施例的VNFD模板中网络供应商提供了多种类型和性能的VNF。作为一个可选实施例，在描述VNF的设备类型时，可以通过VNF1表示该VNF的设备类型为移动管理节点功能(Mobility Management Entity function，MME)；或者可以通过VNFa表示该VNF的设备类型为服务网关(Serving GateWay，SGW)，但本发明实施例不限于此。作为另一个可选实施例，在描述VNF的性能时，可以通过VNF-5w表示该VNF可以部署5万个用户；还可以通过VNF-a表示该VNF可以部署5万个用户，但本发明实施例不限于此。
可选地，VNF的部署资源信息可以包括计算资源、存储资源和网络资源，但本发明实施例不限于此。
S250，根据并根据该每个Sub-NS需要的部署资源，在该每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF。
可选地，根据该每个Sub-NS的部署资源信息，在该每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF之后，可以将所有VNF连接至网络。
S260，NFVO可以将待部署NS的相关信息存储到网络服务记录(Network Service Record，NSR)中，并将该待部署NS中所有的VNF的相关信息存储到虚拟网络功能记录(Virtualised Network Function Record，VNFR)中，从而完成本次网络服务的部署。
应理解，S250和S260可以由NFVO、VNFM和VIM三个部分共同配合完成。
具体而言，该VNFO可以生成待部署NS的部署标识信息和N个Sub-NS中的每个Sub-NS的部署标识信息，并将该NS的部署标识信息，该每个Sub-NS的部署标识信息和部署位置信息储存到网络服务记录NSR中。该NFVO还可以生成该每个Sub-NS对应VNF的部署标识 信息，并将该每个Sub-NS对应的VNF的部署标识信息、该每个VNF所属的Sub-NS的部署位置信息、该每个VNF的性能要求信息储存到VNFR中，因此，部署后NS中的每个VNF和每个部署位置的Sub-NS在网络中都可以通过部署标识信息唯一确定，以便于后续需要对网络进行扩展或者部分重新部署，使得网络服的部署更加灵活。
本发明实施例提供的部署网络服务的方法，通过接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，能够根据实际需要为分布在指定位置的用户部署网络服务。
此外，本发明实施例的一种部署网络服务的方法，可以根据需要网络服务规划需求以及运营商的要求，生成NSD以及VNFD模板，从而使网络服务的部署更加灵活化。
图4示出了本发明实施例提供的部署网络服务的方法400。该部署网络服务的方法400可以应用于图1中所示的NFV-MANO系统，并且由该NFV-MANO系统中的NFVO执行。
S410，接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的VNF以及不同的性能要求。
具体地，S410可以参见图2中的S210的描述，为避免重复，这里不再赘述。
S420，根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF。
具体地，S420可以参见图2中的S220至S230的描述，为避免重复，这里不再赘述。
S430在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF。
具体地，S430可以参见图2中的S240至S250的描述，为避免重复，这里不再赘述。
可选地，该根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF，可以为根据该待部署NS的标识信息，确定该NS对应的网络服务描述NSD模板，该NSD模板存储有Sub-NS的标识与需要的VNF性能之间的映射关系；根据该至少一个Sub-NS中的第一Sub-NS的标识信息和该NSD模板，确定与该第一Sub-NS对应的VNF性能，并将满足该第一Sub-NS对应的VNF性能的VNF确定为部署该第一Sub-NS需要的VNF。
可选地，该NSD模板还用于表示Sub-NS的标识信息与虚拟化网络功能描述VNFD模板之间的映射关系；该方法还包括：根据该第一Sub-NS的标识信息和该NSD模板，确定该第 一Sub-NS对应的VNFD模板，该VNFD模板表示VNF性能与需要的部署资源之间的映射关系；根据该第一Sub-NS对应的VNFD模板，确定部署该第一Sub-NS需要的部署资源；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，包括：根据该第一Sub-NS需要的部署资源，在该第一Sub-NS的部署位置部署该第一Sub-NS需要的VNF。
可选地，在该根据该待部署NS的标识信息，确定该NS对应的NSD模板之前，该方法还包括：获取该NS对应的NSD模板，该NS对应的NSD模板是根据网络规划需求和运营商要求生成的。
可选地，该部署资源包括下列资源中的至少一项：计算资源、网络资源和存储资源。
本发明实施例提供的部署网络服务的方法，通过接收部署请求消息，该部署请求消息携带待部署网络服务NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；根据该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该每个Sub-NS需要的VNF，能够根据实际需要为分布在指定位置的用户部署网络服务。此外，本发明实施例提供的部署网络服务的方法，可以根据网络规划需要和运营商要求提前生成NSD以及VNFD模板，从而使网络服务的部署更加灵活化。
上文中结合图1至图4，详细描述了根据本发明实施例的部署网络服务的方法，下面将结合图5和图6，详细描述根据本发明实施例的部署网络服务的装置。
图5示出了本发明实施例的部署网络服务的装置500。
接收单元510，用于接收部署请求消息，该部署请求消息携带待部署NS的标识信息、组成该待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和该每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；
确定单元520，用于根据该接收单元510接收的该待部署NS的标识信息和该至少一个Sub-NS中每个Sub-NS的标识信息，确定部署该每个Sub-NS需要的VNF；
部署单元530，用于在该至少一个Sub-NS中的每个Sub-NS的部署位置部署该确定单元520确定的该每个Sub-NS需要的VNF。
可选地，该确定单元520具体用于：根据该待部署NS的标识信息，确定该NS对应的网络服务描述NSD模板，该NSD模板存储有Sub-NS的标识与需要的VNF性能之间的映射关系；根据该至少一个Sub-NS中的第一Sub-NS的标识信息和该NSD模板，确定与该第一Sub-NS对应的VNF性能，并将满足该第一Sub-NS对应的VNF性能的VNF确定为部署该第一Sub-NS需要的VNF。
可选地，该NSD模板还用于表示Sub-NS的标识信息与虚拟化网络功能描述VNFD模板之间的映射关系；该确定单元520具体用于根据该第一Sub-NS的标识信息和该NSD模板，确定该第一Sub-NS对应的VNFD模板，该VNFD模板表示VNF性能与需要的部署资源之间的映射关系；根据该第一Sub-NS对应的VNFD模板，确定部署该第一Sub-NS需要的部署资源；该部署单元530具体用于根据该第一Sub-NS需要的部署资源，在该第一Sub-NS的部署位置部署该第一Sub-NS需要的VNF。
可选地，该装置500还包括：生成单元，该生成单元用于在该根据该待部署NS的标识信息，确定该NS对应的NSD模板之前，获取该NS对应的NSD模板，该NS对应的NSD模板是根据网络规划需求和运营商要求生成的。
可选地，该部署资源信息包括：计算资源、网络资源和存储资源。
应理解，这里的装置500以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置500可以具体为上述实施例中的网络设备，装置500可以用于执行上述方法实施例中与网络设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
图6示出了本发明实施例的部署网络服务的装置600。该装置600包括处理器610、发送器620、接收器630、存储器640和总线系统650。其中，处理器610、发送器620、接收器630和存储器640通过总线系统650相连，该存储器640用于存储指令，该处理器610用于执行该存储器640存储的指令，以控制该发送器620发送信号。发送器620和接收器630可以是通信接口，具体发送器620可以是用于接收数据和/或指令的接口，接收器630可以是用于发送数据和/或指令的接口，在此不再对发送器620和接收器630的具体形式进行举例说明。
应理解，装置600可以应用于上述实施例中的NFV-MANO系统，并且可以用于执行上述方法实施例中对应的各个步骤和/或流程。可选地，该存储器640可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器610可以用于执行存储器中存储的指令，并且该处理器执行该指令时，该处理器可以执行上述方法实施例中与终端设备对应的各个步骤。
应理解，在本发明实施例中，该处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例中描述的各方法步骤和单元，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本发明实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory， 简称为“ROM”)、随机存取存储器(Random Access Memory，简称为“RAM”)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (10)

  1. 一种部署网络服务的方法，其特征在于，包括：
    接收部署请求消息，所述部署请求消息携带待部署网络服务NS的标识信息、组成所述待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和所述每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；
    根据所述待部署NS的标识信息和所述至少一个Sub-NS中每个Sub-NS的标识信息，确定部署所述每个Sub-NS需要的VNF；
    在所述至少一个Sub-NS中的每个Sub-NS的部署位置部署所述每个Sub-NS需要的VNF。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述待部署NS的标识信息和所述至少一个Sub-NS中每个Sub-NS的标识信息，确定部署所述每个Sub-NS需要的VNF，包括：
    根据所述待部署NS的标识信息，确定所述NS对应的网络服务描述NSD模板，所述NSD模板存储有Sub-NS的标识与需要的VNF性能之间的映射关系；
    根据所述至少一个Sub-NS中的第一Sub-NS的标识信息和所述NSD模板，确定与所述第一Sub-NS对应的VNF性能，并将满足所述第一Sub-NS对应的VNF性能的VNF确定为部署所述第一Sub-NS需要的VNF。
  3. 根据权利要求2所述的方法，其特征在于，所述NSD模板还用于表示Sub-NS的标识信息与虚拟化网络功能描述VNFD模板之间的映射关系；
    所述方法还包括：
    根据所述第一Sub-NS的标识信息和所述NSD模板，确定所述第一Sub-NS对应的VNFD模板，所述VNFD模板表示VNF性能与需要的部署资源之间的映射关系；
    根据所述第一Sub-NS对应的VNFD模板，确定部署所述第一Sub-NS需要的部署资源；
    所述在所述至少一个Sub-NS中的每个Sub-NS的部署位置部署所述每个Sub-NS需要的VNF，包括：
    根据所述第一Sub-NS需要的部署资源，在所述第一Sub-NS的部署位置部署所述第一Sub-NS需要的VNF。
  4. 根据权利要求2或3所述的方法，其特征在于，在所述根据所述待部署NS的标识信息，确定所述NS对应的NSD模板之前，所述方法还包括：
    获取所述NS对应的NSD模板，所述NS对应的NSD模板是根据网络规划需求和运营商要求生成的。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述部署资源包括下列资源中的至少一项：计算资源、网络资源和存储资源。
  6. 一种部署网络服务的装置，其特征在于，包括：
    接收单元，用于接收部署请求消息，所述部署请求消息携带待部署NS的标识信息、组成所述待部署NS的至少一个子网络服务Sub-NS中每个Sub-NS的标识信息和所述每个Sub-NS的部署位置的信息，其中，具有不同标识的Sub-NS对应于不同设备类型的虚拟化网络功能VNF以及不同的性能要求；
    确定单元，用于根据所述接收单元接收的所述待部署NS的标识信息和所述至少一个Sub-NS中每个Sub-NS的标识信息，确定部署所述每个Sub-NS需要的VNF；
    部署单元，用于在所述至少一个Sub-NS中的每个Sub-NS的部署位置部署所述确定单元确定的所述每个Sub-NS需要的VNF。
  7. 根据权利要求6所述的装置，其特征在于，所述确定单元具体用于：
    根据所述待部署NS的标识信息，确定所述NS对应的网络服务描述NSD模板，所述NSD模板存储有Sub-NS的标识与需要的VNF性能之间的映射关系；
    根据所述至少一个Sub-NS中的第一Sub-NS的标识信息和所述NSD模板，确定与所述第一Sub-NS对应的VNF性能，并将满足所述第一Sub-NS对应的VNF性能的VNF确定为部署所述第一Sub-NS需要的VNF。
  8. 根据权利要求7所述的装置，其特征在于，所述NSD模板还用于表示Sub-NS的标识信息与虚拟化网络功能描述VNFD模板之间的映射关系；
    所述确定单元具体用于根据所述第一Sub-NS的标识信息和所述NSD模板，确定所述第一Sub-NS对应的VNFD模板，所述VNFD模板表示VNF性能与需要的部署资源之间的映射关系；
    根据所述第一Sub-NS对应的VNFD模板，确定部署所述第一Sub-NS需要的部署资源；
    所述部署单元具体用于根据所述第一Sub-NS需要的部署资源，在所述第一Sub-NS的部署位置部署所述第一Sub-NS需要的VNF。
  9. 根据权利要求7或8所述的装置，其特征在于，所述装置还包括：生成单元，所述生成单元用于在所述根据所述待部署NS的标识信息，确定所述NS对应的NSD模板之前，获取所述NS对应的NSD模板，所述NS对应的NSD模板是根据网络规划需求和运营商要求生成的。
  10. 根据权利要求6至9中任一项所述的装置，其特征在于，所述部署资源包括下列资源中的至少一项：计算资源、网络资源和存储资源。
PCT/CN2016/110797 2015-12-31 2016-12-19 部署网络服务的方法和装置 WO2017114219A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511032282.4A CN106936619B (zh) 2015-12-31 2015-12-31 部署网络服务的方法和装置
CN201511032282.4 2015-12-31

Publications (1)

Publication Number Publication Date
WO2017114219A1 true WO2017114219A1 (zh) 2017-07-06

Family

ID=59225655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/110797 WO2017114219A1 (zh) 2015-12-31 2016-12-19 部署网络服务的方法和装置

Country Status (2)

Country Link
CN (1) CN106936619B (zh)
WO (1) WO2017114219A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110034944A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 网络切片部署方法及其装置
EP3720050A4 (en) * 2018-03-29 2021-01-20 Huawei Technologies Co., Ltd. NETWORK TRENCH DEPLOYMENT METHOD AND APPARATUS
WO2023061153A1 (zh) * 2021-10-11 2023-04-20 中兴通讯股份有限公司 网络服务部署方法、装置及计算机可读存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391982B (zh) * 2017-08-10 2022-06-07 中国移动通信有限公司研究院 信息包生成方法及编排管理方法、网元及存储介质
CN107846313B (zh) * 2017-10-30 2019-04-30 中国联合网络通信集团有限公司 一种网络服务模板生成的方法及网络设备
CN110572272B (zh) * 2018-06-06 2020-11-06 大唐移动通信设备有限公司 一种网络切片的创建方法及管理编排系统
CN110708178B (zh) * 2018-07-09 2022-06-21 中兴通讯股份有限公司 网络部署方法及装置
CN109067573B (zh) * 2018-07-26 2020-12-29 新华三技术有限公司 一种流量调度方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
CN104811328A (zh) * 2014-01-27 2015-07-29 杭州华三通信技术有限公司 虚拟网络资源管理方法及装置
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN105049293A (zh) * 2015-08-21 2015-11-11 中国联合网络通信集团有限公司 监控的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
CN104811328A (zh) * 2014-01-27 2015-07-29 杭州华三通信技术有限公司 虚拟网络资源管理方法及装置
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN105049293A (zh) * 2015-08-21 2015-11-11 中国联合网络通信集团有限公司 监控的方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110034944A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 网络切片部署方法及其装置
EP3720050A4 (en) * 2018-03-29 2021-01-20 Huawei Technologies Co., Ltd. NETWORK TRENCH DEPLOYMENT METHOD AND APPARATUS
US11283684B2 (en) 2018-03-29 2022-03-22 Huawei Technologies Co., Ltd. Network slice deployment method and apparatus
WO2023061153A1 (zh) * 2021-10-11 2023-04-20 中兴通讯股份有限公司 网络服务部署方法、装置及计算机可读存储介质

Also Published As

Publication number Publication date
CN106936619A (zh) 2017-07-07
CN106936619B (zh) 2020-10-09

Similar Documents

Publication Publication Date Title
WO2017114219A1 (zh) 部署网络服务的方法和装置
US10432460B2 (en) Network service scaling method and apparatus
US11296923B2 (en) Network fault originator identification for virtual network infrastructure
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
AU2015419073B2 (en) Life cycle management method and device for network service
WO2016119631A1 (zh) 一种接入云服务的方法及接入设备
US20190109756A1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
US10924966B2 (en) Management method, management unit, and system
US20190065234A1 (en) Network function virtualization management and orchestration apparatus, method, and program
CN105593817B (zh) 本地或分布式计算机系统上的柔性节点组成的方法和系统
CN105095023B (zh) 一种云主机创建装置、方法和计算设备
US20200403970A1 (en) Providing Network Address Translation in a Software Defined Networking Environment
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
WO2018076547A1 (zh) 网络切片的管理方法、管理单元及系统
US10892948B2 (en) Creating and using service control functions
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
US20180034709A1 (en) Method and Device for Asset Information Management
US20180004563A1 (en) Orchestrator apparatus, system, virtual machine creation method, and computer-readable recording medium
WO2016058409A1 (zh) 控制报文传输的方法、装置和网络功能虚拟化系统
CN108370329B (zh) 管理功能对象的管理方法及装置
JP7450072B2 (ja) 仮想化ネットワーク・サービス配備方法及び装置
CN111581203B (zh) 信息处理方法、装置及存储介质
WO2022089291A1 (zh) 一种数据流镜像方法及装置
WO2015117498A1 (zh) 一种发现拓扑网络的方法、网络设备及存储介质

Legal Events

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

Ref document number: 16881008

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16881008

Country of ref document: EP

Kind code of ref document: A1