WO2021175105A1 - Connection method and apparatus, device, and storage medium - Google Patents

Abstract

A connection method and apparatus, a device, and a storage medium. Said method comprises: performing life cycle management on a multi-network plane information template of each container object in a container virtualized network function (VNF) (S110); the life cycle management of the multi-network plane information template comprises at least one of the following operations: a creation operation, an update operation, and a deletion operation of the multi-network plane information template of the container object.

Description

Connection method, device, equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 202010136184.X on March 2, 2020. The entire content of this application is incorporated into this application by reference.

Technical field

This application relates to communications, for example, to a connection method, device, device, and storage medium.

Background technique

In the wireless network system, it is necessary to support multi-network plane technology, that is, a telecommunication physical device or logical functional entity is connected to multiple networks at the same time. In short, there are multiple physical network interfaces or multiple virtual network interfaces on a host or logical functional entity. These interfaces are connected to different networks. These networks are generally independent of each other, such as management network and information. Make network, data network, billing network, etc. Since the telecommunications system has very high requirements for reliability, the system will configure multiple network planes to avoid the mutual influence of different network traffic and improve the robustness of the system.

In the Network Functions Virtualization (NFV) system, the NFV system supports the multi-network plane connection of virtual machines, but does not support the multi-network plane connection of containers. A virtual network function (Virtualized Network Function, VNF) constructed by virtual machine instantiation, the virtual machine in the VNF can be assigned multiple Internet Protocol (IP) addresses to access multiple network planes. However, for a VNF constructed using container instantiation, how the container objects in the VNF can access multiple network planes is an urgent problem to be solved.

Summary of the invention

The embodiments of the present application provide a connection method, device, device, and storage medium, which effectively realizes that each container object in the container VNF is supported to be connected to multiple network planes.

The embodiment of the present application provides a connection method applied to a first communication node, including:

The life cycle management of the multi-network plane information template of each container object in the container virtual network function VNF; the life-cycle management of the multi-network plane information template includes at least one of the following operations: the multi-network plane information of the container object Template creation, update, and delete operations.

The embodiment of the present application provides a connection method applied to a second communication node, including:

Receiving a life cycle management operation instruction of the container object sent by the first communication node, where the life cycle management operation instruction includes one of the following: a creation operation instruction, an update operation instruction, and a deletion operation instruction of the container object;

Receiving the multi-network plane information template and multi-network plane routing information of the container object sent by the first communication node;

Create, update or release a network topology connection between the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information.

The embodiment of the present application provides a connection device, which is applied to a first communication node, and includes:

The first management module is configured to perform life cycle management on the multi-network plane information template of each container object in the container virtual network function VNF; the life-cycle management of the multi-network plane information template includes at least one of the following operations: Create, update, and delete the multi-network plane information template of the container object.

The embodiment of the present application provides a connection device, which is applied to a second communication node, and includes:

The first receiving module is configured to receive the life cycle management operation instruction of the container object sent by the first communication node. The life cycle management operation instruction includes one of the following: a container object creation operation instruction, an update operation instruction, and a delete operation instruction ；

The second receiving module is configured to receive the multi-network plane information template and multi-network plane routing information of the container object sent by the first communication node;

The second management module is configured to create, update or release the network topology connection between the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information.

An embodiment of the present application provides a device, including: a memory, and one or more processors;

The memory is configured to store one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the foregoing embodiments.

An embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method described in any of the foregoing embodiments is implemented.

Description of the drawings

Figure 1 is an architecture diagram of an NFV system provided in related technologies;

Figure 2 is an architecture diagram of another NFV system provided in related technologies;

FIG. 3 is a flowchart of a connection method provided by an embodiment of the present application;

FIG. 4 is a flowchart of another connection method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a network topology of a container object provided by an embodiment of the present application;

FIG. 6 is a flowchart of creating a multi-network plane information template provided by an embodiment of the present application;

FIG. 7 is a flowchart of a network topology for creating a container object instance provided by an embodiment of the present application;

FIG. 8 is a flowchart of a network connection for updating container objects according to an embodiment of the present application;

FIG. 9 is a flowchart of releasing multiple network planes according to an embodiment of the present application;

FIG. 10 is a structural block diagram of a connection device provided by an embodiment of the present application;

FIG. 11 is a structural block diagram of another connection device provided by an embodiment of the present application;

Fig. 12 is a schematic structural diagram of a device provided by an embodiment of the present application.

Detailed ways

Hereinafter, the embodiments of the present application will be described with reference to the drawings.

In open source technologies, such as Kubernetes, its container objects (such as POD) can only allocate a single IP address to connect to a single network plane, and cannot directly support multi-network plane access. Many manufacturers have provided plug-in-based multi-network plane access solutions, but because the multi-network plane does not have a standardized unified data model, the NFV products of each manufacturer cannot be compatible and interconnected, and NFV products cannot be truly commercialized on a large scale.

Therefore, an enhanced NFV system is needed to enable it in container VNF lifecycle management operations, such as VNF instantiation construction and update operations, newly define and support a unified multi-network plane data template, and support each container object in the container VNF The technical solution of connecting multiple network planes makes it possible to enhance the support of container objects in the VNF to connect to multiple network planes in the NFV system.

NFV is a software processing technology that uses general-purpose hardware and virtualization technology to carry other functions, and aims to reduce the cost of expensive network equipment. Through software and hardware decoupling and functional abstraction, NFV makes network equipment functions no longer depend on dedicated hardware, resources can be fully and flexibly shared, rapid development and deployment of new services, and automatic deployment, elastic scaling, and fault isolation based on actual business needs And self-healing etc.

Figure 1 is an architecture diagram of an NFV system provided in related technologies. As shown in Figure 1, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) includes: business operation support system and management support platform (Operation-Support System/Business Support System, OSS/BSS), VNF, Network Function Virtualization Infrastructure (NFVI) and Network Function Virtualization Management and Orchestration System (NFV-Management and Orchestration, NFV-MANO). NFVI is responsible for comprehensively virtualizing hardware resources such as computing, storage, and networking, and mapping them into virtual resources; VNF uses software to implement various traditional physical network functions. VNF runs on NFVI and uses virtualized virtual resources after NFVI virtualization. resource. NFV-MANO is responsible for managing and orchestrating the relationship between VNF and NFVI and the connection relationship between VNF and/or between VNF and other physical network functions (Physical Network Functions, PNF).

NFV-MANO includes: Virtualized Infrastructure Manager (VIM), Virtualized Network Function Manager (VNFM), and Network Virtualization Function Orchestrator (NFVO). VIM is responsible for controlling and managing virtualized resources. In addition, VIM can also include physical infrastructure management (Physical Infrastructure Manager, PIM) functions, responsible for the management of bare metal resources, such as physical servers; VNFM is responsible for VNF life cycle management; NFVO is responsible for the orchestration and management of virtual infrastructure, and Network service (Network Service, NS) life cycle management.

The NFV system architecture diagram shown in Figure 1 only supports the virtual machine (Virtual Machine, VM) method to construct the network function virtualization technology of VNF. For the development of how to construct the VNF network function virtualization technology in the container method, it is necessary to compare the diagram 1 The NFV system architecture diagram is enhanced. Figure 2 is an architecture diagram of another NFV system provided in related technologies. As shown in Figure 2, Container Infrastructure Service Management (CISM) is added on the MANO side for container service management and orchestration, and Container Infrastructure Service Environment (CISE) is added on the NFVI side to provide containers. Operating environment, and provide computing, network, and storage resources needed to create containers. CISM and CISE adopt the Container Network Interface (CNI) interface protocol for connection and data exchange.

The basic function of the NFV system is to perform lifecycle management operations on NS, VNF, and Virtualized Network Function Component (VNFC), such as creation, shrinking, self-healing, and release. In the case of using virtual machines to manage the life cycle of NS and VNF, such as instantiation operation: BSS/OSS will issue Network Service Descriptor (NSD) and Virtual Network Function Descriptor (VNF Descriptor) to NFVO , VNFD) template, NFVO instantiates NS according to NSD, generates network service instance (Network Service Instance, NSI) and creates network link virtual link (Virtual Link, VL) between VNFs. The VNFM instantiates the VNF to generate a virtual network function instance (Virtualized Network Function Instance, VNFI)/Virtualized Network Function Component Instance (VNFCI), and network connections between VNFCIs.

In one embodiment, the present application provides a connection method to newly define and support a unified multi-network plane information template in the life cycle management operation of a container VNF to support multiple connections for each container object in the container VNF. Network plane.

In an implementation manner, FIG. 3 is a flowchart of a connection method provided by an embodiment of the present application. This embodiment is applied to the first communication node. Exemplarily, the first communication node may be CISM. As shown in Figure 3, this embodiment includes S110.

S110. Perform life cycle management on the multi-network plane information template of each container object in the container VNF.

In the embodiment, the life cycle management of the multi-network plane information template includes at least one of the following operations: creation operation, update operation, and deletion operation of the multi-network plane information template of the container object.

In the embodiment, after the CISM receives the multi-network plane attribute information of each container object in the container VNF, it constructs the multi-network plane information template according to the multi-network plane attribute information, and creates the multi-network information template according to different operation instructions. Update or delete operations. In the embodiment, the container objects in the container VNF are connected to multiple network planes, and each container object can perform data communication with multiple network planes at the same time.

In an embodiment, the VNFD serving the container VNF includes: multi-network plane attribute information of the container object, and multi-network plane routing information of the container object. In the embodiment, the VNFD of the container VNF refers to the VNFD template of the container VNF, that is, the VNFD template includes: the multi-network plane attribute information of the container object and the multi-network plane routing information of the container object.

In an embodiment, the multi-network plane attribute information of the container object includes at least one of the following: network names, identifiers (IDentifier, ID), network attributes of at least two logical network planes, network node attributes of the container object, and container objects Connection relationship with multiple logical network objects.

In an embodiment, the multi-network plane routing information of the container object includes at least one of the following: virtual network interface card (virtual NIC, vNIC)/network interface card (Network Interface Card, NIC) network node attributes of the physical network, container The network routing connection relationship between the multiple logical network objects connected by the object and the physical network object.

In an embodiment, before the life cycle management of the multi-network plane information template of each container object in the container VNF, the method further includes: receiving the multi-network plane attribute information of the container object sent by the third communication node, and the container object Multi-network plane routing information; receiving the life cycle management operation request of each container object in the container VNF sent by the third communication node.

In an embodiment, the third communication node may be a VNFM.

In an embodiment, performing life cycle management on the multi-network plane information template of each container object in the container VNF includes: creating or updating the multi-network plane information template of the container object according to the multi-network plane attribute information of the container object; The second communication node creates, updates, or deletes the container object instance; and sends the multi-network plane information template and the multi-network plane routing information of the container object to the second communication node.

Fig. 4 is a flowchart of another connection method provided by an embodiment of the present application. This embodiment is applied to the second communication node. Exemplarily, the second communication node may be a container infrastructure service (Container Infrastructure Service, CIS). As shown in Figure 4, this embodiment includes: S210-S230.

S210: Receive a life cycle management operation instruction of the container object sent by the first communication node.

In the embodiment, the life cycle management operation instruction includes one of the following: a creation operation instruction, an update operation instruction, and a deletion operation instruction of the container object.

S220: Receive the multi-network plane information template of the container object and the multi-network plane routing information of the container object sent by the first communication node.

S230: Create, update or release the container object instance and the network topology connection of the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object.

In an embodiment, the creation, update or release of the container object instance and the network topology connection of the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object includes: management according to the life cycle of the container object Operation instructions create, update or delete a container object instance; create, update or release the network topology connection of the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object.

In an embodiment, after creating, updating or releasing the container object instance and the network topology of the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object, the method further includes: connecting the container object instance The configuration information of the multi-network plane network topology is sent to the container object instance to which it belongs; the container object instance is used to report the configuration information of the multi-network plane topology to the target application.

In an embodiment, the connection method applied to the second communication node further includes: sending feedback information of successful creation, update, or deletion to the first communication node. In an embodiment, after the multi-network plane network topology of the container object instance is successfully created, updated, or deleted, feedback information of successful creation, update, or deletion can be sent to CISM through CIS, and feedback to VNFM through CISM, and then Feed back to NFVO through VNFM until it is fed back to OSS/BSS.

In the embodiment, the container-supported NFV enhancement system is adopted. When the container VNF is operated by operating the container object to perform life cycle management operations, such as VNF instantiation, VNF instance update, etc., it is first necessary to perform operations on the container VNF that serves the container. The VNFD is enhanced and extended, and the multi-network plane attribute information of the container object (that is, the definition of multiple logical network objects, and the definition of how the container object and multiple logical network objects are connected), and the multi-network plane routing of the container object are added to the VNFD Information (the multi-network plane routing information of a container object refers to the information describing the network routing connection relationship between multiple logical network objects connecting the container object and one or more physical network objects), and then CISM constructs a multi-layer service for the container object Network plane information template.

The CISM sends the constructed multi-network plane information template of the container object and the multi-network plane routing information of the container object to the CIS through the CNI interface protocol.

In the process of instantiating the container object, CIS constructs the multi-network plane network topology of the container object instance (container object and multiple logical networks) according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object. The virtual or physical network connection of the object, the virtual or physical network connection of the logical network object and the physical network object).

After the container object is instantiated, the CIS sends the multi-network plane network topology configuration information of each container object to the corresponding container object instance, and the container object instance passes it to the upper application.

In the embodiment, the VNFD serving the container object needs to be expanded to support the multi-network plane access of the container object: the multi-network plane attribute information of the container object needs to be added in the VNFD, including but not limited to multiple logical network objects The network name, ID, network attributes (for example, Internet Protocol Version 4 (Internet Protocol Version 4, IPv4)/Internet Protocol Version 6 (Internet Protocol Version 6, IPv6) address and port, etc.), the attributes of the network node that the container object is connected to (For example, IPv4/IPv6 address and port, etc.), the connection relationship between the container object and multiple logical network objects (for example, the eth0 of the container object is connected to the Msc management network, and eth1 is connected to the sig signaling network), and the container object is connected Logical network plug-in information (for example, Flannel plug-in, calico plug-in, canel plug-in, kube-router, etc.) and so on. In addition, the multi-network plane routing information of the container object needs to be expanded in the VNFD, including but not limited to the vNIC/NIC network node attributes of the physical network (for example, IPv4/IPv6 address and port, etc.), the network of logical network objects and physical network objects Routing connection relationship, etc. (for example, the sig network of container object 1 is connected to NIC/vNIC1 of the physical network through network routing, and the Msc network is connected to NIC/vNIC2 of the physical network through network routing). FIG. 5 is a schematic diagram of a network topology of a container object provided by an embodiment of the present application. As shown in Figure 5, the container cluster node (cluster node) can be regarded as an example of CIS.

In the embodiment, the VNFM needs to parse the VNFD, extract the multi-network plane attribute information of each container object described in the VNFD, and send the multi-network plane attribute information of the container object to the CISM. At the same time, the VNFM also takes out the multi-network plane routing information of the container object in the VNFD, that is, the information describing the network connection relationship between the multi-network plane and the physical network, and sends it to the CISM at the same time.

In the embodiment, CISM constructs the multi-network plane information template of the container object according to the multi-network plane attribute information of the container object, which contains the information of the multiple logical networks connected by the container object, the information of the network node of the container object, and the multiple logic The network connection relationship between the network and the container object, the plug-in information supporting multiple network planes, etc.

In the embodiment, the CISM uses the CNI interface protocol to combine the multi-network plane information template and the multi-network plane routing information of the container object (that is, information describing the network connection relationship between multiple logical network objects and one or more physical network objects) , Sent to CIS.

When CIS creates a container object instance, it creates the network node, node, and multiple network nodes of the container object instance according to the multi-network plane information template of the container object and the network connection relationship between the multiple logical network objects of the container object and the physical network object. The network topology of the logical network object, the network topology of the logical network object and the physical network object, finally generates a multi-network plane network topology structure of the container object instance, and realizes that each container object instance in the VNF is connected to the multi-network plane.

