CN112242918B - VNFD multi-version compatible processing method, device, equipment and storage medium - Google Patents

VNFD multi-version compatible processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN112242918B
CN112242918B CN201910656824.7A CN201910656824A CN112242918B CN 112242918 B CN112242918 B CN 112242918B CN 201910656824 A CN201910656824 A CN 201910656824A CN 112242918 B CN112242918 B CN 112242918B
Authority
CN
China
Prior art keywords
vnfd
version
target
plug
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910656824.7A
Other languages
Chinese (zh)
Other versions
CN112242918A (en
Inventor
傅锦华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201910656824.7A priority Critical patent/CN112242918B/en
Priority to PCT/CN2020/099292 priority patent/WO2021012905A1/en
Publication of CN112242918A publication Critical patent/CN112242918A/en
Application granted granted Critical
Publication of CN112242918B publication Critical patent/CN112242918B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

Embodiments of the present invention provide a VNFD multi-version compatibility processing method, apparatus, device, and storage medium, where when an incompatible VNFD version appears in a system, a target processing plugin corresponding to the current incompatible VNFD version of the system may be directly obtained, where the target processing plugin is used to perform parsing and conversion processing on a VNFD version package, and then the obtained target processing plugin and the target VNFD version are stored in the system in a correlated manner, so as to complete upgrading of the plugin, thereby implementing compatibility of the incompatible VNFD version before upgrading.

Description

VNFD multi-version compatible processing method, device, equipment and storage medium
Technical Field
The present invention relates to the field of communications, and in particular, to a VNFD (Virtual Network Function Descriptor) multi-version compatible processing method, apparatus, device, and storage medium.
Background
With the rapid development of technologies such as IT field Virtualization and cloud computing, NFV (Network Function Virtualization) becomes a mainstream technology for Network deployment in the telecommunication field, and under this technology, VNF (Virtualized Network Function) replaces proprietary Network element equipment in the traditional telecommunication Network, and can be flexibly deployed on a VIM (Virtual Infrastructure Manager) platform constructed based on other equipment such as a standard server, a storage and a switch, thereby greatly improving the elasticity of the Network.
According to ETSI (European Telecommunications Standards Institute) Specification requirements, VNFD is a configuration template specifically used to describe the Deployment and operation behaviors of VNF, and the configuration template is described by using a TOSCA (Topology and organization Specification for Cloud Applications) model, and includes information such as VDU (Virtualized Deployment unit) description, internal virtual link description, external connection point description, software image description, and Deployment flag description, which are used by NFVO (Network Functions Virtualization editor, network Function Virtualization) and VNFM (Virtualized Network Function Manager) in VNF lifecycle management.
In the related art, in the implementation of the NFVO system and the VNFM system, a special component is responsible for parsing a VNFD version package and converting a parsing result into a uniform data structure inside the system, in the evolution process of the ETSI specification, the VNFD has multiple versions, if the version of the VNFD changes, for example, the structural definition of a VDU of the VNFD changes, in order to be compatible with the VNFD of the new version, the related art needs to integrally upgrade the NFVO system and the VNFM system, so as to update a processing component in the VNFD of the NFVO system and the VNFM system, which performs parsing and other processing on the VNFD version package.
In addition, in the related art, when the NFVO system and the VNFM system of different vendors are docked, the VNFD supported by the two systems may also be in different versions, and in order to be compatible with the VNFD version provided by the docked vendor, the vendor needs to upgrade the NFVO system or the VNFM system so as to update the processing component in the VNFD in the NFVO and VNFM systems, which performs parsing and other processing on the VNFD version package.
Therefore, in the related art, when the incompatible VNFD version appears in the system, the system can only be upgraded integrally, and the system needs long time for upgrading, consumes more resources, and cannot well meet various application scenarios with requirements on timeliness.
Disclosure of Invention
The embodiment of the invention provides a VNFD multi-version compatibility processing method, a device, equipment and a storage medium, which solve the problems that in the related art, when incompatible VNFD versions occur in a system, the system can only be upgraded integrally, the time required by system upgrading is long, more resources are consumed, and various application scenes with requirements on timeliness cannot be met well.
To solve the foregoing technical problem, an embodiment of the present invention provides a VNFD multi-version compatible processing method, including:
acquiring a target processing plug-in corresponding to a target Virtualization Network Function Description (VNFD) version which is incompatible with the current system;
storing the acquired target processing plug-in and the target VNFD version in a system in an associated manner;
and when the VNFD version package is received, calling a processing plug-in corresponding to the VNFD version of the VNFD version package from the system to process the VNFD version package.
To solve the foregoing technical problem, an embodiment of the present invention further provides a VNFD multi-version compatible processing apparatus, including:
the plug-in management module is used for acquiring a target processing plug-in corresponding to a target Virtualized Network Function Description (VNFD) version which is not compatible with the system at present, and storing the acquired target processing plug-in and the target VNFD version in the system in a correlation manner;
and the processing control module is used for calling a processing plug-in corresponding to the VNFD version of the VNFD version package from the system to process the VNFD version package when the VNFD version package is received.
In order to solve the above technical problem, an embodiment of the present invention further provides a communication device, including a processor, a memory, and a communication bus;
the communication bus is used for connecting the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the VNFD multi-version compatible processing method as described above.
To solve the above technical problem, an embodiment of the present invention further provides a computer-readable storage medium storing one or more computer programs, which are executable by one or more processors to implement the steps of the VNFD multi-version compatible processing method as described above.
Advantageous effects
According to the VNFD multi-version compatible processing method, the device, the equipment and the storage medium provided by the embodiment of the invention, when the incompatible VNFD version appears in the system, the target processing plugin corresponding to the current incompatible VNFD version of the system can be directly obtained, the target processing plugin is used for analyzing and converting the VNFD version packet, and then the obtained target processing plugin and the target VNFD version are stored in the system in a correlation mode so as to complete the upgrading of the plugin, so that the incompatibility VNFD version before upgrading is compatible, and compared with the existing processing mode for directly upgrading the system of the NFVO system and/or the VNFM system, the upgrading flexibility can be improved, the time and consumed resources required by upgrading can be greatly reduced, and the upgrading efficiency and the resource utilization rate are improved; on this basis, when the VNFD version package is received, the processing plug-in corresponding to the VNFD version of the VNFD version package may be called from the system to process the VNFD version package.
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a schematic flow chart of a VNFD multi-version compatibility processing method according to a first embodiment of the present invention;
fig. 2 is a schematic structural diagram of a VNFD multi-version compatible processing apparatus according to a second embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a plug-in management module according to a second embodiment of the present invention;
fig. 4 is a schematic flow chart of VNFD multi-version compatibility processing according to a third embodiment of the present invention;
fig. 5 is a schematic diagram of a VNFD version compatibility processing procedure in the first application scenario of the third embodiment of the present invention;
fig. 6 is a schematic diagram of a VNFD version compatibility processing procedure in a second application scenario according to a third embodiment of the present invention;
fig. 7 is a schematic structural diagram of a communication device according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
The first embodiment is as follows:
the VNFD multi-version compatible processing method provided in this embodiment can flexibly set corresponding processing plug-ins for different VNFD versions, and when an incompatible target VNFD version occurs in a system, the processing plug-in corresponding to the currently incompatible target VNFD version of the system can be directly obtained to perform plug-in level upgrade, without upgrading the entire system, which not only can improve the flexibility of upgrade, but also can greatly reduce the time and resources consumed for upgrade, improve the upgrade efficiency and resource utilization rate, and minimize the impact brought in the upgrade process.
For convenience of understanding, the following description of the present embodiment is given by taking the VNFD multi-version compatible processing method shown in fig. 1 as an example, and includes:
s101: and acquiring a target processing plug-in corresponding to a target Virtualization Network Function Description (VNFD) version which is incompatible with the system at present.
It should be understood that the system in this embodiment may include, but is not limited to, at least one of an NFVO system and a VNFM system, and may be flexibly set according to an application scenario.
In this embodiment, corresponding processing plug-ins may be set in advance for different VNFD versions, and it should be understood by application that, in some examples, the processing plug-ins corresponding to different VNFD versions may be different, that is, may correspond to one another; in other examples, different VNFD versions may also be set to correspond to the same processing plugin, that is, one processing plugin may simultaneously be compatible with multiple VNFD versions.
The processing plug-in corresponding to the VNFD version in this embodiment refers to various plug-ins for processing the VNFD version package corresponding to the VNFD version, and may include, for example and without limitation, at least one of a VNFD parsing plug-in, an inter-VNFD version conversion plug-in, a VNFD system conversion plug-in, and a VIM resource conversion plug-in; in the process of upgrading the plug-in, which plug-ins in the plug-ins need to be acquired specifically for the current incompatible VNFD version can be flexibly selected and determined according to specific application scenarios.
In this embodiment, the manner of acquiring the target processing plugin corresponding to the VNFD version that is currently incompatible with the system may be manual acquisition or automatic acquisition; when the target processing plug-in is manually acquired, the target processing plug-in uploaded by an operation maintenance worker can be acquired; when automatically acquiring, the corresponding target processing plug-in may be searched and downloaded from a plug-in repository (which may be an offline repository or an online repository).
S102: and storing the acquired target processing plug-in and the target VNFD version in the system in an associated manner.
In the step, the obtained target processing plug-in and the target VNFD version are stored in the system in a correlation mode, and then the upgrading of the processing plug-in is completed; the upgraded system can realize the incompatible target VNFD version before upgrading.
Optionally, in this embodiment, each processing plugin in the system may perform associated storage with a VNFD version that is compatible with each processing plugin, so that when a VNFD version package that needs to be processed is received, a processing plugin corresponding to the VNFD version of the VNFD version package is found according to a correspondence between the processing plugin and the VNFD version in the system, so as to process the VNFD version package.
Optionally, in this embodiment, the processing plug-in may be stored locally in the system, so as to be called in time; in some application scenarios, the processing plug-in may also be stored in other locations where the system can invoke and satisfy the invocation failure.
In an example of this embodiment, storing the obtained target processing plug-in association with the target VNFD version in the system may be performed by, but is not limited to, the following:
and performing associated record storage on the version information of the target VNFD version and the storage path information of the target processing plug-in so as to facilitate subsequent matching and calling.
S103: and when the VNFD version package is received, calling a processing plug-in corresponding to the VNFD version of the VNFD version package from the system to process the VNFD version package.
For convenience of understanding, in the present embodiment, the above plug-ins are taken as examples, and the upgrade processing procedures of the above plug-ins are respectively described as examples.
In an example of this embodiment, the obtaining of the target processing plug-in corresponding to the target virtualized network function description VNFD version that is currently incompatible with the system may include:
and when the current incompatible target VNFD version is incompatible versions of current VNFD analysis plug-ins in the system, acquiring a target VNFD analysis plug-in corresponding to the target VNFD version, wherein the target VNFD version is used for analyzing a VNFD version packet with the version as the target VNFD version into data in a target data format which can be identified by the system.
For example, assuming that the current system is compatible with VNFD version V1.1 and VNFD version V1.2, and the target VNFD version that the current system is incompatible with is VNFD version V1.3, and it is determined that none of the VNFD parsing plugins corresponding to VNFD version V1.1 and VNFD version V1.2 is compatible with VNFD version V1.3, at this time, the target VNFD parsing plugin corresponding to VNFD version V1.3 is obtained, and the path information of the target VNFD parsing plugin and the version information V1.3 of VNFD version V1.3 are stored in the system in an associated manner, so that when the version package of VNFD version V1.3 is subsequently received, the stored version information and VNFD parsing plugin are matched with the VNFD parsing plugin corresponding to VNFD version V1.3, so as to parse the version package of VNFD version V1.3 into data in the target data format that can be recognized by the system.
It should be understood that, in the present embodiment, the above target data format may be flexibly set according to requirements, for example, in some examples, the target data format may be set to a JSON (Java Script Object notification) format, and in other examples, the target data format may also be set to an Xml format.
Optionally, in some examples, the VNFD parsing plug-in corresponding to each VNFD version may directly parse the version package of the VNFD version compatible with the VNFD version into the target data format of the system unified formulated version, that is, directly parse into the target data of the set data structure. In other examples, the VNFD parsing plug-in corresponding to each VNFD version may also only implement preliminary parsing of the version packet of the VNFD version compatible with the VNFD parsing plug-in into the target data format corresponding to the VNFD version, and when the obtained data structure of the target data format is inconsistent with the data structure of the target data format corresponding to the preset VNFD version of the system, the VNFD parsing plug-in is converted through the inter-VNFD conversion plug-in, and this processing manner may implement smooth upgrade of the VNFD parsing plug-in, and may improve efficiency and flexibility of upgrade of each VNFD parsing plug-in.
As shown in the foregoing analysis, optionally, in an example of this embodiment, the obtaining of the target processing plug-in corresponding to the target virtualized network function description VNFD version that is currently incompatible with the system may include:
when the target VNFD version is a version incompatible with current conversion plug-ins between VNFD versions in the system, obtaining a conversion plug-in between the target VNFD versions corresponding to the target VNFD version, wherein the conversion plug-in between the target VNFD versions comprises: a first inter-VNFD-version translation plug-in, or a second inter-VNFD-version translation plug-in and a third inter-VNFD-version translation plug-in;
in one example, when the target VNFD inter-version conversion plug-in includes the first VNFD inter-version conversion plug-in, the first VNFD inter-version conversion plug-in is configured to directly convert a data structure of data in the target data format into a data structure in the target data format corresponding to a preset VNFD version after the VNFD version packet of the target VNFD version is parsed into the data in the target data format;
in another example, the second inter-VNFD-version conversion plug-in is configured to convert a data structure of data in the target data format into a data structure in the target data format corresponding to a VNFD version adjacent to the target VNFD version after the VNFD version packet in the target VNFD version is parsed into the data in the target data format; for example, the above example is carried out, where the target VNFD version is VNFD version V1.3, and the adjacent version is VNFD version V1.2, the second inter-VNFD version conversion plug-in is configured to convert the data in the target data format of VNFD version V1.3 into the data structure in the target data format corresponding to VNFD version V1.2 after the VNFD version packet of VNFD version V1.3 is parsed into the data in the target data format;
the third inter-VNFD-version conversion plug-in is configured to convert a data structure of data in a target data format into a data structure in a target data format corresponding to the target VNFD version after the VNFD version packet of the VNFD version adjacent to the target VNFD version is analyzed as the data in the target data format; for example, the above example is carried out, where the target VNFD version is VNFD version V1.3, and the adjacent version is VNFD version V1.2, and the third inter-VNFD-version conversion plug-in is configured to convert the data in the target data format of VNFD version V1.2 into the data structure in the target data format corresponding to VNFD version V1.3 after the VNFD version packet of VNFD version V1.2 is parsed into the data in the target data format.
In this example, the flexible conversion between data structures of target data formats between adjacent VNFD versions can be realized by the second inter-VNFD-version conversion plug-in and the third inter-VNFD-version conversion plug-in, so as to be flexibly selected according to application requirements in a subsequent use process; of course, in some application scenarios, only the second VNFD inter-version conversion plug-in or the third VNFD inter-version conversion plug-in may be flexibly set according to requirements.
In an example of this embodiment, the obtaining of the target processing plug-in corresponding to the target virtualized network function description VNFD version that is currently incompatible with the system may include:
when the target VNFD version is a version incompatible with current VNFD system conversion plugins in the system, the target VNFD system conversion plugins corresponding to the target VNFD version are obtained, and the target VNFD system conversion plugins are used for converting data in a target data format into a uniform data structure in the system after the VNFD version packet of the target VNFD version is converted into the data in the target data format.
In an example of this embodiment, the VNFD system conversion plug-in may convert the data in the target data format of the unified data structure obtained by the conversion of the VNFD inter-version conversion plug-in into a data structure unified within the system.
In this embodiment, determining whether the target VNFD version is a version compatible with each current VNFD system conversion plug-in the system may be determined by, but is not limited to, the following:
when determining that the attribute included in the target VNFD version is different from the attribute included in each version supported by each VNFD system conversion plug-in the system, determining that the target VNFD version is an incompatible version of each current VNFD system conversion plug-in the system; and after determining that the attribute included in the target VNFD version is the same as the attribute included in one of the versions supported by the current VNFD system conversion plugins in the system, determining that the target VNFD version is a version compatible with the current VNFD system conversion plugins in the system, and converting the target data format into a unified data structure in the system after determining that the VNFD version packet of the target VNFD version is converted into the target data format by using the VNFD system conversion plugins.
For example, in the above example, assuming that the target VNFD version is VNFD version V1.3, in an application scenario, it is assumed that VNFD version V1.3 has attributes a, B, and C; in each VNFD version compatible with the current system, the attribute of each VNFD version is A, B and C, and at the moment, the VNFD version V1.3 is judged to be the version incompatible with each current VNFD system conversion plug-in the system; in another application scenario, assume VNFD version V1.3 has attributes a, B, C; in each VNFD version compatible with the current system, the attribute of the VNFD version V1.2 is a, B, and C, and at this time, it is determined that the VNFD version V1.3 is a version compatible with each current VNFD system conversion plug-in the system, and a VNFD system conversion plug-in corresponding to the VNFD version V1.2 may be used as a VNFD system conversion plug-in corresponding to the VNFD version V1.3, and is stored in the system in association with the VNFD version V1.3, and at this time, the VNFD system conversion plug-in may be compatible with the VNFD version V1.2 and the VNFD version V1.3, that is, the multiplexing of the VNFD system conversion plug-in is realized, thereby improving the utilization rate of the VNFD system conversion plug-in.
In an example of this embodiment, the obtaining of the target processing plug-in corresponding to the target virtualized network function description VNFD version that is currently incompatible with the system may include:
when the target VNFD version is a version incompatible with the current virtual infrastructure management VIM resource conversion plug-in the system, the target VIM resource conversion plug-in corresponding to the target VNFD version is obtained, and the VIM resource conversion plug-in is used for converting the unified data structure in the system into a data structure requested by creation of various VIM resources (for example, but not limited to, resources such as a cloud disk, a network, a subnet, a port, a browser, a virtual machine, and the like) after the VNFD version packet of the target VNFD version is converted into the unified data structure in the system.
In this embodiment, determining whether the target VNFD version is compatible with each VIM resource transformation plug-in currently in the system may be determined by, but is not limited to, the following method:
when determining that the attribute included in the target VNFD version is different from the attribute included in each version supported by each current VIM resource conversion plug-in the system, determining that the target VNFD version is an incompatible version of each current VIM resource conversion plug-in the system; and after determining that the attribute included in the target VNFD version is the same as the attribute included in one of the versions supported by the current VIM resource conversion plugins in the system, determining that the target VNFD version is a version compatible with the current VIM resource conversion plugins in the system, and determining that the VNFD version package of the target VNFD version is converted into a unified data structure in the system by using the VIM resource conversion plugins, converting the unified data structure in the system into a data structure of a VIM resource creation request.
For example, in the above example, assuming that the target VNFD version is VNFD version V1.3, in an application scenario, it is assumed that VNFD version V1.3 has attributes a, B, and C; in each VNFD version compatible with the current system, the attribute of each VNFD version is A, B and C, and at the moment, the VNFD version V1.3 is judged to be the version incompatible with each current VIM resource conversion plug-in the system; in another application scenario, VNFD version V1.3 is assumed to have attributes a, B, C; in each VNFD version compatible with the current system, the attribute of VNFD version V1.1 is a, B, C, and at this time, it is determined that VNFD version V1.3 is a version compatible with each current VIM resource conversion plug-in the system, and a VIM resource conversion plug-in corresponding to VNFD version V1.1 may be used as a VIM resource conversion plug-in corresponding to VNFD version V1.3 and stored in the system in association with VNFD version V1.3, and at this time, the VIM resource conversion plug-in may be correspondingly compatible with VNFD version V1.2 and VNFD version V1.3, that is, multiplexing of the VIM resource conversion plug-in is realized, thereby improving the utilization rate of the VIM resource conversion plug-in.
It should be understood that each processing plug-in stored in the system in this embodiment may support functions such as querying, uploading, updating, downloading, deleting, and executing according to specific needs.
It can be seen that, in this embodiment, when an incompatible target VNFD version occurs in the system, at least one of a VNFD analysis plug-in, a plug-in for switching between VNFD versions, a VNFD system conversion plug-in, and a VIM resource conversion plug-in corresponding to the currently incompatible target VNFD version of the system may be directly obtained to perform small-scale flexible upgrade of the plug-in, and the upgrade control is flexible, and has high efficiency and high resource utilization rate, so that various application scenarios with high requirements on timeliness may be better satisfied.
Example two:
the present embodiment provides a VNFD multi-version compatible processing apparatus, which can be disposed in various communication devices (for example, the communication device may be, but is not limited to, an NFVO device or a VNFM device), as shown in fig. 2, including:
the plug-in management module 21 is configured to obtain a target processing plug-in corresponding to a target virtualized network function description VNFD version that is currently incompatible with the system, and store the obtained target processing plug-in and the target VNFD version in the system in an associated manner.
It should be understood that the system in the present embodiment may include, but is not limited to, at least one of an NFVO system and a VNFM system. In this embodiment, corresponding processing plug-ins may be set in advance for different VNFD versions, and it is understood by application that, in some examples, the processing plug-ins corresponding to different VNFD versions may be different, that is, may correspond to one another; in other examples, different VNFD versions may also be configured to correspond to the same processing plugin, that is, one processing plugin may simultaneously be compatible with multiple VNFD versions.
The processing plug-in corresponding to the VNFD version in this embodiment may include, but is not limited to, at least one of a VNFD parsing plug-in, a VNFD inter-version conversion plug-in, a VNFD system conversion plug-in, and a VIM resource conversion plug-in; in the process of upgrading the plug-in, which plug-ins in the plug-ins need to be acquired specifically for the current incompatible VNFD version can be flexibly selected and determined according to specific application scenarios. In this embodiment, the way for the plug-in management module 21 to obtain the target processing plug-in corresponding to the VNFD version that is not compatible with the system currently may be manual obtaining or automatic obtaining.
The plug-in management module 21 stores the acquired target processing plug-in and the target VNFD version in association with the system, and then completes the upgrading of the processing plug-in; the upgraded system can realize the incompatible target VNFD version before upgrading.
Optionally, in this embodiment, the plug-in management module 21 may store the processing plug-in locally in the system, so as to facilitate timely calling; in some application scenarios, the processing plug-in may also be stored in other locations where the system can call and satisfy call failures. In an example of this embodiment, the plug-in management module 21 stores the obtained target processing plug-in and the target VNFD version in the system in an associated manner, which may be stored by, but is not limited to: and performing associated record storage on the version information of the target VNFD version and the storage path information of the target processing plug-in so as to facilitate subsequent matching and calling.
And the processing control module 22 is configured to, when the VNFD version packet is received, call, from the system, a processing plug-in corresponding to the VNFD version of the VNFD version packet to process the VNFD version packet.
For convenience of understanding, in the present embodiment, the following description is given by taking a structure of a plug-in management module 21 as an example, please refer to fig. 3, where the plug-in management module 21 may include at least one of a VNFD parsing plug-in management module 211, a VNFD inter-version conversion plug-in management module 212, a VNFD system conversion plug-in management module 213, and a VIM resource conversion plug-in management module 214, where:
the VNFD analysis plug-in management module 211 is configured to, when a current incompatible target VNFD version is an incompatible version of each current VNFD analysis plug-in the system, obtain a target VNFD analysis plug-in corresponding to the target VNFD version for storage. The VNFD parsing plug-in management module 211 may further be configured to manage VNFD parsing plug-ins corresponding to respective VNFD versions, including but not limited to query, upload, update, download, delete, and execute functions of the VNFD parsing plug-in. It should be understood that, in the present embodiment, the target data format can be flexibly set according to requirements, for example, in some examples, the target data format can be set to a JSON (Java Script Object notification) format, and in other examples, the target data format can also be set to an Xml format.
Optionally, in some examples, the VNFD parsing plug-in corresponding to each VNFD version may directly parse the version package of the VNFD version compatible with the VNFD version into the target data format of the system unified formulated version, that is, directly parse into the target data of the set data structure. In other examples, the VNFD parsing plug-in corresponding to each VNFD version may also only implement preliminary parsing of the version packet of the VNFD version compatible with the VNFD parsing plug-in into the target data format corresponding to the VNFD version, and when the obtained data structure of the target data format is inconsistent with the data structure of the target data format corresponding to the preset VNFD version of the system, the VNFD parsing plug-in is converted through the inter-VNFD conversion plug-in, and this processing manner may implement smooth upgrade of the VNFD parsing plug-in, and may improve efficiency and flexibility of upgrade of each VNFD parsing plug-in.
As shown in the foregoing analysis, the optional inter-VNFD-version conversion plug-in management module 212 is an optional module, and is configured to, when the target VNFD version is a version that is incompatible with current inter-VNFD-version conversion plug-ins in the system, obtain a target inter-VNFD-version conversion plug-in corresponding to the target VNFD version, where the target inter-VNFD-version conversion plug-in includes: a first inter-VNFD-version translation plug-in, or a second inter-VNFD-version translation plug-in and a third inter-VNFD-version translation plug-in; the VNFD inter-version conversion plug-in management module 212 may also be configured to manage VNFD inter-version conversion plug-ins corresponding to each VNFD version, including but not limited to query, upload, update, download, delete, and execute functions of the VNFD inter-version conversion plug-ins.
In an example, when the target VNFD inter-version conversion plug-in includes the first VNFD inter-version conversion plug-in, the first VNFD inter-version conversion plug-in is configured to directly convert the data structure of the data in the target data format into the data structure in the target data format corresponding to the preset VNFD version after the VNFD version packet of the target VNFD version is parsed into the data in the target data format.
In another example, the second inter-VNFD-version conversion plug-in is configured to convert the data structure of the data in the target data format into the data structure in the target data format corresponding to the VNFD version adjacent to the target VNFD version after the VNFD version packet in the target VNFD version is parsed into the data in the target data format.
The third inter-VNFD-version conversion plug-in is configured to convert a data structure of data in the target data format into a data structure in the target data format corresponding to the target VNFD version after the VNFD version packet of the VNFD version adjacent to the target VNFD version is analyzed into the data in the target data format. In this example, the flexible conversion between data structures of target data formats between adjacent VNFD versions can be realized by the second inter-VNFD-version conversion plug-in and the third inter-VNFD-version conversion plug-in, so as to be flexibly selected according to application requirements in a subsequent use process; of course, in some application scenarios, only the second VNFD inter-version conversion plug-in or the third VNFD inter-version conversion plug-in may be flexibly set according to requirements.
The VNFD system conversion plug-in management module 213 is configured to obtain a target VNFD system conversion plug-in corresponding to a target VNFD version when the target VNFD version is a version incompatible with current VNFD system conversion plug-ins in the system. The VNFD system conversion plug-in management module 213 is further configured to manage VNFD system conversion plug-ins corresponding to each VNFD version, including but not limited to query, upload, update, download, delete, and execute functions of the VNFD system conversion plug-in. In an example of this embodiment, the VNFD system conversion plug-in may convert the data in the target data format of the unified data structure obtained after the conversion by the VNFD inter-version conversion plug-in into a unified data structure inside the system.
In this embodiment, the VNFD system conversion plug-in management module 213 may determine whether the target VNFD version is compatible with each current VNFD system conversion plug-in the system by, but not limited to: when determining that the attribute included in the target VNFD version is different from the attribute included in each version supported by each VNFD system conversion plug-in the system, determining that the target VNFD version is an incompatible version of each current VNFD system conversion plug-in the system; and after determining that the attribute included in the target VNFD version is the same as the attribute included in one of the versions supported by the current VNFD system conversion plugins in the system, determining that the target VNFD version is a version compatible with the current VNFD system conversion plugins in the system, and converting the target data format into a unified data structure in the system after determining that the VNFD version packet of the target VNFD version is converted into the target data format by using the VNFD system conversion plugins.
The VIM resource conversion plug-in management module 214 is configured to obtain a target VIM resource conversion plug-in corresponding to a target VNFD version when the target VNFD version is a version incompatible with the VIM resource conversion plug-in of each current virtual infrastructure management in the system, where the VIM resource conversion plug-in is configured to convert a VNFD version packet of the target VNFD version into a unified data structure inside the system, and then convert the unified data structure inside the system into a data structure of a VIM resource creation request. The VIM resource conversion plug-in management module 214 is further configured to manage VIM resource conversion plug-ins corresponding to each VNFD version, including but not limited to query, upload, update, download, delete, and execute functions of the VIM resource conversion plug-ins.
In this embodiment, the VIM resource conversion plug-in management module 214 determines whether the target VNFD version is compatible with each VIM resource conversion plug-in currently in the system, and may be determined by the following methods: when determining that the attribute included in the target VNFD version is different from the attribute included in each version supported by each current VIM resource conversion plug-in the system, determining that the target VNFD version is an incompatible version of each current VIM resource conversion plug-in the system; and after determining that the attribute included in the target VNFD version is the same as the attribute included in one of the versions supported by the current VIM resource conversion plug-ins in the system, determining that the target VNFD version is a version compatible with the current VIM resource conversion plug-ins in the system, and determining that the VNFD version packet of the target VNFD version is converted into a unified data structure in the system by using the VIM resource conversion plug-in, converting the unified data structure in the system into a data structure of a VIM resource creation request.
By using the VNFD multi-version compatible processing device, when an incompatible target VNFD version appears in the system, at least one of a VNFD analysis plug-in, a conversion plug-in among VNFD versions, a VNFD system conversion plug-in and a VIM resource conversion plug-in corresponding to the currently incompatible target VNFD version of the system can be directly obtained so as to perform small-amplitude flexible upgrade of the plug-in, realize the compatibility of the VNFD multi-versions in the same system, have flexible upgrade control and high efficiency and resource utilization rate, and can better meet various application scenes with higher requirements on timeliness.
Example three:
for convenience of understanding, the present embodiment is described below with reference to two specific application scenarios as examples on the basis of the above embodiments.
The application scene one:
in this application scenario, taking the target data format as JSON format as an example, please refer to fig. 4 for a processing procedure of a VNFD version packet of a multi-version-compatible VNFD system, which includes the following steps:
s401: and executing the VNFD parsing plug-in to parse the VNFD version package into data in a JSON format.
S402: and sequentially executing the conversion plug-ins between the VNFD versions to convert the data structure of the JSON format data analyzed in the step S401 into the data structure of the JSON format data corresponding to the designated VNFD version.
S403: and executing the VNFD system conversion plug-in to convert the JSON format data converted in the step S402 into a uniform data structure inside the system.
S404: and executing the VIM resource conversion plug-in to convert the unified data structure in the system obtained in the step S403 into the data structure of the VIM resource creation request.
In an example of the application scenario, assuming that the system is already compatible with the VNFD versions V1.1 and V1.2, and the current system is to be compatible with the VNFD version V1.3, the specific implementation steps shown in fig. 5 include:
s501: uploading the analysis plug-in corresponding to the VNFD of the V1.3 version to a system through a VNFD analysis plug-in management module, and after the uploading is successful, recording the VNFD version number (V1.3) and the path information of the corresponding VNFD analysis plug-in an associated manner in the system. If the VNFD analysis plug-in corresponding to the V1.2 version is compatible with the VNFD of the V1.3 version, the VNFD analysis plug-in is not required to be uploaded, the VNFD version number (V1.3) is only required to be recorded in the system, and the VNFD analysis plug-in path information is directly filled into the VNFD analysis plug-in path of the V1.2 version.
S502: the VNFD version conversion plug-ins from V1.2 to V1.3 are uploaded to a system through a VNFD version conversion plug-in management module, and after the uploading is successful, a source version number (V1.2), a target version number (V1.3) and a VNFD version conversion plug-in path need to be recorded in the system.
S503: the VNFD version conversion plug-in from V1.3 to V1.2 is uploaded to a system through a VNFD version conversion plug-in management module, and after the uploading is successful, a source version number (V1.3), a target version number (V1.2) and a VNFD version conversion plug-in path need to be recorded in the system.
S504: JSON data of VNFD of the V1.3 version is converted into plug-in with a unified data structure in the system through a VNFD system conversion plug-in management module and uploaded to the system, and after the plug-in is uploaded successfully, a VNFD version number (V1.3) needs to be recorded in the system, and the VNFD system converts a path of the plug-in. It should be understood that: this step is an optional step, if the V1.2 and V1.3 versions do not change much, for example, the attributes are the same, it is not necessary to upload the JSON data of VNFD of V1.3 version to convert to the plug-in of the unified data structure inside the system, and the JSON data of VNFD can be converted to the JSON data of V1.2 version through the VNFD version conversion plug-in of V1.3 to V1.2, and then converted to the unified data structure inside the system through the plug-in of the VNFD of V1.2 version to convert to the plug-in of the unified data structure inside the system.
S505: uploading the VIM resource conversion plug-in of the VNFD of the V1.3 version to a system through a VIM resource conversion plug-in management module, and after the uploading is successful, recording the VNFD version number (V1.3) and the path of the VIM resource conversion plug-in the system.
For example, if some attributes are newly added to the VNFD of the V1.3 version, and need to be added to the VIM resource creation request structure, for example, an attribute is newly added to the VNFD and needs to be added to the request parameter for creating the virtual machine, the VIM resource conversion plug-in of the new virtual machine creation request needs to be updated to the system through the VIM resource conversion plug-in management module. In this embodiment, only one conversion plug-in for each VIM resource may be set in the VIM resource conversion plug-in management module, and when the structure of the VIM resource creation request changes, the VIM resource conversion plug-in needs to be updated.
S506: and when a V1.3 version packet is received, transmitting the VNFD version number and the VNFD version path to a VNFD analysis plug-in management module, finding a corresponding VNFD analysis plug-in according to the V1.3 version number by the VNFD analysis plug-in management module, executing the VNFD analysis plug-in, and analyzing the VNFD of the V1.3 version into data in a JSON format.
S507: converting the JSON format data in the S506 into a JSON format data structure of a preset version;
s508: the data structure in JSON format in S507 is converted into a system unified data structure.
In this step, the VNFD system conversion plug-in management module may find whether there is a plug-in for which the VNFD of the V1.3 version is directly converted to the system unified data structure, if not, find the corresponding inter-version conversion plug-in to convert the JSON-formatted data of the VNFD of the V1.3 version into the JSON-formatted data of the VNFD of the V1.2 version according to the source version number V1.3 and the target version number V1.2 (previous version) to the VNFD inter-version conversion plug-in management module, then find whether there is a plug-in for which the VNFD of the V1.2 version is converted to the system unified data structure, and continue to convert to the previous version if not found; if so, the specified version of the VNFD data format is converted to a uniform data structure within the system directly from the found plug-in.
S509: and converting the unified data structure inside the system obtained in the step S508 into the data structure of the VIM resource creation request.
Before creating the VIM resource, the VIM resource conversion plug-in of the specified resource in the VIM resource conversion plug-in management module needs to be executed to obtain the data structure of the VIM resource creation request, and then the interface of the VIM layer is called to complete the creation of the VIM resource based on the request data structure.
VNFD version conversion is complete.
Application scenario two:
in this application scenario, a schematic interaction process of VNFD version conversion of different vendors is used for explanation, and it is assumed that the NFVO of this vendor needs to be interfaced with VNFMs of other vendors, and the difference between the VNFD versions of two vendors is relatively large, and the NFVO of this vendor needs to convert the VNFM of the interfaced vendor, according to this embodiment, specific implementation steps are shown in fig. 6, and include:
s601: uploading a VNFD analysis plug-in corresponding to a VNFD of a corresponding version provided by a docking manufacturer to a system of the manufacturer through a VNFD analysis plug-in management module, wherein after the uploading is successful, a VNFD version number (V1.X) needs to be recorded in the system, and VNFD analysis plug-in path information is obtained.
S602: JSON data of VNFD of the V1.X version is converted into VNFD system conversion plug-in of a unified data structure in the system through a VNFD system conversion plug-in management module and uploaded to the system, and after uploading is successful, a VNFD version number (V1.X) and a path of the VNFD system conversion plug-in need to be recorded in the system.
It should be understood that, according to requirements, a VNFD inter-version conversion plug-in may also be provided in the present application scenario to implement smooth conversion of JSON data. In some application scenarios, the VIM resource conversion plug-in corresponding to the v1.X version may also be uploaded or specified in advance.
S603: the version information (i.e. version packet, for example, including VNFD version number and VNFD version path) of the VNFD of the docking manufacturer is transferred to the VNFD parsing plug-in management module, and the VNFD parsing plug-in management module finds and executes the corresponding VNFD parsing plug-in according to the version number of v1.x, and parses the VNFD of the v1.x version into data in JSON format.
S604: and the VNFD system conversion plug-in management module finds the VNFD of the V1.X version to be converted into the VNFD system conversion plug-in of the system unified data structure according to the V1.X and executes the VNFD system conversion plug-in, and converts the VNFD data format of the V1.X version into the system unified data structure.
S605: before the VIM resource is created, the VIM resource conversion plug-in of the appointed resource in the VIM resource conversion plug-in management module is executed to obtain a VIM resource creation request data structure, and then an interface of a VIM layer is called to complete the creation of the VIM resource based on the request data structure.
And completing the conversion of the VNFD version of the docking manufacturer.
Therefore, the VNFD multi-version compatibility processing method provided by this embodiment can directly obtain at least one of a VNFD analysis plug-in, a plug-in for switching between VNFD versions, a plug-in for switching a VNFD system, and a plug-in for switching VIM resources, which correspond to a current incompatible target VNFD version of the system, for various application scenarios in which incompatible target VNFD versions occur in the system, so as to perform small-scale flexible upgrade of the plug-in, and the upgrade control is flexible and has high efficiency and high resource utilization rate, and can better satisfy various application scenarios with higher requirements on timeliness.
Example four:
the embodiment also provides a communication device, which may be an NFVO device or a VNFM device, as shown in fig. 7, and includes a processor 701, a memory 702, and a communication bus 703;
the communication bus 703 is used for realizing communication connection between the processor 701 and the memory 702;
in one example, the processor 701 may be configured to execute one or more computer programs stored in the memory 702 to implement the steps of the VNFD multi-version compatible processing method as in the embodiments above.
The present embodiments also provide a computer-readable storage medium including volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact disk Read-Only Memory), digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
In one example, the computer readable storage medium in this embodiment may be used to store one or more computer programs that are executable by one or more processors to implement the steps of the VNFD multi-version compatible processing method as in the above embodiments.
The present embodiment also provides a computer program (or computer software), which can be distributed on a computer-readable medium and executed by a computing apparatus to implement at least one step of the VNFD multi-version compatible processing method as shown in the above embodiments; and in some cases at least one of the steps shown or described may be performed in an order different than that described in the embodiments above.
The present embodiments also provide a computer program product comprising a computer readable means having a computer program as shown above stored thereon. The computer readable means in this embodiment may include a computer readable storage medium as shown above.
It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, numerous simple deductions or substitutions may be made without departing from the spirit of the invention, which shall be deemed to belong to the scope of the invention.

Claims (11)

1. A VNFD multi-version compatible processing method comprises the following steps:
acquiring a target processing plug-in corresponding to a currently incompatible target Virtualization Network Function Description (VNFD) version of the system;
storing the acquired target processing plug-in and the target VNFD version in a system in an associated manner;
and when the VNFD version package is received, calling a processing plug-in corresponding to the VNFD version of the VNFD version package from the system to process the VNFD version package.
2. The VNFD multi-version compatibility processing method of claim 1, wherein the obtaining a target processing plugin corresponding to a target virtualized network function description VNFD version that is currently incompatible with the system comprises:
and when the target VNFD version is a version which is incompatible with each current VNFD analysis plug-in the system, acquiring a target VNFD analysis plug-in corresponding to the target VNFD version, wherein the target VNFD analysis plug-in is used for analyzing a VNFD version packet of which the version is the target VNFD version into data of a target data format which can be identified by the system.
3. The VNFD multi-version compatibility processing method of claim 1, wherein the obtaining a target processing plugin corresponding to a target virtualized network function description VNFD version that is currently incompatible with the system comprises:
when the target VNFD version is a version incompatible with current inter-VNFD version conversion plug-in the system, obtaining an inter-target-VNFD version conversion plug-in corresponding to the target VNFD version, where the inter-target-VNFD version conversion plug-in includes: a first inter-VNFD-version translation plug-in, or a second inter-VNFD-version translation plug-in and a third inter-VNFD-version translation plug-in;
the first inter-VNFD-version conversion plug-in is used for directly converting a data structure of data in a target data format into a data structure of the target data format corresponding to a preset VNFD version after the VNFD version packet of the target VNFD version is analyzed into the data in the target data format;
the second inter-VNFD-version conversion plug-in is configured to convert a data structure of data in a target data format into a data structure in a target data format corresponding to a VNFD version adjacent to the target VNFD version after the VNFD version packet of the target VNFD version is analyzed as the data in the target data format;
the third inter-VNFD-version conversion plug-in is configured to convert a data structure of data in a target data format into a data structure in a target data format corresponding to the target VNFD version after the VNFD version packet of the VNFD version adjacent to the target VNFD version is analyzed into the data in the target data format.
4. The VNFD multi-version compatibility processing method of any one of claims 1 to 3, wherein the obtaining a target processing plug-in corresponding to a target virtualized network function description VNFD version that is currently incompatible with the system comprises:
and when the target VNFD version is a version incompatible with each current VNFD system conversion plug-in the system, acquiring a target VNFD system conversion plug-in corresponding to the target VNFD version, wherein the target VNFD system conversion plug-in is used for converting the data in the target data format into a uniform data structure in the system after the VNFD version packet of the target VNFD version is converted into the data in the target data format.
5. The VNFD multi-version compatibility processing method of claim 4, wherein when the attributes included in the target VNFD version are not the same as the attributes included in the versions supported by current VNFD system translation plug-ins in the system, it is determined that the target VNFD version is a version that is incompatible with the current VNFD system translation plug-ins in the system;
and when the attribute included in the target VNFD version is the same as the attribute included in the version supported by a current VNFD system conversion plug-in the system, determining that the VNFD version packet of the target VNFD version is converted into data in a target data format by using the VNFD system conversion plug-in, and converting the data in the target data format into a uniform data structure in the system.
6. The VNFD multi-version compatibility processing method of any one of claims 1 to 3, wherein the obtaining a target processing plug-in corresponding to a target virtualized network function description VNFD version that is currently incompatible with the system comprises:
when the target VNFD version is incompatible versions of the current Virtual Infrastructure Management (VIM) resource conversion plugins in the system, acquiring a target VIM resource conversion plugin corresponding to the target VNFD version, wherein the VIM resource conversion plugin is used for converting a unified data structure in the system into a data structure of a VIM resource creation request after a VNFD version packet of the target VNFD version is converted into the unified data structure in the system.
7. The VNFD multi-version compatibility processing method of claim 6, wherein when the attributes included in the target VNFD version are different from the attributes included in the versions supported by the current VIM resource translation plug-in the system, determining that the target VNFD version is a version that is incompatible with the current VIM resource translation plug-in the system;
and when the attribute included in the target VNFD version is the same as the attribute included in the version supported by a certain current VIM resource conversion plug-in the system, determining that the VNFD version package of the target VNFD version is converted into a unified data structure in the system by adopting the VIM resource conversion plug-in, and then converting the unified data structure in the system into the data structure of the VIM resource creation request.
8. The VNFD multi-version compatibility processing method of any one of claims 1-3, wherein the storing the obtained target processing plug-in association with the target VNFD version in a system comprises:
and performing associated record storage on the version information of the target VNFD version and the storage path information of the target processing plug-in.
9. A VNFD multi-version compatible processing apparatus, comprising:
the plug-in management module is used for acquiring a target processing plug-in corresponding to a target Virtualized Network Function Description (VNFD) version which is not compatible with the system at present, and storing the acquired target processing plug-in and the target VNFD version in the system in a correlation manner;
and the processing control module is used for calling a processing plug-in corresponding to the VNFD version of the VNFD version package from the system to process the VNFD version package when the VNFD version package is received.
10. A communication device comprising a processor, a memory, and a communication bus;
the communication bus is used for connecting the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the VNFD multi-version compatible processing method of any of claims 1-8.
11. A computer-readable storage medium, storing one or more computer programs, the one or more computer programs being executable by one or more processors to perform the steps of the VNFD multi-version compatibility processing method of any one of claims 1-8.
CN201910656824.7A 2019-07-19 2019-07-19 VNFD multi-version compatible processing method, device, equipment and storage medium Active CN112242918B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910656824.7A CN112242918B (en) 2019-07-19 2019-07-19 VNFD multi-version compatible processing method, device, equipment and storage medium
PCT/CN2020/099292 WO2021012905A1 (en) 2019-07-19 2020-06-30 Vnfd multi-version compatible processing method, device, apparatus and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910656824.7A CN112242918B (en) 2019-07-19 2019-07-19 VNFD multi-version compatible processing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112242918A CN112242918A (en) 2021-01-19
CN112242918B true CN112242918B (en) 2023-03-24

