CN107154951B - Virtual network application function unit (VNF) extension management method and device - Google Patents
Virtual network application function unit (VNF) extension management method and device Download PDFInfo
- Publication number
- CN107154951B CN107154951B CN201610118311.7A CN201610118311A CN107154951B CN 107154951 B CN107154951 B CN 107154951B CN 201610118311 A CN201610118311 A CN 201610118311A CN 107154951 B CN107154951 B CN 107154951B
- Authority
- CN
- China
- Prior art keywords
- scaling
- scheme
- vnf
- service
- configuration
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Stored Programmes (AREA)
Abstract
A virtualized network application function (VNF) scale management method, the method comprising: configuring a scaling scheme for the VNF instance; binding a predefined service scene event with a telescopic scheme; and when a predefined service scene event occurs, executing a scaling scheme for binding the service scene event. According to the technical scheme, the service scene event is bound with the VNF scaling scheme, diversified management and unified triggering of VNF scaling actions are achieved, and rapid deployment and flexible adjustment of a VNF instance are completed according to service requirements.
Description
Technical Field
The invention relates to the field of Network Function Virtualization (NFV), in particular to a configuration method and a configuration system.
Background
In order to effectively utilize system resources and reduce operation cost, as shown in fig. 1, a user often deploys a plurality of VNF (Virtual Network function) instances on the same physical resource, and each VNF instance defines a plurality of deployment specifications. According to the change of the service, the VNF instance needs to be flexibly expanded and contracted among different deployment specifications; the conversion between different deployment specifications often requires different scaling actions to be defined. The stretching action is divided into a horizontal direction and a vertical direction, the horizontal direction is stretched in a mode of increasing or reducing the number of the virtual units, and the vertical direction is stretched in a mode of increasing or reducing the number of resources allocated to the virtual units. To accomplish the correct scaling actions, an efficient mechanism is needed to manage the different scaling actions of the same VNF instance.
A service is typically deployed to multiple VNFs, each of which provides a portion of the service functionality. When business expansion and contraction capacity is used, usually, related VNFs are required to be expanded and contracted simultaneously, and due to different types of VNFs and different hardware devices and software products, the expansion and contraction scheme of each VNF is very different, complex and various, and how to provide a set of unified expansion and contraction scheme management mechanism to manage and coordinate the expansion and contraction actions of all related devices is very important.
At present, although the ETSI (European Telecommunications Standards Institute) specification defines an auto _ scale _ policy field in a VNFD (Virtual Network Function Descriptor), there is no description on how to implement diversified management and unified triggering of a VNF scaling action, and rapid deployment and flexible adjustment of a VNF instance cannot be completed according to service requirements.
The invention content is as follows:
the embodiment of the invention provides a configuration method, which is used for meeting the association management requirement of a VNF instance scaling scheme in a complex environment.
To solve the foregoing technical problem, an embodiment of the present invention provides a method for scaling and managing a virtualized network application function unit VNF, where the method includes:
configuring a scaling scheme for the VNF instance;
binding a predefined service scene event with a telescopic scheme;
and when a predefined service scene event occurs, executing a scaling scheme for binding the service scene event.
Optionally, configuring a scaling scheme for the VNF instance includes:
configuring a deployment specification for the VNF instance;
configuring a scaling scheme for the VNF instance according to the deployment specification.
Optionally, the number of the deployment specifications of the VNF instance configuration is two or more;
the number of the scaling schemes configured by the VNF example is one or more than one.
Alternatively,
the binding of the predefined service scenario event with the scaling scheme comprises:
predefined business scenario events are bound to one or more scaling schemes.
Alternatively,
the scaling scheme of the VNF instance configuration comprises the following steps: and switching between any two different deployment specifications in the deployment specifications of the VNF instance configuration.
Optionally, before the predefined service scenario event is bound to the scaling scheme, the method further includes:
determining service requirements according to service data collected regularly, and predefining service scene events according to the service requirements.
An embodiment of the present invention further provides a virtual network application function unit VNF scaling management apparatus, where the apparatus includes:
a configuration module, configured to configure a scaling scheme for the VNF instance;
the binding module is used for binding the predefined service scene event with the telescopic scheme;
and the execution module is used for executing the flexible scheme bound by the binding module when a predefined service scene event occurs.
Optionally, the configuration module includes:
a first configuration submodule, configured to configure a deployment specification for the VNF instance;
and the second configuration submodule is used for configuring a scaling scheme for the VNF instance according to the deployment specification configured by the first configuration submodule.
Optionally, the number of the deployment specifications of the VNF instance configuration is two or more;
the number of the scaling schemes configured by the VNF example is one or more than one.
Alternatively,
the binding module is configured to bind the predefined service scenario event with the scaling scheme specifically:
predefined business scenario events are bound to one or more scaling schemes.
Optionally, the scaling scheme of the second configuration sub-module configuration includes: and switching between any two different deployment specifications in the deployment specifications configured by the first configuration submodule.
Optionally, the configuration module is further configured to determine a service requirement according to the service data collected periodically, and predefine a service scenario event according to the service requirement.
According to the technical scheme, the service scene event is bound with the VNF scaling scheme, diversified management and unified triggering of VNF scaling actions are achieved, and rapid deployment and flexible adjustment of a VNF instance are completed according to service requirements.
Meanwhile, the embodiment of the invention can realize the management of a plurality of different scaling actions of the same VNF instance and can also finish the management of the associated scaling actions of a plurality of different VNF instances triggered by the same service scene event.
Drawings
FIG. 1 is a diagram of a NFV system architecture in the prior art;
FIG. 2 is a flowchart illustrating a configuration method according to a first embodiment;
FIG. 3 is another flow chart of a configuration method according to one embodiment;
FIG. 4 is a schematic configuration diagram according to a second embodiment;
FIG. 5 is a schematic configuration diagram according to a third embodiment;
FIG. 6 is a schematic structural diagram of a configuration device according to a fourth embodiment;
fig. 7 is another schematic structural diagram of a configuration device in the fourth embodiment.
Detailed Description
To make the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application 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.
Example one
As shown in fig. 2, a virtualized network application function unit VNF scaling management method includes:
step S10: configuring a scaling scheme for the VNF instance;
step S12: binding a predefined service scene event with a telescopic scheme;
step S13: and when a predefined service scene event occurs, executing a scaling scheme for binding the service scene event.
Alternatively, step S11 may be implemented by:
firstly, configuring a deployment specification for a VNF instance; and then configuring a scaling scheme for the VNF instance according to the deployment specification.
Alternatively,
in this embodiment, the number of deployment specifications configured by the VNF instance is two or more; the number of the scaling schemes configured by the VNF instance is one or more than one.
Optionally, predefined service scenario events will be bound to one or more scaling schemes in step S12.
Alternatively,
the scaling scheme of the VNF instance configuration comprises the following steps: switching between any two different deployment specifications of the VNF instance configuration.
For example, the deployment specifications of the service deployment in the VNF instance configuration include F1, F2, F2;
the scaling scheme of the VNF may be that the deployment specification F1 switches to the deployment specification F2; or the deployment specification F2 is switched to the deployment specification F3; it may also be that deployment specification F3 switches to deployment specification F1.
Optionally, as shown in fig. 3, step S12 is preceded by:
step S11: determining service requirements according to service data collected regularly, and predefining service scene events according to the service requirements.
The execution of step S11 and step S10 is not limited to a sequential order.
Example two
The technical solution of the present application is further explained below.
According to the embodiment, different deployment specifications and scaling schemes can be defined for the VNF instance according to different scenarios. A telescoping scheme can comprise a telescoping action, and can also comprise a plurality of telescoping actions (including two latitudes including a transverse latitude and a longitudinal latitude), and can define the telescoping action in one latitude, and can also define the telescoping actions in a plurality of latitudes.
And defining a scene event according to the service requirement, and binding different scaling schemes.
The method comprises the steps of acquiring the expansion and contraction requirements of the service by monitoring some key parameters (such as the number of registered users) on the service in real time, generating a scene event according to the expansion and contraction requirements, triggering a corresponding bound expansion and contraction scheme, and executing a formulated expansion and contraction action.
The configuration scheme of the VNF instance scaling scheme of this embodiment is mainly performed from the following aspects:
firstly, establishing VNF instance deployment specification
Depending on the business requirements, a VNF instance may have a number of different deployment specifications.
For example: when the load-carrying service increases, an initial deployment specification F1 of a VNF instance may need to be expanded, and a deployment specification F2 is switched to operate.
Second, establishing a VNF expansion scheme
And configuring a scaling scheme for the VNF instance according to business needs.
A scaling scheme may be formulated for one VNF instance, or multiple scaling schemes may be formulated. A telescoping scheme may define one telescoping action or multiple telescoping actions. Meanwhile, the telescopic action in one latitude can be defined, and the telescopic actions in a plurality of latitudes can also be defined.
Example 1:
the VNF templates, if 3 deployment specifications are defined, F1, F2, F3. The scaling scheme for a VNF instance may be defined as follows:
telescoping scheme P1: switching from deployment specification F1 to deployment specification F2;
telescoping scheme P2: switching from deployment specification F2 to deployment specification F3;
telescoping scheme P3: switching from deployment specification F3 to deployment specification F1;
each of the above configuration schemes defines a scaling action. In other configurations, a telescoping scheme may also define multiple telescoping actions.
Defining business scene event
When the service changes, a service scenario event is defined, and the event can be used as a trigger event of the VNF instance scaling scheme.
Service data (such as the number of registered users) can be collected periodically, service requirements can be determined according to the collected information, and service scene events can be generated.
The service scenario event related in this embodiment may have various expressions, may be an event type, may also be a notification message, and may also be any other concept that may represent a scenario (or a change, or a phenomenon).
Fourth, binding a VNF scaling scheme for the scene event
And binding a VNF scaling scheme for the business scenario event. When an event occurs, the corresponding VNF instance scaling scheme can be triggered to complete the drawn-up scaling action.
For example: as shown in fig. 4, the deployment specification of VNF instance is F1, F2;
configuring the scaling scheme for the VNF as P1: deployment specification F1 switches to F2.
The service scenario event E1 may be bound to a scaling scheme P1.
Under this configuration, if the traffic scenario E1 is triggered, the scaling scheme P1 is executed, i.e., a switch is made from the deployment specification F1 to F2.
The embodiment of the invention can trigger the implementation of the telescoping scheme in the following ways:
in the first mode, relevant key parameters are monitored on an NFVO (Network Function Virtualization architecture), a service scene event is generated, and a scaling scheme is triggered to execute.
In the second mode, relevant key parameters are monitored on a VNFM (Virtualized Network Function Manager), a service scene event is generated, and a scaling scheme is triggered to execute.
And thirdly, detecting corresponding parameters in the VNF according to the defined related scaling scheme, generating a service scene event, triggering strategy execution, and completing the scaling action.
And in the fourth mode, the VNF key parameters are independently monitored through the NFVO, the VNFM and other equipment except the VNF, a business scene event is generated, and the execution of the scaling scheme is triggered.
EXAMPLE III
The technical solution of the present application is further described below with reference to specific scenarios.
As shown in fig. 5, service S1 is deployed to 3 VNF instances: VNF1, VNF2, VNF3 (possibly the same type of VNF, and possibly different types of VNFs).
VNF1 has telescoping scheme P11, P12, P13;
VNF2 has telescoping solutions P21, P22;
VNF3 has telescoping schemes P31, P32.
When the service S1 is scaled, it is necessary to simultaneously execute the scaling scheme P11 of VNF1, the scaling scheme P21 of VNF2, and the scaling scheme P31 of VNF 3.
The scaling scheme management mechanism may be formulated as follows:
1. a business scenario event E1 is defined.
2. The business scenario event E1 is bound to a scaling scheme P11 of VNF1, a scaling scheme P21 of VNF2, and a scaling scheme P31 of VNF 3.
3. When the business scenario event E1 occurs, the scaling scheme P11 of VNF1, the scaling scheme P21 of VNF2, and the scaling scheme P31 of VNF3 are triggered simultaneously, and the respective scaling plans are completed.
Example four
As shown in fig. 6, this embodiment provides a virtualized network application function unit VNF scaling management apparatus, where the apparatus includes:
a configuration module 11, configured to configure a scaling scheme for the VNF instance;
a binding module 12, configured to bind a predefined service scenario event with a scaling scheme;
and the execution module 13 is configured to execute the scaling scheme bound by the binding module when a predefined service scenario event occurs.
Alternatively, as shown in fig. 7, the configuration module 11 includes:
a first configuration submodule 111, configured to configure a deployment specification for the VNF instance;
a second configuration submodule 112, configured to configure a scaling scheme for the VNF instance according to the deployment specification configured by the first configuration submodule.
Alternatively,
the number of the deployment specifications of the VNF instance configuration is two or more;
the number of the scaling schemes configured by the VNF example is one or more than one.
Alternatively,
the binding module 12 is configured to bind the predefined service scenario event with the scaling scheme, specifically:
predefined business scenario events are bound to one or more scaling schemes.
Alternatively,
the scaling scheme of the second configuration sub-112 module configuration comprises: and switching between any two different deployment specifications in the deployment specifications configured by the first configuration submodule.
Alternatively,
the configuration module 11 is further configured to determine a service requirement according to the service data collected periodically, and predefine a service scenario event according to the service requirement.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. 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. It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits, and accordingly, each module/module in the foregoing embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present application is not limited to any specific form of hardware or software combination.
Claims (10)
1. A virtualized network application function (VNF) scaling management method, the method comprising:
determining a service requirement according to service data collected regularly, and predefining a service scene event according to the service requirement;
configuring a scaling scheme for a predefined business scenario event for a VNF instance;
binding a predefined service scene event with a telescopic scheme;
and when a predefined service scene event occurs, executing a scaling scheme for binding the service scene event.
2. The method of claim 1, wherein:
the configuring the scaling scheme for the VNF instance includes:
configuring a deployment specification for the VNF instance;
configuring a scaling scheme for the VNF instance according to the deployment specification.
3. The method of claim 1 or 2, wherein:
the number of the deployment specifications of the VNF instance configuration is two or more;
the number of the scaling schemes configured by the VNF example is one or more than one.
4. The method of claim 3, wherein:
the binding of the predefined service scenario event with the scaling scheme comprises:
predefined business scenario events are bound to one or more scaling schemes.
5. The method of claim 4, wherein:
the scaling scheme of the VNF instance configuration comprises the following steps: and switching between any two different deployment specifications in the deployment specifications of the VNF instance configuration.
6. A virtualized network application function (VNF) scaling management apparatus, the apparatus comprising:
the configuration module is used for determining a service requirement according to service data collected regularly, predefining a service scene event according to the service requirement and configuring a telescopic scheme for the service requirement predefined service scene event for the VNF instance;
the binding module is used for binding the predefined service scene event with the telescopic scheme;
and the execution module is used for executing the flexible scheme bound by the binding module when a predefined service scene event occurs.
7. The apparatus of claim 6, wherein:
the configuration module includes:
a first configuration submodule, configured to configure a deployment specification for the VNF instance;
and the second configuration submodule is used for configuring a scaling scheme for the VNF instance according to the deployment specification configured by the first configuration submodule.
8. The apparatus of claim 7, wherein:
the number of the deployment specifications of the VNF instance configuration is two or more;
the number of the scaling schemes configured by the VNF example is one or more than one.
9. The apparatus of claim 8, wherein:
the binding module is configured to bind the predefined service scenario event with the scaling scheme specifically:
predefined business scenario events are bound to one or more scaling schemes.
10. The apparatus of claim 9, wherein:
the scaling scheme of the second configuration submodule configuration comprises: and switching between any two different deployment specifications in the deployment specifications configured by the first configuration submodule.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610118311.7A CN107154951B (en) | 2016-03-02 | 2016-03-02 | Virtual network application function unit (VNF) extension management method and device |
| PCT/CN2017/074441 WO2017148321A1 (en) | 2016-03-02 | 2017-02-22 | Virtual network feature (vnf) scaling management method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610118311.7A CN107154951B (en) | 2016-03-02 | 2016-03-02 | Virtual network application function unit (VNF) extension management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107154951A CN107154951A (en) | 2017-09-12 |
| CN107154951B true CN107154951B (en) | 2020-10-02 |
Family
ID=59743557
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610118311.7A Active CN107154951B (en) | 2016-03-02 | 2016-03-02 | Virtual network application function unit (VNF) extension management method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107154951B (en) |
| WO (1) | WO2017148321A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10826789B2 (en) | 2018-12-27 | 2020-11-03 | At&T Intellectual Property I, L.P. | Adjusting triggers for automatic scaling of virtual network functions |
| US11388109B2 (en) | 2019-12-05 | 2022-07-12 | At&T Intellectual Property I, L.P. | Hierarchical capacity management in a virtualization environment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104601492A (en) * | 2014-12-29 | 2015-05-06 | 上海华为技术有限公司 | Method and device for controlling business flow under NFV framework |
| CN105262664A (en) * | 2014-06-09 | 2016-01-20 | 诺基亚通信公司 | Controlling of virtualized network functions for usage in communication network |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140007097A1 (en) * | 2012-06-29 | 2014-01-02 | Brocade Communications Systems, Inc. | Dynamic resource allocation for virtual machines |
| EP2849064B1 (en) * | 2013-09-13 | 2016-12-14 | NTT DOCOMO, Inc. | Method and apparatus for network virtualization |
| CN104980297A (en) * | 2014-04-14 | 2015-10-14 | 中兴通讯股份有限公司 | Virtual machine resource changing method and device, and virtualized network function device |
| US20150381423A1 (en) * | 2014-06-26 | 2015-12-31 | Futurewei Technologies, Inc. | System and Method for Virtual Network Function Policy Management |
-
2016
- 2016-03-02 CN CN201610118311.7A patent/CN107154951B/en active Active
-
2017
- 2017-02-22 WO PCT/CN2017/074441 patent/WO2017148321A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105262664A (en) * | 2014-06-09 | 2016-01-20 | 诺基亚通信公司 | Controlling of virtualized network functions for usage in communication network |
| CN104601492A (en) * | 2014-12-29 | 2015-05-06 | 上海华为技术有限公司 | Method and device for controlling business flow under NFV framework |
Non-Patent Citations (2)
| Title |
|---|
| B andwidth Guaranteed Virtual Network Function;Fangxin Wang等;<2015 IEEE 34th International Performance Computing and Communications Conference (IPCCC)>;20151216;全文 * |
| Realizing Network Function Virtualization Management and Orchestration with Model Based Open Architecture;YuLing Chen等;<2015 11th International Conference on Network and Service Management (CNSM)>;20151113;第410页-第417页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107154951A (en) | 2017-09-12 |
| WO2017148321A1 (en) | 2017-09-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11029994B2 (en) | Service creation and management | |
| US20190123963A1 (en) | Method and apparatus for managing resources of network slice | |
| US10644952B2 (en) | VNF failover method and apparatus | |
| US10917294B2 (en) | Network function instance management method and related device | |
| US10541858B2 (en) | Thin client system, management server, workplace environment setting method and workplace environment setting program | |
| CN103559055A (en) | Activity starting method and device applied to Android platform | |
| CN103019746A (en) | Software interaction control method and system based on Android platform | |
| CN109614164B (en) | Method, device and equipment for realizing configurable plug-in and readable storage medium | |
| CN107154951B (en) | Virtual network application function unit (VNF) extension management method and device | |
| CN111797173B (en) | Alliance chain sharing system, method and device, electronic equipment and storage medium | |
| CN111371608B (en) | Method, device and medium for deploying SFC service chain | |
| CN103810040A (en) | Information processing method and electronic equipment | |
| CN105426232A (en) | Interface processing method and apparatus | |
| CN111092828B (en) | Network operation method, device, equipment and storage medium | |
| CN105208537B (en) | A kind of call forwarding method for inquiring status and system | |
| CN104615426A (en) | Method, device and terminal for operating multiple systems | |
| CN108681494B (en) | Backup data restoration method and device, user equipment and storage medium | |
| US20220291958A1 (en) | Mobile phone operating system for minors and its architecture and ecological development method | |
| CN107786382B (en) | Interface selection method and device, test console and test system | |
| CN108681492A (en) | Data processing method and device | |
| CN108762786A (en) | A kind of firmware update of server cabinet, server cabinet and host | |
| CN102929657A (en) | Internal memory data sharing method, device and system | |
| CN110347473B (en) | Method and device for distributing virtual machines of virtualized network elements distributed across data centers | |
| CN106529280A (en) | Method and device for controlling VPN application of mobile equipment | |
| CN112532532A (en) | Service returning method, device, equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200901 Address after: 210012 Nanjing, Yuhuatai District, South Street, Bauhinia Road, No. 68 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 |