In the embodiment, after the instantiation of the VNF is completed, the CIS sends the multi-network plane network topology configuration information of each container object instance in the VNF instance to the corresponding container object instance, including the IPv4/IPv6 address of the container object node And ports, the network routing information from the container object to the multi-network plane, the IP address of the multi-network plane node, the NIC/vNIC IPv4/IPv6 address and port of the physical network, the network routing information from the multi-network plane to the physical network plane, etc. The container object reports the network topology configuration information of the multi-network plane to the upper-layer application, and the upper-layer application realizes the data transmission monitoring of the container object instance according to the network topology configuration of the container object.

In an implementation manner, FIG. 6 is a flowchart of creating a multi-network plane information template provided by an embodiment of the present application. In the embodiment, the creation process of the multi-network plane information template of each container object in the VNF is described. The VNFD template contains the multi-network plane attribute information of the container object and the multi-network plane routing information of the container object. When instantiating the container VNF, CISM creates a multi-network plane information template of the VNF container object according to the multi-network plane attribute information of the container object in the VNFD, and sends it to the CIS through the CNI interface protocol.

As shown in Figure 6, this embodiment includes: S310-S380.

S310. Arrange a VNFD template serving the container object.

In the embodiment, for the VNFD template required by the container VNF, the multi-network plane attribute information of the container object is added to the VNFD template. In addition, the multi-network plane routing information of the container object needs to be added to the VNFD template.

Add the multi-network plane attribute information of the container object to the VNFD template, including but not limited to the network name, ID, network node attributes of multiple logical network objects (for example, IPv4/IPv6 address and port, etc.), and the network node attributes of the container object (For example, IPv4/v6 address and port, etc.), the connection relationship between the container object and multiple logical network objects (for example, eth0 of the container object is connected to the Msc management network, and eth1 is connected to the signaling (sig) network), and the container object Connected logical network plug-in information (such as flannel plug-in, calico plug-in, canel plug-in, kube-router...), etc.

Add the multi-network plane routing information of the container object to the VNFD template, including but not limited to the connection relationship between multiple logical network objects connected to the container object and the physical network object (for example, the sig network of container object 1 is connected to the NIC of the physical network) vNIC1, the Msc network is connected to the physical network's NIC/vNIC2), the physical network's vNIC/NIC network node attributes (IPv4/IPv6 address and port, etc.), etc.

Exemplarily, when creating a container object in a certain VNF and multiple logical network objects (such as signaling (sig) plane, management (management) plane, data (data) plane, charging (charge) network plane) topology , It is necessary to arrange the attributes of the multiple logical network objects in the VNFD, the network node attributes of the container object, the network connection relationship between the container object and multiple logical network objects, the physical network node attributes, and the network routing connection between the logical network and the physical network relation. In this way, when the container object is instantiated, the connection of the container object to multiple logical network objects and the connection of multiple logical network objects to the physical network object can be created.

S320. Upload the arranged NSD and the VNFD template serving the container VNF to the NFVO.

S330. The NFVO delivers each VNFD template associated with the container VNF to the VNFM.

S340. Initiate an NS/VNF instantiation request to the NFVO.

In the embodiment, the NSD ID is carried in the NS instantiation request. According to the different types of VNFD template IDs contained in the NSD, the NFVO notifies the VNFM to initiate the instantiation request of all container VNFs that make up the NS (taking the instantiation request as an example, it can be the life cycle management operation of other VNFs, such as VNF instantiation) , Resurgence, Self-healing, Termination, etc.). In an embodiment, the OSS may also independently initiate a container VNF instantiation request to the NFVO, carrying the ID of the VNFD template.

S350. The NFVO sends a VNF instantiation request to the VNFM.

In an embodiment, NFVO notifies the VNFM to initiate a VNF instantiation request (taking an instantiation request as an example, which can be other VNF lifecycle management operations, such as VNF instantiation, resizing, self-healing, termination, etc.);

S360. Parse the VNFD template, and extract the network attribute information of the container object.

In the embodiment, in the life cycle management operation of the container VNF, such as instantiating the container VNF, the VNFM needs to instantiate all the container objects contained therein. When the container VNF is instantiated, the CISM is responsible for the instantiation of the container object. Therefore, the VNFM needs to parse the VNFD template serving the container object, and retrieve the network attribute information of the container object in the VNFD template, including multi-network plane attributes. Information, multi-network plane routing information.

S370. Send the network attribute information of the container object to the CISM.

In the embodiment, the network attribute information of each container object in the container VNF is sent to the CISM.

S380. Construct a multi-network plane information template of the container object.

In the embodiment, in the container VNF life cycle management process, the CISM is responsible for the life cycle management operations of the container objects, such as instantiation operations. When the container object is instantiated, when the CISM receives the network attribute information of the container object sent by the VNFM, it creates a container object multi-network plane information template according to the relevant NFV rules or policies and according to the container object’s multi-network plane attribute information. save.

In the embodiment, the content in the multi-network plane information template is not limited to the following parameters and information: the attributes of the container object, including the name and ID of the container object, the network attributes of the external node (IPv4/IPv6 address attribute), and the VNF to which the container object belongs Name and ID, etc.; the attribute information of multiple logical network objects connected by the container object: not limited to the number, name, ID, type of multiple logical networks, and the network attributes of the connected nodes (IPv4/IPv6 address attributes); container objects and multiple The connection relationship of each logical network object (network performance constraint); the network performance constraint of the associated logical network object; the input parameters of the associated logical network object, including quality of service (Qos), plug-in information (input and output requirements) , Including injection file format and parameters)

Through this embodiment, during the instantiation process of NS or VNF, CISM can construct a multi-network plane information template according to the multi-network plane attribute information of the container object, which is used for the network of the container object in the subsequent container object instantiation process. Topology creation.

In an implementation manner, FIG. 7 is a flowchart of a network topology for creating a container object instance provided by an embodiment of the present application. In the embodiment, the process of constructing the network topology of the container object instance is described. In the embodiment, the CIS receives the container object instantiation request sent by the CISM, and creates the container object of the VNF in the container operating environment of the node according to the multi-network plane information template of the container object of the VNF. The container object instance allocates computing resources and storage resources for the container object instance, and constructs a network topology for the container object instance.

After the container object is instantiated and its network topology is constructed, CIS sends the network configuration information of each container object to the corresponding container object, and the application (APP) running on the container object can pass the specific network address And routing to monitor the data transmission path.

As shown in Figure 7, this embodiment includes: S410-S470.

S410: Send an instantiation request of the container object to the CISM.

During the instantiation of the container VNF, the VNFM informs the CISM to instantiate each container object in the VNF.

S420. Request the CIS to create a container object instance.

In the embodiment, the CISM sends the computing resources and storage resource requirements required to create the container object instance inside the VNF to the CIS, and requests the CIS to create each container object instance that composes the VNF. At the same time, CISM passes the multi-network plane information template of the container object and the multi-network plane routing information of the container object to the CIS through the CNI interface protocol, requesting the CIS to construct a network connection for the container object instance.

S430. Create a container object instance, and allocate computing resources and storage resources.

In the embodiment, the CIS creates each container object instance in the container VNF instance in the container operating environment, and allocates required computing resources and storage resources.

S440. Construct a network topology of each container object.

In the embodiment, CIS assigns an IP address and port to the externally connected network node of each container object instance according to the multi-network plane information template sent by CISM and the multi-network plane routing information of the container object, and assigns an IP address and port to each container object instance Construct a network topology, that is, a network connection topology of container object instances, multiple logical network objects, and multiple virtual/physical network objects.

CIS saves the network topology configuration information of each container object instance in the container VNF instance, including the external IP address and port assigned by the external connection node of the container object instance, the IP address and port of multiple logical network object nodes, and virtual/physical networks The IP address and port of the object, as well as the network connection routing information of the three.

S450. Send to the CISM that the container object instance has been created, and the instantiation is complete.

In the embodiment, after the computing resources and storage resources of each container object instance in the VNF are successfully allocated, and the network topology is successfully created, the CIS notifies the CISM of the completion of the instantiation of the VNF content container object. In the notification message, CIS notifies CISM that the network topology of each container object in the VNF has been constructed.

S460. Perform service configuration on the VNF instance, and complete the VNF instantiation.

In the embodiment, the VNFM continues the subsequent operations of VNF instantiation, and configures the service parameters of the created VNF instance to complete the instantiation operation of the container VNF. Later, the element management (EM) performs the operation on the container VNF instance. Business configuration and management.

S460. Send the network topology configuration information of each container object instance to the container object instance.

In the embodiment, after the container VNF is instantiated, the CIS sends the network topology configuration information of each container object instance to the relevant container object instance. The container object instance can further report the configuration to the application for monitoring the transmission path.

Through this embodiment, during the instantiation process of the container VNF, the CISM notifies the CIS to instantiate each container object in the VNF. CIS creates each container object instance in the container operating environment, and constructs the network topology of each container object instance according to the container object's multi-network plane information template and the container object's multi-network plane routing information, and completes the instantiation of the container object. After the container object is instantiated, CISM notifies the VNFM, and the VNFM completes the final VNF instantiation operation.

In an implementation manner, FIG. 8 is a flowchart for updating a network connection of a container object provided by an embodiment of the present application. This embodiment describes the update process of updating the container object multi-network plane information template.

In the embodiment, when the multi-network plane attribute information of the container object in the VNFD template, or the network routing attribute information of the container object is changed, OSS/NFVO initiates a VNF instance change request to update the network topology of the container object instance. CISM updates the multi-network plane information template of the container object according to the changed multi-network plane attribute information of the container object. CISM notifies CIS to update the network topology of the container object instance. CIS rebuilds the network topology of the container object instance in the VNF instance according to the updated container object multi-network plane information template or the updated container object multi-network plane routing information to complete the container. The object's network connection update operation.

As shown in Figure 8, this embodiment includes: S510-S5120.

S510. Update the network attribute information in the VNFD template serving the container object.

In the embodiment, updating the network attribute information of the container object in the VNFD template may be updating the multi-network plane attribute information of the container object, or updating the multi-network plane routing information of the container object, or both.

Exemplarily, updating the multi-network plane attribute information can be to change the connection relationship between the logical network object and the container object, or to increase or decrease the logical network object; for example, to update the multi-network plane routing information of the container object, the logical network object can be changed. The network connection relationship of virtual/physical network objects.

S520. Upload the updated VNFD template to NFVO.

In the embodiment, the OSS/BSS initiates a VNF instance update operation, notifies that the network attribute information of the container object in the VNFD template has changed, and uploads the updated VNFD template serving the container VNF to the NFVO.

S530. Initiate a VNF instance update.

In the embodiment, the NFVO initiates a VNF instance update to the VNFM, and at the same time, the NFVO delivers the updated VNFD template to the VNFM.

S540: Send an update request of the container object instance.

In the embodiment, after the VNFM receives the VNF instance update request, it initiates an update request of the container object instance to the CISM, and requests to update the network topology of the container object during the VNF instance update process.

The VNFM parses the changed VNFD template, extracts the updated network attribute information of the container object in the VNF, including the multi-network plane attribute information of the container object, and the multi-network plane routing information of the container object, and updates the container object of the VNF The network attribute information is sent to the CISM, and the CISM is notified to update the container object instance of the container object.

S550. Update the multi-network plane information template of the container object.

In the embodiment, the CISM updates the container object multi-network plane information template based on the updated container object multi-network plane information template and saves the updated container object multi-network plane information template. The content update in the multi-network plane information template is not limited to some or all of the following parameters and information: the attributes of the container object, including the container object name, ID, network attributes of external nodes (IPv4/IPv6 address attributes), and the name of the VNF to which the container object belongs And ID, etc.; the attribute information of multiple logical network objects connected by the container object: not limited to the number, name, ID, type of multiple logical networks, and the network attributes of the connected node (IPv4/IPv6 address attribute); the container object and multiple The connection relationship of logical network objects (network performance constraints); the network performance constraints of the associated logical network objects; the input parameters of the associated logical network objects, including Qos, plug-in information (input and output requirements, including injection file format and parameters).

S560. Send the updated multi-network plane information template to the CIS.

In the embodiment, the CISM transmits the updated multi-network plane information template of the container object or the updated multi-network plane routing information of the container object to the CIS through the CNI interface protocol.

S570. Update the network topology of the container object instance.

In the embodiment, CIS updates the network topology of the container object instance according to the updated container object multi-network plane information template sent by CISM, or/and the updated container object multi-network plane routing information, which is not limited to container objects and logical network objects. , The IP address and port of the virtual/physical network object, and the network connection route of the three.

For the newly added network plane, the CIS needs to construct the network topology connection relationship between the relevant container object node and the newly added logical network object according to the description of the information model.

For the reduced network plane, the CIS needs to delete the network topology connection relationship between the relevant container object node and the existing logical network object according to the description of the information model.

CIS re-saves the updated network topology configuration information of the container object, including the external IP address assigned by the external connection node of the container object instance, the IP address of the logical network object connection node, the IP address of the virtual/physical network object connection node, and the three Network routing information.

S580. The CIS notifies the CISM that the network topology of the container object instance has been updated.

S590. The CISM notifies the VNFM that the update of the container object instance is complete.

In the embodiment, after the network topology update of the container object instance is completed, the CISM notifies the VNFM that the container object has completed the instance update.

S5100, the VNFM notifies the NFVO of the completion of the update of the VNF instance.

In the embodiment, after all the container objects that need to be updated in the container VNF complete the update of the container object instance, the VNFM notifies NFVO that the update of its VNF instance is complete, and the network topology of all the container object instances that need to be updated in the VNF instance is updated.

S5110. The NFVO notifies the OSS/BSS of the completion of the update of the VNF instance.

In the embodiment, after the NFVO receives the container VNF instance update completion message notified by the VNFM, the NFVO notifies the OSS/BSS that the network topology of the relevant VNF instance has been changed.

S5120. The CIS sends the updated configuration information of the multi-network plane network topology to the container object instance.

In the embodiment, the CIS resends the updated multi-network plane network topology configuration information of each container object instance to the relevant container object instance. The container object instance can report the configuration to the application for monitoring the transmission path.

Through this embodiment, when the network topology of the container object needs to be updated, the network attribute information of the container object in the VNFD needs to be updated, and the VNFM informs the CISM to update the container object instance that needs to be updated. The CISM updates the multi-network plane information template of the container object, and sends the updated multi-network plane information template of the container object to the CIS through the CNI interface protocol, requesting to update the network topology of the container object. In the container operating environment, CIS updates the network topology of the container object according to the updated container object multi-network plane information template and the updated container object multi-network plane routing information, and completes the update operation of the network topology of the container object.

In an implementation manner, FIG. 9 is a flowchart of releasing multiple network planes according to an embodiment of the present application. This embodiment describes that in the VNF instance release operation, the multi-network plane network resources occupied by the container VNF are released at the same time.

As shown in Figure 9, this embodiment includes: S610-S690.

S610: Initiate a release request of the VNF instance.

In the embodiment, the OSS/BSS initiates a release request of the VNF instance to the NFVO, and releases the multi-network plane resources occupied by each container object instance in the VNF instance.

S620. The NFVO notifies the VNFM of the release of the VNF instance.

S630. The VNFM notifies the CISM to release the resources of the container object instance.

In the embodiment, the VNFM notifies the CISM to release the network resources of each container object instance in the container VNF instance, as well as the computing resources and storage resources allocated to each container object.

S640. The CISM notifies the CIS to release the resources of the container object instance.

In the embodiment, the CISM notifies the CIS to release the resources allocated by each container object instance in the VNF instance. The CISM initiates the release of the multi-network plane network resources of each container object instance of the VNF to the CIS through the CNI interface protocol, and at the same time notifies the CIS through other interfaces to release the computing resources and storage resources of each container object instance.

S650, CIS releases the network resources, computing resources, and storage resources of the container object instance.

In the embodiment, CIS releases the IP address allocated by each container object in the VNF instance, releases the network resources of each logical network object, deletes the network connection between the container object instance and each logical network object, and the logical network object and virtual /The network connection of the physical network object, and finally delete the network topology of each container object instance of the VNF.

CIS deletes the network topology configuration information of each container object instance stored in the local VNF instance; CIS releases the computing resources and storage resources allocated by each container object in the VNF instance.

S660. The CIS notifies the CISM that the resources of the VNF instance have been released.

In the embodiment, CIS informs CISM that the computing and storage resources of each container object instance of the VNF instance have been released, and informs CISM through the CNI interface that the network resources of each container object instance in the VNF instance have been released, and CISM receives CIS After knowing that the computing resources, storage resources, and network resources of the container object instance inside the VNF have been released, CISM deletes the created container object. CISM deletes the locally stored multi-network plane information template of each container object of the VNF.

S670. The CISM notifies the VNFM that the resources of each container object instance have been released.

In the embodiment, the CISM notifies the VNFM that the computing resources, storage resources, and network resources of each container object of the VNF have been released.

S680: The VNFM notifies the NFVO that the resources of the VNF instance have been released and deletes the VF instance.

In the embodiment, when all the container object instance resources of the VNF instance are released, the VNFM deletes the container VNF instance and informs the NFVO that the VNF instance has been released.

S690. The NFVO notifies the OSS/BSS that the VNF instance has been deleted and the multi-network plane resources have been released.

In the embodiment, the NFVO notifies the OSS/BSS that the VNF instance has been deleted, and the multi-network plane resources of each container object in the VNF instance have been released.

Through this embodiment, in the case of deleting a VNF instance, during the VNF instance deletion process, the CISM needs to notify the CIS to release the resources of each container object instance in the VNF instance, including computing resources, storage resources, and network resources. After CIS releases the resource of the container object, it notifies the CISM, and the CISM notifies the VNFM. After the VNFM confirms that all the container object instances in the VNF instance have been released, the VNFM completes the deletion of the VNF instance.

In an embodiment, FIG. 10 is a structural block diagram of a connection device provided by an embodiment of the present application. As shown in FIG. 10, exemplarily, the first communication node may be CISM. As shown in FIG. 10, this embodiment includes: a first management module 710.

The first management module 710 is configured to perform life cycle management on the multi-network plane information template of each container object in the container virtual network function VNF; the life-cycle management of the multi-network plane information template includes at least one of the following operations: Create, update, and delete multiple network plane information templates.

The connection device provided in this embodiment is configured to implement the connection method applied to the first communication node in the embodiment shown in FIG. 4, and the implementation principle of the connection device provided in this embodiment is similar to the embodiment shown in FIG. .

In an embodiment, the virtual network function descriptor VNFD serving the container VNF includes: multi-network plane attribute information of the container object and multi-network plane routing information of the container object.

In an embodiment, the multi-network plane attribute information of the container object includes at least one of the following: network names, identification IDs, and network attributes of at least two logical network planes, the network node attributes of the container object, and the container object is connected to multiple The connection relationship of logical network objects.

In an embodiment, the multi-network plane routing information of the container object includes at least one of the following: virtual network interface card vNIC/network interface card NIC network node attributes of the physical network, multiple logical network objects connected by the container object to the physical network The network routing connection relationship of the object.

In an embodiment, the connection device applied to the first communication node further includes: a third receiving module configured to receive the third receiving module before performing life cycle management on the multi-network plane information template of each container object in the container VNF The multi-network plane attribute information of the container object and the multi-network plane routing information of the container object sent by the communication node; the fourth receiving module is configured to receive the life cycle management operation request of each container object in the container VNF sent by the third communication node .

In an embodiment, the first management module includes: a first management unit configured to create or update a multi-network plane information template of the container object according to the multi-network plane attribute information of the container object; the second management unit is configured to notify The second communication node creates, updates or deletes the container object instance; the sending unit is configured to send the multi-network plane information template and the multi-network plane routing information of the container object to the second communication node.

Fig. 11 is a structural block diagram of another connection device provided by an embodiment of the present application. This embodiment is applied to the second communication node. Exemplarily, the second communication node may be a CIS. As shown in FIG. 11, this embodiment includes: a first receiving module 810, a second receiving module 820, and a second management module 830.

The first receiving module 810 is configured to receive the life cycle management operation instruction of the container object sent by the first communication node. The life cycle management operation instruction includes one of the following: a creation operation instruction, an update operation instruction, and a deletion operation instruction of the container object.

The second receiving module 820 is configured to receive the multi-network plane information template and the multi-network plane routing information of the container object sent by the first communication node.

The second management module 830 is configured to create, update or release the network topology connection of the container object instance and the multi-network plane according to the multi-network plane information template and the multi-network plane routing information of the container object.

The connection device provided in this embodiment is configured to implement the connection method applied to the second communication node in the embodiment shown in FIG. 5. The implementation principle of the connection device provided in this embodiment is similar to the embodiment shown in FIG. .

In one embodiment, the second management module 830 includes: a third management unit configured to create, update, or delete container object instances according to the life cycle management operation instructions of the container object; the fourth management unit is configured to The multi-network plane information template and the multi-network plane routing information create, update or release the container object instance and the network topology connection of the multi-network plane.

In an embodiment, the connection device applied to the second communication node further includes: a first sending module configured to create, update, or release a container object instance according to the multi-network plane information template and multi-network plane routing information of the container object After connecting with the network topology of the multi-network plane, the configuration information of the multi-network plane network topology of the container object instance is sent to the container object instance to which it belongs; the container object instance is used to report the configuration information of the multi-network plane topology to the target application.

In an embodiment, the connection device applied to the second communication node further includes: a second sending module configured to send feedback information of successful creation, update, or deletion to the first communication node.