Family

ID=74168353

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910656824.7A Active CN112242918B (en) 2019-07-19 2019-07-19 VNFD multi-version compatible processing method, device, equipment and storage medium

Country Status (2)

Country Link
CN (1) CN112242918B (en)
WO (1) WO2021012905A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634778A (en) * 2014-11-04 2016-06-01 中兴通讯股份有限公司 Method and system to achieve VNF instantiation, NFVO and VNFM
CN107209686A (en) * 2015-01-23 2017-09-26 日本电气株式会社 Network function virtual management and method of combination, equipment and program
CN108400998A (en) * 2017-02-07 2018-08-14 华为技术有限公司 A kind of method and system of deployment VNF

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016125554A1 (en) * 2015-02-03 2016-08-11 日本電気株式会社 Virtual network system, virtual network control method, virtual network function database, integrated control device, control device, and control method and control program therefor
CN106982129A (en) * 2016-01-15 2017-07-25 中兴通讯股份有限公司 Method for upgrading software and device
CN107436775A (en) * 2016-05-26 2017-12-05 中兴通讯股份有限公司 The method and device of business release is installed on virtual machine
US20180196687A1 (en) * 2017-01-06 2018-07-12 Ca, Inc. Adaptive data modeling
CN109660575B (en) * 2017-10-10 2022-08-02 中兴通讯股份有限公司 Method and device for realizing NFV service deployment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634778A (en) * 2014-11-04 2016-06-01 中兴通讯股份有限公司 Method and system to achieve VNF instantiation, NFVO and VNFM
CN107209686A (en) * 2015-01-23 2017-09-26 日本电气株式会社 Network function virtual management and method of combination, equipment and program
CN108400998A (en) * 2017-02-07 2018-08-14 华为技术有限公司 A kind of method and system of deployment VNF

