CN114513424A

CN114513424A - Network service expansion and contraction processing method, device, equipment and readable storage medium

Info

Publication number: CN114513424A
Application number: CN202011154080.8A
Authority: CN
Inventors: 陈少凡; 张晓儒
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2020-10-26
Filing date: 2020-10-26
Publication date: 2022-05-17

Abstract

The invention discloses a method, a device and equipment for processing network service expansion and contraction capacity and a readable storage medium, and relates to the technical field of communication, so as to ensure that NS instances successfully execute expansion and contraction capacity operation. The method comprises the following steps: receiving a capacity expansion and reduction operation request, wherein the capacity expansion and reduction operation request comprises information of a VNF instance to be subjected to capacity expansion and reduction operation and information of an NS instance triggering the capacity expansion and reduction operation of the VNF instance; inquiring operation record information of the VNF instance and scaling strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance to obtain an inquiry result; and in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance. The embodiment of the invention can ensure that the NS instance successfully executes the capacity expansion and reduction operation.

Description

Network service expansion and contraction processing method, device, equipment and readable storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for processing network service scaling.

Background

Traditional network equipment manufacturers are customized based on specific specification equipment and specific technical requirements, the maintenance and updating processes of the equipment are complex, and the operation cost of service popularization is high. In order to reduce the complexity and cost of network deployment and service popularization, the cost brought by equipment upgrading can be effectively reduced and the deployment of new services is accelerated by a mode of realizing software and hardware decoupling based on a general hardware platform. NFV (Network Function Virtualization) is proposed based on the above background.

The NFV realizes the management function of the core cloud by a MANO system and a network management system. The MANO system includes three major components, namely, NFVO (Network Functions Virtualization Orchestrator), VNFM (Virtualized Network Function Manager), VIM (Virtualized Infrastructure Manager), and the main Functions include lifecycle management of Network elements, creation of images required by the Network elements, management of templates and software required by the Network elements, and allocation and management of Network resources. Wherein:

NFVO: the method is used for unified scheduling of resources, creating a VNF (virtual Network Function) automatic scaling strategy, providing specification configuration parameters of the instantiated VNF and the like;

VNFM: the VNF management module is responsible for VNF lifecycle management, such as parsing and processing of VNFD (Virtualized Network Function Descriptor), initialization of VNF instance, and scaling of VNF;

VIM: and the system is responsible for scheduling and managing hardware resources and virtualized resources.

After the introduction of SDN (Software Defined Network) technology by NFV, VNF deployment and management tend to be automated. In the SDN scenario, the MANO system defines the concept of NS (Network Service): an NS instance is a specific network service that includes one or more VNFs, and the network service instance has functionality cooperatively provided by the VNFs it includes. Each NS instance is created based on its template NSD (Network Service Descriptor). The NSD may include VNF packages based on which each VNF instance within the NS instance is created, network configuration information of the VNF, and related information collected by VNF signaling.

In the prior art, an NS instance is composed of one or more VNF instances and associated network connectivity resources (Virtual links). The phenomenon that the same VNF instance is multiplexed among different NS instances to complete service bearing tasks exists. Due to the phenomenon that multiple NS instances multiplex the same VNF instance, an operation conflict may occur when a manual scale-up operation on the VNF instance is triggered by different NS instances. The prior art approach to handling such operation conflicts will result in the NS instance being unable to perform the scale and shrink operations.

Disclosure of Invention

The embodiment of the invention provides a method, a device and equipment for processing network service expansion and contraction capacity and a readable storage medium, which are used for ensuring that an NS instance successfully executes the expansion and contraction capacity operation.

In a first aspect, an embodiment of the present invention provides a network service capacity expansion processing method, applied to NFVO, where the method includes:

receiving a capacity expansion and reduction operation request, wherein the capacity expansion and reduction operation request comprises information of a VNF instance to be subjected to capacity expansion and reduction operation and information of an NS instance triggering the capacity expansion and reduction operation of the VNF instance;

inquiring operation record information of the VNF instance and scaling strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance to obtain an inquiry result;

and in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance.

Wherein, the querying, according to the information of the VNF instance and the information of the NS instance, the operation record information of the VNF instance and the scaling policy record information of the VNF instance to obtain a query result includes:

inquiring the scaling strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance, and determining whether the NS instance has the authority of scaling operation on the VNF instance;

determining whether the VNF instance is in a capacity expansion state or not under the condition that the NS instance has the right of carrying out capacity expansion and reduction operation on the VNF instance;

determining whether an operation record exists in operation record information of the VNF instance when the VNF instance is not in a scale-up state.

Wherein the method further comprises:

under the condition that the VNF instance is in a capacity expansion and reduction state, storing the related information of the capacity expansion and reduction operation request into operation record information of the VNF instance;

wherein the related information of the capacity expansion operation request comprises at least one of the following information:

operation sequence number, target VNF, NS instance record NSR, timestamp, target service carrying capacity, priority.

Wherein the method further comprises:

storing the related information of the capacity expansion and contraction operation request into the operation record information of the VNF instance when the operation record exists in the operation record information of the VNF instance;

operation sequence number, target VNF, NSR, timestamp, target service carrying capacity, priority.

Wherein the method further comprises:

integrating operation records in the operation record information of the VNF instance;

and sequencing the integrated operation records according to the priority of the NS instance to which the VNF instance belongs.

Wherein the integrating operation records in the operation record information of the VNF instance includes:

acquiring NS instance records corresponding to the VNF instances and corresponding target service carrying capacity according to the operation record information of the VNF instances;

acquiring the required service load capacity of the VNF instance in all the NS instances to which the VNF instance belongs according to the NS instance record and the scaling strategy record information of the VNF instance;

determining a minimum traffic bearing capacity threshold of the VNF instance;

and deleting the operation record of which the target service bearing capacity is smaller than the minimum service bearing capacity threshold value from the operation record information of the VNF instance.

Wherein the determining a minimum traffic bearer capability threshold of the VNF instance comprises:

acquiring service bearing relations among all NS instances to which the VNF instances belong according to the service bearing relation information of the VNF instances;

and determining the minimum service carrying capacity threshold of the VNF instance according to the service carrying capacity required by the VNF instance in all the NS instances to which the VNF instance belongs and the service carrying relationship.

Wherein the determining a minimum traffic bearer capability threshold of the VNF instance according to the traffic load capabilities required by the VNF instance in all NS instances to which the VNF instance belongs and the traffic bearer relationship includes:

if all the service bearing relations are cumulative, the minimum service bearing capacity threshold of the VNF instance is the sum of the service load capacities of the VNF instances required in all the NS instances to which the VNF instances belong;

if all the service bearing relations are shared, the minimum service bearing capacity threshold value of the VNF instance is the maximum value of the service bearing capacity required by the VNF instance in all the NS instances to which the VNF instance belongs;

if the service bearing relationship comprises sharing and accumulation, calculating the sum of the service load capacities required by the VNF instances in the first NS instance to which the VNF instances belong to obtain a first value, and determining the maximum value of the service load capacity required by the VNF instances in the second NS instance to which the VNF instances belong to obtain a second value; taking the sum of the first value and the second value as a minimum traffic bearer capability threshold of the VNF instance; and the service bearing relationship between the first NS instance and the second NS instance is shared.

Wherein, in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance includes:

and when no operation record exists in the operation record information of the VNF instance, or when an operation record exists in the operation record information of the VNF instance, performing capacity expansion and reduction operation on the VNF instance according to the priority of the NS instance.

Wherein, when there is an operation record in the operation record information of the VNF instance, executing a capacity expansion and reduction operation on the VNF instance according to the priority of the NS instance, includes:

and executing the capacity expansion and reduction operation on the VNF instance according to the sequence of the NS instance from high priority to low priority.

Wherein, before the receiving the request for the operation of expanding and contracting the volume, the method further comprises:

and generating operation record information of the VNF instance, scaling strategy record information of the VNF instance and service bearing relation information of the VNF instance.

Wherein the generating operation record information of the VNF instance, scaling policy record information of the VNF instance, and service bearer relationship information of the VNF instance includes:

acquiring initial operation record information, initial scaling strategy record information and initial service bearing relation information which are sent by a user;

creating an NS instance record;

storing the NS instance record into the initial scaling strategy record information and the initial service bearing relationship information;

and storing the VNF instance record into the initial scale and reduction capacity strategy record information and the initial service bearing relation information through an instantiation NS process.

In a second aspect, an embodiment of the present invention further provides a network service scaling processing apparatus, applied to NFVO, including:

a first receiving module, configured to receive a capacity expansion and reduction operation request, where the capacity expansion and reduction operation request includes information of a VNF instance to be subjected to capacity expansion and reduction operation and information of an NS instance that triggers execution of a capacity expansion and reduction operation of the VNF instance;

the first query module is used for querying the operation record information of the VNF instance and the scaling strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance to obtain a query result;

a first processing module, configured to, if the query result indicates that a capacity expansion and reduction operation is allowed to be performed on the VNF instance, perform a capacity expansion and reduction operation on the VNF instance.

Wherein the first query module comprises:

the first query submodule is used for querying the capacity expansion and reduction strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance, and determining whether the NS instance has the authority of capacity expansion and reduction operation on the VNF instance;

a first determining submodule, configured to determine whether the VNF instance is in a capacity expansion and reduction state if the NS instance has a right to perform a capacity expansion and reduction operation on the VNF instance;

a second determining sub-module, configured to determine whether an operation record exists in operation record information of the VNF instance when the VNF instance is not in a scale-up/scale-down state.

Wherein the apparatus further comprises:

a first storage module, configured to store, when the VNF instance is in a capacity expansion and reduction state, relevant information of the capacity expansion and reduction operation request in operation record information of the VNF instance;

Wherein the apparatus further comprises:

a second storage module, configured to, when an operation record exists in operation record information of the VNF instance, store information related to the scaling operation request in the operation record information of the VNF instance;

Wherein the apparatus further comprises:

the integration module is used for integrating the operation records in the operation record information of the VNF instance;

and the sequencing module is used for sequencing the integrated operation records according to the priority of the NS instance to which the VNF instance belongs.

Wherein the integration module comprises:

the first obtaining sub-module is used for obtaining an NS instance record corresponding to the VNF instance and a corresponding target service carrying capacity according to the operation record information of the VNF instance;

a second obtaining sub-module, configured to obtain, according to the NS instance record and the scaling policy record information of the VNF instance, a service load capacity required by the VNF instance in all NS instances to which the VNF instance belongs;

a first determining submodule, configured to determine a minimum traffic bearer capability threshold of the VNF instance;

and the first deletion submodule is used for deleting the operation record of which the target service bearing capacity is smaller than the minimum service bearing capacity threshold from the operation record information of the VNF instance.

Wherein the first determination submodule includes:

a first determining unit, configured to obtain, according to the service bearer relationship information of the VNF instance, a service bearer relationship between all NS instances to which the VNF instance belongs;

a second determining unit, configured to determine a minimum traffic load capacity threshold of the VNF instance according to the traffic load capacity required by the VNF instance in all NS instances to which the VNF instance belongs and the traffic load relationship.

Wherein the second determination unit includes:

a first determining subunit, configured to determine, if all the traffic bearer relationships are cumulative, that a minimum traffic bearer capability threshold of the VNF instance is a sum of traffic load capabilities required by the VNF instance in all the NS instances to which the VNF instance belongs;

a second determining subunit, configured to, if all the traffic bearer relationships are shared, set a minimum traffic bearer capability threshold of the VNF instance to a maximum value of traffic bearer capabilities required by the VNF instance in all the NS instances to which the VNF instance belongs;

a third determining subunit, configured to, if the traffic bearer relationship includes sharing and accumulation, calculate a sum of traffic load capacities required by the VNF instance in the first NS instance to which the VNF instance belongs, to obtain a first value, and determine a maximum value of the traffic load capacities required by the VNF instance in the second NS instance to which the VNF instance belongs, to obtain a second value; taking the sum of the first value and the second value as a minimum traffic bearer capability threshold of the VNF instance; and the service bearing relationship between the first NS instance and the second NS instance is shared.

The first processing module is configured to, when no operation record exists in the operation record information of the VNF instance, or when an operation record exists in the operation record information of the VNF instance, execute a capacity expansion and reduction operation on the VNF instance according to the priority of the NS instance.

The first processing module is configured to, when an operation record exists in the operation record information of the VNF instance, execute a scaling operation on the VNF instance according to an order from high to low of a priority of the NS instance.

Wherein the apparatus further comprises:

a generating module, configured to generate operation record information of the VNF instance, scaling policy record information of the VNF instance, and service bearing relationship information of the VNF instance.

Wherein the generating module comprises:

the first obtaining submodule is used for obtaining initial operation record information, initial scaling strategy record information and initial service bearing relation information which are sent by a user;

a first creating submodule for creating an NS instance record;

a first storage submodule, configured to store the NS instance record in the initial scaling policy record information and the initial service bearer relationship information;

and the second storage submodule is used for storing the VNF instance record into the initial scaling strategy record information and the initial service bearing relation information through an instantiation NS process.

In a third aspect, an embodiment of the present invention provides a network service scaling processing apparatus, applied to NFVO, including: a processor and a transceiver;

the transceiver is configured to receive a capacity expansion and reduction operation request, where the capacity expansion and reduction operation request includes information of a VNF instance to be subjected to capacity expansion and reduction operation and information of an NS instance triggering execution of capacity expansion and reduction operation of the VNF instance;

the processor is configured to query, according to the information of the VNF instance and the information of the NS instance, operation record information of the VNF instance and scaling policy record information of the VNF instance to obtain a query result; and in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance.

Wherein the processor is further configured to:

inquiring the capacity expansion and contraction strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance, and determining whether the NS instance has the permission of capacity expansion and contraction operation on the VNF instance;

Wherein the processor is further configured to:

wherein, the related information of the capacity expansion operation request comprises at least one of the following information:

Wherein the processor is further configured to:

determining a minimum traffic bearing capacity threshold of the VNF instance;

Wherein the processor is further configured to:

if the service bearing relationship comprises sharing and accumulation, calculating the sum of the service load capacities required by the VNF instance in the first NS instance to which the VNF instance belongs to obtain a first value, and determining the maximum value of the service load capacities required by the VNF instance in the second NS instance to which the VNF instance belongs to obtain a second value; taking the sum of the first value and the second value as a minimum traffic bearer capability threshold of the VNF instance; and the service bearing relationship between the first NS instance and the second NS instance is shared.

Wherein the processor is further configured to:

and when the operation record exists in the operation record information of the VNF instance, carrying out capacity expansion and reduction operation on the VNF instance according to the sequence of the NS instance from high priority to low priority.

Wherein the processor is further configured to:

creating an NS instance record;

In a fourth aspect, an embodiment of the present invention further provides an electronic device, including: the network service scale and volume processing method comprises a transceiver, a memory, a processor and a program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the steps of the network service scale and volume processing method.

In a fifth aspect, an embodiment of the present invention further provides a readable storage medium, where the readable storage medium stores a program, and the program, when executed by a processor, implements the steps in the network service scaling processing method described above.

In the embodiment of the present invention, according to information of a virtualized network function VNF instance to be subjected to a capacity expansion and reduction operation in a capacity expansion and reduction operation request and information of a network service NS instance that triggers execution of a capacity expansion and reduction operation of the VNF instance, operation record information of the VNF instance and capacity expansion and reduction policy record information of the VNF instance are queried to obtain a query result. And in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance. By the scheme of the embodiment of the invention, whether the capacity expansion and reduction operation can be executed on the VNF instance can be determined by combining the operation record information of the VNF instance and the capacity expansion and reduction strategy record information of the VNF instance, so that the capacity expansion and reduction operation request is not required to be directly rejected when operation conflict occurs like in the prior art, and further the NS instance can be ensured to successfully execute the capacity expansion and reduction operation by utilizing the scheme of the embodiment of the invention.

Drawings

Fig. 1 is a flowchart of a network service scaling processing method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an NS instance multiplexing VNF according to an embodiment of the present invention;

FIG. 3 is a second schematic diagram of an NS instance multiplexing VNF in accordance with an embodiment of the present invention;

fig. 4 is a second flowchart of a network service scaling processing method according to an embodiment of the present invention;

FIG. 5 is a schematic process diagram of an embodiment of the invention in which an NFVO automatically processes a table of operation records of the scale-up operation;

FIG. 6 is a schematic diagram of a process for creating an NSR in an embodiment of the present invention;

FIG. 7 is a diagram illustrating the process of NS instantiation in an embodiment of the present invention;

FIG. 8 is a diagram illustrating the relationship between tables and flows in an embodiment of the present invention;

fig. 9 is one of the structural diagrams of the network service capacity expansion processing apparatus according to the embodiment of the present invention;

fig. 10 is a second block diagram of a network service scaling processing apparatus according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

Referring to fig. 1, fig. 1 is a flowchart of a network service scaling processing method provided by an embodiment of the present invention, which is applied to NFVO, and as shown in fig. 1, includes the following steps:

step 101, receiving a capacity expansion and reduction operation request, wherein the capacity expansion and reduction operation request comprises information of a VNF instance to be subjected to capacity expansion and reduction operation and information of an NS instance triggering the capacity expansion and reduction operation of the VNF instance.

When the capacity expansion and contraction operation needs to be executed, a user can select a VNF instance in a certain NS instance (the VNF instance may be multiplexed by other NS instances at the same time) in the NFVO operation interface, and trigger NS manual capacity expansion (VNF manual capacity expansion-increase/decrease of a VM (Virtual Machine)) operation. At this time, NFVO is equivalent to receiving a request for a scaling operation sent by a user.

The information of the VNF instance may be a Virtualized Network Function Record (VNFR) of the VNF instance, and the information of the NS instance may be a Network Service Record (NSR) of the NS.

And 102, inquiring the operation record information of the VNF instance and the scaling strategy record information of the VNF instance according to the information of the VNF instance and the information of the NS instance to obtain an inquiry result.

In the embodiment of the present invention, operation record information, capacity expansion and contraction policy record information, and the like are set. Since a VNF may be multiplexed by multiple NS instances, when an NS instance is to perform a scaling operation on it, the VNF may be in a lifecycle operation state, i.e., in a scaling state. At this point, the scaling operation of the NS instance on the VNF may not be performed immediately. However, in the embodiment of the present invention, the operation of the NS instance is stored in the operation record information, so that the operation of the NS instance on the VNF can be performed at an appropriate time.

In practical applications, the operation record information may be a manual capacity expansion and contraction operation record table, as shown in table 1.

TABLE 1

In table 1:

operation _ Number: indicating the sequence number of the scale and shrink operations.

Timestamp: indicating the triggering time of the capacity expansion and contraction operation.

Target _ VNF: a target VNF representing a scale operation.

Target _ Load: and the service carrying capacity of the target VNF after the capacity expansion and reduction operation is finished is represented.

Trigger _ NS _ Instance: information representing the instance of the NS that triggered the scale operation.

Wherein, NSR: representing NS instance records.

Priority: indicating the priority of the NS instance.

The scaling policy record information may be a VNF scaling policy record table, as shown in table 2:

TABLE 2

In table 2:

VNF _ Name: showing the name of the instance.

VNFR: representing VNF instance records.

Operation _ Type: indicating the type of the operation of expanding and reducing the volume.

Wherein, Type-1: and allowing all NS instances multiplexing the VNF instances to perform capacity expansion and reduction operations on the NS instances. The order of operations is determined by the Priority (Priority) of the NS instance;

type-2: the NS instance that defines part of the reuse of the VNF instance may perform a scale and shrink operation on the VNF (Permission is required to be true). An NS instance having an operation authority, an operation order being determined by a Priority (Priority) of the NS instance;

type-3: and in all the NS instances multiplexing the VNF instance, the NS instance which meets the condition that Permission is true and Priority is higher than a certain threshold value can perform capacity expansion and contraction operation on the VNF instance.

Related NS Instance: information about the NS instance that multiplexes this VNF instance is defined.

Wherein, NS Name: representing the NS instance name.

NSR: representing NS instance records.

Load Requirement (service carrying capacity Requirement): represents a minimum data capacity (e.g., CAPS) threshold requirement for the VNF instance by the NS instance;

priority (Priority): and according to the importance degree of the NS instance, determining the priority of the NS instance for carrying out the capacity expansion and reduction operation on the VNF instance. The higher the degree of importance, the higher the priority.

Permission: whether the NS instance is allowed to scale the multiplexed VNF instance.

In addition, the embodiment of the present invention further defines service bearing relationship information, for example, the information may be embodied by a service bearing relationship record table. The service bearing information is used for embodying a service bearing relation between a certain NS instance and other NS instances multiplexing the same VNF. Specifically, the service bearer relationship record table may be as shown in table 3:

TABLE 3

In table 3:

NS Name: representing the NS instance name.

NSR: representing NS instance records.

Re-used VNF: indicating the relevant information of all VNF instances that contain this NS instance multiplex. One NS instance may multiplex one or more VNF instances.

VNF Name: indicating the name of the VNF instance being multiplexed.

VNFR: representing the multiplexed VNF instance records.

Used-relation with other NS: indicating a multiplexing relationship with other NS instances that multiplex the VNF instance. In the embodiment of the present invention, there are two relationships:

(1) accumulative: in this mode, the minimum service carrying capacity required to be satisfied by the VNF instance is the sum of service carrying requirements of each NS instance multiplexing the VNF instance for the VNF instance.

For example, instance NS #1 multiplexes instance VNF #1 with instance NS #2, and the logical connection is as shown in FIG. 2. In a specific application, this connection relationship may be mapped as: VNF #1 denotes an MME (Mobility Management Entity) network element, and VNF #2 and VNF #3 denote CSCF (Call Session Control Function) network elements. For example, the minimum traffic bearer requirement of NS #1 for VNF #1 is 100CAPS, and the minimum traffic bearer requirement of NS #2 for VNF #1 is 150CAPS, then the minimum traffic bearer capability of VNF #1 should be 100+150 — 250 CAPS.

(2) Shared: in this mode, the minimum service carrying capacity required to be satisfied by the VNF instance is the maximum value of the service carrying capacity required for the VNF instance in each NS instance of the multiplexing VNF instance.

For example, instance NS #1 multiplexes instance VNF #1 with instance NS #2, and the logical connection is as shown in FIG. 3. VNF #1 refers to MME network elements, VNF #2 and VNF #3 refer to CSCF network elements, and VNF #1 refers to eNode bs. For example, the minimum traffic bearer requirement of NS #1 for VNF #1 is 100CAPS, and the minimum traffic bearer requirement of NS #2 for VNF #1 is 150CAPS, then the minimum traffic bearer capability of VNF #1 should be 150 CAPS.

Specifically, in combination with the above table, in this step, according to the information of the VNF instance and the information of the NS instance, the capacity expansion and reduction policy record information of the VNF instance is queried, and it is determined whether the NS instance has a right to perform a capacity expansion and reduction operation on the VNF instance. If there is no authority to scale up the VNF instance, the process may end. Determining whether the VNF instance is in a capacity expansion state or not if the NS instance has the right to perform a capacity expansion operation on the VNF instance. Then, in a case where the VNF instance is not in a scale-up state, it is determined whether an operation record exists in operation record information of the VNF instance. Wherein, whether the VNF instance is in the scaling state or not can be obtained from recorded state information of each VNF instance.

On the basis of the above embodiment, when the VNF instance is in the capacity expansion and reduction state, the related information of the capacity expansion and reduction operation request is stored in the operation record information of the VNF instance, so that the operation record information is convenient to integrate. Wherein the related information of the capacity expansion operation request comprises at least one of the following information: operation sequence number, target VNF, NSR, timestamp, target service carrying capacity, priority. The target service carrying capacity represents the service carrying capacity of the VNF after the capacity expansion and reduction operation is completed.

On the basis of the above embodiment, when there is an operation record in the operation record information of the VNF instance, the related information of the capacity expansion and contraction operation request is stored in the operation record information of the VNF instance. Wherein the related information of the capacity expansion operation request comprises at least one of the following information: operation sequence number, target VNF, NSR, timestamp, target service carrying capacity, priority. The target service carrying capacity represents the service carrying capacity of the VNF after the capacity expansion and reduction operation is completed.

And 103, executing the capacity expansion and reduction operation on the VNF instance under the condition that the query result shows that the capacity expansion and reduction operation on the VNF instance is allowed to be executed.

In practical application, the NFVO may integrate the operation records in the operation record information of the VNF instance in real time, and then sort the integrated operation records according to the priority of the NS instance to which the VNF instance belongs. In the process of ordering, if Priority of two NS instances is the same, timestamp is compared. And sorting the operation records with the time stamps at the top.

Then, when performing a capacity expansion and reduction operation on the VNF instance, if no operation record exists in the operation record information of the VNF instance, or if an operation record exists in the operation record information of the VNF instance, the capacity expansion and reduction operation is performed on the VNF instance according to the priority of the NS instance. Specifically, when an operation record exists in the operation record information of the VNF instance, the capacity expansion and reduction operation is performed on the VNF instance in the order from high to low in the priority of the NS instance.

The NFVO can integrate operation record information in real time to execute the scaling operation on the VNF instance. In the process of integrating the operation record information, the NFVO acquires, according to the operation record information of the VNF instance, an NS instance record corresponding to the VNF instance and a corresponding target service carrying capacity. And then, acquiring the required traffic load capacity of the VNF instance in all the NS instances to which the VNF instance belongs according to the NS instance records and the information of the scaling strategy records of the VNF instance. And then determining the minimum service carrying capacity threshold of the VNF instance, and deleting the operation record of which the target service carrying capacity is smaller than the minimum service carrying capacity threshold from the operation record information of the VNF instance. In this way, the success of the capacity expansion and reduction operation can be further ensured.

In the process of determining the minimum service carrying capacity threshold of the VNF instance, the NFVO acquires, according to the service carrying relationship information of the VNF instance, service carrying relationships among all NS instances to which the VNF instance belongs, and determines the minimum service carrying capacity threshold of the VNF instance according to the service carrying relationships and service carrying capacities required by the VNF instance in all NS instances to which the VNF instance belongs.

Specifically, the NFVO may determine the minimum traffic bearer capability threshold of the VNF instance as follows:

For example, instance VNF #1 is multiplexed simultaneously by NS #1, NS #2, and NS #3, the Reused version of NS #1 and NS #2 is shared, and the Load Requirement is 60CAPS and 50CAPS, respectively; the used relationships among NS #1, NS #2, and NS #3 are all sequential, and the Load Requirement for VNF #1 for NS #3 is 70 CAPS. For NS #1 and NS #2, the minimum traffic carrying capacity of VNF #1 should satisfy the maximum of Load Requirement, i.e. 60CAPS, of the two. Since the Reused relationships among NS #1, NS #2, and NS #3 are accounted, and the Load Requirement of NS #3 is 70CAPS, the minimum traffic bearer capability of VNF #1 is 60+ 70-130 CAPS.

By the scheme of the embodiment of the invention, whether the capacity expansion and reduction operation can be executed on the VNF instance can be determined by combining the operation record information of the VNF instance and the capacity expansion and reduction strategy record information of the VNF instance, so that the capacity expansion and reduction operation request is not required to be directly rejected when operation conflict occurs like in the prior art, and further the NS instance can be ensured to successfully execute the capacity expansion and reduction operation by utilizing the scheme of the embodiment of the invention.

Further, on the basis of the above embodiment, the method may further include: and generating operation record information of the VNF instance, scaling strategy record information of the VNF instance and service bearing relation information of the VNF instance.

Specifically, the NFVO obtains initial operation record information, initial scaling strategy record information, and initial service bearer relationship information sent by a user. Some information filled by a user is stored in the initial expansion and contraction capacity policy record information and the initial service bearing relationship information, for example, VNF Name, Operation Type, NS Name, Load Requirement, Priority, Permission, NS Name, and the like may be recorded in the initial expansion and contraction capacity policy record information, and VNF Name, used relationship, and the like may be recorded in the initial service bearing relationship information. And by creating an NS instance record, storing the NS instance record into the initial scale and reduction capacity strategy record information and the initial service bearing relation information. And meanwhile, storing VNF instance records into the initial scaling strategy record information and the initial service bearing relation information through an instantiation NS process.

Referring to fig. 4, fig. 4 is a flowchart of a network service scaling processing method provided by the embodiment of the present invention, which is applied to NFVO, and as shown in fig. 4, the method includes the following steps:

step 401, receiving a capacity expansion and reduction operation request.

And (3) selecting a VNF instance in a certain NS instance (the VNF instance can be simultaneously multiplexed by other NS instances) by a user in the NFVO operation interface, and triggering NS manual capacity expansion (VNF manual capacity expansion-VM increase/decrease) operation. At this time, the NFVO receives a capacity expansion and contraction operation request sent by the user.

Step 402, the NFVO retrieves the capacity expansion and contraction policy record table based on the VNFR of the selected VNF instance and the NSR of the NS instance triggering the Operation, and determines whether the NS instance has the right to expand and contract the VNF instance according to the corresponding Operation Type, Permission, and Priority parameters.

If yes, go to step 403; otherwise, the flow may end.

In step 403, the NFVO determines whether the VNF instance is in the lifecycle operation process.

If not, go to step 404; otherwise, the related information of the Operation (e.g., Operation Number, Target VNF, NSR, Timestamp, Target Load, Priority) may be written into the capacity expansion and contraction Operation record; thereafter, the flow may end.

Step 404, the NFVO searches the operation record table of scaling operation, and determines whether the operation record in the operation record table of scaling operation is empty.

If it is empty, go to step 405; otherwise, the related information of the Operation (e.g., Operation Number, Target VNF, NSR, Timestamp, Target Load, Priority) may be written into the table 1 capacity expansion/contraction Operation record table; thereafter, the flow may end.

Step 405, NFVO performs manual scaling operation on VNF instance in the specified NS instance.

For the obtained operation record table of the capacity expansion and reduction, if the operation record table is not empty, the capacity expansion and reduction operation on the NFV may be performed according to the integration result of the NFVO after the relevant information of the operation.

With reference to fig. 5, the process of the NFVO automatically processing the table of the scale operation record is as follows:

step 501, combining the service bearing relation record table, integrating the operations in the capacity expansion and reduction operation record table, including:

(1) for a certain VNFR, the NFVO retrieves the scaling operation record table, and obtains all NS instance records (NSRs) for scaling the VNF instance and the Target _ Load of the related operation.

(2) For the obtained VNFR and NSR, the NFVO searches the scaling policy record table, and obtains the traffic Load capacity (Load Requirement) required by the VNFR in each of the belonging NS instances.

(3) Based on the VNFR, the NFVO retrieves the service bearer relationship record table, and obtains the relationship (used relationship) of the NS instance to which the VNFR belongs to the VNF service bearer requirement.

(4) And integrating the obtained Reused relationship and Load Requirement information, and the NFVO calculates the minimum service carrying capacity required by the VNF.

For example, NS #1, NS #2, and NS #3 multiplex instance VNF #1 at the same time, the used relationship between NS #1 and NS #2 is shared, and the Load Requirement is 60CAPS and 50CAPS, respectively; the used relationships among NS #1, NS #2, and NS #3 are all sequential, and the Load Requirement for VNF #1 for NS #3 is 70 CAPS. For NS #1 and NS #2, the minimum traffic carrying capacity of VNF #1 should satisfy the maximum of Load Requirement, i.e. 60CAPS, of the two. Since the used relationships between NS #1, NS #2, and NS #3 are both accounted, and the Load Requirement of NS #3 is 70CAPS, the minimum traffic bearer capability of VNF #1 is 60+ 70-130 CAPS.

(5) Based on the calculated threshold of the minimum service carrying capacity of the VNF instance, deleting the operation records of which Target Load is smaller than the minimum threshold from all the VNF related operation records.

The same operation can be performed for the other VNFRs according to the procedures (1) to (5) described above.

And 502, sorting the operation records in the capacity expansion and reduction operation record table according to the Priority parameter of the NS instance.

The higher the Priority, the higher the ordering of the operation records. If priorities of multiple NS instances are the same, then timestamps corresponding to the NS instances may be compared. The earlier the time stamp, the earlier the ordering of the operational records.

And 503, sequentially executing each expansion and reduction operation according to the sorted expansion and reduction operation record table.

In addition, after the execution is completed, the NFVO may also delete the corresponding record.

In practical application, an operator may plan and fill in part of parameter contents in the scaling strategy record table and the service bearing relationship record table in advance in a network planning stage, specifically:

the following parameters can be pre-filled in the expansion and contraction strategy record table: VNF Name, Operation Type, NS Name, Load Requirement, Priority, Permission;

the following parameters can be pre-filled in the service bearing relation record table: NS Name, VNF Name, used relationship.

For other parameters in the above table, when creating an NS instance record and performing NS instantiation, the NFVO writes the instance records NSR and VNFR of the corresponding NS instance and VNF instance into the scaling policy record table and the traffic bearer relationship record table based on the NS Name and VNF Name.

As shown in fig. 6, the process of creating an NSR may include:

step 601, uploading an expansion and contraction capacity operation record table, an expansion and contraction capacity strategy record table and a service bearing relation record table by a user.

Step 602, the user sends a create NS ID request, which includes the NS name, NSD ID.

Step 603, the NFVO generates an NS ID, creating an NS record.

And step 604, the NFVO returns the operation result to the user.

Step 605, the NFVO stores the NS instance record in the scaling policy record table and the service bearer relationship record table, such as VNFR, NSR, etc.

As shown in fig. 7, the process of NS instantiation may include:

step 701, the user sends an instantiation NS request to the NFVO.

Step 702, NFVO checks the validity of the instantiated NS request.

Step 703, NFVO and VNFM loop create VNF instance record and query all VNFDs referenced by NS, getting input parameters.

Step 704, the NFVO stores the ID information of the VNF instance in the scaling policy record table and the traffic bearer relationship record table, such as VNFR, NSR, etc.

Step 705, NFVO creates VL and network connectivity resources.

Step 706, the NFVO loop creates a new VNF instance in the NS instance.

And step 707, the NFVO returns the scaling operation or the update result to the user.

Referring to fig. 8, fig. 8 shows the relationship between each table and each flow in the embodiment of the present invention.

In the process of creating the NSR and NS instantiations, the NFVO automatically fills some information into the scaling policy record table and the service bearer relationship record table. After receiving the request of the capacity expansion and reduction operation, if the capacity expansion and reduction operation on a certain NFV cannot be executed immediately, the information of the corresponding operation can be stored in the capacity expansion and reduction operation record table. In the process of executing the capacity expansion and reduction operation, the NFVO integrates the capacity expansion and reduction operation record table according to the obtained capacity expansion and reduction operation record table, the capacity expansion and reduction policy record table, and the service bearing relationship record table in the manner of step 501-502 shown in fig. 5, and executes the capacity expansion and reduction operation on the NFV.

As can be seen from the above description, in the embodiment of the present invention, information recording of a conflict operation is implemented through the capacity expansion and reduction operation record table, so that it can be ensured that a necessary manual capacity expansion and reduction operation can be successfully completed. In addition, in the process of capacity expansion and reduction operation, threshold value limitation on NS capacity expansion and reduction is realized, and after the multiplexing VNF instances execute capacity expansion and reduction, the business bearing requirements can be met in each affiliated NS instance.

The embodiment of the invention also provides a network service expansion and contraction processing device which is applied to the NFVO. Referring to fig. 9, fig. 9 is a structural diagram of a network service expansion and capacity processing apparatus according to an embodiment of the present invention. Because the principle of the network service capacity expansion and reduction processing device for solving the problems is similar to the network service capacity expansion and reduction processing method in the embodiment of the invention, the implementation of the network service capacity expansion and reduction processing device can refer to the implementation of the method, and repeated parts are not described again.

As shown in fig. 9, the network service scaling processing apparatus 900 includes:

a first receiving module 901, configured to receive a capacity expansion and reduction operation request, where the capacity expansion and reduction operation request includes information of a VNF instance to be subjected to a capacity expansion and reduction operation and information of an NS instance triggering execution of a capacity expansion and reduction operation of the VNF instance; a first query module 902, configured to query, according to the information of the VNF instance and the information of the NS instance, operation record information of the VNF instance and scaling policy record information of the VNF instance to obtain a query result; a first processing module 903, configured to execute a scaling operation on the VNF instance if the query result indicates that the scaling operation is allowed to be executed on the VNF instance.

Wherein the first query module comprises:

Wherein the apparatus further comprises:

Wherein the integration module comprises:

Wherein the first determination submodule includes:

Wherein the second determination unit includes:

The first processing module is configured to, when an operation record exists in the operation record information of the VNF instance, execute a capacity expansion and reduction operation on the VNF instance in an order from high to low in priority of the NS instance.

Wherein the apparatus further comprises:

Wherein the generating module comprises:

a first creating submodule for creating an NS instance record;

The apparatus provided in the embodiment of the present invention may implement the method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides a network service expansion and contraction processing device which is applied to the NFVO. Referring to fig. 10, fig. 10 is a structural diagram of a network service expansion and capacity processing apparatus according to an embodiment of the present invention. Because the principle of the network service capacity expansion and reduction processing device for solving the problems is similar to the network service capacity expansion and reduction processing method in the embodiment of the invention, the implementation of the network service capacity expansion and reduction processing device can refer to the implementation of the method, and repeated parts are not described again.

As shown in fig. 10, the network service expansion/reduction processing apparatus 1000 includes: a processor 1001 and a transceiver 1002.

The transceiver 1002 is configured to receive a capacity expansion and reduction operation request, where the capacity expansion and reduction operation request includes information of a VNF instance to be subjected to a capacity expansion and reduction operation and information of an NS instance triggering execution of a capacity expansion and reduction operation of the VNF instance;

the processor 1001 is configured to query, according to the information of the VNF instance and the information of the NS instance, operation record information of the VNF instance and scaling policy record information of the VNF instance to obtain a query result; and in the case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing the capacity expansion and reduction operation on the VNF instance.

Wherein the processor 1001 is further configured to:

when an operation record exists in the operation record information of the VNF instance, the related information of the capacity expansion and contraction operation request is stored in the operation record information of the VNF instance;

Wherein the processor 1001 is further configured to:

determining a minimum traffic bearing capacity threshold of the VNF instance;

Wherein the processor 1001 is further configured to:

creating an NS instance record;

As shown in fig. 11, the electronic device according to the embodiment of the present invention includes: the processor 1100, which reads the program in the memory 1120, performs the following processes:

receiving a capacity expansion and reduction operation request, wherein the capacity expansion and reduction operation request comprises information of a Virtual Network Function (VNF) instance to be subjected to capacity expansion and reduction operation and information of a Network Service (NS) instance triggering the capacity expansion and reduction operation of the VNF instance;

A transceiver 1110 for receiving and transmitting data under the control of the processor 1100.

Where in fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1100, and various circuits, represented by memory 1120, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1110 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1100 in performing operations.

The processor 1110 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1100 in performing operations.

The processor 1100 is also adapted to read the program and execute the following steps:

acquiring the required business load capacity of the VNF instance in all NS instances to which the VNF instance belongs according to the NS instance record and the scaling strategy record information of the VNF instance;

determining a minimum traffic bearing capacity threshold of the VNF instance;

The processor 1100 is also adapted to read the program and perform the following steps:

creating an NS instance record;

The embodiment of the present invention further provides a readable storage medium, where a program is stored on the readable storage medium, and when the program is executed by a processor, the program implements each process of the foregoing network service capacity expansion and reduction processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The readable storage medium may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical memory (e.g., CD, DVD, BD, HVD, etc.), and semiconductor memory (e.g., ROM, EPROM, EEPROM, nonvolatile memory (NAND FLASH), Solid State Disk (SSD)), etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. With such an understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A network service expansion and capacity processing method is applied to a Network Function Virtualization Orchestrator (NFVO), and is characterized by comprising the following steps:

2. The method according to claim 1, wherein the querying, according to the information of the VNF instance and the information of the NS instance, operation record information of the VNF instance and scaling policy record information of the VNF instance to obtain a query result, comprises:

3. The method of claim 2, further comprising:

4. The method of claim 2, further comprising:

5. The method of claim 4, further comprising:

6. The method of claim 5, wherein the integrating the operation record in the operation record information of the VNF instance comprises:

determining a minimum traffic bearing capacity threshold of the VNF instance;

7. The method of claim 6, wherein the determining the minimum traffic-bearing capacity threshold for the VNF instance comprises:

8. The method of claim 7, wherein the determining the minimum traffic-bearing capacity threshold of the VNF instance according to the traffic-bearing relationship and a traffic-bearing capacity required by the VNF instance in all NS instances to which the VNF instance belongs comprises:

9. The method according to claim 1 or 5, wherein, in a case that the query result indicates that the capacity expansion and reduction operation is allowed to be performed on the VNF instance, performing a capacity expansion and reduction operation on the VNF instance comprises:

10. The method according to claim 9, wherein, in a case that an operation record exists in the operation record information of the VNF instance, performing a capacity expansion and reduction operation on the VNF instance according to the priority of the NS instance includes:

11. The method of claim 1, wherein prior to said receiving a request for a scale operation, the method further comprises:

12. The method of claim 11, wherein the generating operation record information of the VNF instance, scaling policy record information of the VNF instance, and traffic bearer relationship information of the VNF instance comprises:

creating an NS instance record;

13. A network service scaling processing device applied to NFVO (network function object), comprising:

14. A network service scaling processing device applied to NFVO (network function object), comprising: a processor and a transceiver;

15. An electronic device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; it is characterized in that the preparation method is characterized in that,

the processor, configured to read a program in a memory to implement the steps in the network service scaling processing method according to any one of claims 1 to 12.

16. A readable storage medium storing a program, wherein the program, when executed by a processor, implements the steps in the network service scaling-up processing method according to any one of claims 1 to 12.