CN107924383A - System and method for network function virtualization resource management - Google Patents
System and method for network function virtualization resource management Download PDFInfo
- Publication number
- CN107924383A CN107924383A CN201680047063.XA CN201680047063A CN107924383A CN 107924383 A CN107924383 A CN 107924383A CN 201680047063 A CN201680047063 A CN 201680047063A CN 107924383 A CN107924383 A CN 107924383A
- Authority
- CN
- China
- Prior art keywords
- vnf
- nfvo
- abbreviation
- reuse
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5058—Service discovery by the service manager
-
- 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
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
System and method the invention discloses (network functions virtualization, abbreviation NFV) resource management is virtualized for network function, including:Network function virtualization composer (network functions virtualization orchestrator, abbreviation NFVO) receives the reuse requirement of first network service (network service, abbreviation NS);When the first NS will be terminated, the NFVO may be retained so that according to described at least one composition virtual network function (virtual network function, abbreviation VNF) example reused in definite first NS of requirement and be reused in the 2nd NS.In certain embodiments, these system and method further include:The NFVO retains at least one composition VNF examples in the first NS to be reused in the 2nd NS.
Description
This application claims what is submitted within 25th in August in 2015 entitled " to be used to virtual network function example utilize
The earlier application priority of 62/209th, No. 642 U.S. provisional patent application cases of system and method ", and also require in
The 62/th of entitled " the interacting on NFV quota resource managements between VNFM and VIM " submitted on October 9th, 2015
The earlier application priority of 239, No. 655 U.S. provisional patent application cases, the side of the full contents of this two application cases to introduce
Formula is incorporated herein.
Technical field
The present invention relates to network function to virtualize (network functions virtualization, abbreviation NFV), and
And it is related to the system and method for NFV resource managements in a particular embodiment.
Background technology
NFV is the great Rong that multiple network device type is incorporated to industrywide standard by evolution standard IT virtualization technologies
Measure in server, interchanger and memory, so as to change an industry effort of the mode of Virtual network operator structure network, it is intended to
Cost is reduced, and realizes efficient network operation and performance.In non-virtualized network, network function (network
Function, abbreviation NF) realized as the combination of the specific software and hardware of supplier.In contrast, in NFV environment
In, by NF with being abstracted by virtual hardware the hardware separation of operation so that the NF of whole classifications is virtually turned to can connect or
Link together to create the structure block of communication service.
The content of the invention
In a first aspect, disclosing a kind of network function that is used for virtualizes (network functions
Virtualization, abbreviation NFV) resource management method, including:Network function virtualization composer (network
Functions virtualization orchestrator, abbreviation NFVO) receive first network service (network
Service, abbreviation NS) reuse requirement;When the first NS will be terminated, the NFVO requires to determine according to described reuse
At least one composition virtual network function (virtual network function, abbreviation VNF) example in first NS
It may be retained so that and reused in the 2nd NS.In certain embodiments, this method further includes:The NFVO retains the first NS
In at least one composition VNF examples to be reused in the 2nd NS.
In second aspect, a kind of network function virtualization composer (network functions are disclosed
Virtualization orchestrator, abbreviation NFVO), including:Memory storage, including instruction;One or more processing
Device, communicates with the memory.One or more of processors perform described instruction, with:Receive first network service
The reuse requirement of (network service, abbreviation NS);When the first NS will be terminated, required really according to described reuse
At least one composition virtual network function (virtual network function, abbreviation VNF) in fixed first NS is real
Example can be reserved for reusing in the 2nd NS;Retain at least one composition VNF examples in the first NS so as to
Reused in two NS.
By retaining VNF examples to reuse in the future, rather than release VNF examples, it can save and create VNF for other NS
Some costs of example and time.In addition, Operation Support System (operations support system, abbreviation OSS) is responsible for
Related management is serviced, and NFVO is responsible for resource related management and VNF life cycle managements.Because it is NFVO rather than OSS roots
Determine whether to retain VNF examples according to the reuse requirement received, thus can also reduce overall response time and OSS and NFVO it
Between on VNF reuse management operation high flow capacity exchange.This improves VNF management operating efficiencies, and more neatly disposes
VNF management operation.
In some implementations, the reuse requirement can indicate that the composition VNF examples in the first NS can be retained institute
The requirement of foundation.
In some implementations, the reuse requirement can be included with least a kind of in the following group:VNF relation rules,
Capacity or load requirement, position constraint, NS type constraints, VNF type constraints, the requirement of reusable period.
In some implementations, the reuse requirement can pass through network service descriptor (network service
Descriptor, abbreviation NSD) receive.
In some implementations, at least one composition VNF examples can be retained and be stored in reusable VNF ponds
In.
In the third aspect, disclose a kind of network function that is used for and virtualize (network functions
Virtualization, abbreviation NFV) resource management method, including:Network function virtualization composer (network
Functions virtualization orchestrator, abbreviation NFVO) reception network service (network service,
Abbreviation NS) reuse requirement;The NFVO is according to the virtual network function for reusing and requiring to determine at least one reservation
Whether (virtual network function, abbreviation VNF) example can be used for the 2nd NS.In certain embodiments, this method
Further include:The VNF examples of at least one reservation are reused in the NS by the NFVO.
In fourth aspect, a kind of network function virtualization composer (network functions are disclosed
Virtualization orchestrator, abbreviation NFVO), including:Memory storage, including instruction;One or more processing
Device, communicates with the memory.One or more of processors perform described instruction, with:Receive network service
The reuse requirement of (network service, abbreviation NS);According to the virtual network for reusing and requiring to determine at least one reservation
Whether function (virtual network function, abbreviation VNF) example can be reused in the NS;By at least one reservation
VNF examples be reused in the NS.
By the way that the VNF examples of reservation are reused in NS, rather than create new VNF examples, can save some costs and
Time.In addition, OSS is responsible for servicing related management, and NFVO is responsible for resource related management and VNF life cycle managements.Because
It is that NFVO rather than OSS determine whether to reuse VNF examples according to the reuse requirement received, so when can also reduce overall response
Between and OSS and NFVO between on VNF reuse management operation high flow capacity exchange.This improves VNF management operating efficiencies, and
And more neatly deploy VNF management operations.
In some implementations, the VNF examples that reusing requirement can indicate to retain can be used for the requirement for reusing institute's foundation.
In some implementations, the reuse requirement can be included with least a kind of in the following group:VNF relation rules,
Capacity or load requirement, position constraint, NS type constraints, VNF type constraints, NS number constraints, the requirement of reusable period.
In some implementations, the reuse requirement can pass through network service descriptor (network service
Descriptor, abbreviation NSD) receive.
In some implementations, it can be selected from reusable VNF ponds and reuse the VNF examples of at least one reservation.
At the 5th aspect, disclose a kind of network function that is used for and virtualize (network functions
Virtualization, abbreviation NFV) resource management method, including:Virtual network function manager (virtual network
Function manager, abbreviation VNFM) by the interface between VNFM and VIM from virtualized infrastructure manager
(virtualized infrastructure manager, abbreviation VIM) receives quota information, and the quota information instruction allows
Distribute to the maximum quantity of the resource of one or more VNF examples of VNFM or VNFM management;The VNFM is based on described match somebody with somebody
Volume information carries out resource management action.
At the 6th aspect, a kind of virtual network function manager (virtual network function are disclosed
Manager, abbreviation VNFM), including:Memory storage, including instruction;One or more processors, are led to the memory
Letter.One or more of processors perform described instruction, with:Set by the interface between VNFM and VIM from virtualization basis
Apply manager (virtualized infrastructure manager, abbreviation VIM) and receive quota information, the quota information
Indicate the maximum quantity for allowing to distribute to the resource of one or more VNF examples of VNFM or VNFM management;Matched somebody with somebody based on described
Volume information carries out resource management action.
By VNFM-VIM interfaces without receiving quota information by NFVO, it is possible to reduce VNFM carry out based on quota
Resource management overall response time.Decrease the signaling consumption on quota related management between NFVO and VNFM.Therefore,
Improve the efficiency of the resource management based on quota.
In some implementations, the quota information, which also can indicate that, allows to distribute to the one of VNFM or VNFM management
The change of the maximum quantity of the resource of a or multiple VNF examples.Alternatively, the VNFM can subscribe the maximum resource quantity
Change.
In some implementations, VNFM can ask resource from VIM, or be managed based on quota information to configure VNFM
VNF.
Brief description of the drawings
For a more complete understanding of the present invention and its advantage, referring now to the description carried out below in conjunction with attached drawing, wherein:
Fig. 1 shows the schematic diagram of one embodiment of NFV systems;
Fig. 2 shows the flow chart of one embodiment of the method for NFV resource managements;
Fig. 3 shows the flow chart of another embodiment of the method for NFV resource managements;
Fig. 4 shows the flow chart of another embodiment of the method for NFV resource managements;
Fig. 5 shows the flow chart of another embodiment of the method for NFV resource managements;
Fig. 6 shows the flow chart of another embodiment of the method for NFV resource managements;
Fig. 7 shows the flow chart of another embodiment of the method for NFV resource managements;
Fig. 8 shows the block diagram of the embodiment processing system for performing method described herein.
Embodiment
First it is to be understood that although the illustrative implementation of one or more embodiments is provided below, but disclosed it is
Any number of technology can be used to implement for system, device and/or method, and no matter the technology is currently known or existing.This
Invention should in no way be limited to illustrative implementation, attached drawing and technology described below, including illustrated and described here show
The design of example property and implementation, but can be changed in the scope of the appended claims and the full breadth of its equivalent.
But for the ease of the open present invention, some aspects of the prior art are discussed, applicant never denies these aspects
Technology, and one or more aspects of the prior art the invention is intended to include being discussed herein.
Fig. 1 is showing for one embodiment of the NFV systems 100 in the various embodiments for disclosed system and method
It is intended to.Network function virtualization (Network Functions Virtualization, abbreviation NFV) management collaboration (NFV
Management and Orchestration, abbreviation NFV-MANO), ETSI NFV-MAN 001v1.1.1 (in December, 2014)
In describe some such systems, during the full content of the document is incorporated herein in a manner of being introduced into.NFV systems 100 can be with
Collaboration (NFV Management and Orchestration, abbreviation NFV-MANO) entity 128, NFV bases are managed including NFV
Facility (NFV Infrastructure, abbreviation NFVI) entity 126, virtual functions entity 140 and one or more sets operation branch
Support system (Operations Support Systems, abbreviation OSS) and business support system (Business Support
System, abbreviation BSS) (OSS/BSS) 124.Virtual functions entity 140 can include multiple virtual network function (virtual
Network function, abbreviation VNF) network element 160,162 and 164, and available for the multiple VNF network elements 160,162
With the 164 multiple Element management systems (element management system, abbreviation EMS) for performing typical management function
Network element 170,172 and 174.Although figure 1 illustrates a VNF network elements in three (3) and three EMS network elements, can clearly set
Think, any amount of such network element can be found in systems, and select three network elements to be purely in order at and facilitate purpose.This
Outside, it is to be understood that present invention contemplates alternative configurations, for example, multiple VNF network elements 160,162 and 164 are controlled by single EMS
System.
VNF network elements are used to virtualize the network function in non-virtualized network.For example, in non-virtualized network
Network function can be 3GPP Evolved Packet Core (Evolved Packet Core, abbreviation EPC) network element, for example, mobile
Property management entity (Mobility Management Entity, abbreviation MME), gateway (Serving Gateway, referred to as
SGW), grouped data network gateway (Packet Data Network Gateway, abbreviation PGW);Network element in home network,
For example, home gateway (Residential Gateway, abbreviation RGW);And traditional network function, for example, dynamic host configuration
Agreement (Dynamic Host Configuration Protocol, abbreviation DHCP) server, fire wall etc..For example, VNF
160 can be known as virtualization network function component (virtualized network function by one or more
Component, abbreviation VNFC) intraware composition.Each VNFC both provides the subset of the definition of the VNF functions, it is led
It is characterized in that the single instance of the component and single virtual container are in 1:1 mapping relations.For example, a VNF can be disposed
On multiple virtual machines (Virtual Machine, abbreviation VM), wherein each VM carries the VNFC of the VNF.But some
In the case of, whole VNF can also be deployed in single VM.VM can be the computing environment of virtualization, its behavior is similar to physics
Computer or server, its all the components (processor, memory/storage, interface/end with physical computer/server
Mouthful), and generated by virtual machine monitor.The virtual machine monitor carries out bottom physical resource subregion and assigns them to
VM.Virtual machine monitor can be that subregion is carried out to bottom physical resource, creates virtual machine, and it is soft that virtual machine is isolated from each other
Part.
NFV-MANO entities 128 can be responsible for the behaviour of VNF network elements 160,162 and 164 and corresponding NFVI entities 126
Make, manage and coordinate.NVV-MANO entities 128 can include NFV composers (NFV Orchestrator, abbreviation NFVO) entity
102nd, one or more VNF managers (VNF manager, abbreviation VNFM) entity 104 and one or more virtualization bases
Infrastructure manager (Virtualized Infrastructure Manager, abbreviation VIM) entity 106.NFVO entities 102 can be with
Manage network service (network service, abbreviation NS) life cycle and NS life cycles of coordinating, (by VNFM entities 104
Hold) management of VNF life cycles and (being supported by VIM entities 106) NFVI resources, to ensure the most optimal sorting of necessary resource
Match somebody with somebody and connectivity.VNFM entities 104 can communicate with VNF network elements 160,162 and 164, and be responsible for VNF life cycle pipes
Reason (for example, instantiate, update, inquire about, extend and terminate).For example, can be each VNF network elements in one embodiment
160th, 162 and 164 deployment VNFM entities 104.In other embodiments, VNFM entities 104 can serve multiple VNF network elements
160th, 162 and 164.VIM entities 106 can be responsible for controlling and managing NFVI calculating, storage and Internet resources.In other words, VIM
Entity 106 can be used for controlling and managing interacting between VNF and the calculating in NFVI entities 126, storage and Internet resources.Example
Such as, VIM entities 106 can perform resource management function, for example, management infrastructure resource and distribution (provide for example, increasing to VM
Source, improve energy efficiency and resource reclaim).For resource allocation request, VIM entities 106 and VNFM entities 104 can each other into
Row communication, so as to exchange virtualization hardware resource distribution and status information.
NFVI entities 126 represent that structure is used for the various hardware and software components for disposing, managing and performing the environment of VNF.
For example, the nextport hardware component NextPort in NFVI entities 126 can include providing to VNF entities 160,162 and 164 by virtualization layer 130
Computing hardware 112, storage hardware 114 and the network hardware 116 of processing, storage and connection.Computing hardware 112 can be that configuration is used
In, be designed for or be capable of providing processing in other ways and any equipment of computing resource.Storage hardware 114 can be used for
Information is stored so as to any kind of equipment extracted later.The example of storage device includes:Flash memory, magnetic rotation turntable, CD or
Information can be stored so as to any other mechanism extracted later.Storage hardware 114 can be in shared network attached storage
(network attached storage, abbreviation NAS) and NFVI is directly connected to by internal bus or other additional mechanisms
Local storage between distinguish.In one embodiment, the resource from computing hardware 112 and storage hardware 114 can
It is pooled to together.The network hardware 116 can be performed for the interchanger of function of exchange, for example, router, wired or wireless
Link.The network hardware 116 can cross over multiple network domains.
Virtualization layer 130 in NFVI entities 126 can abstract hardware resource, i.e. computing hardware 112, storage hardware
114 and the network hardware 116, and one or more of VNF network elements 160,162 and 164 are separated with bottom hardware.Example
Such as, virtualization layer 130 can be responsible for abstracting hardware resource and logical partition, enable to realize that the software of VNF uses
Underlying virtual infrastructure, and provide virtualization resource to VNF entities.The virtualization resource that virtualization layer 130 controls can be with
Including virtual computing 110, virtual memory 118 and virtual network 120.
Virtual resource consumes physical resource.The reuse of virtual resource is conducive to optimize use and the availability of physical resource.
For purposes of the present invention, reuse and require to be intended to refer to can be used for any mark for determining whether VNF examples will be retained or be reused
It is accurate.
It is to determine whether to retain, reuse, discharge or in other ways take existing VNF examples for NFVO to reuse requirement
The standard of action.For example, reusing the composition VNF examples for requiring to specify specific NS may be retained so that the requirement for reusing institute's foundation.
In another example, reuse and require to specify the VNF examples retained to can be used for the requirement for reusing institute's foundation in NS.In some realities
Apply in example, reuse during requirement can be considered by OSS based on safety, redundancy or resource at least one is set.Can clearly it set
Think, in certain embodiments, can will reuse require as reuse strategy, reuse constraint, reuse rule, reuse standard or
Any other desired form is realized.Reuse and require to allow NFVO to determine whether the composition for retaining NS1 when NS1 will be terminated
VNF examples in other NS to reuse.Alternatively, reusing requirement can allow NFVO to determine whether to reuse reservation for NS2
VNF examples.
Fig. 2 shows the flow chart of one embodiment of the method 200 for NFV resource managements.It can be expressly understood that
It is that embodiment method 200 can perform in the context of NFV systems as shown in Figure 1.
In step 202, NFVO receives the reuse requirement of the first NS.For example, can be for example, by Application Programming Interface
The interaction mechanism such as (application programming interface, abbreviation API), interaction message, which to reuse from establishment, to be wanted
The OSS or other management entities asked are received to reuse and required.
In step 204, NFVO determines that at least one composition VNF examples in the first NS whether can according to requirement is reused
It is reserved for reusing in the 2nd NS.For example, when first NS will be terminated, this can be triggered and determined.
In step 206, if it is determined that at least one composition VNF examples in the first NS can be retained, then NFVO is protected
At least one composition VNF examples in the first NS are stayed, so that future reuses in the 2nd NS.
In a step 208, if it is determined that can be retained without composition VNF examples in the first NS, then NFVO releases first
Composition VNF examples in NS.
By retaining VNF examples to reuse in the future, rather than these VNF examples are discharged, can save and be created for other NS
Build some costs and the time of these VNF examples.In addition, OSS is responsible for servicing related management, and NFVO is responsible for resource related management
And VNF life cycle managements.Because it is that NFVO rather than OSS determine whether to retain VNF realities according to the reuse requirement received
Example, exchanges so can also reduce and reuse the high flow capacity for managing and operating on VNF between overall response time and OSS and NFVO.
This improves VNF management operating efficiencies, and more neatly deploys VNF management operations.
Fig. 3 shows the flow chart of another embodiment of the method 300 for NFV resource managements.It can be expressly understood that
, embodiment method 300 can perform in the context of NFV systems as shown in Figure 1.
In step 302, NFVO receives the reuse requirement of NS.For example, can be for example, by Application Programming Interface
The interaction mechanism such as (application programming interface, abbreviation API), interaction message, which to reuse from establishment, to be wanted
The OSS or other management entities asked are received to reuse and required.
In step 304, whether the VNF examples that NFVO requires to determine at least one reservation according to reusing can be reused in
NS.For example, when NS will be instantiated or be expanded, this can be triggered and determined.
Within step 306, if it is determined that the VNF examples of at least one reservation can be reused, then NFVO will be at least one
The VNF examples of reservation are reused in NS.
In step 308, if it is determined that do not have VNF examples with a grain of salt to be reused, then NFVO creates the group needed for NS
Into VNF examples.For example, NFVO can instantiate the composition VNF examples needed for NS.
It can be expressly understood that, the selected feature of the example embodiment of Fig. 3 can be selected with the example embodiment of Fig. 2
Feature is combined.
By the way that the VNF examples of reservation are reused in NS, rather than create new VNF examples, can save some costs and
Time.In addition, OSS is responsible for servicing related management, and NFVO is responsible for resource related management and VNF life cycle managements.Because
It is that NFVO rather than OSS determine whether to reuse VNF examples according to the reuse requirement received, so when can also reduce overall response
Between and OSS and NFVO between on VNF reuse management operation high flow capacity exchange.This improves VNF management operating efficiencies, and
And more neatly deploy VNF management operations.
Fig. 4 shows the flow chart of another embodiment of the method 400 for NFV resource managements.It can be expressly understood that
, embodiment method 400 can perform in the context of NFV systems as shown in Figure 1.
Fig. 4 includes the use of network service descriptor (network service descriptor, abbreviation NSD).NSD is
One deployment template, by NFVO carry out NS life cycle managements used by information structure.For example, NSD can be opened up including service
Flutter (for example, composition VNF and relation between them, virtual link, VNF forwardings figure), network service characteristics and for NS
Any other artifact needed for line and life cycle management.In some implementations, NSD can be grasped by airborne NSD
Make to be supplied to NFVO from OSS.For example, NSD can be sent to by NSD management interfaces in OnboardNsdRequest message
NFVO。
In step 402, OSS 124 is to include reusing desired NS1 establishment NSD, and the NSD of NS1 is sent to NFVO
102.In addition, OSS 124 will be transferred to NFVO 102 for the instantiation of NS1 request, to ask instantiation NS1.For example,
OSS124 can will be sent to NFVO for example, by the NS such as lifecycle management interface interfaces for the instantiation of NS1 request
124.Lifecycle management interface is the connection that can be transmitted request of data between OSS 124 and NFVO 102, including but unlimited
Connected in network data.Lifecycle management interface can be used for notifying when providing operation relevant with the states of VNF examples, as
Made to VNF examples change is as a result, described change the change for including but is not limited to VDU quantity, due to automatic extension/more
VNF configurations and/or the change of topology caused by newly/upgrading/termination, the switching of holding state and other functions.These are logical
Know contribute to renewal on the operation that can be triggered earlier completion (such as keep NFV examples catalogue update and/or
NE management (element management, abbreviation EM) update) functional block consumption.It is understood that work as VNF life
When cycle management interface is generated by VNFM entities 104, VNFM can also generate VNF life cycles and change notification interface.When VNF gives birth to
When life cycle management interface is generated by NFVO 102, NFVO 102 can also generate VNF life cycles and change notification interface.
In the present embodiment, NSD includes the reuse requirement of the composition VNF in NS1.In some implementations, reusing will
Cell that can by designator or included in the NSD of NS1 is asked to indicate.Although being not shown in Fig. 4, can clearly manage
Solution, in certain embodiments, can also be by other suitable except NSD the or OnboardNsdRequest message of NS1
The message slave OSS 124 to NFVO 102 to NFVO 102 provide reuse require.
In step 404, when NFVO 102 receives the instantiation request for NS1, it is assumed that there is currently no reservation
VNF examples.According to the NSD of NS1, NS1 needs two composition VNF examples:PGW VNF examples 420 and MME VNF examples 422.
In response to the instantiation request for NS1, NFVO 102 is by instantiating PGW VNF examples 420 and MME VNF needed for NS1
422 instantiate NS1.It will also be appreciated that the VNF examples of any quantity or type can be realized to realize NS1, such as Fig. 4
Shown implementation, which is purely in order at, facilitates purpose.
In a step 406, OSS 124 determines to terminate NS1, and sends the termination request for NS1 to NFVO 102, with
Request terminates NS1.For example, NFVO 102 can be sent to by NS lifecycle management interfaces by terminating request.
In a step 408, asked in response to terminating, NFVO 102 determines composition VNF examples (that is, the PGW VNF in NS1
Example 420 and MME VNF examples 422) whether meet to reuse requirement and therefore can be retained.If it is determined that the composition in NS1
VNF examples, which meet to reuse, to be required and therefore can be retained, then performs step 410.
In certain embodiments, the reuse requirement of polytype described below or form can be used alone or group each other
Close and use.In one embodiment of these embodiments, it can be the one or more composition VNF that can be retained to reuse requirement
The capacity or load requirement of example.For example, load requirement specify the composition VNF examples that can be retained load need be equal to or
Less than threshold value.In another example, capacity requirement specify the composition VNF examples that can be retained residual capacity need be equal to or
More than threshold value, such as 50%.It is expressly contemplated that any suitable threshold value can be set, and 50% is selected purely to go out
In illustration purpose.If NFVO has found that the residual capacity of PGW VNF examples and MME VNF examples in NS1 is equal to or greatly
In 50%, then NFVO determines PGW VNF examples in NS1 and MME VNF examples meet to reuse and require and therefore can be retained.
In another embodiment of these embodiments, it can be the one or more compositions that can be retained to reuse requirement
The position constraint of VNF examples.For example, position constraint can specify the PGW VNF examples in geographical location 1 to be retained,
And the MME VNF examples in reason position 2 can be retained.If NFVO has found the PGW VNF examples and MME in NS1
The geographical location of VNF examples all meets position constraint, then NFVO determines that PGW VNF examples in NS1 and MME VNF examples can
It is retained.It will also be appreciated that position constraint can be configured to specify the composition VNF examples in some position cannot be by
Retain.
In another embodiment of these embodiments, it can be VNF relation rules to reuse requirement.For example, VNF relations are advised
The composition VNF examples with certain relation can be then specified to be retained together.If NFVO has found the PGW VNF in NS1
Relation between example and MME VNF examples is matched with VNF relation rules, then NFVO determine PGW VNF examples in NS1 and
MME VNF examples can be retained together.In another example, VNF relation rules can specify the group with certain relation
It cannot be retained together into VNF examples.It can be expressly understood that, VNF relation rules can be based on supplier, safety or function
Consider to set.
In another embodiment of these embodiments, it can be NS type constraints to reuse requirement.For example, NS type constraints
The composition VNF examples in the NS of given type can be specified to be retained.If NFVO has found that NS1 meets NS type constraints,
Then NFVO determines that PGW VNF examples in NS1 and MME VNF examples can be retained.It will also be appreciated that NS type constraints
The composition VNF examples that can be configured in the NS of given type cannot be retained.
In another embodiment of these embodiments, it can be VNF type constraints to reuse requirement.For example, VNF types are about
Beam can specify the composition VNF examples of one or more given types to be retained.If NFVO has found the PGW in NS1
VNF examples and MME VNF examples are matched with VNF type constraints, then NFVO determines the PGW VNF examples and MME VNF realities in NS1
Example can be retained.It will also be appreciated that VNF type constraints can be configured to specify the group of one or more given types
It cannot be retained into VNF examples.
In another embodiment of these embodiments, reuse requirement, which can be related to, to be allowed using one or more compositions
The reusable period of VNF examples.When expiring the reusable period, it is necessary to discharge one or more composition VNF examples.Example
Such as, the reusable period of the PGW VNF examples in NS1 and MME VNF examples could be provided as 30 days.If NFVO has found
PGW VNF examples and MME VNF examples in NS1 only used 2 days, then NFVO determines PGW VNF examples and the MME in NS1
VNF examples can be retained.
In step 410, if NFVO determines the PGW VNF examples 420 in NS1 and the satisfaction reuse of MME VNF examples 422
It is required that and therefore it can be retained, then NFVO deletions NS1, and retain PGW VNF examples 420 and MME VNF examples 422 to incite somebody to action
To be reused in other NS, rather than release PGW VNF examples 420 and MME VNF examples 422.In certain embodiments, NFVO
The VNF examples of reservation are put into reusable VNF ponds, and remove the PGW VNF examples 420 in NS1 and MME VNF examples 422
All configurations.For example, reusable VNF ponds can be realized as database, to track the VNF example states of those reservations.
It is expressly contemplated that be, it is possible to achieve any other suitable mechanism come preserve those reservation VNF examples and track them,
And pond mechanism is selected purely to be in order at illustration purpose.For example, NFVO can alternatively safeguard the list of the VNF examples of reservation.
Although being not shown in Fig. 4, it can be expressly understood that, in certain embodiments, if NFVO determines NS1
In PGW VNF examples and MME VNF examples be unsatisfactory for reusing and require, then it is real to discharge PGW VNF examples and MME VNF by NFVO
Example, and delete NS1.
Moreover, it is to be understood that NS as described above terminates the example that operation is for illustrative purposes only.It is other
The NS life cycle managements operation of type can also be applied in the embodiment method.
Reused in the future by retaining the VNF examples of the NS terminated, rather than discharge these VNF examples, can saved
Some costs and the time of these VNF examples are created for other NS.In addition, OSS is responsible for servicing related management, and NFVO is responsible for money
Source related management and VNF life cycle managements.Because it is NFVO rather than OSS true according to the reuse requirement/strategy received
It is fixed whether to retain VNF examples, so can also reduce management behaviour is reused on VNF between overall response time and OSS and NFVO
The high flow capacity of work exchanges.This improves VNF management operating efficiencies, and more neatly deploys VNF management operations.
In one embodiment of the invention, a kind of NFVO is disclosed, including:A kind of device, for receiving the first NS's
Reuse and require;And a kind of device, for when first NS will be terminated, requiring to determine in the first NS at least according to reusing
Whether one composition VNF example can be reserved for reusing in the 2nd NS.The embodiment of NFVO further includes a kind of device, uses
In retaining at least one composition VNF examples in the first NS to be reused in the 2nd NS.It can be expressly understood that, the NFVO
Embodiment can keep operation consistent with embodiment of the method as shown in Figure 2 and Figure 4.Specific implementation on the NFVO embodiments
Mode, may be referred to above method embodiment.
Fig. 5 shows the flow chart of another embodiment of the method 500 for NFV resource managements.It can be expressly understood that
, embodiment method 500 can perform in the context of NFV systems as shown in Figure 1.
In step 502, OSS 124 is to include reusing desired NS2 establishment NSD, and the NSD of NS2 is sent to NFVO
102.In some implementations, NSD can be operated from OSS 124 by airborne NSD and is supplied to NFVO.For example, NSD can lead to
Cross NSD management interfaces and NFVO 102 is sent in OnboardNsdRequest message.In addition, OSS is by for the example of NS2
Change request and be sent to NFVO 102, to ask instantiation NS2.For example, OSS 124 be able to will be directed to by NS life cycles interface
The instantiation request of NS2 is sent to NFVO 102.
In the present embodiment, the NSD of NS2 includes the reuse requirement of the composition VNF in NS2.In some implementations, weight
Indicated with cell that can by designator or included in the NSD of NS2 is required., can be bright although being not shown in Figure 5
Really understand, in certain embodiments, can also be by other except NSD the or OnboardNsdRequest message of NS2
Suitably from OSS 124 to NFVO, 102 message is provided to reuse to NFVO and required.
Reuse and require to determine how for NFVO 102 that the VNF examples of reservation are reused in NS2.Rule are required for example, reusing
The VNF examples for having determined to retain can be reused in the requirement of NS2 institutes foundation.In certain embodiments, reusing requirement can be by OSS base
At least one in the consideration of safety, redundancy or resource is set., can be with it is expressly contemplated that in certain embodiments
Reuse is required to realize as reuse strategy, reuse constraint, reuse rule, reuse standard or any other desired form.Also
It is understood that as the reuse described in the embodiment of Fig. 5 require can be used alone or with described in the embodiment such as Fig. 4
Reuse requirement be applied in combination.
In step 504, in response to the instantiation request for NS2, NFVO 102 checks reusable VNF ponds, and determines
Whether the VNF examples of at least one reservation in reusable VNF ponds meet the reuse requirement of NS2.For example, reusable VNF Chi Bao
Include the VNF examples of three reservations:PGW VNF examples 1 520, PGW VNF examples 2 524 and MME VNF examples 522.According to NS2
NSD, NS2 need two composition VNF examples:PGW VNF examples and MME VNF examples 522.Therefore, NFVO is it needs to be determined that three
Whether the VNF examples of a reservation, which meet to reuse, requires.If it is determined that the PGW VNF examples 1 520 and MME VNF examples that retain
522 meet to reuse requirement and therefore can be reused in NS2, then perform step 506.It will also be appreciated that on NS2 and it can weigh
The VNF examples of any quantity or type can be realized with VNF ponds, and implementation as shown in Figure 5 is purely in order at explanation mesh
's.
In certain embodiments, the reuse requirement of polytype described below or form can be used alone or group each other
Close and use.
In one embodiment of these embodiments, it can be the one or more reservations that can be reused to reuse requirement
The capacity or load requirement of VNF examples.For example, load requirement specifies the load needs of the VNF examples that can be reused of reservation
Equal to or less than threshold value.In another example, capacity requirement specifies the residual capacity of the VNF examples that can be reused of reservation
Need to be equal to or more than threshold value, such as 70%.It is expressly contemplated that any suitable threshold value can be set, and select
70% is purely in order at illustration purpose.If NFVO has found the PGW VNF examples 1 520 and MME of the reservation in reusable VNF ponds
The residual capacity of VNF examples 522 is equal to or more than 70%, then NFVO determines the PGW VNF examples 1 520 and MME retained
VNF examples 522, which meet to reuse, requires and can be reused in NS2.
In another embodiment of these embodiments, it can be reused in the one or more of NS2 to reuse requirement
The position constraint of the VNF examples of reservation.For example, position constraint can specify the PGW VNF examples in geographical location 1 can be by
Reuse, and the MME VNF examples 522 in geographical location 2 can be reused.If NFVO is had found in reusable VNF ponds
The PGW VNF examples 1 520 of reservation and the geographical location of MME VNF examples 522 all meet position constraint, then NFVO determines PGW
VNF examples 1 520 and MME VNF examples 522 can be reused.It will also be appreciated that position constraint can be configured to refer to
Surely the VNF examples for the reservation for being in some position cannot be reused.
In another embodiment of these embodiments, it can be VNF relation rules to reuse requirement.For example, VNF relations are advised
The VNF examples of the reservation with certain relation, which can then be specified, can be reused in NS2 together.If NFVO 102 has found reusable
The PGW VNF examples 1 520 of reservation in VNF ponds are matched with the relation between MME VNF examples 522 with VNF relation rules, then
NFVO determines that the PGW VNF examples 1 520 retained and MME VNF examples 522 can be reused together.In another example,
VNF relation rules can specify the VNF examples of the reservation with certain relation to be reused in NS2 together.It can be expressly understood that
, VNF relation rules can consider set based on supplier, safety or function.
In another embodiment of these embodiments, it can be NS type constraints to reuse requirement.For example, NS type constraints
The VNF examples of reservation can be specified to be reused in the NS of given type.If NFVO 102 has found that NS2 meets NS types about
Beam, then NFVO 102 determine that the PGW VNF examples 1 520 of the reservation in reusable VNF ponds and MME VNF examples 522 can be by
Reuse.It will also be appreciated that the VNF examples that NS type constraints can be configured to retain cannot be reused in given type
NS。
In another embodiment of these embodiments, it can be VNF type constraints to reuse requirement.For example, VNF types are about
Beam can specify the VNF examples of the reservation of one or more given types to be reused in NS2.If NFVO has found reusable
The PGW VNF examples 1 520 and MME VNF examples 522 of reservation in VNF ponds are matched with VNF type constraints, then NFVO is determined
PGW VNF examples 1 520 and MME VNF examples 522 can be reused.It will also be appreciated that VNF type constraints can be set
NS2 cannot be reused in by being set to the VNF examples of the reservation of one or more given types.
In another embodiment of these embodiments, it can be NS number constraints to reuse requirement.For example, NS number constraints
It can indicate to allow while reuse the maximum quantity of the NS of the VNF examples of reservation.If NFVO has found matching NS number constraints,
NFVO determines that PGW VNF examples 1 and MME VNF examples can be reused.
In another embodiment of these embodiments, one or more allowed using in NS2 can be related to by reusing requirement
The reusable period of a composition VNF examples.When expiring the reusable period, it is necessary to discharge one or more composition VNF realities
Example.For example, the reusable period of one or more of NS2 composition VNF examples can be configured to 20 days.If NFVO is sent out
The PGW VNF examples 1 520 now retained and the remaining reusable period of MME VNF examples 522 are above 20 days, then NFVO is true
Determine PGW VNF examples 1 520 and MME VNF examples 522 meet to reuse requirement and therefore can be reused in NS2.In step 506
In, NFVO then by reuse meet NS2 reuse require reservation PGW VNF examples 1 520 and MME VNF examples 522 come
Instantiate NS2.Especially, PGW VNF examples 1 520 and MME VNF examples 522 are added in NS2 by NFVO, and match somebody with somebody for NS2
Put PGW VNF examples 1 520 and MME VNF examples 522.
Although being not shown in Figure 5, it can be expressly understood that, in certain embodiments, if determine can by NFVO
Reuse in VNF ponds and do not have the reuse requirement that VNF examples with a grain of salt meet NS2, then NFVO alternatively instantiate PGW VNF examples and
MME VNF examples 522 instantiate NS2.
In step 508, OSS sends the extended requests for being directed to NS2 to NFVO, to add new PGW VNF examples.Example
Such as, OSS can send extended requests by lifecycle management interface to NFVO 102.
In step 510, in response to the extended requests for NS2, NFVO checks reusable VNF ponds, and determines reusable
Whether the VNF examples of at least one reservation in VNF ponds meet the reuse requirement of NS2.For example, it is assumed that reusable VNF ponds are current
Including PGW VNF examples 2 524.Therefore, NFVO is it needs to be determined that whether the PGW VNF examples 2 524 retained meet to reuse requirement.
Require if it is determined that the PGW VNF examples 2 524 retained meet to reuse and therefore can be reused in NS2, then perform step 512
In step 512, NFVO 102 then meets the PGW VNF examples 2 of the reservation of the reuse requirement of NS2 by reusing
524 extend NS2.Especially, PGW VNF examples 2 524 are added in NS2 by NFVO, and configure PGW VNF examples 2 for NS2
524。
Although being not shown in Figure 5, it can be expressly understood that, in certain embodiments, if determine can by NFVO
Reuse in VNF ponds and do not have the reuse requirement that VNF examples with a grain of salt meet NS2, then NFVO alternatively instantiates or create PGW VNF
Example extends NS2.
Moreover, it is to be understood that NS as described above is terminated and what extended operation was for illustrative purposes only shows
Example.Other types of NS life cycle managements operation can also be applied in the embodiment method.NS life cycle managements operate
It can include but is not limited to instantiate, terminate, extend and cure operation etc..
It will also be appreciated that the selected feature of the example embodiment of Fig. 5 can be with the selected spy of the example embodiment of Fig. 4
Sign is combined.
By the way that the VNF examples of reservation are reused in NS, rather than create new VNF examples, can save some costs and
Time.In addition, OSS is responsible for servicing related management, and NFVO is responsible for resource related management and VNF life cycle managements.Because
It is that NFVO rather than OSS determine whether to reuse VNF examples according to the reuse requirement/strategy received, so can also reduce total
The high flow capacity for reusing management operation between response time and OSS and NFVO on VNF exchanges.This improves VNF management operations
Efficiency, and more neatly deploy VNF management operations.
In one embodiment of the invention, a kind of NFVO is disclosed, including:A kind of device, for receiving the reuse of NS
It is required that;And a kind of device, for whether according to the VNF examples for reusing the definite at least one reservation of requirement NS can be reused in.
The embodiment of NFVO further includes a kind of device, for the VNF examples of at least one reservation to be reused in NS.It can be expressly understood that
It is that the NFVO embodiments can keep operation consistent with embodiment of the method as shown in Figure 3 and Figure 5.On the NFVO embodiments
Specific implementation, may be referred to above method embodiment.
Fig. 6 shows the flow chart of another embodiment of the method for NFV resource managements.It can be expressly understood that
It is that embodiment method 600 can perform in the context of NFV systems as shown in Figure 1.
In step 602, VNFM 104 sends the quota inquiry request for being used for inquiring about quota information to VIM 106.Quota
Inquiry request is sent by the interface between VNFM 104 and VIM, i.e. VNFM-VIM interfaces.
In step 604, in response to quota inquiry request, VIM 106 is returned to VNFM 104 includes matching somebody with somebody for quota information
Volume inquiry response.Quota inquiry response is sent directly to VNFM 104 by VNFM-VIM interfaces, without passing through NFVO.Example
Such as, quota information can include quota resource information, it, which is specified, allows to distribute to VNFM 104 or VNFM 104 is managed one
The maximum quantity of the resource of a or multiple VNF examples.In another example, quota information can include quota metadata information or
Quota status information.The resource of distribution includes but not limited to computing resource, Internet resources and storage resource.
In step 606, VNFM 104 is based on quota information and carries out resource management action.For example, resource management action can
To be operated including VNF life cycle managements.VNFM 104 can according to by the quota information that VNFM-VIM interfaces arrive from
VIM asks resource or configures its VNF.
By VNFM-VIM interfaces without receiving quota information by NFVO, it is possible to reduce VNFM carry out based on quota
Resource management overall response time.Decrease the signaling consumption on quota related management between NFVO and VNFM.Therefore,
Improve the efficiency of the resource management based on quota.
Fig. 7 shows the flow chart of another embodiment of the method for NFV resource managements.It can be expressly understood that
It is that embodiment method 700 can perform in the context of NFV systems as shown in Figure 1.
In a step 702, VNFM 104 sends the reservation request for being used for subscribing the change in quota to VIM 106.Subscribe
Request is sent by the interface between VNFM 104 and VIM, i.e. 106 interfaces of VNFM-VIM.
In step 704, returned in response to reservation request, VIM 106 by 106 interfaces of VNFM-VIM with reservation knot
The subscription response of fruit.Assuming that it successfully have subscribed to quota change.It can be expressly understood that, step 702-704 is optional.
In step 706, after successful reservation, VNFM 104 is registered relevant with quota change to be received from VIM
Notice.When quota information is updated, VIM 106 is sent by VNFM-VIM106 interfaces to VNFM 104 includes quota information
Quota change notification, without passing through NFVO.Quota information can include quota change information.For example, quota change information
It can indicate the change for allowing to distribute to the maximum quantity of the resource of one or more VNF examples of VNFM 104 or VNFM management
Change.Quota change information also can indicate that change type.It is expressly contemplated that the change of maximum quantity can be included from 0
To the change of certain number, vice versa.It will also be appreciated that the resource for distributing to VNFM 104 includes but not limited to calculate money
Source, Internet resources and storage resource.
In step 708, after quota change notification is received, VNFM 104 sends quota change response to VIM.
It is appreciated that the step for be optional.
In step 720, VNFM 104 is based on quota information and carries out resource management action.For example, resource management action can
To be operated including VNF life cycle managements.VNFM 104 can believe according to the quota arrived by 106 interfaces of VNFM-VIM
Breath asks resource from VIM 106 or configures its VNF.
By 106 interfaces of VNFM-VIM without receiving quota information by NFVO, it is possible to reduce what VNFM 104 was carried out
The overall response time of resource management based on quota.Decrease the letter on quota related management between NFVO and VNFM 104
Make expense.This improves the efficiency of the resource management based on quota.
In one embodiment of the invention, a kind of VNFM is disclosed, including:A kind of device, for passing through VNFM and VIM
Between interface receive quota information from VIM, quota information instruction allows to distribute to one or more of VNFM or VNFM management
The maximum quantity of the resource of a example.The VNFM embodiments further include a kind of device, for carrying out resource pipe based on quota information
Reason operation.It can be expressly understood that, which can be consistent with embodiment of the method as shown in Figure 6 and Figure 7
Operation.On the specific implementation of the VNFM embodiments, above method embodiment may be referred to.
It is related to subject of the present invention below with reference to document.The full content of the bibliography is incorporated to this in a manner of introducing
Text:Entitled " system and method for being used for the NFV quota resource managements that VNFM is assisted " submitted on May 7th, 2015
No. 62/158,381 U.S. provisional patent application cases.
Fig. 8 shows the block diagram of processing system 800.The processing system can be used for realizing method disclosed herein.It is specific
Equipment can utilize all shown components or the subset merely with the component, and the degree of integration between equipment may be different.
In addition, equipment can include multiple examples of component, such as multiple processing units, processor, memory, transmitter, receiver etc..
Processing system 800 can include equipped with one or more input-output apparatus, such as loudspeaker, microphone, mouse, touch
The processing unit of screen, button, keyboard, printer 807, display 808 etc..Processing unit can include:Central processing unit
(central processing unit, abbreviation CPU) 810, memory 815, mass storage facility 820, video adapter
825 and it is connected to the I/O interfaces 830 of bus 835.
Bus 835 can be one or more of any type of some bus architectures, including rambus or memory
Controller, peripheral bus, video bus etc..The CPU 810 may include any kind of data into electronic data processing.Memory 815
It may include any type of non-transient system storage, such as static RAM (static random
Access memory, abbreviation SRAM), dynamic random access memory (dynamic random access memory, referred to as
DRAM), synchronous dram (synchronous DRAM, abbreviation SDRAM), read-only storage (read-only memory, abbreviation
) or combinations thereof etc. ROM.In one embodiment, memory 815 may include the ROM used in start and perform journey
The DRAM for being used for program and data and storing used during sequence.
Mass storage facility 820 may include any type of non-transient storage device, for storing data, program
And other information, and the data, program and other information is accessed by bus 835.For example, mass storage facility
820 may include the one or more in solid magnetic disc, hard disk drive, disc driver, CD drive etc..
The video adapter 825 and the I/O interfaces 830 provide interface, and external input and output equipment are coupled
To the processing unit.As shown in the figure, the example of input-output equipment includes being coupled to the display 807 of video adapter 825
With any combination of mouse/keyboard/printer 805 for being coupled to I/O interfaces 830.Miscellaneous equipment may be coupled to processing unit,
And additional or less interface equipment can be utilized.For example, Universal Serial Bus (Universal Serial Bus, letter
USB) serial line interface such as (not shown) can be used for be referred to as printer offer interface.
Processing system 800 further includes one or more network interfaces 850, and network interface 850 may include Ethernet cable etc.
Wire link, and/or it is connected to the Radio Link of access node or different networks 855.Network interface 850 allows processing system
System 800 is communicated by network 855 with remote unit.For example, network interface 850 can by one or more transmitters/
Transmitting antenna and one or more receiver/reception antennas provide wireless communication.In one embodiment, processing system 800
Be coupled to LAN or wide area network 855, for data processing, and with for example other processing units, internet, long-range storage
The remote-control devices such as facility communicate.
Although showing combinations of features in the example shown in the series of figures, and it need not realize the present invention with reference to all features
Various embodiments benefit.In other words, the system or method designed according to an embodiment of the invention will not necessarily comprise
All features shown in any one or all parts for being shown schematically in the figures in attached drawing.An in addition, example
The selected feature of embodiment can be combined with the selected feature of other examples embodiment.
Although the invention has been described with reference to an illustrative embodiment, this description is not intended to limit the present invention.Affiliated neck
The technical staff in domain is with reference to after the description, it will be understood that the various modifications and combinations of illustrative embodiment, and the present invention its
Its embodiment.Therefore, the appended claims are intended to cover any such modification or embodiment.
Claims (20)
1. one kind is used for network function virtualization (network functions virtualization, abbreviation NFV) resource pipe
The method of reason, it is characterised in that including:
Network function virtualization composer (network functions virtualization orchestrator, referred to as
NFVO the reuse requirement of first network service (network service, abbreviation NS)) is received;
When the first NS will be terminated, the NFVO requires to determine at least one in the first NS according to the reuse
Composition virtual network function (virtual network function, abbreviation VNF) example may be retained so that in the 2nd NS
Reuse;
The NFVO retains at least one composition VNF examples in the first NS to be reused in the 2nd NS.
2. according to the method described in claim 1, it is characterized in that, described determine to include:Determine in the first NS at least
Whether one composition VNF example meets that described reuse requires.
3. according to the method described in claim 1, it is characterized in that, the reuse requirement of the first NS is by the first NS
Network service descriptor (network service descriptor, abbreviation NSD) come what is received.
4. according to the method in any one of claims 1 to 3, it is characterised in that described reuse requires instruction described first
Composition VNF examples in NS can be retained the requirement of institute's foundation, and including with least a kind of in the following group:
VNF relation rules;
Capacity or load requirement;
Position constraint;
NS type constraints;
VNF type constraints;
The reusable period requires.
5. one kind is used for network function virtualization (network functions virtualization, abbreviation NFV) resource pipe
The method of reason, it is characterised in that including:
Network function virtualization composer (network functions virtualization orchestrator, referred to as
NFVO the reuse requirement of network service (network service, abbreviation NS)) is received;
The NFVO is according to virtual network function (the virtual network for reusing and requiring to determine at least one reservation
Function, abbreviation VNF) whether example can be used for the NS;
The VNF examples of at least one reservation are reused in the NS by the NFVO.
6. according to the method described in claim 5, it is characterized in that, described determine to include:Determine at least one reservation
Whether VNF examples meet that described reuse requires.
7. according to the method described in claim 5, it is characterized in that, described reuse require to be retouched by the network service of the NS
Symbol (network service descriptor, abbreviation NSD) is stated come what is received.
8. method according to any one of claims 5 to 7, it is characterised in that described to reuse the VNF for requiring instruction to retain
Example can be reused the requirement of institute's foundation, and including with least a kind of in the following group:
VNF relation rules;
Capacity or load requirement;
Position constraint;
NS type constraints;
VNF type constraints;
NS number constraints;
The reusable period requires.
9. a kind of network function virtualization composer (network functions virtualization orchestrator,
Abbreviation NFVO), it is characterised in that including:
Memory storage, including instruction;
One or more processors, communicate with the memory, wherein one or more of processors perform described instruction,
With:Receive the reuse requirement of first network service (network service, abbreviation NS);
When the first NS will be terminated, require to determine that at least one composition in the first NS is virtual according to described reuse
Network function (virtual network function, abbreviation VNF) example can be reserved for reusing in the 2nd NS;
Retain at least one composition VNF examples in the first NS to be reused in the 2nd NS.
10. NFVO according to claim 9, it is characterised in that one or more of processors perform described instruction, with
Determine whether at least one composition VNF examples in the first NS meet that described reuse requires, so that it is determined that described at least one
Whether a composition VNF examples can be retained.
11. NFVO according to claim 9, it is characterised in that the reuse requirement of the first NS is by described first
The network service descriptor (network service descriptor, abbreviation NSD) of NS is come what is received.
12. the NFVO according to any one of claim 9 to 11, it is characterised in that described reuse requires instruction described the
Composition VNF examples in one NS can be retained the requirement of institute's foundation, and including with least a kind of in the following group:
VNF relation rules;
Capacity or load requirement;
Position constraint;
NS type constraints;
VNF type constraints;
The reusable period requires.
A kind of 13. network function virtualization composer (network functions virtualization
Orchestrator, abbreviation NFVO), it is characterised in that including:
Memory storage, including instruction;
One or more processors, communicate with the memory, wherein one or more of processors perform described instruction,
With:Receive the reuse requirement of network service (network service, abbreviation NS);
According to it is described reuse require determine at least one reservation virtual network function (virtual network function,
Abbreviation VNF) whether example can be reused in the NS;
The VNF examples of at least one reservation are reused in the NS.
14. NFVO according to claim 13, it is characterised in that one or more of processors perform described instruction,
To determine whether the VNF examples of at least one reservation meet that described reuse requires, so that it is determined that at least one reservation
VNF examples whether can be reused.
15. NFVO according to claim 13, it is characterised in that described reuse requires to be the network service by the NS
Descriptor (network service descriptor, abbreviation NSD) is come what is received.
16. the NFVO according to any one of claim 13 to 15, it is characterised in that described reuse requires what instruction retained
VNF examples can be reused the requirement of institute's foundation, and including with least a kind of in the following group:
VNF relation rules;
Capacity or load requirement;
Position constraint;
NS type constraints;
VNF type constraints;
NS number constraints;
The reusable period requires.
17. one kind is used for network function virtualization (network functions virtualization, abbreviation NFV) resource pipe
The method of reason, it is characterised in that including:
Virtual network function manager (virtual network function manager, abbreviation VNFM) by VNFM with
Interface between VIM from virtualized infrastructure manager (virtualized infrastructure manager, referred to as
VIM quota information) is received, the quota information instruction allows the one or more VNF for distributing to VNFM or VNFM management real
The maximum quantity of the resource of example;
The VNFM is based on the quota information and carries out resource management action.
18. according to the method for claim 17, it is characterised in that the quota information also indicates the maximum resource quantity
Change, and the method further includes:
The VNFM subscribes the change of the maximum resource quantity.
19. a kind of virtual network function manager (virtual network function manager, abbreviation VNFM), it is special
Sign is, including:
Memory storage, including instruction;
One or more processors, communicate with the memory, wherein one or more of processors perform described instruction,
With:By the interface between VNFM and VIM from virtualized infrastructure manager (virtualized infrastructure
Manager, abbreviation VIM) quota information is received, the quota information instruction allows distribute to VNFM or VNFM management one
Or the maximum quantity of the resource of multiple VNF examples;
Resource management action is carried out based on the quota information.
20. VNFM according to claim 19, it is characterised in that the quota information also indicates the maximum resource quantity
Change, and one or more of processors also perform described instruction, to subscribe the change of the maximum resource quantity.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562209642P | 2015-08-25 | 2015-08-25 | |
US62/209,642 | 2015-08-25 | ||
US201562239655P | 2015-10-09 | 2015-10-09 | |
US62/239,655 | 2015-10-09 | ||
PCT/US2016/048772 WO2017035395A1 (en) | 2015-08-25 | 2016-08-25 | System and method for network function virtualization resource management |
Publications (2)
Publication Number | Publication Date |
---|---|
CN107924383A true CN107924383A (en) | 2018-04-17 |
CN107924383B CN107924383B (en) | 2021-02-26 |
Family
ID=58096248
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201680047063.XA Active CN107924383B (en) | 2015-08-25 | 2016-08-25 | System and method for network function virtualized resource management |
Country Status (4)
Country | Link |
---|---|
US (3) | US10223140B2 (en) |
EP (1) | EP3332332A4 (en) |
CN (1) | CN107924383B (en) |
WO (1) | WO2017035395A1 (en) |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2750328A1 (en) * | 2012-12-27 | 2014-07-02 | Telefonica S.A. | Computer-implemented method and system for providing networking service, and computer program product adapted to perform the method |
EP3337095A1 (en) * | 2015-08-31 | 2018-06-20 | Huawei Technologies Co., Ltd. | Resource management method and device |
CN109074288B (en) * | 2016-03-15 | 2022-04-26 | 诺基亚通信公司 | Conflict resolution in network virtualization scenarios |
CN107769932B (en) * | 2016-08-15 | 2021-02-09 | 华为技术有限公司 | Charging method, device and system |
CN108632049B (en) * | 2017-03-15 | 2020-08-25 | 华为机器有限公司 | Method and device for virtual network function expansion |
WO2018174225A1 (en) * | 2017-03-24 | 2018-09-27 | 日本電気株式会社 | Network function virtualized management orchestration device, communication system, method, and program |
CN110546980A (en) * | 2017-04-25 | 2019-12-06 | 英特尔Ip公司 | Virtualized centralized and distributed unit connections in a radio access network |
US10117116B1 (en) | 2017-04-27 | 2018-10-30 | At&T Intellectual Property I, L.P. | System and method supporting delivery of network accessible services to connected devices of a local environment |
US10735275B2 (en) * | 2017-06-16 | 2020-08-04 | Cisco Technology, Inc. | Releasing and retaining resources for use in a NFV environment |
CN109213567B (en) | 2017-06-29 | 2022-05-13 | 华为技术有限公司 | Method and equipment for managing VNF instantiation |
US10768963B2 (en) * | 2017-07-31 | 2020-09-08 | Hewlett Packard Enterprise Development Lp | Virtual network functions allocation in a datacenter based on extinction factor |
US10764115B1 (en) | 2018-01-05 | 2020-09-01 | Open Invention Network Llc | EMS handling of faults in virtual network function components |
US10608907B2 (en) | 2018-05-11 | 2020-03-31 | At&T Intellectual Property I, L.P. | Open-loop control assistant to guide human-machine interaction |
CN112889247B (en) * | 2018-10-18 | 2022-05-31 | 华为技术有限公司 | VNF service instantiation method and device |
CN110351145B (en) * | 2019-07-18 | 2020-03-20 | 重庆电子工程职业学院 | Virtualized wireless network function arrangement method based on economic benefits |
EP4078364A4 (en) * | 2019-12-20 | 2022-12-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Migration of vnfs to vims |
CN113328871B (en) * | 2020-02-28 | 2022-08-12 | 中国移动通信有限公司研究院 | Configuration method and device for signaling acquisition and storage medium |
US11288018B2 (en) * | 2020-03-25 | 2022-03-29 | Verizon Patent And Licensing Inc. | Method and system for deploying a virtual distributed unit on a network device |
US11057274B1 (en) * | 2020-04-09 | 2021-07-06 | Verizon Patent And Licensing Inc. | Systems and methods for validation of virtualized network functions |
US11573837B2 (en) * | 2020-07-27 | 2023-02-07 | International Business Machines Corporation | Service retention in a computing environment |
CN113419828B (en) * | 2021-05-31 | 2022-07-29 | 济南浪潮数据技术有限公司 | Object storage life cycle management method and system |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080201414A1 (en) * | 2007-02-15 | 2008-08-21 | Amir Husain Syed M | Transferring a Virtual Machine from a Remote Server Computer for Local Execution by a Client Computer |
CN102857363A (en) * | 2012-05-04 | 2013-01-02 | 运软网络科技(上海)有限公司 | Automatic computing system and method for virtual networking |
US20140317261A1 (en) * | 2013-04-22 | 2014-10-23 | Cisco Technology, Inc. | Defining interdependent virtualized network functions for service level orchestration |
CN104219127A (en) * | 2014-08-30 | 2014-12-17 | 华为技术有限公司 | Creation method and device of virtual network instance |
CN104253866A (en) * | 2014-09-20 | 2014-12-31 | 华为技术有限公司 | Software deployment method and system of virtual network function network element and relevant equipment |
CN104468688A (en) * | 2013-09-13 | 2015-03-25 | 株式会社Ntt都科摩 | Method and apparatus for network virtualization |
CN104601592A (en) * | 2015-01-31 | 2015-05-06 | 华为技术有限公司 | Method for accessing cloud service and access device |
WO2015113278A1 (en) * | 2014-01-29 | 2015-08-06 | 华为技术有限公司 | Method for upgrading virtualized network function and network function virtualization orchestrator |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8904008B2 (en) * | 2012-01-09 | 2014-12-02 | Microsoft Corporation | Assignment of resources in virtual machine pools |
US9372735B2 (en) * | 2012-01-09 | 2016-06-21 | Microsoft Technology Licensing, Llc | Auto-scaling of pool of virtual machines based on auto-scaling rules of user associated with the pool |
US9350632B2 (en) * | 2013-09-23 | 2016-05-24 | Intel Corporation | Detection and handling of virtual network appliance failures |
US10193963B2 (en) * | 2013-10-24 | 2019-01-29 | Vmware, Inc. | Container virtual machines for hadoop |
US9813335B2 (en) * | 2014-08-05 | 2017-11-07 | Amdocs Software Systems Limited | System, method, and computer program for augmenting a physical system utilizing a network function virtualization orchestrator (NFV-O) |
-
2016
- 2016-08-25 US US15/247,652 patent/US10223140B2/en active Active
- 2016-08-25 WO PCT/US2016/048772 patent/WO2017035395A1/en active Application Filing
- 2016-08-25 CN CN201680047063.XA patent/CN107924383B/en active Active
- 2016-08-25 EP EP16840155.2A patent/EP3332332A4/en active Pending
-
2019
- 2019-03-04 US US16/291,949 patent/US10908936B2/en active Active
-
2021
- 2021-02-01 US US17/164,452 patent/US11429408B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080201414A1 (en) * | 2007-02-15 | 2008-08-21 | Amir Husain Syed M | Transferring a Virtual Machine from a Remote Server Computer for Local Execution by a Client Computer |
CN102857363A (en) * | 2012-05-04 | 2013-01-02 | 运软网络科技(上海)有限公司 | Automatic computing system and method for virtual networking |
US20140317261A1 (en) * | 2013-04-22 | 2014-10-23 | Cisco Technology, Inc. | Defining interdependent virtualized network functions for service level orchestration |
CN104468688A (en) * | 2013-09-13 | 2015-03-25 | 株式会社Ntt都科摩 | Method and apparatus for network virtualization |
WO2015113278A1 (en) * | 2014-01-29 | 2015-08-06 | 华为技术有限公司 | Method for upgrading virtualized network function and network function virtualization orchestrator |
CN104219127A (en) * | 2014-08-30 | 2014-12-17 | 华为技术有限公司 | Creation method and device of virtual network instance |
CN104253866A (en) * | 2014-09-20 | 2014-12-31 | 华为技术有限公司 | Software deployment method and system of virtual network function network element and relevant equipment |
CN104601592A (en) * | 2015-01-31 | 2015-05-06 | 华为技术有限公司 | Method for accessing cloud service and access device |
Also Published As
Publication number | Publication date |
---|---|
EP3332332A4 (en) | 2018-08-08 |
US10908936B2 (en) | 2021-02-02 |
CN107924383B (en) | 2021-02-26 |
EP3332332A1 (en) | 2018-06-13 |
US20190196852A1 (en) | 2019-06-27 |
US10223140B2 (en) | 2019-03-05 |
US20210182088A1 (en) | 2021-06-17 |
US11429408B2 (en) | 2022-08-30 |
WO2017035395A1 (en) | 2017-03-02 |
US20170063714A1 (en) | 2017-03-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107924383A (en) | System and method for network function virtualization resource management | |
EP2849064B1 (en) | Method and apparatus for network virtualization | |
CN106301829B (en) | A kind of method and apparatus of network service dilatation | |
US10481935B2 (en) | Management system, overall management node, and management method for managing virtualization resources in a mobile communication network | |
WO2017045471A1 (en) | Method and apparatus for acquiring service chain information in cloud computing system | |
CN105262685B (en) | A kind of message processing method and device | |
CN107689882A (en) | The method and apparatus of service deployment in a kind of virtualization network | |
EP3447965B1 (en) | Network function instance management method and relevant device | |
CN106375101A (en) | Life cycle management method and apparatus | |
CN107533484A (en) | System and method for dynamically managing virtual network function descriptor | |
US20190050248A1 (en) | Control apparatus, vnf deployment destination selection method and program | |
CN107690822A (en) | Network management | |
CN103346981A (en) | Virtual exchange method, related device and computer system | |
CN103703724A (en) | Resource payment method | |
US20130097617A1 (en) | Integration of disparate applications on a network | |
CN106685679A (en) | Network service deployment method and device | |
CN107967140A (en) | The initiating method of software modification, the method and device for issuing metadata | |
US20140233370A1 (en) | Method and system for virtual network interface cards (vnics) over aggregation spanning multiple switches | |
KR20190084294A (en) | Network service lifecycle management approval methods and devices | |
CN109327319A (en) | Method, equipment and the system of on-premise network slice | |
EP3893437B1 (en) | Method and device for deploying virtual network function | |
CN105493444B (en) | A kind of network function virtualization NFV fault management device, device and method | |
CN109213567A (en) | Method and equipment for managing VNF instantiation | |
JP2024501005A (en) | Management method and device for container clusters | |
CN103516628B (en) | A kind of realize network strategy update method, Apparatus and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |