CN113726541B

CN113726541B - Method and device for configuring network element, electronic equipment and storage medium

Info

Publication number: CN113726541B
Application number: CN202010450995.7A
Authority: CN
Inventors: 李家乐
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Suzhou Software Technology Co Ltd
Priority date: 2020-05-25
Filing date: 2020-05-25
Publication date: 2023-11-07
Anticipated expiration: 2040-05-25
Also published as: CN113726541A

Abstract

The invention discloses a method, a device, electronic equipment and a computer storage medium for configuring network elements, wherein the method comprises the following steps: acquiring configuration data of a Virtual Network Function (VNF) network element; receiving life cycle operation of the VNF network element; determining that VNF network element information corresponding to the lifecycle operation is matched with the first information, and configuring the VNF network element according to the configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data; in this way, the configuration data and the virtual network function descriptor VNFD are separated, the configuration data is optionally adjusted according to the requirement, and the VNF network element is not limited by the configuration data defined in the VNFD when the life cycle operation is performed, and the automatic configuration of the network element can be realized without exposing an interface, so that the flexibility and the universality of the network element configuration are effectively improved.

Description

Method and device for configuring network element, electronic equipment and storage medium

Technical Field

The present invention relates to communication network technologies, and in particular, to a method, an apparatus, an electronic device, and a computer storage medium for configuring a network element.

Background

The european telecommunications standards institute (European Telecom Standards Institute, ETSI) proposes network function virtualization (Network Function virtualization, NFV) technology aimed at implementing in software network functions that can run on industry standard servers and that can be dynamically deployed at different locations in the network as required without the need to reinstall new dedicated hardware devices. In NFV technology, VNF is maintained and managed by a network element management system (Element Management System, EMS). NFV is a virtualization technology or concept that can solve the problem of deploying network functions on general-purpose hardware; while a VNF refers to a specific virtual network function, the VNF is a piece of software that is capable of providing a certain network service, and the VNF may be deployed in a virtual machine, a container, or a physical machine using the infrastructure provided by the network function virtualization infrastructure (Network Functions Virtualization Infrastructure, NFVI).

The operator establishes a network function virtualization standard working group (Industry Specification group, NFV ISG) in ETSI, and the research target is mainly to hope to load various network software functions by widely adopting standardized information technology (Information Technology, IT) virtualization technology and adopting industry standard large-capacity servers, storage and switches, so as to realize flexible loading of the software, realize flexible deployment configuration at various positions of a data center, network nodes, a user side and the like, thereby accelerating the speed of network deployment and adjustment, reducing the complexity of service deployment, improving the unification, generalization, suitability and the like of network equipment, and finally reducing the fixed asset investment and the operation cost of the network. According to ETSI NFV ISG specification requirements, network function virtualization management and orchestration (NFV Management and Orchestration, NFV-MANO) covers orchestration and lifecycle management of physical/software resources supporting infrastructure virtualization, and lifecycle management of VNFs; NFV-MANO focuses on all specific virtual management tasks in the NFV architecture.

In the related art, according to ETSI specifications, configuration information of a virtual network function (Virtualized Network Function, VNF) network element needs to be defined in a virtual network function descriptor (Virtualised Network Function Descriptor, VNFD), then a virtual network function manager (VNF manager, VNFM) configures the VNF network element through an interface exposed by the VNF, in the related art, when the VNF network element is configured, configuration information of the VNF network element needs to be defined in the VNFD, and the configuration information includes some variable parameters; table 1 is a definition manner of defining VNF network element configuration information in VNFD in the related art, as shown in table 1, the definition manner includes: attributes, qualifiers, cardinalities, content, descriptions; here, the description referred to in the table may be a description about VNF configuration attributes, for example: network element capacity reduction, network element self-healing, and the like.

TABLE 1

If the VNF network element wants to operate normally during the life cycle, it needs to be configured by VNFM. In the ETSI specification, it is specified that VNF network elements have to expose interfaces as shown in table 2; table 2 is a VNF network element interface table in which the VNFM configures the VNF network element in the related art, that is, only after the operation is successful for the life cycle of the VNF network element, the VNFM invokes the VNF network element interface to configure the VNF network element, for example, after the instantiation of the VNF network element is successful and the creation of the virtual machine resource is completed, the VNFM configures the VNF network element through the interface exposed by the VNF network element; it can be seen that the network element configuration method is inflexible and has low versatility.

Operation of	Description of the invention	Annotating
			Obtaining a configuration object	Retrieving configuration data for a particular configuration object
Creating configuration objects	Creating a configuration object
			Deleting configuration objects	Deleting a configuration object
Setting configuration object attributes	Modifying a configuration object
			Notifying configuration changes	This operation allows providing notification about configuration changes of the configuration object

TABLE 2

Disclosure of Invention

The invention provides a network element configuration method, a device, electronic equipment and a computer storage medium, wherein configuration data are separated from VNFD (virtual network function), the configuration data are randomly adjusted according to requirements, when the life cycle operation is carried out on the VNF network element, the VNF network element is not limited by the configuration data defined in the VNFD, the automatic configuration of the network element can be realized without exposing an interface, and the flexibility and the universality of the network element configuration are effectively improved.

In order to achieve the above purpose, the technical scheme of the invention is realized as follows:

in a first aspect, the present invention provides a method for configuring a network element, which is applied to VNFM, and the method includes:

acquiring configuration data of a VNF network element;

receiving life cycle operation of the VNF network element;

determining that VNF network element information corresponding to the lifecycle operation is matched with the first information, and configuring the VNF network element according to the configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data.

Optionally, the acquiring configuration data of the VNF network element includes:

receiving configuration data sent by a network function virtualization orchestrator (Network Function Virtualization Orchestrator, NFVO); the NFVO is configured to update the configuration data according to an operation instruction of a user on the configuration data.

Optionally, the method further comprises:

and when the VNF network element information corresponding to the life cycle operation is matched with the first information, storing the configuration data.

Optionally, the storing the configuration data includes: storing the configuration data in a virtual infrastructure manager (Virtualized Infrastructure Managers, VIM);

the configuring the VNF network element according to the configuration data includes: and configuring the VNF network element according to the configuration data and a Virtual Machine (VM) stored in the VIM.

Optionally, the VNF network element information includes at least one of: VNF packet identity, VNF version information, VNF instance information.

Optionally, the lifecycle operation includes at least one of: network element instantiation, network element expansion and contraction capacity, network element inquiry, network element termination and network element self-healing.

In a second aspect, the present invention provides an apparatus configured by a network element, applied to VNFM, where the apparatus includes:

an acquiring module, configured to acquire configuration data of a VNF network element;

a receiving module, configured to receive a life cycle operation on the VNF network element;

a configuration module, configured to determine that VNF network element information corresponding to the life cycle operation matches the first information, and configure the VNF network element according to the configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data.

Optionally, the obtaining module is configured to obtain configuration data of the VNF network element, and includes:

receiving configuration data sent by the NFVO; the NFVO is configured to update the configuration data according to an operation instruction of a user on the configuration data.

Optionally, the device further includes a storage module, where the storage module is configured to:

Optionally, the configuration module is configured to: storing the configuration data into a VIM;

the method is particularly used for: and configuring the VNF network element according to the configuration data stored in the VIM and the VM.

In a third aspect, the present invention provides an electronic device, the device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method for configuring a network element provided by one or more of the foregoing technical solutions when the program is executed by the processor.

In a fourth aspect, there is provided a computer storage medium storing a computer program; the computer program, when executed, is capable of implementing the method for configuring a network element provided by one or more of the foregoing technical solutions.

The invention provides a method, a device, electronic equipment and a computer storage medium for configuring network elements, wherein the method comprises the following steps: acquiring configuration data of a VNF network element; receiving life cycle operation of the VNF network element; determining that VNF network element information corresponding to the lifecycle operation is matched with the first information, and configuring the VNF network element according to the configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data; in this way, the configuration data and the VNFD are separated, the configuration data is arbitrarily adjusted according to the requirement, the VNF network element is not limited to the configuration data defined in the VNFD when the life cycle operation is performed, and the automatic configuration of the network element can be realized without exposing an interface, so that the flexibility and the universality of the network element configuration are effectively improved.

