Network slicing deployment method and device

Abstract

The present invention provides a method and device for deploying network slices, which belongs to the technical field of network slice management and orchestration. The method for deploying network slices is executed by NSMF, and the method includes: receiving a request for creating a network slice from CSMF, carrying network slice service requirements; determining the corresponding NST and NST DM according to the request for creating a network slice; parsing the NSST template and NSST DM of each subdomain in NST and NST DM, and decomposing the network slice service requirements into requirements of each subdomain according to NST; sending a network slice subnet instance NSSI creation request to the NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; receiving the slice subnet creation result returned by NSSMF; completing the network and service configuration of end-to-end network slices across domains; returning the network slice creation result to CSMF. The technical solution of the present invention can avoid waste of resources.

Description

Technical Field

[0001] The present invention relates to the field of network slicing management and orchestration technology, and in particular to a method and device for deploying network slicing. Background Art

[0002] 5G network slicing is an end-to-end logical dedicated network that provides specific network capabilities. An end-to-end network slice instance NSI (Network Slice Instance) is a collection of end-to-end network functions and required physical / virtual resources, and is composed of network slice subnet instances NSSI (Network Slice Subnet Instance) of wireless, transmission and core networks. Network slice services identified by S-NSSAI (Single Network Slice Selection Assistance Information) are carried and implemented through NSI instances. For sharable slice services, NSI instances can be shared with other slice services; for slice services with exclusive resources, one NSI instance can be exclusively used. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide a method and device for deploying a network slice, which can avoid waste of resources.

[0004] To solve the above technical problems, the embodiments of the present invention provide the following technical solutions:

[0005] On the one hand, a network slice deployment method is provided, which is performed by a network slice management function NSMF, and the method includes:

[0006] Receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement;

[0007] Determine a corresponding network slice template NST and an NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, each NST DM represents a combination of a capability model and a resource model;

[0008] Parsing the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, decomposing the network slice service requirements into requirements of each subdomain according to the NST, the NSST template including multiple groups of NSST DMs, each NSST DM representing a combination of a subdomain capability model and a resource model;

[0009] Send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain;

[0010] Receive the slice subnet creation result returned by NSSMF;

[0011] Complete cross-domain network and service configuration for end-to-end network slicing;

[0012] Return the network slice creation result to CSMF.

[0013] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0014] In some embodiments, determining the corresponding NST and NST DM according to the create network slice request includes:

[0015] The network slice creation request carries the identifiers of the NST and the NST DM, and the corresponding NST and NST DM are determined according to the identifiers of the NST and the NST DM; or

[0016] Determine the corresponding NST and NST DM according to the network slicing service requirements.

[0017] In some embodiments, it also includes:

[0018] If the network slicing service requirement indicates that the slicing service can share the network slicing instance NSI with other services, query all NSIs generated according to the NST. If there is an NSI that meets the network slicing service requirement, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirement, create a new NSI that meets the network slicing service requirement.

[0019] In some embodiments, after returning the network slice creation result to the CSMF, the method further includes:

[0020] Change the NST DM corresponding to the NSI;

[0021] Parsing the NSST and NSST DM of each subdomain in the changed NST DM, and determining the target subdomain where the NSST and / or NSST DM is changed;

[0022] Sending an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM;

[0023] Receive the slice subnet update result returned by NSSMF;

[0024] Complete configuration changes for end-to-end network slices;

[0025] Return the network slice update result to CSMF.

[0026] In some embodiments, before changing the NST DM corresponding to the NSI, the following steps are also included:

[0027] Receive CSMF's request to change NST DM.

[0028] An embodiment of the present invention further provides a method for deploying a network slice, which is performed by a network slice subnet management function NSSMF, and the method includes:

[0029] Receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST, and the NSST deployment model DM;

[0030] Create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM;

[0031] Perform network and service configuration of the network and network elements involved in NSSI, and complete the creation of slice subnets;

[0032] Return the slice subnet creation result to NSMF.

[0033] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0034] In some embodiments, if the subdomain where the NSSMF is located supports network function virtualization NFV, the method further includes:

[0035] Parsing the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and the NSST DM;

[0036] Initiate a network service NS creation request to the management and orchestration MANO, carrying the identifier of the NSD and the identifier of the NSD DF;

[0037] Receive the network service creation result returned by MANO, where the network service creation result is returned after MANO creates the network service according to NSD and NSDDF.

[0038] In some embodiments, after returning the slice subnet creation result to the NSMF, the method further includes:

[0039] receiving an NSSI change request from the NSMF, wherein the NSSI change request carries an identifier of a changed NSST and / or NSST DM;

[0040] Update NSSI and corresponding network resources according to the changed NSST and / or NSST DM;

[0041] Perform network and service change configurations for the changed networks and network elements within the subdomain and complete NSSI updates;

[0042] Return the slice subnet update result to NSMF.

[0043] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the method further includes:

[0044] Analyze the NSD logo and NSD DF logo in the changed NSST and / or NSST DM;

[0045] Initiate a change request of the network service NS to MANO, carrying the changed identifier of the NSD and the identifier of the NSD DF;

[0046] Receive the network service update result returned by MANO, where the network service update result is returned by MANO after updating the network service according to NSD and NSDDF.

[0047] An embodiment of the present invention further provides a network slice deployment device, which is applied to a network slice management function NSMF, and the device includes a transceiver and a processor:

[0048] The transceiver is used to receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement;

[0049] The processor is used to determine the corresponding network slice template NST and NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, and each NST DM represents a combination of a capability model and a resource model; parse the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, and decompose the network slice service demand into the demands of each subdomain according to the NST, wherein the NSST template includes multiple groups of NSST DMs, and each NSST DM represents a combination of a subdomain capability model and a resource model;

[0050] The transceiver is used to send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; and receive the slice subnet creation result returned by NSSMF;

[0051] The processor is used to complete the network and service configuration across the end-to-end network slice;

[0052] The transceiver is used to return the network slice creation result to CSMF.

[0053] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0054] In some embodiments, the request to create a network slice carries identifiers of NST and NST DM, and the processor is specifically used to determine the corresponding NST and NST DM based on the identifiers of the NST and NST DM; or, determine the corresponding NST and NST DM based on the network slice service requirements.

[0055] In some embodiments, the processor is also used to, if the network slicing service requirements indicate that the slice service can share the network slice instance NSI with other services, query all NSIs generated according to the NST, and if there is an NSI that meets the network slicing service requirements, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirements, create a new NSI that meets the network slicing service requirements.

[0056] In some embodiments, the processor is further configured to change the NST DM corresponding to the NSI; parse the NSST and NSST DM of each subdomain in the changed NST DM, and determine the target subdomain in which the NSST and / or NSST DM is changed;

[0057] The transceiver is also used to send an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM; and receive the slice subnet update result returned by the NSSMF;

[0058] The processor is also used to complete the configuration change of the end-to-end network slice;

[0059] The transceiver is also used to return the network slice update result to CSMF.

[0060] In some embodiments, the transceiver is further configured to receive a request from the CSMF to change the NST DM.

[0061] The embodiment of the present invention further provides a network slice deployment device, which is applied to a network slice subnet management function NSSMF, and the device includes a transceiver and a processor.

[0062] The transceiver is used to receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST and the NSST deployment model DM;

[0063] The processor is used to create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; perform network and service configuration of the network and network elements involved in the NSSI to complete the creation of the slice subnet;

[0064] The transceiver is used to return the slice subnet creation result to NSMF.

[0065] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0066] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the processor is further configured to parse an identifier of the network service template NSD and an identifier of the NSD deployment preference DF in the NSST and the NSST DM;

[0067] The transceiver is also used to initiate a network service NS creation request to the management and arrangement MANO, carrying the identifier of the NSD and the identifier of the NSD DF; receive the network service creation result returned by the MANO, and the network service creation result is returned after the MANO creates the network service according to the NSD and the NSD DF.

[0068] In some embodiments, the transceiver is further used to receive an NSSI change request from the NSMF, where the NSSI change request carries an identifier of the changed NSST and / or NSST DM;

[0069] The processor is further configured to update the NSSI and corresponding network resources according to the changed NSST and / or NSST DM; perform network and service change configuration of the changed network and network elements within the subdomain to complete the NSSI update;

[0070] The transceiver is also used to return the slice subnet update result to NSMF.

[0071] In some embodiments, if the subdomain where the NSSMF is located supports NFV,

[0072] The processor is further configured to parse the identifier of the NSD and the identifier of the NSD DF in the changed NSST and / or NSST DM;

[0073] The transceiver is also used to initiate a change request of the network service NS to MANO, carrying the changed identifier of the NSD and the identifier of the NSD DF; and receive the network service update result returned by MANO, where the network service update result is returned by MANO after updating the network service according to the NSD and the NSD DF.

[0074] An embodiment of the present invention also provides a network slicing deployment device, including a memory, a processor, and a computer program stored on the memory and executable on the processor; when the processor executes the program, the network slicing deployment method as described above is implemented.

[0075] In some embodiments, the network slice deployment device is applied to the network slice management function NSMF,

[0076] The processor is used to receive a network slice creation request from a communication service management function CSMF, wherein the network slice creation request carries network slice service requirements; determine the corresponding network slice template NST and NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, and each NST DM represents a combination of a capability model and a resource model; parse the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, and decompose the network slice service requirements into requirements of each subdomain according to the NST, wherein the NSST template includes multiple groups of NSST DMs, and each NSST DM represents a combination of a subdomain capability model and a resource model; send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; receive the slice subnet creation result returned by NSSMF; complete the network and service configuration of the end-to-end network slice across domains; and return the network slice creation result to CSMF.

[0077] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0078] In some embodiments, the processor is specifically used to determine the corresponding NST and NST DM according to the identifiers of the NST and NST DM if the request to create a network slice carries the identifiers of the NST and NST DM; or, determine the corresponding NST and NST DM according to the service requirements of the network slice.

[0079] In some embodiments, the processor is also used to, if the network slicing service requirements indicate that the slice service can share the network slice instance NSI with other services, query all NSIs generated according to the NST, and if there is an NSI that meets the network slicing service requirements, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirements, create a new NSI that meets the network slicing service requirements.

[0080] In some embodiments, the processor is also used to change the NST DM corresponding to the NSI; parse the NSST and NSST DM of each subdomain in the changed NST DM, and determine the target subdomain where the NSST and / or NSST DM is changed; send an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM; receive the slice subnet update result returned by the NSSMF; complete the configuration change of the end-to-end network slice; and return the network slice update result to the CSMF.

[0081] In some embodiments, the processor is further configured to receive a request from the CSMF to change the NST DM.

[0082] In some embodiments, the network slice deployment device is applied to NSSMF,

[0083] The processor is used to receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the slice subnet requirements, the network slice subnet template NSST, and the identifier of the NSST deployment model DM; creates NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; performs network and service configuration of the network and network elements involved in the NSSI to complete the slice subnet creation; and returns the slice subnet creation result to NSMF.

[0084] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0085] In some embodiments, the processor is further used to parse the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and NSST DM; initiate a network service NS creation request to the management and orchestration MANO, carrying the identifier of the NSD and the identifier of the NSD DF; receive the network service creation result returned by MANO, and the network service creation result is returned by MANO after creating the network service according to the NSD and NSD DF.

[0086] In some embodiments, the processor is also used to receive an NSSI change request from the NSMF, the NSSI change request carrying an identifier of a changed NSST and / or NSST DM; update the NSSI and corresponding network resources according to the changed NSST and / or NSST DM; perform network and service change configuration of the changed networks and network elements within the subdomain to complete the NSSI update; and return the slice subnet update result to the NSMF.

[0087] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the processor is further used to parse the identifier of the NSD and the identifier of the NSD DF in the changed NSST and / or NSST DM; initiate a change request for the network service NS to MANO, carrying the identifier of the changed NSD and the identifier of the NSD DF; receive the network service update result returned by MANO, and the network service update result is returned by MANO after updating the network service according to the NSD and NSD DF.

[0088] An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements the steps in the network slicing deployment method as described above.

[0089] The embodiments of the present invention have the following beneficial effects:

[0090] In the above solution, by supporting multiple deployment preferences of NST and NSST, multiple groups of specifications of NSI instances can be realized, and flexible switching of NSI instances between multiple groups of specifications can be realized without switching NST, so as to achieve a more accurate match between network resources and business needs, avoid resource waste, and save network resources in the early stage of network slicing construction; at the same time, it also avoids the operational complexity and peripheral impact caused by updating NSI instances by switching NST changes, shortening the update cycle. After supporting multiple deployment preferences of NST and NSST, NST and NSST can be designed and differentiated according to business scenarios, without the need for independent templates for each detailed specification, which can reduce the number of NST and NSST and reduce management difficulty. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Figure 1 It is a schematic diagram of the structure of a network slice management device;

[0092] Figure 2 Example diagrams for NST, NSST, and NSD;

[0093] Figure 3 A schematic diagram of the process of creating a network slice instance based on NST and NSST;

[0094] Figure 4An example diagram of NST, NSST and NSD with deployment preference according to an embodiment of the present invention;

[0095] Figure 5 A schematic diagram of a process for creating a network slice instance according to NST and NSST and deployment preferences in an embodiment of the present invention;

[0096] Figure 6 A schematic diagram of a process for switching a network slice instance deployment preference according to an embodiment of the present invention;

[0097] Figure 7 and Figure 8 This is a schematic diagram of the structure of a deployment device for network slicing according to an embodiment of the present invention;

[0098] Fig. 9 A schematic diagram of the composition of a deployment device for network slicing according to an embodiment of the present invention. DETAILED DESCRIPTION

[0099] In order to make the technical problems, technical solutions and advantages to be solved by the embodiments of the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0100] In order to manage network slice services and instances, 5G networks have added new network slice management functions, including: Communication Service Management Function CSMF (Communication Service Management Function), Network Slice Management Function NSMF (Network Slice Management Function) and Network Slice Subnet Management Function NSSMF (Network Slice Subnet Management Function). Network slice management devices such as Figure 1 As shown, MANO stands for Management and Orchestration.

[0101] In order to improve the efficiency and replicability of network slice creation and management, different network slice templates NST (Network Slice Template) and NSST (Network Slice Subnet Template) can be set according to different application scenarios and different capability requirements of network slices. NSI is created based on NST, and NSSI is created based on NSST. In addition to the basic information of the template itself, the network slice template mainly describes the capabilities (capability model) possessed by the NSI / NSSI generated according to this template and the resource combination form (resource model) corresponding to this capability. The capability model is a set of network slice performance and parameters (such as latency, number of users, bandwidth, etc.), and each parameter value is a numerical range that describes the capability (such as latency: 0-100ms; number of users: 500,000-5 million; bandwidth: 20Gbps-200Gbps, etc.). The resource model corresponding to the capability model is the combination of the corresponding wireless, transmission and core network slice subnet templates NSST for NST. For NSST, the resource model corresponds to the specific resource combination mode corresponding to the subnet. In particular, for subdomains that support network function virtualization NFV (Network Functions Virtualization) orchestration, such as the core network, the NSST resource model corresponds to the network service template NSD (Network Service Descriptor) that describes the combination of networks and network elements and a specific deployment preference DF (Deploy Flavor) corresponding to NSD. The relationship between templates at all levels and examples are as follows: Figure 2 shown.

[0102] The resource model in the template always corresponds to the capability model, because the resource combination form in the resource model needs to meet the capability requirements in the capability model to ensure that the NSI / NSSI created based on this template can meet the capability requirements. The capability requirements for NSI / NSSI creation are determined by the capability model of the template rather than by the requirements of the slice service it carries. If the slice service requirements exceed the capability range of NSI / NSSI, a new NSI / NSSI needs to be created based on the template of a larger capability model to carry the slice service.

[0103] During the process of network slice creation, CSMF will match the NST used according to the network slice service request, and then notify NSMF to create an NSI that can carry the slice service requirements based on this NST. NSMF will query whether a satisfactory NSI already exists based on the slice service requirements and NST. If it already exists, it will be used directly, otherwise a new NSI needs to be created. The process of creating a new NSI is actually the process of creating NSSIs in each subdomain. The information of NSST can be directly obtained through the resource model of NST. NSMF disassembles the slice service requirements into each subdomain, and then notifies each subdomain NSSMF to create NSSI according to the slice subnet requirements and NSST. Each subdomain NSSMF completes NSSI creation based on the resource model and slice subnet requirements in NSST. In particular, for subdomains that support NFV, such as the core network, NSSMF parses the NSD information in NSST and notifies MANO to complete the creation of network services. After completing the creation of network slice resources in each subdomain, NSSMF completes the network and service configuration, and NSMF completes the cross-domain network and service configuration to complete the entire end-to-end slice creation process. The process of network slice creation is as follows: Figure 3 shown.

[0104] The capability requirements for NSI creation are determined by the capability model of NST rather than by the requirements of the slice services it carries. That is to say, when NSI is initially created, even if the demand for the slice services it carries is not large, it is necessary to create an instance according to the capability model defined in the template. For example, the initial slice service demand carried on NSI only has a specification requirement of 500,000 users, but the capability model in NST is a capability model for 5 million users (because NSI will carry multiple slice services in the future). In this case, NSI needs to create relevant network resources according to the 5 million user specifications defined in the capability model at the initial deployment.

[0105] Although a smaller NST can be used to create NSI in the early stage of deployment, the instance can be updated by switching to a new NST when the slice service demand exceeds the instance capacity. However, since the change of NST involves the impact on slice contract subscription, billing, policy and many other links, the operation of switching NST is more complex, has a greater impact on the surrounding area, and has a longer cycle. In addition, it is necessary to prepare a variety of NSTs of different specifications according to the performance requirements of different deployment stages of different business scenarios, resulting in a large number of NSTs and inconvenient NST management.

[0106] On the other hand, for the core network supporting NFV virtualization, although the resource utilization rate can be adjusted by elastic expansion and contraction to solve the problem of resource waste, the elastic expansion and contraction is limited in the actual deployment process due to the reliability problems and increased maintenance difficulty caused by automatic network adjustment. Moreover, it can only be deployed in a single scenario for the core network supporting virtualization.

[0107] This embodiment implements the switching or updating of NSI specifications without changing NST by providing a combination of multiple capability models and resource models in NST and each sub-domain NSST. In the early stage of network slicing deployment, NSI can be created according to the capability model and resource model of the corresponding small specification. As the demand for slice services increases, the NSI specifications can be improved by switching the NST capability model rather than switching the NST itself. It is also possible to reduce the NSI specifications by switching the NST capability model as the demand for slice services decreases.

[0108] In this embodiment, NST DM (Deploy Model) is added to NST to represent a combination of a capability model and a resource model. Each NST DM has a corresponding ID. An NST can have multiple groups of NST DMs, and there is only one default NST DM (that is, the default NST DM). When the NST DM is not specified, the NSI is deployed according to the default NST DM.

[0109] NSST DM (Deploy Model) is added to NSST to represent the combination of a subdomain capability model and a resource model. Each NSST DM has a corresponding ID. An NSST can have multiple groups of NSST DMs. There is only one default NSST DM (that is, the default NSST DM). When no NSST DM is specified, NSSI is deployed according to the default NSST DM.

[0110] The resource models of different NST DMs can correspond to different NSSTs in a subdomain, or to different NSST DMs in the same NSST in a subdomain, or some NST DMs can correspond to NSST and other NST DMs can correspond to DMs of other NSSTs. NSSTDM can also be unspecified in the resource model. If the NSST DM ID is not specified, it means that the NSSI is deployed according to the default NSST DM of the NSST. In other words, during the NST DM switching process, the subdomain can implement NSSI updates by switching between different NSSTs, or by switching between different NSST DMs in the same NSST.

[0111] The resource models of different NSST DMs correspond to the resource combination models that meet the capability model requirements of the NSST DM in the subdomain. In particular, for the subdomain that supports NFV, such as the core network, the resource model of the NSST DM corresponds to the ID of the NSD and the ID of the NSD DF in MANO. The resource models of different NSST DMs can correspond to different NSDs in MANO, or to different NSD DFs of the same NSD in MANO, or some NSST DMs correspond to NSDs and other NSST DMs correspond to DFs of other NSDs. NSD DF can also be unspecified in the resource model. If the ID of NSD DF is not specified, it means that the network service is deployed according to the default NSD DF of the NSD. That is to say, during the NSST DM switching process, MANO can implement network service updates by switching different NSDs, or by switching different NSD DFs in the same NSD.

[0112] The relationship between NST, NSST, and NSD after adding NST and NSST deployment preferences and examples Figure 4 As shown, it can be seen that NST includes multiple ability preferences NST DM, NSST includes multiple ability preferences NSST DM, and there is a corresponding relationship between NST DM and NSST DM.

[0113] In this embodiment, the designer for NST and NSST template design adds the design capability of NST / NSST multiple deployment preferences. During the template design process, the designer can design the deployment preferences of multiple templates based on the prediction and planning of the future business development of such templates. The designer can specify the correspondence between the capability model and the resource model in the preference, as well as the correspondence between the resource model and the next level template and deployment preference.

[0114] During the creation of a network slice, when selecting NST, you need to specify the NST DM selected for the initial creation of the network slice. If you do not specify, the default NST DM will be used for creation. Once the NST DM is selected, the NSST of each subdomain and the DM of the NSST can be directly obtained from the resource model of the NST DM.

[0115] An embodiment of the present invention provides a method for deploying a network slice, which is performed by a network slice management function NSMF, and the method includes:

[0116] Receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement;

[0117] Determine a corresponding network slice template NST and an NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, each NST DM represents a combination of a capability model and a resource model;

[0118] Parsing the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, decomposing the network slice service requirements into requirements of each subdomain according to the NST, the NSST template including multiple groups of NSST DMs, each NSST DM representing a combination of a subdomain capability model and a resource model;

[0119] Send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain;

[0120] Receive the slice subnet creation result returned by NSSMF;

[0121] Complete cross-domain network and service configuration for end-to-end network slicing;

[0122] Return the network slice creation result to CSMF.

[0123] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0124] In some embodiments, determining the corresponding NST and NST DM according to the create network slice request includes:

[0125] The network slice creation request carries the identifiers of the NST and the NST DM, and the corresponding NST and NST DM are determined according to the identifiers of the NST and the NST DM; or

[0126] Determine the corresponding NST and NST DM according to the network slicing service requirements.

[0127] In some embodiments, it also includes:

[0128] If the network slicing service requirement indicates that the slicing service can share the network slicing instance NSI with other services, query all NSIs generated according to the NST. If there is an NSI that meets the network slicing service requirement, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirement, create a new NSI that meets the network slicing service requirement.

[0129] In some embodiments, after returning the network slice creation result to the CSMF, the method further includes:

[0130] Change the NST DM corresponding to the NSI;

[0131] Parsing the NSST and NSST DM of each subdomain in the changed NST DM, and determining the target subdomain where the NSST and / or NSST DM is changed;

[0132] Sending an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM;

[0133] Receive the slice subnet update result returned by NSSMF;

[0134] Complete configuration changes for end-to-end network slices;

[0135] Return the network slice update result to CSMF.

[0136] In some embodiments, before changing the NST DM corresponding to the NSI, the following steps are also included:

[0137] Receive CSMF's request to change NST DM.

[0138] An embodiment of the present invention further provides a method for deploying a network slice, which is performed by a network slice subnet management function NSSMF, and the method includes:

[0139] Receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST, and the NSST deployment model DM;

[0140] Create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM;

[0141] Perform network and service configuration of the network and network elements involved in NSSI, and complete the creation of slice subnets;

[0142] Return the slice subnet creation result to NSMF.

[0143] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0144] In some embodiments, if the subdomain where the NSSMF is located supports network function virtualization NFV, the method further includes:

[0145] Parsing the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and the NSST DM;

[0146] Initiate a network service NS creation request to the management and orchestration MANO, carrying the identifier of the NSD and the identifier of the NSD DF;

[0147] Receive the network service creation result returned by MANO, where the network service creation result is returned after MANO creates the network service according to NSD and NSDDF.

[0148] In some embodiments, after returning the slice subnet creation result to the NSMF, the method further includes:

[0149] receiving an NSSI change request from the NSMF, wherein the NSSI change request carries an identifier of a changed NSST and / or NSST DM;

[0150] Update NSSI and corresponding network resources according to the changed NSST and / or NSST DM;

[0151] Perform network and service change configurations for the changed networks and network elements within the subdomain and complete NSSI updates;

[0152] Return the slice subnet update result to NSMF.

[0153] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the method further includes:

[0154] Analyze the NSD logo and NSD DF logo in the changed NSST and / or NSST DM;

[0155] Initiate a change request of the network service NS to MANO, carrying the changed identifier of the NSD and the identifier of the NSD DF;

[0156] Receive the network service update result returned by MANO, where the network service update result is returned by MANO after updating the network service according to NSD and NSDDF.

[0157] In a specific embodiment, after supporting NST DM and NSST DM, the process of creating a network slice is as follows: Figure 5 As shown, the following steps are included:

[0158] Step 1: After CSMF receives the activation order for the network slicing service product, it selects the appropriate NST template and the initially created NST DM according to the customer's network slicing service requirements, and then calls the NSMF interface to initiate a network slicing creation request to NSMF. The network slicing creation request carries the network slicing service requirements and the ID of the NST and the ID of the NST DM. Another solution is that CSMF does not select NST, but only sends the network slicing service requirements to NSMF, and NSMF selects NST and NST DM;

[0159] Step 2: NSMF receives the network slice creation request sent by CSMF. If the network slice creation request does not carry the NST template and NST DM, NSMF needs to select the appropriate NST template and the initially created NST DM according to the network slice service requirements;

[0160] Step 3: If the network slicing service requirement indicates that the slice service can share the NSI with other services, the NSMF queries all NSIs generated according to the selected NST, and evaluates whether they can meet the current network slicing service requirements one by one. If they can, it means that the existing NSI is available, and the association between the network slicing service and the NSI is directly established; otherwise, a new NSI needs to be created;

[0161] Step 4: NSMF parses the NSST ID and NSST DM of each subdomain in the NST template and NST DM resource model. Then, according to the template, the network slice service requirements are divided into the requirements of each subdomain (including wireless, transmission and core network);

[0162] Step 5: NSMF calls the interfaces of wireless, transmission and core network NSSMFs respectively to initiate NSSI creation requests to each subdomain, carrying the slice subnet requirements decomposed into each subdomain and the NSST ID and NSST DM of each subdomain parsed from NST;

[0163] Step 6: Each subdomain NSSMF creates a slice subnet instance NSSI and corresponding network resources according to the slice subnet requirements, the NSST template and the resource model in the corresponding DM;

[0164] Step 7: For the subdomain supporting NFV (such as the core network), parse the NSST template and the ID of the NSD and the ID of the NSD DF in the corresponding NSST DM resource model;

[0165] Step 8: The subdomain supporting NFV (such as the core network) initiates a request to create a network service NS to MANO, carrying the IDs of NSDID and NSD DF;

[0166] Step 9: MANO creates a network service according to NSD and DF, including the network elements and networks included in the network service;

[0167] Step 10, MANO returns the network service creation result to NSSMF;

[0168] Step 11: NSSMF completes the network and service configuration of the network and network elements involved in NSSI. Completes the creation of the slice subnet;

[0169] Step 12: NSSMF returns the slice subnet creation result to NSMF;

[0170] Step 13: NSMF completes the cross-domain network and service configuration of the end-to-end network slice and completes the creation of the end-to-end network slice;

[0171] Step 14. NSMF returns the network slice creation result to CSMF.

[0172] Among them, NST DM can be specified for creation during the network slice creation process, and the transmission of NST DM information is added to the network slice creation interface of CSMF-NSMF. NSST DM is directly parsed from NST DM and carried and passed to NSSMF in the network slice subnet creation interface of NSMF-NSSMF, and NSSMF creates NSSI according to NSST DM.

[0173] During the operation of the network slicing instance, as the network slicing services carried by the NSI increase or the network slicing service requirements change, the specifications initially deployed may no longer be able to meet the service requirements, and the new service requirements are included in the maximum capability specifications of the NST template. In this case, the NSI can be updated by switching to a larger-specification NST DM.

[0174] Another scenario is that as the number of network slice services carried by NSI decreases or the demand for network slice services decreases, the currently deployed specifications may be far higher than the actual business needs, which may lead to a waste of network resources. At this time, the NSI can be updated by switching to a smaller-specification NST DM to achieve a better match between resources and demand.

[0175] In a specific embodiment, the process of updating the NSI by switching the network slice instance deployment preference is as follows: Figure 6 As shown, the following steps are included:

[0176] Step 1, including the following two situations:

[0177] (a) The operation of changing NST DM can be performed on CSMF;

[0178] (b) Because NSI is updated within the capabilities of NST and does not affect the network slice services carried on it, the NST DM change operation can also be performed directly on NSMF;

[0179] Step 2: NSMF parses the NSST ID and NSST DM of each subdomain in the new NST DM resource model, and then analyzes which subdomains have changed NSST or NSST DM. It only needs to send change requests to the subdomains where NSST or NSST DM has changed.

[0180] Step 3: NSMF sends an NSSI change request to the subdomain NSSMF where the NSST or NSST DM has changed, carrying the new NSST ID or the new NSST DM ID;

[0181] Step 4: NSSMF updates NSSI and corresponding network resources according to the new NSST template or the resource model in the new NSST DM;

[0182] Step 5: For the subdomain supporting NFV (such as core network), parse the NSD ID and NSD DF in the new NSST template or the new NSST DM resource model;

[0183] Step 6: The subdomain supporting NFV (such as the core network) initiates a change request for the network service NS to MANO, carrying a new NSD ID or a new NSD DF;

[0184] Step 7: MANO updates the network and network elements involved in the network service according to NSD and DF;

[0185] Step 8: MANO returns the network service update result to NSSMF;

[0186] Step 9: NSSMF completes the network and service change configuration of the changed network and network elements within the subdomain, and completes the NSSI update;

[0187] Step 10: NSSMF returns the slice subnet update result to NSMF;

[0188] Step 11: NSMF completes the configuration change of the changed part of the end-to-end network slice and completes the NSI update;

[0189] Step 12. NSMF returns the network slice update result to CSMF.

[0190] In this embodiment, the update of the NSI instance can be completed by switching the NST DM to achieve the switching of different deployment preferences. The transmission of new NST DM information is added to the network slice instance update interface of CSMF-NSMF. After the change, the new NSST DM is directly parsed from the new NST DM and carried in the network slice subnet instance update interface of NSMF-NSSMF. It is passed to NSSMF, and NSSMF updates the NSSI according to the new NSST DM.

[0191] The embodiment of the present invention also provides a network slice deployment device, which is applied to a network slice management function NSMF, such as Figure 7 As shown, the device includes a transceiver 11 and a processor 12:

[0192] The transceiver 11 is used to receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement;

[0193] The processor 12 is used to determine the corresponding network slice template NST and NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, and each NST DM represents a combination of a capability model and a resource model; parse the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, and decompose the network slice service demand into the demands of each subdomain according to the NST, wherein the NSST template includes multiple groups of NSSTDMs, and each NSST DM represents a combination of a subdomain capability model and a resource model;

[0194] The transceiver 11 is used to send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; and receive the slice subnet creation result returned by NSSMF;

[0195] The processor 12 is used to complete the network and service configuration across the end-to-end network slice;

[0196] The transceiver 11 is used to return the network slice creation result to CSMF.

[0197] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0198] In some embodiments, the request to create a network slice carries identifiers of NST and NST DM, and the processor 12 is specifically used to determine the corresponding NST and NST DM based on the identifiers of the NST and NST DM; or, determine the corresponding NST and NST DM based on the network slice service requirements.

[0199] In some embodiments, the processor 12 is also used to, if the network slicing service demand indicates that the slice service can share the network slice instance NSI with other services, query all NSIs generated according to the NST, and if there is an NSI that meets the network slicing service demand, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service demand, create a new NSI that meets the network slicing service demand.

[0200] In some embodiments, the processor 12 is further configured to change the NST DM corresponding to the NSI; parse the NSST and NSST DM of each subdomain in the changed NST DM, and determine the target subdomain where the NSST and / or NSST DM is changed;

[0201] The transceiver 11 is also used to send an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM; and receive the slice subnet update result returned by the NSSMF;

[0202] The processor 12 is also used to complete the configuration change of the end-to-end network slice;

[0203] The transceiver 11 is also used to return the network slice update result to the CSMF.

[0204] In some embodiments, the transceiver 11 is further configured to receive a request from the CSMF to change the NST DM.

[0205] The embodiment of the present invention also provides a network slice deployment device, which is applied to the network slice subnet management function NSSMF, such as Figure 8 As shown, the device includes a transceiver 21 and a processor 22.

[0206] The transceiver 21 is used to receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, where the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST, and the NSST deployment model DM;

[0207] The processor 22 is used to create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; perform network and service configuration of the network and network elements involved in the NSSI to complete the creation of the slice subnet;

[0208] The transceiver 21 is used to return the slice subnet creation result to NSMF.

[0209] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0210] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the processor 22 is further configured to parse the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and the NSST DM;

[0211] The transceiver 21 is further used to initiate a network service NS creation request to the management and arrangement MANO, carrying the identifier of the NSD and the identifier of the NSD DF; and receive a network service creation result returned by the MANO, where the network service creation result is returned after the MANO creates the network service according to the NSD and the NSD DF.

[0212] In some embodiments, the transceiver 21 is further configured to receive an NSSI change request from the NSMF, wherein the NSSI change request carries an identifier of the changed NSST and / or NSST DM;

[0213] The processor 22 is further configured to update the NSSI and corresponding network resources according to the changed NSST and / or NSST DM; perform network and service change configuration of the changed network and network elements within the subdomain to complete the NSSI update;

[0214] The transceiver 21 is also used to return the slice subnet update result to the NSMF.

[0215] In some embodiments, if the subdomain where the NSSMF is located supports NFV,

[0216] The processor 22 is further configured to parse the identifier of the NSD and the identifier of the NSD DF in the changed NSST and / or NSST DM;

[0217] The transceiver 21 is further used to initiate a change request of the network service NS to MANO, carrying the changed identifier of the NSD and the identifier of the NSD DF; and receive the network service update result returned by MANO, where the network service update result is returned by MANO after updating the network service according to the NSD and the NSD DF.

[0218] The embodiment of the present invention also provides a network slice deployment device, such as Fig. 9As shown, it includes a memory 31, a processor 32, and a computer program stored in the memory 31 and executable on the processor 32; when the processor 32 executes the program, the network slicing deployment method as described above is implemented.

[0219] In some embodiments, the network slice deployment device is applied to the network slice management function NSMF,

[0220] The processor 32 is used to receive a network slice creation request from a communication service management function CSMF, wherein the network slice creation request carries network slice service requirements; determine the corresponding network slice template NST and NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, and each NST DM represents a combination of a capability model and a resource model; parse the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, and decompose the network slice service requirements into requirements of each subdomain according to the NST, wherein the NSST template includes multiple groups of NSST DMs, and each NSST DM represents a combination of a subdomain capability model and a resource model; send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; receive the slice subnet creation result returned by NSSMF; complete the network and service configuration of the end-to-end network slice across domains; and return the network slice creation result to CSMF.

[0221] In some embodiments, the plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

[0222] In some embodiments, the processor 32 is specifically used to determine the corresponding NST and NST DM according to the identifiers of the NST and NST DM if the request to create a network slice carries the identifiers of the NST and NSTDM; or, determine the corresponding NST and NST DM according to the service requirements of the network slice.

[0223] In some embodiments, the processor 32 is also used to, if the network slicing service requirements indicate that the slice service can share the network slice instance NSI with other services, query all NSIs generated according to the NST, and if there is an NSI that meets the network slicing service requirements, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirements, create a new NSI that meets the network slicing service requirements.

[0224] In some embodiments, the processor 32 is also used to change the NST DM corresponding to the NSI; parse the NSST and NSST DM of each subdomain in the changed NST DM, and determine the target subdomain where the NSST and / or NSST DM is changed; send an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM; receive the slice subnet update result returned by the NSSMF; complete the configuration change of the end-to-end network slice; and return the network slice update result to the CSMF.

[0225] In some embodiments, the processor 32 is further configured to receive a request from the CSMF to change the NST DM.

[0226] In some embodiments, the network slice deployment device is applied to NSSMF,

[0227] The processor 32 is used to receive a network slice subnet instance NSSI creation request from the network slice management function NSMF, and the NSSI creation request carries the slice subnet requirements, the network slice subnet template NSST and the identifier of the NSST deployment model DM; creates NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; performs network and service configuration of the network and network elements involved in the NSSI to complete the slice subnet creation; and returns the slice subnet creation result to NSMF.

[0228] In some embodiments, the NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a sub-domain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

[0229] In some embodiments, the processor 32 is further used to parse the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and NSST DM; initiate a request to create a network service NS to the management and orchestration MANO, carrying the identifier of the NSD and the identifier of the NSD DF; receive a network service creation result returned by MANO, and the network service creation result is returned by MANO after creating the network service according to the NSD and NSD DF.

[0230] In some embodiments, the processor 32 is also used to receive an NSSI change request from the NSMF, the NSSI change request carrying an identifier of the changed NSST and / or NSST DM; update the NSSI and corresponding network resources according to the changed NSST and / or NSST DM; perform network and service change configuration of the changed networks and network elements within the subdomain to complete the NSSI update; and return the slice subnet update result to the NSMF.

[0231] In some embodiments, if the subdomain where the NSSMF is located supports NFV, the processor 32 is further used to parse the identifier of the NSD and the identifier of the NSD DF in the changed NSST and / or NSST DM; initiate a change request for the network service NS to the MANO, carrying the identifier of the changed NSD and the identifier of the NSD DF; receive the network service update result returned by the MANO, and the network service update result is returned by the MANO after updating the network service according to the NSD and the NSD DF.

[0232] An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements the steps in the network slicing deployment method as described above.

[0233] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage terminal devices to be detected or any other non-transmission media that can be used to store information that can be accessed by the computer terminal device to be detected. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carriers.

[0234] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for deploying a network slice, characterized in that: The method is performed by a network slice management function NSMF, and includes: Receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement; Determine a corresponding network slice template NST and an NST deployment model DM according to the network slice creation request, wherein the NST includes multiple groups of NST DMs, each NST DM represents a combination of a capability model and a resource model; Parsing the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, decomposing the network slice service requirements into requirements of each subdomain according to the NST, the NSST template including multiple groups of NSSTDMs, each NSST DM representing a combination of a subdomain capability model and a resource model; Send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; Receive the slice subnet creation result returned by NSSMF; Complete cross-domain network and service configuration for end-to-end network slicing; Return the network slice creation result to CSMF.

2. The method for deploying a network slice according to claim 1, characterized in that: The plurality of sets of NST DMs include a default NST DM, and the plurality of sets of NSST DMs include a default NSST DM.

3. The method for deploying a network slice according to claim 1, characterized in that: Determining the corresponding NST and NST DM according to the network slice creation request includes: The network slice creation request carries the identifiers of the NST and the NST DM, and the corresponding NST and NST DM are determined according to the identifiers of the NST and the NST DM; or Determine the corresponding NST and NST DM according to the network slicing service requirements.

4. The method for deploying a network slice according to claim 1, characterized in that: Also includes: If the network slicing service requirement indicates that the slicing service can share the network slicing instance NSI with other services, query all NSIs generated according to the NST. If there is an NSI that meets the network slicing service requirement, establish an association between the network slicing service and the NSI; if there is no NSI that meets the network slicing service requirement, create a new NSI that meets the network slicing service requirement.

5. The method for deploying network slices according to claim 4, characterized in that: After returning the network slice creation result to the CSMF, the method further includes: Change the NST DM corresponding to the NSI; Parsing the NSST and NSST DM of each subdomain in the changed NST DM, and determining the target subdomain where the NSST and / or NSST DM is changed; Sending an NSSI change request to the NSSMF of the target subdomain, carrying the identifier of the changed NSST and / or NSST DM; Receive the slice subnet update result returned by NSSMF; Complete configuration changes for end-to-end network slices; Return the network slice update result to CSMF.

6. The method for deploying network slices according to claim 5, characterized in that: Before changing the NST DM corresponding to the NSI, it also includes: Receive CSMF's request to change NST DM.

7. A method for deploying a network slice, characterized in that: Executed by the network slice subnet management function NSSMF, the method includes: Receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST, and the NSST deployment model DM; Create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; Perform network and service configuration of the network and network elements involved in NSSI, and complete the creation of slice subnets; Return the slice subnet creation result to NSMF; The NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a subdomain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

8. The method for deploying network slices according to claim 7, characterized in that: If the subdomain where the NSSMF is located supports network function virtualization NFV, the method further includes: Parsing the identifier of the network service template NSD and the identifier of the NSD deployment preference DF in the NSST and the NSST DM; Initiate a network service NS creation request to the management and orchestration MANO, carrying the identifier of the NSD and the identifier of the NSD DF; Receive the network service creation result returned by MANO, where the network service creation result is returned after MANO creates the network service according to NSD and NSD DF.

9. The method for deploying network slices according to claim 7, characterized in that: After returning the slice subnet creation result to the NSMF, the method further includes: receiving an NSSI change request from the NSMF, wherein the NSSI change request carries an identifier of a changed NSST and / or NSST DM; Update NSSI and corresponding network resources according to the changed NSST and / or NSST DM; Perform network and service change configurations for the changed networks and network elements within the subdomain and complete NSSI updates; Return the slice subnet update result to NSMF.

10. The method for deploying network slices according to claim 9, characterized in that: If the subdomain where the NSSMF is located supports NFV, the method further includes: Analyze the NSD logo and NSD DF logo in the changed NSST and / or NSST DM; Initiate a change request of the network service NS to MANO, carrying the changed identifier of the NSD and the identifier of the NSD DF; Receive the network service update result returned by MANO, where the network service update result is returned by MANO after updating the network service according to NSD and NSD DF.

11. A network slice deployment device, characterized in that: Applied to the network slice management function NSMF, the device includes a transceiver and a processor: The transceiver is used to receive a network slice creation request from a communication service management function CSMF, where the network slice creation request carries a network slice service requirement; The processor is used to determine the corresponding network slice template NST and NST deployment model DM according to the request to create a network slice, wherein the NST includes multiple groups of NST DMs, and each NST DM represents a combination of a capability model and a resource model; parse the network slice subnet template NSST template and NSST DM of each subdomain in the NST and the NST DM, and decompose the network slice service demand into the demands of each subdomain according to the NST, wherein the NSST template includes multiple groups of NSST DMs, and each NSST DM represents a combination of a subdomain capability model and a resource model; The transceiver is used to send a network slice subnet instance NSSI creation request to the network slice subnet management function NSSMF of each subdomain, carrying the slice subnet requirements, NSST and NSST DM identifiers of each subdomain; Receive the slice subnet creation result returned by NSSMF; The processor is used to complete the network and service configuration across the end-to-end network slice; The transceiver is used to return the network slice creation result to CSMF.

12. A network slice deployment device, characterized in that: Applied to a network slicing subnet management function NSSMF, the device comprises a transceiver and a processor, The transceiver is used to receive a network slice subnet instance NSSI creation request from a network slice management function NSMF, wherein the NSSI creation request carries the identification of the slice subnet requirement, the network slice subnet template NSST and the NSST deployment model DM; The processor is used to create NSSI and corresponding network resources according to the slice subnet requirements and the resource models in the NSST and NSST DM; Perform network and service configuration of the network and network elements involved in NSSI, and complete the creation of slice subnets; The transceiver is used to return the slice subnet creation result to the NSMF; The NSST includes multiple groups of NSST DMs, each NSST DM represents a combination of a subdomain capability model and a resource model, and the multiple groups of NSST DMs include a default NSST DM.

13. A network slice deployment device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, it implements the network slice deployment method as described in any one of claims 1-10.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, it implements the steps in the network slice deployment method as described in any one of claims 1-10.

Images