CN113115329B - Container-based network slice instance deployment device and method - Google Patents

Abstract

The invention provides a container-based network slice example deployment device and method. The network slice example management module receives a user request for generating a network slice example, decomposes the network slice example into a plurality of network slice subnet examples according to the user request, and sends the related configuration requirements of the network slice subnet examples to the network slice subnet example management module; the network slice subnet instance management module receives the related requirements of the network slice subnet instance, decides to modify the existing network slice subnet instance or create a new network slice subnet instance, and sends the response result to the bottom container platform; and the bottom layer container platform executes resource scheduling according to the related requirements of the network slice subnet instances, and sequentially executes modification or creation of configuration files of related components to prepare for creation of the network slice subnet instances. The invention integrates the container technology and the network slices, realizes the rapid deployment and flexible arrangement of the network slices and ensures the slice isolation.

Description

Container-based network slice instance deployment device and method

Technical Field

The invention relates to the field of a fifth generation mobile communication system core network and network slicing, in particular to a container-based network slicing example deployment device and method.

Background

In the 5G era, network operators need to meet diversified service requirements of different users and different application scenarios, and provide differentiated and guaranteed services. In current network architectures, to achieve such a goal, different dedicated hardware needs to be deployed for each service or scenario, which would significantly increase operator operating costs, which is not practical. The 5G network slice is a new attempt of network service mode, and is a key feature of applying virtualization technology to 5G networks.

The virtualization can be realized by hardware simulation or an operating system, and the container virtualization scheme in recent years makes full use of the existing mechanism and characteristics of the operating system and can realize lightweight virtualization. The container effectively partitions resources managed by a single operating system into isolated groups to better balance conflicting resource usage requirements among the isolated groups. A container may be simply understood as a kind of sandbox, each container runs an application, different containers are isolated from each other, and a communication mechanism may be established between the containers. The creation and termination time response of the container is in millisecond level, and the requirement of the container on resources is very limited and is far lower than that of the virtual machine. Many times, there is no problem even if the container is taken directly as an application itself.

Virtualizing the 5G network physical infrastructure into a plurality of mutually independent virtual network slices according to scene requirements by virtualization, and customizing and cutting network functions and arranging and managing corresponding network resources by each slice according to service scene requirements and a traffic model. One network slice instance can be considered as one instantiated 5G end-to-end network. In one network slice, the operator can further flexibly divide the virtual resources to create sub-networks as required.

According to the construction concept of the network slice, the network slice is not limited to the 5G three-class application scene service, and can meet the service customization requirements of operators more flexibly and meet the requirements of different users or services on the network service quality. With the advent of the commercialization process of 5G networks, the commercialization deployment of network slices is also on the go. Therefore, a technical solution for container-based rapid and efficient deployment of network slice instances is urgently needed at present.

Disclosure of Invention

Aiming at the urgent requirement of a user or a service on the network service quality and meeting the more flexible service customization requirement of an operator, the invention provides the container-based network slice example deployment device and method, which uniformly manage the whole network resources by introducing virtualization methods such as containers and the like, realize the rapid and efficient deployment of the network slice example and meet the service customization requirement of the same user or service on the network slice.

In one aspect, the present invention provides a container-based network slice instance deployment apparatus, including: the system comprises a network slice instance management module, a network slice subnet instance management module and a bottom container platform; wherein:

the network slice example management module comprises a network slice management system, wherein the network slice management system is used for receiving a user request for generating a network slice example, decomposing the network slice example into a plurality of network slice subnet examples according to the user request, copying and forwarding the related configuration requirements of each network slice subnet example to the corresponding network slice subnet management system, receiving a network slice subnet example container of the network slice subnet management system and feeding back MOI of the network slice subnet example container to a user;

the network slice subnet instance management module comprises a network slice subnet management system, wherein the network slice subnet management system is used for receiving configuration requirements of each network slice subnet instance from the network slice management system, generating a decision according to the configuration requirements, sending the decision to a bottom container platform, receiving a network slice subnet instance container fed back by the bottom container platform, and sending the container to a corresponding network slice instance management module;

and the bottom container platform is used for receiving the decision of the network slice subnet management system, generating a network slice subnet instance container meeting the requirement according to the decision and feeding the network slice subnet instance container back to the network slice subnet management system.

Further, the decision is a decision to modify an existing network slice subnet instance container or a decision to create a new network slice subnet instance container;

correspondingly, the network slice subnet management system is specifically configured to:

if the existing network slice subnet instance container is determined to be modified, the MOI of the network slice subnet instance container needing to be modified is obtained, feasibility check is carried out on the network slice subnet instance container needing to be modified, and if the feasibility check is met, the MOI and related configuration requirements are sent to a bottom container platform;

and if the new network slice subnet instance container is determined to be created, an MOI is created for the newly created network slice subnet instance container, and the related configuration requirements of the newly created network slice subnet instance container are sent to the bottom container platform.

Further, the bottom container platform is specifically configured to:

if the decision of modifying the existing network slice subnet instance container is received, calling a VNF list in the network slice subnet instance container according to the MOI of the network slice subnet instance container, performing corresponding operation on the VNF list according to the configuration requirement, updating the operated VNF list to generate a new VNF list and uploading the new VNF list; modifying the NSD configuration file based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the network slice subnet instance container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into a network slicing subnet template, issuing the network slicing subnet template as a new NSSI container, and then sending the network slicing subnet template to a network slicing subnet management system;

if the decision of creating a new network slice subnet instance container is received, determining the functional units required to be contained in the newly created network slice subnet instance container according to the configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the type requirement of the network slice subnet instance container and uploading the NRM configuration file; and combining the published VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new network slice subnet instance container, and sending the network slice subnet instance container to a network slice subnet management system.

Further, the network slice instance management module further comprises an input request module; a user side for presetting a control server network and a port is established in the input request module; when the user side communicates with the server side, the server side receives a user request for generating the network slice example, serializes the user request JSON, and feeds back a deployment result of the network slice example to the user side.

Further, the network slice management system is further configured to receive a user request for terminating a network slice instance, determine an MOI of a corresponding network slice subnet instance container according to the MOI in the user request for terminating the network slice instance, and send a request for terminating each network slice subnet instance container to the corresponding network slice subnet management system;

correspondingly, the network slice subnet management system is also used for receiving the requirement for terminating each network slice subnet instance container from the network slice management system, judging to reserve the network slice subnet instance container and remove the association between the network slice subnet instance container and the user thereof, or terminating the network slice subnet instance container and remove the association between the network slice subnet instance container and the network slice instance to be terminated; generating a request according to the judgment result and sending the request to the bottom layer container platform;

the bottom container platform is also used for receiving a request of the network slice subnet management system for terminating the network slice subnet instance container, sequentially deleting the configuration files of the components of the network slice subnet instance container, and executing resource release.

In another aspect, the present invention provides a container-based network slice instance deployment method, including:

a network slice management system in the network slice instance management module receives a user request for generating a network slice instance, decomposes the network slice instance into a plurality of network slice subnet instances according to the user request, and copies and forwards the relevant configuration requirements of each network slice subnet instance to the corresponding network slice subnet management system;

a network slice subnet management system in the network slice subnet instance management module receives configuration requirements about each network slice subnet instance from the network slice management system, generates a decision according to the configuration requirements and sends the decision to a bottom container platform;

the bottom container platform receives the decision of the network slice subnet management system, generates a network slice subnet instance container meeting the requirement according to the decision and feeds the container back to the network slice subnet management system;

the network slice subnet management system receives the network slice subnet instance containers fed back by the bottom container platform and sends the network slice subnet instance containers to the corresponding network slice instance management module;

and the network slice example management module feeds back the MOI of the network slice subnet example container to the user.

Further, the generating a decision according to the configuration requirement and sending the decision to the bottom-layer container platform specifically includes:

generating a decision to modify an existing network slice subnet instance container or to create a new network slice subnet instance container according to configuration requirements;

if the existing network slice subnet instance container is determined to be modified, the MOI of the network slice subnet instance container needing to be modified is obtained, feasibility check is carried out on the network slice subnet instance container needing to be modified, and if the feasibility check is met, the MOI and related configuration requirements are sent to a bottom container platform;

and if the new network slice subnet instance container is determined to be created, an MOI is created for the newly created network slice subnet instance container, and the related configuration requirements of the newly created network slice subnet instance container are sent to the bottom container platform.

Further, the bottom container platform receives the decision of the network slice subnet management system, generates a network slice subnet instance container meeting the requirement according to the decision, and feeds the container back to the network slice subnet management system, and specifically includes:

if the decision of modifying the existing network slice subnet instance container is received, calling a VNF list in the network slice subnet instance container according to the MOI of the network slice subnet instance container, performing corresponding operation on the VNF list according to the configuration requirement, updating the operated VNF list to generate a new VNF list and uploading the new VNF list; modifying the NSD configuration file based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the network slice subnet instance container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, issuing the network slice subnet template as a new NSSI container, and then sending the network slice subnet template to a network slice subnet management system;

if the decision of creating a new network slice subnet instance container is received, determining a functional unit contained in the newly created network slice subnet instance container according to the configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the type requirement of the network slice subnet instance container and uploading the NRM configuration file; and combining the published VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new network slice subnet instance container, and sending the network slice subnet instance container to a network slice subnet management system.

Further, still include:

when a user side communicates with a server side, the server side receives a user request for generating a network slice example, serializes the user request JSON, and feeds back a deployment result of the network slice example to the user side; the client is established in an input request module in the network slice instance management module and used for presetting a control server network and a port.

Further, still include:

the network slice management system receives a user request for terminating the network slice example, determines the MOI of a corresponding network slice subnet example container according to the MOI in the user request for terminating the network slice example, and sends the requirement for terminating each network slice subnet example container to the corresponding network slice subnet management system;

the network slice subnet management system receives a requirement for terminating each network slice subnet instance container from the network slice management system, judges and reserves the network slice subnet instance container and releases the association between the network slice subnet instance container and a user thereof, or terminates the network slice subnet instance container and releases the association between the network slice subnet instance container and a network slice instance to be terminated; then, generating a request according to a judgment result and sending the request to a bottom container platform;

the bottom container platform receives a request of the network slice subnet management system for terminating the network slice subnet instance container, sequentially deletes configuration files of components of the network slice subnet instance container, and executes resource release.

The invention has the beneficial effects that:

the invention realizes the deployment of the network slice instance by introducing a container technology; the container has the flexibility of the virtualization technology, and avoids the disadvantage of overload of the traditional virtualization technology, and the greatest advantage of the container technology is that the container instance is created more quickly than the virtual machine. And the combination of the container technology and the network slice instance deployment method can more quickly and effectively realize the customized service of the network slice instance and flexibly and quickly migrate the network slice instance. The container technology has good isolation and convenient service deployment characteristics, is very suitable for the requirements of network slicing, and is a future development trend of the slicing technology.

Drawings

Fig. 1 is a schematic structural diagram of a container-based network slice example deployment apparatus according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of an NSI management module according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of an NSSI management module according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a bottom-level container platform provided by an embodiment of the present invention;

fig. 5 is a signaling interaction diagram of a container-based network slice example deployment method according to an embodiment of the present invention;

fig. 6 is a second signaling interaction diagram of an example deployment method of a container-based network slice according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.

In consideration of the important roles of current network function virtualization and network slicing in a 5G application scene and the differentiation requirements of users on network slicing due to different user needs, the problems of flexible deployment, independent management, slicing isolation and the like of slicing services need to be solved urgently. The Docker container technology is based on a Linux kernel to realize lightweight high-performance resource isolation, provides more computing resources for users by utilizing more saved hardware resources, realizes functions similar to virtual machines, is lighter than the virtual machines, supports second-level starting, and is suitable for flexible customization and rapid deployment of microservices.

For convenience of description, terms of art related to the present invention are explained as follows:

NSI (Network sliding Instrument): a network slice instance;

NSSI (Network slipping Network Instance): a network slice subnet instance;

NSMF (Network sizing Management Function): a network slice management system;

NSSMF (Network slipping sub-Network Management Function): a network slice subnet management system;

VNF (Virtual Network Function): a virtual network function;

NSD (Network Service Descriptor): a network service descriptor;

NRM (Network resource Model): a network resource model;

NSST (Network slipping sub Network Template): network slicing subnet template;

MOI (Manager Object Index): and managing the object identification.

Based on the above, referring to fig. 1, an embodiment of the present invention provides a container-based network slice example deployment apparatus, including: an NSI management module, an NSSI management module, and an underlying container platform, wherein:

referring to fig. 2, the NSI management module includes an NSMF, and the NSMF is configured to receive a user request for generating an NSI, decompose the NSI into a plurality of NSSIs according to the user request, copy and forward a relevant configuration requirement of each NSSI to a corresponding NSSMF, and receive an NSSI container of the NSSMF and feed back an MOI of the NSSI container to the user;

specifically, the NSI management module is configured to interact between the user and the NSMF, where on one hand, the NSMF may receive a user request for generating the NSI, and on the other hand, the NSMF may also receive a user request for terminating the NSI (details of the following embodiments are not described herein).

The user request for generating the NSI includes related resources and functions in the network, such as calculation, storage, transmission, and application scenarios. The NSI is broken down into several NSSIs according to the resource and functional requirements for the network slice contained in the request, the number of NSSIs being determined by the NSMF.

The NSMF can also send the message returned by the NSSMF to the user, on one hand, the NSSMF sends the created or modified MOI of the NSSI and the configuration file to the NSMF, the NSMF combines the related NSSIs into the NSSI, updates the MOI of the NSI to correspond to the matched MOI of the NSSI, sends the MOI of the NSI to the user, and responds to the NSI creation request of the user; on the other hand, the NSSMF feeds back the MOI and the termination result of the NSSI to the NSMF, and the NSMF disassembles the relation between the NSI and the corresponding NSSI, deletes the MOI and the related files of the NSI, and then responds to the request of the user for deleting the NSI (the following embodiments will be described in detail, and will not be described here again).

Referring to fig. 3, the NSSI management module includes an NSSMF, and the NSSMF is configured to receive a configuration requirement for each NSSI from the NSMF, generate a decision according to the configuration requirement, and send the decision to the bottom container platform, and receive an NSSI container fed back by the bottom container platform and send the NSSI container to the corresponding NSI management module;

in particular, the configuration requirements comprise different functional network elements (e.g. mobility management, charging management, policy control management, security management, etc.), different performance requirements (e.g. latency, mobility, reliability, rate, etc.), different slice types (describing characteristics of the slices in terms of characteristics and traffic).

The bottom container platform is used for receiving the NSSMF decision, generating the NSSI container meeting the requirement according to the decision and feeding the NSSMF container back.

Specifically, the underlying container platform performs resource scheduling according to the decision result of the NSSMF, and creates a new slice component based on the relevant requirements or modifies the existing slice component to generate an NSSI container meeting the requirements.

On the basis of the above embodiment, the decision is a decision to modify an existing NSSI container or a decision to create a new NSSI container;

correspondingly, referring to fig. 3, the NSSMF is specifically configured to:

if the existing NSSI container is determined to be modified, acquiring the MOI of the NSSI container needing to be modified, acquiring all contents related to the NSSI after acquiring the MOI, performing feasibility check on the NSSI container needing to be modified, and if the feasibility check is met, sending the MOI and related configuration requirements to a bottom-layer container platform; and after receiving the NSSI container fed back by the bottom container platform, updating the MOI of the NSSI container modified by the bottom container platform.

And if the new NSSI container is determined to be created, an MOI is created for the newly created NSSI container, and the related configuration requirements of the newly created NSSI container are sent to the bottom-layer container platform.

Referring to fig. 4, the bottom container platform is specifically configured to:

if the decision of modifying the existing NSSI container is received, calling a VNF list in the NSSI container according to the MOI of the NSSI container, performing corresponding operation (such as adding, deleting or modifying the VNF list) on the VNF list according to the configuration requirement, updating the operated VNF list to generate a new VNF list and uploading the new VNF list; modifying the NSD configuration file (such as the functional units contained in the NSD configuration file and the virtual links between the functions) based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the NSSI container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into NSST, issuing the NSST as a new NSSI container, and then sending the NSSMF container to NSSMF;

if the decision of creating a new NSSI container is received, determining the functional units required by the newly created NSSI container according to the configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the type requirement of the NSSI container and uploading the NRM configuration file; and combining the issued VNF list, NSD configuration file and NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new NSSI container, and sending the NSSI container to NSSMF.

The NSI management module and the NSSI management module in the embodiment of the invention analyze the network slice example based on the specific requirements of the user on the network slice example, send the next operation and the specific requirements of the network slice example to the bottom layer container platform, and the bottom layer container platform executes the modification of the existing NSSI container and creates a new NSSI container. Each NSSI container contains three profile packages, namely a VNF list, an NSD profile, and an NRM profile. Wherein, the VNF list includes different network functions and related configurations that each NSI needs to implement; the NSD configuration file is responsible for connecting all VNFs together and packaging the VNFs into a network service; the NRM is responsible for the performance requirements of the NSI (including application scenario, data rate, user density and coverage), public land mobile network requirements (PLMN), individual network slice selection assistance information (S-NSSAI), etc. of the NSI-related profiles. The containers are very fast to create and stop, the requirements of the containers for resources are very limited, and the NSSI is packed by the containers, so that a large amount of precious time is saved, and the risk of problems in the deployment process is reduced.

On the basis of the above embodiments, the network slice instance management module further includes an input request module; a user side for presetting a control server network and a port is established in the input request module; when the user side communicates with the server side, the server side is not only responsible for receiving a user request for generating NSI, serializing the user request JSON, facilitating the receiving and processing of a subsequent network slice instance management module, and feeding back the NSI deployment result to the user side.

On the basis of the foregoing embodiments, the container-based network slice instance deployment apparatus provided in the embodiments of the present invention is further configured to terminate a network slice instance, specifically:

the NSMF is also used for receiving a user request for terminating NSI, determining the MOI of the corresponding NSSI container according to the MOI in the user request for terminating NSI, and sending the requirement for terminating each NSSI container to the corresponding NSSMF;

correspondingly, the NSSMF is further configured to receive a request for terminating each NSSI container from the NSMF, and determine to reserve the NSSI container and disassociate the NSSI container from its user, or terminate the NSSI container and disassociate the NSSI container from the NSI to be terminated; generating a request according to the judgment result and sending the request to the bottom layer container platform;

specifically, if the NSSMF receives a request to terminate an NSSI container, it indicates that the NSSI container is no longer needed. If a container is shared or NSSMF decides to reserve this container for later use, NSSMF feeds back the result to NSMF; otherwise, the NSSMF sends a request to the underlying container platform to terminate the NSSI container and the MOI of the associated NSSI container. The NSSMF then sends the results of the bottom-tier container platform feedback to the NSMF, and deletes the MOI of this NSSI.

The bottom-layer container platform is further configured to receive a request of the NSSMF to terminate the NSSI container, delete configuration files of components of the NSSI container in sequence, and perform resource release.

Specifically, if the bottom-layer container platform receives a command for terminating the NSSI container, the corresponding profile package is obtained according to the MOI of the NSSI container to be deleted, the profiles of the NRM, the NSD, and the VNF are sequentially deleted, corresponding resources are released, and the termination result is fed back to the NSSMF.

Corresponding to the container-based network slice instance deployment device in each of the above embodiments, an embodiment of the present invention further provides a container-based network slice instance deployment method, including:

referring to fig. 5, the NSMF in the NSI management module receives a user request for generating an NSI, decomposes the NSI into a plurality of NSSIs according to the user request, and copies and forwards a relevant configuration requirement of each NSSI to a corresponding NSSMF;

NSSMF in NSSI management module receives configuration requirement of each NSSI from NSMF, generates decision according to the configuration requirement and sends the decision to bottom container platform;

specifically, the generating a decision according to the configuration requirement and sending the decision to the bottom-layer container platform specifically includes:

generating a decision to modify an existing NSSI container or to create a new NSSI container according to configuration requirements;

if the existing NSSI container is determined to be modified, acquiring the MOI of the NSSI container needing to be modified, performing feasibility check on the NSSI container needing to be modified, and if the feasibility check is met, sending the MOI and the related configuration requirements to a bottom-layer container platform;

and if the new NSSI container is determined to be created, an MOI is created for the newly created NSSI container, and the related configuration requirements of the newly created NSSI container are sent to the bottom-layer container platform.

The bottom container platform receives the NSSMF decision, generates an NSSI container meeting the requirement according to the decision and feeds the NSSMF back to the NSSMF;

specifically, if a decision to modify an existing NSSI container is received, a VNF list in the NSSI container is called according to the MOI of the NSSI container, corresponding operation is performed on the VNF list according to a configuration requirement, and the operated VNF list is updated to generate a new VNF list and is uploaded; modifying the NSD configuration file based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the NSSI container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, issuing the network slice subnet template as a new NSSI container, and sending the network slice subnet template to NSSMF;

if the decision of creating a new NSSI container is received, determining a functional unit contained in the newly created NSSI container according to a configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the NSSI container type requirement and uploading the NRM configuration file; combining the issued VNF list, NSD configuration file and NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new NSSI container, and sending the NSSI container to NSSMF

The NSSMF receives the NSSI container fed back by the bottom container platform and sends the NSSI container to the corresponding NSI management module;

the NSI management module feeds back the MOI of the NSSI container to the user.

On the basis of the above embodiment, the method further includes:

when a user side communicates with a server side, the server side receives a user request for generating NSI, serializes the user request JSON, facilitates receiving and processing of a subsequent network slice instance management module, and feeds back a deployment result of the NSI to the user side; the user side is established in an input request module in the NSI management module and is used for presetting a control server network and a port.

Referring to fig. 5, the input request module directly sends the received user request for generating NSI to the NSMF, then the NSSF creates an MOI for the NSI, decomposes the NSI into several NSSIs according to the relevant configuration requirements, sends the NSSI to the corresponding NSSMF, and the NSSMF determines to modify or create a new NSSI container and sends the new NSSI container to the corresponding module. If the modification step is executed, the MOI of the modified NSSI container needs to be obtained, and then feasibility check is carried out on the configuration file; if the creating step is performed, an MOI is created for the container. The NSSMF sends the NSSI processing result to a bottom-layer container platform, and the bottom-layer container platform creates or modifies the configuration file of the related components (VNF, NSD and NRM) and uploads the configuration file to the bottom-layer container platform. The underlying container platform combines the modified related components into a new NSSI container and feeds back the new NSSI container to the NSSMF. The NSSMF updates the MOI of the modified NSSI container that meets the configuration requirements and sends it to the NSMF. The NSMF establishes a relation between the MOI of the container and the MOI of the corresponding NSI, feeds back the MOI of the NSI to the user, and completes the creation process of the whole network slice example.

On the basis of the above embodiments, the embodiments of the present invention further provide a method for terminating NSI, including the following steps:

the NSMF receives a user request for terminating the NSI, determines the MOI of the corresponding NSSI container according to the MOI in the user request for terminating the NSI, and sends a requirement for terminating each NSSI container to the corresponding NSSMF;

the NSSMF receives a request from the NSMF to terminate each NSSI container and determines to retain the NSSI container and disassociate the NSSI container from its subscriber or to terminate the NSSI container and disassociate the NSSI container from the NSI to be terminated; then, generating a request according to a judgment result and sending the request to a bottom container platform;

the underlying container platform receives NSSMF's request to terminate the NSSI container, deletes in turn the NSSI container's component's configuration file, and performs resource release.

Specifically, referring to fig. 6, the input request module directly sends the received user request for terminating the NSI to the NSSF, and then the NSSF acquires the associated NSSI according to the MOI of the NSI and sends a request for deleting each NSSI to the corresponding NSSMF. The NSSMF judges the affiliation of the NSSI after receiving the termination request, if the NSSI is shared or the NSSMF decides to reserve for later use, the NSSMF feeds the result back to the NSMF, and then feeds the result back to the user; otherwise, the NSSMF sends a termination request and the MOI of the associated NSSI to the underlying container platform. After receiving the termination request, the bottom-layer container platform obtains all the configuration files owned by the NSSI container according to the MOI of the NSSI container to be deleted, sequentially deletes the configuration file packages of the NRM, the NSD and the VNF, releases corresponding resources, and feeds back the termination result to the NSSMF. The NSSMF then feeds back the termination result returned by the bottom container platform to the NSMF, and deletes the MOI of this NSSI. Finally, NSMF relieves the relation between NSI and corresponding NSSI, deletes the MOI and the related configuration file of NSI, and feeds back the termination result to the user

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, and not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (6)

1. A container-based network slice instance deployment apparatus, comprising: the system comprises a network slice instance management module, a network slice subnet instance management module and a bottom container platform; wherein:

the network slice instance management module comprises a network slice management system, the network slice management system is used for receiving a user request for generating a network slice instance, decomposing the network slice instance into a plurality of network slice subnet instances according to the user request, copying and forwarding related configuration requirements of each network slice subnet instance to the corresponding network slice subnet management system, receiving a network slice subnet instance container of the network slice subnet management system and feeding back MOI of the network slice subnet instance container to a user;

the network slice subnet instance management module comprises a network slice subnet management system, and the network slice subnet management system is used for receiving configuration requirements of each network slice subnet instance from the network slice management system, generating and determining the configuration requirements according to the configuration requirements, sending the configuration requirements to the bottom container platform, receiving a network slice subnet instance container fed back by the bottom container platform, and sending the network slice subnet instance container to the corresponding network slice instance management module;

the bottom container platform is used for receiving the decision of the network slice subnet management system, generating a network slice subnet instance container meeting the requirement according to the decision and feeding back the network slice subnet instance container to the network slice subnet management system;

the decision is a decision to modify an existing network slice subnet instance container or a decision to create a new network slice subnet instance container;

correspondingly, the network slice subnet management system is specifically configured to:

if the existing network slice subnet instance container is determined to be modified, the MOI of the network slice subnet instance container needing to be modified is obtained, feasibility check is carried out on the network slice subnet instance container needing to be modified, and if the feasibility check is met, the MOI and related configuration requirements are sent to a bottom container platform;

if the new network slice subnet instance container is determined to be created, an MOI is created for the newly created network slice subnet instance container, and the related configuration requirements of the newly created network slice subnet instance container are sent to a bottom container platform;

the bottom container platform is specifically configured to:

if the decision of modifying the existing network slice subnet instance container is received, calling a VNF list in the network slice subnet instance container according to the MOI of the network slice subnet instance container, performing corresponding operation on the VNF list according to the configuration requirement, updating the operated VNF list to generate a new VNF list and uploading the new VNF list; modifying the NSD configuration file based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the network slice subnet instance container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, issuing the network slice subnet template as a new NSSI container, and then sending the network slice subnet template to a network slice subnet management system;

if the decision of creating a new network slice subnet instance container is received, determining the functional units required to be contained in the newly created network slice subnet instance container according to the configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the type requirement of the network slice subnet instance container and uploading the NRM configuration file; and combining the published VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new network slice subnet instance container, and sending the network slice subnet instance container to a network slice subnet management system.

2. The apparatus of claim 1, wherein the network slice instance management module further comprises an input request module; a user side for presetting a control server network and a port is established in the input request module; when the user side communicates with the server side, the server side receives a user request for generating the network slice example, serializes the user request JSON, and feeds back a deployment result of the network slice example to the user side.

3. The apparatus according to claim 1 or 2, wherein the network slice management system is further configured to receive a user request for terminating the network slice instance, determine the MOI of the corresponding network slice subnet instance container according to the MOI in the user request for terminating the network slice instance, and send a request for terminating each network slice subnet instance container to the corresponding network slice subnet management system;

correspondingly, the network slice subnet management system is also used for receiving the requirement for terminating each network slice subnet instance container from the network slice management system, judging to reserve the network slice subnet instance container and remove the association between the network slice subnet instance container and the user thereof, or terminating the network slice subnet instance container and remove the association between the network slice subnet instance container and the network slice instance to be terminated; generating a request according to the judgment result and sending the request to the bottom layer container platform;

the bottom container platform is also used for receiving a request of the network slice subnet management system for terminating the network slice subnet instance container, sequentially deleting the configuration files of the components of the network slice subnet instance container, and executing resource release.

4. The container-based network slice instance deployment method is characterized by comprising the following steps:

a network slice management system in the network slice instance management module receives a user request for generating a network slice instance, decomposes the network slice instance into a plurality of network slice subnet instances according to the user request, and copies and forwards the related configuration requirements of each network slice subnet instance to the corresponding network slice subnet management system;

a network slice subnet management system in the network slice subnet instance management module receives configuration requirements of each network slice subnet instance from the network slice management system, generates a decision according to the configuration requirements and sends the decision to a bottom container platform; the generating a decision according to the configuration requirement and sending the decision to the bottom-layer container platform specifically includes:

generating a decision to modify an existing network slice subnet instance container or to create a new network slice subnet instance container according to configuration requirements;

if the existing network slice subnet instance container is determined to be modified, the MOI of the network slice subnet instance container needing to be modified is obtained, feasibility check is carried out on the network slice subnet instance container needing to be modified, and if the feasibility check is met, the MOI and related configuration requirements are sent to a bottom container platform;

if the new network slice subnet instance container is determined to be created, an MOI is created for the newly created network slice subnet instance container, and the related configuration requirements of the newly created network slice subnet instance container are sent to a bottom container platform;

the bottom container platform receives the decision of the network slice subnet management system, generates a network slice subnet instance container meeting the requirement according to the decision and feeds the container back to the network slice subnet management system; the bottom container platform receives the decision of the network slice subnet management system, generates a network slice subnet instance container meeting the requirement according to the decision and feeds the container back to the network slice subnet management system, and the method specifically comprises the following steps:

if the decision of modifying the existing network slice subnet instance container is received, calling a VNF list in the network slice subnet instance container according to the MOI of the network slice subnet instance container, performing corresponding operation on the VNF list according to the configuration requirement, updating the operated VNF list to generate a new VNF list and uploading the new VNF list; modifying the NSD configuration file based on the new VNF list, and uploading to generate a new NSD configuration file; modifying the NRM configuration file based on the new VNF list, the new NSD configuration file and the type requirement of the network slice subnet instance container, and uploading to generate a new NRM configuration file; combining the new VNF list, the NSD configuration file and the NRM configuration file into a network slice subnet template, issuing the network slice subnet template as a new NSSI container, and then sending the network slice subnet template to a network slice subnet management system;

if the decision of creating a new network slice subnet instance container is received, determining a functional unit contained in the newly created network slice subnet instance container according to the configuration requirement, and creating and uploading a VNF list; creating and uploading an NSD configuration file according to the VNF list; establishing an NRM configuration file according to the VNF list, the NSD configuration file and the type requirement of the network slice subnet instance container and uploading the NRM configuration file; combining the issued VNF list, NSD configuration file and NRM configuration file into a network slice subnet template, uploading the network slice subnet template to generate a new network slice subnet instance container, and sending the new network slice subnet instance container to a network slice subnet management system;

the network slice subnet management system receives the network slice subnet instance container fed back by the bottom container platform and sends the container to the corresponding network slice instance management module;

and the network slice example management module feeds back the MOI of the network slice subnet example container to the user.

5. The method of claim 4, further comprising:

when a user side communicates with a server side, the server side receives a user request for generating a network slice example, serializes the user request JSON, and feeds back a deployment result of the network slice example to the user side; the client is established in an input request module in the network slice instance management module and used for presetting a control server network and a port.

6. The method of any of claims 4 or 5, further comprising:

the network slice management system receives a user request for terminating the network slice example, determines the MOI of a corresponding network slice subnet example container according to the MOI in the user request for terminating the network slice example, and sends the requirement for terminating each network slice subnet example container to the corresponding network slice subnet management system;

the network slice subnet management system receives the requirement for terminating each network slice subnet instance container from the network slice management system, judges and reserves the network slice subnet instance container and releases the association between the network slice subnet instance container and the user thereof, or terminates the network slice subnet instance container and releases the association between the network slice subnet instance container and the network slice instance to be terminated; then, generating a request according to a judgment result and sending the request to a bottom layer container platform;

the bottom container platform receives a request of the network slice subnet management system for terminating the network slice subnet instance container, sequentially deletes configuration files of components of the network slice subnet instance container, and executes resource release.

Images