A method for processing network slicing services and related equipment

Abstract

This invention discloses a method and related equipment for processing network slicing services, relating to the field of communication technology. The method includes: receiving a network slice termination request sent by the Network Slice Management Function (NSMF) of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI to be shut down, an identifier of a network slice instance NSI of the non-shared network, and an identifier of a network slice instance SNSI of the shared network, and SNSI, S-NSSAI, and NSI are mutually bound; if, based on the identifiers of S-NSSAI, NSI, and SNSI, it is determined that the network slice service corresponding to S-NSSAI is the last service associated with SNSI, and NSI is the last NSI associated with SNSI, then the binding relationship between SNSI, S-NSSAI, and NSI is released. This invention improves the efficiency of network slicing service activation.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a method for processing network slicing services and related equipment. Background Art

[0002] With the development of communication technology, network slicing technology has emerged. As different communication operators are increasingly cooperating in business and resources such as wireless spectrum are scarce, in order to make more full use of scarce network resources, the concept of shared network has been proposed, that is, the non-shared networks of various operators are connected through a shared network to realize the resource division of network slicing services.

[0003] The resource division of the operator's network slicing service is achieved on the basis of the binding relationship between the network slicing service, the network slicing instance of the non-shared network and the network slicing instance of the shared network. When the operator's network slicing service is activated, it is necessary to create a network slicing instance in the shared network and bind it to the network slicing service. However, the creation time of the network slicing instance is relatively long, which makes the activation efficiency of the network slicing service low. Summary of the invention

[0004] The embodiments of the present invention provide a method and related equipment for processing network slicing services to solve the problem of low activation efficiency of network slicing services.

[0005] To solve the above technical problems, the present invention is achieved as follows:

[0006] In a first aspect, an embodiment of the present invention provides a method for processing a network slice service, which is applied to a network slice management function SNSMF of a shared network, and the method includes:

[0007] Receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other;

[0008] When it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI, and the NSI is the last NSI associated with the SNSI, the binding relationship between the SNSI, the S-NSSAI and the NSI is released.

[0009] In a second aspect, an embodiment of the present invention provides a method for processing a network slicing service, which is applied to SNSSMF, and the method includes:

[0010] Receive a network slice subnet termination request sent by the SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, and SNSSI identifier;

[0011] When it is determined based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI, the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI is released.

[0012] In a third aspect, an embodiment of the present invention further provides a method for processing a network slicing service, which is applied to MANO, and the method includes:

[0013] Receive a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier, and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

[0014] When it is determined according to the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance, the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released;

[0015] Send the virtual network element instance termination result to SNSSMF.

[0016] In a fourth aspect, an embodiment of the present invention further provides a method for processing a network slicing service, which is applied to NSMF, and the method includes:

[0017] Receive a service suspension request carrying S-NSSAI sent by the communication service management function CSMF;

[0018] When the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI, release the binding relationship between the S-NSSAI and the NSI;

[0019] Send a network slice termination request to the SNSMF so that the SNSMF releases the binding relationship between SNSI, S-NSSAI and NSI;

[0020] Receiving the target termination result sent by SNSMF, wherein, when SNSSMF receives the virtual network element instance termination result sent by MANO, the network slice subnet termination result of the shared network and the virtual network element instance termination result are sent to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the network slice subnet termination result of the shared network, and the termination result of the network slice of the shared network;

[0021] Send the target termination result to the CSMF.

[0022] In a fifth aspect, an embodiment of the present invention further provides an SNSMF, including:

[0023] A first receiving module is used to receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other;

[0024] The first release module is used to release the binding relationship between the SNSI, the S-NSSAI and the NSI when it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI and the NSI is the last NSI associated with the SNSI.

[0025] In a sixth aspect, an embodiment of the present invention further provides a SNSSMF, including:

[0026] A second receiving module is used to receive a network slice subnet termination request sent by the SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier and SNSSI identifier;

[0027] The second release module is used to release the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI when it is determined, based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI.

[0028] In a seventh aspect, an embodiment of the present invention further provides a MAMO, including:

[0029] A third receiving module is used to receive a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier, and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

[0030] A third release module is used to release the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI, the NSSI and the SNSSI when it is determined that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance according to the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance;

[0031] The first sending module is used to send the virtual network element instance termination result to the SNSSMF.

[0032] In an eighth aspect, an embodiment of the present invention further provides a NSMF, including:

[0033] A fourth receiving module is used to receive a service suspension request of S-NSSAI sent by the communication service management function CSMF;

[0034] A fourth release module is used to release the binding relationship between the S-NSSAI and the NSI when the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI;

[0035] The second sending module is used to send a network slice termination request to the SNSMF, so that the SNSMF releases the binding relationship between the SNSI, the S-NSSAI and the NSI;

[0036] The fourth receiving module is further used to receive a target termination result sent by SNSMF, wherein, when SNSSMF receives the termination result of the virtual network element instance sent by MANO, the network slice subnet termination result of the shared network and the termination result of the virtual network element instance are sent to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the termination result of the network slice subnet of the shared network, and the termination result of the network slice of the shared network;

[0037] The second sending module is used to send the target termination result to the CSMF.

[0038] In the ninth aspect, an embodiment of the present invention also provides a network device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for processing network slicing services as described above.

[0039] In the tenth aspect, an embodiment of the present invention also provides a computer-readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method for processing the network slicing service as described above are implemented.

[0040] In an embodiment of the present invention, a network slice management function SNSMF of a shared network receives a network slice termination request sent by a network slice management function NSMF of a non-shared network, and according to the network slice termination request carrying a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of the non-shared network, and an identifier of the SNSI, it is determined that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI, and the NSI is the last NSI associated with the SNSI, and then the binding relationship between the SNSI, S-NSSAI and the NSI is released, thereby releasing the network slice instance SNSI in the shared network from the binding relationship between the network slice service requested to be stopped and the network slice instance of the non-shared network, thereby enabling the network slice instance SNSI in the shared network to be used by subsequent network slice services, eliminating the process of creating a new SNSI for subsequent network slice services, and improving the activation efficiency of network slice services. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0042] Figure 1 A schematic diagram of the structures of non-shared networks and shared networks of different operators provided in an embodiment of the present invention;

[0043] Figure 2 A flowchart of a method for processing a network slicing service provided by an embodiment of the present invention;

[0044] Figure 3 A flowchart of another method for processing a network slicing service provided by an embodiment of the present invention;

[0045] Figure 4 A flowchart of another method for processing a network slicing service provided by an embodiment of the present invention;

[0046] Figure 5 A flowchart of a method for processing yet another network slicing service provided by an embodiment of the present invention;

[0047] Figure 6 An interactive flow chart of a method for processing a network slicing service provided in an embodiment of the present invention;

[0048] Figure 7 A structural diagram of the SNSMF provided in an embodiment of the present invention;

[0049] Figure 8 A structural diagram of the SNSSMF provided in an embodiment of the present invention;

[0050] Fig. 9 A structural diagram of a MANO provided in an embodiment of the present invention;

[0051] Fig.10 A structural diagram of the NSMF provided by an embodiment of the present invention;

[0052] Fig.11 A schematic diagram of the hardware structure of a network device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0053] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0054] To help better understand the embodiments of the present invention, before introducing this solution, a schematic diagram of the structure of non-shared networks and shared networks of different operators is given below. Figure 1 As shown, the non-shared network includes a communication service management function CSMF (Communication Service Management Function), a network slice management function NSMF (Network Slice Management Function) and a network slice subnet management function NSSMF (Network SliceSubnet Management Function) which are connected in sequence. CSMF completes the deployment and termination of network slice instances by interacting with NSMF, each subdomain NSSMF and the virtualization resource orchestration management function MANO to realize the activation and shutdown of network slice services. The shared network includes SNSMF and SNSSMF connected to SNSMF. SNSMF is the network slice management function of the shared network, and SNSSMF is the network slice subnet management function of the shared network. The NSMFs of different non-shared networks are connected through SNSMF.

[0055] In an embodiment of the present invention, the network slice instance SNSI of the shared network is released from the binding relationship between the network slice service requested to be shut down and the network slice instance of the non-shared network, so that the SNSI can be used by subsequent network slice services, eliminating the process of creating a new SNSI for subsequent network slice services, thereby improving the activation efficiency of the network slice services.

[0056] See also Figure 2 , Figure 2 A flowchart of a method for processing a network slice service provided in an embodiment of the present invention is applied to a network slice management function SNSMF of a shared network, such as Figure 2 As shown, the following steps are included:

[0057] Step S201, receiving a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries an identifier of a network slice service S-NSSAI requested to be shut down, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other.

[0058] When an operator needs to shut down a certain network slice service, it can send a network slice service shutdown request to NSMF on CSMF in a non-shared network. The network slice service shutdown request carries the identifier S-NSSAI of the network slice service requested to be shut down. After receiving the network slice service shutdown request, NSMF first deletes the service configuration of the network slice service represented by S-NSSAI. NSMF stores the binding relationship between S-NSSAI and the identifier of the network slice instance NSI, and NSI may have a binding relationship with multiple network slice services at the same time, that is, multiple network slice services share one NSI. If the network slice service corresponding to S-NSSAI is the last service associated with NSI, it can be determined that NSI is only bound to the network slice service requested to be shut down. At this time, NSMF releases the binding relationship between S-NSSAI and NSI, thereby releasing NSI from the binding relationship, so that NSI can be used by the operator's subsequent network slice services.

[0059] NSMF also stores the binding relationship between the NSI identifier, S-NSSAI and the identifier of the network slice instance SNSI of the shared network. The NSI identifier, S-NSSAI and SNSI identifier are bound to each other. After NSMF releases the binding relationship between NSI and S-NSSAI, NSMF generates a network slice termination request based on the binding relationship between the NSI identifier, S-NSSAI and SNSI identifier. It can be understood that the network slice termination request carries the mutually bound NSI identifier, S-NSSAI identifier and SNSI identifier. NSMF then sends the network slice termination request to SNSMF.

[0060] Step S202: When it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI and the NSI is the last NSI associated with the SNSI, the binding relationship between the SNSI, the S-NSSAI and the NSI is released.

[0061] After receiving the network slice termination request, SNSMF parses the network slice termination request to obtain the NSI identifier, the S-NSSAI identifier and the SNSI identifier. The binding relationship between S-NSSAI, NSI and SNSI is stored in SNSMF. SNSMF first finds the corresponding SNSI based on the SNSI identifier, and determines whether the network slice service corresponding to S-NSSAI is the last service associated with SNSI. If the network slice service corresponding to S-NSSAI is the last service associated with SNSI, it can be determined that SNSI is only bound to the network slice service requested to be stopped. SNSMF determines whether NSI is the last NSI associated with SNSI. If NSI is the last NSI associated with SNSI, it can be determined that SNSI is only bound to the NSI bound to the network slice service requested to be stopped. At this time, SNSMF releases the binding relationship between SNSI, S-NSSAI and NSI, thereby releasing all binding relationships of SNSI, that is, releasing SNSI.

[0062] Since the released SNSI is not bound to any NSI or network slicing service, the operator can make a simple change to the SNSI when opening a new network slicing service, and then bind the changed SNSI with the identifier of the new network slicing service and the NSI bound to the identifier of the network slicing service. There is no need to create a new SNSI for the new network slicing service, which improves the efficiency of opening the network slicing service.

[0063] According to the method for processing network slicing services in an embodiment of the present invention, a network slice management function SNSMF of a shared network receives a network slice termination request sent by a network slice management function NSMF of a non-shared network, and according to the network slice termination request carrying a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of the non-shared network, and an identifier of the SNSI, it is determined that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI, and the NSI is the last NSI associated with the SNSI, then the binding relationship between the SNSI, S-NSSAI and NSI is released, thereby releasing the network slice instance SNSI in the shared network from the binding relationship between the network slice service requested to be stopped and the network slice instance of the non-shared network, thereby enabling the network slice instance SNSI in the shared network to be used by subsequent network slice services, eliminating the process of creating a new SNSI for subsequent network slice services, and improving the activation efficiency of network slice services.

[0064] Optionally, after the SNSMF releases the binding relationship between the SNSI, the S-NSSAI and the NSI, that is, after step S202, the method further includes:

[0065] A network slice subnet termination request is sent to the network slice subnet management function SNSSMF of the shared network, so that the SNSSMF releases the binding relationship between the network slice subnet instance SNSSI, the S-NSSAI, the NSI and the SNSI of the shared network.

[0066] SNSMF also stores the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier and the identifier of the network slice subnet instance SNSSI of the shared network. The NSI identifier, S-NSSAI, SNSI identifier and SNSSI identifier are bound to each other. After SNSMF releases the binding relationship between SNSI, S-NSSAI and NSI, SNSMF generates a network slice subnet termination request based on the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier and SNSSI identifier. It can be understood that the network slice subnet termination request carries the mutually bound NSI identifier, S-NSSAI identifier, SNSI identifier and SNSSI identifier. SNSMF then sends the network slice termination subnet request to SNSSMF.

[0067] SNSSMF will release the binding relationship between SNSSI, the S-NSSAI, the NSI and the SNSI based on the network slice termination subnet request.

[0068] Specifically, after receiving the network slice subnet termination request, SNSSMF parses the network slice subnet termination request to obtain the NSI identifier, the S-NSSAI identifier, the SNSI identifier, and the SNSSI identifier. The binding relationship between S-NSSAI, NSI, SNSI, and SNSSI is stored in SNSSMF. SNSSMF first finds the corresponding SNSSI based on the SNSSI identifier, and determines whether the network slice service corresponding to S-NSSAI is the last service associated with SNSSI. If the network slice service corresponding to S-NSSAI is the last service associated with SNSSI, it can be determined that SNSSI is only bound to the network slice service requested to be stopped. SNSSMF then determines whether NSI is the last NSI associated with SNSSI. If NSI is the last NSI associated with SNSSI, it can be determined that SNSSI is only bound to the NSI bound to the network slice service requested to be stopped. SNSSMF finally determines whether SNSI is the last SNSI associated with SNSSI. If SNSI is the last SNSI associated with SNSSI, it can be determined that SNSSI is only bound to the SNSI bound to the network slice service requested to be shut down. At this time, SNSSMF releases the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all binding relationships of SNSSI, that is, releasing SNSSI.

[0069] Since the released SNSSI is not bound to any NSI, SNSI or network slicing service, the operator can make a simple change to the SNSSI when opening a new network slicing service, and then bind the changed SNSSI with the identifier of the new network slicing service, the NSI bound to the identifier of the network slicing service, and the SNSI bound to the identifier of the network slicing service. There is no need to create a new SSNSI for the new network slicing service, which further improves the efficiency of opening the network slicing service.

[0070] Optionally, the step of releasing the binding relationship between the SNSI, the S-NSSAI and the NSI includes:

[0071] Determining a termination type of the SNSI;

[0072] When the termination type of the SNSI is to retain the SNSI, releasing the binding relationship between the SNSI, the S-NSSAI and the NSI;

[0073] In the case where the termination type of the SNSI is terminate SNSI, the binding relationship between the SNSI, the S-NSSAI and the NSI is released, and the record corresponding to the SNSI is deleted.

[0074] SNSMF stores the termination type of the network slice instance SNSI. The termination types of SNSI include retaining SNSI and terminating SNSI. The termination type can be set manually. If the user confirms that the SNSI has available value, the termination type can be set to retaining SNSI; if the user confirms that the SNSI does not have available value, the termination type can be set to terminating SNSI. In addition, a function for setting the termination type of SNSI can be deployed for SNSMF, and the function is deployed with standard parameters that characterize that the SNSI has available value. If the actual parameters in the SNSI in SNSMF obtained by the function are greater than the standard parameters, it can be determined that the SNSI has available value. At this time, the function sends a request to SNSMF to retain SNSI, and SNSMF sets the termination type of the SNSI to retain SNSI; if the actual parameters in the SNSI in SNSMF obtained by the function are less than or equal to the standard parameters, the function sends a request to SNSMF to terminate SNSI, and SNSMF sets the termination type of the SNSI to terminate SNSI. The standard parameters may be the network capability parameters of the SNSI. The network capability parameters are divided into numerical type and enumeration type parameters according to the value type. For example, parameters such as rate and network delay that can be represented by specific numerical values ​​may be classified as numerical type parameters. Non-numerical type parameters such as isolation, reliability, and security that are usually represented by strong, medium, and low may be classified as enumeration type parameters.

[0075] SNSMF first determines the termination type of SNSI. If the termination type of SNSI is to retain SNSI, the binding relationship between SNSI, S-NSSAI and NSI is released. To release the relationship means to delete the NSI identifier and S-NSSAI. If the termination type of SNSI is to terminate SNSI, the binding relationship between SNSI, S-NSSAI and NSI is released, and the records corresponding to SNSI are deleted. Deleting the records corresponding to SNSI means deleting all records corresponding to SNSI, deleting the records corresponding to NSI bound to SNSI, and deleting the records corresponding to S-NSSAI bound to SNSI.

[0076] In this embodiment, SNSMF decides whether to retain the record corresponding to the SNSI or delete the record corresponding to the SNSI according to the termination type of the SNSI, thereby reasonably deleting the record of the SNSI.

[0077] Optionally, before step S201, the method further includes:

[0078] receiving a deletion instruction carrying the S-NSSAI sent by the NSMF;

[0079] Delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to the SNSSMF so that the SNSSMF deletes the service configuration.

[0080] When NSMF receives a request to stop a network slice service, it will first delete the service configuration corresponding to the network slice service requested to be stopped. NSMF then generates a deletion instruction based on the identifier S-NSSAI of the network slice service requested to be stopped, and sends the deletion instruction to SNSMF. SNSMF parses the deletion instruction to obtain S-NSSAI, thereby deleting the service configuration of the network slice service corresponding to S-NSSAI. SNSMF then sends the deletion instruction to SNSSMF, so that SNSSMF deletes the service configuration of the network slice service corresponding to S-NSSAI.

[0081] The functions of non-shared power and shared network have layer-by-layer sharing characteristics. Therefore, after NSMF deletes the service configuration of the network slice service corresponding to S-NSSAI, it notifies NSSMF and SNSMF connected to NSMF to delete the service configuration of the network slice service corresponding to S-NSSAI; after SNSMF deletes the service configuration of the network slice service corresponding to S-NSSAI, it notifies SNSSMF and MANO connected to SNSMF to delete the service configuration of the network slice service corresponding to S-NSSAI.

[0082] In this embodiment, SNSMF releases more resources by deleting the service configuration of the network slicing service corresponding to S-NSSAI, thereby improving the network rate of SNSMF and improving the activation efficiency of subsequent network slicing services.

[0083] Reference Figure 3 , Figure 3 A flowchart of another method for processing a network slicing service improved by an embodiment of the present invention, applied to SNSSMF, the method comprising:

[0084] Step S301, receiving a network slice subnet termination request sent by SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier and SNSSI identifier.

[0085] Step S302, when it is determined based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI, the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI is released.

[0086] After SNSMF releases the binding relationship between SNSI, S-NSSAI and NSI, SNSMF generates a network slice subnet termination request based on the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier and SNSSI identifier. It can be understood that the network slice subnet termination request carries the mutually bound NSI identifier, S-NSSAI identifier, SNSI identifier and SNSSI identifier. SNSMF then sends the network slice subnet termination request to SNSSMF. SNSMF then sends the network slice subnet termination request to SNSSMF.

[0087] SNSSMF will release the binding relationship between SNSSI, the S-NSSAI, the NSI and the SNSI based on the network slice termination subnet request.

[0088] Specifically, after receiving the network slice subnet termination request, SNSSMF parses the network slice subnet termination request to obtain the NSI identifier, the S-NSSAI identifier, the SNSI identifier, and the SNSSI identifier. The binding relationship between S-NSSAI, NSI, SNSI, and SNSSI is stored in SNSSMF. SNSSMF first finds the corresponding SNSSI based on the SNSSI identifier, and first determines whether the network slice service corresponding to S-NSSAI is the last service associated with SNSSI. If the network slice service corresponding to S-NSSAI is the last service associated with SNSSI, it can be determined that SNSSI is only bound to the network slice service requested to be stopped. SNSSMF then determines whether NSI is the last NSI associated with SNSSI. If NSI is the last NSI associated with SNSSI, it can be determined that SNSSI is only bound to the NSI bound to the network slice service requested to be stopped. SNSSMF finally determines whether SNSI is the last SNSI associated with SNSSI. If SNSI is the last SNSI associated with SNSSI, it can be determined that SNSSI is only bound to the NSSI bound to the network slice service requested to be shut down. At this time, SNSSMF releases the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all binding relationships of SNSSI, that is, releasing SNSSI.

[0089] In this embodiment, the released SNSSI is not bound to any NSI, SNSI or network slicing service. When the operator opens a new network slicing service, the operator can make a simple change to the SNSSI, and then bind the changed SNSSI with the identifier of the new network slicing service, the NSI bound to the identifier of the network slicing service, and the SNSI bound to the identifier of the network slicing service. There is no need to create a new SSNSI for the new network slicing service, which further improves the efficiency of opening the network slicing service.

[0090] Optionally, after releasing the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, that is, after step S302, SNSSMF further includes:

[0091] A virtual network element instance termination request is sent to a virtualization resource orchestration management function MANO, so that the MANO releases the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI, and the SNSSI.

[0092] SNSSMF also stores the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier, SNSSI identifier, and virtual network element instances. The NSI identifier, S-NSSAI, SNSI identifier, SNSSI identifier, and virtual network element instances are bound to each other. Virtual network element instances include network service instances NS or virtualized network element instances VNF.

[0093] After SNSSMF releases the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, SNSMF generates a virtual network element instance termination request based on the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier, SNSSI identifier and virtual network element instance identifier. It can be understood that the virtual network element instance termination request carries the mutually bound NSI identifier, S-NSSAI identifier, SNSI identifier, SNSSI identifier and virtual network element instance identifier. SNSSMF then sends the virtual network element instance termination request to MANO.

[0094] MANO will release the binding relationship between SNSSI, S-NSSAI, NSI, SNSI and virtual network element instance based on the virtual network element instance termination request.

[0095] Specifically, after receiving the network element instance termination request, MANO parses the virtual network element instance termination request to obtain the NSI identifier, S-NSSAI identifier, SNSI identifier, SNSSI identifier and virtual network element instance identifier. MANO stores the binding relationship between the virtual network element instance, S-NSSAI, NSI, SNSI and SNSSI. MANO first finds the corresponding virtual network element instance based on the virtual network element instance identifier, and determines whether the network slice service corresponding to S-NSSAI is the last service associated with the virtual network element instance. If the network slice service corresponding to S-NSSAI is the last service associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the network slice service requested to be shut down. MANO then determines whether NSI is the last NSI associated with the virtual network element instance. If NSI is the last NSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the NSI bound to the network slice service requested to be shut down. MANO then determines whether SNSI is the last SNSI associated with the virtual network element instance. If SNSI is the last SNSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the SNSI bound to the network slice service requested to be shut down. MANO finally determines whether SNSSI is the last SNSSI associated with the virtual network element instance. If SNSSI is the last SNSSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the SNSSI bound to the network slice service requested to be shut down. At this point, MANO releases the binding relationship between the virtual network element instance, SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all binding relationships of the virtual network element instance, that is, releasing the virtual network element instance.

[0096] Since the released virtual network element instance is not bound to any NSI, SNSI, SNSSI or network slicing service, the operator can make a simple change to the virtual network element instance when opening a new network slicing service, and then bind the changed virtual network element instance to the identifier of the new network slicing service, the NSI bound to the identifier of the network slicing service, the SNSI bound to the identifier of the network slicing service, and the SNSSI bound to the identifier of the network slicing service. There is no need to create a new virtual network element instance for the new network slicing service, which further improves the efficiency of opening the network slicing service.

[0097] Optionally, the step of releasing the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI includes:

[0098] Determining a termination type of the SNSSI;

[0099] When the termination type of the SNSSI is to retain the SNSSI, releasing the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI;

[0100] In the case where the termination type of the SNSSI is to terminate the SNSSI, the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI is released, and the record corresponding to the SNSSI is deleted.

[0101] SNSSMF stores the termination type of the network slice instance SNSSI. The termination types of SNSSI include retaining SNSSI and terminating SNSSI. The termination type can be set manually. If the user confirms that the SNSSI has available value, the termination type can be set to retain SNSSI; if the user confirms that the SNSSI does not have available value, the termination type can be set to terminate SNSSI. In addition, a function for setting the termination type of SNSSI can be deployed for SNSSMF, and the function is deployed with standard parameters that characterize that the SNSSI has available value. If the actual parameters in the SNSSI in the SNSSMF obtained by the function are greater than the standard parameters, it can be determined that the SNSSI has available value. At this time, the function sends a request to the SNSMF to retain the SNSSI, and the SNSSMF sets the termination type of the SNSSI to retain the SNSSI; if the actual parameters in the SNSSI in the SNSSMF obtained by the function are less than or equal to the standard parameters, the function sends a request to the SNSSMF to terminate the SNSSI, and the SNSSMF sets the termination type of the SNSSI to terminate the SNSSI. The standard parameters may be the network capability parameters of the SNSSI. The network capability parameters are divided into numerical type and enumeration type parameters according to the value type. For example, parameters such as rate and network delay that can be represented by specific numerical values ​​may be classified as numerical type parameters. Non-numerical type parameters such as isolation, reliability, and security that are usually represented by strong, medium, and low may be classified as enumeration type parameters.

[0102] SNSSMF first determines the termination type of SNSSI. If the termination type of SNSSI is to retain SNSSI, the binding relationship between SNSSI, S-NSSAI, NSI and SNSI is released. To release the relationship means to delete the NSI identifier, SNSI identifier and S-NSSAI. If the termination type of SNSSI is to terminate SNSSI, the binding relationship between SNSSI, SNSI, S-NSSAI and NSI is released, and the records corresponding to SNSSI are deleted. Deleting the records corresponding to SNSSI means deleting all records corresponding to SNSSI, deleting the records corresponding to NSI bound to SNSSI, deleting the records corresponding to SNSI bound to SNSSI, and deleting the records corresponding to S-NSSAI bound to SNSI.

[0103] In this embodiment, SNSSMF determines whether to retain the record corresponding to the SNSSI or delete the record corresponding to the SNSSI according to the termination type of the SNSSI, thereby reasonably deleting the record of the SNSSI.

[0104] Optionally, before step S301, the method further includes:

[0105] receiving a deletion instruction carrying the S-NSSAI sent by the SNSMF;

[0106] Delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to MANO so that the MANO deletes the service configuration.

[0107] After SNSMF deletes the service configuration of the network slice service corresponding to S-NSSAI, SNSMF sends a deletion instruction to SNSSMF, so that SNSSMF deletes the service configuration of the network slice service corresponding to S-NSSAI.

[0108] The functions of non-shared power and shared network have layer-by-layer sharing characteristics. Therefore, after deleting the service configuration of the network slice service corresponding to S-NSSAI, SNSSMF notifies SNSSMF to connect to MANO to delete the service configuration of the network slice service corresponding to S-NSSAI.

[0109] In this embodiment, SNSSMF releases more resources by deleting the service configuration of the network slicing service corresponding to S-NSSAI, thereby improving the network rate of SNSSMF and improving the activation efficiency of subsequent network slicing services.

[0110] See also Figure 4 , Figure 4 A flowchart of another method for processing a network slicing service provided in an embodiment of the present invention is applied to MANO, and the method includes:

[0111] Step S401, receiving a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

[0112] After SNSSMF releases the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, SNSMF generates a virtual network element instance termination request based on the binding relationship between the NSI identifier, S-NSSAI, SNSI identifier, SNSSI identifier and virtual network element instance identifier. The virtual network element instance includes a network service instance NS or a virtualized network element instance VNF. It can be understood that the virtual network element instance termination request carries the mutually bound NSI identifier, S-NSSAI identifier, SNSI identifier, SNSSI identifier and virtual network element instance identifier. SNSSMF then sends the virtual network element instance termination request to MANO.

[0113] Step S402, when it is determined based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance, the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released.

[0114] MANO will release the binding relationship between SNSSI, S-NSSAI, NSI, SNSI and virtual network element instance based on the virtual network element instance termination request.

[0115] Specifically, after receiving the virtual network element instance termination request, MANO parses the virtual network element instance termination request to obtain the NSI identifier, the S-NSSAI identifier, the SNSI identifier, the SNSSI identifier, and the virtual network element instance identifier. MANO stores the binding relationship between the virtual network element instance, S-NSSAI, NSI, SNSI, and SNSSI. MANO first finds the corresponding virtual network element instance based on the virtual network element instance identifier, and determines whether the network slice service corresponding to S-NSSAI is the last service associated with the virtual network element instance. If the network slice service corresponding to S-NSSAI is the last service associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the network slice service requested to be shut down. MANO then determines whether NSI is the last NSI associated with the virtual network element instance. If NSI is the last NSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the NSI bound to the network slice service requested to be shut down. MANO then determines whether SNSI is the last SNSI associated with the virtual network element instance. If SNSI is the last SNSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the SNSI bound to the network slice service requested to be shut down. MANO finally determines whether SNSSI is the last SNSSI associated with the virtual network element instance. If SNSSI is the last SNSSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the SNSSI bound to the network slice service requested to be shut down. At this point, MANO releases the binding relationship between the virtual network element instance, SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all binding relationships of the virtual network element instance, that is, releasing the virtual network element instance.

[0116] Step S403: Send the virtual network element instance termination result to SNSSMF.

[0117] After releasing the binding relationship between SNSSI, S-NSSAI, NSI and SNSI, MANO sends the virtual network element instance termination result to SNSSMF. The virtual network element instance termination result indicates whether the virtual network element instance is released from the binding relationship. After receiving the virtual network element instance termination result, SNSSMF will send its own network slice subnet termination result and virtual network element instance termination result to SNSMF. SNSMF will finally send its own network slice termination result, network slice subnet termination result and virtual network element instance termination result to NSMF.

[0118] In this embodiment, since the released virtual network element instance is not bound to any NSI, SNSI, SNSSI and network slicing service, the operator can make a simple change to the virtual network element instance when opening a new network slicing service, and then bind the changed virtual network element instance to the identifier of the new network slicing service, the NSI bound to the identifier of the network slicing service, the SNSI bound to the identifier of the network slicing service, and the SNSSI bound to the identifier of the network slicing service. There is no need to create a new virtual network element instance for the new network slicing service, which further improves the efficiency of opening the network slicing service.

[0119] Optionally, the step of releasing the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the NSSI includes:

[0120] Determining a termination type of the virtual network element instance;

[0121] When the termination type of the virtual network element instance is to retain the virtual network element instance, releasing the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI;

[0122] When the termination type of the virtual network element instance is termination of the virtual network element instance, the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released, and the record of the virtual network element instance is deleted.

[0123] MANO stores the termination type of the virtual network element instance. The termination type of the virtual network element instance includes two types: retaining the virtual network element instance and terminating the virtual network element instance. The termination type can be set manually. If the user confirms that the virtual network element instance has available value, the termination type can be set to retain the virtual network element instance; if the user confirms that the virtual network element instance does not have available value, the termination type can be set to terminate the virtual network element instance. In addition, a function for setting the termination type of the virtual network element instance can be deployed for MANO, and the function is deployed with standard parameters that characterize that the virtual network element instance has available value. If the actual parameters of the virtual network element instance in MANO obtained by the function are greater than the standard parameters, it can be determined that the virtual network element instance has available value. At this time, the function sends a request to MANO to retain the virtual network element instance, and MANO sets the termination type of the virtual network element instance to retain the virtual network element instance; if the actual parameters of the virtual network element instance in MANO obtained by the function are less than or equal to the standard parameters, the function sends a request to SNSSMF to terminate SNSSI, and MANO sets the termination type of the virtual network element instance to terminate the virtual network element instance. Standard parameters may be network capability parameters of a virtual network element instance. Network capability parameters are classified into numerical type and enumeration type parameters according to the value type. For example, parameters such as rate and network delay that can be represented by specific numerical values ​​may be classified as numerical type parameters. Non-numerical type parameters such as isolation, reliability, and security that are usually represented by strong, medium, and low may be classified as enumeration type parameters.

[0124] MANO first determines the termination type of the virtual network element instance. If the termination type of the virtual network element instance is to retain the virtual network element instance, the binding relationship between the virtual network element instance, SNSSI, S-NSSAI, NSI and SNSI is released. To release the relationship means to delete the NSI identifier, SNSI identifier, SNSSI identifier and S-NSSAI. If the termination type of the virtual network element instance is to terminate the virtual network element instance, the binding relationship between the virtual network element instance, SNSSI, SNSI, S-NSSAI and NSI is released, and the records corresponding to the virtual network element instance are deleted. Deleting the records corresponding to the virtual network element instance means to delete all records corresponding to the virtual network element instance, delete the records corresponding to the NSI bound to the virtual network element instance, delete the records corresponding to the SNSI bound to the virtual network element instance, delete the records corresponding to the SNSSI bound to the virtual network element instance, and delete the records corresponding to the S-NSSAI bound to the virtual network element instance.

[0125] In this embodiment, MANO determines whether to retain the record corresponding to the virtual network element instance or delete the record corresponding to the virtual network element instance according to the termination type of the virtual network element instance, thereby reasonably deleting the record of the virtual network element instance.

[0126] Optionally, before step S401, the method further includes:

[0127] receiving a deletion instruction carrying the S-NSSAI sent by the SNSSMF;

[0128] Delete the service configuration of the network slice service corresponding to the S-NSSAI.

[0129] After deleting the service configuration of the network slice service corresponding to S-NSSAI, SNSSMF sends a deletion instruction to MANO. MANO parses the deletion instruction to obtain SNSSAI, thereby deleting the service configuration of the network slice service corresponding to S-NSSAI, thereby releasing more resources on MANO.

[0130] Reference Figure 5 , Figure 5 A flowchart of a method for processing another network slicing service provided in an embodiment of the present invention is applied to NSMF, and the method includes:

[0131] Step S501: Receive a service suspension request carrying S-NSSAI sent by the communication service management function CSMF.

[0132] When an operator needs to shut down a network slice service, it can send a network slice service shutdown request to NSMF on the CSMF in the non-shared network. The network slice service shutdown request carries the S-NSSAI of the network slice service requested to be shut down.

[0133] Step S502: When the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI, the binding relationship between the S-NSSAI and the NSI is released.

[0134] After receiving the request to stop the network slicing service, NSMF first deletes the service configuration of the network slicing service represented by S-NSSAI. NSMF stores the binding relationship between S-NSSAI and the identifier of the network slice instance NSI, and NSI may have a binding relationship with multiple network slicing services at the same time, that is, multiple network slicing services share one NSI. If the network slicing service corresponding to S-NSSAI is the last service associated with NSI, it can be determined that NSI is only bound to the network slicing service requested to be stopped. At this time, NSMF releases the binding relationship between S-NSSAI and NSI, thereby releasing NSI from the binding relationship, so that NSI can be used by the operator's subsequent network slicing services.

[0135] Step S503: Send a network slice termination request to the SNSMF so that the SNSMF releases the binding relationship between SNSI, S-NSSAI and NSI.

[0136] NSMF also stores the binding relationship between the NSI identifier, S-NSSAI and the identifier of the network slice instance SNSI of the shared network. The NSI identifier, S-NSSAI and SNSI identifier are bound to each other. After NSMF releases the binding relationship between NSI and S-NSSAI, NSMF generates a network slice termination request based on the binding relationship between the NSI identifier, S-NSSAI and SNSI identifier. It can be understood that the network slice termination request carries the mutually bound NSI identifier, S-NSSAI identifier and SNSI identifier. NSMF then sends the network slice termination request to SNSMF.

[0137] Step S504, receiving the target termination result sent by SNSMF, wherein, when SNSSMF receives the virtual network element instance termination result sent by MANO, it sends the network slice subnet termination result of the shared network and the virtual network element instance termination result to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the network slice subnet termination result of the shared network, and the termination result of the network slice of the shared network;

[0138] After NSMF sends the network slice termination request to SNSMF, SNSMF releases the binding relationship between SNSI, NSI and S-NSSAI. SNSMF then sends a network slice subnet termination request to SNSSMF, so that SNSSMF releases the binding relationship between SNSSI, SNSI, NSI and S-NSSAI. SNSSMF then sends a virtual network element instance termination request to MANO, so that MANO releases the binding relationship between the virtual network element instance, SNSSI, SNSI, NSI and S-NSSAI. MANO then sends the virtual network element instance termination result to SNSSMF. After receiving the virtual network element instance termination result, SNSSMF will send its own network slice subnet termination result and virtual network element instance termination result to SNSMF. SNSMF finally sends its own network slice termination result, network slice subnet termination result and virtual network element instance termination result to NSMF, that is, NSMF receives the target termination result sent by SNSMF, including the virtual network element instance termination result, the network slice subnet termination result of the shared network and the network slice termination result of the shared network.

[0139] Step S505: Send the target termination result to the CSMF.

[0140] After receiving the target termination result, NSMF sends the target termination result to CSMF. The target termination result refers to the network slice termination result of the shared network. NSMF also needs to send the network slice termination result of the non-shared network to CSMF.

[0141] Specifically, when NSMF sends a network slice termination request for the shared network to SNSMF, it will also send a network slice subnet termination request for the non-shared network to NSSMF.

[0142] The network slice subnet termination request of the non-shared network carries the identifiers of the mutually bound NSIs, the identifiers of the S-NSSAI, and the identifier of the network slice subnet instance NSSI of the non-shared network. After receiving the network slice subnet termination request, the NSSMF parses the network slice subnet termination request to obtain the identifier of the NSI, the identifier of the S-NSSAI, and the identifier of the NSSI. The binding relationship between the S-NSSAI, NSI, and NSSI is stored in the NSSMF. The NSSMF first finds the corresponding NSSI based on the identifier of the NSSI, and determines whether the network slice service corresponding to the S-NSSAI is the last service associated with the NSSI. If the network slice service corresponding to the S-NSSAI is the last service associated with the NSSI, it can be determined that the NSSI is only bound to the network slice service requested to be shut down. NSSMF determines whether NSI is the last NSI associated with NSSI. If NSI is the last NSI associated with NSSI, it can be determined that NSSI is only bound to the NSI bound to the network slice service requested to be shut down. At this time, NSSMF releases the binding relationship between NSSI, S-NSSAI and NSI, thereby releasing all binding relationships of NSSI, that is, releasing NSSI. NSSMF stores the termination type of NSSI. If the termination type of NSSI is to retain NSSI, the binding relationship between NSSI, S-NSSAI and NSI is released; if the termination type of NSSI is to terminate NSSI, the binding relationship between NSSI, S-NSSAI and NSI is released, and the record corresponding to NSSI is deleted.

[0143] After NSSMF releases NSSI, NSSMF generates a virtual network element instance termination request based on the binding relationship between the NSI identifier, S-NSSAI, NSSI identifier, and virtual network element instance identifier. The virtual network element instance includes a network service instance NS or a virtualized network element instance VNF. It can be understood that the virtual network element instance termination request carries the mutually bound NSI identifier, S-NSSAI identifier, NSSI identifier, and virtual network element instance identifier. NSSMF then sends the virtual network element instance termination request to MANO.

[0144] MANO will release the binding relationship between NSSI, S-NSSAI, NSI and virtual network element instance based on the virtual network element instance termination request.

[0145] Specifically, after receiving the virtual network element instance termination request, MANO parses the virtual network element instance termination request to obtain the NSI identifier, the S-NSSAI identifier, the NSSI identifier, and the virtual network element instance identifier. MANO stores the binding relationship between the virtual network element instance, S-NSSAI, NSI, and NSSI. MANO first finds the corresponding virtual network element instance based on the virtual network element instance identifier, and determines whether the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance. If the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the network slice service requested to be shut down. MANO then determines whether the NSI is the last NSI associated with the virtual network element instance. If the NSI is the last NSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the NSI bound to the network slice service requested to be shut down. MANO then determines whether the NSSI is the last NSSI associated with the virtual network element instance. If the NSSI is the last NSSI associated with the virtual network element instance, it can be determined that the virtual network element instance is only bound to the NSSI bound to the network slice service requested to be shut down. At this time, MANO releases the binding relationship between the virtual network element instance, NSSI, S-NSSAI, and NSI, thereby releasing all binding relationships of the virtual network element instance, that is, releasing the virtual network element instance. MANO releases the binding relationship between the virtual network element instance, NSSI, S-NSSAI, and NSI through the termination type of the virtual network element instance. The specific principle refers to the above description and will not be repeated. It should be noted that MANO's release of the binding relationship between the virtual network element instance, NSSI, S-NSSAI, and NSI involves the release of the virtual network element instance of the non-shared network, while MANO's release of the binding relationship between the virtual network element instance, SNSSI, S-NSSAI, NSI, and SNSI involves the release of the virtual network element instance of the shared network. The two virtual network element instances are not the same. The virtual network element instance of the shared network may be represented by a first virtual network element instance, and the virtual network element instance of the non-shared network may be represented by a second virtual network element instance.

[0146] After releasing the binding relationship between NSSI, S-NSSAI, and NSI, MANO sends the virtual network element instance termination result to NSSMF. The virtual network element instance termination result indicates whether the virtual network element instance is released from the binding relationship. After receiving the virtual network element instance termination result, NSSMF will send its own network slice subnet termination result and virtual network element instance termination result to NSMF. NSMF will finally send its own network slice termination result, network slice subnet termination result, and virtual network element instance termination result to NSMF. That is, NSMF obtains the network slice termination result of the non-shared network.

[0147] NSMF summarizes the network slice termination results of non-shared networks and shared networks and sends them to CSMF, so that users can know the instance termination results of each function based on CSMF.

[0148] Optionally, the step of releasing the binding relationship between the S-NSSAI and the NSI includes:

[0149] Determining a termination type of the NSI;

[0150] When the termination type of the NSI is to retain the NSI, releasing the binding relationship between the S-NSSAI and the NSI;

[0151] In the case where the termination type of the NSI is to terminate the NSI, the binding relationship between the S-NSSAI and the NSI is released, and the record corresponding to the NSI is deleted.

[0152] NSMF stores the termination type of NSI. The termination type of NSI includes two types: retaining NSI and terminating NSI. The termination type can be set manually. If the user confirms that the NSI has available value, the termination type can be set to retain NSI; if the user confirms that the NSI does not have available value, the termination type can be set to terminate NSI. In addition, a function for setting the termination type of NSI can be deployed for NSMF, and the function is deployed with standard parameters that characterize that the NSI has available value. If the actual parameters of the NSI in the NSMF obtained by the function are greater than the standard parameters, it can be determined that the NSI has available value. At this time, the function sends a request to NSMF to retain the NSI, and NSMF sets the termination type of the NSI to retain the NSI; if the actual parameters of the NSI in the NSMF obtained by the function are less than or equal to the standard parameters, the function sends a request to NSMF to terminate the NSI, and NSMF sets the termination type of the NSI to terminate the NSI. The standard parameters may be the network capability parameters of the NSI. The network capability parameters are divided into numerical type and enumeration type parameters according to the value type. For example, parameters such as rate and network delay that can be represented by specific numerical values ​​can be classified as numerical type parameters. Non-numerical type parameters such as isolation, reliability, and security that are usually represented by strong, medium, and low can be classified as enumeration type parameters.

[0153] NSMF first determines the termination type of NSI. If the termination type of NSI is to retain NSI, the binding relationship between NSI and S-NSSAI is released. To release the relationship means to delete S-NSSAI. If the termination type of NSI is to terminate NSI, the binding relationship between NSI and S-NSSAI is released, and the records corresponding to NSI are deleted. To delete the records corresponding to NSI means to delete all records corresponding to NSI and the records corresponding to S-NSSAI bound to NSI.

[0154] In this embodiment, NSMF determines whether to retain the record corresponding to the NSI or delete the record corresponding to the NSI according to the termination type of the NSI, thereby reasonably deleting the record of the NSI.

[0155] Based on the above embodiments, the processing method of the network slicing service provided by the present invention is briefly described. Figure 6 , Figure 6 An interactive flow chart of a method for processing a network slicing service provided in an embodiment of the present invention, the method comprising:

[0156] S1. CSMF sends a service suspension request carrying the identifier S-NSSAI of the network slice service requested to be suspended to NSMF.

[0157] S2 and NSMF interact with NSSMF, SNSMF, SNSSMF, and MANO in turn to delete the service configuration corresponding to S-NSSAI.

[0158] S3. If S-NSSAI is the last service associated with NSI, NSMF selects one of the two termination types to release NSI: a. Retain NSI: release the binding relationship between S-NSSAI and NSI; b. Terminate NSI: release the binding relationship between S-NSSAI and NSI and delete the record corresponding to NSI.

[0159] NSMF sends a network slice subnet termination request for a non-shared network to NSSMF (the network slice subnet termination request includes S-NSSAI, NSI ID, and NSSI ID) to execute S4a-S9a, and sends a network slice termination request for a shared network to SNSMF (the network slice termination request includes S-NSSAI, NSI ID, and SNSI ID) to execute S4b-S12b, that is, steps S4a-S9a and steps S4b-S12b are executed in parallel.

[0160] S4a. NSMF sends the network slice subnet termination request of the non-shared network to NSSMF, carrying S-NSSAI, NSIID and NSSI ID.

[0161] S5a. If S-NSSAI is the last service associated with NSSI and NSI is the last NSI associated with NSSI, NSSMF releases NSI according to one of the two termination types of NSSI; a. Retain NSSI: release the binding relationship between S-NSSAI, NSI and NSSI; b. Terminate NSSI: release the binding relationship between S-NSSAI, NSI and NSSI and delete the record corresponding to NSSI.

[0162] S6a. NSSMF sends a virtual network element instance (network service NS / virtualized network element VNF) termination request to MANO. The virtual network element instance termination request carries S-NSSAI, NSI ID, NSSI ID and NS ID / VNF ID.

[0163] S7a. If S-NSSAI, NSI and NSSI are respectively the last service, the last NSI and the last NSSI associated with the NS / VNF instance, MANO releases the virtual network element instance according to one of the two termination types of the virtual network element instance; a. Retain NS / VNF: release the binding relationship between NS / VNF, S-NSSAI, NSI and NSSI; b. Terminate NS / VNF: release the binding relationship between NS / VNF S-NSSAI, NSI and NSSI and delete the corresponding record of NS / VNF;

[0164] S8a. MANO notifies NSSMF of the network service NS / virtualized network element VNF ​​termination result.

[0165] S9a. NSSMF notifies NSMF of the termination result of the network slice subnet of the non-shared network.

[0166] S4b. NSMF sends the network slice termination request of the shared network to SNSMF. The network slice termination request of the shared network carries S-NSSAI, NSI ID and SNSI ID.

[0167] S5b. If S-NSSAI and NSI are the last service and the last NSI associated with SNSI respectively, SNSMF releases SNSI according to one of the two termination types of SNSI; a. Retain SNSI: release the binding relationship between S-NSSAI, NSI and SNSI; b. Terminate SNSI: release the binding relationship between S-NSSAI, NSI and SNSI and delete the records corresponding to SNSI.

[0168] S6b. SNSMF sends the network slice subnet termination request of the shared network to SNSSMF. The network slice subnet termination request carries S-NSSAI, NSI ID, SNSI ID and SNSSI ID.

[0169] S7b. If S-NSSAI, NSI and SNSI are respectively the last service, the last NSI and the last SNSI associated with SNSSI, SNSSMF releases SNSSI according to one of the two termination types of SNSSI; a. Retain SNSSI: release the binding relationship between SNSSI, S-NSSAI, NSI and SNSI; b. Terminate SNSSI: release the binding relationship between SNSSI, S-NSSAI, NSI and SNSI and delete the records corresponding to SNSSI.

[0170] S8b. SNSSMF sends the network service NS / virtualized network element VNF ​​termination request to MANO, carrying S-NSSAI, NSI ID, SNSI ID, SNSSI ID and NS ID / VNF ID.

[0171] S9b. If S-NSSAI, NSI, SNSI, and SNSSI are respectively the last service, the last NSI, the last SNSI, and the last SNSSI associated with the NS / VNF instance, MANO releases the NS / VNF according to one of the two termination types of NS / VNF; a. Retain NS / VNF: release the binding relationship between NS / VNF, SNSSI, S-NSSAI, NSI, and SNSI; b. Terminate NS / VNF: release the binding relationship between NS / VNF, SNSSI, S-NSSAI, NSI, and SNSI, and delete the corresponding record of NS / VNF.

[0172] S10b. MANO notifies SNSSMF of the network service NS / virtualized network element VNF ​​termination result.

[0173] S11b. SNSSMF notifies SNSMF of the termination result of the network slice subnet of the shared network.

[0174] S12b. SNSMF notifies NSMF of the termination result of the network slice of the shared network.

[0175] S13. NSMF summarizes the network slice subnet termination results of the non-shared network and the network slice termination results of the shared network.

[0176] S14. NSMF notifies CSMF of the network slicing service suspension result, carrying the service identifier S-NSSAI.

[0177] The embodiment of the present invention also provides a SNSMF. Figure 7 , Figure 7 A structural diagram of the SNSMF provided for an embodiment of the present invention. Since the principle of solving the problem by the SNSMF is similar to the method for processing the network slicing service in the embodiment of the present invention, the implementation of the SNSMF and the technical effects achieved can refer to the above description, and the repetitions will not be repeated.

[0178] like Figure 7 As shown, SNSMF700 includes:

[0179] The first receiving module 701 is used to receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other;

[0180] The first release module 702 is used to release the binding relationship between the SNSI, the S-NSSAI and the NSI when it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI and the NSI is the last NSI associated with the SNSI.

[0181] Optionally, SNSMF700 includes:

[0182] A sending module is used to send a network slice subnet termination request to the network slice subnet management function SNSSMF of the shared network, so that the SNSSMF releases the binding relationship between the network slice subnet instance SNSSI, the S-NSSAI, the NSI and the SNSI of the shared network.

[0183] Optionally, SNSMF700 includes:

[0184] A determination module, used to determine the termination type of the SNSI;

[0185] The first release module 702 is further configured to release the binding relationship between the SNSI, the S-NSSAI and the NSI when the termination type of the SNSI is a reserved SNSI;

[0186] The first release module 702 is further used to release the binding relationship between the SNSI, the S-NSSAI and the NSI, and delete the record corresponding to the SNSI when the termination type of the SNSI is termination SNSI.

[0187] Optionally, SNSMF700 includes:

[0188] The first receiving module 701 is further configured to receive a deletion instruction carrying the S-NSSAI sent by the NSMF;

[0189] The deletion module is used to delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to the SNSSMF so that the SNSSMF deletes the service configuration.

[0190] The embodiment of the present invention also provides a SNSSMF. Figure 8 , Figure 8 A structural diagram of the SNSSMF provided for an embodiment of the present invention. Since the principle of solving the problem by the SNSSMF is similar to the method for processing the network slicing service in the embodiment of the present invention, the implementation of the SNSSMF and the technical effects achieved can refer to the above description, and the repetitions will not be repeated.

[0191] like Figure 8 As shown, SNSSMF800 includes:

[0192] The second receiving module 801 is used to receive a network slice subnet termination request sent by the SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier and SNSSMF identifier;

[0193] The second release module 802 is used to release the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI when it is determined, based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI.

[0194] Optionally, the SNSSMF800 also includes:

[0195] The sending module is used to send a virtual network element instance termination request to the virtualization resource orchestration management function MANO, so that the MANO releases the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI.

[0196] Optionally, the SNSSMF800 also includes:

[0197] A determination module, used to determine the termination type of the SNSSI;

[0198] A second releasing module 802 is configured to release the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI when the termination type of the SNSSI is to retain the SNSSI;

[0199] The second releasing module 802 is used to release the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI, and delete the record corresponding to the SNSSI when the termination type of the SNSSI is termination of the SNSSI.

[0200] Optionally, the SNSSMF800 also includes:

[0201] The second receiving module 801 is configured to receive a deletion instruction carrying the S-NSSAI sent by the SNSMF;

[0202] The deletion module is used to delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to the MANO so that the MANO deletes the service configuration.

[0203] The embodiment of the present invention also provides a MANO. Fig. 9 , Fig. 9 A structural diagram of MANO provided for an embodiment of the present invention. Since the principle of MANO in solving the problem is similar to the method for processing network slicing services in an embodiment of the present invention, the implementation of MANO and the technical effects achieved can refer to the above description, and the repeated parts will not be repeated.

[0204] like Fig. 9 As shown, MANO900 includes:

[0205] The third receiving module 901 is used to receive a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

[0206] The third release module 902 is used to release the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI, the NSSI and the SNSSI when it is determined that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance according to the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance;

[0207] The first sending module 903 is used to send the virtual network element instance termination result to the SNSSMF.

[0208] Optionally, MANO900 also includes:

[0209] A determination module, used to determine the termination type of the virtual network element instance;

[0210] A third release module 902 is used to release the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI when the termination type of the virtual network element instance is to retain the virtual network element instance;

[0211] The third release module 902 is used to release the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI, and delete the record of the virtual network element instance when the termination type of the virtual network element instance is termination of the virtual network element instance.

[0212] Optionally, MANO900 also includes:

[0213] The third receiving module 901 is used to receive a deletion instruction carrying the S-NSSAI sent by the SNSSMF;

[0214] The deletion module is used to delete the service configuration of the network slice service corresponding to the S-NSSAI.

[0215] The embodiment of the present invention also provides a NSMF. Fig.10 , Fig.10 A structural diagram of the NSMF provided for an embodiment of the present invention. Since the principle of solving the problem by the NSMF is similar to the method for processing the network slicing service in the embodiment of the present invention, the implementation of the NSMF and the technical effects achieved can refer to the above description, and the repetitions will not be repeated.

[0216] like Fig.10 As shown, NSMF1000 includes:

[0217] The fourth receiving module 1001 is used to receive a service suspension request of S-NSSAI sent by the communication service management function CSMF;

[0218] The fourth release module 1002 is used to release the binding relationship between the S-NSSAI and the NSI when the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI;

[0219] The second sending module 1003 is used to send a network slice termination request to the SNSMF, so that the SNSMF releases the binding relationship between the SNSI, S-NSSAI and NSI;

[0220] The fourth receiving module 1004 is further used to receive a target termination result sent by SNSMF, wherein, when SNSSMF receives the termination result of the virtual network element instance sent by MANO, the network slice subnet termination result of the shared network and the termination result of the virtual network element instance are sent to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the termination result of the network slice subnet of the shared network, and the termination result of the network slice of the shared network;

[0221] The second sending module is used to send the target termination result to the CSMF.

[0222] Optionally, the NSMF1000 also includes:

[0223] A determination module, used to determine the termination type of the NSI;

[0224] The fourth releasing module 1002 is configured to release the binding relationship between the S-NSSAI and the NSI when the termination type of the NSI is a reserved NSI;

[0225] The fourth releasing module 1002 is used to release the binding relationship between the S-NSSAI and the NSI and delete the record corresponding to the NSI when the termination type of the NSI is to terminate the NSI.

[0226] Optionally, the NSMF1000 also includes:

[0227] A deletion module, used to delete the service configuration of the network slice service corresponding to the S-NSSAI;

[0228] A sending module is used to send a deletion instruction carrying the S-NSSAI to the SNSMF, so that the SNSMF deletes the service configuration of the network slice service corresponding to the S-NSSAI.

[0229] Optional, such as Figure 7 As shown, an embodiment of the present invention further provides a network device 1100, including a processor 1101, a memory 1102, and a program or instruction stored in the memory 1102 and executable on the processor 1101. When the program or instruction is executed by the processor 1101, each process of the above-mentioned method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0230] The embodiment of the present invention further provides a computer-readable storage medium, wherein a program or instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, the above Figures 2 to 6 The various processes of any method embodiment can achieve the same technical effect, and will not be described again here to avoid repetition.

[0231] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0232] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A method for processing a network slice service, applied to a network slice management function SNSMF of a shared network, characterized in that: The method comprises: Receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other; When it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI, and the NSI is the last NSI associated with the SNSI, the binding relationship between the SNSI, the S-NSSAI and the NSI is released.

2. The method according to claim 1, characterized in that After the step of releasing the binding relationship between the SNSI, the S-NSSAI and the NSI, the method further includes: A network slice subnet termination request is sent to the network slice subnet management function SNSSMF of the shared network, so that the SNSSMF releases the binding relationship between the network slice subnet instance SNSSI, the S-NSSAI, the NSI and the SNSI of the shared network.

3. The method according to claim 1, characterized in that The step of releasing the binding relationship between the SNSI, the S-NSSAI and the NSI comprises: Determining a termination type of the SNSI; When the termination type of the SNSI is to retain the SNSI, releasing the binding relationship between the SNSI, the S-NSSAI and the NSI; In the case where the termination type of the SNSI is terminate SNSI, the binding relationship among the SNSI, the S-NSSAI and the NSI is released, and the record corresponding to the SNSI is deleted.

4. The method according to any one of claims 1 to 3, characterized in that Before the step of receiving a network slice termination request sent by a network slice management function NSMF of a non-shared network, the method further includes: receiving a deletion instruction carrying the S-NSSAI sent by the NSMF; Delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to the SNSSMF so that the SNSSMF deletes the service configuration.

5. A method for processing network slicing services, applied to SNSSMF, characterized in that: The method comprises: Receive a network slice subnet termination request sent by the SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, and SNSSI identifier; When it is determined based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI, the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI is released.

6. The method according to claim 5, characterized in that After the step of releasing the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI, the method further includes: A virtual network element instance termination request is sent to a virtualization resource orchestration management function MANO, so that the MANO releases the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI, and the SNSSI.

7. The method according to claim 5, characterized in that The step of releasing the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI comprises: Determining a termination type of the SNSSI; When the termination type of the SNSSI is to retain the SNSSI, releasing the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI; In the case where the termination type of the SNSSI is to terminate the SNSSI, the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI is released, and the record corresponding to the SNSSI is deleted.

8. The method according to any one of claims 5 to 7, characterized in that: Before the step of receiving the network slice subnet termination request sent by the SNSMF, the step further includes: receiving a deletion instruction carrying the S-NSSAI sent by the SNSMF; Delete the service configuration of the network slice service corresponding to the S-NSSAI, and send the deletion instruction to MANO so that the MANO deletes the service configuration.

9. A method for processing network slicing services, applied to MANO, characterized in that: The method comprises: Receive a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier, and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF; When it is determined according to the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance, the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released; Send the virtual network element instance termination result to SNSSMF.

10. The method according to claim 9, characterized in that The step of releasing the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the NSSI comprises: Determining a termination type of the virtual network element instance; When the termination type of the virtual network element instance is to retain the virtual network element instance, releasing the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI; When the termination type of the virtual network element instance is termination of the virtual network element instance, the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released, and the record of the virtual network element instance is deleted.

11. The method according to claim 9 or 10, characterized in that: Before the step of receiving the virtual network element instance termination request sent by the SNSSMF, the method further includes: receiving a deletion instruction carrying the S-NSSAI sent by the SNSSMF; Delete the service configuration of the network slice service corresponding to the S-NSSAI.

12. A method for processing network slicing services, applied to NSMF, characterized in that: The method comprises: Receive a service suspension request carrying S-NSSAI sent by the communication service management function CSMF; When the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI, release the binding relationship between the S-NSSAI and the NSI; Send a network slice termination request to the SNSMF so that the SNSMF releases the binding relationship between the SNSI, S-NSSAI and NSI; Receiving the target termination result sent by SNSMF, wherein, when SNSSMF receives the virtual network element instance termination result sent by MANO, the network slice subnet termination result of the shared network and the virtual network element instance termination result are sent to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the network slice subnet termination result of the shared network, and the termination result of the network slice of the shared network; Send the target termination result to the CSMF.

13. The method according to claim 12, characterized in that The step of releasing the binding relationship between the S-NSSAI and the NSI comprises: Determining a termination type of the NSI; When the termination type of the NSI is to retain the NSI, releasing the binding relationship between the S-NSSAI and the NSI; In the case where the termination type of the NSI is to terminate the NSI, the binding relationship between the S-NSSAI and the NSI is released, and the record corresponding to the NSI is deleted.

14. The method according to claim 12 or 13, characterized in that In the case where the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI, before the step of releasing the binding relationship between the S-NSSAI and the NSI, the step further includes: Delete the service configuration of the network slice service corresponding to the S-NSSAI; A deletion instruction carrying the S-NSSAI is sent to the SNSMF so that the SNSMF deletes the service configuration of the network slice service corresponding to the S-NSSAI.

15. A SNSMF, characterized in that: include: A first receiving module is used to receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, wherein the network slice termination request carries a network slice service identifier S-NSSAI requested to be stopped, an identifier of a network slice instance NSI of a non-shared network, and an identifier of a network slice instance SNSI of a shared network, and the SNSI, the S-NSSAI and the NSI are bound to each other; The first release module is used to release the binding relationship between the SNSI, the S-NSSAI and the NSI when it is determined, based on the S-NSSAI, the identifier of the NSI and the identifier of the SNSI, that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSI and the NSI is the last NSI associated with the SNSI.

16. A SNSSMF, characterized in that: include: A second receiving module is used to receive a network slice subnet termination request sent by SNSMF, wherein the network slice subnet termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier and SNSSMF identifier; The second release module is used to release the binding relationship between the SNSSI, the S-NSSAI, the NSI and the SNSI when it is determined based on the S-NSSAI, the identifier of the NSI, the identifier of the SNSI and the identifier of the SNSSI that the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI, and the SNSI is the last SNSI associated with the SNSSI.

17. A MAMO, characterized in that: include: A third receiving module is used to receive a virtual network element instance termination request sent by the SNSSMF, wherein the virtual network element termination request carries the mutually bound S-NSSAI, NSI identifier, SNSI identifier, SNSSI identifier, and virtual network element instance identifier, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF; A third release module is used to release the binding relationship between the virtual network element instance, the S-NSSAI, the NSI, the SNSI, the NSSI and the SNSSI when it is determined that the network slice service corresponding to the S-NSSAI is the last service associated with the virtual network element instance, the NSI is the last NSI associated with the virtual network element instance, the SNSI is the last SNSI associated with the virtual network element instance, and the SNSSI is the last SNSSI associated with the virtual network element instance according to the S-NSSAI, the identifier of the NSI, the identifier of the SNSI, the identifier of the NSSI and the identifier of the virtual network element instance; The first sending module is used to send the virtual network element instance termination result to the SNSSMF.

18. A NSMF, characterized in that: include: A fourth receiving module is used to receive a service suspension request of S-NSSAI sent by the communication service management function CSMF; A fourth release module is used to release the binding relationship between the S-NSSAI and the NSI when the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound to the S-NSSAI; The second sending module is used to send a network slice termination request to the SNSMF, so that the SNSMF releases the binding relationship between the SNSI, the S-NSSAI and the NSI; The fourth receiving module is further used to receive a target termination result sent by SNSMF, wherein, when SNSSMF receives the termination result of the virtual network element instance sent by MANO, the network slice subnet termination result of the shared network and the termination result of the virtual network element instance are sent to the SNSMF, and the target termination result includes the termination result of the virtual network element instance, the termination result of the network slice subnet of the shared network, and the termination result of the network slice of the shared network; The second sending module is used to send the target termination result to the CSMF.

19. A network device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for processing network slicing services as described in any one of claims 1 to 4, or implements the steps of the method for processing network slicing services as described in any one of claims 5 to 8, or implements the steps of the method for processing network slicing services as described in any one of claims 9 to 11, or implements the steps of the method for processing network slicing services as described in any one of claims 12 to 14.

20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the steps of the method for processing network slicing services as described in any one of claims 1 to 4, or implement the steps of the method for processing network slicing services as described in any one of claims 5 to 8, or implement the steps of the method for processing network slicing services as described in any one of claims 9 to 11, or implement the steps of the method for processing network slicing services as described in any one of claims 12 to 14.

Images