WO2015113278A1 - 虚拟网络功能的升级方法和网络功能虚拟化编排器 - Google Patents
虚拟网络功能的升级方法和网络功能虚拟化编排器 Download PDFInfo
- Publication number
- WO2015113278A1 WO2015113278A1 PCT/CN2014/071806 CN2014071806W WO2015113278A1 WO 2015113278 A1 WO2015113278 A1 WO 2015113278A1 CN 2014071806 W CN2014071806 W CN 2014071806W WO 2015113278 A1 WO2015113278 A1 WO 2015113278A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vnf instance
- vnf
- instance
- service flow
- vnffg
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 148
- 238000012545 processing Methods 0.000 claims description 130
- 230000006870 function Effects 0.000 claims description 126
- 230000008569 process Effects 0.000 claims description 93
- OOXMVRVXLWBJKF-DUXPYHPUSA-N n-[3-[(e)-2-(5-nitrofuran-2-yl)ethenyl]-1,2,4-oxadiazol-5-yl]acetamide Chemical compound O1C(NC(=O)C)=NC(\C=C\C=2OC(=CC=2)[N+]([O-])=O)=N1 OOXMVRVXLWBJKF-DUXPYHPUSA-N 0.000 claims 2
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 15
- 230000007246 mechanism Effects 0.000 description 8
- 230000000694 effects Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000013507 mapping Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000005641 tunneling Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/06—Generation of reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method for upgrading a virtual network function and a network function virtualization orchestrator. Background technique
- the European Telecommunications Sdandards Institut has established the Network Function Virtulization Industry Specification Group (hereinafter referred to as the NFV ISG), with the aim of learning from Internet technology.
- the virtualization technology of Technology hereinafter referred to as IT
- IT enables general-purpose hardware to implement part of the network functions. Therefore, the network function needs to be run on general-purpose hardware in the form of Virtual Network Function (VNF).
- VNF Virtual Network Function
- the VNF is a virtualized entity with network capabilities. For example, if the VNF has the function of Mobi le Management Entity (MME), then this VNF is a virtual MME.
- MME Mobi le Management Entity
- the VNF is deployed on one or more virtual machines (VMs) to be a VNF instance, which is the process of instantiating the VNF.
- VMs virtual machines
- NFV MANO Virtul ization Management and Orchestration
- Figure 1 may include Operation Support System (OSS) or Business Support System (BSS), VNF, Network Functional Virtualization Infrastructure (NFV Infrastructure, hereinafter referred to as NFVI), Virtual Infrastructure Manager (VIM), NFV Orchestrator (NFVO), VNF Manager (VNF Manager, below) VNFM);
- NFVI Network Functional Virtualization Infrastructure
- VIM Virtual Infrastructure Manager
- NFVO NFV Orchestrator
- VNF Manager VNF Manager
- the VNF corresponds to a virtualized physical network function (PNF).
- the VNF can be a virtual core network (Evolved Packet Core, hereinafter referred to as EPC) node, that is, it can be virtual.
- EPC Evolved Packet Core
- NFVI E or virtual service gateway (Service Gateway, hereinafter referred to as S_GW), etc.
- S_GW Service Gateway
- NFVI consists of hardware resources and virtual resources and virtual layers
- VIM is used to control and manage virtualized entities
- NFV0 is responsible for network side programming and management of NFVI resources, and implements NFV service topology on NFVI
- VNFM is responsible for the lifecycle management of VNF instances.
- NFV MAN0 also includes a network service catalog (Network Service Catalog hereinafter referred to as NS Catalog), a VNF catalog, an NFV instance library (Instance), and four NFVI repositories; wherein, it is used to describe a network service (Network Service, The NS Descriptor (NSD) is stored in the (NS Catalog), where the NS can be a virtual EPC, including at least one VNF Forwarding Graph (hereinafter referred to as VNF Forwarding Graph).
- NS Catalog Network Service Catalog
- VNF Forwarding Graph VNF Forwarding Graph
- VNFFG a VNFFG includes at least one VNF, and a virtual link between these network functions, the VNFFG is mainly used to describe the service flow between the various network functions; a VNF description for describing the software resource requirements in the VNF (The VNF Descriptor (hereinafter referred to as VNFD) is stored in the VNF repository; the NS instance and the VNF instance are stored in the NFV instance library; the NFVI resource state is stored in the NFVI repository.
- VNFD The VNF Descriptor
- the software version in the VNF needs to be upgraded.
- the sender sends a VNF upgrade request to the NFV0, and the NFV0 sends the upgrade request to the VNFM, so that the VNFM indicates that the VM corresponding to the VNF is ready for upgrade and data migration; and the VNFM obtains the response from the VM.
- the VNF instantiation process is initiated, and a new VNF instance is obtained.
- the software in the VNF instance is the upgraded software version, and the migrated data is installed on the upgraded new VNF instance for subsequent processing.
- the VNFM performs the handover process, and the VNF instance is powered on after the upgrade, and the old version of the VNF instance is shut down.
- VNF upgrade process in the prior art may cause the VNF instance of the old version to be interrupted, which may affect the services on the VNF instance of the old version, especially for services with higher real-time requirements.
- the embodiment of the present invention provides a method for upgrading a virtual network function and a network function virtualization orchestrator, which is used to solve the problem that the VNF instance of the old version is interrupted during the VNF upgrade process in the prior art, thereby affecting the VNF instance of the old version.
- an embodiment of the present invention provides a network function virtualization orchestration device, including: a receiver, configured to receive an upgrade request message sent by a sending end, where the upgrade request message is used to request virtualization of the network function
- the arranger NFV0 corresponds to the first virtual network function VNF
- the first software version is upgraded to the second software version, the first software version corresponds to the first VNF instance, and the second software version corresponds to the second VNF instance;
- a processor configured to instantiate the first VNF according to a VNFD of the second software version of the first VNF preset in the VNF directory, obtain a second VNF instance, and connect the second VNF instance to After the network service NS where the first VNF instance is located, the forwarding path of the service flow in the NS is configured, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second The VNF instance performs processing; and determines that the first VNF instance runs idling within a preset time, and the NFV0 terminates the first VNF instance.
- the processor is specifically configured to determine at least one first NS to which the first VNF instance belongs, and the first NS
- the first NS includes at least one virtual network function forwarding map VNFFG, the first VNFFG in the VNFFG includes the first VNF instance, and the first NS corresponds to the first network.
- the service description NSD is configured to obtain a second NSD preset in the NS directory according to the identifier of the second NS in the NS instance update request sent by the sender, and determine the location according to the second NSD.
- the first VNF is instantiated; wherein the second NS is the first NS to be updated that is determined by the sending end according to the identifier of the first NS, and the second NSD is the modified first NSD; and instantiating the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory to obtain the second VNF instance; the receiver is further configured to receive the Said N sent by the sender An S instance update request; wherein the NS instance update request includes an identifier of at least one second NS.
- the processor is specifically configured to connect the second VNF instance to the second NS Obtaining an updated second NS; wherein the updated second NS includes the first VNFFG and the second VNFFG, the second VNFFG includes the second VNF instance, and the second VNF instance a connection manner of the other VNF instances in the second VNFFG in the second VNFFG, and a connection of the first VNF instance in the first VNFFG with other VNF instances in the first VNFFG The same way.
- the processor is configured to configure the first VNFFG and the second VNFFG Deriving the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the The first VNFFG performs processing, and the second service flow is forwarded to the second VNFFG processing.
- the processor is specifically configured to indicate that the NS service management entity: the first VNFFG and the first The second VNFFG is configured to forward the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG for processing. .
- the processor is configured to check whether the first VNF instance exists; if yes, obtain the preset in the VNF directory VNFD of the second software version of the first VNF; and instantiating the first VNF according to the VNFD of the second software version of the first VNF to obtain the second VNF instance.
- the processor is specifically configured to connect the second VNF instance to the first VNF instance In the NS, the connection manner between the second VNF instance and other VNF instances in the NS, and the first VNF instance are connected to other VNF instances in the NS.
- the processor is configured to configure the first VNF instance and the second VNF instance And generating, by the service flow, a service flow forwarding table as a node in the forwarding path of the service flow in the NS; and configuring the service flow forwarding table to the third VNF instance, so that the third VNF instance is configured And forwarding, by the service flow forwarding table, the first service flow to the first VNF instance, and forwarding the second service flow to the second VNF instance, where the third VNF instance is respectively Adjacent to the first VNF instance and the second VNF instance.
- the processor is specifically configured to: between the first VNF instance and the third VNF instance a weight value of the first virtual link, and a weight value of the second virtual link between the second VNF instance and the third VNF instance is configured to the third VNF instance, so that the third The VNF instance forwards the first service flow to the first VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link, and forwards the second service flow. And processing, by the second VNF instance, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the processor is configured to be used by the NS service management entity to perform the first VNF instance and the The second VNF instance is configured to send the service flow forwarding table to the node in the forwarding path of the NS in the service flow, and instruct the NS service management entity to configure the service flow forwarding table to the
- the third VNF instance is configured to forward, by the third VNF instance, the first service flow to the first VNF instance according to the service flow forwarding table, and forward the second service flow to the first The VNF instance is processed; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the processor is configured to instruct the NS service management entity to perform the first VNF instance and the third a weight value of the first virtual link between the VNF instances, and a weight value of the second virtual link between the second VNF instance and the third VNF instance are configured to the third VNF instance to And causing the third VNF instance to forward the first service flow to the first VNF instance according to a weight value of the first virtual link and a weight value of the second virtual link, where The second service flow is forwarded to the second VNF instance, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the processor is specifically configured to acquire an NS service management entity Monitoring the running status of the first VNF instance; if the first VNF instance runs idly within the preset time, instructing the NS management entity to terminate the first VNF instance.
- the tenth possible implementation manner of the first aspect The operating state of the first VNF instance is monitored, and the first VNF instance is terminated when it is detected that the first VNF instance runs idle during the preset time.
- the processor is further configured to be configured in the NS After the service flow forwarding path, the second VNF instance is added to the network function virtualization NFV instance library; and the VNF resource scaling process is started to perform resource scaling processing on the first VNF instance and the second VNF instance.
- the processor is further configured to delete the first VNF instance in the NFV instance library.
- an embodiment of the present invention provides a network function virtualization orchestration device, including: a receiving module, configured to receive an upgrade request message sent by a sending end, where the upgrade request message is used to request the virtualizing of the network function
- the orchestrator NFV0 upgrades the first software version corresponding to the first virtual network function VNF to the second software version, the first software version corresponds to the first VNF instance, and the second software version corresponds to the second VNF instance;
- An instantiation module configured to instantiate the first VNF according to a VNFD of the second software version of the first VNF preset in the VNF directory, to obtain a second VNF instance;
- connection module configured to connect the second VNF instance to the network service NS where the first VNF instance is located;
- a configuration module configured to: configure a forwarding path of the service flow in the NS, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing;
- the NFV0 terminates the first VNF instance by determining that the first VNF instance runs idle during a preset time.
- the instantiating module includes:
- Determining a sending unit configured to determine at least one first NS to which the first VNF instance belongs, and sending the identifier of the first NS to the sending end; where the first NS includes at least one virtual network function Forwarding map VNFFG, the first VNFFG in the VNFFG includes the first VNF instance, and the first NS corresponds to the first network service description NSD;
- Determining an obtaining unit configured to obtain a second NSD preset in the NS directory according to the identifier of the second NS in the NS instance update request sent by the sending end, and determine the pair according to the second NSD
- the first VNF is instantiated; wherein the second NS is the first NS to be updated that is determined by the sending end according to the identifier of the first NS, and the second NSD is a modified An NSD;
- a first instantiating unit configured to instantiate the first VNF according to a VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the second VNF instance;
- the receiving module is further configured to receive the NS instance update request sent by the sending end, where the NS instance update request includes an identifier of at least one second NS.
- the connecting module is specifically configured to connect the second VNF instance to the second NS Obtaining the updated second NS; wherein the updated second NS includes the first VNFFG and the second VNFFG, the second VNFFG includes the second VNF instance, and the second VNF instance a connection manner of the second VNFFG with other VNF instances in the second VNFFG, and a connection of the first VNF instance with the other VNF instances in the first VNFFG in the first VNFFG.
- the configuration module is configured to configure the first VNFFG and the second VNFFG
- the service flow is used as a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG process.
- the configuration module is specifically configured to instruct the NS service management entity to use the first VNFFG and the first The second VNFFG is configured to forward the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG for processing. .
- the instantiating module further includes:
- the obtaining unit is configured to check whether the first VNF instance exists; if yes, acquiring a VNFD of the second software version of the first VNF preset in the VNF directory;
- a second instantiating unit configured to instantiate the first VNF according to the VNFD of the second software version of the first VNF, to obtain the second VNF instance.
- the connecting module is specifically configured to connect the second VNF instance to the first VNF instance In the NS, the connection manner between the second VNF instance and other VNF instances in the NS, and the first VNF instance are connected to other VNF instances in the NS.
- the configuration module is configured to configure the first VNF instance and the second VNF instance Giving the service flow, as a node in the forwarding path of the service flow in the NS,
- the service flow forwarding table is configured to be configured to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table for processing. And forwarding the second service flow to the second VNF instance processing, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the configuration module is specifically configured to: between the first VNF instance and the third VNF instance a weight value of the first virtual link, and a weight value of the second virtual link between the second VNF instance and the third VNF instance is configured to the third VNF instance, so that the third The VNF instance forwards the first service flow to the first VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link, and forwards the second service flow. And processing, by the second VNF instance, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the configuration module is specifically configured to instruct the NS service management entity to perform the first VNF instance and the The second VNF instance is configured to send the service flow forwarding table to the node in the forwarding path of the NS in the service flow, and instruct the NS service management entity to configure the service flow forwarding table to the
- the third VNF instance is configured to forward, by the third VNF instance, the first service flow to the first VNF instance according to the service flow forwarding table, and forward the second service flow to the first The VNF instance is processed; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the configuration module is specifically configured to instruct the NS service management entity to use the first VNF instance and the third a weight value of the first virtual link between the VNF instances, and a weight value of the second virtual link between the second VNF instance and the third VNF instance are configured to the third VNF instance to And causing the third VNF instance to forward the first service flow to the first VNF instance according to a weight value of the first virtual link and a weight value of the second virtual link, where The second service flow is forwarded to the second VNF instance, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the determining termination module is specifically used for acquiring the NS industry The operating state of the first VNF instance monitored by the management entity; if the first VNF instance runs idly within the preset time, instructing the NS management entity to terminate the first VNF instance.
- the determining termination module is specifically used to indicate NS service management
- the entity monitors an operating state of the first VNF instance, and terminates the first VNF instance when it is detected that the first VNF instance runs idle during the preset time.
- a module configured to add the second VNF instance to a network function virtualization NFV instance library after the configuration module configures a service flow forwarding path in the network service NS;
- the resource scaling module is configured to perform resource scaling processing on the first VNF instance and the second VNF instance by using a VNF resource scaling process.
- the network function virtualization orchestrator further includes:
- a deleting module configured to delete the first VNF instance in the NFV instance library after the determining termination module terminates the first VNF instance.
- the present invention provides a method for upgrading a virtual network function, including:
- the network function virtualization orchestrator NFV0 receives the upgrade request message sent by the sending end, where the upgrade request message is used to request the NFV0 to upgrade the first software version corresponding to the first virtual network function VNF to the second software version.
- the first software version corresponds to the first VNF instance
- the second software version corresponds to the second VNF instance;
- the NFV0 instantiates the first VNF according to a VNFD of the second software version of the first VNF preset in the VNF directory, to obtain a second VNF instance;
- the NFV0 connects the second VNF instance to the network service NS where the first VNF instance is located;
- the NFV0 configures a forwarding path of the service flow in the NS, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing;
- the first VNF instance runs idling for a preset time, and the NFV0 terminates the first VNF instance.
- the NFV0 is based on The VNFD of the second software version of the first VNF that is preset in the VNF directory instantiates the first VNF to obtain a second VNF instance, including:
- the first NS includes at least one virtual network function forwarding map VNFFG
- the first VNFFG in the VNFFG includes the first VNF instance
- the NFV0 receives the NS instance update request sent by the sending end, where the NS instance update request includes at least one identifier of the second NS
- the second NS is the first NS to be updated that is determined by the sending end according to the identifier of the first NS; wherein the first NS corresponds to a first network service description NSD;
- the NFV0 obtains a second NSD preset in the NS directory according to the identifier of the second NS, and determines to instantiate the first VNF according to the second NSD; wherein, the second NSD is modified First NSD;
- the NFV0 instantiates the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the second VNF instance.
- the NFV0 connects the second VNF instance to a network service NS where the first VNF instance is located Including:
- the NFV0 connects the second VNF instance to the second NS, and obtains the updated second NS; wherein the updated second NS includes the first VNFFG and the second VNFFG, The second VNFFG includes the second VNF instance, and the second VNF instance is connected to the other VNF instances in the second VNFFG in the second VNFFG, and the first VNF instance is in the The first VNFFG is connected in the same manner as the other VNF instances in the first VNFFG.
- the forwarding path of the NFV0 configuration service flow in the NS includes:
- the NFV0 configures the first VNFFG and the second VNFFG to the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, The second traffic flow is forwarded to the second VNFFG process.
- the forwarding path of the NFV0 configuration service flow in the NS includes: The NFVO instructs the NS service management entity to configure the first VNFFG and the second VNFFG to the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG Processing, the second service flow is forwarded to the second VNFFG for processing.
- the NFV0 instantiates the first VNF according to a VNFD of a second software version of the first VNF preset in a VNF directory , obtain the second VNF instance, including:
- the NFV0 checks whether the first VNF instance exists
- the NFV0 acquires a VNFD of the second software version of the first VNF preset in the VNF directory;
- the NFV0 instantiates the first according to the VNFD of the second software version of the first VNF
- the NFV0 connects the second VNF instance to a network service NS where the first VNF instance is located Including:
- the NFV0 connects the second VNF instance to the NS in which the first VNF instance is located, and the manner in which the second VNF instance is connected to other VNF instances in the NS, and the first VNF The instance is connected in the same way as other VNF instances in the NS.
- the forwarding path of the NFV0 configuration service flow in the NS includes:
- the NFV0 configures the first VNF instance and the second VNF instance to the service flow, and generates a service flow forwarding table as a node in the forwarding path of the service flow in the NS;
- the NFV0 configures the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table, and processes the The second service flow is forwarded to the second VNF instance processing; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the forwarding path of the NFV0 configuration service flow in the NS includes:
- the NFV0 sets a weight value of the first virtual link between the first VNF instance and the third VNF instance, and a second virtual link between the second VNF instance and the third VNF instance
- the weight value is configured to the third VNF instance such that the third VNF instance is according to the first virtual chain
- the weight value of the road and the weight value of the second virtual link forward the first traffic flow to the first
- the VNF instance is processed, and the second VNF instance is forwarded to the second VNF instance.
- the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the forwarding path of the NFV0 configuration service flow in the NS includes:
- the NFV0 indicates that the NS service management entity configures the first VNF instance and the second VNF instance to the service flow, and generates a service flow forwarding table as a node in the forwarding path of the service flow in the NS. ;
- the NFV0 instructs the NS service management entity to configure the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the The first VNF instance is processed to forward the second service flow to the second VNF instance process; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the forwarding path of the NFV0 configuration service flow in the NS includes:
- the NFV0 indicates, by the NS service management entity, a weight value of the first virtual link between the first VNF instance and the third VNF instance, and between the second VNF instance and the third VNF instance. And assigning, by the third VNF instance, the weight value of the second virtual link to the third VNF instance, according to the weight value of the first virtual link and the weight value of the second virtual link.
- the first service flow is forwarded to the first VNF instance for processing
- the second service flow is forwarded to the second VNF instance for processing; wherein the third VNF instance is respectively associated with the first VNF instance and the The second VNF instance is adjacent.
- the NFV0 determines that the first VNF instance is preset The NFV0 terminates the first VNF instance, and the method includes:
- the NFV0 acquires an operating state of the first VNF instance monitored by the NS service management entity; if the first VNF instance runs idly within the preset time, the NFV0 indicates that the NS management entity terminates The first VNF instance is described.
- the NFV0 determines that the first VNF instance is preset The NFV0 terminates the first VNF instance, and the method includes:
- the NFV0 instructs the NS service management entity to monitor an operating state of the first VNF instance, and terminates the first VNF instance when the first VNF instance runs idle during the preset time.
- the NFV0 configures service flow forwarding in the network service NS After the path, it also includes:
- the NFV0 adds the second VNF instance to the network function virtualization NFV instance library; the NFV0 starts the VNF resource scaling process to perform resource scaling processing on the first VNF instance and the second VNF instance.
- the method further includes:
- the NFV0 deletes the first VNF instance in the NFV instance library.
- the method for upgrading the virtual network function and the network function virtualization orchestration receive, by the receiver, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version.
- the processor instantiates the first VNF according to the VNFD of the second software version preset in the VNF directory to obtain the second VNF instance, and connects the second VNF instance to the NS where the first VNF instance is located;
- the processor configures the forwarding path of the service flow in the NS, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second
- the VNF instance can process different service flows in parallel; and when it is determined that the first VNF instance runs in a preset time, the first VNF instance is terminated, thereby completing seamless switching between the first VNF instance and the second VNF instance.
- FIG. 1 is a schematic structural diagram of an NFV MAN0 provided by the present invention.
- FIG. 2 is a schematic structural diagram of Embodiment 1 of a network function virtualization orchestrator provided by the present invention
- FIG. 3 is a schematic diagram 1 of connection of a second VNF instance in an NS according to the present invention
- FIG. 4 is a schematic diagram 2 of a connection of a second VNF instance provided in the NS according to the present invention.
- FIG. 5 is a schematic structural diagram of Embodiment 2 of a network function virtualization orchestrator provided by the present invention
- FIG. 6 is a schematic structural diagram of Embodiment 3 of a network function virtualization orchestrator provided by the present invention
- FIG. 7 is a schematic diagram of network function virtualization arrangement provided by the present invention
- FIG. 8 is a schematic structural diagram of Embodiment 5 of a network function virtualization orchestrator provided by the present invention
- FIG. 9 is a flowchart of Embodiment 1 of a method for upgrading a virtual network function provided by the present invention
- FIG. 11 is a flowchart of Embodiment 3 of a method for upgrading a virtual network function provided by the present invention
- FIG. 2 is a schematic structural diagram of Embodiment 1 of a network function virtualization orchestrator provided by the present invention.
- the NFV0 involved in this embodiment is applicable to the NFV architecture diagram shown in FIG. 1.
- the NFV0 includes: a receiver 10 and a processor 11.
- the receiver 10 is configured to receive an upgrade request message sent by the sender (Sender), where the upgrade request message is used to request the NFV0 to upgrade the first software version corresponding to the first VNF to the second software version, where the A software version corresponds to the first VNF instance, the second software version corresponds to the second VNF instance, and the processor 11 is configured to pair the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory.
- the forwarding path of the service flow in the NS is configured to forward the first service flow to the first
- the VNF instance is processed, and the second service flow is forwarded to the second VNF instance for processing; and the first VNF is determined.
- NFV0 terminates the first VNF instance.
- the sending end sends an upgrade request message to the receiver 10, and is configured to request the NFV0 to upgrade the first software version corresponding to the first VNF in the NS to the second software version, where the first software version corresponds to the first VNF.
- the second software version corresponds to the second VNF instance.
- the first VNF may be a VNF or a plurality of VNFs, which is not limited by the embodiment of the present invention. If there are multiple first VNFs, you only need to repeat the following process when upgrading the software version of each VNF. Moreover, the process of upgrading the first software version corresponding to the first VNF to the second software version is actually a process of obtaining the second VNF instance corresponding to the second software version.
- the processor 11 After the receiver 10 receives the upgrade request message, the processor 11 verifies the validity of the upgrade request message (the processor 11 has its own authentication mechanism); when the upgrade request message is valid, the processor 11 slaves the VNF directory.
- the VNFD of the second software version of the preset first VNF is read, and the first VNF is instantiated according to the VNFD of the second software version to obtain a second VNF instance.
- the function of the VNFD preset in the VNF directory is mainly to describe the hardware resource requirements of the software corresponding to the second software version of the first VNF, so that the software corresponding to the second software version can match the hardware resources. , enabling the second software version in the first VNF to run to become the second VNF instance.
- the first VNF instance is the VNF instance before the upgrade (the old VNF instance)
- the second VNF instance is the upgraded VNF instance (the new version of the VNF instance).
- multiple VNF instances are connected to one or more NSs through virtual links.
- the processor 11 obtains the second VNF instance, the second VNF instance is connected to the NS where the first VNF instance is located. Further, the processor 11 configures a forwarding path of the service flow in the NS, so that the first service flow transmitted from one or more senders can be forwarded to the first VNF instance for processing, and the second service flow can be forwarded to The second VNF instance is processed (the first service flow is the old service flow previously processed by the first VNF instance, and the second service flow is the new service flow), that is, the first VNF instance and the second VNF. Instances can run in parallel, but the business flows processed are not the same.
- the processor 11 configures a forwarding path of the service flow in the NS, which may be a service flow forwarding policy preset by the NFV0, or may be a parameter related to the service flow forwarding path, that is, the related parameter may be indirectly utilized.
- the forwarding path of the service flow is obtained.
- the embodiment of the present invention does not limit the form of the forwarding path.
- the processor 11 determines the first service of the sender. The service flow has been processed, and the first VNF instance is terminated, and the new service flow (second service flow) is forwarded to the second VNF instance for processing, thereby completing the soft handover of the old and new service flows, and does not cause the old The interruption of the business flow.
- the processor 11 may further determine that the virtual i sed Network Function Forwarding Graph belongs to the NS in a certain preset time period. VNFFG) When all the first VNF instances are running at no load, all the first VNF instances in the VNFFG are terminated.
- the network function virtualization orchestrator provided by the embodiment of the present invention receives, by the receiver, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the processor is preset according to the preset
- the second software version of the VNFD in the VNF directory instantiates the first VNF to obtain the second VNF instance, and connects the second VNF instance to the NS where the first VNF instance is located; afterwards, the processor configures the service flow in the above
- the forwarding path in the NS is such that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can be processed in parallel.
- the embodiment relates to a specific process in which the processor 11 obtains the second VNF instance.
- the processor 11 is specifically configured to determine the at least one first NS to which the first VNF instance belongs, and send the identifier of the first NS to the sending end, where the first NS includes at least one VNFFG, where The first VNFFG in the VNFFG includes the first VNF instance, and the first NS corresponds to the first NSD; and the NS directory is obtained according to the identifier of the second NS in the NS instance update request sent by the sender received by the receiver 10 Determining the second NSF, and determining the first VNF according to the second NSD; wherein, the second NS is the first NS to be updated, and the second, determined by the sending end according to the identifier of the first NS, The NSD is the modified first NSD; and the first VNF is instantiated according to the VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the second VNF instance; And the NS instance update request is sent by the sending end, where the NS instance update request includes an
- the processor 10 verifies the validity of the upgrade request message (the processor 11 has its own verification mechanism); when the upgrade request message is valid, the process is processed.
- the first NS in which the first VNF instance corresponding to the first software version of the first VNF is located may be one, or may be multiple; and the first NS includes at least one VNFFG, VNFFG
- the first VNFFG includes a first VNF instance.
- the first NS corresponds to the first NSD, and the role of the first NSD is mainly to describe how many VNFFGs in the first NS, how many VNF instances are included in each VNFFG, and the connection relationship between the VNF instances.
- the processor 11 sends the identifiers of the first NSs to the sender, so that the sender determines, from the identifiers of the first NSs, which first NS to update, that is, the second NS mentioned in the following embodiment.
- the second NS is the first NS to be updated determined by the transmitting end.
- the sender sends the determined identifier of the second NS to the receiver 10 in the NS instance update request, where the NS instance update request includes the identifier of the at least one second NS.
- the receiver 10 instructs the processor 11 to obtain a preset second NSD from the NS directory according to the identifier of the second NS, where the second NSD is the modified first NSD, that is,
- the role of the second NSD is mainly to describe the NS to update the first NS, for example:
- the second NSD describes how many VNFFGs, how many VNF instances, and each VNF instance to be updated. How is the NS connected?
- the processor 11 After acquiring the second NSD in the NS directory, the processor 11 checks in the second NS which VNF instance corresponding to the software version of the VNF already exists according to the specific description of the second NSD, and which VNF software version corresponds to The VNF instance does not exist, that is, the processor 11 can learn which VNF to specifically instantiate according to the second NSD, thereby implementing a software version upgrade process of the VNF.
- the first VNF instance corresponding to the first software version of the first VNF in the second NS is already present, but the VNF instance corresponding to the second software version of the first VNF does not exist, so the processor 11 determines the first VNF.
- the instance is instantiated.
- the processor 11 can obtain the VNFD of the second software version of the preset first VNF from the VNF directory, and instantiate the first VNF according to the VNFD of the second software version to obtain the second VNF instance.
- the second NSD preset in the NS directory can be obtained by modifying the process of the NSD (the process of modifying the NSD can be referred to the prior art), and modifying the first NSD may be sent by the receiver 10 to the sender.
- the NS instance update request is executed by the processor 11 before or after the request, and is pre-stored in the NS directory; the second software version of the first VNF preset in the VNF directory
- the VNFD can be obtained through the VNF loading process (the VNF loading process can be seen in the prior art), and the process of loading the VNF is actually the process of loading the second VNFD into the VNF directory, and the process of loading the VNF can also be at the receiver 10.
- the method involved in the embodiment is to obtain a specific process of the second VNF instance.
- the processor 11 is specifically configured to check whether the first VNF instance exists; if yes, obtain a VNFD of the second software version of the first VNF preset in the VNF directory; and according to the second VNF The software version of the VNFD instantiates the first VNF to obtain a second VNF instance.
- the processor 11 After receiving the upgrade request sent by the sender, the processor 11 verifies the validity of the upgrade request message (the processor 11 has its own verification mechanism); when the upgrade request message is valid, the process is processed.
- the device 11 checks in the NS whether the first VNF instance exists. When the first VNF instance exists, the processor returns a consent to upgrade the response to the sender, and obtains a VNFD of the second software version of the first VNF preset in the VNF directory, and according to the second software version of the first VNF The VNFD instantiates the first VNF and obtains the second VNF instance.
- VNFD of the second software version of the first VNF preset in the VNF directory can be obtained through the VNF loading process (the VNF loading process can be referred to the prior art), and the process of loading the VNF is actually loading the second VNFD.
- the process to the VNF directory, and the process of loading the VNF may also be performed by the processor 11 before or after the receiver receives the NS instance update request sent by the sender.
- the network function virtualization orchestrator provided by the embodiment of the present invention receives, by the receiver, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the processor is preset according to the preset
- the second software version of the VNFD in the VNF directory instantiates the first VNF to obtain the second VNF instance, and connects the second VNF instance to the NS where the first VNF instance is located; afterwards, the processor configures the service flow in the above
- the forwarding path in the NS is such that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can be processed in parallel.
- the processor 11 connects the second VNF instance to the NS for the difference in the process of obtaining the second VNF instance, and the process of configuring the forwarding path of the service flow in the NS is also different. The following are introduced separately.
- the embodiment relates to the processor 11 connecting the obtained second VNF instance to the NS and configuring the forwarding path of the service flow in the NS.
- Specific process Specifically:
- the processor 11 obtains the second VNF instance
- the second VNF instance is connected to the second NS, and the updated second NS is obtained.
- the updated second NS includes the first VNFFG and the second VNFFG.
- the second VNFFG includes a second VNF instance, and a connection manner of the second VNF instance in the second VNFFG with other VNF instances in the second VNFFG and the first VNF instance in the first VNFFG
- the connection with other VNF instances in the first VNFFG is the same, that is, a second VNFFG is added to the second NS, and becomes the updated second NS. For example: As shown in FIG.
- the updated second The NS includes two VNFFGs, which are a first VNFFG and a second VNFFG (the first VNFFG is the original VNFFG in the second NS, and the second VNFFG is a new VNFFG including the second VNF instance); wherein, the first VNFFG Five VNF instances including VNF1, VNF2, VNF3, VNFx and VNF4 are included, and VNFx represents the first VNF instance, and the second VNFFG includes VNFK VNF2, VNF3, VNFy, VNF4 five VNF instances, and VNFy represents the second VNF instance. . Referring to FIG.
- VNFx is connected in a cascade manner with VNF1, VNF2, VNF3 and VNF4, and in the second VNFFG, VNFy is also connected in cascade with VNF 1, VNF2, VNF3 and VNF4. .
- VNFx is connected in a cascade manner with VNF1, VNF2, VNF3 and VNF4
- VNFy is also connected in cascade with VNF 1, VNF2, VNF3 and VNF4.
- the updated second NS includes two VNFFGs, which are a first VNFFG and a second VNFFG (the first VNFFG is the original VNFFG in the second NS, and the second VNFFG is newly added including the first VNFFG of the second VNF instance; wherein the first VNFFG includes VNFx 1, VNF2x, VNF3x, VNF4x, VNF5x 5 VNF instances, and VNFx 1, VNF2x, VNF3x, VNF4x, VNF5x are the first VNF instance, the second VNFFG
- the VNF1 y, VNF2y, VNF3y, VNF4y, VNF5y 5 VNF instances are included, and VNFly, VNF2y, VNF3y, VNF4y, and VNF5y represent the second VNF instance, that is, the example of FIG.
- VNF 4 is included in the second NS. All VNFs are upgraded with the software version to obtain a new software version of the VNF instance.
- VNFxl, VNF2x, VNF3x, VNF4x and VNF5x are connected in a cascade manner, then in the second VNFFG, VNFl y , VNF2y , VNF3y , VNF4y And VNF5y are also connected in a cascading manner.
- the foregoing processor 11 can configure the forwarding path of the service flow in the NS in two implementation manners, namely:
- the first type the processor 11 configures the first VNFFG and the second VNFFG as the forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG. deal with.
- the second processor instructs the NS service management entity to configure the first VNFFG and the second VNFFG as the forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second The traffic is forwarded to the second VNFFG for processing.
- the forwarding path can be implemented in a variety of ways, for example: Using policy-based routing, the service flow is required to be forwarded according to the source address, so that the traffic from the new source address is forwarded. To the new VNFFG; or, use tunneling technology to distinguish the forwarding path of new and old data streams through tunnel configuration; or use the Service Function Chaining (SFC) mechanism defined in the IETF or other service chain (service chain) ) Mechanism.
- SFC Service Function Chaining
- the processor 11 when the processor 11 configures the forwarding path of the service flow in the NS, the first service flow is forwarded to the first VNF instance, and the second service flow is forwarded to the second VNF instance.
- the processor 11 determines whether the first VNF instance is running at no load for a preset period of time, and if so, the processor 11 terminates the first VNF instance in time.
- the processor 11 is further configured to obtain an operation state of the first VNF instance that is monitored by the NS service management entity, that is, the running state of the VNF instance is monitored by the NS service management entity, and the NS service management entity monitors the first
- the operating state of the VNF instance is communicated to the processor 11; if the first VNF instance runs idling for a preset time, the processor 11 instructs the NS management entity to terminate the first VNF instance.
- the processor 11 instructs the NS service management entity to monitor the running status of the first VNF instance, and instructs the NS service management entity to terminate the first VNF instance when it detects that the first VNF instance runs idle within a preset time.
- the processor 11 directly instructs the NS service management entity to directly terminate the first VNF instance by the NS service management entity, as long as the NS service management entity detects that the first VNF instance is running at a preset time.
- the device 11 transmits the monitored operational status of the first VNF instance.
- the processor 11 configures a service flow forwarding path in the NS, so that the first service flow is forwarded to the first VNF instance, and after the second service flow is forwarded to the second VNF instance, the second VNF is The instance is added to the NFV instance library. At this time, the second VNF instance and the first VNF instance are working at the same time, but the load of the second VNF instance is increased, and the load of the first VNF instance is gradually reduced. To ensure efficient use of resources, the processor 11 can start the resource scaling process. The resources used by the first VNF instance are reduced, and the resources used by the second VNF instance are increased to ensure effective and rational use of the resources. In addition, after the first VNF instance is terminated, the processor 11 deletes the entry of the first VNF instance in the NFV instance library to ensure the accuracy of the NFV instance library content.
- the network function virtualization orchestrator provided by the embodiment of the present invention receives, by the receiver, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the processor is preset according to the preset
- the second software version of the VNFD in the VNF directory instantiates the first VNF to obtain the second VNF instance, and connects the second VNF instance to the NS where the first VNF instance is located; afterwards, the processor configures the service flow in the above
- the forwarding path in the NS is such that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can be processed in parallel.
- the embodiment relates to the processor 11 connecting the obtained second VNF instance to the NS and configuring the forwarding path of the service flow in the NS. Another specific process. Specifically:
- the processor 11 connects the obtained second VNF instance to the NS in which the first VNF instance is located, and the connection manner between the second VNF instance and other VNF instances in the NS, and the first VNF instance and the NS in the NS Other VNF instances are connected in the same way.
- the second VNF instance that is connected to the NS as an extension of the first VNF instance.
- the foregoing processor 1 1 can configure the forwarding path of the service flow in the NS in four implementation manners, namely:
- the first type the processor 1 1 configures the first VNF instance and the second VNF instance to the service flow, and generates a service flow forwarding table as a node in the forwarding path of the service flow in the NS;
- the processor 11 configures the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table, and forwards the second service flow to the second VNF instance processing; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the second type the processor 11 indicates that the NS service management entity configures the first VNF instance and the second VNF instance to the service flow, and generates a service flow forwarding table as a node in the forwarding path of the service flow in the NS;
- the processor 11 configures the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table, and forwards the second service flow to the second The VNF instance is processed; wherein the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the third type the processor 1 1 adds a weight value of the first virtual link between the first VNF instance and the third VNF instance, and a second virtual link between the second VNF instance and the third VNF instance.
- the weight value is configured to be sent to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link, Forwarding the second service flow to the second VNF instance processing; where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the fourth type the processor 11 indicates that the NS service management entity sets the weight value of the first virtual link between the first VNF instance and the third VNF instance, and between the second VNF instance and the third VNF instance.
- the weight value of the second virtual link is configured to the third VNF instance, so that the third VNF instance forwards the first service flow to the first according to the weight value of the first virtual link and the weight value of the second virtual link.
- the VNF instance is processed to forward the second service flow to the second VNF instance processing, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the service flow forwarding table may be a mapping relationship table between different service flows and forwarding nodes, that is, the third VNF instance learns different according to the mapping relationship table between the service flow and the forwarding node.
- the traffic is forwarded to the corresponding node for processing.
- the COST value of the virtual link between the second VNF instance and the third VNF instance may be configured, so that the COST value is much smaller than the first VNF instance.
- the virtual link between the third VNF instances is configured with a very low COST value to It is guaranteed that it is smaller than the COST value of the virtual link between the first VNF instance and the third VNF instance. Therefore, the third VNF instance selects a link with a low COST value according to the configured forwarding path, and the old service flow is still processed by the first VNF instance, and the new service flow is forwarded to the second VNF instance for processing.
- the processor 11 when the processor 11 configures the forwarding path of the service flow in the NS, the first service flow is forwarded to the first VNF instance, and the second service flow is forwarded to the second VNF instance.
- the processor 11 determines whether the first VNF instance is running at no load for a preset period of time, and if so, the processor 11 terminates the first VNF instance in time.
- the processor 11 can also obtain the running status of the first VNF instance monitored by the NS service management entity, that is, the running status of the VNF instance is monitored by the NS service management entity, and the NS service management entity monitors the The operating state of a VNF instance is communicated to the processor 11; if the first VNF instance runs idling for a preset time, the processor 11 instructs the NS management entity to terminate the first VNF instance. Alternatively, the processor 11 instructs the NS service management entity to monitor the running status of the first VNF instance, and instructs the NS service management entity to terminate the first VNF instance when it detects that the first VNF instance runs idle within a preset time.
- the processor 1 1 directly instructs the NS service management entity to terminate the first VNF instance directly by the NS service management entity, as long as the NS service management entity detects that the first VNF instance runs in a preset time.
- the processor 11 transmits the monitored operational status of the first VNF instance.
- the processor 11 configures a service flow forwarding path in the NS, so that the first service flow is forwarded to the first VNF instance, and after the second service flow is forwarded to the second VNF instance, the second VNF instance is added to the NFV instance library. .
- the second VNF instance and the first VNF instance are working at the same time, but the load of the second VNF instance is increased, and the load of the first VNF instance is gradually reduced.
- the processor 11 can start the resource scaling process. The resources used by the first VNF instance are reduced, and the resources used by the second VNF instance are increased to ensure effective and rational use of the resources.
- the processor 11 deletes the entry of the first VNF instance in the NFV instance library to ensure the accuracy of the NFV instance library content.
- the network function virtualization orchestrator provided by the embodiment of the present invention receives, by the receiver, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the processor is preset according to the preset
- the second software version of the VNFD in the VNF directory instantiates the first VNF to obtain the second VNF instance, and connects the second VNF instance to the NS where the first VNF instance is located; afterwards, the processor configures the service flow in the above
- the forwarding path in the NS is such that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing.
- the first VNF instance and the second VNF instance are configured to process different service flows in parallel; and when it is determined that the first VNF instance runs in a preset time, the first VNF instance is terminated, thereby completing the first VNF instance and the second
- the seamless switching of the VNF instance avoids the interruption of the VNF instance of the old version during the VNF upgrade process, and satisfies the real-time requirements of the service; and ensures the rational use of resources by starting the resource scaling process.
- FIG. 5 is a schematic structural diagram of Embodiment 2 of a network function virtualization orchestrator provided by the present invention.
- the NFV0 involved in this embodiment is applicable to the NFV architecture diagram shown in FIG.
- the NFV0 includes: a receiving module 20, an instantiation module 21, a connection module 22, a configuration module 23, and a judgment termination module 24, wherein the receiving module 20 is configured to receive an upgrade request message sent by the sender;
- the upgrade request message is used to request the network function virtualization orchestrator NFV0 to upgrade the first software version corresponding to the first virtual network function VNF to the second software version, where the first software version corresponds to the first VNF instance.
- the second software version corresponds to the second VNF instance;
- the instantiation module 21 is configured to instantiate the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the first a VNF instance, a connection module 22, configured to connect the second VNF instance to the network service NS where the first VNF instance is located, and a configuration module 23, configured to configure a forwarding path of the service flow in the NS,
- the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing;
- determining the termination module 24 For determining whether the first no-load operation VNF instance within the preset time, then the first example NFV0 VNF said termination.
- the sending end sends an upgrade request message to the receiving module 10, and is configured to request the NFV0 to upgrade the first software version corresponding to the first VNF in the NS to the second software version, where the first software version corresponds to the first VNF.
- the second software version corresponds to the second VNF instance.
- the first VNF may be a VNF or a plurality of VNFs, which is not limited by the embodiment of the present invention. If there are multiple first VNFs, you only need to repeat the following process when upgrading the software version of each VNF. Moreover, the process of upgrading the first software version corresponding to the first VNF to the second software version is actually a process of obtaining the second VNF instance corresponding to the second software version.
- the instantiation module 21 After receiving the upgrade request message, the instantiation module 21 verifies the validity of the upgrade request message (NFV0 has its own verification mechanism); when the upgrade request message is valid, The instantiation module 21 reads the VNFD of the second software version of the preset first VNF from the VNF directory, and instantiates the first VNF according to the VNFD of the second software version to obtain a second VNF instance.
- the function of the VNFD preset in the VNF directory is mainly to describe the hardware resource requirements of the software corresponding to the second software version of the first VNF, so that the software corresponding to the second software version can match the hardware resources. , enabling the second software version in the first VNF to run to become the second VNF instance. That is, the first VNF instance is a pre-upgrade VNF instance (an old version of the VNF instance), and the second VNF instance is an upgraded VNF instance (a new version of the VNF instance).
- VNF instances are connected to one or more NSs through virtual links.
- the connection module 22 connects the second VNF instance to the NS where the first VNF instance is located.
- the configuration module 23 configures a forwarding path of the service flow in the NS, so that the first service flow transmitted from one or more senders can be forwarded to the first VNF instance for processing, and the second service flow can be forwarded to
- the second VNF instance is processed (the first service flow is the old service flow previously processed by the first VNF instance, and the second service flow is the new service flow), that is, the first VNF instance and the second VNF. Instances can run in parallel, but the business flows processed are not the same.
- the configuration module 23 configures the forwarding path of the service flow in the NS, which may be a service flow forwarding policy preset by the NFV0, or may be a parameter related to the service flow forwarding path, that is, the related parameters may be indirectly learned.
- the forwarding path of the service flow is not limited in the form of the forwarding path in the embodiment of the present invention.
- the determining termination module 24 determines the first service of the sender. After the flow has been processed, the first VNF instance is terminated, and the new service flow (second traffic flow) is forwarded to the second VNF instance for processing, thereby completing the soft handover of the old and new service flows, and does not cause the old service. The interruption of the flow.
- the determining termination module 24 may further determine that all the first VNF instances belonging to the same VNFFG in the NS are in no-load operation during a certain preset time period. Terminate all first VNF instances in the VNFFG.
- the network function virtualization orchestrator receives, by the receiving module, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the instantiation module is preset according to the preset
- the second software version of the VNFD in the VNF directory instantiates the first VNF to obtain the second VNF instance, and the connection module connects the second VNF instance to the first
- the configuration module configures the forwarding path of the service flow in the NS, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing.
- the first VNF instance and the second VNF instance may be processed in parallel to process different service flows.
- the termination module determines that the first VNF instance runs in a preset time
- the first VNF instance is terminated, thereby completing the first VNF instance and
- the seamless switching between the second VNF instances avoids the interruption of the running of the old version of the VNF instance during the VNF upgrade process, and satisfies the real-time requirements of the service flow.
- FIG. 6 is a schematic structural diagram of Embodiment 3 of a network function virtualization orchestrator provided by the present invention.
- the embodiment relates to a specific process in which the instantiation module 21 obtains the second VNF instance.
- the foregoing instantiation module 21 includes: a determining sending unit 211, a determining obtaining unit 212, and a first instantifying unit 213.
- the determining sending unit 211 is configured to determine at least one part of the first VNF instance.
- An NS, and the identifier of the first NS is sent to the sending end, where the first NS includes at least one virtual network function forwarding map VNFFG, and the first VNFFG of the VNFFG includes the first VNF
- the first NS corresponds to the first network service description NSD
- the determining obtaining unit 212 is configured to obtain the NS directory according to the identifier of the second NS in the NS instance update request sent by the sending end that is received by the receiving module 20
- the second NSD is preset, and the first VNF is determined according to the second NSD.
- the second NS is the to-be-updated by the sending end according to the identifier of the first NS.
- the first NS, the second NSD is a modified first NSD; the first instantiation unit 213 is configured to: according to the second software version of the first VNF preset in the VNF directory The VNFD instantiates the first VNF to obtain the second VNF instance.
- the receiving module 20 is further configured to receive the NS instance update request sent by the sending end, where the NS instance update request includes at least one The identity of the second NS.
- the instantiation module 21 verifies the validity of the upgrade request message.
- the determining sending unit 21 1 determines the first VNF.
- the first NS of the first VNF instance corresponding to the first software version may be one, or may be multiple; and the first NS includes at least one VNFFG, and the first VNFFG of the VNFFG includes the first VNF.
- the first NS corresponds to the first NSD, and the role of the first NSD is mainly to describe how many VNFFGs in the first NS, how many VNF instances are included in each VNFFG, and the connection relationship between the VNF instances.
- the identifier of the first NS is sent to the sending end, so that the sending end determines, from the identifiers of the first NSs, which first NS to update, that is, the second NS mentioned in the following embodiment, where the second NS is sent.
- the first NS to be updated determined by the terminal.
- the sender sends the determined identifier of the second NS in the NS instance update request to the receiving module 20, where the NS instance update request includes the identifier of the at least one second NS.
- the receiving module 20 determines that the obtaining unit 212 obtains the preset second NSD from the NS directory according to the identifier of the second NS, where the second NSD is the modified first NSD, that is, Said that the role of the second NSD is mainly to describe the NS to update the first NS, for example:
- the second NSD describes how many VNFFGs to be included in the first NS update, how many VNF instances, and each VNF The example is how to connect to the NS.
- the obtaining unit 212 After obtaining the second NSD in the NS directory, the obtaining unit 212 checks in the second NS which VNF instance corresponding to the software version of the VNF is already existing according to the specific description of the second NSD, and which VNF software version exists. The corresponding VNF instance does not exist, that is, the obtaining unit 212 can learn which VNF to be instantiated according to the second NSD, thereby implementing the software version upgrade process of the VNF.
- the first VNF instance corresponding to the first software version of the first VNF in the second NS is already existing, but the VNF instance corresponding to the second software version of the first VNF does not exist, so the determining obtaining unit 212 determines to be the first The VNF instance is instantiated.
- the first instantiation unit 213 may obtain a VNFD of the second software version of the preset first VNF from the VNF directory, and instantiate the first VNF according to the VNFD of the second software version to obtain a second VNF instance.
- the second NSD preset in the NS directory can be obtained by modifying the process of the NSD (the process of modifying the NSD can be referred to the prior art), and modifying the first NSD may be sent by the receiving module 20 to the sending end.
- the NS instance update request is executed by the instantiation module 21 before or after the request, and is pre-stored in the NS directory; the VNFD of the second software version of the first VNF preset in the VNF directory can be obtained through the VNF loading process (VNF)
- VNF VNF
- the loading process can be referred to the prior art, and the process of loading the VNF is actually a process of loading the second VNFD into the VNF directory, and the process of loading the VNF may also be that the receiving module 20 receives the NS instance update request sent by the sending end. Executed by instantiation module 21 before or after.
- the network function virtualization orchestrator receives, by the receiving module, an upgrade request sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version.
- the instantiating module obtains the second VNF instance by instantiating the first VNF according to the VNFD of the second software version preset in the VNF directory, and the connecting module connects the second VNF instance to the NS where the first VNF instance is located.
- the configuration module configures the forwarding path of the service flow in the NS, the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF is processed.
- FIG. 7 is a schematic structural diagram of Embodiment 4 of a network function virtualization orchestrator provided by the present invention. On the basis of the foregoing embodiment 2, this embodiment relates to another specific process in which the instantiation module 21 obtains the second VNF instance.
- the foregoing instantiation module 21 specifically includes: a check obtaining unit 214, configured to check whether the first VNF instance exists; if yes, obtain a second software version of the first VNF preset in the VNF directory The VNFD; the second instantiation unit 215 is configured to instantiate the first VNF according to the VNFD of the second software version of the first VNF, to obtain the second VNF instance.
- the instantiation module 21 verifies the validity of the upgrade request message; when the upgrade request message is valid, the check obtaining unit 214 checks the first in the NS. Whether the VNF instance exists. When the first VNF instance exists, the check obtaining unit 214 returns a consent upgrade response to the sender, and acquires the VNFD of the second software version of the first VNF preset in the VNF directory, so that the second instantiation unit 215 is configured according to the first A VNFD of a second software version of the VNF instantiates the first VNF to obtain a second VNF instance.
- VNFD of the second software version of the first VNF preset in the VNF directory can be obtained through the VNF loading process (the VNF loading process can be referred to the prior art), and the process of loading the VNF is actually loading the second VNFD.
- the process to the VNF directory, and the process of loading the VNF may also be performed by the instantiation module 21 before or after the receiving module 20 receives the NS instance update request sent by the sender.
- the network function virtualization orchestrator provided by the embodiment of the present invention receives, by the receiving module, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the instantiation module is preset according to the preset
- the second software version of the VNFD in the VNF directory is for the first VNF
- the second VNF instance is obtained by instantiating, and the connection module connects the second VNF instance to the NS where the first VNF instance is located; after that, the configuration module configures the forwarding path of the service flow in the NS, so that the first service flow is forwarded.
- the second VNF instance is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can process different service flows in parallel; determining that the termination module determines that the first VNF instance is When the vacant operation is performed for a preset period of time, the first VNF instance is terminated, and the seamless switching between the first VNF instance and the second VNF instance is completed, so that the VNF instance of the old version is interrupted during the VNF upgrade process, and the service is satisfied.
- the real-time requirements of the flow is provided.
- connection module 22 connects the second VNF instance to the NS, and the process of the configuration module 23 configuring the forwarding path of the service flow in the NS is different. of. The following are introduced separately.
- the embodiment relates to a specific process in which the connection module 22 connects the obtained second VNF instance to the NS and the configuration module 23 configures the forwarding path of the service flow in the NS. Specifically:
- the second VNF instance is connected to the second NS, and the updated second NS is obtained.
- the updated second NS includes the first VNFFG and the second.
- VNFFG, the second VNFFG includes a second VNF instance, and a connection manner of the second VNF instance in the second VNFFG with other VNF instances in the second VNFFG and the first VNF instance are in the first
- the VNFFG is connected to the other VNF instances in the first VNFFG in the same manner, that is, a new VNFFG is added to the second NS, and becomes the updated second NS. For example: As shown in FIG.
- the updated The second NS includes two VNFFGs, which are a first VNFFG and a second VNFFG (the first VNFFG is the original VNFFG in the second NS, and the second VNFFG is a newly added VNFFG including the second VNF instance); wherein, the first VNFFG includes five VNF instances of VNF1, VNF2, VNF3, VNFx and VNF4, and VNFx represents the first VNF instance, and the second VNFFG includes five VNF instances of VNFK VNF2, VNF3, VNFy, VNF4, and VNFy represents the second VNF.
- VNFFGs which are a first VNFFG and a second VNFFG (the first VNFFG is the original VNFFG in the second NS, and the second VNFFG is a newly added VNFFG including the second VNF instance); wherein, the first VNFFG includes five VNF instances of VNF1, VNF2, VNF3, VNFx and VNF4, and VNFx represents the first VNF instance, and the second VNFFG includes
- VNFx is connected in a cascade manner with VNF1, VNF2, VNF3 and VNF4, and in the second VNFFG, VNFy is also connected in cascade with VNF 1, VNF2, VNF3 and VNF4. .
- VNFy is also connected in cascade with VNF 1, VNF2, VNF3 and VNF4.
- the updated second NS includes two VNFFGs, which are a first VNFFG and a second VNFFG (the first VNFFG is the second The original VNFFG in the NS, the second VNFFG is a new VNFFG including the second VNF instance); wherein the first VNFFG includes VNFxl, VNF2x, VNF3x, VNF4x, VNF5x 5 VNF instances, and VNFx l , VNF2x , VNF3x VNF4x, VNF5x are the first VNF instances, and the second VNFFG includes VNF1 y, VNF2y, VNF3y, VNF4y, VNF5y 5 VNF instances, and VNFly, VNF2y, VNF3y, VNF4y, VNF5y represent the second VNF instance, that is, The example of FIG.
- VNF 4 is to upgrade the software version of all the VNFs included in the second NS to obtain a VNF instance of the new software version.
- VNFxl, VNF2x, VNF3x, VNF4x and VNF5x are connected in a cascade manner
- VNFl y , VNF2y , VNF3y , VNF4y and VNF5y are also connected in a cascade manner.
- the configuration module 23 can configure the forwarding path of the service flow in the NS in two ways, namely:
- the first type the configuration module 23 configures the first VNFFG and the second VNFFG as the forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG for processing. .
- the second type the configuration module 23 instructs the NS service management entity to configure the first VNFFG and the second VNFFG as the forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service is performed. The flow is forwarded to the second VNFFG for processing.
- the forwarding path can be implemented in a variety of ways, for example: Using policy-based routing, the service flow is required to be forwarded according to the source address, so that the traffic from the new source address is forwarded. To the new VNFFG; or, using tunneling technology, to distinguish the forwarding path of new and old data streams through tunnel configuration; or use the SFC mechanism defined in the IETF or other service chain mechanism.
- the configuration module 23 configures the forwarding path of the service flow in the NS
- the first service flow is forwarded to the first VNF instance
- the second service flow is forwarded to the second VNF instance.
- the judgment termination module 24 determines whether the first VNF instance is running at no load for a preset period of time, and if so, terminates the first VNF instance in time.
- the determining termination module 24 can also obtain the running status of the first VNF instance monitored by the NS service management entity, that is, the running status of the VNF instance is monitored by the NS service management entity, and the NS service management entity monitors the The operation status of a VNF instance is notified to the judgment termination module 24; if the first VNF instance runs idly within a preset time, the judgment termination module 24 instructs the NS management entity to terminate the first VNF instance.
- the determining termination module 24 instructs the NS service management entity to monitor the running status of the first VNF instance, and instructs the NS service management entity to terminate the first VNF when it detects that the first VNF instance runs idle within a preset time.
- the NS service management entity directly terminates the first VNF instance, and the NS service management entity directly terminates the first VNF instance, as long as the NS service management entity detects that the first VNF instance is running idle for a preset time.
- the operational state of the monitored first VNF instance is not sent to the decision termination module 24.
- the embodiment relates to another specific process in which the connection module 22 connects the obtained second VNF instance to the NS and the configuration module 23 configures the forwarding path of the service flow in the NS. Specifically:
- the connection module 22 connects the second VNF instance obtained by the instantiation module 21 to the NS in which the first VNF instance is located, and the connection manner of the second VNF instance with other VNF instances in the NS, and the first VNF instance and the Other VNF instances in NS are connected in the same way.
- the second VNF instance is connected to the NS as an extension of the first VNF instance.
- the configuration module 23 configures the forwarding path of the service flow in the NS. Specifically, there are four implementation modes:
- the first type the configuration module 23 configures the first VNF instance and the second VNF instance to the service flow, and generates a service flow forwarding table as a node in the forwarding path of the service flow in the NS;
- the flow forwarding table is configured to be sent to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table, and forwards the second service flow to the second VNF instance, where The three VNF instances are adjacent to the first VNF instance and the second VNF instance, respectively.
- the second configuration instructs the NS service management entity to configure the first VNF instance and the second VNF instance to be sent to the service flow as a node in the forwarding path of the service flow in the NS, and generate a service flow forwarding table.
- the module 23 configures the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the service flow forwarding table, and forwards the second service flow to the second VNF instance. Processing; wherein, the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the third type the configuration module 23 sets the weight value of the first virtual link between the first VNF instance and the third VNF instance, and the right of the second virtual link between the second VNF instance and the third VNF instance.
- the value of the value is configured to be sent to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link, and The second service flow is forwarded to the second VNF instance processing; where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the fourth type the configuration module 23 instructs the NS service management entity to assign a weight value of the first virtual link between the first VNF instance and the third VNF instance, and a second between the second VNF instance and the third VNF instance.
- the weight value of the virtual link is configured to the third VNF instance, so that the third VNF instance forwards the first service flow to the first VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link. Processing, forwarding the second service flow to the second VNF instance processing; wherein, the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the service flow forwarding table may be a mapping relationship table between different service flows and forwarding nodes, that is, the third VNF instance learns different according to the mapping relationship table between the service flow and the forwarding node.
- the traffic is forwarded to the corresponding node for processing.
- the configuration module 23 may be configured to configure a COST value of the virtual link between the second VNF instance and the third VNF instance, such that the COST value is much smaller than the first The COST value of the virtual link between the VNF instance and the third VNF instance; if the NFV0 or NS service management entity does not know the COST value of the virtual link between the first VNF instance and the third VNF instance, the second The virtual link between the VNF instance and the third VNF instance configures a very low COST value to ensure that it is less than the COST value of the virtual link between the first VNF instance and the third VNF instance. Therefore, the third VNF instance selects a link with a low link COST value according to the configured forwarding path, and the old service flow is still processed by the first VNF instance, and the new service flow is forwarded to the second VNF instance for processing.
- the configuration module 23 configures the forwarding path of the service flow in the NS
- the first service flow is forwarded to the first VNF instance
- the second service flow is forwarded to the second VNF instance.
- the determining termination module 24 determines whether the first VNF instance is running at no load for a preset period of time, and if so, terminating the first VNF instance in time.
- the determining termination module 24 can also obtain the running status of the first VNF instance monitored by the NS service management entity, that is, the running status of the VNF instance is monitored by the NS service management entity, and the NS service management entity monitors the The operating state of a VNF instance is sent to the judgment termination module 24; if the first VNF instance runs idling within a preset time, the judgment termination module 24 instructs the NS management entity to terminate the first VNF instance.
- the determining termination module 24 instructs the NS service management entity to monitor the running status of the first VNF instance, and instructs the NS service management entity to terminate the first VNF when it detects that the first VNF instance runs idle within a preset time.
- the NS service management entity directly terminates the first VNF instance, and the NS service management entity directly terminates the first VNF instance, as long as the NS service management entity detects that the first VNF instance runs in a preset time.
- the operational state of the monitored first VNF instance is not sent to the decision termination module 24.
- the network function virtualization orchestrator receives, by the receiving module, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the instantiation module is preset according to the preset
- the VNFD of the second software version in the VNF directory instantiates the first VNF to obtain the second VNF instance, and the connection module connects the second VNF instance to the NS where the first VNF instance is located; Flowing in the forwarding path in the NS, the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can be parallelized.
- the termination module determines that the first VNF instance runs in a preset time, and terminates the first VNF instance, thereby completing seamless handover between the first VNF instance and the second VNF instance, avoiding the VNF
- the old version of the VNF instance is interrupted, which meets the real-time requirements of the service flow.
- FIG. 8 is a schematic structural diagram of Embodiment 5 of a network function virtualization orchestrator provided by the present invention.
- the network function virtualization orchestrator may further include: an adding module 25, configured to add the second VNF instance to the NFV after the configuration module 23 configures the service flow forwarding path in the NS An instance library; a resource scaling module 26, configured to start a VNF resource scaling process to perform resource scaling processing on the first VNF instance and the second VNF instance; and a deleting module 27, configured to terminate the After the first VNF instance, the first VNF instance in the NFV instance library is deleted.
- the adding module 25, the resource scaling module 26, and the deleting module 27 may all be located in the embodiment shown in FIG. 5, or may be located in the embodiment shown in FIG. 6, or may be the one shown in FIG. In the embodiment, FIG. 8 is only taken as an example in which the adding module 25, the resource scaling module 26, and the deleting module 27 are located in the embodiment shown in FIG. 5.
- the configuration module 23 configures the service flow forwarding path in the NS, so that the first service flow is forwarded to the first VNF instance, and after the second service flow is forwarded to the second VNF instance, the module is added. 25 Add the second VNF instance to the NFV instance library. At this time, the second VNF instance and the first VNF instance are working at the same time, but the load of the second VNF instance is increased, and the load of the first VNF instance is gradually reduced. To ensure effective utilization of resources, the resource scaling module 26 can start resource scaling. The process reduces the resources used by the first VNF instance and increases the resources used by the second VNF instance to ensure effective and rational use of the resources.
- the deleting module 27 deletes the entry of the first VNF instance in the NFV instance library to ensure the accuracy of the NFV instance library content.
- the network function virtualization orchestrator receives, by the receiving module, an upgrade request message sent by the sending end for requesting to upgrade the first software version of the first VNF to the second software version, and the instantiation module is preset according to the preset
- the VNFD of the second software version in the VNF directory instantiates the first VNF to obtain the second VNF instance, and the connection module connects the second VNF instance to the NS where the first VNF instance is located; Flowing in the forwarding path in the NS, the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing, so that the first VNF instance and the second VNF instance can be parallelized.
- the termination module determines that the first VNF instance runs in a preset time, and terminates the first VNF instance, thereby completing seamless handover between the first VNF instance and the second VNF instance, avoiding the VNF
- the VNF instance of the old version is interrupted, which meets the real-time requirements of the service flow.
- the shrinking module 26 performs resource expansion processing on the first VNF instance and the second VNF instance to ensure reasonable utilization of resources.
- FIG. 9 is a flowchart of Embodiment 1 of a method for upgrading a virtual network function according to the present invention.
- the executor of the method may be NFV0 in the above embodiment. As shown in Figure 9, the method includes:
- the NFV0 receives the upgrade request message sent by the sending end, where the upgrade request message is used to request the NFV0 to upgrade the first software version corresponding to the first VNF to the second software version, where the first software version corresponds to the first VNF instance.
- the second software version corresponds to the second VNF instance.
- the NFV0 instantiates the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the second VNF instance.
- S103 NFV0 connects the second VNF instance to the NS where the first VNF instance is located.
- S104 NFV0 configures a forwarding path of the service flow in the NS, so that the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing.
- S105 The NFVO determines that the first VNF instance runs idling within a preset time, and the NFV0 terminates the first VNF instance.
- FIG. 10 is a flowchart of Embodiment 2 of a method for upgrading a virtual network function according to the present invention.
- the executor of the method may be the NFV0 in the above embodiment, and the embodiment relates to a feasible implementation manner in which the NFV0 obtains the second VNF instance. That is, the above S 102 specifically includes:
- NFV0 determines at least one first NS to which the first VNF instance belongs, and sends the identifier of the first NS to the sending end, where the first NS includes at least one VNFFG, and the first VNFFG in the VNFFG includes The first VNF instance.
- the NFV0 receives the NS instance update request sent by the sending end, where the NS instance update request includes the identifier of the at least one second NS, and the second NS is the first to be updated that is determined by the sending end according to the identifier of the first NS. NS ; wherein the first NS corresponds to the first NSD.
- NFVO acquires a second NSD preset in the NS directory according to the identifier of the second NS, and determines to instantiate the first VNF according to the second NSD; wherein the second NSD is modified The first NSD.
- the NFVO instantiates the first VNF according to the VNFD of the second software version of the first VNF preset in the VNF directory, to obtain the second VNF instance.
- the foregoing S103 may be specifically: the NFV0 connects the second VNF instance to the second NS, and obtains the updated second NS; wherein the updated second NS includes the first VNFFG And the second VNFFG, the second VNFFG includes the second VNF instance, and the second VNF instance is connected to the other VNF instances in the second VNFFG in the second VNFFG, and The first VNF instance is connected in the first VNFFG in the same manner as the other VNF instances in the first VNFFG.
- S 104 may specifically have two implementation manners, specifically:
- NFV0 configures the first VNFFG and the second VNFFG to the service flow And being a forwarding path of the service flow, so that the first service flow is forwarded to the first VNFFG for processing, and the second service flow is forwarded to the second VNFFG process.
- the second type: NFV0 instructs the NS service management entity to configure the first VNFFG and the second VNFFG to the service flow as a forwarding path of the service flow, so that the first service flow is forwarded to the first A VNFFG performs processing, and the second service flow is forwarded to the second VNFFG for processing.
- the foregoing S105 may be specifically: the NFV0 acquires an operation state of the first VNF instance that is monitored by the NS service management entity, and when the first VNF instance runs in no-load for the preset time, the NS management entity is terminated.
- the first VNF instance optionally, the S105 may further indicate that the NS service management entity monitors an operating state of the first VNF instance, and the first VNF instance is in the preset time When the no-load operation is running, the first VNF instance is terminated.
- FIG. 1 is a flowchart of Embodiment 3 of a method for upgrading a virtual network function according to the present invention.
- the executor of the method may be NFV0 in the above embodiment, and the embodiment relates to another feasible implementation manner in which the NFV0 obtains the second VNF instance. That is, the above S102 may specifically include:
- NFV0 checks whether the first VNF instance exists, and if yes, the NFV0 acquires the VNFD of the second software version of the first VNF preset in the VNF directory.
- NFVO instantiates the first according to the VNFD of the second software version of the first VNF.
- the foregoing S103 may be specifically: the NFV0 connects the second VNF instance to the NS where the first VNF instance is located, and the connection manner of the second VNF instance with other VNF instances in the NS, And, the first VNF instance is connected in the same manner as the other VNF instances in the NS.
- S 104 may specifically have four implementation manners, specifically:
- NFV0 configures the first VNF instance and the second VNF instance to the service Generating, as a node in the forwarding path of the service flow in the NS, generating a service flow forwarding table; and configuring the service flow forwarding table to the third VNF instance, so that the third VNF instance is according to the service
- the flow forwarding table forwards the first service flow to the first VNF instance for processing, and forwards the second service flow to the second VNF instance process, where the third VNF instance and the first A VNF instance is adjacent to the second VNF instance.
- the second type NFV0, the weight value of the first virtual link between the first VNF instance and the third VNF instance, and the second virtual between the second VNF instance and the third VNF instance
- the weight value of the link is configured to the third VNF instance, so that the third VNF instance sends the first service according to the weight value of the first virtual link and the weight value of the second virtual link. Forwarding to the first VNF instance for processing, forwarding the second service flow to the second VNF instance processing, where the third VNF instance is respectively associated with the first VNF instance and the second VNF instances are adjacent.
- the NFV0 indicates that the NS service management entity configures the first VNF instance and the second VNF instance to the service flow, and generates a service as a node in the forwarding path of the service flow in the NS. a flow forwarding table, and instructing the NS service management entity to configure the service flow forwarding table to the third VNF instance, so that the third VNF instance forwards the first service flow to the server according to the service flow forwarding table.
- the first VNF instance is processed, and the second VNF instance is forwarded to the second VNF instance, where the third VNF instance is adjacent to the first VNF instance and the second VNF instance, respectively.
- the fourth type NFV0, the NS service management entity, the weight value of the first virtual link between the first VNF instance and the third VNF instance, and the second VNF instance and the third VNF instance
- the weight value of the second virtual link is configured to the third VNF instance, so that the third VNF instance according to the weight value of the first virtual link and the weight value of the second virtual link
- the first service flow is forwarded to the first VNF instance for processing, and the second service flow is forwarded to the second VNF instance for processing; wherein the third VNF instance is respectively associated with the first VNF instance Adjacent to the second VNF instance.
- the foregoing S105 may be specifically: the NFV0 acquires an operation state of the first VNF instance that is monitored by the NS service management entity, and when the first VNF instance runs in no-load for the preset time, the NS management entity is terminated.
- the first VNF instance optionally, the S105 may further indicate that the NS service management entity monitors an operating state of the first VNF instance, and the first VNF instance is in the preset time When the no-load operation is running, the first VNF instance is terminated.
- FIG. 12 is a flowchart of Embodiment 4 of a method for upgrading a virtual network function according to the present invention.
- the method involved in this embodiment is a process in which NFV0 performs resource scaling processing on the second VNF instance and the first VNF instance.
- the method further includes: S401: NFV0 adds the second VNF instance to the NFV instance library.
- the NFV0 starts the VNF resource scaling process to perform resource scaling processing on the first VNF instance and the second VNF instance.
- the method further includes:
- NFV0 deletes the first VNF instance in the NFV instance library.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14880848.8A EP3094049B1 (en) | 2014-01-29 | 2014-01-29 | Method for upgrading virtualized network function and network function virtualization orchestrator |
PCT/CN2014/071806 WO2015113278A1 (zh) | 2014-01-29 | 2014-01-29 | 虚拟网络功能的升级方法和网络功能虚拟化编排器 |
CN201480001637.0A CN105379191B (zh) | 2014-01-29 | 2014-01-29 | 虚拟网络功能的升级方法和网络功能虚拟化编排器 |
KR1020167023320A KR101979362B1 (ko) | 2014-01-29 | 2014-01-29 | 가상화된 네트워크 기능을 업그레이드하는 방법 및 네트워크 기능 가상화 오케스트레이터 |
US15/222,270 US10177982B2 (en) | 2014-01-29 | 2016-07-28 | Method for upgrading virtualized network function and network function virtualization orchestrator |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2014/071806 WO2015113278A1 (zh) | 2014-01-29 | 2014-01-29 | 虚拟网络功能的升级方法和网络功能虚拟化编排器 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/222,270 Continuation US10177982B2 (en) | 2014-01-29 | 2016-07-28 | Method for upgrading virtualized network function and network function virtualization orchestrator |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015113278A1 true WO2015113278A1 (zh) | 2015-08-06 |
Family
ID=53756171
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/071806 WO2015113278A1 (zh) | 2014-01-29 | 2014-01-29 | 虚拟网络功能的升级方法和网络功能虚拟化编排器 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10177982B2 (zh) |
EP (1) | EP3094049B1 (zh) |
KR (1) | KR101979362B1 (zh) |
CN (1) | CN105379191B (zh) |
WO (1) | WO2015113278A1 (zh) |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016165470A1 (zh) * | 2015-08-27 | 2016-10-20 | 中兴通讯股份有限公司 | Vnf实例的处理方法、装置及vnfm |
CN106304144A (zh) * | 2015-06-23 | 2017-01-04 | 中兴通讯股份有限公司 | 虚拟化核心网关开局方法、装置和系统 |
CN106385330A (zh) * | 2016-09-07 | 2017-02-08 | 中国联合网络通信集团有限公司 | 一种网络功能虚拟化编排器的实现方法及装置 |
WO2017035395A1 (en) * | 2015-08-25 | 2017-03-02 | Huawei Technologies Co., Ltd. | System and method for network function virtualization resource management |
WO2017058251A1 (en) | 2015-10-02 | 2017-04-06 | Nokia Solutions And Networks Oy | Managing the graceful termination of a virtualized network function instance |
WO2017121153A1 (zh) * | 2016-01-15 | 2017-07-20 | 中兴通讯股份有限公司 | 软件升级方法及装置 |
GB2549574A (en) * | 2016-03-21 | 2017-10-25 | Ibm | Replacing a virtual network function in a network service |
CN107357603A (zh) * | 2016-05-10 | 2017-11-17 | 华为技术有限公司 | 一种软件加载方法、设备及系统 |
CN107431651A (zh) * | 2015-12-30 | 2017-12-01 | 华为技术有限公司 | 一种网络服务的生命周期管理方法及设备 |
CN107431637A (zh) * | 2015-08-31 | 2017-12-01 | 华为技术有限公司 | 一种网络服务的部署方法及装置 |
WO2018072503A1 (zh) * | 2016-10-18 | 2018-04-26 | 华为技术有限公司 | 软件修改的发起方法、发布元数据的方法及装置 |
EP3337095A4 (en) * | 2015-08-31 | 2018-06-20 | Huawei Technologies Co., Ltd. | Resource management method and device |
CN109391482A (zh) * | 2017-08-02 | 2019-02-26 | 华为技术有限公司 | 网络功能的升级方法及升级管理实体 |
CN109474522A (zh) * | 2017-09-07 | 2019-03-15 | 华为技术有限公司 | 业务路由的方法、装置及存储介质 |
EP3447965A4 (en) * | 2016-05-06 | 2019-04-03 | Huawei Technologies Co., Ltd. | METHOD FOR MANAGING NETWORK FUNCTIONAL INSTRUMENTS AND ASSOCIATED DEVICE |
CN110447205A (zh) * | 2017-03-14 | 2019-11-12 | 英特尔Ip公司 | 用于实例化并连接无线电接入网络虚拟化网络功能和核心网络虚拟化网络功能的方法和系统 |
WO2022063127A1 (zh) * | 2020-09-22 | 2022-03-31 | 中兴通讯股份有限公司 | 虚拟化网络服务的更新方法、电子设备、计算机可读存储介质 |
US11316758B2 (en) * | 2016-08-18 | 2022-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Network service design and deployment process for NFV systems |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10700946B2 (en) * | 2017-08-08 | 2020-06-30 | Amdocs Development Limited | System, method, and computer program for automatically certifying a virtual network function (VNF) for use in a network function virtualization (NFV) based communication network |
CN105284094B (zh) * | 2014-05-15 | 2019-05-28 | 华为技术有限公司 | 一种网络功能虚拟化网络系统、数据处理方法及装置 |
US9979602B1 (en) * | 2014-08-25 | 2018-05-22 | Cisco Technology, Inc. | Network function virtualization infrastructure pod in a network environment |
WO2016117694A1 (ja) * | 2015-01-23 | 2016-07-28 | 日本電気株式会社 | ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム |
EP3255839B1 (en) * | 2015-02-03 | 2024-04-24 | Nec Corporation | Virtual network system, virtual network control method, virtual network function database, integrated control device, control device, and control method and control program therefor |
JP6772751B2 (ja) * | 2016-10-14 | 2020-10-21 | 富士通株式会社 | 設定方法及びサーバ装置 |
US10469359B2 (en) * | 2016-11-03 | 2019-11-05 | Futurewei Technologies, Inc. | Global resource orchestration system for network function virtualization |
EP3596886A1 (en) * | 2017-03-14 | 2020-01-22 | Intel IP Corporation | Instantiation of a virtual network function (vnf) as part of a gnodeb (gnb) |
CN110546980A (zh) * | 2017-04-25 | 2019-12-06 | 英特尔Ip公司 | 虚拟化无线电接入网络中的集中式单元和分布式单元连接 |
FI3616467T3 (fi) * | 2017-04-25 | 2023-03-22 | Apple Inc | GNB:n hallinta verkkotoimintojen virtualisointikehyksessä |
JP6714541B2 (ja) * | 2017-05-19 | 2020-06-24 | 日本電信電話株式会社 | 管理装置、および、ネットワークサービス管理方法 |
EP3639474B1 (en) * | 2017-06-16 | 2022-08-31 | Telefonaktiebolaget LM Ericsson (publ) | Derivation of network service descriptor from network service requirements |
WO2019027827A1 (en) * | 2017-08-01 | 2019-02-07 | Intel IP Corporation | TECHNIQUES ASSOCIATED WITH AN INTERFACE BETWEEN A NEXT GENERATION NODE B CENTRAL UNIT AND A DISTRIBUTED NODE OF NEXT GENERATION B |
CN109391982B (zh) * | 2017-08-10 | 2022-06-07 | 中国移动通信有限公司研究院 | 信息包生成方法及编排管理方法、网元及存储介质 |
CN109639449B (zh) * | 2017-10-09 | 2021-09-03 | 中兴通讯股份有限公司 | 虚拟化流镜像策略自动化管理的方法、设备及介质 |
MX2020003447A (es) * | 2017-10-17 | 2020-07-29 | Ericsson Telefon Ab L M | Registro de servicios en una red de comunicaciones. |
CN107769976B (zh) * | 2017-10-31 | 2020-06-26 | 电子科技大学 | 一种基于传输带宽优化的服务功能链映射方法 |
CN112202673B (zh) * | 2017-11-21 | 2022-01-04 | 华为技术有限公司 | 一种配置方法及装置 |
US10587474B2 (en) * | 2017-11-28 | 2020-03-10 | Cisco Technology, Inc. | Elastic capacity management with a cloud cable modem termination system (cCMTS) |
KR102486236B1 (ko) * | 2017-12-26 | 2023-01-09 | 삼성전자주식회사 | 무선 통신 시스템에서 네트워크 기능 가상화를 위한 장치 및 방법 |
US10896069B2 (en) | 2018-03-16 | 2021-01-19 | Citrix Systems, Inc. | Dynamically provisioning virtual machines from remote, multi-tier pool |
US11382150B2 (en) * | 2018-03-26 | 2022-07-05 | Apple Inc. | System and method of managing PNF connectivity in a network slice instance |
US10979321B2 (en) * | 2018-12-10 | 2021-04-13 | Nec Corporation | Method and system for low-latency management and orchestration of virtualized resources |
WO2020167820A1 (en) * | 2019-02-12 | 2020-08-20 | Apple Inc. | Systems and methods to deploy user plane function (upf) and edge computing virtualized network functions (vnfs) in network functions virtualization (nfv) environment networks |
CN113924549A (zh) | 2019-06-11 | 2022-01-11 | 瑞典爱立信有限公司 | 虚拟网络功能和物理网络功能软件升级 |
US11456989B2 (en) * | 2020-03-20 | 2022-09-27 | Verizon Patent And Licensing Inc. | Systems and methods for virtualized network function (“VNF”) selection in a wireless telecommunications network |
CN114553692A (zh) * | 2020-11-25 | 2022-05-27 | 中兴通讯股份有限公司 | 网络切片升级的方法及装置 |
WO2023147882A1 (en) * | 2022-02-07 | 2023-08-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Version-dependency information for management of a network service |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1659539A (zh) * | 2002-04-19 | 2005-08-24 | 因卡网络工程公司 | 一种具有虚拟服务模块的网络系统 |
US20100290348A1 (en) * | 2009-05-14 | 2010-11-18 | Avaya Inc. | Generation and usage of mobility vlan id version value |
US20120005276A1 (en) * | 2010-06-30 | 2012-01-05 | Guo Katherine H | Method and apparatus for reducing application update traffic in cellular networks |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6658480B2 (en) * | 1997-10-14 | 2003-12-02 | Alacritech, Inc. | Intelligent network interface system and method for accelerated protocol processing |
US7403980B2 (en) * | 2000-11-08 | 2008-07-22 | Sri International | Methods and apparatus for scalable, distributed management of virtual private networks |
US8429639B2 (en) | 2009-02-10 | 2013-04-23 | Microsoft Corporation | Image-based software update |
-
2014
- 2014-01-29 WO PCT/CN2014/071806 patent/WO2015113278A1/zh active Application Filing
- 2014-01-29 EP EP14880848.8A patent/EP3094049B1/en active Active
- 2014-01-29 CN CN201480001637.0A patent/CN105379191B/zh active Active
- 2014-01-29 KR KR1020167023320A patent/KR101979362B1/ko active IP Right Grant
-
2016
- 2016-07-28 US US15/222,270 patent/US10177982B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1659539A (zh) * | 2002-04-19 | 2005-08-24 | 因卡网络工程公司 | 一种具有虚拟服务模块的网络系统 |
US20100290348A1 (en) * | 2009-05-14 | 2010-11-18 | Avaya Inc. | Generation and usage of mobility vlan id version value |
US20120005276A1 (en) * | 2010-06-30 | 2012-01-05 | Guo Katherine H | Method and apparatus for reducing application update traffic in cellular networks |
Cited By (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106304144A (zh) * | 2015-06-23 | 2017-01-04 | 中兴通讯股份有限公司 | 虚拟化核心网关开局方法、装置和系统 |
CN107924383A (zh) * | 2015-08-25 | 2018-04-17 | 华为技术有限公司 | 用于网络功能虚拟化资源管理的系统和方法 |
US11429408B2 (en) | 2015-08-25 | 2022-08-30 | Futurewei Technologies, Inc. | System and method for network function virtualization resource management |
WO2017035395A1 (en) * | 2015-08-25 | 2017-03-02 | Huawei Technologies Co., Ltd. | System and method for network function virtualization resource management |
US10908936B2 (en) | 2015-08-25 | 2021-02-02 | Futurewei Technologies, Inc. | System and method for network function virtualization resource management |
US10223140B2 (en) | 2015-08-25 | 2019-03-05 | Futurewei Technologies, Inc. | System and method for network function virtualization resource management |
WO2016165470A1 (zh) * | 2015-08-27 | 2016-10-20 | 中兴通讯股份有限公司 | Vnf实例的处理方法、装置及vnfm |
CN107431637B (zh) * | 2015-08-31 | 2020-09-11 | 华为技术有限公司 | 一种网络服务的部署方法及装置 |
CN107431637A (zh) * | 2015-08-31 | 2017-12-01 | 华为技术有限公司 | 一种网络服务的部署方法及装置 |
EP3675424A1 (en) * | 2015-08-31 | 2020-07-01 | Huawei Technologies Co., Ltd. | Method and apparatus for deploying network service |
EP3337095A4 (en) * | 2015-08-31 | 2018-06-20 | Huawei Technologies Co., Ltd. | Resource management method and device |
EP3337094A4 (en) * | 2015-08-31 | 2018-06-20 | Huawei Technologies Co., Ltd. | Method and apparatus for deploying network services |
US10523529B2 (en) | 2015-08-31 | 2019-12-31 | Huawei Technologies Co., Ltd. | Method and apparatus for deploying network service |
EP3356919A4 (en) * | 2015-10-02 | 2019-06-26 | Nokia Solutions and Networks Oy | ADMINISTRATION OF THE TERMINAL TERMINATION OF A VIRTUALIZED NETWORK FUNCTION SETTING |
WO2017058251A1 (en) | 2015-10-02 | 2017-04-06 | Nokia Solutions And Networks Oy | Managing the graceful termination of a virtualized network function instance |
US10846128B2 (en) | 2015-10-02 | 2020-11-24 | Nokia Solutions And Networks Oy | Managing the graceful termination of a virtualized network function instance |
US10700947B2 (en) | 2015-12-30 | 2020-06-30 | Huawei Technologies Co., Ltd | Life cycle management method and device for network service |
CN107431651A (zh) * | 2015-12-30 | 2017-12-01 | 华为技术有限公司 | 一种网络服务的生命周期管理方法及设备 |
CN107431651B (zh) * | 2015-12-30 | 2020-07-21 | 华为技术有限公司 | 一种网络服务的生命周期管理方法及设备 |
WO2017121153A1 (zh) * | 2016-01-15 | 2017-07-20 | 中兴通讯股份有限公司 | 软件升级方法及装置 |
US10362122B2 (en) | 2016-03-21 | 2019-07-23 | International Business Machines Corporation | Replacing a virtual network function in a network service |
GB2549574B (en) * | 2016-03-21 | 2019-06-05 | Ibm | Replacing a virtual network function in a network service |
GB2549574A (en) * | 2016-03-21 | 2017-10-25 | Ibm | Replacing a virtual network function in a network service |
US10547696B2 (en) | 2016-03-21 | 2020-01-28 | International Business Machines Corporation | Replacing a virtual network function in a network service |
EP3447965A4 (en) * | 2016-05-06 | 2019-04-03 | Huawei Technologies Co., Ltd. | METHOD FOR MANAGING NETWORK FUNCTIONAL INSTRUMENTS AND ASSOCIATED DEVICE |
US10917294B2 (en) | 2016-05-06 | 2021-02-09 | Huawei Technologies Co., Ltd. | Network function instance management method and related device |
CN107357603A (zh) * | 2016-05-10 | 2017-11-17 | 华为技术有限公司 | 一种软件加载方法、设备及系统 |
US11316758B2 (en) * | 2016-08-18 | 2022-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Network service design and deployment process for NFV systems |
CN106385330B (zh) * | 2016-09-07 | 2019-10-11 | 中国联合网络通信集团有限公司 | 一种网络功能虚拟化编排器的实现方法及装置 |
CN106385330A (zh) * | 2016-09-07 | 2017-02-08 | 中国联合网络通信集团有限公司 | 一种网络功能虚拟化编排器的实现方法及装置 |
US10742502B2 (en) | 2016-10-18 | 2020-08-11 | Huawei Technologies Co., Ltd. | Software modification initiation method, and metadata release method and apparatus |
EP3518465A4 (en) * | 2016-10-18 | 2019-09-25 | Huawei Technologies Co., Ltd. | SOFTWARE MODIFICATION INITIATION METHOD, METADATA PUBLICATION METHOD AND DEVICE |
WO2018072503A1 (zh) * | 2016-10-18 | 2018-04-26 | 华为技术有限公司 | 软件修改的发起方法、发布元数据的方法及装置 |
EP3839726A1 (en) * | 2016-10-18 | 2021-06-23 | Huawei Technologies Co., Ltd. | Software modification initiation method and apparatus |
CN110447205A (zh) * | 2017-03-14 | 2019-11-12 | 英特尔Ip公司 | 用于实例化并连接无线电接入网络虚拟化网络功能和核心网络虚拟化网络功能的方法和系统 |
CN110447205B (zh) * | 2017-03-14 | 2023-01-06 | 苹果公司 | 用于实例化并连接无线电接入网络虚拟化网络功能和核心网络虚拟化网络功能的方法和系统 |
CN109391482B (zh) * | 2017-08-02 | 2021-01-29 | 华为技术有限公司 | 网络功能的升级方法及升级管理实体 |
CN109391482A (zh) * | 2017-08-02 | 2019-02-26 | 华为技术有限公司 | 网络功能的升级方法及升级管理实体 |
CN109474522A (zh) * | 2017-09-07 | 2019-03-15 | 华为技术有限公司 | 业务路由的方法、装置及存储介质 |
WO2022063127A1 (zh) * | 2020-09-22 | 2022-03-31 | 中兴通讯股份有限公司 | 虚拟化网络服务的更新方法、电子设备、计算机可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
KR20160113250A (ko) | 2016-09-28 |
CN105379191B (zh) | 2019-08-06 |
KR101979362B1 (ko) | 2019-08-28 |
EP3094049A1 (en) | 2016-11-16 |
US10177982B2 (en) | 2019-01-08 |
CN105379191A (zh) | 2016-03-02 |
EP3094049A4 (en) | 2016-11-16 |
US20160337172A1 (en) | 2016-11-17 |
EP3094049B1 (en) | 2018-01-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015113278A1 (zh) | 虚拟网络功能的升级方法和网络功能虚拟化编排器 | |
WO2021218397A1 (zh) | 用于实现业务连续性的方法及相关设备 | |
US11941423B2 (en) | Data processing method and related device | |
JP5835846B2 (ja) | ネットワークシステム及び仮想ノードのマイグレーション方法 | |
KR100950840B1 (ko) | 폴리시 결정을 통해 동적 시스템 내의 접속의 처리 및 트래픽 흐름을 개선하는 방법, 시스템, 액세스 네트워크 및 단말 장치 | |
US8671176B1 (en) | Virtual network prototyping environment | |
JP5671022B2 (ja) | 少なくとも1つの仮想ネットワークをオンザフライかつオンデマンドでデプロイする方法及びシステム | |
CN107111509B (zh) | 用于计算机网络中的虚拟机迁移的方法 | |
US20160212237A1 (en) | Management server, communication system and path management method | |
WO2016155394A1 (zh) | 一种虚拟网络功能间链路建立方法及装置 | |
JP6432955B2 (ja) | 仮想ネットワーク機能インスタンスをマイグレーションさせるための方法、装置およびシステム | |
US20160117185A1 (en) | Virtual overlay mobility using label based underlay network forwarding | |
EP3518465B1 (en) | Method and device for initiating software modification | |
WO2017066931A1 (zh) | 网络功能虚拟化架构中证书的管理方法及装置 | |
WO2019214508A1 (zh) | 网络配置方法、设备及系统 | |
JP2019536365A (ja) | ネットワークサービスライフサイクル管理許可方法及び装置 | |
WO2015180154A1 (zh) | 网络控制方法和装置 | |
WO2021093455A1 (zh) | 一种虚拟机接入方法及装置 | |
WO2019238060A1 (zh) | 一种数据传输方法及装置 | |
CN108234215B (zh) | 一种网关的创建方法、装置、计算机设备及存储介质 | |
US10291717B2 (en) | Prioritizing VDI sessions and redirected devices in software defined networks | |
US11095514B2 (en) | System and method for propagating anima network objective changes | |
US10469374B2 (en) | Multiple provider framework for virtual switch data planes and data plane migration | |
WO2014071637A1 (zh) | 一种对虚拟机进行网络配置的方法和设备 | |
JP6275180B2 (ja) | 設定情報生成装置、ネットワーク制御装置、方法、及び、プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14880848 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014880848 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014880848 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20167023320 Country of ref document: KR Kind code of ref document: A |