Drawings

FIG. 1 is a diagram of an NFV-MANO architecture in an ETSI of the related art;

fig. 2 is a flowchart of a method for VNF instantiation in ETSI according to the related art;

fig. 3 is a flow chart of a method of network element configuration in the present invention;

fig. 4 is a flowchart of a network element configuration in the present invention;

fig. 5 is a second flowchart of network element configuration in the present invention;

fig. 6 is a schematic diagram of the composition structure of the device configured by the network element of the present invention;

fig. 7 is a schematic structural diagram of an electronic device provided by the present invention.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

FIG. 1 is a diagram of an NFV-MANO architecture in an ETSI of the related art, and as shown in FIG. 1, the NFV-MANO is mainly composed of three modules: NFVO, VNFM, and VIM.

In the NFV-MANO architecture diagram, NFVO is responsible for management of network traffic by connecting with devices storing network traffic directories (NS catalyst), virtual network function directories (VNF catalyst), network function virtual Instances (NFV Instances), and network function virtualization infrastructure (NFVI Resources); the VNFM calls the data request of the NFVO, and the VNFM is connected with the VIM to execute the resource allocation established by the VM.

The system in fig. 1 further includes an operation support subsystem (Operation Station Subsystem, OSS) and a base station subsystem (Base Station Subsystem, BSS), where the OSS/BSS system supports interaction with NFVO in a virtualized environment, so as to complete maintenance and management functions; and may invoke the functionality of network element management (Element management, EM), which may provide operation and maintenance functions for one or more VNFs, which NFVI provides virtualized resources to the VNFs.

Here, NFVO is mainly responsible for orchestration and management of NFV infrastructure, software resources, and underlying NFVI-level network services. The VNFM manages the life cycle operations of the VNF, where the life cycle operations may include instantiation, update, query, scaling, termination, self-healing, and so on. VIM is a virtualized infrastructure management system that provides a virtualized resource pool to an upper layer.

Fig. 2 is a flowchart of a method for VNF instantiation in ETSI according to the related art, wherein step 10 represents main steps for configuration of the VNF; as shown in fig. 2, the method comprises the steps of:

step 1, NFVO receives the request.

In a specific example, NFVO is instantiated using operations of the VNF lifecycle management interface; the NFVO receives a trigger request to instantiate a VNF in the infrastructure; the trigger request may be a trigger request from a manual trigger or an automatic service creation of the base station subsystem BSS or OSS.

Step 2, the VNFM receives the request for sending the NFVO.

In a specific example, the NFVO uses an instantiation VNF operation of the VNF lifecycle management interface, the NFVO requests the VNFM to instantiate a new VNF in the infrastructure, and the VNFM receives a trigger request sent by the NFVO; the trigger request may include VNF instantiation information.

And 3, VNFM granting life cycle operation.

In a specific example, the VNFM requests that the vnvo instantiate the VNF using a VNF lifecycle operation grant interface by invoking the interface to perform the grant lifecycle operation according to information in the VNFD, e.g., information of CPU, memory, IP, etc.

And 4, checking the resource availability by the NFVO.

In a specific example, the NFVO checks the resource request against its capacity database for free resource availability based on the information received in the trigger request.

And 5-6, the NFVO creates resource reservation, and the VIM sends a reservation result.

In a specific example, the NFVO may optionally make a resource reservation for the requested resource by using a create resource reservation operation on the virtualized resource management interface, the NFVO sends a resource reservation request to the VIM, and when the VIM receives the resource reservation request, the VIM sends a resource reservation result to the NFVO.

And 7, responding the VNFM request by the NFVO.

In a specific example, the NFVO responds to the VNFM request by sending a VIM identifier and other needed reservation information to inform the VNFM of the location where the VNF is instantiated as a response to step 4.

And 8, VNFM allocates resources.

In a specific example, the NFVM sends a request to the VIM to create and launch the VM, and performs the operations of allocating resources to send the VIM identifier and VM parameters by invoking the virtualized resource management interface.

And 9, VIM confirmation operation.

In a specific example, the VIM creates and initiates a VM, and then confirms successful operation of the VNFM.

Step 10, VNFM configures VNF data.

In a specific example, the VNFM uses an add/create/set configuration object operation of the VNF configuration interface to configure VNF data specific to VNF instantiation.

Step 11, the VNFM notifies to create a VNF.

In a specific example, the VNFM uses a VNF lifecycle change notification interface to notify the EM that a new VNF has been created.

Step 12, EM and VNFM add VNF as managed device.

In a specific example, EM and VNFM add a new VNF as the managed device.

Step 13, EM configures VNF.

In a specific example, the EM configures the VNF using VNF data specific to VNF instantiation.

Step 14, the VNFM informs the VNF of the instantiation.

In a specific example, the VNFM reports a successful VNF instantiation to the NFVO as a response to the request issued in step 3; the NFVO determines at this point that a new VNF is instantiated in the infrastructure.

Step 15, NFVO maps VNF.

In a specific example, NFVO maps VNFs to the appropriate VIM and resource pool.

In summary, the method related to VNF network element configuration in the related art has the following drawbacks:

1) In the ETSI specification, it is specified that the VNF network element must externally expose the configuration interface, however, the definition of the interface in ETSI is not clear, and consistency cannot be achieved among various manufacturers;

2) When the existing VNF network element is modified, parameters of the configuration interface are modified according to the ETSI specification, so that the modification amount is large, and the modification cost is high;

3) The manner of defining VNF network element configuration information in VNFD is inflexible, and definable configuration information, whether format, content, etc. are limited; for example, when the configuration file is expanded, the configuration file cannot be expanded.

Based on the above technical problems, the present invention provides a method for configuring a network element, and the technical solution of the present invention will be clearly and completely described below with reference to the drawings in the present invention.

Fig. 3 is a flowchart of a method for configuring a network element according to the present invention, where the method is applied to VNFM, as shown in fig. 3, and the method includes:

s301: acquiring configuration data of a VNF network element;

it should be noted that the VNF network element represents a virtualized network element under VNFM management.

Here, the configuration data may be configuration data corresponding to one VNF network element, or may be configuration data corresponding to a plurality of VNF network elements, where the number of VNF network elements is set according to an actual scenario, and the embodiment of the present invention is not limited.

The content and format of the configuration data in the embodiment of the present invention are not limited to the configuration file defined in the VNFD, where the content of the configuration data is arbitrary, for example, may be a program, may be a script, may also be a simple configuration file, and the format of the configuration data may be embodied in the form of a compressed packet, or may be embodied in other forms, that is, the content of the configuration data and the format of the configuration data may be set according to an actual scenario.

In an embodiment, the VNFM obtains configuration data of the VNF network element, which may include: receiving configuration data sent by the NFVO; the NFVO is configured to update the configuration data according to an operation instruction of the user on the configuration data.

For example, when the VNF network element needs to be configured, the configuration data is directly uploaded to the NFVO, where the NFVO may support operations of a user on the configuration data, for example, create, modify, or delete the configuration data, that is, the configuration data may be changed correspondingly according to some data operations of the user, and further updating the configuration data may be achieved through these operations.

In one embodiment, the VNFM receives configuration data sent by the NFVO. Further, when the NFVO receives an operation request of a user for the configuration data, the NFVO performs corresponding operation on the configuration data, and sends the configuration data after the operation to the VNFM; when the NFVO does not receive the operation request of the user for the configuration data, the original configuration data in the NFVO is sent to the VNFM.

S302: receiving life cycle operation of the VNF network element;

in the embodiment of the invention, the VNFM receives the life cycle operation of the VNF network element, and manages the VNF network element according to the life cycle operation of the VNF network element.

The VNF network element may be a VNF network element managed by one VNFM or a VNF network element managed by a plurality of VNFMs, where the number of VNFMs is set according to an actual scenario, and embodiments of the present invention are not limited.

For example, the lifecycle operations corresponding to the VNF network elements may include at least one of: network element instantiation, network element expansion and contraction capacity, network element inquiry, network element termination and network element self-healing.

Wherein network element instantiation means that in the virtualized infrastructure, the network element sets up, turns on, activates, creates or performs its own virtualized network functions in some way available through some communication network element or function. The expansion and contraction capacity of the network element is respectively divided into two modes: the method comprises the steps of transversely expanding and shrinking, wherein the transverse expansion and shrinking are realized through outward and inward operations, the longitudinal expansion and shrinking are realized through upward and downward operations, the transverse expansion and shrinking are realized through expanding and shrinking of network elements in a mode of adding or reducing network element virtual machines, and the longitudinal expansion and shrinking are realized through expanding and shrinking of network elements in a mode of adding or reducing virtualized hardware configuration. The network element inquiry indicates that the corresponding network element is inquired through the attribute information of the network element so as to carry out related service operation on the network element; the network element termination represents the attribute information of the termination network element; the attribute information of the terminated network element comprises the name of the terminated network element, the network element type, the network element version and the network element instance number. The network element self-healing means that when the network element fails, the network element can automatically recover from the failure in an extremely short time without human intervention.

In one embodiment, before configuring a VNF network element, the VNFM receives a life cycle operation for the VNF network element, and performs a corresponding life cycle operation for the VNF network element through the VNFM; for example, before configuring the VNF network element, network element instantiation is performed through the VNFM; before configuring the VNF network element, performing network element expansion and contraction through the VNFM; before configuring the VNF network element, carrying out network element inquiry through the VNFM; before the configuration of the VNF network element, the network element self-healing is performed through the VNFM.

In the embodiment of the invention, after the life cycle operation of the VNF network element is completed, the VNF network element under the management of the VNFM is configured, and then the normal operation of the VNF network element is realized.

S303: determining that the VNF network element information corresponding to the life cycle operation is matched with the first information, and configuring the VNF network element according to configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data.

Here, the first information represents VNF network element information associated with the configuration data; wherein the VNF network element information includes at least one of: VNF packet identity, VNF version information, VNF instance information.

In the embodiment of the present invention, when the configuration data is uploaded to the NFVO, VNF network element information associated with the configuration data may be specified; here, different VNF network element information may be associated with different configuration data, or may be associated with the same configuration data, or may be set according to an actual scenario, which is not limited by the embodiment of the present invention.

In the embodiment of the invention, when the life cycle operation is performed on the VNF network element, the VNF network element information corresponding to the life cycle operation is matched with the VNF network element information associated with the configuration data, that is, the VNF packet identification code, the VNF version information and the VNF instance information included in the VNF network element information are matched, if the matching is successful, the configuration data associated with the VNF network element information is stored, and if the matching is failed, the life cycle operation information of the network element is different from the VNF network element information, and further, the configuration data associated with the life cycle operation of the network element does not exist.

In one embodiment, the configuration data may be stored when VNF network element information corresponding to the lifecycle operation matches the first information. Illustratively, the configuration data may be stored into the VIM; configuring the VNF network element according to the configuration data, including: and configuring the VNF network element according to the configuration data stored in the VIM and the virtual machine VM.

For example, when the life cycle operation of the network element is executed as the network element instantiation, the VNF packet identifier, the VNF version information and the VNF instance information during the network element instantiation are matched, if the matching is successful, the configuration data associated with the VNF network element information during the network element instantiation is stored, the configuration data is stored into the VIM, and then the VM is mounted through the VIM, and further, the VNF network element is configured according to the configuration data stored in the VIM and the VM; otherwise, if the matching fails, the VNF network element uses the original configuration data.

In the embodiment of the invention, the VIM stores the configuration data associated with the VNF network element information, when the VNF network element is started, the original configuration data of the VNF network element is replaced by the associated configuration data, when the VNF network element is not started, the original configuration data of the VNF network element is not replaced, and therefore, when the VNF network element is started, the automatic configuration of the network element can be realized.

The invention provides a method, a device, electronic equipment and a computer storage medium for configuring network elements, wherein the method comprises the following steps: acquiring configuration data of a VNF network element; receiving life cycle operation of the VNF network element; determining that the VNF network element information corresponding to the life cycle operation is matched with the first information, and configuring the VNF network element according to configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data; in this way, the configuration data is separated from the VNFD, the configuration data is arbitrarily adjusted according to the requirement, and the VNF network element is not limited by the configuration data defined in the VNFD when the life cycle operation is performed, and the automatic configuration of the network element can be realized without exposing an interface, so that the flexibility and the universality of the network element configuration are effectively improved; further, when the VNF network element information corresponding to the life cycle operation is determined to be matched with the configuration data, the configuration data is stored in the VIM, and when the VNF network element is started, the original configuration data of the VNF network element is replaced according to the configuration data of the VIM, so that the automatic configuration of the network element is realized.

In order to further embody the objects of the present invention, further examples will be given on the basis of the above-described embodiments of the present invention.

Fig. 4 is a first flowchart of network element configuration in the present invention, fig. 5 is a second flowchart of network element configuration in the present invention, and referring to fig. 4 and fig. 5, the network element configuration process may include:

the user uploads the configuration data which needs to be configured to the network element to the NFVO, the NFVO sends the received configuration data to the VNFM, after the life cycle operation of the network element by the VNFM is completed, the configuration data is uploaded to the VIM for storage, then the configuration data is mounted on the VM through the VIM, and when the VM reads the configuration data, the configuration data is analyzed to be used for configuring the VNF network element, so that the automatic configuration of the VNF network element is realized.

In one embodiment, the configuration data of the network element is separated from the VNFD, where the configuration data may be a program, may be a script, or may be a simple configuration file, where the configuration data is stored in a compressed package, and when a user needs to configure the network element, the configuration data is directly uploaded to the NFVO, and if the user needs to create, modify, or delete the network element, the configuration data may be correspondingly updated, and sent to the VNFM, and when the VNFM performs life cycle operations such as instantiation, capacity expansion, self-healing, and upgrading on the network element, the configuration data is directly uploaded to the VIM, and is mounted on the VM through the VIM, and when the network element is started, the original configuration data of the network element is replaced by the configuration data, thereby implementing automatic configuration of the network element.

On the basis of the method for configuring the network element provided by the foregoing embodiment, the embodiment of the present invention provides a device for configuring the network element.

Fig. 6 is a schematic structural diagram of a device configured by a network element according to the present invention, which is applied to VNFM, as shown in fig. 6, the device includes: an acquisition module 601, a receiving module 602, and a configuration module 603, wherein:

an obtaining module 601, configured to obtain configuration data of a VNF network element;

a receiving module 602, configured to receive a life cycle operation on a VNF network element;

a configuration module 603, configured to determine that VNF network element information corresponding to the life cycle operation matches the first information, and configure the VNF network element according to configuration data when the VNF network element is started; wherein the first information represents VNF network element information associated with the configuration data.

In an embodiment, the obtaining module 601 is configured to obtain configuration data of a VNF network element, and includes:

receiving configuration data sent by the NFVO; the NFVO is configured to update the configuration data according to an operation instruction of the user on the configuration data.

In one embodiment, the apparatus further comprises a storage module 604, where the storage module 604 is configured to: and when the VNF network element information corresponding to the life cycle operation is matched with the first information, storing the configuration data.

In one embodiment, the configuration module 603 is configured to:

storing the configuration data in a virtual infrastructure manager VIM; the method is particularly used for: and configuring the VNF network element according to the configuration data stored in the VIM and the VM.

In one embodiment, the VNF network element information includes at least one of: VNF packet identity, VNF version information, VNF instance information.

In one embodiment, the lifecycle operation includes at least one of: network element instantiation, network element expansion and contraction capacity, network element inquiry, network element termination and network element self-healing.

In practical applications, the acquiring module 601, the receiving module 602, the configuring module 603 and the storing module 604 may be implemented by a processor located in an electronic device, where the processor may be at least one of an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD), a programmable logic device (Programmable Logic Device, PLD), a field programmable gate array (Field Programmable Gate Array, FPGA), a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller and a microprocessor.

In addition, each functional module in the present embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional modules.

The integrated units, if implemented in the form of software functional modules, may be stored in a computer-readable storage medium, if not sold or used as separate products, and based on such understanding, the technical solution of the present embodiment may be embodied essentially or partly in the form of a software product, which is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or processor (processor) to perform all or part of the steps of the method of the present embodiment. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Specifically, the computer program instructions corresponding to the method for configuring a network element in this embodiment may be stored on a storage medium such as an optical disc, a hard disc, or a usb disc, and when the computer program instructions corresponding to the method for configuring a network element in the storage medium are read or executed by an electronic device, the method for configuring a network element in any of the foregoing embodiments is implemented.

Based on the same technical concept as the foregoing embodiments, referring to fig. 7, an electronic device 700 provided by the present invention may include: a memory 701 and a processor 702; wherein,

a memory 701 for storing a computer program and data;

a processor 702 for executing computer programs stored in the memory to implement the method of configuring any one of the network elements of the foregoing embodiments.

In practical applications, the memory 701 may be a volatile memory (RAM); or a non-volatile memory (non-volatile memory), such as ROM, flash memory (flash memory), hard Disk (HDD), or Solid State Drive (SSD); or a combination of the above types of memory and provides instructions and data to the processor 702.

The processor 702 may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, a controller, a microcontroller, and a microprocessor. It will be appreciated that, for different augmented reality cloud platforms, the electronic device for implementing the above-described processor functions may also be other, and embodiments of the present invention are not specifically limited.

In some embodiments, a function or a module included in an apparatus provided by the embodiments of the present invention may be used to perform a method described in the foregoing method embodiments, and a specific implementation of the function or module may refer to the description of the foregoing method embodiments, which is not repeated herein for brevity

The foregoing description of various embodiments is intended to emphasize the differences between the various embodiments, and the same or similar features thereof may be referred to each other for brevity and will not be repeated herein

The methods disclosed in the method embodiments provided by the invention can be arbitrarily combined under the condition of no conflict to obtain a new method embodiment.

The features disclosed in the embodiments of the products provided by the invention can be combined arbitrarily under the condition of no conflict to obtain new embodiments of the products.

The features disclosed in the embodiments of the method or the device provided by the invention can be arbitrarily combined under the condition of no conflict to obtain a new embodiment of the method or the device.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method of network element configuration, applied in a virtualized network function manager VNFM, the method comprising:

acquiring configuration data of a Virtual Network Function (VNF) network element;

receiving life cycle operation of the VNF network element;

2. The method according to claim 1, wherein the obtaining configuration data of the VNF network element for a virtual network function comprises:

receiving configuration data sent by a Network Function Virtualization Orchestrator (NFVO); the NFVO is configured to update the configuration data according to an operation instruction of a user on the configuration data.

3. The method according to claim 1, wherein the method further comprises:

4. A method according to claim 3, wherein said storing said configuration data comprises: storing the configuration data in a virtual infrastructure manager VIM;

the configuring the VNF network element according to the configuration data includes: and configuring the VNF network element according to the configuration data stored in the VIM and the virtual machine VM.

5. The method according to any of claims 1 to 4, wherein the VNF network element information comprises at least one of: VNF packet identity, VNF version information, VNF instance information.

6. The method of any one of claims 1 to 4, wherein the lifecycle operation comprises at least one of: network element instantiation, network element expansion and contraction capacity, network element inquiry, network element termination and network element self-healing.

7. An apparatus for configuring a network element, the apparatus being applied to a virtualized network function manager VNFM, the apparatus comprising:

an obtaining module, configured to obtain configuration data of a VNF network element of a virtual network function;

8. The apparatus of claim 7, wherein the means for obtaining configuration data of a virtual network function VNF network element comprises:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method according to any one of claims 1 to 6 when the program is executed.

10. A computer storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method according to any of claims 1 to 6.