WO2017188387A1 - ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム - Google Patents
ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム Download PDFInfo
- Publication number
- WO2017188387A1 WO2017188387A1 PCT/JP2017/016763 JP2017016763W WO2017188387A1 WO 2017188387 A1 WO2017188387 A1 WO 2017188387A1 JP 2017016763 W JP2017016763 W JP 2017016763W WO 2017188387 A1 WO2017188387 A1 WO 2017188387A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- virtual machine
- vim
- nfvi
- network function
- vnf
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
-
- 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/45562—Creating, deleting, cloning virtual machine instances
-
- 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/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/503—Resource availability
Definitions
- the present invention is based on the priority claim of Japanese patent application: Japanese Patent Application No. 2016-090735 (filed on Apr. 28, 2016), the entire contents of which are incorporated herein by reference. Shall.
- the present invention relates to a network function virtualization management orchestration apparatus, method, and program.
- NFV Network Functions Virtualization
- VM Virtual Machine
- Virtualization Layer Virtualization Layer
- HV hypervisor
- Fig. 9 is a figure quoted from Figure 5.1 (The NFV-MANO architectural framework with reference points) on page 23 of Non-Patent Document 1.
- a VNF (Virtualized Network Function) 22 corresponds to an application operating on a virtual machine (VM) on the server, and realizes a network function in software.
- Each VNF 22 is provided with a management function called EM (Element Manager: Element Management) 23 (also referred to as EMS (Element Management System)).
- NFVI (Network Functions Virtualization Infrastructure) 21 is a virtualized computing / virtualized storage / virtualized system that virtualizes hardware resources of physical machines (servers) such as computing, storage, and network functions in a virtualization layer such as a hypervisor. This is a platform that can be flexibly handled as a virtual hardware resource such as a virtual network.
- NFV-MANO NFV Management & Orchestration
- 10 NFV Orchestrator NFV Orchestrator: NFVO
- 11 is the NFVI 21 resource orchestration and network service (Network Service: NS) instance life cycle management (NS) instance (Instantiation), scaling (Scaling), termination (Termination), update (Update), etc.). It also manages the NS catalog 14 (NSD / VLD / VNFFGD) and the VNF catalog 15 (VNFD (VNF / PNFD)), and has a repository 16 for NFV instances and a repository 17 for NFVI resources.
- VNF Manager VNFM
- VNF instance life cycle management for example, instantiation, update, query, scaling, termination, etc.
- event notification for example, instantiation, update, query, scaling, termination, etc.
- a virtualized infrastructure manager (VIM) 13 performs NFVI 21 computing, storage, network resource management, NFVI 21 failure monitoring, NFVI 21 resource monitoring, and the like.
- OSS Operations Support Systems
- BSS Business Support systems
- information systems devices, software, mechanisms, etc.
- the NS catalog 14 represents a network service (NS) repository.
- NS Catalog is a network service (NS) deployment template (Network Service Descriptor: NSD), virtual link descriptor (Virtual Link Descriptor: VLD), VNF Forwarding Graph Descriptor (VNFDGrFrGrFrG) Support generation and management.
- NSD Network Service Descriptor
- VLD Virtual Link Descriptor
- VNF Forwarding Graph Descriptor VNFDGrFrGrFrG
- the VNF catalog (VNF catalog) 15 represents a repository of on-board VNF packages (on-boarded VNF packages), for example.
- the VNF catalog (VNF catalog) 15 includes VNFD (VNF Descriptor), PNFD (PNF Descriptor), and the like.
- NFV instance repository (NFV instance Repository) 16 holds instance information of all VNFs and all network services (NS).
- the VNF instance and NS instance are described in the VNF and NS records, respectively. These records are updated to reflect the execution results of the VNF life cycle management operation and the NS life cycle management operation in the life cycle of each instance.
- the NFVI resource repository (NFVI Resources Repository) 17 holds information on resources of the NFVI 21 extracted by the VIM 13 and is available / reserved / allocated. Provide useful information for monitoring, etc.
- the NFVI resource repository 17 transfers the reserved / allocated resources of the NFVI 21 to NS and VNF instances associated with these resources (such as the number of virtual machines used by the VNF 22 at any point in the VNF 22 life cycle). Therefore, it is important for resource orchestration of the NFVO 11.
- the reference point Os-Ma-nfvo is a reference point between the OSS / BSS 30 and the NFVO 11, -Network service lifecycle management request (Network Service Lifecycle management), -VNF lifecycle management request (VNF Lifecycle management request), Used for transferring state information related to NFV, exchanging policy management information, etc.
- the reference point Vi-Vnfm is A resource allocation request from the VNFM 12 to the VIM 13; Used to exchange virtual resource configuration and status information.
- Reference point Ve-Vnfm-em is between EMS23 and VNFM12. ⁇ VNF instantiation, VNF instance search, update, termination, scale out / in, scale up / down, Used for configuration from the EM (EMS) 23 to the VNFM 12, event transfer, VNF configuration from the VNFM 12 to the VNF 22, event notification, and the like.
- Ve-Vnfm-vnf is between VNF22 and VNFM12, Used for VNF instantiation, VNF instance search, update, termination, scale out / in, scale up / down, VNF to VNFM configuration, event forwarding, VNF configuration from VNFM12 to VNF22, event notification, etc. It is done.
- the reference point Nf-Vi is a resource allocation request such as allocation of a virtual machine (VM), update of VM resource allocation, VM migration, termination of VM, creation / deletion of connection between VMs, together with an instruction of computing / storage resources Are used for allocation of virtualization resources, transfer of status information of virtualization resources, exchange of configuration and status information of hardware resources, and the like.
- VM virtual machine
- update of VM resource allocation VM migration
- termination of VM creation / deletion of connection between VMs
- the reference point Vn-Nf represents an execution environment provided to the VNF 22 by the NFVI 21.
- the reference point Or-Vnfm is Used for resource-related requests (authentication, reservation, allocation, etc.) by the VNFM 12, transfer of configuration information to the VNFM 12, and collection of VNF status information.
- the reference point Or-Vi is Used for exchanging resource information (reservation resource request), resource allocation request (allocation resource request), and virtual resource configuration and status information from the NFVO 11 to the VIM 13 (see Non-Patent Document 1 for details).
- NSD Network Service Descriptor
- NS Catalog 14 is a network service deployment template (Network Service Deployment Template), and scripts / network functions for specific life cycle events (instantiation, termination, scaling, etc.) Has an entity that defines the workflow.
- VNFFGD VNF Forwarding Graph Descriptor
- VNFFGD VNF Forwarding Graph Descriptor
- VLD Virtual Link Descriptor
- the VNFD (VNF Descriptor) of the VNF catalog 15 is a deployment template that describes VNFs from the viewpoint of deployment and operational behavior requirements (development and operational behaviors).
- the VNFD is mainly used by the VNFM 12 in VNF instantiation and instantiation lifecycle management.
- the VNFD is used by the NFVO 11 for management and orchestration of network resources and virtual resources on the NFVI 21 (computer system / middleware / service deployment / setting / management automation). It includes connectivity interface KPI (Key Performance Indicators) requirements used in NFVO11 for building a virtual link between a VNFC instance of NFVI21 or a VNF instance and endpoints to other network functions.
- KPI Key Performance Indicators
- PNFD Physical Network Function Descriptor: PNFD
- VNF catalog 15 describes the connectivity, connectivity, and KPI requirements of virtual links to the attached physical network function. Necessary when a physical device is incorporated in the NS, facilitating network expansion.
- An NS or VNF instantiation operation is executed from the OSS / BSS 30 or the VNFM 12 to the NFVO 11.
- a record representing a newly generated instance is generated.
- each record generated based on information given in each descriptor and additional runtime information related to the component instance provides data for modeling the instance state of the network service (NS).
- NS Network Service Record
- VNFFG Record: VNFFFGR VNFFG Record: VNFFFGR
- VLR Virtual Link Record
- VNF record Virtualized Network Function Record: VNFR
- PNF record Physical Network Function Record: PNFR
- the NSR, VNFR, VNFFGR, and VLR information elements provide a set of data items necessary for modeling the state of NS, VNF, VNFFG, and VL instances.
- a PNF record represents an instance related to PNF that already exists in NS and includes a runtime attribute (connectivity to NFVO) of PNF information.
- the placement of the virtual machine (VM) is a function sharing performed by the VIM 13. Further, in many cases, the VIM 13 described above is mounted based on OpenStack, but the placement of the virtual machine (VM) cannot be realized by the VIM 13 based on OpenStack. Therefore, in OPNFV (Open Platform for NFV) that implements NFV in an open source, the Promise WG is studying that the VIM 13 has the optimal placement logic of the virtual machine (VM), but is this function incorporated? The situation is indeterminate.
- OPNFV Open Platform for NFV
- the VIM 13 functions required by the NFV standard architecture cannot be realized by the VIM 13 implemented based on OpenStack. Therefore, when it becomes necessary to generate a virtual machine (VM) during execution of the VNF life cycle, the VNFM 12 sends a virtual machine (VM) generation request to the VIM 13 and an arrangement rule (at the time of virtual machine (VM) generation) AZ (Availability Zone) selection, PM (Physical Machine) selection, Anti-Affinity rule designation, Different Host Filter designation, etc.) are designated for the VIM 13.
- AZ Availability Zone
- PM Physical Machine
- Anti-Affinity rule designation Different Host Filter designation, etc.
- the VIM 13 by OpenStack at the time of filing does not support the optimal placement function of the virtual machine (VM), and the virtual machine (VM) placement rule at the time of virtual machine (VM) generation is transmitted from the VNFM 12 to the VIM 13
- the virtual machine (VM) is instructed indirectly from the VNFM 12. Therefore, in some cases, the virtual machine (VM) may be arranged at an arrangement destination that is not intended by the NFVO 11 or the VNFM 12.
- the present invention relates to a network function virtualization management orchestration apparatus, method, and program that contributes to enabling the optimal placement of virtual machines while using a VIM that does not have a virtual machine (VM) placement destination determination function.
- the purpose is to provide.
- NFVI Network Function Virtualization Infrastructure
- VIM Virtualized Infrastructure Manager
- the upper entity collects the resource information of the NFVI from the VIM, and arranges the virtual machine based on the collected resource information of the NFVI
- a network function virtualization management orchestration device is provided in which a destination is determined and the VIM generates a virtual machine at the determined placement destination of the virtual machine.
- NFVI Network Function Virtualization Infrastructure
- VIM Virtualized Infrastructure Manager
- a step of collecting the NFVI resource information from the VIM and a virtual machine placement destination are determined based on the collected NFVI resource information
- a network function virtualization management orchestration method including the step of generating a virtual machine at the determined virtual machine placement destination.
- NFVI Network Function Virtualization Infrastructure
- VNF virtual network function
- a network function virtualization management orchestration device including a VIM (Virtualized Infrastructure Manager)
- a virtual machine placement destination is determined based on the process of collecting the NFVI resource information from the VIM and the collected NFVI resource information
- a program for causing a computer to execute a process for generating a virtual machine at the determined placement destination of the virtual machine can be recorded on a computer-readable storage medium.
- the storage medium may be non-transient such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, or the like.
- the present invention can also be embodied as a computer program product.
- a network function virtualization management orchestration that contributes to enabling optimal placement of virtual machines while using a VIM that does not have a virtual machine (VM) placement destination determination function.
- An apparatus, method, and program are provided.
- a network function virtualization management orchestration apparatus (NFV-MANO) 100 includes a VIM 101 and an upper entity 102 of the VIM 101.
- the VIM 101 performs resource management and control of NFVI (Network Function Virtualization Infrastructure) that provides an execution base of VNF (Virtual Network Function) implemented by software operating on a virtual machine.
- the upper entity 102 collects NFVI resource information from the VIM 101, and determines the placement destination of the virtual machine based on the collected NFVI resource information.
- the VIM 101 generates a virtual machine at the determined placement destination of the virtual machine.
- NFV-MANO network function virtualization management orchestration device 100
- an upper entity of the VIM 101 upper node; for example, NFVO, VNFM
- the placement destination of the virtual machine (VM) is determined in consideration of the NFVI resource information.
- optimization of a virtual machine (VM) can be realized while using a VIM that does not have a virtual machine (VM) placement destination determination function.
- FIG. 2 is a diagram illustrating an example of a network system configuration according to the first embodiment.
- the network system includes a network function virtualization management orchestration device (NFV) including an NFV orchestrator (NFVO) 11, a VNF manager (VNFM) 12, and a virtualization infrastructure manager (VIM) 13. -MANO) 10.
- NFV network function virtualization management orchestration device
- NFVO NFV orchestrator
- VNFM VNF manager
- VIP virtualization infrastructure manager
- NFVO11, VNFM12, and VIM13 are functional entities that manage the network system.
- the VIM 13 is an entity that generates a virtual machine (VM) and a VNF on a physical machine (PM) under the control of the NFVO 11 and the VNFM 12, and the NFVO 11 and the VNFM 12 function as an upper entity of the VIM 13.
- VM virtual machine
- PM physical machine
- the network system includes a physical machine (PM) 20 and an OSS / BSS 30.
- the physical machine 20 includes an NFVI 21, and a VNF 22 and an EMS 23 are configured on the NFVI 21.
- the network system shown in FIG. 2 provides a communication function by a virtual server (VNF 22) realized by software in a virtual machine (VM) configured on the physical machine 20.
- VNF 22 virtual server
- VM virtual machine
- FIG. 2 one physical machine 20 is illustrated, but actually, a plurality of physical machines 20 are included in the network system.
- FIG. 3 is a block diagram illustrating an example of a hardware configuration of the physical machine 20 according to the first embodiment.
- the physical machine 20 is a so-called information processing apparatus (computer) and has a configuration illustrated in FIG.
- the physical machine 20 includes a CPU (Central Processing Unit) 51, a memory 52, an input / output interface 53, a NIC (Network Interface Card) 54 that is a communication means, and the like that are connected to each other via an internal bus.
- a CPU Central Processing Unit
- memory 52 for example, the physical machine 20 includes a CPU (Central Processing Unit) 51, a memory 52, an input / output interface 53, a NIC (Network Interface Card) 54 that is a communication means, and the like that are connected to each other via an internal bus.
- NIC Network Interface Card
- the configuration shown in FIG. 3 is not intended to limit the hardware configuration of the physical machine 20.
- the physical machine 20 may include hardware (not shown).
- the number of CPUs included in the physical machine 20 is not limited to the example illustrated in FIG. 3.
- a plurality of CPUs may be included in the physical machine 20.
- the memory 52 is a RAM (Random Access Memory), a ROM (Read Only Memory), or an auxiliary storage device (such as a hard disk).
- the input / output interface 53 is a means that serves as an interface for a display device and an input device (not shown).
- the display device is, for example, a liquid crystal display.
- the input device is a device that accepts user operations such as a keyboard and a mouse, for example.
- each server device constituting the NFVO 11, VNFM 12, VIM 13, and OSS / BSS 30 is basically the same as the configuration of the physical machine 20 and is obvious to those skilled in the art, and thus description thereof is omitted. .
- FIG. 4 is a diagram for explaining the NFV-MANO 10 according to the first embodiment in terms of functions.
- the NFVO 11 includes a VNF generation control unit 201, an NFVI resource acquisition unit 202, and a virtual machine placement destination determination unit 203.
- the VNF generation control unit 201 is a unit that performs control related to VNF generation. Specifically, the VNF generation control unit 201 receives a request for VNF generation from a transmission source (Sender; maintenance person or higher-level device). The VNF generation control unit 201 that has received the request requests the VNFM 12 to generate VNF.
- a transmission source Send; maintenance person or higher-level device.
- the VNF generation control unit 201 that has received the request requests the VNFM 12 to generate VNF.
- the NFVI resource acquisition unit 202 is a means for acquiring NFVI resource information. Specifically, the NFVI resource acquisition unit 202 requests the VIM 13 to provide NFVI resource information. The NFVI resource acquisition unit 202 acquires AZ (Availability Zone) resource information and PM resource information from the VIM 13 as NFVI resource information.
- the AZ resource information includes information related to PMs constituting each availability zone.
- the PM resource information includes information related to virtual machines (VMs) that are already arranged in each physical machine.
- VMs virtual machines
- the virtual machine placement destination determination unit 203 is a means for determining the placement destination of the virtual machine (VM) based on the NFVI resource information acquired (collected) from the VIM 13. Specifically, the virtual machine placement destination determination unit 203, based on the NFVI resource information, the virtual machine (VM) so that the virtual machines are intensively arranged in one zone (AZ) or physical machine (PM). Or a virtual machine (VM) placement destination is determined so that the virtual machine is distributed and placed in a zone or a physical machine (PM). Note that the virtual machine (VM) placement destination determination by the virtual machine placement destination determination unit 203 (determination of the optimal placement of the VM) is not limited to the above, and various types can be considered.
- the virtual machine placement destination determination unit 203 notifies the VNFM 12 of the determined placement location of the virtual machine (VM). Specifically, when transmitting a response (VNF generation permission) to a VNF generation permission request from the VNFM 12 to be described later (VNF generation permission), the virtual machine placement destination determination unit 203 specifies an identifier that specifies the placement destination of the virtual machine as a parameter of the response ( In the following, the virtual machine placement destination is specified by including a VM placement destination ID (Identifier). It is desirable that the VM placement destination ID indicating the placement destination of the virtual machine (VM) is an identifier that can be used in the current OpenStack, such as AZ ID or hostname.
- the VNFM 12 includes a VNF generation unit 211 and a resource allocation request unit 212.
- the VNF generation unit 211 is a unit that generates the VNF 22 in the physical machine 20. Specifically, when receiving a request for VNF generation from the NFVO 11, the VNF generation unit 211 transmits a VNF generation permission request to the NFVO 11. When the VNF generation unit 211 obtains a response indicating that the virtual machine (VM) resource allocation has been completed from the VIM 13, the VNF generation unit 211 generates a VNF 22 in the physical machine 20 corresponding to the VM allocation destination ID (setting necessary for VNF allocation). I do).
- VM virtual machine
- the resource allocation request unit 212 is a means for making an NFVI resource allocation request (Allocate Resources) to the VIM 13. At that time, the resource allocation request unit 212 transmits a resource allocation request including the VM placement destination ID acquired from the NFVO 11 to the VIM 13.
- the VIM 13 includes an NFVI resource information providing unit 221 and a resource allocation unit 222.
- the NFVI resource information providing unit 221 is a means for processing a request for providing NFVI resource information from the NFVO 11. Specifically, when the NFVI resource information providing unit 221 receives the request from the NFVO 11, the NFVI resource information providing unit 221 includes the NFVI resource information managed by itself in the response to the request.
- the resource allocation unit 222 is a means for processing a resource allocation request from the VNFM 12. Specifically, the resource allocation unit 222 generates a network resource related to the designated virtual machine (VM) in the physical machine corresponding to the “VM placement destination ID” included in the resource allocation request acquired from the VNFM 12. to start. When the resource assignment is completed, the resource assignment unit 222 responds to the VNFM 12 that the placement of the virtual machine (VM) in the VM placement destination ID is completed.
- VM virtual machine
- FIG. 5 is a sequence diagram illustrating an example of the operation of the network system according to the first embodiment.
- the operation of the VM placement that is executed at the time of VNF instantiation in the VNF life cycle will be described.
- step S101 the transmission source (maintenance person or host device) instructs the NFVO 11 to generate VNF.
- step S ⁇ b> 102 the NFVO 11 that has received the instruction issues an instruction (request) related to VNF generation to the VNFM 12.
- step S103 the VNFM 12 transmits a VNF generation permission request to the NFVO 11. Specifically, the VNFM 12 specifies a VNF using a grant lifecycle operation (Grant Lifecycle Operation), and requests the NFVO 11 to permit the instantiation.
- Grant Lifecycle Operation a grant lifecycle operation
- step S104 the NFVO 11 requests the VIM 13 for NFVI resource information.
- step S105 the VIM 13 responds to the request from the NFVO 11 to transmit the NFVI resource information managed by itself to the NFVO 11.
- step S106 the NFVO 11 determines the placement destination of the virtual machine (VM) based on the NFVI resource information acquired from the VIM 13.
- step S107 the NFVO 11 grants VNF generation permission in which the determined virtual machine (VM) placement destination (VM placement destination ID) and the placement destination VIM identifier (VIM ID) are set, and the VNF from the VNFM 12 in step S103. Sent as an acknowledgment (ACK) to the generation permission request.
- VM placement destination ID the determined virtual machine
- VIM ID the placement destination VIM identifier
- step S108 the VNFM 12 requests the VIM 13 to allocate resources (Allocate Resources). At that time, the VNFM 12 requests the VIM 13 to generate and start a virtual machine (VM) at the placement destination designated by the NFVO 11 (placement destination based on the VM placement destination ID).
- VM virtual machine
- step S109 the VIM 13 generates and activates a network resource related to the virtual machine (VM) at the designated placement destination, and transmits an acknowledgment (ACK) to the VNFM 12.
- VM virtual machine
- ACK acknowledgment
- step S110 the VNFM 12 sets the VNF 22 by setting parameters specific to the deployment.
- step S111 the VNFM 12 notifies the EMS 23 that the VNF 22 has been instantiated using the VNF life cycle change notification interface (VNF Lifecycle Change Notification interface).
- step S112 the EMS 23 and the VNFM 12 add the instantiated VNF 22 as a managed device.
- step S113 the EMS 23 sets the VNF 22 with application-specific parameters.
- step S114 the VNFM 12 notifies the NFVO 11 of the successful instantiation of the VNF 22 through the VNF life cycle change notification interface (VNF Lifecycle Change Notification interface).
- step S115 the NFVO 11 maps the instantiated VNF 22 to the VIM 13 and the resource pool (positions the VNF 22).
- the NFVO 11 collects NFVI resource information between the NFVO 11 and the VIM 13 (steps S104 and S105 in FIG. 5). Then, the NFVO 11 determines the optimal placement destination of the virtual machine (VM) based on the collected NFVI resource information (step S106). Thereafter, an identifier indicating the placement destination of the virtual machine (VM placement destination ID) is notified between the NFVO 11 and the VNFM 12, and the VNFM 12 uses the notified identifier to generate a virtual machine (VM) generation request. (Steps S107 and S108). The VIM 13 generates a virtual machine (VM) in the virtual machine placement destination determined by the NFVO 11 (step S109).
- VM placement destination ID an identifier indicating the placement destination of the virtual machine
- VNFM 12 uses the notified identifier to generate a virtual machine (VM) generation request.
- the NFVO 11 has a function of determining the placement destination of the virtual machine (VM). This makes it possible to arrange an optimal virtual machine (VM) in an NFV environment.
- the VIM (VIM by OpenStack) 13 that does not have the Promise function makes a virtual machine arrangement reservation in advance (before the VNFM 12 requests VM generation) during execution of the VNF life cycle, and notifies the reservation ID through the Or-Vi interface. I can't do it.
- a VIM 13 that does not have the Promise function can provide NFVO 11 with NFVI resource information managed by the VIM 13. Therefore, instead of the reservation sequence (notification of reservation ID) between the NFVO 11 and the VIM 13, the NFVO 11 collects NFVI resource information and determines the placement destination of the virtual machine (VM).
- the NFVO 11 determines the placement destination of the virtual machine (VM).
- the VNFM 12 may not be able to specify a flexible placement rule according to the VNF configuration, which may cause inconvenience. is there. Therefore, in the second embodiment, a VNFM 12 that performs optimal virtual machine (VM) placement on the premise of using the VIM 13 implemented by the current OpenStack will be described.
- FIG. 6 is a diagram for explaining the NFV-MANO 10 according to the second embodiment in terms of functions.
- the difference between FIG. 4 and FIG. 6 is that the processing blocks by the NFVI resource acquisition unit 202 and the virtual machine placement destination determination unit 203 included in the NFVO 11 are included in the VNFM 12 as the NFVI resource acquisition unit 213 and the virtual machine placement destination determination unit 214. Is a point. Note that the basic operation of each processing block described in FIG. 4 and FIG. 6 can be the same, and thus detailed description of each processing block is omitted.
- FIG. 7 is a sequence diagram illustrating an example of the operation of the network system according to the second embodiment.
- FIG. 7 corresponds to FIG. 5 described in the first embodiment, and includes steps S101 to S103 shown in FIG. 5, steps S201 to S203 shown in FIG. 7, and step S108 shown in FIG. To S115 and steps S208 to S215 shown in FIG. 7 are the same operations. Therefore, the description of the above steps shown in FIG. 7 is omitted.
- step S204 the NFVO 11 that has received the VNF generation permission request transmits an acknowledgment (ACK) including the VIM identifier to the VNFM 12 in response to the request.
- ACK acknowledgment
- step S205 the VNFM 12 requests the VIM 13 for NFVI resource information.
- step S206 the VIM 13 transmits NFVI resource information managed by itself to the VNFM 12 by responding to the request from the VNFM 12.
- step S207 the VNFM 12 determines the placement destination of the virtual machine (VM) based on the NFVI resource information acquired from the VIM 13. Thereafter, the VNFM 12 makes a resource allocation request to the VIM 13 including an identifier (VM placement destination ID) that specifies the placement destination of the determined virtual machine (VM) (step S208).
- VM placement destination ID an identifier that specifies the placement destination of the determined virtual machine (VM)
- the NFVI resource information is provided from the VIM 13 to the higher-level entities (NFVO11, VNFM12), but the resource information that can be collected is limited in the information granularity of the current OpenStack. Specifically, the above-described AZ resource information and PM resource information are only collected and provided, and resource information (remaining resource information) that can be used in the physical machine (PM) cannot be collected accurately. . For this reason, the VNFM 12 cannot perform strict optimal placement of virtual machines (VMs) in consideration of remaining resource information in each physical machine (PM). Therefore, as a modified example according to the second embodiment, an optimal arrangement of virtual machines (VM) taking into account the remaining resource information in the physical machine (PM) will be described.
- VM virtual machines
- an upper limit of resources for each physical machine 20 (upper limit information regarding resources) is registered in advance in the VNFM 12.
- the registered resource upper limit is handled as static information in the NFVI resource information.
- the NFVI resource information collected from the VIM 13 changes as a virtual machine (VM) is generated in the physical machine (PM), and thus is handled as dynamic information in the NFVI resource information.
- the virtual machine placement destination determination unit 214 calculates remaining resource information by subtracting dynamic information (the amount of resources allocated to the virtual machine) from static information (resource upper limit of the physical machine) of NFVI resource information.
- dynamic information the amount of resources allocated to the virtual machine
- static information resource upper limit of the physical machine
- FIG. 8 is a sequence diagram showing the operation of the modified example according to the second embodiment.
- the difference between FIG. 7 and FIG. 8 is limited to steps S207 and S207a due to the difference in function of the virtual machine placement destination determination unit 214, and the description regarding FIG. 8 is omitted.
- VM virtual machine
- the VNFM 12 determines the placement destination of the virtual machine (VM). At that time, the VNFM 12 collects NFVI resource information (steps S205 and S206), and uses the collected NFVI resource information (or the physical machine resource upper limit; a modified example) to determine the optimal placement destination of the virtual machine (VM). decide.
- VIM virtual machine not having the Promise function 13 implemented by OpenStack
- the flexible virtual machine can be arranged in the NFV environment by the VNFM 12.
- the network systems described in the first and second embodiments are examples, and are not intended to limit the configuration and operation.
- the placement destination determination method of the virtual machine (VM) described in the first and second embodiments can be applied to ScaleOut and Healing that allocates NFVI resources from the VNFM 12. It is.
- the VIM 13 does not make a resource reservation.
- the resource (virtual machine placement destination) selected by the NFVO 11 may be the virtual machine (VM) in step S108.
- the VNFM 12 may notify a plurality of identifiers in the notification of the VM placement destination ID in step S107 so that another resource can be specified and the virtual machine (VM) generation request can be retried. Good. That is, the NFVO 11 calculates a plurality of candidates that can be placement destinations of virtual machines based on the NFVI resource information.
- the NFVO 11 transmits VM placement destination IDs corresponding to the calculated plurality of candidates (virtual machine placement destination candidates) to the VNFM 12.
- the VNFM 12 selects one from the acquired plurality of VM placement destination IDs, and issues a virtual machine (VM) generation request to the VIM 13. If the request cannot be processed normally by the VIM 13, a virtual machine (VM) is generated by selecting another VM placement destination ID from the acquired plurality of VM placement destination IDs and transmitting it to the VIM 13. Retry the request.
- the priority order when the VNFM 12 selects from a plurality of identifiers may be notified from the NFVO 11 to the VNFM 12.
- the placement destination determination of the virtual machine (VM) by the higher-order entity described in the above embodiment may be combined with the placement destination determination of the virtual machine (VM) based on the placement rule sent from the VNFM 12 to the VIM 13.
- both the VM placement destination ID and the placement rule are transmitted from the VNFM 12 to the VIM 13 (the VM placement destination ID and the placement rule are notified from the NFVO 11 to the VNFM 12 on the same signal), and the VIM 13 places the placement destination based on the VM placement destination ID. If a virtual machine (VM) cannot be generated, a virtual machine (VM) may be generated according to the placement rule.
- a placement rule including a rule (Filter rule) for filtering the placement destination of the virtual machine (VM) is transmitted to the VIM 13, and the placement destination of the virtual machine (VM) from the higher-order entity with respect to the rule and the VIM 13
- VMs virtual machines
- the VIM 13 in which the Promise function by OpenStack is not implemented is connected to the NFVO 11 and the VNFM 12.
- the NFVO 11 determines the specifications of the VIM 13 (the presence or absence of the Promise function) and switches (selects) necessary processing. Specifically, when the VIM 13 does not have the Promise function, the NFVO 11 performs the control and processing described in the above embodiment.
- the NFVO 11 may entrust the placement of the virtual machine (VM) to the VIM 13.
- VM virtual machine
- Various methods are conceivable for determining the function of the VIM 13 (determining whether the Promise function is present). For example, a method of registering the functions of each of the plurality of VIMs 13 in advance in the NFVO 11 or a method of exchanging information (capability exchange) between the NFVO 11 and the VIM 13 can be used.
- each device illustrated in FIGS. 4 and 6 can be realized by a computer program that causes a computer installed in each device to execute the above-described processing using its hardware. That is, a part or all of each means may be realized by a program executed by a computer (processor or the like), and the function performed by each processing module described above is executed by some hardware and / or software. There should be a means to do this.
- [Form 1] The network function virtualization management orchestration apparatus according to the first aspect described above.
- [Form 2] The upper entity requests the VIM to provide resource information of the NFVI, The network function virtualization management orchestration apparatus according to the first aspect, wherein the VIM provides resource information of the NFVI to the upper entity in response to the request.
- [Form 3] The upper entity holds in advance upper limit information related to the resource of the physical machine that is the placement destination of the virtual machine, and determines the placement destination of the virtual machine based on the upper limit information and the resource information of the NFVI. Or the network function virtualization management orchestration device of 2.
- the network function virtualization management orchestration device according to any one of aspects 1 to 3, wherein the higher-level entity notifies the VIM of an identifier that designates the determined placement destination of the virtual machine.
- the upper entity is an NFVO (NFV-Orchestrator) that realizes a network service on the NFVI, preferably a network function virtualization management orchestration device according to mode 1.
- a VNFM (VNF Manager) for managing the life cycle of the VNF;
- the NFVO transmits an identifier for designating the placement destination of the determined virtual machine to the VNFM,
- the network function virtualization management orchestration device according to claim 5, wherein the VNFM transmits a virtual machine resource allocation request including the transmitted identifier to the VIM.
- the NFVO calculates a plurality of candidates as placement destinations of virtual machines, transmits the identifier corresponding to each of the calculated plurality of candidates to the VNFM, Preferably, the VNFM selects an identifier to be transmitted to the VIM from the plurality of transmitted identifiers, preferably the network function virtualization management orchestration device according to mode 6.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
本発明は、日本国特許出願:特願2016-090735号(2016年 4月28日出願)の優先権主張に基づくものであり、同出願の全記載内容は引用をもって本書に組み込み記載されているものとする。
本発明は、ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラムに関する。
・ネットワークサービスのライフサイクル管理要求(Network Service Lifecycle management)、
・VNFライフサイクル管理要求(VNF Lifecycle management request)、
・NFV関連の状態情報の転送、ポリシ管理情報の交換等に用いられる。
・VNFM12からVIM13へのリソース割り当て要求、
・仮想化リソースの構成と状態情報の交換に用いられる。
・VNFのインスタンシエーション、VNFインスタンス検索、更新、終了、スケールアウト/イン、スケールアップ/ダウン、
・EM(EMS)23からVNFM12への構成、イベントの転送、VNFM12からVNF22へのVNF構成、イベントの通知等に用いられる。
・VNFのインスタンシエーション、VNFインスタンス検索、更新、終了、スケールアウト/イン、スケールアップ/ダウン、VNFからVNFMへの構成、イベントの転送、VNFM12からVNF22へのVNFの構成、イベントの通知等に用いられる。
・VNFM12によるリソース関連要求(認証、予約(reservation)、割り当て等)、VNFM12への構成情報の転送、VNFの状態情報の収集に用いられる。
・NFVO11からのVIM13ヘのリソース予約要求(reserve resource request)、リソース割り当て要求(allocate resource request)と仮想化リソースの構成と状態情報の交換に用いられる(詳細は非特許文献1参照)。
・ネットワークサービスレコード(Network Service Record:NSR)、
・VNFFGレコード(VNFFG Record :VNFFGR)、
・仮想リンクレコード(Virtual Link Record :VLR)、
・VNFレコード(Virtualized Network Function Record:VNFR)、
・PNFレコード(Physical Network Function Record:PNFR)
がある。NSR、VNFR、VNFFGR、VLR情報要素はNS、VNF、VNFFG、VLのインスタンスの状態のモデル化に必要なデータアイテム集合を提供する。PNFレコードはNSの部分をなし前から存在するPNFに関連したインスタンスを表し、PNF情報のランタイム属性(NFVOへのコネクティビティ)を含む。
なお、このプログラムは、コンピュータが読み取り可能な記憶媒体に記録することができる。記憶媒体は、半導体メモリ、ハードディスク、磁気記録媒体、光記録媒体等の非トランジェント(non-transient)なものとすることができる。本発明は、コンピュータプログラム製品として具現することも可能である。
第1の実施形態について、図面を用いてより詳細に説明する。
続いて、第2の実施形態について図面を参照して詳細に説明する。
次に、第2の実施形態に係る変形例を説明する。
[形態1]
上述の第1の視点に係るネットワーク機能仮想化管理オーケストレーション装置のとおりである。
[形態2]
前記上位エンティティは、前記VIMに対して前記NFVIのリソース情報の提供を要求し、
前記VIMは、前記要求に対する応答により前記NFVIのリソース情報を前記上位エンティティに提供する、好ましくは形態1のネットワーク機能仮想化管理オーケストレーション装置。
[形態3]
前記上位エンティティは、仮想マシンの配置先となる物理マシンのリソースに関する上限情報を予め保持すると共に、前記上限情報と前記NFVIのリソース情報に基づいて仮想マシンの配置先を決定する、好ましくは形態1又は2のネットワーク機能仮想化管理オーケストレーション装置。
[形態4]
前記上位エンティティは、前記決定された仮想マシンの配置先を指定する識別子を前記VIMに通知する、好ましくは形態1乃至3のいずれか一に記載のネットワーク機能仮想化管理オーケストレーション装置。
[形態5]
前記上位エンティティは、前記NFVI上にて、ネットワークサービスを実現するNFVO(NFV-Orchestrator)である、好ましくは形態1のネットワーク機能仮想化管理オーケストレーション装置。
[形態6]
前記VNFのライフサイクルを管理するVNFM(VNF Manager)をさらに含み、
前記NFVOは、前記決定された仮想マシンの配置先を指定する識別子を前記VNFMに送信し、
前記VNFMは、前記送信された識別子を含む、仮想マシンのリソース割り当て要求を前記VIMに送信する、好ましくは形態5のネットワーク機能仮想化管理オーケストレーション装置。
[形態7]
前記NFVOは、仮想マシンの配置先として複数の候補を算出し、前記算出された複数の候補それぞれに対応する前記識別子を前記VNFMに送信し、
前記VNFMは、前記送信された複数の識別子から前記VIMに送信する識別子を選択する、好ましくは形態6のネットワーク機能仮想化管理オーケストレーション装置。
[形態8]
前記上位エンティティは、前記VNFのライフサイクルを管理するVNFM(VNF Manager)である、好ましくは形態1のネットワーク機能仮想化管理オーケストレーション装置。
[形態9]
上述の第2の視点に係るネットワーク機能仮想化管理オーケストレーション方法のとおりである。
[形態10]
上述の第3の視点に係るプログラムのとおりである。
なお、形態9及び形態10は、形態1と同様に、形態2~形態8に展開することが可能である。
11 NFVO(NFV Orchestrator)
12 VNFM(VNF Manager)
13、101 VIM(Virtualized Infrastructure Manager)
14 NSカタログ
15 VNFカタログ
16 NFVインスタンスリポジトリ
17 NFVIリソースリポジトリ
20 物理マシン
21 NFVI
22 VNF
23 EM(EMS)
30 OSS/BSS
51 CPU
52 メモリ
53 入出力インターフェイス
54 NIC
102 上位エンティティ
201 VNF生成制御部
202、213 NFVIリソース取得部
203、214 仮想マシン配置先決定部
211 VNF生成部
212 リソース割り当て要求部
221 NFVIリソース情報提供部
222 リソース割り当て部
Claims (10)
- 仮想マシン上で動作するソフトウェアによって実装され仮想されたVNF(Virtual Network Function)の実行基盤を提供するNFVI(Network Function Virtualization Infrastructure)のリソース管理と制御を行うVIM(Virtualized Infrastructure Manager)と、
前記VIMの上位エンティティと、を含み、
前記上位エンティティは、
前記NFVIのリソース情報を前記VIMから収集し、
前記収集したNFVIのリソース情報に基づいて、仮想マシンの配置先を決定し、
前記VIMは、
前記決定された仮想マシンの配置先に仮想マシンを生成する、
ネットワーク機能仮想化管理オーケストレーション装置。 - 前記上位エンティティは、前記VIMに対して前記NFVIのリソース情報の提供を要求し、
前記VIMは、前記要求に対する応答により前記NFVIのリソース情報を前記上位エンティティに提供する、請求項1のネットワーク機能仮想化管理オーケストレーション装置。 - 前記上位エンティティは、仮想マシンの配置先となる物理マシンのリソースに関する上限情報を予め保持すると共に、前記上限情報と前記NFVIのリソース情報に基づいて仮想マシンの配置先を決定する、請求項1又は2のネットワーク機能仮想化管理オーケストレーション装置。
- 前記上位エンティティは、前記決定された仮想マシンの配置先を指定する識別子を前記VIMに通知する、請求項1乃至3のいずれか一項に記載のネットワーク機能仮想化管理オーケストレーション装置。
- 前記上位エンティティは、前記NFVI上にて、ネットワークサービスを実現するNFVO(NFV-Orchestrator)である、請求項1のネットワーク機能仮想化管理オーケストレーション装置。
- 前記VNFのライフサイクルを管理するVNFM(VNF Manager)をさらに含み、
前記NFVOは、前記決定された仮想マシンの配置先を指定する識別子を前記VNFMに送信し、
前記VNFMは、前記送信された識別子を含む、仮想マシンのリソース割り当て要求を前記VIMに送信する、請求項5のネットワーク機能仮想化管理オーケストレーション装置。 - 前記NFVOは、仮想マシンの配置先として複数の候補を算出し、前記算出された複数の候補それぞれに対応する前記識別子を前記VNFMに送信し、
前記VNFMは、前記送信された複数の識別子から前記VIMに送信する識別子を選択する、請求項6のネットワーク機能仮想化管理オーケストレーション装置。 - 前記上位エンティティは、前記VNFのライフサイクルを管理するVNFM(VNF Manager)である、請求項1のネットワーク機能仮想化管理オーケストレーション装置。
- 仮想マシン上で動作するソフトウェアによって実装され仮想されたVNF(Virtual Network Function)の実行基盤を提供するNFVI(Network Function Virtualization Infrastructure)のリソース管理と制御を行うVIM(Virtualized Infrastructure Manager)を含むネットワーク機能仮想化管理オーケストレーション装置において、
前記NFVIのリソース情報を前記VIMから収集するステップと、
前記収集したNFVIのリソース情報に基づいて、仮想マシンの配置先を決定するステップと、
前記決定された仮想マシンの配置先に仮想マシンを生成するステップと、
を含む、ネットワーク機能仮想化管理オーケストレーション方法。 - 仮想マシン上で動作するソフトウェアによって実装され仮想されたVNF(Virtual Network Function)の実行基盤を提供するNFVI(Network Function Virtualization Infrastructure)のリソース管理と制御を行うVIM(Virtualized Infrastructure Manager)を含むネットワーク機能仮想化管理オーケストレーション装置において、
前記NFVIのリソース情報を前記VIMから収集する処理と、
前記収集したNFVIのリソース情報に基づいて、仮想マシンの配置先を決定する処理と、
前記決定された仮想マシンの配置先に仮想マシンを生成する処理と、
をコンピュータに実行させるプログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17789669.3A EP3451594A4 (en) | 2016-04-28 | 2017-04-27 | DEVICE, METHOD AND ORGORIZATION PROGRAM FOR MANAGING NETWORK FUNCTION VIRTUALIZATION |
US16/079,249 US10719348B2 (en) | 2016-04-28 | 2017-04-27 | Network function virtualization management and orchestration apparatus, method, and program |
CN201780016735.5A CN108886492A (zh) | 2016-04-28 | 2017-04-27 | 网络功能虚拟化管理和编排装置、方法和程序 |
JP2018514706A JP6614340B2 (ja) | 2016-04-28 | 2017-04-27 | ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016090735 | 2016-04-28 | ||
JP2016-090735 | 2016-04-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017188387A1 true WO2017188387A1 (ja) | 2017-11-02 |
Family
ID=60159707
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/016763 WO2017188387A1 (ja) | 2016-04-28 | 2017-04-27 | ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US10719348B2 (ja) |
EP (1) | EP3451594A4 (ja) |
JP (1) | JP6614340B2 (ja) |
CN (1) | CN108886492A (ja) |
WO (1) | WO2017188387A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019132314A1 (ko) * | 2017-12-26 | 2019-07-04 | 삼성전자 주식회사 | 무선 통신 시스템에서 네트워크 기능 가상화를 위한 장치 및 방법 |
CN110943967A (zh) * | 2018-09-21 | 2020-03-31 | 中兴通讯股份有限公司 | 一种认证方法、装置和*** |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10686651B2 (en) * | 2016-06-20 | 2020-06-16 | Apple Inc. | End-to-end techniques to create PM (performance measurement) thresholds at NFV (network function virtualization) infrastructure |
MX2019001895A (es) * | 2016-08-18 | 2019-07-01 | Ericsson Telefon Ab L M | Proceso de diseño e implementacion de serivicios de red para sistemas de nfv. |
US11290353B2 (en) * | 2017-06-16 | 2022-03-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Derivation of network service descriptor from network service requirements |
US11382150B2 (en) * | 2018-03-26 | 2022-07-05 | Apple Inc. | System and method of managing PNF connectivity in a network slice instance |
GB2573283B (en) * | 2018-04-26 | 2020-04-29 | Metaswitch Networks Ltd | Improvements relating to network functions virtualization |
CN111726241B (zh) * | 2019-03-22 | 2023-05-19 | 中兴通讯股份有限公司 | 网络资源管理方法、***、网络设备和可读存储介质 |
CN111082960B9 (zh) * | 2019-04-15 | 2023-01-24 | 中兴通讯股份有限公司 | 数据的处理方法及装置 |
CN112436952B (zh) * | 2019-08-26 | 2022-05-13 | 中移(苏州)软件技术有限公司 | 一种信息获取方法、nfv-mano***和计算机存储介质 |
CN112463285A (zh) * | 2019-09-06 | 2021-03-09 | ***通信有限公司研究院 | 一种部署虚拟化的网络功能模块的方法及设备 |
CN110519730B (zh) * | 2019-09-11 | 2021-11-26 | 杭州芯云智创科技有限公司 | 一种业务***与nfv管理和编排对接的方法与装置 |
CN112887118B (zh) * | 2019-11-29 | 2024-05-31 | 中兴通讯股份有限公司 | Vnf信息获取及控制方法、装置、nfvo、vnfm及存储介质 |
CN114846445A (zh) * | 2019-12-20 | 2022-08-02 | 瑞典爱立信有限公司 | Vnf到vim的迁移 |
CN113328871B (zh) * | 2020-02-28 | 2022-08-12 | ***通信有限公司研究院 | 信令采集的配置方法、装置及存储介质 |
CN113726541B (zh) * | 2020-05-25 | 2023-11-07 | 中移(苏州)软件技术有限公司 | 一种网元配置的方法、装置、电子设备和存储介质 |
US11368409B2 (en) * | 2020-07-22 | 2022-06-21 | Nec Corporation | Method for customized, situation-aware orchestration of decentralized network resources |
CN114978912A (zh) * | 2021-02-23 | 2022-08-30 | 中国电信股份有限公司 | 资源授权方法、nfvo、网络***以及存储介质 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015194949A (ja) * | 2014-03-31 | 2015-11-05 | 株式会社Nttドコモ | 管理システム及び管理方法 |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2936754B1 (en) * | 2013-01-11 | 2020-12-02 | Huawei Technologies Co., Ltd. | Network function virtualization for a network device |
WO2015099036A1 (ja) * | 2013-12-27 | 2015-07-02 | 株式会社Nttドコモ | 管理システム、全体管理ノード及び管理方法 |
WO2015099035A1 (ja) * | 2013-12-27 | 2015-07-02 | 株式会社Nttドコモ | 管理システム、仮想通信機能管理ノード及び管理方法 |
WO2015146374A1 (ja) * | 2014-03-28 | 2015-10-01 | 株式会社Nttドコモ | 仮想化資源管理ノード及び仮想マシン移行方法 |
EP2940968A1 (en) * | 2014-04-30 | 2015-11-04 | Hewlett-Packard Development Company, L.P. | Network infrastructure management |
EP3142309B1 (en) * | 2014-06-05 | 2019-11-27 | Huawei Technologies Co., Ltd. | Method and apparatus for allocating reliability resource |
EP2955631B1 (en) * | 2014-06-09 | 2019-05-01 | Nokia Solutions and Networks Oy | Controlling of virtualized network functions for usage in communication network |
ES2726699T3 (es) * | 2014-08-07 | 2019-10-08 | Intel Ip Corp | Gestión de función de red virtualizada |
EP3855681A1 (en) * | 2014-09-25 | 2021-07-28 | Apple Inc. | Network functions virtualization |
US10356162B2 (en) * | 2014-10-14 | 2019-07-16 | Futurewei Technologies, Inc. | System and method for generic service NFV orchestration and management for converged services |
US9729396B2 (en) * | 2014-11-04 | 2017-08-08 | Cisco Technology, Inc. | System and method for providing dynamic radio access network orchestration |
WO2016093861A1 (en) * | 2014-12-12 | 2016-06-16 | Nokia Solutions And Networks Oy | Alarm correlation in network function virtualization environment |
WO2016128049A1 (en) * | 2015-02-12 | 2016-08-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for running a virtual machine |
CN107852337B (zh) * | 2015-07-23 | 2021-07-13 | 英特尔公司 | 支持网络功能虚拟化生命周期管理的网络资源模型 |
WO2017018965A1 (en) * | 2015-07-27 | 2017-02-02 | Intel IP Corporation | Virtual mobile management entity management |
US10116571B1 (en) * | 2015-09-18 | 2018-10-30 | Sprint Communications Company L.P. | Network Function Virtualization (NFV) Management and Orchestration (MANO) with Application Layer Traffic Optimization (ALTO) |
-
2017
- 2017-04-27 US US16/079,249 patent/US10719348B2/en active Active
- 2017-04-27 JP JP2018514706A patent/JP6614340B2/ja active Active
- 2017-04-27 EP EP17789669.3A patent/EP3451594A4/en not_active Withdrawn
- 2017-04-27 CN CN201780016735.5A patent/CN108886492A/zh active Pending
- 2017-04-27 WO PCT/JP2017/016763 patent/WO2017188387A1/ja active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015194949A (ja) * | 2014-03-31 | 2015-11-05 | 株式会社Nttドコモ | 管理システム及び管理方法 |
Non-Patent Citations (4)
Title |
---|
ETSI: "Network Functions Virtualisation (NFV); Management and Orchestration", ETSI GS NFV-MAN 001 V1.1.1, December 2014 (2014-12-01), XP055278655, Retrieved from the Internet <URL:http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_nfv-man001v010101p.pdf> [retrieved on 20170710] * |
RIGGIO, ROBERTO ET AL.: "Virtual network functions orchestration in enterprise WLANs", 2015 IFIP/IEEE INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGEMENT (IM), 11 May 2015 (2015-05-11), pages 1220 - 1225, XP033167959 * |
See also references of EP3451594A4 * |
SHEN, WENYU ET AL.: "vConductor: An enabler for achieving virtual network integration as a service", IEEE COMMUNICATIONS MAGAZINE 53.2, 2015, pages 116 - 124, XP055315308 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019132314A1 (ko) * | 2017-12-26 | 2019-07-04 | 삼성전자 주식회사 | 무선 통신 시스템에서 네트워크 기능 가상화를 위한 장치 및 방법 |
US11656897B2 (en) | 2017-12-26 | 2023-05-23 | Samsung Electronics Co., Ltd. | Apparatus and method for network function virtualization in wireless communication system |
CN110943967A (zh) * | 2018-09-21 | 2020-03-31 | 中兴通讯股份有限公司 | 一种认证方法、装置和*** |
Also Published As
Publication number | Publication date |
---|---|
JPWO2017188387A1 (ja) | 2019-01-10 |
US10719348B2 (en) | 2020-07-21 |
EP3451594A1 (en) | 2019-03-06 |
CN108886492A (zh) | 2018-11-23 |
US20190065234A1 (en) | 2019-02-28 |
JP6614340B2 (ja) | 2019-12-04 |
EP3451594A4 (en) | 2019-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6614340B2 (ja) | ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム | |
JP6954267B2 (ja) | ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム | |
KR101934286B1 (ko) | 네트워크 기능 가상화 관리 및 오케스트레이션 방법과 장치와 프로그램 | |
JP6658882B2 (ja) | 制御装置、vnf配置先選択方法及びプログラム | |
JP6686910B2 (ja) | ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム | |
JP6819296B2 (ja) | 仮想化管理・オーケストレーション装置、仮想化管理・オーケストレーション方法、および、プログラム | |
EP3313023B1 (en) | Life cycle management method and apparatus | |
US11093296B2 (en) | System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program | |
CN107959582B (zh) | 一种切片实例的管理方法及装置 | |
KR102524540B1 (ko) | 멀티 클라우드 서비스 플랫폼 장치 및 방법 | |
JP2010218049A (ja) | 情報処理装置、情報処理方法及びプログラム | |
CN111221618A (zh) | 一种容器化虚拟网络功能的部署方法和装置 | |
JPWO2018003020A1 (ja) | 制御装置、コンテナの起動方法及びプログラム | |
CN109213567B (zh) | 一种管理vnf实例化的方法和设备 | |
US20190377596A1 (en) | Flexible batch job scheduling in virtualization environments | |
JP2017068480A (ja) | ジョブ管理方法、ジョブ管理装置及びプログラム | |
WO2016121879A1 (ja) | 仮想化制御装置、配置先選択方法及びプログラム | |
CN109905258B (zh) | PaaS的管理方法、装置及存储介质 | |
JP7115561B2 (ja) | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム | |
CN112889247A (zh) | Vnf服务实例化方法及装置 | |
US20230281054A1 (en) | Computer System Execution Environment Builder Tool |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2018514706 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017789669 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017789669 Country of ref document: EP Effective date: 20181128 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17789669 Country of ref document: EP Kind code of ref document: A1 |