Fig. 12 is a schematic structural diagram of a device provided by an embodiment of the present application. As shown in FIG. 12, the device provided by the present application includes: a processor 910, a memory 920, and a communication module 930. The number of processors 910 in the device may be one or more, and one processor 910 is taken as an example in FIG. 12. The number of memories 920 in the device may be one or more, and one memory 920 is taken as an example in FIG. 12. The processor 910, the memory 920, and the communication module 930 of the device may be connected through a bus or in other ways. In FIG. 12, the connection through a bus is taken as an example. In this embodiment, the device is the first communication node.

As a computer-readable storage medium, the memory 920 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the device of any embodiment of the present application (for example, the first management module in the connecting device). ). The memory 920 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like. In addition, the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the memory 920 may further include a memory remotely provided with respect to the processor 910, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The communication module 930 is configured to perform a communication connection between the first communication node and the second communication node for data communication and signal communication.

The above-provided device can be configured to execute the connection method applied to the first communication node provided by any of the above-mentioned embodiments, and has corresponding functions.

In the case that the device is the second communication node, the device provided above can be configured to execute the connection method applied to the second communication node provided by any of the foregoing embodiments, and have corresponding functions.

An embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to execute a connection method applied to a first communication node. The method includes: virtualizing a container The multi-network plane information template of each container object in the network function VNF performs life cycle management; the life-cycle management of the multi-network plane information template includes at least one of the following operations: creation of the multi-network plane information template of the container object Operation, update operation, delete operation.

An embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to execute a connection method applied to a second communication node. The method includes: receiving a first communication node. The life cycle management operation instruction of the container object sent by the communication node, the life cycle management operation instruction includes one of the following: a creation operation instruction, an update operation instruction, and a deletion operation instruction of the container object; The multi-network plane information template and multi-network plane routing information of the container object; create, update or release the network topology connection of the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information .

Those skilled in the art should understand that the term user equipment encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.

In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.

The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.

Claims (14)

1. A connection method, applied to a first communication node, includes:

   The life cycle management of the multi-network plane information template of each container object in the container virtual network function VNF; the life-cycle management of the multi-network plane information template includes at least one of the following operations: the multi-network plane information of the container object Template creation, update, and delete operations.
2. The method according to claim 1, wherein the virtual network function descriptor VNFD serving the container VNF comprises: multi-network plane attribute information of the container object, and multi-network plane routing information of the container object.
3. The method according to claim 2, wherein the multi-network plane attribute information of the container object includes at least one of the following: network names, identification IDs, network attributes of at least two logical network planes, and network node attributes of the container object , The connection relationship between the container object and multiple logical network objects.
4. The method according to claim 2, wherein the multi-network plane routing information of the container object includes at least one of the following: virtual network interface card vNIC/network interface card NIC network node attributes of the physical network, and the container object is connected The network routing connection relationship between multiple logical network objects and physical network objects.
5. The method according to claim 1, before said performing life cycle management on the multi-network plane information template of the container object in the container VNF, the method further comprises:

   Receiving the multi-network plane attribute information of the container object and the multi-network plane routing information of the container object sent by the third communication node;

   Receiving the life cycle management operation request of each container object in the container VNF sent by the third communication node.
6. The method according to claim 5, wherein said performing life cycle management on the multi-network plane information template of the container object in the container VNF comprises:

   Create or update the multi-network plane information template of the container object according to the multi-network plane attribute information of the container object;

   Notifying the second communication node to create, update or delete the container object instance;

   Sending the multi-network plane information template of the container object and the multi-network plane routing information of the container object to the second communication node.
7. A connection method, applied to a second communication node, includes:

   Receiving a life cycle management operation instruction of the container object sent by the first communication node, where the life cycle management operation instruction includes one of the following: a creation operation instruction, an update operation instruction, and a deletion operation instruction of the container object;

   Receiving the multi-network plane information template of the container object and the multi-network plane routing information of the container object sent by the first communication node;

   According to the multi-network plane information template of the container object and the multi-network plane routing information of the container object, create, update or release the container object instance and the network topology connection of the multi-network plane.
8. 8. The method according to claim 7, wherein said creating, updating or releasing the network topology of the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object Connection, including:

   Create, update or delete the container object instance according to the life cycle management operation instruction of the container object;

   Create, update or release the network topology connection between the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object.
9. The method according to claim 7, wherein the container object instance and the multi-network plane network are created, updated, or released according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object. After the topological connection, it also includes:

   The configuration information of the multi-network plane network topology of the container object instance is sent to the container object instance to which the configuration information belongs; the container object instance is used to report the configuration information of the multi-network plane topology to a target application.
10. The method according to claim 7, further comprising:

    Send feedback information of successful creation, update, or deletion to the first communication node.
11. A connection device applied to a first communication node, including:

    The first management module is configured to perform life cycle management on the multi-network plane information template of each container object in the container virtual network function VNF; the life-cycle management of the multi-network plane information template includes at least one of the following operations: Create, update, and delete the multi-network plane information template of the container object.
12. A connection device applied to a second communication node, including:

    The first receiving module is configured to receive the life cycle management operation instruction of the container object sent by the first communication node, and the life cycle management operation instruction includes one of the following: the creation operation instruction, the update operation instruction, and the deletion of the container object Operating instructions

    The second receiving module is configured to receive the multi-network plane information template of the container object and the multi-network plane routing information of the container object sent by the first communication node;

    The second management module is configured to create, update or release the network topology connection between the container object instance and the multi-network plane according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object.
13. A device, including: a memory, and at least one processor;

    The memory is configured to store at least one program;

    When the at least one program is executed by the at least one processor, the at least one processor implements the method according to any one of claims 1-10.
14. A storage medium storing a computer program, which implements the method of any one of claims 1-10 when the computer program is executed by a processor.

Images