CN113342456A

CN113342456A - Connection method, device, equipment and storage medium

Info

Publication number: CN113342456A
Application number: CN202010136184.XA
Authority: CN
Inventors: 谢宝国; 朱进磊; 巨满昌
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-03-02
Filing date: 2020-03-02
Publication date: 2021-09-03
Also published as: WO2021175105A1

Abstract

The application provides a connection method, a connection device, equipment and a storage medium. The method comprises the following steps: performing life cycle management on a multi-network plane information template of each container object in a container Virtual Network Function (VNF); the life cycle management of the multi-network plane information template at least comprises the following operations: and the creation operation, the updating operation and the deleting operation of the multi-network plane information template of the container object.

Description

Connection method, device, equipment and storage medium

Technical Field

The present application relates to communications, and in particular, to a connection method, apparatus, device, and storage medium.

Background

In the existing wireless network system, there is a need to support multiple network plane technologies, that is, one telecom physical device or logical function entity is connected to multiple networks at the same time. In short, a host or a logical functional entity has a plurality of physical or virtual network interfaces, which are respectively connected to different networks, and the networks are generally independent of each other, such as a management network, a signaling network, a data network, a charging network, and the like. Because the telecommunication system has very high requirement on reliability, the system can avoid the mutual influence of different network flows by configuring multiple network planes, and the robustness of the system is improved.

In an existing Network Function Virtualization (NFV) system, the NFV system supports multiple Network plane connections of virtual machines, but does not support multiple Network plane connections of containers. A Virtual Network Function (VNF) constructed by instantiating a virtual machine, where the virtual machine in the VNF can allocate multiple Internet Protocol (IP) addresses and access multiple Network planes. However, in a VNF constructed by using container instantiation, how container objects in the VNF access to multiple network planes is an urgent problem to be solved.

Disclosure of Invention

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

The embodiment of the application provides a connection method, which is applied to a first communication node and comprises the following steps:

performing life cycle management on a multi-network plane information template of each container object in a container Virtual Network Function (VNF); the life cycle management of the multi-network plane information template at least comprises the following operations: and the creation operation, the updating operation and the deleting operation of the multi-network plane information template of the container object.

The embodiment of the application provides a connection method, which is applied to a second communication node and comprises the following steps:

receiving a life cycle management operation instruction of a container object sent by a first communication node, wherein the life cycle management operation instruction comprises one of the following items: creating an operation instruction, updating the operation instruction and deleting the operation instruction of the container object;

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

and creating, updating or releasing 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.

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 a multi-network plane information template of each container object in a container Virtual Network Function (VNF); the life cycle management of the multi-network plane information template at least comprises the following operations: and the creation operation, the updating operation and the deleting operation of 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:

a first receiving module, configured to receive a lifecycle management operation instruction of a container object sent by a first communication node, where the lifecycle management operation instruction includes one of: creating an operation instruction, updating the operation instruction and deleting the operation instruction of the container object;

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

and 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 an apparatus, including: a memory, and one or more processors;

the memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any of the embodiments described above.

The embodiment of the application provides a storage medium, wherein a computer program is stored in the storage medium, and when being executed by a processor, the computer program realizes the method of any one of the above embodiments.

Drawings

FIG. 1 is an architecture diagram of an NFV system provided in the prior art;

FIG. 2 is an architecture diagram of another NFV system provided in the prior art;

fig. 3 is a flowchart of a connection method provided in an embodiment of the present application;

fig. 4 is a flowchart of another connection method provided in the embodiments of the present application;

fig. 5 is a schematic network topology diagram of a container object according to an embodiment of the present application;

fig. 6 is a flowchart of creating a multi-network plane information template according to an embodiment of the present application;

FIG. 7 is a flowchart of a network topology for creating container object instances according to an embodiment of the present application;

FIG. 8 is a flow chart illustrating a network connection for updating a container object according to an embodiment of the present disclosure;

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

fig. 10 is a block diagram of a connection device according to an embodiment of the present disclosure;

FIG. 11 is a block diagram of another connection device according to an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of an apparatus provided in an embodiment of the present application.

Detailed Description

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

In the existing open source technology, for example, Kubernetes, a container object (such as POD) thereof can only allocate a single IP address to connect to a single network plane, and cannot directly support multi-network plane access. At present, a plurality of manufacturers provide a multi-network plane access solution based on plug-ins, but because the multi-network plane has no standardized unified data model, NFV products of each manufacturer cannot be mutually compatible and interconnected, and the NFV products cannot be really commercialized in a large scale.

Therefore, it is necessary to enhance the existing NFV system, so that in the lifecycle management operation of the container VNF, such as VNF instantiation building and updating operation, a unified multi-network-plane data template is newly defined and supported, and a technical scheme that each container object in the container VNF is connected to a multi-network plane is supported, so that the container object in the VNF is enhanced and supported to be connected to the multi-network plane in the NFV system.

NFV is a software processing technology that carries other functions by using general-purpose hardware and virtualization technology, aiming to reduce the cost of expensive equipment of the network. The NFV decouples software and hardware and abstracts functions, so that the functions of network equipment do not depend on special hardware any more, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements.

Fig. 1 is an architecture diagram of an NFV system provided in the prior art. As shown in fig. 1, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) includes: service Operation Support systems and Management Support platforms (OSS/BSS), VNFs, Network Function Virtualization Infrastructure (NFVI), and Network function Virtualization Management and Orchestration systems (NFV-Management and architecture, NFV-MANO). The NFVI is responsible for comprehensively virtualizing hardware resources such as calculation, storage and network and mapping the hardware resources into virtual resources; the VNF implements various conventional physical network functions using software, runs on the NFVI, and uses virtual resources virtualized by the NFVI. The NFV-MANO is responsible for managing and orchestrating the relationships between VNFs and NFVI and the connectivity between VNFs and/or with other Physical Network Functions (PNFs).

The NFV-MANO includes a Virtualized Infrastructure Manager (VIM), a Virtual Network Function Manager (VNFM), and a Network Virtualization Function Orchestrator (NFVO). The VIM is responsible for controlling and managing the virtualized resources. In addition, the VIM may also include Physical Infrastructure Management (PIM) functionality, responsible for managing bare machine resources, such as Physical servers; the VNFM is responsible for lifecycle management of the VNF; NFVO is responsible for orchestration and management of virtual infrastructure, as well as lifecycle management for Network Services (NS).

The NFV system architecture diagram shown in fig. 1 only supports a network function virtualization technology for constructing a VNF in a Virtual Machine (VM) manner, and the NFV system architecture diagram of fig. 1 needs to be enhanced for a network function virtualization technology that is developing how to construct a VNF in a container manner. Fig. 2 is an architecture diagram of another NFV system provided in the prior art. As shown in fig. 2, a Container Infrastructure Service Management (CISM) is added on the MANO side for Container Service Management and organization, and a Container Service Environment (CISE) is added on the NFVI side for providing a Container operation Environment and providing computing, network, and storage resources required for creating a Container. The CISM and the CISE adopt a Container Network Interface (CNI) Interface protocol for connection and data interaction.

The basic functions of the NFV system are: and performing life cycle management operations such as creation, elastic shrinkage, self-healing, release and the like on the NS, the VNF and the VNFC. In the case of performing lifecycle management on the NS and the VNF in a virtual machine manner, as an example operation: the BSS/OSS issues an NSD and a Virtual Network function Descriptor (VNF Descriptor, VNFD) template to the NFVO, and the NFVO instantiates the NS according to the NSD, generates a Network Service Instance (NSI), and creates a Virtual Link (VL) of a Network Link between VNFs. The VNFM instantiates the VNF to generate the VNFI/VNFCI and the network connection between the VNFCIs.

In an embodiment, the present application provides a connection method, so that in a lifecycle management operation of a container VNF, a unified multi-network-plane information template is newly added and defined and supported to support connection of each container object in the container VNF to a multi-network plane.

In one implementation, fig. 3 is a flowchart of a connection method provided in an embodiment of the present application. The present embodiment is applied to the first communication node. Illustratively, the first communication node may be a CISM. As shown in fig. 3, the present embodiment includes S110.

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

In an embodiment, the lifecycle management of the multi-network plane information template comprises at least one of: creating operation, updating operation and deleting operation of the multi-network plane information template of the container object.

In the embodiment, after receiving the multi-network plane attribute information of each container object in the container VNF, the CISM constructs a multi-network plane information template according to the multi-network plane attribute information, and performs operations such as creating, updating, or deleting on the multi-network plane information template according to different operation instructions. In an embodiment, the container objects in the container VNF are connected to multiple network planes, just that each container object can be in data communication with multiple network planes simultaneously.

In an embodiment, the VNFD serving the container VNF comprises: multi-network plane attribute information for the container object, and multi-network plane routing information for the container object. In an embodiment, the VNFD of the container VNF refers to a VNFD template of the container VNF, i.e. in the VNFD template comprises: multi-network plane attribute information for the container object, and multi-network plane routing information for the container object.

In one embodiment, the multi-network plane attribute information of the container object includes at least one of: network names, IDs, network attributes of at least two logical network planes, network node attributes of container objects, connection relationships of container objects to a plurality of logical network objects.

In one embodiment, the multi-network plane routing information of the container object includes at least one of: a virtual NIC (virtual NIC)/NIC (Network Interface Card, NIC) Network node attribute of the physical Network, and a Network routing connection relationship from a plurality of logical Network objects connected to the container object to the physical Network object.

In an embodiment, before performing lifecycle management on the multi-network plane information template of each container object in the container VNF, the method further includes:

receiving multi-network plane attribute information of a container object and multi-network plane routing information of the container object, which are sent by a third communication node;

and receiving a 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, the lifecycle management for the multi-network plane information template of each container object in the container VNF includes:

creating or updating a 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 a container object instance;

and sending 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 in the embodiment of the present application. The present embodiment is applied to the second communication node. Exemplarily, the second communication node may be a CIS. As shown in fig. 4, the present embodiment includes: S210-S230.

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

In an embodiment, the lifecycle management operation instruction comprises one of: and creating operation instructions, updating operation instructions and deleting operation instructions of the container object.

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

And S230, creating, updating or releasing the network topology connection between 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.

In one embodiment, creating, updating, or releasing a network topology connection of a container object instance to a multi-network plane based on a multi-network plane information template and multi-network plane routing information of the container object comprises:

creating, updating or deleting container object instances according to the life cycle management operation instructions of the container objects;

and creating, updating or releasing 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.

In one embodiment, after creating, updating or releasing 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 method further includes:

sending the configuration information of the multi-network plane network topology structure of the container object instance to which the container object instance belongs; the container object instance is used for reporting configuration information of the multi-network plane topology structure to the target application.

In an embodiment, the connection method applied to the second communication node further includes:

and sending feedback information of successful creation, updating and 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 and deletion can be sent to the CISM through the CIS, and fed back to the VNFM through the CISM, and then fed back to the NFVO through the VNFM until the feedback is fed back to the OSS/BSS.

In an embodiment, with the NFV enhancement system supporting a container, when performing lifecycle management operations on a container VNF by operating a container object, such as VNF instantiation, VNF instance update, and other operations, it is first required to perform enhancement extension on a VNFD serving the container VNF, add multi-network plane attribute information of the container object (i.e., definitions of multiple logical network objects and definitions of how the container object is connected to the multiple logical network objects) and multi-network plane routing information of the container object (the multi-network plane routing information of the container object refers to information describing a network routing connection relationship between the multiple logical network objects connecting the container object and one or more physical network objects) in the VNFD, and then construct a multi-network plane information template serving the container object by using a CISM.

And 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 a CNI interface protocol.

In the instantiation process of the container object, the CIS constructs a multi-network plane network topology structure of the container object instance (the container object is connected with virtual or physical networks of a plurality of logical network objects, and the logical network objects are connected with the virtual or physical networks of the physical network objects) according to a multi-network plane information template of the container object and multi-network plane routing information of the container object.

After the container object instantiation is completed, 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 transmits the multi-network plane network topology configuration information to the upper layer application.

In an embodiment, the VNFD serving the container object needs to be extended to support multiple network plane access of the container object: in the VNFD, multi-network plane attribute information of a container object needs to be added, including but not limited to network names, IDs, network attributes (e.g., IPv4/v6 addresses and ports, etc.) of multiple logical network objects, network node attributes (e.g., IPv4/v6 addresses and ports, etc.) of external connections of the container object, connection relationships of the container object to the multiple logical network objects (e.g., eth0 of the container object is connected to the Msc management network, eth1 is connected to the sig signaling network), logical network plug-in information (e.g., Flannel plug-in, calico plug-in, canel plug-in, kube-router, etc.) of the container object connection, and so on. In addition, in the VNFD, it is necessary to extend multi-network plane routing information of the container object, including but not limited to vNIC/NIC network node attributes of the physical network (e.g., IPv4/v6 addresses and ports, etc.), network routing connection relationship between the logical network object and the physical network object, etc. (e.g., sig network of the container object 1 is connected to NIC/vNIC1 of the physical network through network routing, and Msc network is connected to NIC/vNIC2 of the physical network through network routing). Fig. 5 is a schematic network topology diagram of a container object according to an embodiment of the present application. As shown in fig. 5, a container cluster node (cluster node) may be regarded as an example of the CIS.

In an embodiment, the VNFM needs to analyze 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. And simultaneously, the VNFM also takes out multi-network plane routing information of the container object in the VNFD, namely information describing the network connection relation between the multi-network plane and the physical network, and simultaneously sends the information to the CISM.

In the embodiment, the CISM constructs a multi-network plane information template of the container object according to the multi-network plane attribute information of the container object, where the multi-network plane information template includes information of multiple logical networks connected to the container object, information of network nodes of the container object, network connection relationships between the multiple logical networks and the container object, plug-in information supporting multiple network planes, and the like.

In an embodiment, the CISM sends the multi-network plane information template and the multi-network plane routing information of the container object (i.e., information describing the network connection relationship between the plurality of logical network objects and the one or more physical network objects) to the CIS through the CNI interface protocol.

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

In the embodiment, after the VNF instantiation is completed, the CIS sends the multi-network-plane network topology configuration information to which each container object instance in the VNF instance belongs, to the corresponding container object instance, where the configuration information includes an IPv4/v6 address and port of the container object node, network routing information from the container object to the multi-network plane, an IP address of the multi-network-plane node, an NIC/vNIC IPv4/v6 address and port of a physical network, network routing information from the multi-network plane to the physical network plane, and the like. The container object reports the multi-network plane network topology configuration information to the upper layer application, and the upper layer application realizes data transmission monitoring of the container object instance according to the network topology configuration of the container object.

In one implementation, fig. 6 is a flowchart for creating a multi-network plane information template according to an embodiment of the present application. In an embodiment, a process of creating a multi-network plane information template for each container object in a VNF is described. The VNFD template includes multi-network plane attribute information of the container object and multi-network plane routing information of the container object. When the container VNF is instantiated, the 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 the multi-network plane information template to the CIS through a CNI interface protocol.

As shown in fig. 6, the present embodiment includes: S310-S380.

S310, arranging a VNFD template serving the container object.

In an embodiment, a VNFD template required by a container VNF adds multi-network plane attribute information of a container object to an existing VNFD template. In addition, in the existing VNFD template, multi-network plane routing information of the container object needs to be expanded and added.

Adding multi-network plane attribute information of the container object in the VNFD template, including but not limited to network names, IDs, network node attributes (e.g., IPv4/v6 addresses and ports, etc.) of a plurality of logical network objects, network node attributes (e.g., IPv4/v6 addresses and ports, etc.) of the container object, connection relationships of the container object to the plurality of logical network objects (e.g., eth0 of the container object is connected to the Msc management network, eth1 is connected to the signaling (sig) network), logical network plug-in information of the container object connection (e.g., flannel plug-in, calico plug-in, canel plug-in, kube-router).

The VNFD template is added with multi-network plane routing information of the container object, including but not limited to connection relationships between multiple logical network objects connected by the container object and physical network objects (e.g., the sig network of the container object 1 is connected to NIC/vNIC1 of the physical network, the Msc network is connected to NIC/vNIC2 of the physical network), and vNIC/NIC network node attributes (IPv4/v6 addresses and ports, etc.) of the physical network.

Illustratively, in creating a topology of a container object and a plurality of logical network objects (e.g., a signaling (sig) plane, a management (management) plane, a data (data) plane, and a charging (charge) network plane) in a certain VNF, attributes of the plurality of logical network objects, network node attributes of the container object, network connection relationships of the container object and the plurality of logical network objects, network routing connection relationships of the logical network and a physical network are programmed in the VNFD. This may create connections of the container object to multiple logical network objects, as well as connections of multiple logical network objects to physical network objects, when the container object is instantiated.

S320, upload orchestrated NSDs and VNFD templates serving container VNFs to NFVO.

S330, the NFVO issues each VNFD template associated with the container VNF to the VNFM.

S340, initiating an NS/VNF instantiation request to the NFVO.

In an embodiment, the NSD ID is carried in the NS instantiation request. The NFVO notifies the VNFM of an instantiation request to initiate all container VNFs constituting the NS according to different types of VNFD template IDs included in the NSD (taking the instantiation request as an example, the instantiation request may be a lifecycle management operation of other VNFs, such as VNF instantiation, snapping, self-healing, termination, and the like). In an embodiment, the OSS may also initiate an instantiation request of the container VNF to the NFVO separately, carrying the ID of the VNFD template.

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

In an embodiment, the NFVO notifies the VNFM to initiate a VNF instantiation request (taking the instantiation request as an example, it may be a lifecycle management operation of other VNFs, such as VNF instantiation, snapping, self-healing, termination, etc.);

and S360, analyzing the VNFD template and taking out the network attribute information of the container object.

In an embodiment, in a lifecycle management operation of a container VNF, such as an instantiation operation on the container VNF, the VNFM needs to instantiate all container objects contained therein. When the container VNF is instantiated, the container object is instantiated by the CISM, so the VNFM needs to parse the VNFD template serving the container object, and extract the network attribute information of the container object in the VNFD template, where the network attribute information includes multi-network plane attribute information and multi-network plane routing information.

And S370, sending the multi-network attribute information of the container object to the CISM.

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

And S380, constructing a multi-network plane information template of the container object.

In an embodiment, in the container VNF lifecycle management process, the CISM is responsible for lifecycle management operations of the container object, such as instantiation operations. When the instantiation operation of the container object is carried out, after the CISM receives the network attribute information of the container object sent by the VNFM, a multi-network plane information template of the container object is created and stored according to the multi-network plane attribute information of the container object according to the related rules or strategies of the NFV.

In an 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 comprise the name and ID of the container object, the network attribute (IPv4/V6 address attribute) of an external node, the name and ID of a VNF (virtual network function) to which the container object belongs, and the like; attribute information of a plurality of logical network objects to which the container object is connected: not limited to the number, name, ID, type of the plurality of logical networks, network attributes of the connecting nodes (IPv4/V6 address attributes); the container object's connection relationships to multiple logical network objects (constraints on network performance); network performance constraints associated with the logical network objects; associated logical network object input parameters, including Qos, plug-in information (input and output requirements, including injection file format and parameters)

By the embodiment, in the instantiation process of the NS or VNF, the CISM may construct a multi-network plane information template according to the multi-network plane attribute information of the container object, so as to be used for network topology creation of the container object in the subsequent container object instantiation process.

In one implementation, fig. 7 is a flowchart of a network topology for creating a container object instance according to an embodiment of the present application. In an embodiment, a process of constructing a container object instance network topology is described. In the embodiment, after receiving a container object instantiation command sent by the CISM and a container object multi-network plane information template of the VNF, the CIS creates each container object instance in a container runtime environment, allocates computing resources and storage resources to the container object instance, and constructs a network topology for the container object instance.

After the container object instantiation and the network topology construction are completed, the CIS sends the network configuration information of each container object to each container object, and the APP running on the container object can monitor the data transmission path through a specific network address and a specific route.

As shown in fig. 7, the present embodiment includes: S410-S470.

S410, sending an instantiation request of the container object to the CISM.

During instantiation of the container VNF, the VNFM informs the CISM to perform instantiation operation on each container object in the VNF.

And S420, requesting the CIS to create a container object instance.

In an embodiment, the CISM sends the computing resource and storage resource requirements needed for creating container object instances inside the VNF to the CIS, and requests the CIS to create each container object instance constituting the VNF. And simultaneously, the CISM transmits 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 a CNI interface protocol, and requests the CIS to construct network connection for the container object instance.

S430, creating a container object instance, and allocating computing resources and storage resources.

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

S440, constructing a network topology of each container object.

In the embodiment, the CIS allocates an IP address and a port to an external connection network node of each container object instance according to a multi-network plane information template sent by the CISM and multi-network plane routing information of the container object, and constructs a network topology for each container object instance, that is, a network connection topology of the container object instance, a plurality of logical network objects, and a plurality of virtual/physical network objects.

The CIS stores network topology configuration information of each container object instance in the container VNF instance, including an external IP address and port allocated to an external connection node of the container object instance, IP addresses and ports of a plurality of logical network object nodes, IP addresses and ports of virtual/physical network objects, and network connection routing information of the three.

S450, sending the created container object instance to the CISM, and completing instantiation.

In an embodiment, after successful allocation of computing resources, storage resources, and successful creation of its network topology for each container object instance within the VNF, the CIS notifies the CISM that container object instantiation is complete within the VNF. In the notification message, the CIS notifies the CISM that the network topology of each container object within the VNF has been built.

And S460, carrying out service configuration on the VNF instance to complete the instantiation of the VNF.

In the embodiment, the VNFM continues subsequent operations of VNF instantiation, performs service parameter configuration on the created VNF instance, completes instantiation operations of the container VNF, and performs service configuration and management on the container VNF instance by the EM at a later stage.

And S460, sending the network topology configuration information of each container object instance to the container object instance.

In an 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 may further report the configuration to an application for monitoring the transmission path.

With this embodiment, in the instantiation process of the container VNF, the CISM notifies the CIS to instantiate each container object within the VNF. The CIS creates each container object instance in a container runtime environment, and constructs a network topology of each container object instance according to a multi-network plane information template of the container object and multi-network plane routing information of the container object, thereby completing instantiation of the container object. And after the instantiation of the container object is completed, the CISM informs the VNFM, and the VNFM completes the final VNF instantiation operation.

In one implementation, fig. 8 is a flowchart of a network connection for updating a container object according to an embodiment of the present application. The present embodiment describes an update process for updating a container object multi-network plane information template.

In an 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, the OSS/NFVO initiates a VNF instance change request to update the network topology of the container object instance. And the 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. And the CIS informs the CIS to update the network topology of the container object instance, and the CIS reconstructs 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 finish the network connection updating operation of the container object.

As shown in fig. 8, the present embodiment includes: S510-S5120.

And S510, updating network attribute information in the VNFD template serving the container object.

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

Illustratively, the updating of the multi-network plane attribute information may be changing the connection relationship between the logical network object and the container object, or adding or reducing the logical network object; and if the multi-network plane routing information of the container object is updated, the network connection relation of the logic network object and the virtual/physical network object can be changed.

And S520, uploading the updated VNFD template to the NFVO.

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

And S530, initiating VNF instance updating.

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

And S540, sending an updating request of the container object instance.

In an embodiment, after the VNFM receives the VNF instance update request, an update request of the container object instance is initiated to the CISM, and the network topology of the container object is requested to be updated in the VNF instance update process.

The VNFM analyzes the changed VNFD template, extracts updated container object network attribute information in the VNF, including multi-network plane attribute information of the container object and multi-network plane routing information of the container object, and sends the updated container object network attribute information of the VNF to the CISM, and notifies the CISM to perform a container object instance update operation on the container object.

And S550, updating the multi-network plane information template of the container object.

In the embodiment, the CISM updates and stores the container object multi-network plane information template based on the updated container object multi-network plane information. 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 comprise the name and ID of the container object, the network attribute (IPv4/V6 address attribute) of an external node, the name and ID of a VNF (virtual network function) to which the container object belongs, and the like; attribute information of a plurality of logical network objects to which the container object is connected: not limited to the number, name, ID, type of the plurality of logical networks, network attributes of the connecting nodes (IPv4/V6 address attributes); the container object's connection relationships to multiple logical network objects (constraints on network performance); network performance constraints associated with the logical network objects; associated logical network object input parameters include Qos, plug-in information (input and output requirements, including injection file format and parameters).

And S560, sending the updated multi-network plane information template to the CIS.

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

And S570, updating the network topology of the container object instance.

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

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

For reduced network planes, the CIS needs to delete the network topology connection relationship of the relevant container object node and the existing logical network object as described by the information model.

The CIS restores the updated network topology configuration information of the container object, including the external IP address assigned to 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 network routing information of the three.

S580, the CIS informs the CISM that the network topology of the container object instance is updated.

S590, the CISM informs the VNFM that the update of the container object instance is completed.

In an 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, VNFM notifies NFVO of VNF instance update completion.

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

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

In an embodiment, after the NFVO receives the VNFM notification container VNF instance update completion message, 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 an embodiment, the CIS resends the updated multi-network plane network topology configuration information for each container object instance to the relevant container object instance. The container object instance may further report the configuration to an application for monitoring the transmission path.

By the 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 notifies the CISM to update the container object instance needing to be updated in a VNF instance updating manner. The CISM updates the multi-network plane information template of the container object, issues the multi-network plane information template to the CIS through a CNI interface protocol, and requests to update the network topology of the container object. And the CIS updates the network topology structure of the container object according to the updated multi-network-plane information template of the container object and the updated multi-network-plane routing information of the container object in the container operation environment, so as to complete the updating operation of the network topology of the container object.

In one implementation, 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 simultaneously.

As shown in fig. 9, the present embodiment includes: S610-S690.

And S610, initiating a release request of the VNF instance.

In an 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 informs the CISM of releasing the resources of the container object instance.

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

S640, the CIS is informed by the CISM to release the resources of the container object instance.

In an embodiment, the CISM notifies the CIS to release the resources allocated by each container object instance within the VNF instance. And the CISM initiates the release of the multi-network plane network resources of each container object instance of the VNF to the CIS through a CNI interface protocol, and simultaneously informs the CIS to release the computing resources and the storage resources of each container object instance through other interfaces.

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

In an embodiment, the CIS releases the IP address assigned by each container object within the VNF instance, releases the network resources of each logical network object, deletes the network connection of the container object instance with each logical network object, and the network connection of the logical network object with the virtual/physical network object, finally deletes the network topology of each container object instance of the VNF.

The CIS deletes the network topology configuration information of each container object instance stored in the local VNF instance; the 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 an embodiment, the CIS notifies the CISM that the computation and storage resources of each container object instance of the VNF instance are released, and notifies the CISM that the network resources of each container object instance in the VNF instance are released through a CNI interface, the CISM receives a notification message of the CIS, learns that the computation resources, the storage resources, and the network resources of the container object instance inside the VNF are all released, and deletes the created container object. And the CISM deletes the multi-network plane information template of each container object of the VNF, which is locally stored.

S670, the CISM informs the VNFM that the resources of each container object instance are released.

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

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

In an embodiment, when the release of all container object instance resources of the VNF instance is completed, the VNFM deletes the container VNF instance and notifies the NFVO that the VNF instance has been released.

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

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

With the embodiment, for the case of deleting the VNF instance, in the VNF instance deletion process, the CISM needs to notify the CIS to release resources, including computing resources, storage resources, and network resources, of each container object instance in the VNF instance. And the CIS notifies the CISM after releasing the resources of the container object, the CISM notifies the VNFM, and the VNFM completes the deletion of the VNF instance after confirming that all container object instances in the VNF instance are released.

In an embodiment, fig. 10 is a block diagram of a connection device according to an embodiment of the present disclosure. As shown in fig. 10, the first communication node may illustratively be a CISM. As shown in fig. 10, the present embodiment includes: a first management module 710.

A first management module 710 configured to perform lifecycle management on a multi-network plane information template of each container object in a container virtual network function VNF; the life cycle management of the multi-network plane information template at least comprises the following operations: creating operation, updating operation and deleting operation of the multi-network plane information template of the container object.

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 and the technical effect of the connection device provided in this embodiment are similar, and are not described herein again.

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

In one embodiment, the multi-network plane attribute information of the container object includes at least one of: network names, identification IDs, network attributes of at least two logical network planes, network node attributes of container objects, and connection relationships of container objects to a plurality of logical network objects.

In one embodiment, the multi-network plane routing information of the container object includes at least one of: the virtual network card vNIC/network card NIC network node attribute of the physical network, the network routing connection relation from a plurality of logical network objects connected with the container object to the physical network object.

In one embodiment, the connection device applied to the first communication node further includes:

a third receiving module, configured to receive, before performing lifecycle management on the multi-network-plane information template of each container object in the container VNF, multi-network-plane attribute information of the container object and multi-network-plane routing information of the container object, which are sent by a third communication node;

a fourth receiving module, configured to receive the lifecycle management operation request of each container object in the container VNF sent by the third communication node.

In one embodiment, a first management module includes:

the first management unit is 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;

a second management unit configured to notify the second communication node of creation, update, or deletion of a container object instance;

a sending unit 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 block diagram of another connection device according to an embodiment of the present disclosure. The present embodiment is applied to the second communication node. Exemplarily, the second communication node may be a CIS. As shown in fig. 11, the present embodiment includes: a first receiving module 810, a second receiving module 820, and a second managing module 830.

A first receiving module 810 configured to receive a lifecycle management operation instruction of a container object sent by a first communication node, where the lifecycle management operation instruction includes one of: creating an operation instruction, updating the operation instruction and deleting the operation instruction of the container object;

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

and the second management module 830 is configured to create, update or release a 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, and the implementation principle and the technical effect of the connection device provided in this embodiment are similar, and are not described herein again.

In one embodiment, the second management module 830 includes:

the third management unit is configured to create, update or delete the container object instance according to the life cycle management operation instruction of the container object;

and the fourth management unit 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 and the multi-network plane routing information of the container object.

In one embodiment, the connection device applied to the second communication node further includes:

the first sending module is configured to send the configuration information of the multi-network plane network topology structure of the container object instance to the container object instance after the container object instance is created, updated or released according to the multi-network plane information template and the multi-network plane routing information of the container object; the container object instance is used for reporting configuration information of the multi-network plane topology structure to the target application.

and the second sending module is configured to send feedback information of successful creation, update and deletion to the first communication node.

Fig. 12 is a schematic structural diagram of an apparatus provided in an embodiment of the present application. As shown in fig. 12, the present application provides an apparatus comprising: a processor 910, a memory 920, and a communication module 930. The number of the 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 the 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 by a bus or other means, and fig. 12 illustrates the connection by a bus as an example. In this embodiment, the apparatus is a first communication node.

The memory 920, as a computer-readable storage medium, may be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the apparatuses of any embodiment of the present application (e.g., the first management module in the connection device). The memory 920 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the device, and the like. Further, the memory 920 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 920 may further include memory located remotely from the processor 910, which may be connected to devices over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

A communication module 930 configured to perform communication connection between the first communication node and the second communication node to perform data communication and signal communication.

The apparatus provided above may be configured to perform the connection method applied to the first communication node provided in any of the embodiments above, with corresponding functions and effects.

In the case where the device is a second communication node, the device provided above may be configured to execute the connection method applied to the second communication node provided in any of the embodiments above, and has corresponding functions and effects.

Embodiments of the present application also provide a storage medium containing computer-executable instructions which, when executed by a computer processor, perform a connectivity method applied to a first communication node, the method comprising: performing life cycle management on a multi-network plane information template of each container object in a container Virtual Network Function (VNF); the life cycle management of the multi-network plane information template at least comprises the following operations: and the creation operation, the updating operation and the deleting operation of the multi-network plane information template of the container object.

Embodiments of the present application also provide a storage medium containing computer-executable instructions which, when executed by a computer processor, perform a connectivity method applied to a second communication node, the method comprising: receiving a life cycle management operation instruction of a container object sent by a first communication node, wherein the life cycle management operation instruction comprises one of the following items: creating an operation instruction, updating the operation instruction and deleting the operation instruction of the container object; receiving a multi-network plane information template and multi-network plane routing information of the container object sent by a first communication node; and creating, updating or releasing 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.

It will be clear to a person skilled in the art that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers or vehicle-mounted mobile stations.

In general, the various embodiments of the application may be implemented in hardware or special purpose 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 which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.

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

Any logic flow block diagrams in the figures of this 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 may be stored on a memory. The Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.

Claims

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

2. The method of claim 1, wherein serving a Virtual Network Function Descriptor (VNFD) of 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 of claim 2, wherein the multi-network plane property information of the container object comprises at least one of: network names, identification IDs, network attributes of at least two logical network planes, network node attributes of container objects, and connection relationships of container objects to a plurality of logical network objects.

4. The method of claim 2, wherein the multi-network plane routing information of the container object comprises at least one of: the virtual network card vNIC/network card NIC network node attribute of the physical network, the network routing connection relation from a plurality of logical network objects connected with the container object to the physical network object.

5. The method of claim 1, prior to the lifecycle management for the multi-network plane information template for each container object in the container VNF, further comprising:

6. The method of claim 5, wherein the lifecycle management for the multi-network plane information template of each container object in the container VNF comprises:

7. A method for connection, applied to a second communication node, comprising:

8. The method of claim 7, wherein creating, updating, or releasing network topology connections of container object instances to multiple network planes according to the multiple network plane information templates and the multiple network plane routing information of the container objects comprises:

9. The method of claim 7, further comprising, after creating, updating, or releasing network topology connections of the container object instance to multiple network planes according to the multiple network plane information templates and the multiple network plane routing information of the container object:

sending the configuration information of the multi-network plane network topology structure of the container object instance to which the container object instance belongs; and the container object instance is used for reporting the configuration information of the multi-network plane topological structure to a target application.

10. The method of claim 7, further comprising:

and sending feedback information of successful creation, updating and deletion to the first communication node.

11. A connecting device, applied to a first communication node, comprising:

12. A connecting device, for use in a second communications node, comprising:

13. An apparatus, comprising: a memory, and one or more processors;

the memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-10.

14. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1-10.