CN105634778B - Method and system for realizing VNF instantiation, NFVO and VNFM - Google Patents
Method and system for realizing VNF instantiation, NFVO and VNFM Download PDFInfo
- Publication number
- CN105634778B CN105634778B CN201410612825.9A CN201410612825A CN105634778B CN 105634778 B CN105634778 B CN 105634778B CN 201410612825 A CN201410612825 A CN 201410612825A CN 105634778 B CN105634778 B CN 105634778B
- Authority
- CN
- China
- Prior art keywords
- vnf
- vnfm
- nfvo
- instantiated
- tool
- 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
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)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for realizing VNF instantiation, and NFVO and VNFM. In the VNF instantiation process, different VNF version packages do not need to be issued according to different capacities on the basis of the original instantiation mechanism, the frequency of issuing the VNF version packages is reduced, the number of VNF versions managed by NFVO is reduced, the VNF instantiation process is simplified, and therefore the usability of VNF management is improved. The technical scheme provided by the invention is suitable for all types of VNFs.
Description
Technical Field
The present invention relates to Network Function Virtualization (NFV) technology, and in particular, to a method and a system for implementing VNF instantiation, and NFVO and VNFM.
Background
NFV technology refers to the conversion of traditional network functions such as: a Proxy call session control Function (P-CSCF), an Interrogating call session control Function (I-CSCF), a Serving call session control Function (S-CSCF), a Home Subscriber Server (HSS), and an Application Server (AS), etc., virtualize and deploy these virtual Network Function components (VNFC, Virtualized Network Function Component) on a cloud vm, thereby implementing virtualization of Network functions, the Virtualized Network functions are referred to AS Virtual Network Functions (VNF), which runs on the cloud, the NFV implements decoupling of VNF and hardware resources, the VNF occupies resources AS needed, thereby improving resource utilization efficiency, when Network load is low, the Server is turned off, thereby also saving energy, is more environment-friendly.
The European Telecommunications Standardization Institute (ETSI) has established a Telecommunications NFV protocol standard, an end-to-end reference architecture is defined in ETSI NFV technical specifications, and a Network Function Virtualization Orchestrator (NFVO), also called an editor, a Virtual Network Function Manager (VNFM), a Virtual Infrastructure Management (VIM), a Network Function Virtualization Infrastructure (NFVI), and a Virtual Network Function (VNF), among other functional units, are introduced into the end-to-end reference architecture. The NFVO is mainly responsible for arranging and managing network services, virtual resources and physical resources of the whole network; the VNFM is mainly responsible for lifecycle management (e.g., instantiation, deletion, viewing, updating, horizontal elastic scale in/out, vertical elastic scale up/down, self-healing, etc.) of the VNF of the network element and allocation and management of virtual resources related to the VNF; the VIM is mainly responsible for virtualized infrastructure management, and has the main functions of realizing allocation and management (such as addition, deletion, viewing, update, failure recovery and the like) of resources of the whole infrastructure layer, including calculation, storage and network resources; the NFVI is used as a virtualized resource layer and comprises a newly added virtualized platform and original hardware resources after virtualization; the VNF refers to a virtualized network element, is deployed on the NFVI, performs a network element function defined by 3GPP, and maintains the function consistent with non-virtualization.
Compared with the traditional network, the NFV technology manages resources and VNFs in a unified manner, and includes the following functions: the network service management system comprises a cloud resource management function, a VNF management function, a network service management function and the like, wherein the function related to the VNF management function is a VNF instantiation function in the VNF management function.
ETSI standard "GS NFV-MAN 001v0.5.0 (2014-05)" annexes b.3.1 and b.3.2 describe a VNF instantiated collaboration flow, in the VNF instantiated collaboration flow, the same version of VNF needs to publish a plurality of corresponding VNF version packages according to different VNF capacities, and these version packages all need to be registered on the NFVO and generate corresponding templates, and these templates are referred to in the deployment process to create VNFs with corresponding capacities.
Annex b.2 of ETSI standard GS NFV-MAN 001v0.5.0(2014-05) describes a VNF registration process, where the VNF registration process completes a registration process of a Virtual Network Function Description (VNFD) in the NFVO database, which is equivalent to registering a template of a VNF in the NFVO database, and subsequently, in a deployment process, the template may be referred to create a VNF instance, fig. 1 is a flowchart of a VNF registration process in the existing specification, and as shown in fig. 1, the flowchart includes:
step 100: and submitting the VNF version package to the NFVO by the user, and registering the VNFD.
Step 101: NFVO checks the essential elements of NVFD, checking authenticity and security through the manifiest file.
Step 102: NFVO registers VNFD in the database.
Step 103: and the NFVO saves the image file in the VNF version package into an image library of the VIM.
Step 104: the VIM replies to the NFVO that the reservation image was successful.
Step 105: the NFVO replies VNFD registration success to the user.
Appendices b.3.1 and b.3.2 of ETSI standard GS NFV-MAN 001v0.5.0(2014-05) describe a VNF instantiation scheme, for a total of three implementations, wherein appendix b.3.1 describes scheme one: namely VNF instantiation by NFVO responsible for allocating resources; appendix b.3.2.1 describes scheme two: the VNFM is responsible for allocating resources, and an Authenticated third Party (EM) initiates instantiation of the VNF of an instantiation request; appendix b.3.2.2 describes scheme three: i.e. VNFM is responsible for allocating resources, NFVO initiates instantiation of VNF that instantiates the request.
Fig. 2 is a schematic flowchart of instantiation of a VNF in the existing specification, which is responsible for resource allocation by NFVO, and as shown in fig. 2, the method includes the following steps:
step 200: the user (sender) sends an instantiation VNF request to the NFVO.
Step 201: the NFVO checks the validity of the request including, but not limited to: 1) authenticating the user who initiates the request; 2) the requested parameters are checked for validity.
Step 202: and the NFVO performs feasibility analysis on the instantiation request.
In this step, while performing feasibility analysis, the NFVO optionally reserves resources.
Step 203: the NFVO requests the VNFM to instantiate the VNF.
Step 204: the VNFM processes instantiation requests, including but not limited to: 1) checking the validity of the request; 2) checking the validity of the request parameter; 3) VNF-related parameter checking, such as license (license) checking, etc.; 4) virtual Deployment Units (VDUs) are computed.
Step 205: and the VNFM sends a resource reservation request to the NFVO according to the calculated resource demand.
Step 206: the NFVO performs validity checks on the resource reservation request including, but not limited to: 1) carrying out validity check on the parameters of the resource reservation request; 2) checking the position requirement of the resource, and confirming whether the NFVO can meet the resource position requirement of the VNFM; 3) the interdependencies of the resources are checked.
Step 207: the NFVO initiates a resource occupation request to the VIM, wherein the resources comprise computing resources, storage resources, network resources and the like.
Step 208: the VIM creates an internal network.
Step 209: the VIM creates virtual machines and links the virtual machines to the relevant internal and external networks.
Step 210: the VIM returns a create resource success response to the NFVO.
Step 211: the NFVO informs the VNFM that the resource reservation is successful.
Step 212: the VNFM configures VNF deployment related data.
Step 213: VNFM informs EM: VNF deployment is successful, requiring VNF to be brought into EM management scope.
Step 214: EM configuration VNF data including, but not limited to: 1) office data; 2) user data.
Step 215: VNFM informs NFVO: VNF instantiation was successful.
Step 216: the NFVO notifies the user: VNF instantiation was successful.
Fig. 3 is a schematic flowchart of a VNF instantiation process in an existing specification, where the VNFM is responsible for allocating resources and the EM initiates an instantiation request, and as shown in fig. 3, the VNF instantiation process includes:
step 300: the EM (authenticated) sends an instantiate VNF request to the VNFM.
Step 301: the VNFM calculates the number of resources needed and then sends an instantiate VNF request to the NFVO, including the resource requirements.
In this step, the instantiation VNF request is used to request the NFVO to perform validity and feasibility checks on the instantiation request, and resource reservation is performed only after the checks pass.
Step 302: and the NFVO checks the validity and feasibility of the instantiation request.
Step 303: and after the NFVO finishes the check, initiating a resource reservation request to the VIM.
Step 304: and the VIM replies a resource reservation success response to the NFVO.
It should be noted that step 303 and step 304 are optional steps.
Step 305: and the NFVO replies to the VNFM to perform validity check passing, feasibility check passing and resource reservation success response.
Step 306: the VNFM sends create network and create Virtual Machine (VMs) requests to the VIM.
Step 307: after the VIM creates the network and creates VMs, a successful creation response is returned to the VNFM.
Step 308: the VNFM configures VNF deployment data.
Step 309: the VNFM returns VNF instantiation success to the EM.
Step 310: EM and VNFM bring VNF into its own regulatory scope.
Step 311: EM configuration VNF data including, but not limited to: 1) office data; 2) user data.
Step 312: VNFM informs NFVO: VNF instantiation was successful.
Step 313: and the NFVO establishes a corresponding relation between the VNF and the resource pool.
Fig. 4 is a schematic flowchart of a VNF instantiation process in an existing specification, where the VNFM is responsible for allocating resources and the NFVO initiates an instantiation request, and as shown in fig. 4, the VNF instantiation process includes:
step 400: the NFVO receives the VNF instantiation request. The VNF instantiation request in this step may be a manual trigger or an automatic trigger, such as a trigger from the OSS/BSS, etc.
Step 401: the NFVO sends an instantiate VNF request to the VNFM.
Step 402: the VNFM calculates the number of resources needed and then sends an instantiate VNF request to the NFVO, including the resource requirements.
In this step, the instantiation VNF request is used to request the NFVO to perform validity and feasibility checks on the instantiation request, and resource reservation is performed only after the checks pass.
Step 403: and the NFVO checks the validity and feasibility of the instantiation request.
Step 404: and after the NFVO finishes the check, initiating a resource reservation request to the VIM.
Step 405: and the VIM replies a resource reservation success response to the NFVO.
It should be noted that step 303 and step 304 are optional steps.
Step 406: and the NFVO replies to the VNFM to perform validity check passing, feasibility check passing and resource reservation success response.
Step 407: the VNFM sends create network and create VMs requests to the VIM.
Step 408: after the VIM creates the network and creates VMs, a successful creation response is returned to the VNFM.
Step 409: the VNFM configures VNF deployment data.
Step 410: the VNFM returns VNF instantiation success to the EM.
Step 411: EM and VNFM bring VNF into its own regulatory scope.
Step 412: EM configuration VNF data including, but not limited to: 1) office data; 2) user data.
Step 413: VNFM informs NFVO: VNF instantiation was successful.
Step 414: and the NFVO establishes a corresponding relation between the VNF and the resource pool.
In practical applications, when a VNF is instantiated through the NFVO, VNFs with different capacities often need to be instantiated for the same VNF version, such as the same S-CSCF version, and a shanghai office and a suzhou office need to be instantiated, and capacities of the two offices may be completely different. Currently, in a VNF registration and VNF instantiation scheme of ETSI, it is required that the same version of a VNF needs to publish a plurality of corresponding VNF version packages according to different VNF capacities, and these VNF version packages all need to be registered on NFVO and generate corresponding templates, and then refer to these templates in a deployment process so as to create VNFs with corresponding capacities. The VNF registration and instantiation scheme in the existing specification has a complex process and poor system usability. Furthermore, in general, when a vendor releases a VNF version package, different version packages are not released for different capacities. That is, VNF instantiation is not possible for this case, according to the current ETSI specifications.
Disclosure of Invention
In order to solve the above technical problems, the present invention provides a method and a system for implementing VNF instantiation, and NFVO and VNFM, which do not need to issue different VNF version packages for different capacities, and can simplify the VNF instantiation process and improve the usability of the system.
In order to achieve the object of the present invention, the present invention provides a method for implementing VNF instantiation, including:
in the VNF instantiation process, the virtual network function management VNFM calculates, according to a tool for automatically calculating VDUs, the virtual network function component VNFC instantiated by the VNF and the virtual deployment unit VDUs thereof in combination with the capacity to be instantiated and information thereof.
The method also comprises the following steps: in the process of registering the virtual network function description VNFD, the network function virtualization orchestrator NFVO obtains and stores the tool for automatically computing the VDU.
The NFVO tool for acquiring and storing the auto-computation VDU includes:
a user carries a plug-in of an automatic computing VDU in a VNF version package and submits the plug-in to the NFVO;
and when the NFVO registers VNFD in the database, storing the acquired plug-in of the automatic computing VDU into the database.
When a VNF that is responsible for allocating resources by the NFVO is instantiated, the calculating VNFCs and VDUs instantiated by the VNF includes:
when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM;
in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating the VDU, and the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated are calculated by combining the capacity to be instantiated and the information thereof.
When the VNFM is responsible for allocating resources, the EM initiates an instantiation request, or the VNFM is responsible for allocating resources, and the NFVO initiates an instantiation request, the calculating VNFCs and VDUs instantiated by the VNF includes:
before the VNFM initiates an instantiation VNF request to the NFVO, the VNFM calls a tool for automatically calculating VDUs, and the VNFC of the VNF instance which is currently requested to be instantiated and the VDUs of the VNF instance are calculated by combining capacity to be instantiated and information of the capacity to be instantiated.
The invention also discloses a system for realizing the instantiation of the VNF, which at least comprises a VNFM;
the VNFM at least comprises a processing module, and is used for automatically calculating the VNFC instantiated by the VNF and the VDUs thereof by the VNFM according to a tool for automatically calculating the VDU in the instantiation process of the VNF and by combining the capacity to be instantiated and the information thereof.
Further comprising: NFVO; the NFVO at least comprises an acquisition module, and is used for acquiring and storing a tool for automatically calculating the VDU in the registration process of the VNFD.
The acquisition module is specifically configured to: receiving a VNF version package carrying plug-in units of automatically-calculated VDUs from a user; the obtained plug-in for the autonomic computing VDU is saved to the database while the VNFD is registered in the database.
The processing module is specifically configured to:
when the VNF which is responsible for resource allocation by the NFVO is instantiated, when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM; in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating a VDU, and automatically calculates the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated according to the capacity to be instantiated and the information thereof;
alternatively, the first and second electrodes may be,
the processing module is specifically configured to, when the VNFM is responsible for allocating resources, the EM initiates an instantiation request, or the VNFM is responsible for allocating resources, and the NFVO initiates an instantiation request, before the VNFM initiates an instantiation VNF request to the NFVO, the VNFM calls a tool for automatically calculating VDUs, and in combination with capacity to be instantiated and information thereof, automatically calculates VNFCs of VNF instances currently requesting to instantiate and VDUs thereof.
The invention also discloses a VNFM, which at least comprises a processing module and is used for automatically calculating the VNFC instantiated by the VNF and the VDUs thereof by the VNFM according to a tool for automatically calculating the VDU in the instantiation process of the VNF and by combining the capacity to be instantiated and the information thereof.
The processing module is specifically configured to: when the VNF which is responsible for resource allocation by the NFVO is instantiated, when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM;
in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating the VDU, and the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated are automatically calculated by combining the capacity to be instantiated and the information thereof.
The processing module is specifically configured to: when VNFM is responsible for resource allocation and EM initiates instantiation requests, or VNFM is responsible for resource allocation and NFVO initiates instantiation requests, before VNFM initiates VNF instantiation requests to NFVO, VNFM calls a tool for automatically calculating VDUs, and VNFC and VDUs of VNF instances which are currently requested to be instantiated are automatically calculated by combining capacity to be instantiated and information of the capacity to be instantiated.
The invention further discloses an NFVO, which at least comprises an acquisition module and is used for acquiring and storing a tool for automatically calculating the VDU in the registration process of the VNFD.
The acquisition module is specifically configured to: receiving a VNF version package carrying plug-in units of automatically-calculated VDUs from a user; the obtained plug-in for the autonomic computing VDU is saved to the database while the VNFD is registered in the database.
Compared with the prior art, the technical scheme includes that in the VNF instantiation process, the VNFM automatically calculates the VNFC instantiated by the VNF and the VDUs thereof according to a tool for automatically calculating the VDU and by combining the capacity to be instantiated and information thereof. In the VNF instantiation process, different VNF version packages do not need to be issued according to different capacities on the basis of the original instantiation mechanism, the frequency of issuing the VNF version packages is reduced, the number of VNF versions managed by NFVO is reduced, the VNF instantiation process is simplified, and therefore the usability of VNF management is improved. The technical scheme provided by the invention is suitable for all types of VNFs.
The method provided by the invention is characterized in that a tool for calculating capacity is arranged in the VNF version packet, the tool for calculating capacity is utilized in the Deployment process, and corresponding VNFC (virtualized network function component) s and VDUs (virtual delivery units) thereof are calculated according to the requirements of different VNFs
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flow diagram illustrating a VNF registration process in the existing specification;
fig. 2 is a schematic flowchart of instantiation of a VNF in an existing specification, which is responsible for resource allocation by an NFVO;
fig. 3 is a schematic flowchart of VNF instantiation in an existing specification, where VNFM is responsible for allocating resources and EM initiates an instantiation request;
fig. 4 is a schematic flowchart of VNF instantiation in the existing specification, where VNFM is responsible for allocating resources and NFVO initiates an instantiation request;
FIG. 5 is a flow diagram of a method of implementing VNF instantiation of the present invention;
fig. 6 is a schematic structural diagram of a system for implementing VNF instantiation according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
Fig. 5 is a flowchart of a method for implementing VNF instantiation according to the present invention, as shown in fig. 5, including:
step 501: in the instantiation process of the VNF, the VNFM calculates the VNFC instantiated by the VNF and the VDUs thereof according to a tool for automatically calculating the VDU and by combining the capacity to be instantiated and the information thereof.
The method specifically comprises the following steps:
when the VNF, for which the NFVO is responsible for allocating resources, is instantiated, when the NFVO requests the VNFM to instantiate the VNF, that is, step 203, the NFVO transmits a tool for automatically calculating the VDU to the VNFM in a request;
in the process of processing instantiation by the VNFM, that is, in step 204, the VNFM calls a tool for automatically calculating VDUs, and automatically calculates VNFCs and VDUs of the VNF instance currently requested to be instantiated by combining the capacity to be instantiated and information thereof.
Alternatively, the first and second electrodes may be,
when VNFM is responsible for allocating resources, EM initiates an instantiation request, or VNFM is responsible for allocating resources, and NFVO initiates an instantiation request, before VNFM initiates an instantiation VNF request to NFVO, that is, step 301 or step 402, VNFM calls a tool for automatically calculating VDUs, and VNFCs and VDUs of VNF instances currently requested to be instantiated are automatically calculated in combination with capacity to be instantiated and information thereof.
Each VNF has its own unique information, i.e. the information of the VNF to be instantiated in step 100, and different VNFs may have different information, such as CSCF and SSS, and the information may be different, and for the CSCF, the frequency of registration and deregistration, the number of user traffic erl, the frequency of subscription and refresh subscription, the frequency of short message, and the like may be included, and for the SSS, the service penetration rate of call forwarding, the service penetration rate of three-way call, and the like may be included. The capacity to be instantiated is mainly the number of users (different VNFs may be different).
The specific implementation of the VNFC and its VDUs for calculating the VNF instance currently requested to be instantiated in this step is described in the ETSI specification, and mainly includes requirements of the VNFC and the VDU on computation, storage, network resources, and the like.
According to the technical scheme, in the VNF instantiation process, different VNF version packages do not need to be issued according to different capacities on the basis of the original instantiation mechanism, the frequency of issuing the VNF version packages by the VNF is reduced, the number of VNF versions managed by NFVO is reduced, the VNF instantiation process is simplified, and therefore the usability of VNF management is improved.
The method also comprises the following steps:
step 500: in the registration process of VNFD, NFVO obtains and saves the tool for automatically computing VDU. In particular, the amount of the solvent to be used,
according to the VNF registration process shown in fig. 1, when a user submits a VNF version package to the NFVO, the method of the present invention also carries a tool for automatically calculating a VDU in the VNF version package and sends the VDU to the NFVO;
according to the VNF registration procedure shown in fig. 1, while the NFVO registers the VNFD in the database, the method of the present invention further includes: the NFVO saves the obtained tool for automatically computing VDUs into a database.
The tool for automatically calculating the VDU may be implemented in a plug-in manner in actual implementation, which is not used to limit the protection scope of the present invention, and the implementation of the tool according to the technical solution provided by the present invention is easily obtained by those skilled in the art, and is not used to limit the protection scope of the present invention, which is not described herein again.
According to the technical scheme provided by the invention, a tool for automatically calculating the VDU is carried in the VNF version packet, so that the corresponding VNFCs and the VDUs thereof are calculated according to different VNF capacity requirements of the tool by using the tool for calculating the capacity in the deployment process, and then instantiation is carried out according to the VDUs. By adopting the method, because of the tool for automatically calculating the VDUs, aiming at 10 ten thousand bureaus, 20 ten thousand bureaus, 50 ten thousand bureaus, 100 ten thousand bureaus and the like, the automatic tool in the released version can automatically calculate the number of the VDUs; if there is no tool for automatically calculating VDUs, different versions need to be released for 10 ten thousand stations, 20 ten thousand stations, 50 ten thousand stations, 100 ten thousand stations, and so on because there is no function for automatic calculation. Therefore, the same version of the VNF in the present invention only needs to publish one version package and only needs to register once on the NFVO. The VNF does not need to issue different VNF version packages aiming at different capacities, the issuing of the VNF is simplified, and the usability of the system is improved.
The process of the present invention is described in detail below with reference to specific examples.
A first embodiment, aiming at a flow of a VNF registration process in the existing specification shown in fig. 1, the present invention optimizes the flow, and on the basis of inheriting the flow shown in fig. 1, the optimization performed on the flow shown in fig. 1 includes:
in step 100 shown in fig. 1, a VNF version package submitted by a user to NFVO to register VNFD further includes a plug-in for automatically computing a VDU;
furthermore, when the NFVO registers the VNFD in the database, the plug-in for the auto-compute VDU obtained from the VNF version report is saved to the database at the same time.
In a second embodiment, for a process instantiated by a VNF in the existing specification shown in fig. 2 and responsible for allocating resources by an NFVO, the optimization performed on the process shown in fig. 2 by the present invention, on the basis of inheriting the process shown in fig. 2, includes:
in step 203, the NFVO requests the VNFM to instantiate the VNF, and the NFVO simultaneously carries an automatic calculation tool for automatically calculating the VDU in the request and sends the request to the VNFM;
in processing the instantiation request by the VNFM shown in step 204, in addition to including in the existing flow: the VNFM checks the legitimacy of the request; the VNFM checks the validity of the request parameters; and VNFM check VNF related parameters, such as license check, including: and the VNFM calls a tool for automatically calculating the VDU, and calculates the VDUs corresponding to the VNF meeting the current request example by combining the capacity to be instantiated and the information thereof.
In a third embodiment, for a VNF instantiation process in the existing specification shown in fig. 3, where VNFM is responsible for resource allocation and EM initiates an instantiation request, the optimization of the process shown in fig. 3 includes, based on inheriting the process shown in fig. 3:
after step 300, before step 301, further comprising: and the VNFM calls a tool for automatically calculating the VDU, and calculates the VDUs corresponding to the VNF meeting the current request example by combining the capacity to be instantiated and the information thereof. Then, in step 301, an instantiation VNF request (including a resource requirement) is sent to the NFVO, and the NFVO is requested to perform validity and feasibility check on the instantiation request, and if the check is passed, perform resource reservation, and the like.
In a fourth embodiment, for a VNF instantiation process in the existing specification shown in fig. 4, where a VNFM is responsible for allocating resources and an NFVO initiates an instantiation request, the optimization of the process shown in fig. 4 includes, based on inheriting the process shown in fig. 4:
after step 401, before step 402, further comprising: and the VNFM calls a tool for automatically calculating the VDU, and calculates the VDUs corresponding to the VNF meeting the current request example by combining the capacity to be instantiated and the information thereof. Then, in step 301, an instantiation VNF request (including a resource requirement) is sent to the NFVO, and the NFVO is requested to perform validity and feasibility check on the instantiation request, and if the check is passed, perform resource reservation, and the like.
FIG. 6 is a schematic diagram of a component structure of a system for implementing instantiation of a VNF according to the present invention, as shown in FIG. 6, at least including a VNFM;
the VNFM at least comprises a processing module, and is used for automatically calculating the VNFC instantiated by the VNF and the VDUs thereof by the VNFM according to a tool for automatically calculating the VDU in the instantiation process of the VNF and by combining the capacity to be instantiated and the information thereof.
In particular, the amount of the solvent to be used,
the processing module is specifically configured to, when the VNF for which the NFVO is responsible for allocating resources is instantiated, when the NFVO requests the VNFM to instantiate the VNF, carry, by the NFVO, a tool for automatically calculating the VDU in the request, and transmit the tool to the VNFM;
in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating the VDU, and the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated are automatically calculated by combining the capacity to be instantiated and the information thereof.
Alternatively, the first and second electrodes may be,
the processing module is specifically configured to, when the VNFM is responsible for allocating resources and the EM initiates an instantiation request, or when the VNFM is responsible for allocating resources and the NFVO initiates an instantiation request, call a VDUs auto-calculation tool by the VNFM before the VNFM initiates an instantiation VNF request to the NFVO, and automatically calculate the VNFC of the VNF instance currently requested to be instantiated and the VDUs thereof in combination with the capacity to be instantiated and information thereof
The system of the invention further comprises: NFVO; the NFVO at least comprises an acquisition module, and is used for acquiring and storing a tool for automatically calculating the VDU in the registration process of the VNFD.
Specifically, the obtaining module is specifically configured to: receiving a VNF version package carrying plug-in units of automatically-calculated VDUs from a user; the obtained plug-in for the autonomic computing VDU is saved to the database while the VNFD is registered in the database.
The above description is only a preferred example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (14)
1. A method for implementing a Virtual Network Function (VNF) instantiation, comprising:
in the instantiation process of the VNF, the virtual network function management VNFM calculates a virtual network function component VNFC instantiated by the VNF and a virtual deployment unit VDUs thereof according to a tool for automatically calculating a VDU and by combining the capacity to be instantiated and information thereof; wherein the tool for automatically computing the VDU is carried in a VNF version package.
2. The method of claim 1, further comprising, prior to the method: in the process of registering the virtual network function description VNFD, the network function virtualization orchestrator NFVO obtains and stores the tool for automatically computing the VDU.
3. The method of claim 2, wherein the NFVO tool to obtain and save the auto-compute VDU comprises:
a user carries a plug-in of an automatic computing VDU in a VNF version package and submits the plug-in to the NFVO;
and when the NFVO registers VNFD in the database, storing the acquired plug-in of the automatic computing VDU into the database.
4. The method of claim 2, wherein when an instantiated VNF responsible for allocating resources by an NFVO is instantiated, the calculating VNFCs and VDUs instantiated by the VNF comprises:
when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM;
in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating the VDU, and the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated are calculated by combining the capacity to be instantiated and the information thereof.
5. The method of claim 2, wherein when the VNFM is responsible for allocating resources, the network element management EM initiates an instantiation request, or the VNFM is responsible for allocating resources, and the NFVO initiates an instantiation request, the calculating VNFCs and VDUs instantiated by the VNF comprises:
before the VNFM initiates an instantiation VNF request to the NFVO, the VNFM calls a tool for automatically calculating VDUs, and the VNFC of the VNF instance which is currently requested to be instantiated and the VDUs of the VNF instance are calculated by combining capacity to be instantiated and information of the capacity to be instantiated.
6. A system implementing VNF instantiation for virtual network functions, comprising at least VNFM;
the VNFM at least comprises a processing module, and is used for automatically calculating VNFCs instantiated by the VNFs and VDUs thereof according to a tool for automatically calculating VDUs and the combination of capacity to be instantiated and information thereof in the instantiation process of the VNFs; wherein the tool for automatically computing the VDU is carried in a VNF version package.
7. The system of claim 6, further comprising: NFVO; the NFVO at least comprises an acquisition module, and is used for acquiring and storing a tool for automatically calculating the VDU in the registration process of the VNFD.
8. The system of claim 7, wherein the acquisition module is specifically configured to: receiving a VNF version package carrying plug-in units of automatically-calculated VDUs from a user; the obtained plug-in for the autonomic computing VDU is saved to the database while the VNFD is registered in the database.
9. The system of claim 7, wherein the processing module is specifically configured to:
when the VNF which is responsible for resource allocation by the NFVO is instantiated, when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM; in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating a VDU, and automatically calculates the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated according to the capacity to be instantiated and the information thereof;
alternatively, the first and second electrodes may be,
the processing module is specifically configured to, when the VNFM is responsible for allocating resources, the EM initiates an instantiation request, or the VNFM is responsible for allocating resources, and the NFVO initiates an instantiation request, before the VNFM initiates an instantiation VNF request to the NFVO, the VNFM calls a tool for automatically calculating VDUs, and in combination with capacity to be instantiated and information thereof, automatically calculates VNFCs of VNF instances currently requesting to instantiate and VDUs thereof.
10. The VNFM is characterized by at least comprising a processing module, wherein the processing module is used for automatically calculating VNFCs instantiated by the VNFs and VDUs thereof according to a tool for automatically calculating VDUs and the combination of capacity to be instantiated and information thereof in the process of instantiating the VNFs; wherein the tool for automatically computing the VDU is carried in a VNF version package.
11. The VNFM of claim 10, wherein the processing module is specifically configured to: when the VNF which is responsible for resource allocation by the NFVO is instantiated, when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries a tool for automatically calculating the VDU in the request and transmits the tool to the VNFM;
in the process of processing instantiation by the VNFM, the VNFM calls a tool for automatically calculating the VDU, and the VNFC and the VDUs of the VNF instance which is currently requested to be instantiated are automatically calculated by combining the capacity to be instantiated and the information thereof.
12. The VNFM of claim 10, wherein the processing module is specifically configured to: when VNFM is responsible for resource allocation and EM initiates instantiation requests, or VNFM is responsible for resource allocation and NFVO initiates instantiation requests, before VNFM initiates VNF instantiation requests to NFVO, VNFM calls a tool for automatically calculating VDUs, and VNFC and VDUs of VNF instances which are currently requested to be instantiated are automatically calculated by combining capacity to be instantiated and information of the capacity to be instantiated.
13. A Network Function Virtualization Orchestrator (NFVO) is characterized in that the NFVO at least comprises an acquisition module, a processing module and a storage module, wherein the acquisition module is used for acquiring and storing a tool for automatically calculating a VDU (virtual desktop Unit) in the process of registering a VNFD; wherein the tool for automatically computing the VDU is carried in a VNF version package.
14. The NFVO of claim 13, wherein the obtaining module is specifically configured to: receiving a VNF version package carrying plug-in units of automatically-calculated VDUs from a user; the obtained plug-in for the autonomic computing VDU is saved to the database while the VNFD is registered in the database.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410612825.9A CN105634778B (en) | 2014-11-04 | 2014-11-04 | Method and system for realizing VNF instantiation, NFVO and VNFM |
| PCT/CN2015/079839 WO2016070609A1 (en) | 2014-11-04 | 2015-05-26 | Method and system for implementing vnf instantiation, nfvo and vnfm |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410612825.9A CN105634778B (en) | 2014-11-04 | 2014-11-04 | Method and system for realizing VNF instantiation, NFVO and VNFM |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105634778A CN105634778A (en) | 2016-06-01 |
| CN105634778B true CN105634778B (en) | 2020-09-22 |
Family
ID=55908502
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410612825.9A Active CN105634778B (en) | 2014-11-04 | 2014-11-04 | Method and system for realizing VNF instantiation, NFVO and VNFM |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105634778B (en) |
| WO (1) | WO2016070609A1 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107689882B (en) | 2016-08-05 | 2020-04-21 | 华为技术有限公司 | Method and device for service deployment in virtual network |
| CN107786360A (en) * | 2016-08-30 | 2018-03-09 | 中兴通讯股份有限公司 | Network function virtualized management method and device |
| CN108011733B (en) * | 2016-10-27 | 2021-04-16 | 上海中兴软件有限责任公司 | Plug-in implementation method and device |
| CN108132827B (en) * | 2016-11-30 | 2021-12-10 | 华为技术有限公司 | Network slice resource mapping method, related equipment and system |
| CN108243205B (en) * | 2016-12-23 | 2021-06-08 | 上海诺基亚贝尔股份有限公司 | Method, equipment and system for controlling resource allocation of cloud platform |
| CN109428874B (en) * | 2017-08-31 | 2020-10-09 | 华为技术有限公司 | Registration method and device based on service architecture |
| CN109495529B (en) * | 2017-09-12 | 2022-04-12 | 华为技术有限公司 | Service processing method, first device and second device |
| CN109784085B (en) * | 2017-11-15 | 2023-10-27 | 中兴通讯股份有限公司 | Virtual network application implementation method, management system and computer readable storage medium |
| CN112242918B (en) * | 2019-07-19 | 2023-03-24 | 中兴通讯股份有限公司 | VNFD multi-version compatible processing method, device, equipment and storage medium |
| CN113495776A (en) | 2020-03-18 | 2021-10-12 | 华为技术有限公司 | VNF instantiation method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1866850A (en) * | 2005-05-18 | 2006-11-22 | 中兴通讯股份有限公司 | Method for H.323 gatekeeper realizing H.323 terminal timely registration |
| CN103838871A (en) * | 2014-03-21 | 2014-06-04 | 北京广利核系统工程有限公司 | Method for checking nuclear power plant safety level DCS S-VDU process file |
| CN104050045A (en) * | 2014-06-27 | 2014-09-17 | 华为技术有限公司 | Method and device for distributing virtual resources based on disk IO |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101389942B (en) * | 2005-12-31 | 2012-05-30 | 通用汽车有限责任公司 | Vehicle email notification using templates |
| US8595289B2 (en) * | 2010-09-21 | 2013-11-26 | Telefonaktiebolaget L M Ericsson (Publ) | Cloud phone with distributed processing |
| CN102857363B (en) * | 2012-05-04 | 2016-04-20 | 运软网络科技(上海)有限公司 | A kind of autonomous management system and method for virtual network |
-
2014
- 2014-11-04 CN CN201410612825.9A patent/CN105634778B/en active Active
-
2015
- 2015-05-26 WO PCT/CN2015/079839 patent/WO2016070609A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1866850A (en) * | 2005-05-18 | 2006-11-22 | 中兴通讯股份有限公司 | Method for H.323 gatekeeper realizing H.323 terminal timely registration |
| CN103838871A (en) * | 2014-03-21 | 2014-06-04 | 北京广利核系统工程有限公司 | Method for checking nuclear power plant safety level DCS S-VDU process file |
| CN104050045A (en) * | 2014-06-27 | 2014-09-17 | 华为技术有限公司 | Method and device for distributing virtual resources based on disk IO |
Non-Patent Citations (1)
| Title |
|---|
| ETSI NFV Management and Orchestration-An Overview;Mehmet Ersue;《IETF #88》;20131031;3,6,7,8 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016070609A1 (en) | 2016-05-12 |
| CN105634778A (en) | 2016-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105634778B (en) | Method and system for realizing VNF instantiation, NFVO and VNFM | |
| CN107689882B (en) | Method and device for service deployment in virtual network | |
| US11272036B2 (en) | API hybrid multi-tenant routing method and system, and API gateway | |
| US10944621B2 (en) | Orchestrator for a virtual network platform as a service (VNPAAS) | |
| US10140112B2 (en) | Update management system and update management method | |
| CN105634780B (en) | Method and device for realizing VNF elastic expansion | |
| US10567196B2 (en) | Decision coordination method, execution apparatus, and decision coordinator | |
| RU2683630C2 (en) | Method for update of nsd network service descriptor and device | |
| WO2016037479A1 (en) | Method, device and system for optimizing virtualized network function (vnf) | |
| CN105429780A (en) | Virtualized network service business automatic generation and dynamic monitoring method | |
| US11687354B2 (en) | Virtual machine management using onboarding operations and openstack control | |
| EP3133771A1 (en) | Virtual machine resource changing method, device and virtual network function device | |
| JPWO2015099035A1 (en) | Management system, virtual communication function management node, and management method | |
| RU2690198C1 (en) | Method of processing network functions virtualization resources and virtualised network function manager | |
| KR20190084294A (en) | Network service lifecycle management approval methods and devices | |
| CN103369038B (en) | Platform serves PaaS management platform and method | |
| CN102916930A (en) | Convergent service network, node thereof and method for acquiring routing information of resource request | |
| WO2018153354A1 (en) | Resource application and vnf instance creation method and apparatus | |
| CN109819023A (en) | Distributed transaction processing method and Related product | |
| US20170054519A1 (en) | Resource Creation Method and Apparatus | |
| CN104092737A (en) | Location-based service middleware method based on cloud technology | |
| CN113032111B (en) | Application migration method, device, system and computer readable storage medium | |
| CN115834600B (en) | Multi-cloud nanotube data synchronization method and device, electronic equipment and storage medium | |
| US20210256600A1 (en) | Connector leasing for long-running software operations | |
| JP2015195519A (en) | flow control device and flow control method |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200825 Address after: No. 68 Bauhinia Road, Ningnan Street, Nanjing City, Jiangsu Province, 210022 Applicant after: Nanjing Zhongxing Software Co.,Ltd. Address before: 518057 Nanshan District Guangdong high tech Industrial Park, South Road, science and technology, ZTE building, Ministry of Justice Applicant before: ZTE Corp. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |