A connection method, device, equipment and storage medium

Abstract

The present application provides a connection method, apparatus, device, and storage medium. The method includes: performing lifecycle management on a multi-network plane information template of each container object in a container virtual network function (VNF); the lifecycle management of the multi-network plane information template includes 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

Technical Field

[0001] This application relates to communications, and in particular, to a connection method, apparatus, device, and storage medium. Background Art

[0002] In existing wireless network systems, it is necessary to support multi-network plane technology, that is, a telecommunication physical device or logical function entity is simultaneously connected to multiple networks. In short, there are multiple physical or virtual network interfaces on a host or logical function entity, and these interfaces are respectively connected to different networks, and these networks are generally independent of each other, such as management networks, signaling networks, data networks, billing networks, etc. Since the telecommunication system has very high requirements for reliability, the system configures multi-network planes to avoid the mutual influence of different network traffic and improve the robustness of the system.

[0003] In existing Network Functions Virtualization (NFV) systems, the NFV system supports multi-network plane connections of virtual machines, but does not support multi-network plane connections of containers. For a Virtualized Network Function (VNF) constructed by virtual machine instantiation, the virtual machines within the VNF can be assigned multiple Internet Protocol (IP) addresses and access multiple network planes. However, for a VNF constructed by container instantiation, how the container objects within the VNF access multiple network planes is an urgent problem to be solved. Summary of the Invention

[0004] Embodiments of this application provide a connection method, apparatus, device, and storage medium, which effectively support each container object in a container VNF to be connected to multiple network planes.

[0005] An embodiment of this application provides a connection method, which is applied to a first communication node and includes:

[0006] Perform lifecycle management on the multi-network plane information template of each container object in a container virtual network function VNF; the lifecycle 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.

[0007] An embodiment of this application provides a connection method, which is applied to a second communication node and includes:

[0008] 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 the following: creation operation instruction, update operation instruction, and deletion operation instruction of the container object;

[0009] Receive the multi-network plane information template and multi-network plane routing information of the container object sent by the first communication node;

[0010] 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.

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

[0012] A first management module, 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: the creation operation, update operation, and deletion operation of the multi-network plane information template of the container object.

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

[0014] A first receiving module, 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, update operation instruction, and deletion operation instruction of the container object;

[0015] A second receiving module, 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;

[0016] A second management module, 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.

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

[0018] The memory is used to store one or more programs;

[0019] 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 of the above embodiments.

[0020] An embodiment of the present application provides a storage medium, which stores a computer program, and when the computer program is executed by a processor, it implements the method described in any of the above embodiments. Description of the Drawings

[0021] Figure 1 It is an architecture diagram of an NFV system provided in the prior art;

[0022] Figure 2 is the architecture diagram of another NFV system provided in the prior art;

[0023] Figure 3 is the flowchart of a connection method provided in an embodiment of the present application;

[0024] Figure 4 is the flowchart of another connection method provided in an embodiment of the present application;

[0025] Figure 5 is the schematic diagram of the network topology of a container object provided in an embodiment of the present application;

[0026] Figure 6 is the flowchart of creating a multi-network plane information template provided in an embodiment of the present application;

[0027] Figure 7 is the flowchart of creating the network topology of a container object instance provided in an embodiment of the present application;

[0028] Figure 8 is the flowchart of updating the network connection of a container object provided in an embodiment of the present application;

[0029] Figure 9 is the flowchart of releasing a multi-network plane provided in an embodiment of the present application;

[0030] Figure 10 is the structural block diagram of a connection device provided in an embodiment of the present application;

[0031] Figure 11 is the structural block diagram of another connection device provided in an embodiment of the present application;

[0032] Figure 12 is the schematic diagram of the structure of a device provided in an embodiment of the present application. Detailed implementation manners

[0033] The embodiments of the present application will be described below with reference to the accompanying drawings.

[0034] In the existing open-source technologies, for example, in Kubernetes, its container objects (such as PODs) can only be assigned a single IP address to connect to a single network plane and cannot directly support multi-network plane access. Currently, multiple manufacturers have provided plugin-based multi-network plane access solutions. However, due to the lack of a standardized unified data model for multi-network planes, the NFV products of each manufacturer cannot be compatible and interconnected with each other, and the NFV products cannot be truly commercialized on a large scale.

[0035] Therefore, it is necessary to enhance the existing NFV system so that in the life cycle management operations of container VNFs, such as VNF instantiation construction and update operations, a unified multi-network plane data template is newly defined and supported, and a technical solution for connecting each container object in the container VNF to multiple network planes is supported, so as to enhance the support for connecting container objects in the VNF to multiple network planes in the NFV system.

[0036] NFV is a software processing technology that uses general-purpose hardware and virtualization technology to carry other functions, aiming to reduce the expensive equipment costs of the network. Through software-hardware decoupling and function abstraction, NFV makes the functions of network devices no longer dependent on dedicated hardware, and resources can be fully and flexibly shared, enabling the rapid development and deployment of new services, and automatic deployment, elastic scaling, fault isolation, and self-healing based on actual business needs.

[0037] Figure 1 It is an architecture diagram of an NFV system provided in the prior art. As Figure 1 shown, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) includes: the Operation-Support System / Business Support System (OSS / BSS), VNF, Network Functions Virtualization Infrastructure (NFVI), and Network Functions Virtualization Management and Orchestration System (NFV-Management and Orchestration, NFV-MANO). Among them, NFVI is responsible for fully virtualizing hardware resources such as computing, storage, and network, and mapping them into virtual resources; VNF uses software to implement various traditional physical network functions, and VNF runs on NFVI and uses the virtual resources virtualized by NFVI. NFV-MANO is responsible for managing and orchestrating the relationship between VNF and NFVI, as well as the connection relationship between VNFs and / or with other Physical Network Functions (PNFs).

[0038] NFV-MANO includes: Virtualized Infrastructure Manager (VIM), Virtualized Network Function Manager (VNFM), and Network Function Virtualization Orchestrator (NFVO). VIM is responsible for controlling and managing virtualized resources. Additionally, VIM may also include Physical Infrastructure Manager (PIM) functionality, which is responsible for managing bare-metal resources, such as physical servers; VNFM is responsible for the lifecycle management of VNFs; NFVO is responsible for the orchestration and management of virtual infrastructure, as well as the lifecycle management of Network Services (NS).

[0039] Figure 1 The NFV system architecture diagram shown only supports the network function virtualization technology for building VNFs in the form of Virtual Machines (VMs). For the developing network function virtualization technology of how to build VNFs in the form of containers, it is necessary to enhance the Figure 1 NFV system architecture diagram. Figure 2 This is the architecture diagram of another NFV system provided in the prior art. As Figure 2 shown, 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 a container runtime environment and the computing, network, and storage resources required to create containers. CISM and CISE use the Container Network Interface (CNI) interface protocol for connection and data interaction.

[0040] The basic functions of the NFV system are: performing life cycle management operations on NS, VNF, and VNFC, such as creation, scaling, self-healing, release, etc. In the case of using virtual machine mode to perform life cycle management on NS and VNF, such as the instantiation operation: BSS / OSS will send the NSD and virtual network function descriptor (VNF Descriptor, VNFD) templates to the NFVO. The NFVO instantiates the NS according to the NSD, generates a network service instance (NSI) and creates a virtual link (VL) for the network link between VNFs. The VNFM performs an instantiation operation on the VNF to generate VNFI / VNFCI and the network connection between VNFCI.

[0041] In one embodiment, the present application provides a connection method, which newly defines and supports a unified multi-network plane information template in the life cycle management operation of container VNF to support each container object in the container VNF to connect to multiple network planes.

[0042] In one implementation manner, Figure 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 Figure 3 shown, this embodiment includes S110.

[0043] S110, perform life cycle management on the multi-network plane information template of each container object in the container VNF.

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

[0045] In the embodiment, after the CISM receives the multi-network plane attribute information of each container object in the container VNF, it constructs a multi-network plane information template according to the multi-network plane attribute information, and performs operations such as creation, update, or deletion on the multi-network information template according to different operation instructions. In the embodiment, the container objects in the container VNF are connected to multiple network planes. However, each container object can communicate with multiple network planes simultaneously.

[0046] In one embodiment, the VNFD serving the container VNF includes: the multi-network plane attribute information of the container object, and the 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, in the VNFD template, it includes: the multi-network plane attribute information of the container object, and the multi-network plane routing information of the container object.

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

[0048] In one embodiment, the multi-network plane routing information of a container object includes at least one of the following: the network node attributes of the virtual network interface card (vNIC) / network interface card (NIC) of the physical network, and the network routing connection relationships of the multiple logical network objects connected by the container object to the physical network object.

[0049] In one embodiment, before performing life cycle management on the multi-network plane information template of each container object in a container VNF, it further includes:

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

[0051] Receiving the life cycle management operation requests of each container object in the container VNF sent by the third communication node.

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

[0053] In one embodiment, performing life cycle management on the multi-network plane information template of each container object in a container VNF includes:

[0054] 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;

[0055] Informing a second communication node to create, update, or delete a container object instance;

[0056] Sending the multi-network plane information template and the multi-network plane routing information of the container object to the second communication node.

[0057] Figure 4 It is a flowchart of another connection method provided by an embodiment of the present application. This embodiment is applied to a second communication node. Exemplarily, the second communication node may be a CIS. As Figure 4 shown, this embodiment includes: S210 - S230.

[0058] S210. Receiving the life cycle management operation instruction of the container object sent by the first communication node.

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

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

[0061] S230. 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 multi-network plane routing information of the container object.

[0062] In one embodiment, 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 multi-network plane routing information of the container object includes:

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

[0064] 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 multi-network plane routing information of the container object.

[0065] In one embodiment, after 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 multi-network plane routing information of the container object, it further includes:

[0066] Send the configuration information of the multi-network plane network topology structure of the container object instance to the belonging container object instance; the container object instance is used to report the configuration information of the multi-network plane topology structure to the target application.

[0067] In one embodiment, the connection method applied to the second communication node further includes:

[0068] Send feedback information of successful creation, update, or deletion to the first communication node. In the embodiment, after the multi-network plane network topology structure of the container object instance is successfully created, updated, or deleted, the feedback information of successful creation, update, or deletion can be sent from the CIS to the CISM, and then from the CISM to the VNFM for feedback, and then from the VNFM to the NFVO for feedback until it is feedback to the OSS / BSS.

[0069] In an embodiment, a container-supported NFV enhanced system is adopted. When performing lifecycle management operations on a container VNF by operating on container objects, such as VNF instantiation, VNF instance update, etc., first, it is necessary to enhance and extend the VNFD serving the container VNF. Add multi-network plane attribute information of container objects (i.e., the definition of multiple logical network objects and the definition of how the container object is connected to multiple logical network objects) and multi-network plane routing information of container objects (the multi-network plane routing information of container objects refers to the information describing the network routing connection relationship between multiple logical network objects connected to the container object and one or more physical network objects) to the VNFD. Then, the CISM constructs a multi-network plane information template serving the container object.

[0070] 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.

[0071] During the instantiation process of the container object, the CIS constructs a multi-network plane network topology structure of the container object instance (the virtual or physical network connection between the container object and multiple logical network objects, and the virtual or physical network connection between the logical network object and the physical network object) according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object.

[0072] After the instantiation of the container object is completed, the CIS sends the multi-network plane network topology configuration information of each container object to the corresponding container object instance, which is passed to the upper-layer application by the container object instance.

[0073] In an embodiment, it is necessary to expand the VNFD serving the container object to support the multi-network plane access of the container object: In the VNFD, it is necessary to add the multi-network plane attribute information of the container object, including but not limited to the network names, IDs, network attributes (such as IPv4 / v6 addresses and ports, etc.) of multiple logical network objects, the network node attributes (such as IPv4 / v6 addresses and ports, etc.) of the external connection of the container object, the connection relationships of the container object to multiple logical network objects (such as the eth0 of the container object accesses the Msc management network, and eth1 accesses the sig signaling network), the logical network plugin information (such as Flannel plugin, calico plugin, canal plugin, kube-router, etc.) connected by the container object, etc. In addition, in the VNFD, it is necessary to expand the multi-network plane routing information of the container object, including but not limited to the vNIC / NIC network node attributes (such as IPv4 / v6 addresses and ports, etc.) of the physical network, the network routing connection relationships from the logical network object to the physical network object (such as the sig network of container object 1 is connected to the NIC / vNIC1 of the physical network through network routing, and the Msc network is connected to the NIC / vNIC2 of the physical network through network routing). Figure 5 is a schematic diagram of the network topology of a container object provided by an embodiment of the present application. As Figure 5 shown, the container cluster node can be regarded as an instance of CIS.

[0074] In an 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 extracts 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.

[0075] In an embodiment, the CISM constructs a multi-network plane information template for the container object according to the multi-network plane attribute information of the container object, which includes the information of multiple logical networks connected by the container object, the information of the container object network node, the network connection relationship between the multiple logical networks and the container object, the plugin information supporting the multi-network plane, etc.

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

[0077] When creating an instance of a container object, the CIS creates the network nodes of the container object instance, the network topologies between the nodes and multiple logical network objects, and the network topologies between the logical network objects and physical network objects according to the multi-network plane information template of the container object and the network connection relationships between multiple logical network objects and physical network objects of the container object, and finally generates a multi-network plane network topology structure of the container object instance, so as to connect each container object instance within the VNF to the multi-network plane.

[0078] In the embodiment, after the VNF is instantiated, the CIS sends the multi-network plane network topology configuration information of each container object instance within the VNF instance to the corresponding container object instance, including the IPv4 / v6 address and port of the container object node, 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 / v6 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 multi-network plane network topology configuration information to the upper-layer application, and the upper-layer application realizes the monitoring of data transmission of the container object instance according to the network topology configuration of the container object.

[0079] In one implementation manner, Figure 6 It 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 for 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, the CISM creates a multi-network plane information template for 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.

[0080] As Figure 6 shown, this embodiment includes: S310 - S380.

[0081] S310, orchestrate the VNFD template for the container object.

[0082] 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 existing VNFD template. In addition, the multi-network plane routing information of the container object also needs to be extended and added to the existing VNFD template.

[0083] Add multi-network plane attribute information of container objects to the VNFD template, including but not limited to the network names, IDs, network node attributes of multiple logical network objects (such as IPv4 / v6 addresses and ports, etc.), network node attributes of container objects (such as IPv4 / v6 addresses and ports, etc.), the connection relationships between container objects and multiple logical network objects (such as the eth0 of the container object accesses the Msc management network, and eth1 accesses the signaling (sig) network), the logical network plugin information connected by the container object (such as flannel plugin, calico plugin, canal plugin, kube-router...), etc.

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

[0085] Exemplarily, when creating the topology of container objects in a certain VNF and multiple logical network objects (such as the signaling (sig) plane, management plane, data plane, charging network plane), it is necessary to orchestrate the attributes of the multiple logical network objects, the network node attributes of the container objects, the network connection relationships between the container objects and the multiple logical network objects, the physical network node attributes, and the network routing connection relationships between the logical network and the physical network. In this way, when instantiating the container object, the connection from the container object to multiple logical network objects and the connection from multiple logical network objects to physical network objects can be created.

[0086] S320: Upload the orchestrated NSD and the VNFD template serving the container VNF to the NFVO.

[0087] S330: The NFVO distributes each VNFD template associated with the container VNF to the VNFM.

[0088] S340: Initiate an NS / VNF instantiation request to the NFVO.

[0089] In an embodiment, the NSD ID is carried in the NS instantiation request. The NFVO notifies the VNFM to initiate an instantiation request for all container VNFs that make up the NS according to different types of VNFD template IDs included in the NSD (taking the instantiation request as an example, it can be other VNF lifecycle management operations, such as VNF instantiation, scaling, self-healing, termination, etc.). In an embodiment, the OSS can also separately initiate an instantiation request for the container VNF to the NFVO, carrying the ID of the VNFD template.

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

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

[0092] S360. Parse the VNFD template and extract the network attribute information of the container object.

[0093] In an embodiment, in the lifecycle management operation of the container VNF, such as performing an instantiation operation on the container VNF, the VNFM needs to instantiate all container objects included therein. When performing the instantiation operation of the container VNF, the instantiation operation of the container object is the responsibility of the CISM. Therefore, 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, including multi-network plane attribute information and multi-network plane routing information.

[0094] S370. Send the multi-network attribute information of the container object to the CISM.

[0095] In an embodiment, send the multi-network network attribute information of each container object in the container VNF to the CISM.

[0096] S380. Build a multi-network plane information template for the container object.

[0097] In an embodiment, in the container VNF lifecycle management process, the CISM is responsible for the lifecycle management operations of the container object, such as the instantiation operation. When performing the instantiation operation of the container object, after the CISM receives the network attribute information of the container object sent by the VNFM, according to the NFV-related rules or policies, it creates and saves a multi-network plane information template for the container object based on the multi-network plane attribute information of the container object.

[0098] In an embodiment, the content in the multi-network plane information template is not limited to the following parameters and information: attributes of the container object, including the container object name, ID, network attributes (IPv4 / V6 address attributes) of the external nodes, the VNF name and ID to which the container object belongs, etc.; attribute information of multiple logical network objects connected to the container object: not limited to the number, name, ID, type, and network attributes (IPv4 / V6 address attributes) of the connection nodes of multiple logical networks; connection relationships between the container object and multiple logical network objects (constraints on network performance); network performance constraints of associated logical network objects; input parameters of associated logical network objects, including Qos, plug-in information (input and output requirements, including injection file format and parameters).

[0099] Through this embodiment, during the instantiation process of the NS or VNF, CISM can construct a multi-network plane information template based on the multi-network plane attribute information of the container object for creating the network topology of the container object during the subsequent container object instantiation process.

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

[0101] After the container object instantiation is completed and its network topology construction is completed, 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 specific network addresses and routes.

[0102] As Figure 7 shown, this embodiment includes: S410 - S470.

[0103] S410. Send an instantiation request for the container object to CISM.

[0104] During the container VNF instantiation process, the VNFM notifies CISM to perform an instantiation operation on each container object within the VNF.

[0105] S420. Request CIS to create a container object instance.

[0106] In an embodiment, CISM sends the computing resource and storage resource requirements needed to create container object instances inside the VNF to CIS, and requests 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 CIS through the CNI interface protocol, and requests CIS to build network connections for the container object instances.

[0107] S430. Create container object instances and allocate computing resources and storage resources.

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

[0109] S440. Build the network topology of each container object.

[0110] In an embodiment, CIS assigns IP addresses and ports to the external connection network nodes 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 builds the network topology for each container object instance, that is, the network connection topology of the container object instance, multiple logical network objects, and multiple virtual / physical network objects.

[0111] CIS saves the network topology configuration information of each container object instance in the container VNF instance, including the external IP addresses and ports assigned to the external connection nodes of the container object instance, the IP addresses and ports of multiple logical network object nodes, the IP addresses and ports of virtual / physical network objects, and the network connection routing information of the three.

[0112] S450. Send to CISM that the container object instances have been created and the instantiation is completed.

[0113] In an embodiment, after the computing resources and storage resources of each container object instance in the VNF are successfully allocated and its network topology is successfully created, CIS notifies CISM that the instantiation of the container object in the VNF is completed. In the notification message, CIS notifies CISM that the network topology of each container object in the VNF has been built.

[0114] S460. Perform service configuration on the VNF instance to complete the VNF instantiation.

[0115] In an embodiment, VNFM continues the subsequent operations of the VNF instantiation, and performs service parameter configuration on the created VNF instance to complete the instantiation operation of the container VNF. Later, EM performs service configuration and management on the container VNF instance.

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

[0117] 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 can further report this configuration to the application for monitoring the transmission path.

[0118] In this embodiment, during 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 the container runtime environment, and constructs the network topology of each container object instance according to the multi-network plane information template of the container object and the multi-network plane routing information of the container object, thus completing the instantiation of the container object. After the container object instantiation is completed, the CISM notifies the VNFM, and the VNFM completes the final VNF instantiation operation.

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

[0120] 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 changes, the OSS / NFVO initiates a VNF instance change request to update the network topology of the container object instance. 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. The CISM notifies 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 multi-network plane information template of the container object or the updated multi-network plane routing information of the container object, thus completing the network connection update operation of the container object.

[0121] As Figure 8 shown, this embodiment includes: S510 - S5120.

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

[0123] In an embodiment, updating the network attribute information of the container object in the VNFD template can be the multi-network plane attribute information of the container object, or the multi-network plane routing information of the container object, or both can be updated.

[0124] 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 add or reduce logical network objects; for another example, updating the multi-network plane routing information of the container object can change the network connection relationship between the logical network object and the virtual / physical network object.

[0125] S520. Upload the updated VNFD template to the NFVO.

[0126] In an 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.

[0127] S530. Initiate a VNF instance update.

[0128] In an embodiment, the NFVO initiates a VNF instance update to the VNFM. At the same time, the NFVO distributes the updated VNFD template to the VNFM.

[0129] S540. Send an update request for the container object instance.

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

[0131] 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 sends the updated network attribute information of the container object in the VNF to the CISM to notify the CISM to perform a container object instance update operation on the container object.

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

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

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

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

[0136] S570. Update the network topology of the container object instance.

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

[0138] For the newly added network plane, 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.

[0139] For the reduced network plane, 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.

[0140] CIS re-saves 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 connection node of the logical network object, the IP address of the connection node of the virtual / physical network object, and the network routing information among the three.

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

[0142] S590 and CISM notify VNFM that the update of the container object instance is completed.

[0143] In an embodiment, after the network topology of the container object instance is updated, CISM notifies VNFM that the instance update of the container object is completed.

[0144] S5100, VNFM notifies NFVO that the VNF instance update is completed.

[0145] In an embodiment, when all the container objects to be updated in the container VNF complete the container object instance update, VNFM notifies NFVO that the VNF instance update is completed, and the network topologies of all the container object instances to be updated in the VNF instance are updated.

[0146] S5110, NFVO notifies OSS / BSS that the VNF instance update is completed.

[0147] In an embodiment, after receiving the message that the container VNF instance update is completed notified by VNFM, NFVO notifies OSS / BSS that the network topology of the relevant VNF instance has been changed.

[0148] S5120, CIS sends the configuration information of the updated multi-network plane network topology to the container object instance.

[0149] In an embodiment, 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 further report the configuration to the application for monitoring the transmission path.

[0150] Through this embodiment, when the network topology of the container object needs to be updated, it is necessary to update the network attribute information of the container object in VNFD, and in the way of VNF instance update, VNFM notifies CISM to update the container object instance to be updated. CISM updates the multi-network plane information template of the container object and sends it to CIS through the CNI interface protocol, requesting to update the network topology of the container object. CIS updates the network topology structure of the container object in the container runtime environment 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.

[0151] In one implementation manner, Figure 9 is a flowchart of releasing a multi-network plane provided by 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.

[0152] Such as Figure 9As shown, this embodiment includes: S610 - S690.

[0153] S610. Initiate a release request for the VNF instance.

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

[0155] S620. The NFVO notifies the VNFM of the release of the VNF instance.

[0156] S630. The VNFM notifies the CISM of the release of the resources of the container object instance.

[0157] In the embodiment, the VNFM notifies the CISM of the release of 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.

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

[0159] In the embodiment, the CISM notifies the CIS to release the resources allocated to each container object instance within 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 to release the computing resources and storage resources of each container object instance through other interfaces.

[0160] S650. The CIS releases the network resources, computing resources, and storage resources of the container object instance.

[0161] In the embodiment, the CIS releases the IP addresses allocated to each container object within the VNF instance, releases the network resources of each logical network object, deletes the network connections between the container object instance and each logical network object, and the network connections between the logical network object and the virtual / physical network object, and finally deletes the network topology of each container object instance of the VNF.

[0162] The CIS deletes the network topology configuration information of each container object instance in the VNF instance saved locally; the CIS releases the computing resources and storage resources allocated to each container object in the VNF instance.

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

[0164] In an embodiment, the CIS notifies the CISM that the computing and storage resources of each container object instance of the VNF instance have been released, and notifies the CISM through the CNI interface that the network resources of each container object instance in the VNF instance have been released. After receiving the notification message from the CIS, the CISM learns that the computing resources, storage resources, and network resources of the container object instances inside its VNF have all been released, and the CISM deletes the created container objects. The CISM deletes the multi-network plane information templates of each container object of this VNF saved locally.

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

[0166] In an 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.

[0167] S680. The VNFM notifies the NFVO that the VNF instance resources have been released and deletes the VF instance.

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

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

[0170] In an 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.

[0171] Through this embodiment, in the case of deleting a VNF instance, during the deletion process of the VNF instance, 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 the CIS releases the resources of the container object, it notifies the CISM, and after the CISM notifies the VNFM and the VNFM confirms that all container object instances in the VNF instance have been released, the VNFM completes the deletion of the VNF instance.

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

[0173] The first management module 710 is configured to perform lifecycle management on the multi-network plane information templates of each container object in the container virtual network function (VNF); the lifecycle management of the multi-network plane information templates includes at least one of the following operations: creation operation, update operation, and deletion operation of the multi-network plane information templates of the container objects.

[0174] The connection device provided in this embodiment is configured to implement Figure 4 the connection method applied to the first communication node in the shown embodiment. The implementation principle and technical effects of the connection device provided in this embodiment are similar and will not be elaborated here.

[0175] In one embodiment, the virtual network function descriptor (VNFD) serving the container VNF includes: the multi-network plane attribute information of the container object and the multi-network plane routing information of the container object.

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

[0177] In one embodiment, the multi-network plane routing information of the container object includes at least one of the following: the virtual network interface card (vNIC) / network interface card (NIC) network node attributes of the physical network and the network routing connection relationships of the multiple logical network objects connected by the container object to the physical network object.

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

[0179] The third receiving module is configured to receive 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 before performing lifecycle management on the multi-network plane information templates of each container object in the container VNF.

[0180] The fourth receiving module is configured to receive the lifecycle management operation requests of each container object in the container VNF sent by the third communication node.

[0181] In one embodiment, the first management module includes:

[0182] The first management unit is configured to 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.

[0183] The second management unit is configured to notify the second communication node to create, update, or delete the container object instance.

[0184] A sending unit, configured to send a multi-network plane information template and multi-network plane routing information of a container object to a second communication node.

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

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

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

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

[0189] The connection device provided by this embodiment is set to implement Figure 5 the connection method applied to the second communication node shown in the embodiment. The implementation principle and technical effect of the connection device provided by this embodiment are similar and will not be elaborated here.

[0190] In one embodiment, the second management module 830 includes:

[0191] A third management unit, configured to create, update, or delete a container object instance according to the life cycle management operation instruction of the container object;

[0192] A fourth management unit, configured to create, update, or release a network topology connection between a container object instance and a multi-network plane according to the multi-network plane information template and multi-network plane routing information of the container object.

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

[0194] A first sending module, configured to, after creating, updating, or releasing a network topology connection between a container object instance and a multi-network plane according to the multi-network plane information template and multi-network plane routing information of the container object, send configuration information of the multi-network plane network topology structure of the container object instance to the belonging container object instance; the container object instance is used to report the configuration information of the multi-network plane topology structure to a target application.

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

[0196] A second sending module, configured to send feedback information indicating successful creation, update, or deletion to the first communication node.

[0197] Figure 12 It is a schematic structural diagram of a device provided by an embodiment of the present application. As Figure 12 shown, 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, Figure 12 and one processor 910 is taken as an example herein. The number of memories 920 in the device may be one or more, Figure 12 and one memory 920 is taken as an example herein. The processor 910, memory 920, and communication module 930 of the device may be connected through a bus or other means, Figure 12 and connected through a bus is taken as an example herein. In this embodiment, the device is the first communication node.

[0198] The memory 920, as a computer-readable storage medium, can be set to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the device of any embodiment of the present application (for example, the first management module in the connection device). The memory 920 may include a storage program area and a storage data area. Among them, the storage program area may store an operating system and application programs required for at least one function; the storage data area may store data created according to the use of the device, etc. 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 instances, the memory 920 may further include a memory remotely set relative to the processor 910, and these remote memories may be connected to the device through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0199] The communication module 930 is configured to establish a communication connection between the first communication node and the second communication node for data communication and signal communication.

[0200] The above-provided device can be set to execute the connection method applied to the first communication node provided in any of the above embodiments, and has corresponding functions and effects.

[0201] In the case where the device is the second communication node, the above-provided device can be set to execute the connection method applied to the second communication node provided in any of the above embodiments, and has corresponding functions and effects.

[0202] The embodiments of the present application further provide a storage medium containing computer-executable instructions, which are used to execute a connection method applied to a first communication node when executed by a computer processor. The method includes: performing life cycle management on the multi-network plane information templates of each container object in a container virtual network function (VNF); the life cycle management of the multi-network plane information templates includes at least one of the following operations: the creation operation, the update operation, and the deletion operation of the multi-network plane information template of the container object.

[0203] The embodiments of the present application further provide a storage medium containing computer-executable instructions, which are used to execute a connection method applied to a second communication node when executed by a computer processor. The method includes: receiving a life cycle management operation instruction of a container object sent by the first communication node, where the life cycle management operation instruction includes one of the following: a creation operation instruction of the container object, an update operation instruction, and a deletion operation instruction; receiving the multi-network plane information template and the multi-network plane routing information of the container object sent by the first communication node; 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.

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

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

[0206] The embodiments of the present application can 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 can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0207] Any block diagram of a logical process in the accompanying drawings of the present application may represent a program step, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. A computer program may be stored in a memory. The memory may be of any type suitable for 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 memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. The computer-readable medium may include a non-transitory storage medium. The data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FGPA), and a processor based on a multi-core processor architecture.

Claims

1. A connection method, characterized in that Applied to a first communication node, including: Performing lifecycle management on the multi-network plane information templates of each container object in a container virtual network function (VNF); the lifecycle management of the multi-network plane information templates includes at least one of the following operations: the creation operation, update operation, and deletion operation of the multi-network plane information templates of the container objects; The virtual network function descriptor (VNFD) serving the container VNF includes: the multi-network plane attribute information of the container objects, and the multi-network plane routing information of the container objects; Wherein, the multi-network plane attribute information of the container objects is the definition of multiple logical network objects and the definition of the connection between the container objects and the multiple logical network objects, and the multi-network plane routing information of the container objects is the information describing the network connection relationship between the multiple logical network objects connected to the container objects and one or more physical network objects; The performing lifecycle management on the multi-network plane information templates of each container object in the container VNF includes: Creating or updating the multi-network plane information templates of the container objects according to the multi-network plane attribute information of the container objects; Informing a second communication node to create, update, or delete a container object instance; Sending the multi-network plane information templates and the multi-network plane routing information of the container objects to the second communication node, so that the second communication node creates, updates, or releases the network topology connection between the container object instance and the multi-network plane according to the multi-network plane information templates and the multi-network plane routing information.

2. The method according to claim 1, wherein The multi-network plane attribute information of the container objects includes at least one of the following: the network names, identification IDs, and network attributes of at least two logical network planes, the network node attributes of the container objects, and the connection relationships of the container objects connected to multiple logical network objects.

3. The method according to claim 1, wherein The multi-network plane routing information of the container objects includes at least one of the following: the virtual network interface card (vNIC) / network interface card (NIC) network node attributes of the physical network, and the network routing connection relationships of the multiple logical network objects connected to the container objects to the physical network objects.

4. The method according to claim 1, characterized in that, Before performing lifecycle management on the multi-network plane information templates of each container object in the container VNF, it further includes: Receiving the multi-network plane attribute information of the container objects and the multi-network plane routing information of the container objects sent by a third communication node; Receiving the lifecycle management operation requests of each container object in the container VNF sent by the third communication node.

5. A connection method, characterized in that, Applied to a second communication node, including: Receiving the lifecycle management operation instructions of the container objects sent by the first communication node, and the lifecycle management operation instructions include one of the following: the creation operation instructions, update operation instructions, and deletion operation instructions of the container objects; Receiving the multi-network plane information templates and the multi-network plane routing information of the container objects sent by the first communication node; 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 templates and the multi-network plane routing information; Among them, the multi-network plane attribute information of the container object is the definition of multiple logical network objects and the definition of the connection between the container object and the multiple logical network objects, and the multi-network plane routing information of the container object is the information describing the network connection relationship between the multiple logical network objects connected to the container object and one or more physical network objects; After 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 following is further included: Sending the configuration information of the multi-network plane network topology structure of the container object instance 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 structure to the target application.

6. The method according to claim 5, wherein The 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 includes: Creating, updating, or deleting the container object instance according to the life cycle management operation instruction of the container object; 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.

7. The method according to claim 5, characterized in that, The method further includes: Sending feedback information of successful creation, update, or deletion to the first communication node.

8. A connecting device, characterized in that, Applied to the first communication node, it 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: the creation operation, update operation, and deletion operation of the multi-network plane information template of the container object; The virtual network function descriptor (VNFD) serving the container VNF includes: the multi-network plane attribute information of the container object and the multi-network plane routing information of the container object; Among them, the multi-network plane attribute information of the container object is the definition of multiple logical network objects and the definition of the connection between the container object and the multiple logical network objects, and the multi-network plane routing information of the container object is the information describing the network connection relationship between the multiple logical network objects connected to the container object and one or more physical network objects; The first management module includes: The first management unit is configured to 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; The second management unit is configured to notify the second communication node to create, update, or delete 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, so that the second communication node creates, updates, or releases 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.

9. A connecting device, characterized in that, Applied to the second communication node, it 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 the following: a creation operation instruction of the container object, an update operation instruction, and a deletion operation instruction; A second receiving module, 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; A second management module, configured to 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; Wherein, the multi-network plane attribute information of the container object is a definition of multiple logical network objects and a definition of the connection between the container object and the multiple logical network objects, and the multi-network plane routing information of the container object is information describing the network connection relationship between the multiple logical network objects connecting the container object and one or more physical network objects; The connection device further includes: A first sending module, configured to, after 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, send the configuration information of the multi-network plane network topology structure of the container object instance to the container object instance to which it belongs, and the container object instance is used to report the configuration information of the multi-network plane topology structure to a target application.

10. A device, characterized in that, Including: A memory, and one or more processors; The memory is used 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 according to any one of claims 1-7.

11. A storage medium, characterized in that, The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1-7 is implemented.

Images