CN105577409B - Method and device for realizing automatic deployment of virtual network function - Google Patents
Method and device for realizing automatic deployment of virtual network function Download PDFInfo
- Publication number
- CN105577409B CN105577409B CN201410549642.7A CN201410549642A CN105577409B CN 105577409 B CN105577409 B CN 105577409B CN 201410549642 A CN201410549642 A CN 201410549642A CN 105577409 B CN105577409 B CN 105577409B
- Authority
- CN
- China
- Prior art keywords
- node
- software version
- deployment
- available
- vnf software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 10
- 238000009434 installation Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000012216 screening Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a method for realizing automatic deployment of a Virtual Network Function (VNF), which is applied to a first node, wherein the first node is any node of a Network Function Virtualization (NFV) network topology where a VNF software version is to be installed, and the method comprises the following steps: the first node sends a broadcast message for updating the deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed; receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table; determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths; the VNF software version is downloaded through the determined set of available paths. The invention also provides a device for realizing the method for VNF automatic deployment.
Description
Technical Field
The present invention relates to a Virtual Network Function (VNF) installation and deployment technology in a Network Function Virtualization (NFV) Network topology, and in particular, to a method and an apparatus for implementing VNF automatic deployment.
Background
In a conventional telecommunication network system, network functions are implemented by dedicated hardware and network devices, so that an operator has great difficulty in deploying, operating and maintaining the network functions in heterogeneous environments provided by different equipment vendors. Therefore, operators hope to construct a new network architecture to replace closed network with open network, and replace proprietary network with universal network, that is, network functions of originally different proprietary network element devices are extracted and virtualized, and the network functions are operated on a unified universal server platform.
Currently, the European Telecommunications Standardization Institute (ETSI) proposes an NFV network topology architecture. In the NFV Network topology architecture, the separation of Network Functions and Network Function Virtualization Infrastructure (NFVI) is realized by the VNF, so that the decoupling of software and hardware is realized. In the NFV network topology architecture, VNF deployment is required to be implemented. The VNF deployment comprises installation or upgrade of VNF software versions by network elements.
In the NFV network topology architecture, a conventional VNF deployment is generally configured by performing centralized installation and deployment through a single node (note that there may be other single nodes, which is only an example of EMS) of an Element Management System (EMS) as shown in fig. 1. The conventional VNF deployment has the following disadvantages:
1) all VNF software versions are downloaded, installed and deployed in a centralized mode through EMS, so that single-point faults are easy to generate, and deployment failure can be caused when link communication between the EMS and a node of the VNF software version to be installed is abnormal.
2) When a plurality of nodes of the VNF software versions to be installed are deployed in parallel, the VNF software versions are downloaded from the EMS by the nodes at the same time, so that the network of the EMS is congested, the time for realizing the VNF deployment by each node is long, and the risk of deployment failure caused by overtime or overload of the EMS is increased.
3) When a network function is newly built or expanded, manual intervention is needed, a debugging node (namely a network element) foreground needs to be installed first, and then an EMS is accessed to deploy and open a new function, so that the defects of complex deployment and long period exist.
In summary, in the VNF deployment process, the flexibility, the rapidity, the stability, and the reliability of the VNF deployment are seriously affected by the existing manner of centralized installation and deployment through the EMS, so that the requirements of the NFV network topology architecture on the rapidity, the flexibility, the automation, the high performance, and the high reliability of the VNF deployment cannot be met.
Disclosure of Invention
In view of this, embodiments of the present invention are expected to provide a method and an apparatus for implementing VNF automatic deployment, which can meet requirements of an NFV network topology framework on VNF deployment, such as rapidness, flexibility, automation, high performance, and high reliability.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
the embodiment of the invention provides a method for realizing VNF automatic deployment, which is applied to a first node, wherein the first node is any node of a VNF software version to be installed in a NFV network topology, and the method comprises the following steps:
sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths;
the VNF software version is downloaded through the determined set of available paths.
In the foregoing solution, in the process of downloading the VNF software version through the determined available path set, the method further includes:
when all available paths in the determined available path set are interrupted, if the VNF software version is determined to be not downloaded completely through judgment, determining a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
the VNF software version continues to be downloaded through the determined new set of available paths.
In the foregoing solution, in the process of downloading the VNF software version through the determined available path set, the method further includes:
when a third node is newly added in the NFV network topology, the third node is a node which can be used for the first node to realize VNF software version downloading, and if the third node is judged to be unfinished in downloading the VNF software version, a new available path set is determined again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
the VNF software version continues to be downloaded through the determined new set of available paths.
In the above scheme, the method further comprises: when the available path set is not determined according to the updated deployment routing information table, the preset path selection strategy and the VNF software version trust strategy, initiating an available path set arbitration request to a Virtual Network Function Management (VNFM) node;
receiving an available path set fed back by a VNFM node;
the VNF software version is downloaded over the received set of available paths.
In the above scheme, the preset path selection policy includes that the available bandwidth of the second node is greater than a bandwidth threshold, or the available bandwidth of the second node is greater than the bandwidth threshold and the next hop count of the first node and the second node is less than or equal to a hop count threshold; the bandwidth threshold is a minimum bandwidth required by the first node to download the VNF software version.
The embodiment of the invention also provides a device for realizing the automatic deployment of the virtual network function VNF, which is applied to a first node, wherein the first node is any node to be provided with the VNF software version in the network topology of Network Function Virtualization (NFV), and the device comprises a sending unit, a receiving unit, a determining unit and a downloading unit; wherein,
the sending unit is used for sending the broadcast message of the updated deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
the receiving unit is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment path routing information table of the receiving unit, so as to update the deployment path routing information table;
the determining unit is configured to determine an available path set according to the updated deployment routing information table, a preset path selection policy, and a VNF software version trust policy; the set of available paths includes one or more available paths;
and the downloading unit is used for downloading the VNF software version through the determined available path set.
In the above scheme, the apparatus further comprises a first judgment processing unit; wherein,
the first judgment processing unit is configured to, when all available paths in the determined available path set are interrupted, determine, if it is determined that the downloading of the VNF software version is not completed through judgment, determine a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust policy;
correspondingly, the downloading unit is further configured to continue downloading the VNF software version through the new available path set determined by the first determination processing unit.
In the above solution, the apparatus further includes a second judgment processing unit; wherein,
the second judgment processing unit is configured to, when a third node is newly added to the NFV network topology, determine that the VNF software version download is not completed by the third node as a node that can be used for the first node to implement the VNF software version download, and determine a new available path set again according to the deployment route information table updated in real time and the VNF software version trust policy;
accordingly, the downloading unit is further configured to continue downloading the VNF software version through the new available path set determined by the second determination processing unit.
In the foregoing solution, when the determining unit does not determine the available path set according to the updated deployment route information table, the preset path selection policy, and the VNF software version trust policy, the sending unit is further configured to initiate an available path set arbitration request to the virtual network function management VNFM node;
the receiving unit is further configured to receive an available path set fed back by a VNFM node;
and the downloading unit is used for downloading the VNF software version according to the available path set received by the receiving unit.
The method and the device for realizing the automatic VNF deployment are applied to a first node, wherein the first node is any node of a VNF software version to be installed in an NFV network topology; the first node sends a broadcast message for updating a deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed; receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table; determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths; the VNF software version is downloaded through the determined set of available paths. Therefore, the VNF automatic deployment method provided by the embodiment of the invention can meet the requirements of the NFV network topology framework on the VNF deployment, such as rapidness, flexibility, automation, high performance and high reliability.
Drawings
Fig. 1 is a schematic structural diagram of a component structure of an NFV network topology architecture for implementing VNF deployment in the related art;
fig. 2 is a first flowchart illustrating a method for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a component of an NFV network topology architecture for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a second method for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 5 is a third schematic flowchart of a method for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 6 is a fourth flowchart illustrating a method for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 7 is a first schematic structural diagram of a device for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a second configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 9 is a third schematic structural diagram of a device for implementing VNF automatic deployment according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a fourth configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention.
Detailed Description
In the embodiment of the present invention, a first node sends a broadcast message of an updated deployment path routing information table to all second nodes, where the second nodes represent nodes that can provide VNF software versions to be installed in the NFV network topology; receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table; determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths; the VNF software version is downloaded through the determined set of available paths.
Here, the first node is any node to be installed with the VNF software version in the NFV network topology.
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Fig. 2 is a first flowchart of a method for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node of any VNF software version to be installed in an NFV network topology, and as shown in fig. 2, the method for implementing VNF automatic deployment according to an embodiment of the present invention includes:
step S100: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
it should be noted that, in the NFV Network topology shown in fig. 3, before the method for implementing VNF automatic deployment in the embodiment of the present invention is implemented, a Network function virtualization orchestration and management (NFVO) node cooperates with a VNFM node to implement creation of a virtual machine required for VNF deployment, so as to specify a system mechanism that the virtual machine starts the entire NFV Network topology to implement VNF deployment. At this time, when the first node determines that the VNF software version is not installed in itself by judgment, step S100 is performed.
After step S100 is executed, when the second node receives the deployment path route information table updating broadcast message, the deployment path route information is fed back to the first node in time.
Step S101: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
here, the deployment path routing information fed back by the second node includes a topology node number of the second node, software version information that can be provided externally, a remaining bandwidth, a maximum number of users providing an externally downloaded version, a current number of users accessing the user, and the like; the software version information which can be provided externally includes VNF network element type and version number, version file signature, version status, and Cyclic Redundancy Check (CRC) Check of version, etc.
Step S102: determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths;
here, the preset path selection policy includes that the available bandwidth of the second node is greater than a bandwidth threshold, or the available bandwidth of the second node is greater than the bandwidth threshold and the next hop count of the first node and the second node is less than or equal to a hop count threshold, and the like; wherein the bandwidth threshold is a minimum bandwidth required by the first node to download the VNF software version.
Here, the VNF software version trust policy includes one or any combination of a VNF network element type and version number, a version file signature, a version status, and a version CRC check, etc. according to which the first node is deployed in the VNF.
Specifically, when the preset path selection policy includes that the available bandwidth of the second node is greater than the bandwidth threshold, the step S102 of determining the available path set according to the updated deployment routing information table, the preset path selection policy, and the VNF software version trust policy includes:
step 1a, traversing the whole updated deployment routing information table, and screening all second nodes matched with the VNF software version trust strategy;
step 2a, searching the screened residual bandwidth of the second node in the updated deployment routing information table, and determining the available bandwidth of the second node; wherein the available bandwidth of the second node is 50% of the remaining bandwidth.
Step 3a, judging whether a second node meeting a preset path selection strategy exists, namely the second node meeting the condition that the available bandwidth is greater than a bandwidth threshold value, and obtaining a judgment result;
and 4a, when the judgment result shows that second nodes meeting the preset path selection strategy exist, determining links between each second node meeting the preset path selection strategy and the first node as an available path, wherein the combination of the available paths is called an available path set.
Here, it should be noted that, when the determination result is that there is no second node that meets the preset path selection policy, the available path set is not determined; at this time, the first node may further initiate an available path set arbitration request to the VNFM node, so that the VNFM node determines the available path set according to a preset arbitration policy.
Specifically, when the preset path selection policy includes that the available bandwidth of the second node is greater than the bandwidth threshold and the next hop count of the first node and the second node is less than or equal to the hop count threshold, the step S102 of determining the available path set according to the updated deployment routing information table, the preset path selection policy, and the VNF software version trust policy includes:
step 1b, traversing the whole updated deployment routing information table, and screening all second nodes matched with the VNF software version trust strategy;
step 2b, searching the screened next hop count of the second node and the first node in the updated deployment routing information table;
step 3b, searching the screened residual bandwidth of the second node in the updated deployment routing information table, and determining the available bandwidth of the second node; wherein the available bandwidth of the second node is 50% of the remaining bandwidth.
Step 4b, judging whether a second node meeting a preset path selection strategy exists, namely the second node which meets the condition that the available bandwidth is larger than the bandwidth threshold and the next hop count of the first node and the second node is smaller than or equal to the hop count threshold, and obtaining a judgment result;
and 5b, when the judgment result shows that second nodes meeting the preset path selection strategy exist, determining links between each second node meeting the preset path selection strategy and the first node as an available path, wherein the combination of the available paths is called an available path set.
Here, it should be noted that, when the determination result is that there is no second node that meets the preset path selection policy, the available path set is not determined; at this time, the first node may further initiate an available path set arbitration request to the VNFM node, so that the VNFM node determines the available path set according to a preset arbitration policy.
Step S103: the VNF software version is downloaded through the determined set of available paths.
Here, when the available path set includes a plurality of available paths, downloading the VNF software version through the determined available path set includes two ways: 1) respectively downloading different files from a plurality of second nodes corresponding to a plurality of available paths by using the VNF software version to be downloaded as a granularity; 2) and merging and downloading the files in the VNF software version to be downloaded from a plurality of second nodes corresponding to the plurality of available paths. Therefore, multipoint continuous transmission of the VNF software version can be achieved through multiple paths, the downloading time of the VNF software version is reduced, and the VNF deployment efficiency and reliability are improved. Step S104: after the downloading is completed, the downloaded VNF software version is installed.
It should be noted that, in this embodiment of the present invention, before the first node downloads the VNF software version through the determined available path set, the first node sends the determined available path set information to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information tables in real time.
Further, after step S103, since the first node may install the downloaded VNF software version after the downloading of the VNF software version to be deployed is completed. Thus, according to the embodiment of the invention, the first node can complete automatic installation and deployment of the VNF software version. At this time, the first node sends a path information request for increasing the first node to be available to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information tables in real time.
The method flow for implementing VNF automatic deployment according to the embodiment of the present invention is described below by way of example with reference to the NFV network topology and the specific example shown in fig. 2.
Specific example one:
there are two NFVI resource pools in the NFV network topology as shown in fig. 3, including a provincial-centric resource pool and a local-urban resource pool. The provincial center resource pool comprises NFVO, VNFM, EMS, VNF1 and VNF2 network elements, and the local city resource pool comprises VNF 3-VNF 7 nodes. The VNFs 1, 3, and 7 are Mobility Management Entity (MME) network elements, and the VNFs 2, 4, 5, and 6 are Serving General Packet Radio Service (GPRS) Support Node (SGSN) network elements.
In this example one, assume that VNF4 and VNF7 do not have VNF software versions installed, and that the determined set of available paths includes only one available path.
Here, before implementing VNF automatic deployment according to the embodiment of the present invention, it is necessary to implement creation of a virtual machine required for VNF deployment through cooperation between an NFVO node and a VNFM node, so as to specify a system mechanism for implementing VNF deployment by starting a virtual machine on an NFV network topology as shown in fig. 2; after that, the VNFM node starts the virtual machine where the VNF4 is located and which has a function of starting the downloading of the VNF software version, and the VNF4 determines that the VNF software version is not installed, that is, the VNF4 is the first node, that is, the node to which the VNF software version is to be installed.
At this time, the VNF4 implementing VNF automatic deployment includes the following steps:
step A1: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
here, in the NFV network topology shown in fig. 2, the second nodes shown include EMS, VNF1, VNF2, VNF3, VNF5, VNF6, and the like.
Step A2: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table; here, the updated deployment route information table is shown in table 1 below.
TABLE 1
Step A3: the VNF4 determines an available path set according to the updated deployment routing information table (e.g., table 1), the preset path selection policy, and the VNF software version trust policy;
specifically, traversing the whole table 1, screening out all second nodes matched with the VNF network element type and version number SGSNVERA2.0 included in the VNF4 software version trust policy, where the second nodes include EMS and VNF 6; searching the screened next hop numbers of the second node EMS and the second node VNF6 and the first node VNF4 to be 3 and 1 respectively in the table 1; meanwhile, the screened residual bandwidths of the second node EMS and the VNF6 are sequentially searched out in the table 1 to be 800M and 400M; further determining that the available bandwidth of the second node EMS and VNF6 is 800M 50% ═ 400M and 400M 50% ═ 200M; the second node which is determined to meet the preset path selection policy (i.e. the available bandwidth is greater than the bandwidth threshold 200M and the next hops of the first node and the second node are less than or equal to 1) is VNF6, so the link VNF6 → VNF4 is determined as the available path set;
at this time, before the VNF4 downloads the VNF software version through the determined available path set VNF6 → VNF4, the VNF4 sends the determined available path set information to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information table in real time, where the updated deployment path routing information table is shown in table 2 below.
TABLE 2
Step A4: download the VNF software version through the determined VNF6 → VNF 4;
step A5: after the download is completed, the VNF software version is installed.
After step a5, the deployment is completed because the VNF software version of VNF4 has been automatically installed. At this time, the VNF4 sends a path information request for increasing the VNF4 to be available to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information tables in real time, and the updated deployment path routing information tables are shown in table 3 below.
TABLE 3
The following describes, by way of example, a method flow for implementing VNF automatic deployment according to an embodiment of the present invention with reference to the NFV network topology and the specific example shown in fig. 2.
Specific example two:
in this example two, assume that VNF4 and VNF7 do not have VNF software versions installed, and the determined set of available paths includes multiple available paths.
The VNF4 for realizing the automatic VNF deployment comprises the following steps:
step B1: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
here, in the NFV network topology shown in fig. 2, the second nodes shown include EMS, VNF1, VNF2, VNF3, VNF5, VNF6, and the like.
Step B2: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
step B3: the VNF4 determines an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy;
specifically, traversing the whole table 1, screening out all second nodes matched with the VNF network element type and version number SGSNVERA2.0 included in the VNF4 software version trust policy, where the second nodes include EMS and VNF 6; sequentially finding out that the screened residual bandwidths of the EMS and the VNF6 of the second node are 800M and 400M in the table 1; further determining that the available bandwidth of the second node EMS and VNF6 is 800M 50% ═ 400M and 400M 50% ═ 200M; at this time, the available bandwidth allocated to the VNF4 by the available links VNF6 → VNF4 and EMS → VNF4 is 600M in total, and the second nodes determined to meet the preset path selection policy (i.e., the available bandwidth is greater than the bandwidth threshold 500M) are the VNF6 and EMS, so that the two links VNF6 → VNF4 and EMS → VNF4 are determined as the available path set;
at this time, before the VNF4 downloads the VNF software version through the determined available path set VNF6 → VNF4 and EMS → → VNF4, the VNF4 sends the determined available path set information to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information tables in real time.
Step B4: downloading a VNF software version through the determined VNF6 → VNF4 and EMS → VNF 4;
step B5: after the download is completed, the VNF software version is installed.
After step B5, the deployment is completed because the VNF software version of VNF4 has been automatically installed. At this time, the VNF4 sends a path information request for adding the VNF4 to be available to all second nodes in the NFV network topology in real time, so that all second nodes update their own deployment path routing information tables in real time.
In this example two, since the available path set includes a plurality of available paths, the VNF4 downloads the VNF software version through the determined available path set includes the following two ways: 1) downloading different files from the available paths VNF6 → VNF4 and EMS → VNF4 corresponding to the second nodes VNF6 and EMS respectively by taking the VNF software version to be downloaded as the granularity of the files; 2) files in the VNF software version to be downloaded are merged and downloaded from the second nodes VNF6 and EMS corresponding to the available paths VNF6 → VNF4 and EMS → VNF 4. Therefore, multipoint continuous transmission of the VNF software version can be achieved through multiple paths, the downloading time of the VNF software version is reduced, and the VNF deployment efficiency and reliability are improved.
Fig. 4 is a second flowchart of a method for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node of any VNF software version to be installed in an NFV network topology, and as shown in fig. 4, the method for implementing VNF automatic deployment according to an embodiment of the present invention includes:
step S200: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that may provide an installation VNF software version;
step S201: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
step S202: determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths;
step S203: the VNF software version is downloaded through the determined set of available paths. In the embodiment of the present invention, in the process of downloading the VNF software version through the determined available path set in step S203, the method further includes steps S203a to S203 b:
step S203 a: when all available paths in the determined available path set are interrupted, if the VNF software version is determined to be not downloaded completely through judgment, determining a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
here, the determined occurrence of the interruption of the available path set includes a link interruption between the second node and the first node, or a transition of a version status of the second node from an available status to an unavailable status, or the like.
It should be noted that, in the NFV network topology, when there is a change in the version status of the second node, the second node may send its own deployment path routing information to all other nodes in real time; wherein, all other nodes comprise the first node and all other second nodes, so that all other nodes update the deployment path routing information table in real time.
Step S203 b: the VNF software version continues to be downloaded through the determined new set of available paths. The method flow for implementing VNF automatic deployment according to the embodiment of the present invention is described below with reference to the NFV network topology and the specific example three shown in fig. 3.
A specific example is three:
in an example first implementation of the step a4 of downloading the VNF software version via the determined VNF6 → VNF4, when the VNF6 → VNF4 link is interrupted, the method further comprises:
step A4a, if it is determined that the VNF4 does not complete the downloading of the VNF software version, determining to obtain a new available path set EMS → VNF4 again according to the deployment routing information table updated in real time and the trust policy of the VNF software version;
step A4 b: the VNF4 continues to download the VNF software version through the determined new set of available paths EMS → VNF 4.
Thus, in the NFV network topology, when the available path set is interrupted, the method according to the embodiment of the present invention can still implement VNF automatic deployment, thereby improving the reliability and flexibility of VNF deployment.
Fig. 5 is a third schematic flowchart of a method for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node of any VNF software version to be installed in an NFV network topology, and as shown in fig. 5, the method for implementing VNF automatic deployment according to an embodiment of the present invention includes:
step S300: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
step S301: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
step S302: determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths;
step S303: the VNF software version is downloaded through the determined set of available paths.
In the embodiment of the present invention, in the process of downloading the VNF software version through the determined available path set in step S303, the method further includes steps S303a to S303 b:
step S303 a: when a third node is newly added in the NFV network topology, the third node is a node which can be used for the first node to realize VNF software version downloading, and if the third node is judged to be unfinished in downloading the VNF software version, a new available path set is determined again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
it should be noted that, in the NFV network topology, when a third node is newly added to the NFV network topology, the third node also sends the deployment path routing information of itself to all other nodes in real time; and all other nodes comprise the first node and all the second nodes, so that all other nodes update the deployment path routing information table in real time.
Step S303 b: the VNF software version continues to be downloaded through the determined new set of available paths.
The method flow for implementing VNF automatic deployment according to the embodiment of the present invention is described below with reference to the NFV network topology and the specific example four shown in fig. 3.
A specific example is four:
in the process of performing step B4 to download the VNF software version through the determined VNF6 → VNF4 and EMS → VNF4, when a third node VNF8 is newly added to the NFV network topology, the third node VNF8 is a node available for the VNF4 to implement VNF software version download, and the method further includes:
step B4 a: determining that the VNF4 does not complete the downloading of the VNF software version according to judgment, and determining a new available path set { VNF6 → VNF4, EMS → VNF4, VNF8 → VNF4} according to the deployment routing information table updated in real time and the VNF software version trust policy;
step B4B: VNF4 proceeds to download the VNF software version through the determined new set of available paths { VNF6 → VNF4, EMS → VNF4, VNF8 → VNF4 }.
In the fourth example, since the available path set includes a plurality of available paths, the VNF4 downloads the VNF software version through the determined available path set includes the following two ways: 1) respectively downloading different files from second nodes VNF6, EMS and VNF8 corresponding to available path sets { VNF6 → VNF4, EMS → VNF4, VNF8 → VNF4} by taking the VNF software version to be downloaded as the granularity of the files; 2) files in the VNF software version to be downloaded are merged and downloaded from the second nodes VNF6, EMS and VNF8 corresponding to the available paths { VNF6 → VNF4, EMS → VNF4, VNF8 → VNF4 }. Therefore, multipoint continuous transmission of the VNF software version can be achieved through multiple paths, the downloading time of the VNF software version is reduced, and the VNF deployment efficiency and reliability are improved.
Fig. 6 is a fourth flowchart of a method for implementing VNF automatic deployment according to an embodiment of the present invention, where the fourth flowchart is applied to a first node, where the first node is a node of any VNF software version to be installed in an NFV network topology, and as shown in fig. 6, the method for implementing VNF automatic deployment according to an embodiment of the present invention includes:
step S400: sending a broadcast message for updating the deployment path routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
step S401: receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment path routing information table of the second nodes so as to update the deployment path routing information table;
step S402: initiating an available path set arbitration request to the VNFM node when the available path set is not determined according to the updated deployment routing information table, a preset path selection strategy and the VNF software version trust strategy;
here, when the VNFM node receives an available path set arbitration request, the VNFM node determines an available path set according to a preset arbitration policy; upon determining that there is an available path set, feeding back the determined available path set to the first node. Wherein the VNFM node determines an available path set according to a preset arbitration policy, including: the VNFM node decides available download paths based on the VNF software version of the first node and the path IP routing next hop count, among other factors.
Step S403: receiving an available path set fed back by a VNFM node;
step S404: the VNF software version is downloaded over the received set of available paths.
Fig. 7 is a schematic structural diagram of a first configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node to be installed with a VNF software version in an NFV network topology, and as shown in fig. 7, the apparatus includes a sending unit 10, a receiving unit 11, a determining unit 12, and a downloading unit 13; wherein,
the sending unit 10 is configured to send a broadcast message for updating the deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
the receiving unit 11 is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment path routing information table of the receiving unit, so as to update the deployment path routing information table;
the determining unit 12 is configured to determine an available path set according to the updated deployment routing information table, a preset path selection policy, and a VNF software version trust policy; the set of available paths includes one or more available paths;
the downloading unit 13 is configured to download the VNF software version through the determined available path set. Fig. 8 is a schematic structural diagram of a second configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node to be installed with a VNF software version in an NFV network topology, and as shown in fig. 8, the apparatus includes a sending unit 10, a receiving unit 11, a determining unit 12, and a downloading unit 13; the apparatus further includes a first judgment processing unit 131; wherein,
the sending unit 10 is configured to send a broadcast message for updating the deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
the receiving unit 11 is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment path routing information table of the receiving unit, so as to update the deployment path routing information table;
the determining unit 12 is configured to determine an available path set according to the updated deployment routing information table, a preset path selection policy, and a VNF software version trust policy; the set of available paths includes one or more available paths;
the downloading unit 13 is configured to download the VNF software version through the determined available path set;
the first judgment processing unit 131 is configured to, when all available paths in the determined available path set are interrupted, determine, if it is determined that the downloading of the VNF software version is not completed through judgment, determine a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust policy;
accordingly, the downloading unit 13 is further configured to continue downloading the VNF software version through the new available path set determined by the first determination processing unit 131.
Fig. 9 is a schematic structural diagram of a third configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node to be installed with a VNF software version in an NFV network topology, and as shown in fig. 9, the apparatus includes a sending unit 10, a receiving unit 11, a determining unit 12, and a downloading unit 13; the apparatus further includes a second determination processing unit 132; wherein,
the sending unit 10 is configured to send a broadcast message for updating the deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
the receiving unit 11 is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment path routing information table of the receiving unit, so as to update the deployment path routing information table;
the determining unit 12 is configured to determine an available path set according to the updated deployment routing information table, a preset path selection policy, and a VNF software version trust policy; the set of available paths includes one or more available paths;
the downloading unit 13 is configured to download the VNF software version through the determined available path set;
the second determination processing unit 132 is configured to, when a third node is newly added in the NFV network topology, determine that the third node is a node that can be used for the first node to implement downloading of the VNF software version, and determine that the downloading of the VNF software version is not completed after determining that the downloading of the VNF software version is completed, determine a new available path set again according to the deployment route information table updated in real time and the VNF software version trust policy;
accordingly, the downloading unit 13 is further configured to continue downloading the VNF software version through the new available path set determined by the second determination processing unit 132.
Fig. 10 is a schematic structural diagram of a fourth configuration of an apparatus for implementing VNF automatic deployment according to an embodiment of the present invention, which is applied to a first node, where the first node is a node to be installed with a VNF software version in an NFV network topology, and as shown in fig. 10, the apparatus includes a sending unit 10, a receiving unit 11, a determining unit 12, and a downloading unit 13; wherein,
the sending unit 10 is configured to send a broadcast message for updating the deployment path routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed; the VNFM node is also used for initiating an available path set arbitration request to the VNFM node;
the receiving unit 11 is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment path routing information table of the receiving unit, so as to update the deployment path routing information table; also for receiving a set of available paths for VNFM node feedback;
the determining unit 12 is configured to determine, according to the updated deployment routing information table, the preset path selection policy, and the VNF software version trust policy, that an available path set is not determined, that is, the determined available path set is empty;
the downloading unit 13 is configured to download the VNF software version according to the available path set received by the receiving unit 11.
In practical applications, the sending unit 10, the receiving unit 11, the determining unit 12, the downloading unit 13, the first judging and processing unit 131, and the second judging and processing unit 132 may all be implemented by a Central Processing Unit (CPU), a microprocessor unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like in a node to which the VNF automatic deployment apparatus belongs according to the embodiment of the present invention.
The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.
In the embodiments provided in the present invention, it should be understood that the disclosed method and apparatus can be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.
Claims (8)
1. A method for realizing Virtual Network Function (VNF) automatic deployment is applied to a first node, wherein the first node is any node of a Network Function Virtualization (NFV) network topology where a VNF software version is to be installed, and the method comprises the following steps:
sending a broadcast message for updating the deployment routing information table to all second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
receiving the deployment path routing information fed back by all the second nodes and recording the deployment path routing information in a deployment routing information table of the second nodes so as to update the deployment routing information table;
determining an available path set according to the updated deployment routing information table, a preset path selection strategy and a VNF software version trust strategy; the set of available paths includes one or more available paths;
downloading the VNF software version through the determined available path set;
the preset path selection strategy comprises that the available bandwidth of the second node is greater than a bandwidth threshold, or the available bandwidth of the second node is greater than the bandwidth threshold and the next hop count of the first node and the second node is less than or equal to the hop count threshold; the bandwidth threshold is the minimum bandwidth required by the first node for downloading the VNF software version;
downloading the VNF software version through the determined set of available paths, including: respectively downloading different files from a plurality of second nodes corresponding to a plurality of available paths by using the VNF software version to be downloaded as a granularity; or merging and downloading the files in the VNF software versions to be downloaded from a plurality of second nodes corresponding to the plurality of available paths.
2. The method of claim 1, wherein during the downloading of the VNF software version over the determined set of available paths, the method further comprises:
when all available paths in the determined available path set are interrupted, if the VNF software version is determined to be not downloaded completely through judgment, determining a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
the VNF software version continues to be downloaded through the determined new set of available paths.
3. The method of claim 1, wherein during the downloading of the VNF software version over the determined set of available paths, the method further comprises:
when a third node is newly added in the NFV network topology, the third node is a node which can be used for the first node to realize VNF software version downloading, and if the third node is judged to be unfinished in downloading the VNF software version, a new available path set is determined again according to the deployment routing information table updated in real time and the VNF software version trust strategy;
the VNF software version continues to be downloaded through the determined new set of available paths.
4. The method of claim 1, further comprising: when the available path set is not determined according to the updated deployment routing information table, the preset path selection strategy and the VNF software version trust strategy, initiating an available path set arbitration request to a Virtual Network Function Management (VNFM) node;
receiving an available path set fed back by a VNFM node;
the VNF software version is downloaded over the received set of available paths.
5. A device for realizing automatic deployment of a Virtual Network Function (VNF) is applied to a first node, wherein the first node is any node to be installed with a VNF software version in a network topology of Network Function Virtualization (NFV), and is characterized by comprising a sending unit, a receiving unit, a determining unit and a downloading unit; wherein,
the sending unit is used for sending the broadcast message of the updated deployment routing information table to all the second nodes; the second node characterizes a node in the NFV network topology that can provide a version of VNF software to be installed;
the receiving unit is configured to receive the deployment path routing information fed back by all the second nodes and record the deployment path routing information in a deployment routing information table of the receiving unit, so as to update the deployment routing information table;
the determining unit is configured to determine an available path set according to the updated deployment routing information table, a preset path selection policy, and a VNF software version trust policy; the set of available paths includes one or more available paths;
the downloading unit is used for downloading the VNF software version through the determined available path set;
the preset path selection strategy comprises that the available bandwidth of the second node is greater than a bandwidth threshold, or the available bandwidth of the second node is greater than the bandwidth threshold and the next hop count of the first node and the second node is less than or equal to the hop count threshold; the bandwidth threshold is the minimum bandwidth required by the first node for downloading the VNF software version;
the download unit is specifically configured to: respectively downloading different files from a plurality of second nodes corresponding to a plurality of available paths by using the VNF software version to be downloaded as a granularity; or merging and downloading the files in the VNF software versions to be downloaded from a plurality of second nodes corresponding to the plurality of available paths.
6. The apparatus according to claim 5, characterized in that the apparatus further comprises a first judgment processing unit; wherein,
the first judgment processing unit is configured to, when all available paths in the determined available path set are interrupted, determine, if it is determined that the downloading of the VNF software version is not completed through judgment, determine a new available path set again according to the deployment routing information table updated in real time and the VNF software version trust policy;
correspondingly, the downloading unit is further configured to continue downloading the VNF software version through the new available path set determined by the first determination processing unit.
7. The apparatus according to claim 5, further comprising a second determination processing unit; wherein,
the second judgment processing unit is configured to, when a third node is newly added to the NFV network topology, determine that the VNF software version download is not completed by the third node as a node that can be used for the first node to implement the VNF software version download, and determine a new available path set again according to the deployment route information table updated in real time and the VNF software version trust policy;
accordingly, the downloading unit is further configured to continue downloading the VNF software version through the new available path set determined by the second determination processing unit.
8. The apparatus according to claim 5, wherein when the determining unit determines that the available path set is not determined according to the updated deployment routing information table, the preset path selection policy, and the VNF software version trust policy, the sending unit is further configured to initiate an available path set arbitration request to the virtual network function management VNFM node;
the receiving unit is further configured to receive an available path set fed back by a VNFM node;
and the downloading unit is used for downloading the VNF software version according to the available path set received by the receiving unit.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410549642.7A CN105577409B (en) | 2014-10-16 | 2014-10-16 | Method and device for realizing automatic deployment of virtual network function |
| PCT/CN2015/083042 WO2016058412A1 (en) | 2014-10-16 | 2015-07-01 | Method and device for achieving virtualized network function deployment, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410549642.7A CN105577409B (en) | 2014-10-16 | 2014-10-16 | Method and device for realizing automatic deployment of virtual network function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105577409A CN105577409A (en) | 2016-05-11 |
| CN105577409B true CN105577409B (en) | 2020-08-11 |
Family
ID=55746091
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410549642.7A Active CN105577409B (en) | 2014-10-16 | 2014-10-16 | Method and device for realizing automatic deployment of virtual network function |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105577409B (en) |
| WO (1) | WO2016058412A1 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3472971B1 (en) * | 2016-06-16 | 2022-09-14 | Telefonaktiebolaget LM Ericsson (publ) | Technique for resolving a link failure |
| CN107967140B (en) | 2016-10-18 | 2021-08-03 | 华为技术有限公司 | Software modification initiating method, metadata publishing method and device |
| CN108400940B (en) * | 2018-02-27 | 2019-11-05 | 西南交通大学 | A kind of multicast virtual network function dispositions method based on Estimation of Distribution Algorithm |
| CN110545193B (en) * | 2018-05-28 | 2021-04-09 | 华为技术有限公司 | Virtual resource management method, virtual resource management equipment and server |
| CN110708178B (en) * | 2018-07-09 | 2022-06-21 | 中兴通讯股份有限公司 | Network deployment method and device |
| CN109495304B (en) * | 2018-11-19 | 2020-10-16 | 中国科学院信息工程研究所 | Convergence node deployment method and device |
| US11171859B2 (en) * | 2019-05-01 | 2021-11-09 | Sony Corporation | Large-scale node configuration management for MAAS platform |
| CN112865988B (en) * | 2019-11-26 | 2023-03-24 | 中国电信股份有限公司 | Logic network deployment method, controller, node, equipment and system |
| CN110990127B (en) * | 2019-12-23 | 2023-05-12 | 深信服科技股份有限公司 | Automatic deployment method, device, equipment and storage medium for virtual machine |
| CN111786901B (en) * | 2020-05-21 | 2023-08-22 | 网宿科技股份有限公司 | Transmission parameter self-adaptive adjustment method and acceleration service system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447884A (en) * | 2007-11-26 | 2009-06-03 | 华为技术有限公司 | Method for achieving software upgrade by cooperation among network elements, equipment and system therefor |
| CN102385519A (en) * | 2011-09-04 | 2012-03-21 | 上海量明科技发展有限公司 | Method and system for installing software |
| CN103475578A (en) * | 2013-09-09 | 2013-12-25 | 华为技术有限公司 | Method and device for path selection |
| CN103607349A (en) * | 2013-11-14 | 2014-02-26 | 华为技术有限公司 | Method for determining route in virtual network and provider edge equipment |
| CN103916302A (en) * | 2013-01-04 | 2014-07-09 | 上海贝尔股份有限公司 | Method and device for providing SDN stream route for virtual WLAN |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050120106A1 (en) * | 2003-12-02 | 2005-06-02 | Nokia, Inc. | System and method for distributing software updates to a network appliance |
| CN101848111A (en) * | 2009-03-23 | 2010-09-29 | 华为技术有限公司 | Method, device and system for updating software |
-
2014
- 2014-10-16 CN CN201410549642.7A patent/CN105577409B/en active Active
-
2015
- 2015-07-01 WO PCT/CN2015/083042 patent/WO2016058412A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447884A (en) * | 2007-11-26 | 2009-06-03 | 华为技术有限公司 | Method for achieving software upgrade by cooperation among network elements, equipment and system therefor |
| CN102385519A (en) * | 2011-09-04 | 2012-03-21 | 上海量明科技发展有限公司 | Method and system for installing software |
| CN103916302A (en) * | 2013-01-04 | 2014-07-09 | 上海贝尔股份有限公司 | Method and device for providing SDN stream route for virtual WLAN |
| CN103475578A (en) * | 2013-09-09 | 2013-12-25 | 华为技术有限公司 | Method and device for path selection |
| CN103607349A (en) * | 2013-11-14 | 2014-02-26 | 华为技术有限公司 | Method for determining route in virtual network and provider edge equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105577409A (en) | 2016-05-11 |
| WO2016058412A1 (en) | 2016-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105577409B (en) | Method and device for realizing automatic deployment of virtual network function | |
| RU2654128C1 (en) | Software defined network infrastructure with virtual range expanders | |
| CN103109270B (en) | Software upgrading in service on the card of the NE virtual partition leaving the card of virtual partition including guide service | |
| CN104219127B (en) | A kind of creation method and equipment of virtual network example | |
| CN105122936B (en) | Service distribution processing method and related device | |
| CN109586938B (en) | Method and device for generating instance service topology | |
| US9584369B2 (en) | Methods of representing software defined networking-based multiple layer network topology views | |
| TW202026901A (en) | Independent datastore in a network routing environment | |
| US10721315B1 (en) | Developing and implementing migration sequences in data communication networks | |
| JP2017508401A (en) | Switch replacement of partial software defined network in IP network | |
| US20220303335A1 (en) | Relaying network management tasks using a multi-service receptor network | |
| CN111245735B (en) | Flow scheduling method for ensuring service quality in SDN environment | |
| CN110086640B (en) | Service enabling method and device | |
| US11444840B2 (en) | Virtualized networking application and infrastructure | |
| CN104486394B (en) | In-service Software Upgrade method and device | |
| JP5869041B2 (en) | Method for mapping network topology request to physical network, computer program product, mobile communication system, and network configuration platform | |
| US11509527B1 (en) | Assisted and context-driven network changes | |
| WO2005098735A2 (en) | System using planning information to modify operation of a digital network | |
| CN112532408A (en) | Method, device and storage medium for extracting fault propagation conditions | |
| CN116094868A (en) | Selective formation and maintenance of tunnels within a mesh topology | |
| CN113127023A (en) | Method, device and system for upgrading service | |
| US20240106708A1 (en) | Fabric availability and synchronization | |
| CN108271149B (en) | Method, equipment and system for migrating user data anchor points | |
| US20160043894A1 (en) | Automatic reconfiguration of network parameters during file system failover | |
| Yasin et al. | Reliable multipath flow for link failure recovery in 5G networks using SDN paradigm |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |