CN112889247B - VNF service instantiation method and device - Google Patents
VNF service instantiation method and device Download PDFInfo
- Publication number
- CN112889247B CN112889247B CN201880098821.XA CN201880098821A CN112889247B CN 112889247 B CN112889247 B CN 112889247B CN 201880098821 A CN201880098821 A CN 201880098821A CN 112889247 B CN112889247 B CN 112889247B
- Authority
- CN
- China
- Prior art keywords
- container service
- container
- caas
- management platform
- instance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
Abstract
The application discloses a VNF service instantiation method and a VNF service instantiation device, and the VNF service instantiation method comprises the steps that a VNFM receives a VNF instantiation request message of a virtual network function, and obtains container service capacity information needing to be called in the VNF instantiation; the VNFM sends a container service discovery request to a container service (CaaS) management platform, and container service capability information is carried in a container service discovery request message; receiving a container service discovery response message from a CaaS management platform by a VNFM, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information; the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for instantiating a Virtual Network Function (VNF) service.
Background
Network Function Virtualization (NFV) technology can be simply understood as migrating the functions of various Network elements used in a telecommunication Network from the current dedicated hardware platform to a common Commercial-off-the-shelf (COTS) server. Each network element used in the telecommunication network is converted into independent application through NFV technology, the network element can be flexibly deployed on a unified infrastructure platform constructed by other equipment such as a standard server, a storage and a switch, the resources of infrastructure hardware equipment are pooled and virtualized through virtualization technology, virtual resources are provided for upper-layer application, application and hardware decoupling is achieved, each application can rapidly increase the virtual resources to achieve the purpose of rapidly expanding the system capacity, or the virtual resources can be rapidly reduced to achieve the purpose of shrinking the system capacity, and the elasticity of the network is greatly improved. A shared resource pool is formed by adopting a universal COTS server, newly developed services do not need to be independently deployed with hardware equipment, and the online time of the new services is greatly shortened.
The foundation of NFV technology includes cloud computing technology and virtualization technology. Hardware devices such as general COTS calculation/storage/network can be decomposed into multiple virtual resources through virtualization technology, so that the multiple virtual resources can be used by various upper-layer applications. The decoupling between the application and the hardware is realized through a virtualization technology, so that the virtual resource supply speed is greatly increased; by the cloud computing technology, elastic expansion of application can be achieved, matching of virtual resources and service loads is achieved, utilization efficiency of the virtual resources is improved, and response rate of a system is improved.
The virtualized telecommunication network function gradually evolves as containers, a Container as a Service (CaaS) being a specific type of Platform as a Service (PaaS) Service. A container is an operating system level virtualization technology, and separates different processes through operating system isolation technologies such as CGroup and NameSpace under Linux. The container technology is different from a hardware virtualization (Hypervisor) technology, virtual hardware is not provided, an operating system is not provided inside the container, and only a process is provided. Due to the important characteristic of the container technology, the container is lighter in weight and more convenient to manage compared with a virtual machine. In the run state of the container, a common set of management operations is defined, such as: start, stop, pause, delete, etc., to perform unified life cycle management on the containers.
However, the prior art does not describe any explicit description of how different types of VNF instances are instantiated and how container services are invoked.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, and a system for instantiating a VNF service, which explicitly describe a flow and an interface with respect to the prior art.
The embodiment of the invention provides a Virtual Network Function (VNF) service instantiation method, which comprises the following steps:
a Virtual Network Function Manager (VNFM) receives a Virtual Network Function (VNF) instantiation request message and acquires container service capability information to be called when the VNF is instantiated;
the VNFM sends a container service discovery request to a container service (CaaS) management platform, and container service capability information is carried in a container service discovery request message;
receiving a container service discovery response message from a CaaS management platform by a VNFM, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information;
the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
The step of obtaining the container service capability needing to be called by the VNF instantiation by the VNFM includes:
and the VNFM acquires the corresponding VNFD in a database according to the VNF instantiation request message, and acquires the corresponding container service capability information in the VNFD.
The discovering, by the CaaS management platform according to the container service capability information, a container service instance includes:
the CaaS management platform determines a corresponding container service descriptor file according to the container service capability information carried in the request message;
and the CaaS management platform searches or instantiates a container service instance according to the container service descriptor file.
The embodiment of the invention provides a VNFM device of a virtual network function manager, which comprises:
a receiving unit, configured to receive a virtual network function VNF instantiation request message;
the processing unit is used for acquiring the container service capability information needing to be called in the VNF instantiation;
the sending unit is used for sending a container service discovery request to the CaaS management platform, and the container service capability information is carried in a container service discovery request message;
the receiving unit is further configured to receive a container service discovery response message from the CaaS management platform, where the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information.
The processing unit is further configured to create a corresponding VNF instance according to the instantiation request message, and send identification information of the container service instance to the VNF instance.
The step of acquiring, by the processing unit, the container service capability information to be called in the VNF instantiation specifically includes:
and the processing unit acquires the corresponding VNFD in a database according to the VNF instantiation request message and acquires the corresponding container service capability information in the VNFD.
The container service capability information includes: a capacity threshold for container service instances to scale elastically, and/or affinity or anti-affinity rules between container services, and/or monitoring parameters supported by container services.
The embodiment of the invention provides a CaaS management platform device, which comprises:
a receiving unit, configured to receive a container service discovery request from a VNFM, where a container service discovery request message carries the container service capability information;
a processing unit for discovering a container service instance according to the container service capability information;
and the sending unit is used for sending a container service discovery response message to the VNFM, wherein the response message carries the identification information of the discovered container service instance.
The discovering, by the processing unit, the container service instance according to the container service capability information includes:
the processing unit determines a corresponding container service descriptor file according to the container service capability information carried in the request message; and find or instantiate a container service instance based on the container service descriptor file.
The embodiment of the invention provides a virtual network function VNF service instantiation system, which comprises a virtual network function manager VNFM and a container as a service (CaaS) management platform, wherein the VNFM is used for receiving a virtual network function manager VNFM receiving virtual network function VNF instantiation request message and acquiring container service capacity information required to be called by VNF instantiation; the VNFM sends a container service discovery request to a CaaS management platform, and container service capability information is carried in a container service discovery request message; the VNFM receives a container service discovery response message from the CaaS management platform, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information; the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
And the CaaS management platform is used for discovering the container service instance according to the container service capability information and sending a service discovery response message to the VNFM.
The discovering, by the CaaS management platform according to the container service capability information, a container service instance includes:
the CaaS management platform determines a corresponding container service descriptor file according to the container service capability information carried in the request message;
and the CaaS management platform searches or instantiates a container service instance according to the container service descriptor file.
The container service capability information includes: a capacity threshold for container service instances to scale elastically, and/or affinity or anti-affinity rules between container services, and/or monitoring parameters supported by container services.
The embodiment of the invention also provides a virtual network function VNF service instantiation device, which comprises a processor and a memory; the memory is used for storing programs for executing the method and storing data related to the method; the processor is configured to execute programs stored in the memory.
The embodiment of the invention also provides a container as a service (CaaS) management platform device, which comprises a processor and a memory; the memory is used for storing programs for executing the method and data for realizing the method; the processor is configured to execute programs stored in the memory.
Embodiments of the present invention further provide a computer-readable storage medium, where executable program instructions are stored, and when the executable program instructions are executed, the computer-readable storage medium is configured to perform the steps involved in the above method.
Embodiments of the present invention also provide a computer program product for performing the above-described method steps when the computer program product is executed.
The solution provided by the above embodiment makes clear how different types of VNF instances are instantiated and how container services are invoked, and solves the technical problem that different types of VNFs in the prior art cannot invoke container services.
Drawings
Fig. 1 is a schematic diagram of an NFV architecture according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an NFV architecture deployed with a CaaS management platform according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating a VNF service instantiation process according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a VNF service instantiation system architecture provided in an embodiment of the present invention;
FIG. 5 is a schematic diagram of a VNFM apparatus according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a CaaS management platform apparatus according to an embodiment of the present invention;
fig. 7 is a schematic hardware diagram of a VNFM/CaaS device according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Before further detailed description of the embodiments of the present application, an application scenario of the embodiments of the present application is introduced.
Since the CaaS management platform according to the embodiment of the present application is deployed in the NFV architecture, the NFV architecture is introduced first. Fig. 1 is a schematic diagram of an NFV architecture according to an embodiment of the present application, where the NFV system architecture can be applied to various types of networks, such as an operator communication network or a local area network.
As shown in fig. 1, the NFV architecture mainly includes a MANO entity 110, an NFVI 120, a plurality of VNFs 130, a plurality of Element Management (EM) 140, and an Operation Support Management System (OSS/BSS) 150. The MANO entity 110 further includes a Network Function Virtualization Orchestrator (NFVO) 110a, one or more Virtual Network Function Managers (VNFM) 110b, and a Virtualized Infrastructure Manager (VIM) 110 c.
For convenience of description, the functions of the respective modules in the NFV architecture of fig. 1 are described next.
The NFVO 110a is configured to implement Network Service Descriptors (NSDs) and management and processing of virtual Network function Forwarding graphs (VNF Forwarding graphs, VNFFGs), management of a Network Service lifecycle, and implement the lifecycle management of the VNF and a global view function of virtual resources in cooperation with the VNFM.
The VNFM110b is used to implement lifecycle management of a VNF, including management of virtualized network function Descriptor (VNF Descriptor, VNFD) files, instantiation of the VNF, elastic Scaling of VNF instances (including volume Scaling out/up and volume Scaling in/down), healing (healing) of VNF instances, and termination of VNF instances. The VNFM also supports receiving a flexible scaling (scaling) strategy issued by the NFVO, and realizes automatic VNF flexible scaling.
The VIM 110b is responsible for managing (including reserving and allocating) hardware resources of an infrastructure layer, managing virtualized resources, monitoring and reporting a fault of a virtual resource state, and providing a virtualized resource pool to an upper-layer application.
OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.
The EM 140 is used to perform traditional Fault, Configuration, user, Performance and Security Management (FCAPS) functions for the VNF 130.
The VNF 130 corresponds to a Physical Network Function (PNF) in a conventional non-virtualized Network, such as a virtualized 4G Core Network (EPC) EPC node, such as a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network Gateway (PGW), and the like. The functional behavior and state of the network function are independent of virtualization, and the NFV technology is required to expect that VNF and PNF have the same functional behavior and external interface.
In addition, the VNF 130 may be composed of multiple VNF components (VNFCs), and thus, in practical applications, one VNF 130 may be deployed on multiple Virtual Machines (VMs), each VM carrying a function of one VNF Component. Of course, one VNF 130 may also be deployed on one VM.
The NFVI 120 is composed of hardware resources and virtual resources and a virtualization layer, which from the perspective of the VNF 130 appears to be a complete entity that can provide the required virtual resources.
Fig. 2 is a schematic diagram of an NFV architecture deployed with a CaaS management platform according to an embodiment of the present application, and as shown in fig. 2, relative to the NFV architecture shown in fig. 1, the NVF architecture shown in fig. 2 further includes the CaaS management platform, and the management platform mainly includes a container manager 160 and a container service 170. The container manager 160 is communicatively connected to the VNFM and VIM, and is responsible for functions of the platform management plane, instantiating or terminating instances of the respective container services 170, and the like; the container service 170 is called by the containerization VNF in the process of configuring after the instantiation is completed.
The CaaS management platform deployed in the NFV architecture and the VNFM entity in the NFV architecture are used to execute the method in the embodiment of the present application. As shown in fig. 3, the method mainly includes:
step 301-: the method comprises the steps that a virtual network function manager VNFM receives a virtual network function VNF instantiation request message sent by NFVO or EM, and obtains container service capability information needing to be called by VNF instantiation in the request message.
Specifically, the VNFM instantiates a request message according to the VNF, where the request message carries specific type information of the VNF to be instantiated, where the specific type specifically refers to a function of which network element (e.g., MME, SGW, PGW, PCRF, or the like) the instantiated VNF corresponds to, and therefore, functions included in each type of VNF are different. And then the VNFM acquires the VNFD corresponding to the instantiated VNF of the type from the database, and acquires the capability information of the container service which needs to be called by the VNF of the type from the VNFD. The capability information specifically includes but is not limited to: a capacity threshold of the container service elastic expansion, an Affinity (Affinity) or Anti-Affinity (Anti-Affinity) rule between container services, a Monitoring Parameter (Monitoring Parameter) supported by the container service, and the like.
Step 303: and the VNFM sends a container service discovery request to the CaaS management platform, and the container service capability information is carried in a container service discovery request message.
Step 304: the CaaS management platform locally searches a container service descriptor file matched with the container service capability information according to the capability information of the container service carried in the received discovery request message, searches or instantiates a container service instance on the CaaS management platform according to the container service descriptor file, and sends a service discovery response message to the VNFM.
For example, if the requirement information of the container service capability includes a requirement on a capacity threshold of elastic expansion of the container service, the CaaS management platform maps the requirement information to a specification of the number of container service copies corresponding to the container service (including upper and lower thresholds of the number of copies), and searches and determines a corresponding container service descriptor file according to a description about the specification of the number of container service copies in the container service descriptor file.
After determining a container service descriptor file matching the demand information of the container service capability carried in the request message, the CaaS management platform searches or instantiates a container service instance on the CaaS management platform according to the container service descriptor file, and sends a service discovery response message to the VNFM, wherein the response message carries identification information of the container service instance. Specifically, the method comprises the following steps:
1. if only one container service descriptor file is determined by the CaaS management platform and matches the requirement information of the container service capability carried in the request message, then:
the CaaS management platform locally searches whether a container service instance instantiated by using the container service descriptor file exists;
b1. if the container service instance exists and the status of the container service instance is "available" (unused by other VNF instances), the container service management platform treats the container service instance as a discovered container service instance and returns an identification of the container service instance to the VNFM in a reply message;
b2. if the container service instance exists, but the state of the container service instance is 'unavailable', or no such container service instance exists, the CaaS management platform instantiates a new container service instance by using the container service descriptor file, takes the newly instantiated container service instance as a discovered container service instance, and returns the identifier of the container service instance to the VNFM in a response message;
2. if a plurality of container service descriptor files are determined by the CaaS management platform to match the requirement information of the container service capability carried in the request message, the CaaS management platform selects one of the descriptor files according to a preset descriptor file selection strategy and continues to execute the steps a, b1/b 2; alternatively, the first and second electrodes may be,
the CaaS management platform sends the multiple container service descriptor files to the VNFM; the VNFM selects a container service descriptor file meeting VNFM requirements from the VNFM according to a container service descriptor file selection strategy configured in advance locally, and then sends the selected container service descriptor file to the CaaS management platform. And the CaaS management platform continues to execute the steps a, b1/b 2.
The container descriptor file selection policy of the CaaS management platform and the container service descriptor file selection policy preconfigured by the VNFM may be non-technical policies, and may be selected according to a pricing range or business constraint terms of a container service instance created by the container service descriptor file. Examples include: and selecting a descriptor file corresponding to a container service with a higher price from container service prices corresponding to different descriptor files, or selecting a descriptor file corresponding to a higher constraint term from container service business constraint terms corresponding to different descriptor files, and the like.
The identifier of the container service instance includes an ID and container service instance access address information, and the like, where the address information may be an IP address, and the instantiated VNF can access the corresponding container service instance according to the identifier of the container service instance.
Step 305: and the VNFM receives a container service discovery response message from the CaaS management platform, wherein the response message carries the identification information of the container service instance discovered by the CaaS management platform according to the container service capability information.
After receiving the container service discovery response message from the CaaS management platform, the VNFM acquires the identification information of the container service instance from the message. In the scenario of instantiating different types of VNFs, the VNFM may locally store, maintain and update the correspondence between the different types of VNFs to be instantiated and the identification information of the container service instance to be called.
Step 306-307: the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
The VNFM creates one or more VNF instances according to the VNF instantiation request message in step 301, where the VNF instances are all of the same type; and the instantiated VNF calls a corresponding container service instance in the CaaS management platform according to the container service instance identification information received from the VNFM.
Fig. 4 is a schematic diagram of an architecture of a VNF service instantiation system in an embodiment of the present invention, where the system includes a virtual network function manager VNFM and a container as a service, CaaS, management platform, where,
the VNFM is used for receiving a virtual network function manager VNFM receiving virtual network function VNF instantiation request message and acquiring the container service capability required to be called by the VNF instantiation; the VNFM sends a container service discovery request to a CaaS management platform, and container service capability information is carried in a container service discovery request message; the VNFM receives a container service discovery response message from the CaaS management platform, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information; the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
And the CaaS management platform is used for determining a corresponding container service descriptor file according to the container service capability information carried in the request message, locally searching or instantiating a container service instance according to the container service descriptor file and sending a service discovery response message to the VNFM.
The VNFM and CaaS management platform may be configured to perform each of the method steps described above as being performed by the VNFM.
Fig. 5 is a schematic diagram of a virtual network function manager VNFM apparatus, including:
a receiving unit 510, configured to receive a virtual network function VNF instantiation request message;
a processing unit 520, configured to obtain a container service capability that needs to be invoked by the VNF instantiation;
a sending unit 530, configured to send a container service discovery request to a CaaS management platform, where a container service discovery request message carries the container service capability information;
the receiving unit 510 is continuously configured to receive a container service discovery response message from the CaaS management platform, where the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information.
The processing unit 520 is further configured to create a corresponding VNF instance according to the instantiation request message, and send identification information of the container service instance to the VNF instance.
The detailed steps and functions of the above units can refer to the description of the method steps in fig. 3, and are not repeated here.
Fig. 6 is a schematic diagram of an apparatus of a CaaS management platform, where the apparatus includes:
a receiving unit 610, configured to receive a container service discovery request from a VNFM, where a container service discovery request message carries the container service capability information;
the processing unit 620 determines a corresponding container service descriptor file according to the container service capability information carried in the request message; searching or instantiating a container service instance locally according to the container service descriptor file;
a sending unit 630, configured to send a container service discovery response message to the VNFM, where the response message carries identification information of the discovered container service instance.
The specific steps and functions of the above units can refer to the description of the method steps of fig. 3, and are not repeated here.
Fig. 7 is a hardware diagram of a VNFM device provided by an embodiment of the present invention, where the device 70 may include: a processor, a communication interface, and a memory.
The processor 71 may include one or more processing units, which may be a Central Processing Unit (CPU) or a Network Processor (NP), etc.
The communication interface 74 is used for interfacing and information interaction with other communication devices, including receiving and sending corresponding messages; the network device 70 may further comprise a memory 73, and the processor 71 may be connected to the memory 73 and the communication interface 74 via a bus. The memory 73 may be used to store software programs that may be executed by the processor 71 to implement the method steps performed by the VNFM in the embodiment shown in fig. 3. In addition, the memory 93 may also store various service data or user data, including status data of various application instances and services in the above method steps.
Optionally, the apparatus 70 may further comprise an output device 75 and an input device 77. An output device 75 and an input device 77 are connected to the processor 71. The output device 75 may be a display for displaying information, a power amplifier device for playing sound, or a printer, etc., and the output device 75 may further include an output controller for providing output to the display, the power amplifier device, or the printer. The input device 77 may be a device such as a mouse, keyboard, electronic stylus, or touch panel for user input of information, and the input device 77 may further include an output controller for receiving and processing input from the mouse, keyboard, electronic stylus, or touch panel, among other devices
Likewise, the device hardware diagram described above is also applicable to a CaaS management platform device, except that the software program stored in the memory 73 is executed by the processor 71 to implement the method steps performed by the CaaS management platform in the embodiment shown in fig. 3, and will not be repeated here.
In the above embodiments, the implementation may be wholly or partly realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Versatile Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above-mentioned embodiments are provided not to limit the present application, and any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (18)
1. A Virtual Network Function (VNF) service instantiation method is characterized by comprising the following steps:
a Virtual Network Function Manager (VNFM) receives a Virtual Network Function (VNF) instantiation request message and acquires container service capability information to be called when the VNF is instantiated;
the VNFM sends a container service discovery request to a container service (CaaS) management platform, and container service capability information is carried in a container service discovery request message;
receiving a container service discovery response message from a CaaS management platform by a VNFM, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information;
the VNFM creates a corresponding VNF instance and sends identification information of the container service instance to the VNF instance.
2. The method of claim 1, wherein the step of obtaining the VNFM the container service capability to be invoked by instantiating the VNF comprises:
and the VNFM acquires the corresponding VNFD in a database according to the VNF instantiation request message, and acquires the corresponding container service capability information in the VNFD.
3. The method of claim 1, wherein discovering, by the CaaS management platform, a container service instance according to the container service capability information comprises:
the CaaS management platform determines a corresponding container service descriptor file according to the container service capability information carried in the request message;
and the CaaS management platform searches or instantiates a container service instance according to the container service descriptor file.
4. The method of claim 3, wherein the CaaS management platform finding or instantiating a container service instance according to the container service descriptor file comprises:
if only one container service descriptor file is determined by the CaaS management platform and matches the requirement information of the container service capability carried in the request message, then:
the CaaS management platform searches whether a container service instance instantiated by using the container service descriptor file exists;
if the container service instance exists and the state of the container service instance is available, the CaaS management platform takes the container service instance as the discovered container service instance and returns the identifier of the container service instance to the VNFM in a response message; otherwise, the CaaS management platform uses the container service descriptor file to instantiate a new container service instance, and takes the newly instantiated container service instance as the discovered container service instance.
5. The method of claim 3, wherein the CaaS management platform finding or instantiating a container service instance according to the container service descriptor file comprises:
if a plurality of container service descriptor files are determined by the CaaS management platform and are matched with the requirement information of the container service capability carried in the request message, then:
the CaaS management platform sends the multiple container service descriptor files to the VNFM; the VNFM selects a container service descriptor file meeting VNFM calling container service requirements from the container service descriptor file selection strategies configured in advance locally, and then sends the selected container service descriptor file to the CaaS management platform;
the CaaS management platform searches whether a container service instance instantiated by using the container service descriptor file exists;
if the container service instance exists and the state of the container service instance is available, the CaaS management platform takes the container service instance as the discovered container service instance and returns the identifier of the container service instance to the VNFM in a response message; otherwise, the CaaS management platform uses the container service descriptor file to instantiate a new container service instance, and takes the newly instantiated container service instance as the discovered container service instance.
6. The method of claim 3, wherein the container service descriptor file selection policy comprises: the selection is made based on pricing ranges or business constraint terms of the container service instance created by the container service descriptor file.
7. The method of claim 1, wherein the container service capability information comprises: a capacity threshold for container service instance resiliency scaling, and/or affinity or anti-affinity rules between container services, and/or monitoring parameters supported by container services.
8. A virtual network function manager, VNFM, apparatus, comprising:
a receiving unit, configured to receive a virtual network function VNF instantiation request message;
the processing unit is used for acquiring the container service capability information needing to be called in the VNF instantiation;
the sending unit is used for sending a container service discovery request to the CaaS management platform, and the container service capability information is carried in a container service discovery request message;
the receiving unit is further configured to receive a container service discovery response message from the CaaS management platform, where the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information;
the processing unit is further configured to create a corresponding VNF instance according to the instantiation request message, and send identification information of the container service instance to the VNF instance.
9. The apparatus according to claim 8, wherein the processing unit obtaining the container service capability information to be invoked by instantiating the VNF specifically includes:
and the processing unit acquires the corresponding VNFD in a database according to the VNF instantiation request message and acquires the corresponding container service capability information in the VNFD.
10. The apparatus of claim 8 or 9, wherein the container service capability information comprises: a capacity threshold for container service instance resiliency scaling, and/or affinity or anti-affinity rules between container services, and/or monitoring parameters supported by container services.
11. A container as a service, CaaS, management platform apparatus, comprising:
a receiving unit, configured to receive a container service discovery request from a VNFM, where a container service discovery request message carries the container service capability information;
a processing unit for discovering a container service instance according to the container service capability information;
and the sending unit is used for sending a container service discovery response message to the VNFM, wherein the response message carries the identification information of the discovered container service instance.
12. The apparatus of claim 11, wherein the processing unit discovering the container service instance according to the container service capability information comprises:
the processing unit determines a corresponding container service descriptor file according to the container service capability information carried in the request message; and find or instantiate a container service instance based on the container service descriptor file.
13. A virtual network function VNF service instantiation system comprises a virtual network function manager VNFM and a container as a service CaaS management platform,
the VNFM is used for receiving a virtual network function manager VNFM receiving virtual network function VNF instantiation request message and acquiring container service capability information needing to be called by the VNF instantiation; the VNFM sends a container service discovery request to a CaaS management platform, and container service capability information is carried in a container service discovery request message; receiving a container service discovery response message from a CaaS management platform by a VNFM, wherein the response message carries identification information of a container service instance discovered by the CaaS management platform according to the container service capability information; the VNFM creates a corresponding VNF instance and sends the identification information of the container service instance to the VNF instance;
and the CaaS management platform is used for discovering the container service instance according to the container service capability information and sending a service discovery response message to the VNFM.
14. The system of claim 13, wherein the CaaS management platform discovering the container service instance according to the container service capability information comprises:
the CaaS management platform determines a corresponding container service descriptor file according to the container service capability information carried in the request message;
and the CaaS management platform searches or instantiates a container service instance according to the container service descriptor file.
15. The system according to claim 13 or 14, wherein the container service capability information comprises: a capacity threshold for container service instances to scale elastically, and/or affinity or anti-affinity rules between container services, and/or monitoring parameters supported by container services.
16. A virtual network function, VNF, service instantiation apparatus, the apparatus comprising a processor and a memory;
the memory is used for storing a program for executing the method of any one of claims 1 to 7 and storing data involved in implementing the method of any one of claims 1 to 7;
the processor is configured to execute programs stored in the memory.
17. A container as a service, CaaS, management platform apparatus, the apparatus comprising a processor and a memory;
the memory is used for storing a program for executing the method of any one of claims 1-7 and storing data involved in implementing the method of any one of claims 1-7;
the processor is configured to execute programs stored in the memory.
18. A computer readable storage medium having stored thereon executable program instructions for, when executed, performing the method of any of claims 1 to 7.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2018/110787 WO2020077585A1 (en) | 2018-10-18 | 2018-10-18 | Vnf service instantiation method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112889247A CN112889247A (en) | 2021-06-01 |
| CN112889247B true CN112889247B (en) | 2022-05-31 |
Family
ID=70284199
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201880098821.XA Active CN112889247B (en) | 2018-10-18 | 2018-10-18 | VNF service instantiation method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112889247B (en) |
| WO (1) | WO2020077585A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113746802B (en) * | 2021-08-02 | 2022-12-09 | 北京邮电大学 | Method in network function virtualization and VNF device with full storage of local state and remote state |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104253866A (en) * | 2014-09-20 | 2014-12-31 | 华为技术有限公司 | Software deployment method and system of virtual network function network element and relevant equipment |
| WO2015149600A1 (en) * | 2014-03-31 | 2015-10-08 | 华为技术有限公司 | Virtual network service deployment method and device |
| WO2016029821A1 (en) * | 2014-08-30 | 2016-03-03 | 华为技术有限公司 | Method and device for creating virtual network instance |
| CN105634782A (en) * | 2014-11-06 | 2016-06-01 | 华为技术有限公司 | Method of instancing virtual network function (VNF) and network element management device |
| WO2016095121A1 (en) * | 2014-12-17 | 2016-06-23 | 华为技术有限公司 | Method and system for automatically adjusting network service capability |
| CN106161173A (en) * | 2015-04-15 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of virtual network function that realizes disposes the method and device of specification configuration |
| WO2017041508A1 (en) * | 2015-09-09 | 2017-03-16 | 中兴通讯股份有限公司 | Method and device for re-instantiating virtual network function |
| WO2017107098A1 (en) * | 2015-12-23 | 2017-06-29 | 华为技术有限公司 | Parameter configuration method, device and system for virtualized network function (vnf) |
| WO2017166136A1 (en) * | 2016-03-30 | 2017-10-05 | 华为技术有限公司 | Vnf resource allocation method and device |
| EP3249528A1 (en) * | 2015-01-23 | 2017-11-29 | Nec Corporation | Method, device, and program for management and orchestration of network functions virtualization |
| CN107431637A (en) * | 2015-08-31 | 2017-12-01 | 华为技术有限公司 | The dispositions method and device of a kind of network service |
| EP3253005A1 (en) * | 2015-01-29 | 2017-12-06 | Nec Corporation | Data file registration management system, method, management device, and program |
| CN107533484A (en) * | 2015-05-07 | 2018-01-02 | 华为技术有限公司 | System and method for dynamically managing virtual network function descriptor |
| WO2018000197A1 (en) * | 2016-06-28 | 2018-01-04 | 华为技术有限公司 | Virtual network function resource management method and device |
| CN108011732A (en) * | 2016-11-02 | 2018-05-08 | 中国电信股份有限公司 | Method, controller and the system of configuration service resource |
| CN108282507A (en) * | 2017-01-06 | 2018-07-13 | 阿里巴巴集团控股有限公司 | The method, apparatus and electronic equipment using publication are carried out in CaaS environment |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10225335B2 (en) * | 2011-02-09 | 2019-03-05 | Cisco Technology, Inc. | Apparatus, systems and methods for container based service deployment |
| EP2940968A1 (en) * | 2014-04-30 | 2015-11-04 | Hewlett-Packard Development Company, L.P. | Network infrastructure management |
| US9436443B2 (en) * | 2014-08-28 | 2016-09-06 | At&T Intellectual Property I, L.P. | Software defined network controller |
| CN106301829B (en) * | 2015-05-21 | 2019-08-09 | 华为技术有限公司 | A kind of method and apparatus of network service dilatation |
| WO2016197346A1 (en) * | 2015-06-10 | 2016-12-15 | 华为技术有限公司 | Method and apparatus for managing life circle of virtualized network function |
| US10223140B2 (en) * | 2015-08-25 | 2019-03-05 | Futurewei Technologies, Inc. | System and method for network function virtualization resource management |
| US10048977B2 (en) * | 2015-12-22 | 2018-08-14 | Intel Corporation | Methods and apparatus for multi-stage VM virtual network function and virtual service function chain acceleration for NFV and needs-based hardware acceleration |
| CN107153565B (en) * | 2016-03-03 | 2020-06-16 | 华为技术有限公司 | Method for configuring resource and network equipment thereof |
| CN105955824B (en) * | 2016-04-21 | 2019-07-19 | 华为技术有限公司 | A kind of virtual resource configuration method and device |
| US10856183B2 (en) * | 2016-11-10 | 2020-12-01 | Huawei Technologies Co., Ltd. | Systems and methods for network slice service provisioning |
| US10716150B2 (en) * | 2016-12-19 | 2020-07-14 | At&T Intellectual Property I, L.P. | Method for mobile service chaining via hybrid network resources switching |
| WO2018174897A1 (en) * | 2017-03-24 | 2018-09-27 | Nokia Technologies Oy | Methods and apparatuses for multi-tiered virtualized network function scaling |
-
2018
- 2018-10-18 CN CN201880098821.XA patent/CN112889247B/en active Active
- 2018-10-18 WO PCT/CN2018/110787 patent/WO2020077585A1/en active Application Filing
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015149600A1 (en) * | 2014-03-31 | 2015-10-08 | 华为技术有限公司 | Virtual network service deployment method and device |
| WO2016029821A1 (en) * | 2014-08-30 | 2016-03-03 | 华为技术有限公司 | Method and device for creating virtual network instance |
| CN104253866A (en) * | 2014-09-20 | 2014-12-31 | 华为技术有限公司 | Software deployment method and system of virtual network function network element and relevant equipment |
| CN105634782A (en) * | 2014-11-06 | 2016-06-01 | 华为技术有限公司 | Method of instancing virtual network function (VNF) and network element management device |
| WO2016095121A1 (en) * | 2014-12-17 | 2016-06-23 | 华为技术有限公司 | Method and system for automatically adjusting network service capability |
| EP3249528A1 (en) * | 2015-01-23 | 2017-11-29 | Nec Corporation | Method, device, and program for management and orchestration of network functions virtualization |
| EP3253005A1 (en) * | 2015-01-29 | 2017-12-06 | Nec Corporation | Data file registration management system, method, management device, and program |
| CN106161173A (en) * | 2015-04-15 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of virtual network function that realizes disposes the method and device of specification configuration |
| CN107533484A (en) * | 2015-05-07 | 2018-01-02 | 华为技术有限公司 | System and method for dynamically managing virtual network function descriptor |
| CN107431637A (en) * | 2015-08-31 | 2017-12-01 | 华为技术有限公司 | The dispositions method and device of a kind of network service |
| WO2017041508A1 (en) * | 2015-09-09 | 2017-03-16 | 中兴通讯股份有限公司 | Method and device for re-instantiating virtual network function |
| WO2017107098A1 (en) * | 2015-12-23 | 2017-06-29 | 华为技术有限公司 | Parameter configuration method, device and system for virtualized network function (vnf) |
| WO2017166136A1 (en) * | 2016-03-30 | 2017-10-05 | 华为技术有限公司 | Vnf resource allocation method and device |
| WO2018000197A1 (en) * | 2016-06-28 | 2018-01-04 | 华为技术有限公司 | Virtual network function resource management method and device |
| CN108011732A (en) * | 2016-11-02 | 2018-05-08 | 中国电信股份有限公司 | Method, controller and the system of configuration service resource |
| CN108282507A (en) * | 2017-01-06 | 2018-07-13 | 阿里巴巴集团控股有限公司 | The method, apparatus and electronic equipment using publication are carried out in CaaS environment |
Non-Patent Citations (4)
| Title |
|---|
| "S5-165094 - pCR TS 28.525 Add Use Cases for NS update with add VL and VNF".《3GPP tsg_sa\WG5_TM》.2016, * |
| Efficient virtual evolved packet core deployment across multiple cloud domains;Miloud Bagaa;《2018 IEEE Wireless Communications and Networking Conference (WCNC)》;20180611;全文 * |
| S5-171844 "R14 CR TS 28.622 Add VNFInfo related attributes in IOC ManagedFunction";ZTE Corporation等;《3GPP tsg_sa\WG5_TM》;20170330;全文 * |
| 网络服务功能链拓扑设计及映射研究;吕晨;《中国优秀硕士学位论文全文数据库 (信息科技辑)》;20170228;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020077585A1 (en) | 2020-04-23 |
| CN112889247A (en) | 2021-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111385114B (en) | VNF service instantiation method and device | |
| US10701139B2 (en) | Life cycle management method and apparatus | |
| US9967136B2 (en) | System and method for policy-based smart placement for network function virtualization | |
| EP3291499B1 (en) | Method and apparatus for network service capacity expansion | |
| US10917294B2 (en) | Network function instance management method and related device | |
| WO2018024059A1 (en) | Method and device for service deployment in virtualized network | |
| CN105429776B (en) | Method and system for managing functions of virtual network | |
| US11611481B2 (en) | Policy management method and system, and apparatus | |
| EP3285439A1 (en) | Network service lifecycle management method and device | |
| CN109995552B (en) | VNF service instantiation method and device | |
| US11249788B2 (en) | Cloud management platform, and virtual machine management method and system | |
| EP3905588A1 (en) | Cloud platform deployment method and apparatus, server and storage medium | |
| WO2017185251A1 (en) | Vnfm determining method and network function virtualization orchestrator | |
| WO2020103925A1 (en) | Method and apparatus for deploying containerization virtualized network function | |
| US20230342183A1 (en) | Management method and apparatus for container cluster | |
| CN108667750B (en) | Virtual resource management method and device | |
| CN112889247B (en) | VNF service instantiation method and device | |
| CN112087311B (en) | Virtual network function VNF deployment method and device | |
| CN112015515A (en) | Virtual network function instantiation method and device | |
| CN113098705B (en) | Authorization method and device for life cycle management of network service | |
| CN115037788A (en) | Method and related device for creating Network Service (NS) | |
| CN116686264A (en) | Elastic expansion method and device | |
| CN111581203A (en) | Information processing method, device and 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 |