WO2019080593A1 - Management, maintenance and control method for virtual network element and related device - Google Patents

Abstract

Disclosed in the present application are a management method for a virtual network element and a related device. A VNFM maintains an instance list and a connection relationship table. The VNFM updates the instance list according to VNFs or an instance update result of a basic service, redistributes connection relationships between paas instances after the instance update of the base service and VNFC instances of VNFs, and updates the connection relationship table according to the redistributed connection relationships, the calling relationship between the basic service and the VNFs can be automatically re-established to improve the service operation efficiency and quickly restore the service.

Description

Management, maintenance and control method of virtual network element and related device

This application claims the priority of the Chinese patent application filed on October 27, 2017, the Chinese Patent Office, the application number is 201711023648.0, and the invention name is "the management, maintenance and control method of the virtual network element and related devices". The citations are incorporated herein by reference.

Technical field

The present invention relates to the field of communications, and in particular, to a method, a method for managing and maintaining a virtual network element of a virtual network element, and related devices.

Background technique

NFV (network function virtualization) is a virtualization technology. NFV implements software hardware decoupling, so that the functions of network devices no longer depend on dedicated hardware, and carry the functions of dedicated devices in traditional networks on general hardware. This reduces the cost of deploying dedicated equipment.

The NFV platform includes the following network elements: NFVO (network function virtualisation orchestrator), VNF (virtualized network function), VNFM (virtualized network function management), VIM (VIM) Virtualized infrastructure management, and NFVI (network function virtualization infrastructure). Among them, NFVO, VNFM, and VIM are collectively referred to as NFV-MANO, which is equivalent to CSP (cloud service provider), NFVO, VNFM (Network Functions Virtualisation Manager), and VIM (Virtualised Infrastructure Manager, The Virtualization Infrastructure Manager) provides NFV management capabilities together. NFVO manages the life cycle of VNF through VNFM, provides functions such as NS (network service) management, VNF Package management, and provides NS management interface to external entities (such as OSS/BSS). VNF is an application deployed on NFVI that implements specific network functions. VNFM is a functional module for lifecycle management of VNF. VIM is a functional module that controls and manages NFVI computing resources, storage resources, and network resources. VIM can be deployed to the infrastructure domain Infrastructure Domain (for example, NFVI access point/service provisioning point). NFVI is the collective name for all hardware devices and software components in an NFV-capable environment. NFVI can be deployed across several physical locations (for example, data center operations).

Paas (platform as a service) is a mode that provides software development platform as a service to users. At present, it has begun to discuss the introduction of paas mode into NFV platform. VNF in NFV platform passes API. The (application programming interface) method calls the basic services (such as database, log, authentication, encryption, etc.) in the paas platform. Based on the requirements of NFV for paas, the gateway or loadbalancer may be used to shield the underlying paas instance details, or the paas instance may be directly invoked by the VNF without using the above middleware. During the running of the system, instances in the NFV platform or the paas platform may be subject to scaling (reduction or increase of instances). When the VNF directly invokes the paas instance, the original call between the VNF and the underlying service is performed after the instance is scaled. If the relationship is invalid, the service is interrupted, or the calling relationship between the newly added VNFC instance and the newly added paas instance cannot be dynamically updated to reduce the efficiency of the original service.

Summary of the invention

The embodiment of the present invention is based on the scenario in which the VNF directly invokes the paas instance. The technical problem to be solved is how to provide a virtual network element virtual network element management, maintenance, and control method, and related devices, and the VNFM maintenance instance list and the connection relationship table. When an instance in the NFV platform or the paas platform is updated, the connection relationship between the instances of the two platforms is automatically implemented to achieve the purpose of quickly establishing a calling relationship between the VNF and the basic service and restoring the business function.

In a first aspect, the present application provides a method for managing a virtual network element, including: when a basic service satisfies an instance update condition, a paas management network element performs an instance update on a basic service, and a paas management network element sends a basic service to a VNFM. Instance update results.

Among them, the basic services in the paas platform provide basic business functions for the paas platform, such as: database, log, authentication or encryption services. The instance update condition indicates a condition for triggering the base service to perform the paas instance update. The paas instance update described in this application includes terminating or creating a paas instance, and the instance update condition may be based on a pre-storage or pre-configuration condition of the paas management network element. The instance update result represents the attribute information of the updated paas instance in the basic service, for example, the attribute information includes at least one of an identifier of the paas instance, a service type identifier, an update type, and a network address, and the representation of the instance update result includes but is not limited to A table, array, linked list, structure, or other form. The paas instance is a stand-alone logical entity with the basic service capability, and can run in an environment such as a physical machine, a virtual machine, or a container. The basic service is associated with at least one paas instance.

In the present application, the paas management network element in the paas platform has an interface for communicating with the VNFM in the NFV platform. When the basic service in the paas platform satisfies the instance update condition, the paas management network element performs an instance of the basic service through the above interface. The update result is reported to VNFM, so that VNFM automatically updates the maintained instance list and connection relationship table according to the instance update result.

In one possible design, the instance update result includes at least one of an identifier of the updated paas instance in the underlying service, a service type identifier, an update type, and a network address.

The identifier of the paas instance is used to uniquely represent the identity of the paas instance; the service type identifier of the paas instance indicates the service type of the paas instance; the network address of the paas instance indicates the address of the paas instance for external service, and the network address can be a port number and/or The IP address is used to indicate.

In a possible design, before the basic service satisfies the instance update condition, the paas management network element performs an instance update on the basic service, and further includes:

The paas management network element obtains the average load of all paas instances associated with the basic service;

The paas management network element determines that the average load is greater than the first load threshold; or

The paas management network element determines that the average load is less than the second load threshold.

The service type identifier of the paas instance at this time is defined by using the first mode, and all paas instances associated with the basic service have the same service type identifier. The load in this application includes, but is not limited to, at least one of CPU usage, memory usage, and disk occupancy.

In a possible design, before the basic service satisfies the instance update condition, the paas management network element performs an instance update on the basic service, and further includes:

The paas management network element acquires the load of at least one paas instance in all paas instances associated with the basic service;

The paas management network element determines that the load of each paas instance in at least one paas instance is greater than the first load threshold; or

The paas management network element determines that the load of each paas instance in at least one service instance is less than the second load threshold.

The service type identifier of the paas instance is defined by the second method, and all the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance and the paas The identifiers of the instances are the same. The load in this application includes, but is not limited to, at least one of CPU usage, memory usage, and disk occupancy.

In a second aspect, the application provides a method for managing a virtual network element, including: the VNFM receives an instance update result about a basic service from a paas management network element; and the VNFM updates all VNF connections associated with the basic service according to the instance update result. Point configuration information.

The VNFM is a network element for managing the VNF in the NFV platform, and the paas management network element is a network element for managing the basic service in the paas platform, and the VNFM and the paas management network element are provided with interfaces for mutual communication. VNFM maintains the association between all VNF and all basic services in the paas platform in the NFV platform. The connection point configuration information of the VNF indicates the network address of the connection point of the VL instance to which the VNF belongs, and the VL instance is used to connect two VNFC instances, or a VNFC instance and a paas instance. When a VL instance needs to be connected to two instances, the connection with the two instances is the connection point, and the VNFM configures the network address of the connection point to be the same as the network address of the corresponding instance.

In the present application, the VNFM receives the connection point configuration information of the VNF associated with the instance update result update from the paas management network element, so that when the paas instance associated with the basic service is increased or decreased, the calling relationship between the associated VNF and the associated VNF can be automatically updated. To achieve the purpose of quickly recovering business.

In one possible design, the VNFM updates the connection point configuration information of all VNFs associated with the base service according to the instance update structure: the VNFM updates the pre-stored or pre-configured instance list according to the instance update result; the VNFM is based on pre-storage or pre-configuration The connection relationship table queries all the VNFs associated with the basic service, and queries the VNFC instances associated with the VNFs. The VNFM redistributes the connection relationship between the associated paas instance and the VNFC instances associated with all VNFs. The VNFM updates the pre-stored or pre-configured connection relationship table according to the re-assigned connection relationship, and updates the connection point configuration information of all the VNFs according to the updated connection relationship table.

The instance list represents attribute information of all paas instances in the paas platform, and the attribute information includes at least one of a service type identifier of the paas instance, an identifier of the paas instance, and a network address of the paas instance. Connects all paas in the paas platform to all VNFC instances in the NFV platform. The basic service can be called by at least one VNF, that is, one basic service is associated with at least one VNF; one VNF includes at least one VNFC, each VNFC runs on at least one VNFC instance, and the VNFC instance is a virtual machine or a container. The connection point configuration information of the VNF indicates the network address of the connection point of the VL instance associated with the VNFC instance in the VNF, and the VL instance is used to connect two instances (two VNFC instances, or one VNFC instance and one paas instance), and the corresponding VL The instance has two connection points, and the network address of the connection point of the VL instance needs to be configured to be the same as the network address of the connected instance. The connection point where the VL instance and the VNFC instance are connected is an internal connection point, and the connection point where the VL instance and the paas instance are connected is an external connection point.

In the present application, the VNFM maintains an instance list and a connection relationship table. The VNFM updates the instance list according to the instance update result of the basic service notified by the paas management network element, and redistributes the paas instance and the VNF VNF instance of the VNF after the basic service occurrence instance is updated. The connection relationship between the basic relationship and the VNF can be automatically re-established according to the re-allocated connection relationship to achieve the purpose of quickly recovering the service.

In one possible design, the instance update result includes at least one of an identifier of the updated paas instance in the pass service, a service type identifier, an update type, and a network address.

The updated service instance is a paas instance created or terminated in the underlying service. The representation of the instance update result may be a table, an array, a linked list, a structure, or other forms, which is not limited in this application.

In one possible design, the service type identifier is defined in the first way, and all paas instances associated with the paas instance have the same service type identifier; or

The service type identifier is defined in the second mode. All the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier of the paas instance.

In a possible design, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set; the service type identifier set includes n service type identifiers, and the paas instance identifier set includes n paas instances. The identifier subset, the network address set includes n network address subsets. The instance list has n rows, each row including a service type identifier having an association relationship, a paas instance identifier sub-collection, and a network address sub-collection.

In one possible design, the VNFM updates the list of instances based on the instance update results including:

In the case that the update type of the updated paas instance is created and the service type identifier is defined in the first manner, the search is performed in the service type identifier set of the instance list according to the service type identifier of the update paas instance;

In the case of retrieving the service type identifier of the updated paas instance, the identifier of the updated paas instance is added to the paas instance identifier sub-collection associated with the update type of the updated paas instance in the instance list, and updated in the instance list Add the network address of the updated paas instance to the sub-collection of network addresses associated with the paas instance; or

In the case that the service type identifier of the updated paas instance is not retrieved, a row is created in the instance list, the service type identifier of the updated paas instance is added in the service type identifier set, and the updated paas is in the instance list. The service type of the instance identifies the identifier of the added paas instance in the associated paas instance identifier sub-collection, and adds the updated network address of the paas instance in the network address sub-collection associated with the service type identifier of the updated paas instance in the instance list. .

In one possible design, the VNFM updates the list of instances based on the instance update results including:

In the case that the update type of the updated paas instance is terminated and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set according to the service type identifier of the paas instance;

If the service type identifier of the paas instance is retrieved, the identifier of the updated paas instance is deleted from the base service identifier sub-collection associated with the service type identifier of the updated paas instance in the instance list, and the updated paas instance is in the instance list. The service type identifies the network address of the updated paas instance in the associated network address sub-collection.

In one possible design, the VNFM updates the list of instances based on the instance update results including:

In the case that the update type of the updated paas instance is created and the service type identifier is defined by using the second mode, the search is performed in the paas instance identifier set according to the service type identifier of the update paas instance;

If the same paas instance identifier is retrieved from the updated paas instance, the updated paas instance identifier is added to the paas instance identifier sub-collection associated with the paas instance identifier in the instance list, and the network associated with the paas instance identifier in the instance list Add the network address of the updated paas instance to the address sub-collection; or

If the same paas instance identifier as the updated paas instance is not retrieved, create 1 row in the instance list, add the service type identifier of the updated paas instance in the service type identifier set, and update the paas instance in the instance list. The service type identifier identifies the associated paas instance identifier sub-set with the identifier of the updated paas instance added, and the network address of the updated paas instance added to the network address sub-collection associated with the service type identifier of the updated paas instance in the instance list.

In one possible design, the VNFM updates the list of instances based on the instance update results including:

In the case that the update type of the updated paas instance is terminated and the service type identifier is defined by using the second mode, the search is performed in the paas instance identifier set according to the service type identifier of the update paas instance;

If the same paas instance identifier is retrieved from the updated paas instance, the updated paas instance identifier is deleted from the paas instance identifier sub-collection corresponding to the paas instance identifier in the instance list, and the network associated with the paas instance identifier in the instance list is deleted. The network address of the updated paas instance is deleted from the address sub-collection.

In one possible design, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

Each row of the connection relationship table includes a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier with an association relationship.

In a possible design, the connection relationship between the associated paas instance and the VNFC instance associated with at least one VNF after the re-allocation of the basic service to complete the instance update includes:

The connection relationship between the associated paas instance and the at least one VNFC instance after the instance update is completed in a random manner; wherein each paas instance is connected to at least one VNFC instance.

In a possible design, updating the connection relationship table includes: searching, in the connection relationship table, the VNFC instance identifier to be updated according to the re-allocated connection relationship;

If the VNFC instance identifier to be updated is retrieved, the connection relationship between the VNFC instance identifier to be updated in the reassigned connection relationship and the connection relationship between the VNFC instance to be updated in the connection relationship table is compared. the same;

If the same, do not perform the update;

If not, the connection relationship between the re-allocated connection relationship and the VNFC instance to be updated in the connection relationship table is determined according to the VNFC instance to be updated;

If the VNFC instance identifier to be updated is not retrieved, a row is created in the connection relationship table, and a connection relationship corresponding to the VNFC instance to be updated in the connection relationship table is added in the created row.

In a possible design, updating the connection point configuration information of all VNF associations includes: obtaining a connection relationship modified or created in the updated connection relationship table, and if the modified or created connection relationship includes the VL instance identifier, the corresponding The network address of the external connection point of the VL instance is configured as the network address of the connected paas instance. If the modified or created connection does not include the VL instance ID, create a VL instance and create the internal connection point configuration information of the VL instance. Configure the network address of the connected VNFC instance, configure the external connection point configuration information of the created VL instance as the network address of the connected paas instance, and add the identifier of the created VL instance to the connection relationship.

In a third aspect, the application provides a method for managing a virtual network element, including:

In the case that the VNF satisfies the instance update condition, the VNFM obtains the instance update result of the VNF, and updates the connection point configuration information of the VNF according to the instance update result of the VNF.

The VNF is associated with at least one VNFC instance and /VL instance, and the instance update condition indicates a condition for triggering a VNF increase or decrease or a decrease of an instance (a VNFC instance and a /VL instance), and the instance update result indicates attribute information of an instance of an increase or decrease in the VNF. The connection point configuration information of the VNF indicates the network address of the connection point of the VL instance to which the VNF belongs, and the VL instance is used to connect two VNFC instances, or a VNFC instance and a paas instance. When a VL instance needs to be connected to two instances, the connection with the two instances is the connection point, and the VNFM configures the network address of the connection point to be the same as the network address of the corresponding instance.

In this application, the VNFM updates the connection point configuration information of the associated VNF according to the instance update result of the VNF, so that when the VNFC instance associated with the VNF is increased or decreased, the calling relationship between the associated and the associated paas instance can be automatically updated to achieve fast The purpose of restoring business.

In a possible design, updating the connection point configuration information of the VNF according to the VNF instance update result includes:

Query all the basic services associated with the VNF according to the pre-stored or pre-configured connection relationship table, and query the paas instances associated with all the basic services. The VNFM re-allocates between the associated instance after the instance update and the paas instance associated with all the basic services. The connection relationship, updating the pre-stored or pre-configured connection relationship table according to the re-allocated connection relationship, and updating the connection point configuration information of the VNF associated with the VNF according to the updated connection relationship table.

The instance update condition indicates a condition for triggering an instance (VNFC instance and/or VL instance) in the VNF to be added or deleted. For example, the VNFM can determine whether the instance update condition is met according to the load of the VNFC instance associated with the VNF. The instance update result includes attribute information of the updated VNFC instance in the VNF, for example, the attribute information includes, but is not limited to, at least one of a VNFC identifier, a VNF identifier, and a VL identifier.

In one possible design, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier. The connection relationship table identifies the connection relationship between all instances in the NFV platform and all instances in the paas platform.

In a fourth aspect, the application provides a method for managing a virtual network element, including:

The VNFM obtains the paas instance allocation result of the VNF and the VNFC instance allocation result when the VNF needs to be created.

Updating the instance list according to the paas instance allocation result;

Allocating a connection relationship between the VNFC instance corresponding to the VNFC instance assignment result and the paas instance assignment result corresponding to the paas instance;

Updating the connection relationship table according to the allocated connection relationship, and updating the connection point configuration information of the VNF according to the updated connection relationship table.

In a possible design, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, where the service type identifier set includes n service type identifiers, and the paas instance identifier The set includes n paas instance identifier sub-sets, the network address set includes n network address sub-sets, the service type identifier in the service type identifier set, the paas instance identifier sub-collection in the paas instance identifier set, and the The network address subsets in the network address set are in one-to-one correspondence, and n is an integer greater than 0.

In a possible design, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

In a fifth aspect, the present application provides a management device for a virtual network element, where the management device has a function of implementing the behavior of a paas management network element in the foregoing method. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation manner, the management apparatus includes: a processing unit, configured to perform an instance update on the basic service if the basic service satisfies an instance update condition; and a sending unit, configured to the virtual network function management network The meta VNFM sends an instance update result of the base service.

In another possible implementation, the management apparatus includes: a transmitter, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke program code stored in the memory And performing the following operations: performing an instance update on the basic service if the basic service satisfies the instance update condition. The transmitter is configured to send an instance update result of the basic service to a virtual network function management network element VNFM.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible terminal devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.

In a sixth aspect, the present application provides a maintenance device for a virtual network element, the maintenance device having a function of implementing the behavior of the VNFM in the foregoing method. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation manner, the maintenance apparatus includes: a receiving unit, configured to receive an instance update result about a basic service from a paas management network element; and a processing unit, configured to update and base the update result according to the instance Connection point configuration information for all VNFs associated with the service.

In another possible implementation manner, the maintenance apparatus includes: a receiver, a memory, and a processor; wherein the receiver is configured to receive an instance update result about the basic service from the paas management network element; A set of program code, and the processor is configured to invoke program code stored in the memory, and perform the operation of: updating connection point configuration information of all VNFs associated with the base service according to the instance update result.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible terminal devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.

In a seventh aspect, the present application provides a control device for a virtual network element, the control device having a function of implementing the behavior of the VNFM in the above method. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation, the control device includes: an acquiring unit, configured to acquire an instance update result of the VNF if the VNF meets an instance update condition; and a processing unit, configured to update according to the instance of the VNF The result updates the connection point configuration information of the VNF.

In another possible implementation, the control device includes: a transmitter, a receiver, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory The program code is configured to: obtain an instance update result of the VNF if the VNF meets the instance update condition; and the processing unit updates the connection point configuration information of the VNF according to the instance update result of the VNF.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible terminal devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.

In a seventh aspect, the present application provides a device for creating a virtual network element, the creating device having a function of implementing the behavior of the VNFM in the foregoing method. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible implementation manner, the creating apparatus includes: an acquiring unit, configured to acquire, by the VNFM, a paas instance allocation result of the VNF and a VNFC instance allocation result, where the VNF needs to be created;

a processing unit, configured to update the instance list according to the paas instance allocation result; assign a connection relationship between the VNFC instance corresponding to the VNFC instance assignment result and the paas instance assignment result corresponding to the paas instance; and update the connection according to the allocated connection relationship The relationship table, and the connection point configuration information of the VNF is updated according to the updated connection relationship table.

In another possible implementation, the creating device includes: a transmitter, a receiver, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory The program code is configured to: obtain a paas instance assignment result of the VNF and a VNFC instance assignment result when the VNF needs to be created; update the instance list according to the paas instance assignment result; and assign the VNFC instance assignment result to the corresponding The VNFC instance and the paas instance assignment result correspond to a connection relationship between the paas instances; update the connection relationship table according to the allocated connection relationship, and update the connection point configuration information of the VNF according to the updated connection relationship table.

Based on the same inventive concept, the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible terminal devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.

Yet another aspect of the present application is directed to a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background art, the drawings to be used in the embodiments of the present invention or the background art will be described below.

1 is a network architecture diagram of a communication system according to an embodiment of the present invention;

2 is a schematic flowchart of a method for managing a virtual network element according to an embodiment of the present invention;

3 is a schematic flowchart of a method for maintaining a virtual network element according to an embodiment of the present invention;

4 is a schematic flowchart of a method for creating a virtual network element according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a virtual network element management apparatus according to an embodiment of the present disclosure;

FIG. 6 is another schematic structural diagram of a virtual network element management apparatus according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a maintenance device for a virtual network element according to an embodiment of the present disclosure;

FIG. 8 is another schematic structural diagram of a maintenance device for a virtual network element according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a device for controlling a virtual network element according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of another structure of a virtual network element control apparatus according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a device for creating a virtual network element according to an embodiment of the present disclosure;

FIG. 12 is another schematic structural diagram of a device for creating a virtual network element according to an embodiment of the present invention.

Detailed ways

The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention. The communication system includes a VFV platform and a paas platform, wherein the NFV platform includes OSS/BSS, NFVO, VNFM, VIM, NFVI, and VNF.

OSS/BSS is a comprehensive business operations and management platform with key functions including network management, system management, billing, business, finance and customer service.

NFVO is mainly used for service lifecycle management, resource scheduling capabilities across data centers, and business lifecycle management capabilities across vendors (including service deployment, capacity expansion, capacity reduction, and downline).

A VNF is a virtualized network element device or service. A VNF usually has multiple components with independent functions called VNFC. VNFC usually runs on one or more instances (virtual machines or containers).

VNFM is used to provide VNF with automated management capabilities such as deployment, expansion, shrinkage, and offline.

The VNFM maintains an instance list and a connection relationship table. The instance list and the connection relationship table are located in the VNFM, and may be located in other network elements. This embodiment is not limited. The instance list stores attribute information of all paas instances in the paas platform, for example, the attribute information includes, but is not limited to, at least one of an identity identifier, a service type identifier, an update type, and a network address. The connection relationship table stores the connection relationship between the instance in the paas platform and the instance in the NFV platform. For example, the connection relationship table includes at least one of a VNFC identifier, a VNF identifier, a paas instance identifier, and a VL instance identifier.

NFVI is the infrastructure of the NFV platform, providing virtual computing resources, storage resources and network resources to the upper layer in the form of virtual machines or containers.

VIM is primarily responsible for managing and monitoring the underlying virtual resources.

VNFC (Virtualized Network Function Component) is a subset of VNF related functions.

A VNFC Instance is an instance of a virtualized network function module component VNFC deployed to a specific virtualized container instance. The lifecycle management of the VNFC instance is related to its associated VNF.

The VL instance is used to connect two VNFCs. It can also be used to connect one VNFC instance and one paas instance. The VL instance includes two connection points. The connection point that interfaces with the VNFC instance is an internal connection point, and the connection with the paas instance is connected. The point is the external connection point.

In the communication system of the embodiment of the present invention, the paas platform includes one or more basic services, and the type of the basic service may be a general basic service or a dedicated basic service, and the basic service provides a corresponding service function. The paas platform may have multiple deployment methods, for example, the whole form exists in the form of a VNF black box or exists in the form of NFVI, but regardless of the deployment form, the basic service can only be managed by the paas management network element, and the basic service pair The parts outside the paas platform are invisible. For example, the virtual network element in the NVF platform cannot directly know the attribute information (load status or number of instances, etc.) of the basic service.

Referring to FIG. 2, FIG. 2 is a schematic diagram of a method for managing a virtual network element according to an embodiment of the present invention, where the method includes but is not limited to the following steps:

S201. The paas management network element detects that the basic service satisfies the instance update condition.

Specifically, the instance update condition is a condition for triggering the termination of the basic service or the creation of the paas instance, and the paas management network element may determine whether the instance update condition is met by detecting the load associated with the paas instance, and the load includes but is not limited to the CPU occupancy rate and the memory occupancy rate. And at least one of disk usage.

In a possible implementation manner, the paas management network element uses method 1 to detect whether the basic service meets the instance update condition: the paas management network element obtains the average load of all the paas instances associated with the basic service, and if the average load is greater than the first load threshold And determining that the basic service satisfies the instance update condition; or, if the average load is less than the second load threshold, determining that the basic service satisfies the instance update condition.

In another possible implementation manner, the paas management network element uses method 2 to detect whether the basic service satisfies the instance update condition: the paas management network element acquires the load of at least one paas instance in all paas instances associated with the basic service, if at least one The load of the service instance is greater than the pre-stored or pre-configured first load threshold, determining that the base service satisfies the instance update condition; or determining the base service if the load of the at least one service instance is less than the pre-stored or pre-configured second load threshold The instance update condition is met.

S202: The paas management network element performs an instance update on the basic service.

The paas management network element determines whether the basic service satisfies the instance update condition, and increases or decreases the paas instance in the basic service according to the pre-stored or pre-configured instance update policy.

When the paas management network element uses method 1 to check whether the basic service meets the instance update condition, if the average load of all the paas instances associated with the basic service is greater than the first load threshold, the paas management network element updates the policy according to the pre-stored or pre-configured instance. The base service creates a new paas instance; if the average load is less than the second load threshold, the paas management network element terminates the paas instance in the base service according to the pre-stored or pre-configured instance update policy.

If the paas management network element uses method 2 to detect whether the basic service meets the instance update condition, if the load of at least one paas instance in all the paas instances associated with the basic service is greater than the pre-stored or pre-configured first load threshold, according to pre-storage or The pre-configured instance update policy creates a new paas instance for the underlying service; if the load of at least one paas instance is less than the pre-stored or pre-configured second load threshold, the paas instance in the underlying service is terminated according to the instance update policy.

The method for updating the paas instance includes: the first load threshold is greater than or equal to the second load threshold, the instance update policy indicates a policy of increasing or decreasing the paas instance, and the number and location of the paas instance terminated or created in the instance update policy. The embodiments are not limited and may be pre-defined or pre-configured as needed.

S203. The paas management network element sends the instance result of the basic service to the VNFM, and the VNFM receives the instance update result from the paas management network element.

The instance update result indicates the attribute information of the updated paas instance in the paas instance, and the updated paas instance is the created paas instance or the terminated paas instance, and the instance update result includes the updated paas instance identifier, the service type identifier, the update type, and At least one of the network addresses. The identifier of the paas instance is used to uniquely represent the identity of the paas instance, the service type identifier is used to indicate the service type of the paas instance, the update type of the paas instance indicates that the paas instance is terminated or created, and the network address indicates the address of the paas instance providing the service externally, including IP address and port number. The network address can be empty when the update type of the paas instance is terminated. When the update type of the paas instance is created, the network address is indispensable.

The service type identifier of the paas instance may have different definition manners according to different methods for detecting the load of the basic service. In the same paas platform, the service type identifier of the paas instance uses a unified definition manner.

In a possible implementation manner, in the case that the method update condition is triggered by using the method 1 in S201, all paas instances associated with the basic service have the same service type identifier, and the service type identifier may be managed by paas when the basic service is created. The network element is specified.

In another possible implementation manner, in the case that the method update condition is triggered by using the method 2 in S202, all the paas instances associated with the basic service have different service type identifiers, and the update type of the paas instance is terminated, paas The service type identifier of the instance is the same as the identity of the paas instance. For example, the basic service is associated with four paas instances, and the identifiers of the four paas instances are 2, 4, 6, and 7, respectively. Then the service type identifiers and identifiers of the four paas instances are the same, and the update types of the four paas instances are created. The service type identifiers of the four paas instances are 3, 5, 7, and 8, respectively. For example, if the identifier of the paas instance is 5, and the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier indicating the identity, and is also 5.

For example, the instance update result is represented by a table, and each row of the instance update result represents attribute information of one updated paas instance, and the instance update result is as shown in Table 1:

Table 1

The updated paas instance identifiers in Table 1 are 2, 5, and 12, wherein the update types of paas instances 2, 5, and 12 use the first definition mode, the service type identifier has 6, and the update type of paas instance 2 is terminated, corresponding The network address can be empty; the update type of paas instance 5 and paas instance 12 is created, and the network address is not empty.

It should be noted that the data structure of the instance update result is not limited to the form of Table 1, and may be represented by an array, a linked list, a structure, or other data structures, which is not limited in this embodiment.

The process of updating the instance list by the paas management network element may include:

The instance list represents attribute information of all paas instances in the paas platform, and the attribute information includes at least one of an identifier of the paas instance, a service type identifier, and a network address.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, the service type identifier set includes n service type identifiers, and the paas instance identifier set includes n paas The instance identifier sub-collection, the network address set includes n network address sub-sets, the service type identifier in the service type identifier set, the paas instance identifier sub-collection in the paas instance identifier set, and the network address sub-set in the network address set are one-to-one correspondence , that is, the instance list includes n rows, each row includes a service type identifier having an association relationship, a paas instance identifier sub-collection and a network address sub-collection, a service type identifier set, a paas instance identifier set, and a network address set are columns of an instance list. .

Exemplarily, a list of VNFM pre-stored or pre-configured instances is shown in Table 2:

Table 2

The elements of each row in Table 2 have an association relationship, the service type identifier 1, the paas instance identifier sub-set {1, 2, 3} and the network address sub-collection {192.168.1.1: 80, 192.168.1.2: 80, 192.168.1.3: 80} are associated. The paas instance identifier 1 corresponds to the network address 192.168.1.1:80, the paas instance identifier 2 corresponds to the network address 192.168.1.2:80, the paas instance identifier 3 and the network address 192.168.1.3:80. Service type identifier 5, paas instance identifier sub-set {5, 7, 8, 9, 12} and network address sub-set {192.168.1.55:8080,192.168.1.57:8080,192.168.1.58:8080,192.168.1.59:8080 , 192.168.1.62:8080} association, paas instance identification sub-collection {5,7,8,9,12} and network address sub-set {192.168.1.55:8080,192.168.1.57:8080,192.168.1.58:8080,192.168 The elements in .1.59:8080, 192.168.1.62:8080} correspond one-to-one.

In a possible implementation manner, the method for the VNFM to update the instance list includes:

In a case that the update type of the updated paas instance is created and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set of the instance list according to the service type identifier of the update paas instance;

In the case that the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection associated with the update type of the updated paas instance in the instance list. And adding a network address of the updated paas instance to a subset of network addresses associated with the updated paas instance in the list of instances; or

And adding, in the service type identifier set, a service type identifier of the updated paas instance, and the update in the instance list, in a case that the service type identifier identifier of the updated paas instance is not retrieved The service type of the paas instance identifies the identifier of the associated paas instance in the associated paas instance identifier sub-collection, and the network address sub-collection associated with the service type identifier of the updated paas instance in the instance list. Add the network address of the updated paas instance.

For example, the service type identifier of the updated paas instance is 1, the update type is created, the identifier of the updated paas instance is 4, and the network address is 192.168.1.105:80. The VNFM searches in the service type identifier set of the instance list of Table 2. Service type identifier 1, the search result is the retrieved service type identifier 1, and the updated paas instance identifier 4 is added in the paas instance identifier set {1, 2, 3}, and is updated to be {1, 2, 3, 4}, Add the network address of the updated paas instance to 192.168.1.105:80 in the network address sub-set {192.168.1.1:80,192.168.1.2:80,192.168.1.3:80}, and the updated network address sub-collection is {192.168.1.1:80,192.168. 1.2: 80, 192.168.1.3: 80, 192.168.1.105: 80}, the correspondence between the paas instance identifier 4 and the network address 192.168.1.105:80 is established. The list of instances in Table 2 is updated as shown in Table 3:

table 3

For example, the service type identifier of the updated paas instance is 2, the service type identifier is defined by the first mode, the update type of the paas instance is created, the network address is 192.168.1.105:80, and the identifier of the updated paas instance is 4. VNFM does not retrieve paas instance 4 in the service type identifier set of the instance list of Table 2, creates 1 row in the instance list, adds service type identifier 4, paas instance identifier 4, and network address 192.168.1.105:80 in the row. The updated list of examples is shown in Table 4:

Table 4

In another possible implementation manner, the VNFM updates the instance list according to the instance update result, including:

In a case that the update type of the updated paas instance is terminated and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set according to the service type identifier of the paas instance;

If the service type identifier of the paas instance is retrieved, the identifier of the updated paas instance is terminated in the basic service identifier subset associated with the service type identifier of the updated paas instance in the instance list, and Terminating the network address of the updated paas instance in the network address subset associated with the service type identifier of the updated paas instance in the instance list.

For example, the update type of the updated paas instance is terminated, the service type identifier is defined by the first mode, the paas instance identifier is 5, the paas instance identifier is 8, and the VNFM retrieves the service in the service type identifier set of the instance list of Table 2. Type identifier 5, delete the paas instance identifier 8 in the paas instance identifier sub-collection associated with the service type identifier 5, and delete the network address 192.168.1.58:8080 in the network address sub-collection associated with the paas instance identifier 8, the updated instance list As shown in Table 5:

table 5

In another possible implementation manner, the VNFM updates the instance list according to the instance update result, including:

In a case that the update type of the updated paas instance is created and the service type identifier is defined by using the second manner, the search is performed in the paas instance identifier set according to the service type identifier of the update paas instance;

If the paas instance identifier is the same as the updated paas instance, the updated paas instance identifier is added to the paas instance identifier sub-collection associated with the paas instance identifier in the instance list, and the instance list is Adding the network address of the updated paas instance to the network address subset associated with the paas instance identifier; or

If the same paas instance identifier as the updated paas instance is not retrieved, the service type identifier of the updated paas instance is added to the service type identifier set, and the updated paas is in the instance list. The service type identifier of the instance identifies an identifier of the updated paas instance in the associated paas instance identifier sub-collection, and adds a network address sub-collection associated with the service type identifier of the updated paas instance in the instance list. The network address of the updated paas instance.

For example, the update type of the updated paas instance is created, and the service type identifier is defined by the second method. The service type identifier of the created paas instance is 8, the paas instance identifier is 10, the network address is 192.168.1.70:8080, and the VNFM is in the table. The service type identifier 8 shown in 2 retrieves the service type identifier 8, and the service type identifier 9 is not retrieved, and then the VNFM continues to retrieve in the paas instance identifier set of the instance list, and retrieves the paas instance identifier 8, which will update the paas instance. The identifier 10 is added to the paas instance identifier set corresponding to the paas instance identifier 8, and the network address 192.168.1.70:8080 is added to the network address subset. The updated instance list 3 is shown in Table 6.

Table 6

For example, the update type of the updated paas instance is created, the service type identifier is defined by the second method, the service type identifier of the created paas instance is 11, the updated paas instance identifier is 13, and the network address is 192.168.1.71: 8080. The VNFM first retrieves the service type identifier 11 in the service type identifier set of the instance list, does not retrieve the service type identifier 11, continues to search in the paas instance identifier set, still does not retrieve 11, creates a row, and adds an update in the row. The service type identifier, identifier, and network address of the paas instance. The updated instance list is shown in Table 7:

Table 7

In another possible implementation manner, the VNFM updates the instance list according to the instance update result, including:

In a case that the update type of the updated paas instance is terminated and the service type identifier is defined by using the second manner, the search is performed in the paas instance identifier set according to the service type identifier of the update paas instance;

If the paas instance identifier that is the same as the updated paas instance is retrieved, the identifier of the updated paas instance is terminated in the paas instance identifier sub-collection corresponding to the paas instance identifier in the instance list, and Terminating the network address of the updated paas instance in the network address sub-collection associated with the paas instance identifier in the instance list.

For example, the update type of the updated paas instance is terminated, and the service type identifier of the terminated service instance is defined by the second method. The service type identifier of the terminated paas instance is 12, and the identifier is 12, and the VNFM searches in the service type identifier set. The service type identifier 12, the search result is that the service type identifier 12 is not retrieved, and the search is continued in the paas instance identifier set, the paas instance identifier 12 is retrieved, the paas instance 12 is deleted in the paas instance identifier set, and the network address set is deleted. The associated network address, the updated instance list is shown in Table 8.

Table 8

S204. Update connection point configuration information corresponding to all VNFs associated with the basic service according to the instance update result.

Specifically, VNFM maintains the association between all VNF and all basic services in the paas platform in the NFV platform. The connection point configuration information of the VNF indicates the network address of the connection point of the VL instance to which the VNF belongs, and the VL instance is used to connect two VNFC instances, or a VNFC instance and a paas instance. When a VL instance needs to be connected to two instances, the connection with the two instances is the connection point, and the VNFM configures the network address of the connection point to be the same as the network address of the corresponding instance.

In a possible implementation manner, the VNFM updates the connection point configuration information of all the VNFs associated with the basic service according to the instance update structure, and the VNFM updates the pre-stored or pre-configured instance list according to the instance update result; the VNFM is pre-stored or pre-stored according to the pre-stored or pre-stored The configured connection relationship table queries all the VNFs associated with the basic service, and queries the VNFC instances associated with the VNFs. The VNFM redistributes the connection between the associated paas instance and all VNF-related VNFC instances. The VNFM updates the pre-stored or pre-configured connection relationship table according to the reassigned connection relationship, and updates the connection point configuration information of all the VNFs according to the updated connection relationship table.

Specifically, the connection relationship table is used to record the connection relationship between all VNFC instances in the NFV platform and all instances in the paas platform. Optionally, the connection relationship table includes at least one of a VNF identifier, a VNFC instance identifier, a paas instance identifier, and a VL instance identifier. The VNF identifier is used to uniquely represent the identity of the VNF. The VNF identifier can be assigned by the MANO when the VNF is created; the VNFC instance is used to uniquely represent the identity of the VNFC, and can also be assigned by the MANO; the VL instance is used to connect two instances, for example: VL An instance connects two VNFC instances, or connects to a VNFC instance and a paas instance. The VL instance has two connection points. The network address of the connection point is the same as the network address of the connected VNFC instance or paas instance. For example, the VL instance is used to connect to the VNFC. The connection point between the instance 1 and the VNFC instance 2, the VL instance and the VNFC instance 1 is set as the first connection point, the network address of the first connection point is the same as the network address of the VNFC instance 1, and between the VL instance and the VNFC instance 2 The connection point is the second connection point, and the network address of the second connection point is the same as the network address of the VNFC instance 2.

The connection point between the VL instance and the VNFC instance is an internal connection point, and the connection point between the VL instance and the paas instance is an external connection point.

For example, each row of the connection relation table represents a connection relationship, and the VNFM pre-stored or pre-configured connection relationship table is as shown in Table 9:

VNF logo	VNFC instance ID	Paas instance ID	VL instance ID
1	2	4	3
1	3	5	4
1	4	6	5

Table 9

The VNFM queries the paas instance after the instance update of the base service in the updated instance list. For example, the paas instance that belongs to the same service type identifier is queried in the updated instance list, and the queed instance is generated. List of paas instances. Then, the VNFC instance list is generated according to the retrieved VNFC instance according to each paas instance identifier in the paas instance list, and the VNFC instance list can be classified according to the VNF.

The VNFM re-allocates the connection between the VNFC instance in the VNFC instance list and the paas instance in the paas instance list according to a preset rule, for example, re-allocating the VNFC instance in the VNFC instance list and the paas instance in the paas instance list in a random manner. Ensure that a VNFC instance is connected to at least one paas instance. In the process of redistributing the connection relationship, there are three cases: the connection relationship between the VNFC instance and the paas instance remains unchanged, and the connection between the VNFC instance and the paas instance is deleted. The instance is changed to connect with other paas instances.

For example, the paas instance after the instance update of the basic service is paas instance 1, paas instance 5, and paas instance 6. The VNFM retrieves the VNFC instance associated with the base service as VNFC instance 2, VNFC instance 3, and VNFC instance in the connection relationship table. 4, wherein VNFC instance 2, VNFC instance 3, and VNFC instance 4 belong to VNF1. The connection relationship between the above three paas instances and three VNFC instances is as shown in Table 10:

VNF logo	VNFC instance ID	Paas instance ID	VL instance ID
1	2	1	7
1	3	5	8
2	4	6	9

Table 10

VNFM connects VNFC instance 2 with paas instance 1, connects VNFC instance 2 with paas instance 5, and connects VNFC instance 4 with paas instance 6. VNFC instance 2 and paas instance 1 are connected by VL instance 7, VNFC instance 3 and paas instance 5 are connected by VL instance 7, and VNFC instance 4 is connected by VL instance 8.

It should be noted that the re-allocation of the connection relationship in Table 10 is merely illustrative and does not limit the embodiments of the present invention.

The process of updating the connection relationship table by the VNFM may include:

The VNFM updates the connection relationship table according to the re-allocated connection relationship. The update process includes: retrieving the VNFC instance identifier and the VNF identifier according to the re-assigned connection relationship in the connection relationship table, if the VNFC is retrieved in the connection relationship table. The instance identifier and the VNF identifier are compared. The connection relationship retrieved in the connection relationship table is the same as the connection relationship corresponding to the VNFC instance identifier in the reassigned connection relationship. If they are the same, they remain unchanged. If they are not the same, the reclassified connection is The relationship overrides the connection relationship in the connection relationship table. If the VNFC instance ID is not retrieved, a row is created in the connection relationship table, and the VNF identifier, the VNFC instance identifier, and the paas instance identifier are added to the corresponding positions of the created row.

For example, the update process of the connection relation table is described according to the examples in Table 9 and Table 10:

The VNFC first searches in Table 9 according to the VNFC instance ID 2 and the VNF ID 1 in Table 10, and retrieves the VNFC instance ID 2 and the VNF ID 1 in Table 9, comparing the rows retrieved in Table 9 with the VNFC in Table 10. The row where the instance identifier 2 is located is different. The row in which the VNFC instance identifier 2 in the table 10 is located covers the row retrieved by the table 9. The VNFC searches in Table 9 according to the VNFC instance ID 1 and VNFC instance 3 in Table 10, and retrieves the VNFC instance ID 3 and the VNF ID 1, and compares the rows retrieved in Table 9 with the corresponding rows in Table 10, which will be inconsistent. The row corresponding to the VNFC identifier 3 and the VNF identifier 1 in Table 10 covers the rows retrieved in Table 9. The VNFM searches in Table 9 according to the VNFC Instance ID 4 and the VNF ID 2, and does not retrieve the corresponding row in Table 9, creates 1 row in Table 9, and adds VNFC Instance 4 and VNF ID in Table 10 in the row. 2 corresponding identifier.

According to the update process of the above connection relationship table, the updated connection relationship table is as shown in Table 11.

VNF logo	VNFC instance ID	Paas instance ID	VL instance ID
1	2	1	7
1	3	5	8
2	4	6	9
1	4	6	5

Table 11

The process of updating the connection point configuration information of all VNFs by the VNFM may include:

The VNFM obtains the modified connection relationship or the created connection relationship in the updated connection relationship table. If the modified connection relationship or the created connection relationship includes the VL instance identifier, the external connection point configuration information of the corresponding VL instance is configured as the connected The network address of the paas instance; if the modified or created connection does not include the VL instance ID, create a VL instance, configure the internal connection point configuration information of the created VL as the network address of the connected VNFC instance, and create the VL. The external connection point configuration information of the instance is configured as the network address of the connected paas instance, and the identifier of the created VL instance is added to the connection relationship.

For example, the process of updating the connection point configuration information of the VNF according to the connection relationship table of Table 11 is explained:

The VNFM determines that the row (connection relationship) in which the update occurs in Table 11 is the first to third rows, and the VNFM configures the network address of the internal connection point of the VL instance 7 as the network address of the VNFC instance 2, and the external connection of the VL instance 7 The network address of the point is configured as the network address of paas instance 1. The VNFM configures the network address of the internal connection point of the VL instance 8 as the network address of the VNFC instance 2, and configures the network address of the external connection point of the VL instance 8 as the network address of the paas instance 5. The VNFM configures the network address of the internal connection point of the VL instance 9 as the network address of the VNFC instance 4, and configures the network address of the external connection point of the VL instance 9 as the network address of the paas instance 6.

In the method described in FIG. 2, the VNFM maintains an instance list and a connection relationship table, and the VNFM updates the instance list according to the instance update result of the basic service notified by the paas management network element, and redistributes the paas instance after the basic service occurrence instance is updated. The connection relationship between the VNFC instances of the VNF is updated according to the re-allocated connection relationship, and the call relationship between the basic service and the VNF can be automatically re-established to achieve the purpose of quickly recovering the service.

FIG. 3 is a schematic flowchart of a method for managing a virtual network element according to an embodiment of the present invention. In this embodiment, the method includes the following steps:

S301. The VNFM detects that the VNF satisfies the instance update condition, and performs an instance update on the VNF.

Specifically, the instance update condition is a condition for triggering termination or creation of an instance of the VNF, and the instance of terminating or creating the VNF includes a VNFC instance and/or a VL instance. The VNFM may determine whether the instance update condition is met according to the load of the VNFC instance associated with the VNF, and the load includes, but is not limited to, at least one of a CPU load, a memory load, and a disk load.

In a possible implementation manner, the VNFM uses the method 1 to determine whether the instance update condition is met: the VNFM obtains the average load of the load of all VNFC instances associated with the VNF, and if the average load is greater than the first load threshold, determining that the VNF satisfies the instance update condition. Or, if the average load is less than the second load threshold, it is determined that the VNF satisfies the instance update condition.

In another possible implementation manner, the VNFM uses the second method to determine whether the instance update condition is met: the VNFM acquires the load of at least one VNFC instance in all VNFC instances associated with the VNF, and if each VNFC instance in the at least one VNFC instance load The load is greater than the first load threshold, determining that the VNF meets the instance update condition; or if the load of each VNFC instance in the at least one VNFC instance is less than the second load threshold, determining that the VNF meets the instance update condition.

The above example updates the detection mode, and the first load threshold is greater than or equal to the second load threshold.

The VNFM may indicate that the VNF performs an instance update by sending a VNF instance update indication, and the instance update indication is used to instruct the VNF to increase or decrease the instance (the VL instance and/or the VNFC instance according to the pre-stored or pre-configured instance update policy).

S302. The VNFM obtains an instance update result of the VNF.

Specifically, the instance update result indicates attribute information of an instance (VNFC instance and/or VL instance) in which an increase or decrease occurs in the VNF, for example, the instance update result includes at least one of a VNF identifier, a VL instance identifier, and a VNFC identifier.

S303. The VNFM updates the connection point configuration information of the VNF.

Specifically, the connection point configuration information of the VNF indicates the network address of the connection point of the VL instance to which the VNF belongs, and the VL instance is used to connect two VNFC instances, or a VNFC instance and a paas instance. When a VL instance needs to be connected to two instances, the connection with the two instances is the connection point, and the VNFM configures the network address of the connection point to be the same as the network address of the corresponding instance.

In a possible design, updating the connection point configuration information of the VNF according to the VNF instance update result includes:

Query all the basic services associated with the VNF according to the pre-stored or pre-configured connection relationship table, and query the paas instances associated with all the basic services. The VNFM re-allocates between the associated instance after the instance update and the paas instance associated with all the basic services. The connection relationship, updating the pre-stored or pre-configured connection relationship table according to the re-allocated connection relationship, and updating the connection point configuration information of the VNF associated with the VNF according to the updated connection relationship table.

Specifically, the instance update result indicates attribute information of the updated instance in the VNF, for example, the attribute information includes at least one of a VNF identifier, a VNFC instance identifier, and a VL instance identifier. In a possible implementation manner, the instance update result is expressed in the form of a table, for example, the instance update result is as shown in Table 12:

VNF logo	VNFC instance ID	VL instance ID
2	5	11
2	6	12

Table 12

The VNFM obtains a VNFC instance that is associated with the VNF instance update. For example, the VNFM searches for a VNFC instance that belongs to the same VNF as the VNFC instance updated in the VNF in the instance list, and generates a VNFC instance list according to the found VNFC instance, according to the found VNFC. The instance finds all the corresponding paas instances in the connection relationship table, generates a paas instance list according to the found paas instance, and reassigns the connection relationship between the VNFC instance in the VNFC instance list and the paas instance in the paas instance list to ensure the VNFC instance and At least one paas instance is connected, and the process of reassigning the connection relationship is described in the description of the embodiment of FIG. 2, and details are not described herein again.

The process of updating the connection relationship table by the VNFM may include:

The VNFM updates the connection relationship table according to the re-allocated connection relationship. The update process includes: retrieving the VNFC instance identifier according to the re-allocated connection relationship in the connection relationship table, and if the VNFC instance identifier is retrieved in the connection relationship table, The connection relationship between the connection relationship and the re-assigned connection relationship in the connection relationship table is the same as that of the VNFC instance ID. If they are the same, they remain unchanged. If they are not the same, the re-classified connection relationship is overwritten with the update connection relationship table. If the VNFC instance ID is not retrieved, create a row in the connection relationship table, and add the VNF ID, VNFC instance ID, and paas instance ID to the corresponding location of the created row.

The process of updating the VNF connection point configuration information by the VNFM may include:

The VNFM obtains the modified connection relationship or the created connection relationship in the updated connection relationship table. If the modified connection relationship or the created connection relationship includes the VL instance identifier, configure the external connection point configuration information of the corresponding VL instance as the The network address of the connected paas instance. If the VL instance ID is not included in the modified or created connection relationship, create a VL instance and configure the internal connection point configuration information of the created VL as the network address of the connected VNFC instance. The external connection point configuration information of the VL instance is configured as the network address of the connected paas instance, and the identifier of the created VL instance is added to the connection relationship.

In the method described in FIG. 3, the VNFM maintains a connection relationship table, and the VNFM re-allocates the connection relationship between the VNF instance instance updated instance and the VNF corresponding paas instance according to the VNF instance update result, according to the reassigned connection relationship. The connection relationship table is updated, and the calling relationship between the VNF and the basic service can be automatically re-established to achieve the purpose of quickly recovering the service.

FIG. 4 is a schematic flowchart of a method for creating a virtual network element according to an embodiment of the present invention. In the embodiment of the present invention, the method includes:

S401, VNFM create a VNF.

Specifically, the VNFM can instantiate the created VNF according to the VNFD (virtual network function descriptor), allocate a VNFC instance to the created VNF, and configure related parameters of the VFN, so that the created VNF can be a logical entity. run. The VNFM obtains the VNFC instance allocation result of the created VNF. The VNFC instance allocation result includes the attribute information of the VNFC allocated to the VNF, and the attribute information includes, but is not limited to, at least one of a VNFC identifier, a VNF identifier, and a VNFC instance identifier.

S402. The VNFM sends a request for allocating a basic service to the paas management network element, and the paas management network element receives the request from the VNFM.

Specifically, when the VNF needs to invoke an basic service, the VNFM sends a request for the basic service to the paas management network element, where the request may carry the attribute information of the basic service, where the attribute information includes but is not limited to: deployment location information, basic capabilities Information and identity, etc.

S403. The paas management network element sends a paas instance allocation result to the VNFM, and the VNFM receives the paas instance allocation result from the paas management network element.

The paas instance allocation result indicates that the paas management network element is the attribute information of the paas instance allocated by the created VNF, and the attribute information includes, but is not limited to, at least one of a paas instance identifier, a service type identifier, and a network address. The paas instance identifies the identity that is used to uniquely represent the paas instance. The service type identifier indicates the service type of the paas instance. The service type identifiers of all paas instances associated with the base service are the same or different. The network address indicates the address of the paas instance for external service. The representation of the paas instance assignment result can be a table, an array, a linked list, or a structure. The paas instance assigned by the paas management NE to the VNF may be an existing paas instance or a created paas instance.

S404, VNFM update the list of instances.

Specifically, the VNFM updates the pre-stored or pre-configured instance list according to the paas instance allocation result, where the instance list represents attribute information of all paas instances in the paas platform, and the attribute information includes at least one of an identifier, a service type identifier, and a network address. The VNFM searches in the instance list. If the instance list includes the attribute information of the assigned paas instance, the instance list is not updated; if the assigned paas instance is not included in the instance list, the attribute information of the assigned paas instance is added to the instance. List.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, the service type identifier set includes n service type identifiers, and the paas instance identifier set includes n paas The instance identifier sub-collection, the network address set includes n network address sub-sets, the service type identifier in the service type identifier set, the paas instance identifier sub-collection in the paas instance identifier set, and the network address sub-set in the network address set are one-to-one correspondence , that is, the instance list includes n rows, each row includes a service type identifier having an association relationship, a paas instance identifier sub-collection and a network address sub-collection, a service type identifier set, a paas instance identifier set, and a network address set are columns of an instance list. .

S405 and VNFM allocate a connection relationship.

The VNFM allocates the connection relationship between the VNFC instance in the VNFC instance assignment result and the paas instance in the paas instance assignment result in S403. For example, the VNFM allocates the connection relationship in a random manner to ensure that the VNFC instance is connected to at least one paas instance. . The connection between the paas instance and the VNFC instance is required. The paas instance and the VNFC instance are connected through the VL instance. In the process of assigning a connection relationship, you need to ensure that each VNFC instance establishes a connection relationship with at least one paas instance.

S406. The VNFM updates the connection relationship table.

Specifically, the connection relationship table is pre-stored or pre-configured, and the connection relationship table may be set in the VNFM, and the connection relationship table is used to record the connection relationship between all VNFC instances in the NFV platform and all instances in the paas platform. The VNFM updates the connection relationship table according to the allocated connection relationship. The update process includes: searching for the VNFC instance identifier according to the assigned connection relationship in the connection relationship table. If the VNFC instance identifier is retrieved in the connection relationship table, the comparison is performed. The connection relationship between the connection relationship and the re-assigned connection relationship in the connection relationship table is the same as the connection relationship of the VNFC instance ID. If they are the same, they remain unchanged. If they are not the same, the re-classified connection relationship is overwritten in the update connection relationship table. If the VNFC instance ID is not retrieved, create a row in the connection relationship table, and add the VNF ID, VNFC instance ID, and paas instance ID to the corresponding location of the created line.

S407. The VNFM updates the connection point configuration information of the VNF.

Specifically, the VNFM obtains the modified connection relationship or the created connection relationship in the updated connection relationship table. If the modified connection relationship or the created connection relationship includes the VL instance identifier, the network address of the external connection point of the corresponding VL instance is configured. The network address of the connected paas instance. If the modified or created connection does not include the VL instance ID, create a VL instance and configure the network address of the created VL internal connection point as the network address of the connected VNFC instance. The network address of the external connection point of the created VL instance is configured as the network address of the connected paas instance, and the identifier of the created VL instance is added to the connection relationship.

In the method described in FIG. 4, the VNFM maintains an instance list and a connection relationship table, and the VNFM allocates a connection relationship between the VNF-associated paas instance and the VNF VNFC instance according to the created VNF allocation and the paas instance update instance list, according to the allocated relationship. The connection relationship updates the connection relationship table, and can automatically establish a calling relationship between the basic service and the VNF to achieve the purpose of quickly establishing a service.

The above describes the method of the embodiment of the present invention in detail, and the apparatus of the embodiment of the present invention is provided below.

Referring to FIG. 5, FIG. 5 is a schematic structural diagram of a virtual network element management apparatus according to an embodiment of the present invention. Hereinafter, the management apparatus 5 may include a processing unit 501 and a sending unit 502, where each unit is included. The detailed description is as follows.

The processing unit 501 is configured to perform an instance update on the basic service if the basic service satisfies the instance update condition; for example, the processing unit 501 performs S201 and S202 in FIG. 2 .

The sending unit 502 is configured to send an instance update result of the basic service to the virtual network function management network element VNFM. For example, the transmitting unit 502 is configured to execute S203 in FIG. 2.

In a possible implementation manner, the instance update result includes at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the basic service.

In a possible implementation, the processing unit 501 is configured to: before the basic service meets the instance update condition, before the paas management network element updates the basic service, the method is further configured to:

Detecting an average load of all paas instances associated with the base service;

Determining that the average load is greater than a first load threshold; or

It is determined that the average load is less than a second load threshold.

In a possible implementation manner, the service type identifier is defined in a first manner, and all paas instances associated with the base service have the same service type identifier.

In a possible implementation, the processing unit 501 is configured to: before the basic service meets the instance update condition, before the paas management network element updates the basic service, the method is further configured to:

Detecting the load of at least one paas instance in all paas instances associated with the underlying service;

Determining that a load of each paas instance in the at least one paas instance is greater than a first load threshold; or

Determining that the load of each paas instance in the at least one paas instance is less than a second load threshold.

In a possible implementation manner, the service type identifier is defined in a second manner, and all paas instances associated with the basic service have different service type identifiers, and the service type of the paas instance is when the update type of the paas instance is terminated. The identity is the same as the identity of the paas instance.

The management device 5 can be a paas management network element, and the management device 5 can also be a field-programmable gate array (FPGA), a dedicated integrated chip, and a system on chip (SoC). , central processor unit (CPU), network processor (network processor, NP), digital signal processing circuit, microcontroller (micro controller unit (MCU), can also use programmable logic device (programmable logic device, PLD) or other integrated chips.

The embodiment of the present invention and the method embodiment of FIG. 2 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 2, and details are not described herein again.

As shown in FIG. 6, the embodiment of the present invention further provides a management device for a virtual network element, hereinafter referred to as the management device 6.

In a possible design, the management device 6 is a paas management network element, and the paas management network element includes:

The memory 602 is configured to store programs and data. The number of memories may be one or more, and the type of the memory may be any form of storage medium. For example, the memory may be a random access memory (English: random access memory, RAM for short) or a read only memory (English: read only memory, abbreviated as: ROM) or a flash memory, wherein the memory 602 may be located separately in the terminal device, It can be located inside the processor 601.

The receiver 603 is configured to receive a signal. The receiver 603 can be a separate chip or a receiving circuit within the processor 601 or as an input interface.

The processor 601 is configured to execute the program code stored in the memory 602, and when the program code is executed, the processor 601 is used to perform an instance update on the basic service if the basic service satisfies the instance update condition; for example The processor 601 performs S201 and S202 in FIG.

A transmitter 604 is configured to transmit a signal. Transmitter 604 can function as a separate chip, as well as a transmit circuit within processor 601 or as an output interface. Optionally, the transmitter 1504 can also include a transmit antenna. The transmitting antenna included in the transmitter 1504 and the receiving antenna included in the receiver 1503 may be two antennas separately provided, or may be one antenna. The transmitter 604 is configured to send an instance update result of the basic service to the virtual network function management network element VNFM, for example, the transmitter performs S203 in FIG. 2.

The receiver 603, the transmitter 604, the memory 602, and the processor 601 communicate with each other through an internal connection path, for example, via a bus.

In a possible implementation, the processor 601 is further configured to:

Detecting an average load of all paas instances associated with the base service;

Determining that the average load is greater than a first load threshold; or

It is determined that the average load is less than a second load threshold.

In a possible implementation manner, the service type identifier is defined in a first manner, and all paas instances associated with the base service have the same service type identifier.

In a possible implementation, the processor 601 is further configured to:

Detecting the load of at least one paas instance in all paas instances associated with the underlying service;

Determining that a load of each paas instance in the at least one paas instance is greater than a first load threshold; or

Determining that the load of each paas instance in the at least one paas instance is less than a second load threshold.

In a possible implementation manner, the service type identifier is defined in a second manner, and all paas instances associated with the basic service have different service type identifiers, and the service type of the paas instance is when the update type of the paas instance is terminated. The identity is the same as the identity of the paas instance.

In one possible design, the management device 6 can be a chip, for example, can be a processor chip in a computing device for implementing related functions of the processor in the computing device. The chip can be a field programmable gate array for implementing related functions, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, and a programmable controller or other integrated chip. In the chip, optionally, one or more memories may be included for storing program code, and when the program code is executed, the processor implements corresponding functions.

These chips may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (sometimes referred to as code or programs). When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

The embodiment of the present invention and the method embodiment of FIG. 2 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 2, and details are not described herein again.

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of a maintenance device for a virtual network element according to an embodiment of the present invention. Hereinafter, the maintenance device 7 may include a receiving unit 701 and a processing unit 702, where each unit is included. The detailed description is as follows.

The receiving unit 701 is configured to receive an instance update result about the basic service from the paas management network element; for example, the receiving unit 701 performs S203 in FIG. 2 .

The processing unit 702 updates connection point configuration information of all VNFs associated with the base service according to the instance update result. For example, the processing unit 702 performs S204 in FIG.

In a possible implementation, the processing unit 702 updates the connection point configuration information of all the VNFs associated with the basic service according to the instance update result, specifically:

Updating the instance list according to the instance update result;

Querying, according to the connection relationship table, all VNFs associated with the basic service, and VNFC instances associated with all the VNFs;

Redistributing the connection relationship between the associated paas instance and the VNFC instance associated with all the VNFs after the instance update is completed;

Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of all the VNFs according to the updated connection relationship table.

In a possible implementation manner, the instance update result includes at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the basic service.

In a possible implementation manner, the service type identifier is defined in a first manner, and all paas instances associated with the basic service have the same service type identifier; or

The service type identifier is defined in the second mode, and all the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier of the paas instance.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, where the service type identifier set includes n service type identifiers, and the paas instance The identifier set includes n paas instance identifier sub-sets, the network address set includes n network address sub-sets, the service type identifier in the service type identifier, the paas instance identifier sub-collection in the paas instance identifier set, and The network address subsets in the network address set are in one-to-one correspondence, and n is an integer greater than 0.

In a possible implementation reflection, the processing unit 702 is configured to update the instance list according to the instance update result, specifically:

In a case that the update type of the updated paas instance is created and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance;

If the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection associated with the updated paas instance's update type, and in the update with the Adding the network address of the updated paas instance to the network address sub-collection associated with the paas instance; or

If the service type identifier of the updated paas instance is not retrieved, adding the service type identifier of the updated paas instance to the service type identifier set, and being associated with the service type identifier of the updated paas instance The paas instance identifies the identifier of the updated paas instance in the sub-collection, and adds the network address of the updated paas instance in the network address sub-collection associated with the service type identifier of the updated paas instance.

In a possible implementation, the processing unit 702 is configured to update the instance list according to the instance update result, specifically:

If the update type of the updated paas instance is termination and the service type identifier is defined by using the first manner, searching is performed in the service type identifier set according to the service type identifier of the updated paas instance;

If the service type identifier of the paas instance is retrieved, the identifier of the updated paas instance is deleted in the basic service identifier subset associated with the service type identifier of the updated paas instance, and in the updated paas The service type of the instance identifies the network address of the updated paas instance in the associated network address sub-collection.

In a possible implementation, the processing unit 702 is configured to update the instance list according to the instance update result, specifically:

In the case that the update type of the updated paas instance is created and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the updated paas instance;

If the paas instance identifier that is the same as the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection with the paas instance identifier, and the paas Adding, by the instance identifier, the network address of the updated paas instance in the associated network address sub-collection; or

If the paas instance identifier that is the same as the service type identifier of the updated paas instance is not retrieved, the service type identifier of the updated paas instance is added to the service type identifier set, and the paas instance is updated with the The service type identifier identifies the associated paas instance identifier sub-collection, the identifier of the updated paas instance is added, and the updated paas instance is added to the network address sub-collection associated with the service type identifier of the updated paas instance. website address.

In a possible implementation manner, the processing unit 702 updates the instance list according to the instance update result, specifically:

In the case that the update type of the updated paas instance is terminated and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the update paas instance;

If the paas instance identifier that is the same as the updated paas instance is retrieved, the identifier of the updated paas instance is terminated in the paas instance identifier sub-collection corresponding to the paas instance identifier in the instance list, and Terminating the network address of the updated paas instance in the network address sub-collection associated with the paas instance identifier in the instance list.

In a possible implementation manner, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

In a possible implementation, the processing unit 702 is configured to re-allocate the connection relationship between the associated paas instance and the VNFC instance associated with the at least one VNF.

Reconnecting the connection relationship between the associated paas instance and the at least one VNFC instance after the instance update is performed in a random manner; wherein each paas instance is connected to at least one VNFC instance.

In a possible implementation, the processing unit 702 is configured to update the connection relationship table, specifically:

Retrieving the VNFC instance identifier to be updated in the connection relationship table according to the reassigned connection relationship;

If the VNFC instance identifier to be updated is retrieved, the connection relationship between the VNFC instance identifier to be updated in the reassigned connection relationship and the connection relationship between the VNFC instance to be updated in the connection relationship table is compared. the same;

If the same, do not perform the update;

If not, the connection relationship between the re-allocated connection relationship and the VNFC instance to be updated in the connection relationship table is determined according to the VNFC instance to be updated;

If the VNFC instance identifier to be updated is not retrieved, a row is created in the connection relationship table, and a connection relationship corresponding to the VNFC instance to be updated in the connection relationship table is added in the created row.

In a possible implementation, the processing unit 702 is configured to update connection point configuration information of all VNF associations, specifically: obtaining a connection relationship modified or created in the updated connection relationship table, if the connection relationship is modified or created. The VL instance identifier is included, and the network address of the external connection point of the corresponding VL instance is configured as the network address of the connected paas instance; if the modified or created connection relationship does not include the VL instance identifier, creating a VL instance will be created. The internal connection point configuration information of the VL instance is configured as the network address of the connected VNFC instance, and the external connection point configuration information of the created VL instance is configured as the network address of the connected paas instance, and the identifier of the VL instance to be created. Add to this connection relationship.

The maintenance device 7 may be a VNFM, and the maintenance device 7 may also be a field-programmable gate array (FPGA), a dedicated integrated chip, a system on chip (SoC), and a central processing. Central processor unit (CPU), network processor (NP), digital signal processing circuit, microcontroller (micro controller unit (MCU), can also use programmable logic device (PLD) or Other integrated chips.

The embodiment of the present invention and the method embodiment of FIG. 2 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 2, and details are not described herein again.

As shown in FIG. 8, the embodiment of the present invention further provides a maintenance device 8 for a virtual network element, hereinafter referred to as a maintenance device 8.

In one possible design, the maintenance device 8 is a VNFM, and the VNFM includes:

The memory 802 is configured to store programs and data. The number of the memories may be one or more, and the type of the memory may be any form of storage medium. For example, the memory may be a random access memory (English: random access memory, RAM for short) or a read only memory (English: read only memory, abbreviated as: ROM) or a flash memory, wherein the memory 802 may be located separately in the terminal device, It can be located inside the processor 801.

The receiver 803 is configured to receive a signal. The receiver 803 can be a separate chip or a receiving circuit within the processor 801 or as an input interface. The receiver 803 is configured to receive an instance update result about the basic service from the paas management network element; for example, the receiver 801 performs S203 in FIG. 2.

The processor 801 is configured to execute the program code stored by the memory 802, and when the program code is executed, the processor 801 is configured to update a connection point configuration of all VNFs associated with the basic service according to the instance update result. information. For example, the processor 801 executes S204 in FIG.

A transmitter 804 is configured to transmit a signal. Transmitter 804 can function as a separate chip, as well as a transmit circuit within processor 801 or as an output interface.

The receiver 803, the transmitter 804, the memory 802, and the processor 801 communicate with each other through an internal connection path, for example, via a bus.

In a possible implementation, the processor 801 updates the connection point configuration information of all the VNFs associated with the basic service according to the instance update result, specifically:

Updating the instance list according to the instance update result;

Querying, according to the connection relationship table, all VNFs associated with the basic service, and VNFC instances associated with all the VNFs;

Redistributing the connection relationship between the associated paas instance and the VNFC instance associated with all the VNFs after the instance update is completed;

Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of all the VNFs according to the updated connection relationship table.

In a possible implementation manner, the instance update result includes at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the basic service.

In a possible implementation manner, the service type identifier is defined in a first manner, and all paas instances associated with the basic service have the same service type identifier; or

The service type identifier is defined in the second mode, and all the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier of the paas instance.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, where the service type identifier set includes n service type identifiers, and the paas instance The identifier set includes n paas instance identifier sub-sets, the network address set includes n network address sub-sets, the service type identifier in the service type identifier, the paas instance identifier sub-collection in the paas instance identifier set, and The network address subsets in the network address set are in one-to-one correspondence, and n is an integer greater than 0.

In a possible implementation reflection, the processor 801 is configured to update the instance list according to the instance update result, specifically:

In a case that the update type of the updated paas instance is created and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance;

If the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection associated with the updated paas instance's update type, and in the update with the Adding the network address of the updated paas instance to the network address sub-collection associated with the paas instance; or

If the service type identifier of the updated paas instance is not retrieved, adding the service type identifier of the updated paas instance to the service type identifier set, and being associated with the service type identifier of the updated paas instance The paas instance identifies the identifier of the updated paas instance in the sub-collection, and adds the network address of the updated paas instance in the network address sub-collection associated with the service type identifier of the updated paas instance.

In a possible implementation, the processor 801 is configured to update the instance list according to the instance update result, specifically:

If the update type of the updated paas instance is termination and the service type identifier is defined by using the first manner, searching is performed in the service type identifier set according to the service type identifier of the updated paas instance;

If the service type identifier of the paas instance is retrieved, the identifier of the updated paas instance is deleted in the basic service identifier subset associated with the service type identifier of the updated paas instance, and in the updated paas The service type of the instance identifies the network address of the updated paas instance in the associated network address sub-collection.

In a possible implementation, the processor 801 is configured to update the instance list according to the instance update result, specifically:

In the case that the update type of the updated paas instance is created and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the updated paas instance;

If the paas instance identifier that is the same as the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection with the paas instance identifier, and the paas Adding, by the instance identifier, the network address of the updated paas instance in the associated network address sub-collection; or

If the paas instance identifier that is the same as the service type identifier of the updated paas instance is not retrieved, the service type identifier of the updated paas instance is added to the service type identifier set, and the paas instance is updated with the The service type identifier identifies the associated paas instance identifier sub-collection, the identifier of the updated paas instance is added, and the updated paas instance is added to the network address sub-collection associated with the service type identifier of the updated paas instance. website address.

In a possible implementation manner, the processor 801 updates the instance list according to the instance update result, specifically:

In the case that the update type of the updated paas instance is terminated and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the update paas instance;

If the paas instance identifier that is the same as the updated paas instance is retrieved, the identifier of the updated paas instance is terminated in the paas instance identifier sub-collection corresponding to the paas instance identifier in the instance list, and Terminating the network address of the updated paas instance in the network address sub-collection associated with the paas instance identifier in the instance list.

In a possible implementation manner, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

In a possible implementation, the processor 801 is configured to re-allocate the connection relationship between the associated paas instance and the VNFC instance associated with the at least one VNF.

Reconnecting the connection relationship between the associated paas instance and the at least one VNFC instance after the instance update is performed in a random manner; wherein each paas instance is connected to at least one VNFC instance.

In a possible implementation manner, the processor 801 performs an update connection relationship table, specifically:

Retrieving the VNFC instance identifier to be updated in the connection relationship table according to the reassigned connection relationship;

If the VNFC instance identifier to be updated is retrieved, the connection relationship between the VNFC instance identifier to be updated in the reassigned connection relationship and the connection relationship between the VNFC instance to be updated in the connection relationship table is compared. the same;

If the same, do not perform the update;

If not, the connection relationship between the re-allocated connection relationship and the VNFC instance to be updated in the connection relationship table is determined according to the VNFC instance to be updated;

If the VNFC instance identifier to be updated is not retrieved, a row is created in the connection relationship table, and a connection relationship corresponding to the VNFC instance to be updated in the connection relationship table is added in the created row.

In a possible implementation manner, the processor 801 performs connection point configuration information for updating all VNF associations, specifically: obtaining a connection relationship modified or created in the updated connection relationship table, if the modified or created connection relationship is included. VL instance identifier, the network address of the external connection point of the corresponding VL instance is configured as the network address of the connected paas instance; if the modified or created connection relationship does not include the VL instance identifier, a VL instance is created, and the VL will be created. The internal connection point configuration information of the instance is configured as the network address of the connected VNFC instance, the external connection point configuration information of the created VL instance is configured as the network address of the connected paas instance, and the identifier of the created VL instance is added to In the connection relationship.

In one possible design, the maintenance device 8 can be a chip, for example, can be a processor chip in a computing device for implementing the relevant functions of the processor in the computing device. The chip can be a field programmable gate array for implementing related functions, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, and a programmable controller or other integrated chip. In the chip, optionally, one or more memories may be included for storing program code, and when the program code is executed, the processor implements corresponding functions.

These chips may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (sometimes referred to as code or programs). When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

The embodiment of the present invention and the method embodiment of FIG. 2 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 2, and details are not described herein again.

Referring to FIG. 9, FIG. 9 is a schematic structural diagram of a control device for a virtual network element according to an embodiment of the present invention. Hereinafter, the control device 9 may include an obtaining unit 901 and a processing unit 902, where each unit is used. The detailed description is as follows.

The obtaining unit 901 is configured to acquire an instance update result of the VNF if the VNF satisfies the instance update condition; for example, the obtaining unit 901 is configured to execute S301 and S302 in FIG. 3 .

The processing unit 902 is configured to update the connection point configuration information of the VNF according to the instance update result of the VNF. For example, the processing unit 902 is configured to execute S303 in FIG.

Obtaining an instance update result of the VNF when the VNF satisfies the instance update condition;

Updating the connection point configuration information of the VNF according to the instance update result of the VNF.

In a possible implementation, the processing unit 902 updates the connection point configuration information of the VNF according to the instance update result of the VNF, specifically:

Querying all basic services associated with the VNF according to the connection relationship table, and querying a paas instance associated with all the basic services;

Redistributing the connection relationship between the VNF and the queried instance of the queried instance;

Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of the VL associated with the VNF according to the updated connection relationship table.

In a possible implementation manner, the instance update result includes at least one of an identifier of the VNF, an identifier of a VNFC instance associated with the VNF, and a VL instance identifier.

In a possible implementation manner, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

The control device 9 may be a VNFM, and the control device 9 may also be a field-programmable gate array (FPGA), a dedicated integrated chip, a system on chip (SoC), and a central processing. Central processor unit (CPU), network processor (NP), digital signal processing circuit, microcontroller (micro controller unit (MCU), can also use programmable logic device (PLD) or Other integrated chips.

The embodiment of the present invention and the method embodiment of FIG. 3 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 3, and details are not described herein again.

As shown in FIG. 10, the embodiment of the present invention further provides a control device for a virtual network element, hereinafter referred to as the control device 10.

In one possible design, the control device 10 is a VNFM, and the VNFM includes:

The memory 1002 is configured to store programs and data. The number of the memories may be one or more, and the type of the memory may be any form of storage medium. For example, the memory may be a random access memory (English: random access memory, RAM for short) or a read only memory (English: read only memory, abbreviated as: ROM) or a flash memory, wherein the memory 1002 may be located separately in the terminal device, It may be located inside the processor 1001.

The receiver 1003 is configured to receive a signal. The receiver 1003 can be a separate chip or a receiving circuit within the processor 1001 or as an input interface.

The processor 1001 is configured to execute the program code stored in the memory 1002. When the program code is executed, the processor 1001 is configured to obtain an instance update result of the VNF if the VNF satisfies the instance update condition; The instance update result of the VNF updates the connection point configuration information of the VNF. For example, the processor 1001 is configured to execute S301, S302, and S303 in FIG.

A transmitter 1004 is configured to transmit a signal. The transmitter 1004 can be a separate chip, or can be a transmit circuit within the processor 1001 or as an output interface.

The receiver 1003, the transmitter 1004, the memory 1002, and the processor 1001 communicate with each other through an internal connection path, for example, via a bus.

In a possible implementation, the processor 1001 performs connection point configuration information that updates the VNF according to the instance update result of the VNF, specifically:

Querying all basic services associated with the VNF according to the connection relationship table, and querying a paas instance associated with all the basic services;

Redistributing the connection relationship between the VNF and the queried instance of the queried instance;

Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of the VL associated with the VNF according to the updated connection relationship table.

In a possible implementation manner, the instance update result includes at least one of an identifier of the VNF, an identifier of a VNFC instance associated with the VNF, and a VL instance identifier.

In a possible implementation manner, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

In one possible design, the control device 10 can be a chip, for example, can be a processor chip in a computing device for implementing related functions of the processor in the computing device. The chip can be a field programmable gate array for implementing related functions, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, and a programmable controller or other integrated chip. In the chip, optionally, one or more memories may be included for storing program code, and when the program code is executed, the processor implements corresponding functions.

These chips may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (sometimes referred to as code or programs). When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

The embodiment of the present invention and the method embodiment of FIG. 3 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 3, and details are not described herein again.

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of a device for creating a virtual network element according to an embodiment of the present invention. The following is abbreviated as a creating device 11 that may include an obtaining unit 1101 and a processing unit 1102, where each unit is used. The detailed description is as follows.

The obtaining unit 1101 is configured to acquire a paas instance allocation result and a VNFC instance allocation result of the VNF in a case that a VNF needs to be created; for example, the obtaining unit 1101 is configured to execute S401 to S403 in FIG. 4 .

The processing unit 1102 is configured to update the instance list according to the paas instance allocation result;

Allocating a connection relationship between the VNFC instance corresponding to the VNFC instance assignment result and the paas instance assignment result corresponding to the paas instance;

Updating the connection relationship table according to the allocated connection relationship, and updating the connection point configuration information of the VNF according to the updated connection relationship table. For example, the processing unit 1102 is configured to execute S404 to S407 in FIG.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, where the service type identifier set includes n service type identifiers, and the paas instance The identifier set includes n paas instance identifier sub-sets, the network address set includes n network address sub-sets, the service type identifier in the service type identifier, the paas instance identifier sub-collection in the paas instance identifier set, and The network address subsets in the network address set are in one-to-one correspondence, and n is an integer greater than 0.

In a possible implementation, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

For the specific process of updating the implementation list and the connection relationship table in this embodiment, reference may be made to FIG. 2, and details are not described herein again.

The creating device 11 may be a VNFM, and the creating device 11 may also be a field-programmable gate array (FPGA), a dedicated integrated chip, a system on chip (SoC), and a central processing. Central processor unit (CPU), network processor (NP), digital signal processing circuit, microcontroller (micro controller unit (MCU), can also use programmable logic device (PLD) or Other integrated chips.

The embodiment of the present invention and the method embodiment of FIG. 4 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 3, and details are not described herein again.

As shown in FIG. 12, the embodiment of the present invention further provides a virtual network element creation device 12, hereinafter referred to as the creation device 12.

In one possible design, the creation device 12 is a VNFM, and the VNFM includes:

The memory 1202 is configured to store programs and data. The number of the memories may be one or more, and the type of the memory may be any form of storage medium. For example, the memory may be a random access memory (English: random access memory, RAM for short) or a read only memory (English: read only memory, abbreviated as: ROM) or a flash memory, wherein the memory 1202 may be located separately in the terminal device, It may be located inside the processor 1201.

The receiver 1203 is configured to receive a signal. The receiver 1203 can be a separate chip or a receiving circuit within the processor 1201 or as an input interface.

The processor 1201 is configured to execute the program code stored in the memory 1202. When the program code is executed, the processor 1201 is configured to acquire a paas instance allocation result and a VNFC instance of the VNF if a VNF needs to be created. Assigning a result; updating the instance list according to the paas instance allocation result;

Allocating a connection relationship between the VNFC instance corresponding to the VNFC instance assignment result and the paas instance assignment result corresponding to the paas instance;

Updating the connection relationship table according to the allocated connection relationship, and updating the connection point configuration information of the VNF according to the updated connection relationship table.

A transmitter 1204 is configured to transmit a signal. The transmitter 1204 can function as a separate chip, as well as a transmit circuit within the processor 1201 or as an output interface.

The receiver 1203, the transmitter 1204, the memory 1202, and the processor 1201 communicate with each other through an internal connection path, for example, via a bus.

In a possible implementation manner, the instance list includes at least one of a service type identifier set, a paas instance identifier set, and a network address set, where the service type identifier set includes n service type identifiers, and the paas instance The identifier set includes n paas instance identifier sub-sets, the network address set includes n network address sub-sets, the service type identifier in the service type identifier, the paas instance identifier sub-collection in the paas instance identifier set, and The network address subsets in the network address set are in one-to-one correspondence, and n is an integer greater than 0.

In a possible implementation, the connection relationship table includes at least one of a VNF identifier, a VNFC identifier, a paas instance identifier, and a VL instance identifier.

For the specific process of updating the implementation list and the connection relationship table in this embodiment, reference may be made to FIG. 2, and details are not described herein again.

In one possible design, the creation device 12 can be a chip, for example, can be a processor chip in a computing device for implementing related functions of the processor in the computing device. The chip can be a field programmable gate array for implementing related functions, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, and a programmable controller or other integrated chip. In the chip, optionally, one or more memories may be included for storing program code, and when the program code is executed, the processor implements corresponding functions.

These chips may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (sometimes referred to as code or programs). When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

The embodiment of the present invention and the method embodiment of FIG. 2 are based on the same concept, and the technical effects thereof are also the same. For the specific process, reference may be made to the description of the method embodiment of FIG. 2, and details are not described herein again.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state hard disk Sol Identification State Disk (SSD)) or the like.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Claims (28)

1. A method for managing a virtual network element, comprising:

   In the case that the basic service satisfies the instance update condition, the platform as a service paas management network element performs an instance update on the basic service;

   The paas management network element sends an instance update result of the basic service to the virtual network function management network element VNFM.
2. The method of claim 1, wherein the instance update result comprises at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the base service.
3. The method according to claim 1 or 2, wherein, before the basic service satisfies the instance update condition, the paas management network element further includes:

   The paas management network element detects an average load of all paas instances associated with the basic service;

   The paas management network element determines that the average load is greater than a first load threshold; or

   The paas management network element determines that the average load is less than a second load threshold.
4. The method of claim 3 wherein the service type identification is defined using a first manner, and all paas instances associated with the basic service have the same service type identification.
5. The method according to claim 1 or 2, wherein, before the basic service satisfies the instance update condition, the paas management network element further includes:

   The paas management network element detects a load of at least one paas instance in all paas instances associated with the basic service;

   The paas management network element determines that the load of each paas instance in the at least one paas instance is greater than a first load threshold; or

   The paas management network element determines that the load of each paas instance in the at least one paas instance is less than a second load threshold.
6. The method according to claim 5, wherein the service type identifier is defined in a second manner, and all paas instances associated with the base service have different service type identifiers, and when the update type of the paas instance is terminated, paas The service type identifier of the instance is the same as the identity of the paas instance.
7. A method for maintaining a virtual network element, comprising:

   The virtual network function management network element VNFM receives an instance update result about the basic service from the platform as a service paas management network element;

   The VNFM updates connection point configuration information of all virtual network functions VNF associated with the base service according to the instance update result.
8. The method of claim 7, wherein the VNFM updates connection point configuration information of all VNFs associated with the basic service according to the instance update result, including:

   The VNFM updates the instance list according to the instance update result;

   The VNFM queries all VNFs associated with the basic service according to a connection relationship table, and VNFC instances associated with all the VNFs;

   The VNFM re-allocates the connection relationship between the associated paas instance and the VNFC instance associated with all the VNFs after the basic service completes the instance update;

   The VNFM updates the connection relationship table according to the reassigned connection relationship, and updates the connection point configuration information of all the VNFs according to the updated connection relationship table.
9. The method according to claim 8, wherein the instance update result comprises at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the base service.
10. The method of claim 8 wherein the service type identifier is defined using a first manner, and all paas instances associated with the base service have the same service type identifier; or

    The service type identifier is defined in the second mode, and all the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier of the paas instance.
11. The method according to any one of claims 8 to 10, wherein the instance list comprises at least one of a service type identification set, a paas instance identification set, and a network address set, the service type identification set comprising n a service type identifier, the paas instance identifier set includes n paas instance identifier sub-sets, the network address set includes n network address subsets, the service type identifier in the service type identifier set, and the paas instance identifier The paas instance identifier sub-collection in the set corresponds to the network address sub-set in the network address set, and n is an integer greater than 0.
12. The method of claim 11, wherein the updating, by the VNFM, the list of instances according to the instance update result comprises:

    In a case that the update type of the updated paas instance is created and the service type identifier is defined by using the first manner, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance;

    If the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection associated with the updated paas instance's update type, and in the update with the Adding the network address of the updated paas instance to the network address sub-collection associated with the paas instance; or

    If the service type identifier of the updated paas instance is not retrieved, adding the service type identifier of the updated paas instance to the service type identifier set, and being associated with the service type identifier of the updated paas instance The paas instance identifies the identifier of the updated paas instance in the sub-collection, and adds the network address of the updated paas instance in the network address sub-collection associated with the service type identifier of the updated paas instance.
13. The method of claim 11, wherein the updating, by the VNFM, the list of instances according to the instance update result comprises:

    If the update type of the updated paas instance is termination and the service type identifier is defined by using the first manner, searching is performed in the service type identifier set according to the service type identifier of the updated paas instance;

    If the service type identifier of the paas instance is retrieved, the identifier of the updated paas instance is deleted in the basic service identifier subset associated with the service type identifier of the updated paas instance, and in the updated paas The service type of the instance identifies the network address of the updated paas instance in the associated network address sub-collection.
14. The method of claim 11, wherein the updating, by the VNFM, the list of instances according to the instance update result comprises:

    In the case that the update type of the updated paas instance is created and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

    If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the updated paas instance;

    If the paas instance identifier that is the same as the service type identifier of the updated paas instance is retrieved, the identifier of the updated paas instance is added to the paas instance identifier sub-collection with the paas instance identifier, and the paas Adding, by the instance identifier, the network address of the updated paas instance in the associated network address sub-collection; or

    If the paas instance identifier that is the same as the service type identifier of the updated paas instance is not retrieved, the service type identifier of the updated paas instance is added to the service type identifier set, and the paas instance is updated with the The service type identifier identifies the associated paas instance identifier sub-collection, the identifier of the updated paas instance is added, and the updated paas instance is added to the network address sub-collection associated with the service type identifier of the updated paas instance. website address.
15. The method of claim 11, wherein the updating, by the VNFM, the list of instances according to the instance update result comprises:

    In the case that the update type of the updated paas instance is terminated and the service type identifier is defined using the second mode, the search is performed in the service type identifier set according to the service type identifier of the updated paas instance shown;

    If the service type identifier of the updated paas instance is not retrieved, continue to search in the paas instance identifier set according to the service type identifier of the update paas instance;

    If the paas instance identifier that is the same as the updated paas instance is retrieved, the identifier of the updated paas instance is terminated in the paas instance identifier sub-collection corresponding to the paas instance identifier in the instance list, and Terminating the network address of the updated paas instance in the network address sub-collection associated with the paas instance identifier in the instance list.
16. The method according to any one of claims 8-15, wherein the connection relationship table comprises at least one of a VNF identifier, a virtual network function component VNFC identifier, a paas instance identifier, and a virtual link VL instance identifier.
17. The method of claim 16, wherein the re-allocating the connection relationship between the associated paas instance and the VNFC instance associated with the at least one VNF is:

    Reconnecting the connection relationship between the associated paas instance and the at least one VNFC instance after the instance update is performed in a random manner; wherein each paas instance is connected to at least one VNFC instance.
18. A method for controlling a virtual network element, comprising:

    The virtual network function management network element VNFM obtains an instance update result of the VNF, where the virtual network function VNF satisfies the instance update condition;

    Updating the connection point configuration information of the VNF according to the instance update result of the VNF.
19. The method of claim 18, wherein the updating the connection point configuration information of the VNF according to the instance update result of the VNF comprises:

    Querying all basic services associated with the VNF according to the connection relationship table, and querying a paas instance associated with all the basic services;

    Redistributing the connection relationship between the VNF and the queried instance of the queried instance;

    Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of the VNF according to the updated connection relationship table.
20. The method of claim 19, wherein the instance update result comprises at least one of an identifier of the VNF, an identifier of a VNFC instance associated with the VNF, and a VL instance identifier.
21. The method according to claim 19, wherein the connection relationship table comprises at least one of a VNF identifier, a virtual network function component VNFC identifier, a paas instance identifier, and a virtual link VL instance identifier.
22. A management device for a virtual network element, comprising:

    a processing unit, configured to perform an instance update on the basic service if the basic service satisfies an instance update condition;

    And a sending unit, configured to send an instance update result of the basic service to the virtual network function management network element VNFM.
23. The apparatus according to claim 22, wherein the instance update result comprises at least one of an identifier of an updated paas instance, a service type identifier, an update type, and a network address in the base service.
24. The apparatus according to claim 23, wherein the service type identifier is defined in a first manner, and all paas instances associated with the base service have the same service type identifier; or

    The service type identifier is defined in the second mode, and all the paas instances associated with the basic service have different service type identifiers. When the update type of the paas instance is terminated, the service type identifier of the paas instance is the same as the identifier of the paas instance.
25. A maintenance device for a virtual network element, comprising:

    a receiving unit, configured to receive an instance update result about the basic service from the platform as a service paas management network element;

    And a processing unit, configured to update connection point configuration information of all virtual network functions VNF associated with the basic service according to the instance update result.
26. The device according to claim 25, wherein the processing unit is configured to update connection point configuration information of all VNFs associated with the basic service according to the instance update result, specifically:

    Updating the instance list according to the instance update result;

    Querying, according to the connection relationship table, all VNFs associated with the basic service, and VNFC instances associated with all the VNFs;

    Reassigning a connection relationship between the associated paas instance and the virtual network function component VNFC instance associated with all the VNFs after the instance update is completed;

    Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of all the VNFs according to the updated connection relationship table.
27. A control device for a virtual network element, comprising:

    An obtaining unit, configured to acquire an instance update result of the VNF if the virtual network function VNF satisfies an instance update condition;

    And a processing unit, configured to update the connection point configuration information of the VNF according to the instance update result of the VNF.
28. The device according to claim 27, wherein the processing unit is configured to update the connection point configuration information of the VNF according to the instance update result of the VNF, specifically:

    Querying all basic services associated with the VNF according to the connection relationship table, and querying a paas instance associated with all the basic services;

    Redistributing the connection relationship between the VNF and the queried instance of the queried instance;

    Updating the connection relationship table according to the reassigned connection relationship, and updating the connection point configuration information of the VNF according to the updated connection relationship table.

Images