Also Published As

Publication number Publication date
CN112242918A (en) 2021-01-19
WO2021012905A1 (en) 2021-01-28

Similar Documents

Publication Publication Date Title
US11625281B2 (en) Serverless platform request routing
US10592402B2 (en) Automated integration testing with mock microservices
US20220078092A1 (en) Provisioning a service
US10452372B2 (en) Method and deployment module for managing a container to be deployed on a software platform
CN110324169B (en) Interface management method and device
US11693642B2 (en) Method and system for cross-platform deployment
CN109120678A (en) The method and apparatus of service tray for distributed memory system
CN110096424B (en) Test processing method and device, electronic equipment and storage medium
CN111427594B (en) Application program running method and device
CN105072398B (en) A kind of device updating method and device
CN112398673A (en) Upgrading method, communication equipment and computer readable storage medium
US10608907B2 (en) Open-loop control assistant to guide human-machine interaction
US20230239212A1 (en) Stable References for Network Function Life Cycle Management Automation
CN110557281B (en) Intelligent operation and maintenance method and device based on CMDB and alarm map
US10838712B1 (en) Lifecycle management for software-defined datacenters
CN117112122A (en) Cluster deployment method and device
CN114338820A (en) Network access method, device, electronic equipment and storage medium
CN108370329B (en) Management method and device for management function object
CN112242918B (en) VNFD multi-version compatible processing method, device, equipment and storage medium
CN112015454A (en) System upgrade package generation method and device, electronic equipment and storage medium
CN109495298B (en) Method and device for managing nodes in OpenStack system
CN111897565A (en) Data processing method, device and equipment based on Internet of things
CN116225617A (en) Management migration method and device for container instance, electronic equipment and storage medium
EP3340048A1 (en) System and method for content - application split
CN110830275B (en) Transponder configuration method, device, equipment and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant