CN114727296A

CN114727296A - Processing method of network slicing service and related equipment

Info

Publication number: CN114727296A
Application number: CN202110001390.4A
Authority: CN
Inventors: 高芳; 万奇; 廖佩贞; 方冬梅
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-01-04
Filing date: 2021-01-04
Publication date: 2022-07-08

Abstract

The invention discloses a processing method of a network slicing service and related equipment, and relates to the technical field of communication. The method comprises the following steps: 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 a network slice service identifier S-NSSAI requesting to be closed, 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 the SNSI, the S-NSSAI and the NSI are bound with each other; and under the condition that the network slice service corresponding to the S-NSSAI is determined to be the last service associated with the SNSI and the NSI is determined to be the last NSI associated with the SNSI according to the identifications of the S-NSSAI and the NSI and the identification of the SNSI, removing the binding relationship among the SNSI, the S-NSSAI and the NSI. The invention improves the opening efficiency of the network slicing service.

Description

Processing method of network slicing service and related equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method for processing a network slicing service and a related device.

Background

With the development of communication technology, network slicing technology is in force. As different communication operators become more compact in service cooperation and resources such as wireless spectrum are scarce, in order to more fully utilize scarce network resources, a concept of a shared network is proposed, that is, non-shared networks of the operators are connected through the shared network to realize resource division of network slicing services.

The resource division of the network slicing service of the operator is realized on the basis that the network slicing service, the network slicing example of the non-shared network and the network slicing example of the shared network have a binding relationship. When the network slice service of the operator is opened, a network slice instance needs to be established in the shared network to be bound with the network slice service, and the network slice instance is established for a long time, so that the opening efficiency of the network slice service is low.

Disclosure of Invention

The embodiment of the invention provides a processing method of a network slicing service and related equipment, which aim to solve the problem of low opening efficiency of the network slicing service.

In order to solve the technical problem, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a method for processing a network slice service, where the method is applied to a network slice management function SNSMF of a shared network, and the method includes:

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 a network slice service identifier S-NSSAI requesting to be closed, 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 the SNSI, the S-NSSAI and the NSI are bound to each other;

and under the condition that the network slice service corresponding to the S-NSSAI is determined to be the last service associated with the SNSI and the NSI is determined to be the last NSI associated with the SNSI according to the S-NSSAI, the NSI identifier and the SNSI identifier, removing the binding relationship among the SNSI, the S-NSSAI and the NSI.

In a second aspect, an embodiment of the present invention provides a method for processing a network slice service, where the method is applied to SNSSMF, and the method includes:

receiving a network slice subnet termination request sent by an SNSMF (network slice subnet management function), wherein the network slice subnet termination request carries an S-NSSAI (service name system identifier), an NSI (network slice subnet identifier), an SNSI (service provider identifier) and an SNSSI (service session identifier) which are bound with each other;

and under the condition that the network slice service corresponding to the S-NSSAI is determined to be the last service related to the SNSSI, the NSI is determined to be the last NSI related to the SNSSI, and the SNSI is determined to be the last SNSI related to the SNSSI according to the S-NSSAI, the NSI identifier, the SNSI identifier and the SNSSI identifier, the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI is released.

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

receiving a virtual network element instance termination request sent by SNSSMF, wherein the virtual network element termination request carries an identifier of S-NSSAI, an identifier of NSI, an identifier of SNSI, an identifier of SNSSI and an identifier of a virtual network element instance which are bound with each other, and the virtual network element instance comprises a network service instance NS or a virtualized network element instance VNF;

under the condition that the network slice service corresponding to the S-NSSAI is determined to be the last service associated with the virtual network element instance, the NSI is determined to be the last NSI associated with the virtual network element instance, the SNSI is determined to be the last SNSI associated with the virtual network element instance, and the SNSSI is determined to be the last SNSSI associated with the virtual network element instance, the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is determined according to the S-NSSAI, the NSI identifier, the SNSI identifier, the NSSI identifier and the virtual network element instance;

and sending the termination result of the virtual network element instance to the SNSSMF.

In a fourth aspect, an embodiment of the present invention further provides a method for processing a network slice service, where the method is applied to an NSMF, and the method includes:

receiving a service shutdown request which is sent by a communication service management function CSMF and carries S-NSSAI;

removing the binding relationship between the S-NSSAI and the NSI under the condition that the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound by the S-NSSAI;

sending a network slice termination request to the SNSMF so that the SNSMF releases the binding relationship among SNSI, S-NSSAI and NSI;

receiving a target termination result sent by SNSMF, wherein under the condition that SNSSMF receives a virtual network element instance termination result sent by MANO, the target termination result comprises a virtual network element instance termination result, a shared network slice subnet termination result and a shared network slice termination result;

sending the target termination result to the CSMF.

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

a first receiving module, configured to receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, where the network slice termination request carries a network slice service identifier S-NSSAI requesting to close, 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 the SNSI, the S-NSSAI, and the NSI are bound to each other;

a first release module, configured to release a binding relationship between the SNSI, the S-NSSAI, and the NSI when 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 according to the S-NSSAI, the identifier of the NSI, and the identifier of the SNSI.

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

a second receiving module, configured to receive a network slice subnet termination request sent by the SNSMF, where the network slice subnet termination request carries an identifier of an S-NSSAI and an identifier of an NSI, an identifier of an SNSI, and an identifier of an SNSSI that are bound to each other;

and the second removing module is used for removing the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI under the condition that the network slice service corresponding to the S-NSSAI is determined to be the last service associated with the SNSSI, the NSI is the last NSI associated with the SNSSI and the SNSI is determined to be the last SNSI associated with the SNSSI according to the S-NSSAI, the NSI identifier, the SNSI identifier and the SNSSI identifier.

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

a third receiving module, configured to receive a virtual network element instance termination request sent by an SNSSMF, where the virtual network element termination request carries an identifier of an S-NSSAI, an identifier of an NSI, an identifier of an SNSI, an identifier of an SNSSI, and an identifier of a virtual network element instance that are bound to each other, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

a third removing module, configured to remove the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI, 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 NSI identifier, the SNSI identifier, the NSSI identifier, and the virtual network element instance identifier;

a first sending module, configured to send a virtual network element instance termination result to the SNSSMF.

In an eighth aspect, an embodiment of the present invention further provides an NSMF, including:

the fourth receiving module is used for receiving a service shutdown request of S-NSSAI sent by a communication service management function CSMF;

a fourth removing module, configured to remove a binding relationship between the S-NSSAI and the NSI when the network slice service corresponding to the S-NSSAI is a last service associated with the network slice instance NSI bound by the S-NSSAI;

a second sending module, configured to send a network slice termination request to the SNSMF, so that the SNSMF releases a binding relationship between the SNSI, the S-NSSAI, and the NSI;

the fourth receiving module is further configured to receive a target termination result sent by SNSMF, where, when SNSSMF receives a virtual network element instance termination result sent by MANO, the target termination result includes a virtual network element instance termination result, a shared network slice subnet termination result, and a shared network slice termination result;

and a second sending module, configured to send the target termination result to the CSMF.

In a ninth aspect, an embodiment of the present invention further provides a network device, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps of the processing method for a network slice service as described above.

In a tenth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a program or an instruction is stored on the computer-readable storage medium, and when executed by a processor, the program or the instruction implements the steps of the processing method for the network slice service described above.

In the embodiment of the invention, the network slice management function SNSMF of the shared network receives a network slice termination request sent by the network slice management function NSMF of the unshared network, determines 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 under the condition that the network slice termination request carries the identifier S-NSSAI of the network slice service requesting to be shut down, the identifier of the network slice instance NSI of the unshared network and the identifier of the SNSI, and releases the binding relationship among the SNSI, the S-NSSAI and the NSI, so that the network slice instance SNSI in the shared network is released from the binding relationship between the network slice service requesting to be shut down and the network slice instance of the unshared network, the network slice instance SNSI in the shared network can be used by the subsequent network slice service, and the process of creating a new SNSI for the subsequent network slice service is omitted, the opening efficiency of the network slicing service is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a schematic structural diagram of an unshared network and a shared network of different operators according to an embodiment of the present invention;

fig. 2 is a flowchart of a method for processing a network slicing service according to an embodiment of the present invention;

fig. 3 is a flowchart of a processing method of another network slicing service according to an embodiment of the present invention;

fig. 4 is a flowchart of a processing method of another network slicing service according to an embodiment of the present invention;

fig. 5 is a flowchart of a processing method of another network slicing service according to an embodiment of the present invention;

fig. 6 is an interaction flowchart of a processing method of a network slicing service according to an embodiment of the present invention;

fig. 7 is a structural diagram of SNSMF according to an embodiment of the present invention;

fig. 8 is a structural diagram of an SNSSMF according to an embodiment of the present invention;

FIG. 9 is a block diagram of a MANO provided by an embodiment of the present invention;

FIG. 10 is a block diagram of a NSMF provided in accordance with an embodiment of the present invention;

fig. 11 is a schematic hardware structure diagram of a network device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

To help better understand the embodiments of the present invention, before introducing the present solution, a schematic structural diagram of the unshared network and the shared network of different operators is given below. As shown in fig. 1, 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 Slice Subnet Management function) connected in sequence. The CSMF interacts with the NSMF, each sub-domain NSSMF and a virtualized resource arranging and managing function MANO to complete the deployment and termination of the network slice example so as to realize the opening and closing of the network slice service. The shared network comprises SNSMF and SNSSMF connected with the SNSMF, wherein the SNSMF is a network slice management function of the shared network, and the SNSSMF is a network slice subnet management function of the shared network. The NSMFs of different unshared networks are connected by SNSMF.

In the embodiment of the invention, the SNSI of the network slice example of the shared network is released from the binding relationship between the network slice service requesting to be shut down and the network slice example of the unshared network, so that the SNSI can be used by the subsequent network slice service, a process of creating a new SNSI for the subsequent network slice service is omitted, and the opening efficiency of the network slice service is improved.

Referring to fig. 2, fig. 2 is a flowchart of a processing method of a network slice service according to an embodiment of the present invention, which is applied to a network slice management function SNSMF of a shared network, and as shown in fig. 2, the processing method includes the following steps:

step S201, receiving a network slice termination request sent by a network slice management function NSMF of a non-shared network, where the network slice termination request carries a network slice service identifier S-NSSAI requesting to close, 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 the SNSI, the S-NSSAI, and the NSI are bound to each other.

When an operator needs to shut down a certain network slice service, the operator can send a network slice service shutdown request to the NSMF on the CSMF in the non-shared network. The network slice service shutdown request carries the standard S-NSSAI of the network slice service requested to be shut down. After receiving the network slice service shutdown request, the NSMF deletes the service configuration of the network slice service represented by the S-NSSAI. The NSMF stores a binding relationship between the S-NSSAI and an identifier of the network slice instance NSI, and the 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 the S-NSSAI is the last service associated with the NSI, it may be determined that the NSI only binds the network slice service requested to be closed, and at this time, the NSMF releases the binding relationship between the S-NSSAI and the NSI, thereby releasing the NSI from the binding relationship, so that the NSI can be used by the subsequent network slice service of the operator.

The NSMF also stores the binding relationship among the identifiers of the NSI, the S-NSSAI and the network slice instance SNSI of the shared network, and the identifiers of the NSI, the S-NSSAI and the SNSI are bound with each other. After the NSMF releases the binding relationship between the NSI and the S-NSSAI, the NSMF generates a network slice termination request based on the binding relationship between the identification of the NSI, the identification of the S-NSSAI and the identification of the SNSI. It is understood that the network slice termination request carries the identities of the mutually bound NSI, S-NSSAI and SNSI. The NSMF then sends a network slice termination request to the SNSMF.

Step S202, when the network slice service corresponding to the S-NSSAI is determined to be the last service associated with the SNSI according to the S-NSSAI, the NSI identifier and the SNSI identifier, and the NSI is determined to be the last NSI associated with the SNSI, the binding relationship among the SNSI, the S-NSSAI and the NSI is released.

After receiving the network slice termination request, the SNSMF analyzes the network slice termination request to obtain the NSI identifier, the S-NSSAI identifier and the SNSI identifier. The SNSMF stores the binding relationship of S-NSSAI, NSI and SNSI, firstly finds out the corresponding SNSI based on the identification of the SNSI, and determines whether the network slice service corresponding to the S-NSSAI is the last service related to the SNSI. And if the network slice service corresponding to the S-NSSAI is the last service related to the SNSI, determining that the SNSI only binds the network slice service requesting to be shut down. The SNSMF determines whether the NSI is the last NSI associated with the SNSI, if the NSI is the last NSI associated with the SNSI, the SNSMF can determine that the SNSI only binds the NSI bound by the network slice service requesting to be shut down, and at the moment, the SNSMF releases the binding relation among the SNSI, the S-NSSAI and the NSI, so that all the binding relation of the SNSI is released, namely the SNSI is released.

Because the released SNSI is not bound with any NSI and network slice service, when an operator opens a new network slice service, the SNSI can be simply changed, and then the changed SNSI is bound with the new network slice service identifier and the NSI bound with the network slice service identifier, so that a new SNSI does not need to be created for the new network slice service, and the opening efficiency of the network slice service is improved.

The network slice service processing method of the embodiment of the invention comprises the steps that 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, determines that a network slice service corresponding to S-NSSAI is the last service related to SNSI under the condition that the network slice termination request carries a network slice service identifier S-NSSAI requesting to be shut down, an identifier of a network slice instance NSI of the non-shared network and an identifier of SNSI, and releases the binding relationship among SNSI, S-NSSAI and NSI, thereby releasing the network slice instance SNSI in the shared network from the binding relationship between the network slice service requesting to be shut down and the network slice instance of the non-shared network, and further enabling the network slice instance SNSI in the shared network to be used by subsequent network slice services, the process of creating a new SNSI for the subsequent network slicing service is omitted, and the opening efficiency of the network slicing service is improved.

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:

and sending a network slice subnet termination request to a network slice subnet management function SNSSMF of the shared network so that the SNSSMF can release the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI of the network slice subnet of the shared network.

The SNSMF also stores the binding relationship among the identifiers of the NSI, the S-NSSAI and the SNSI and the identifiers of the network slice subnet instances SNSSI of the shared network, and the identifiers of the NSI, the S-NSSAI and the SNSI and the identifiers of the SNSSI are bound with 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 identity of NSI, the identity of S-NSSAI, SNSI and the identity of SNSSI. It is understood that the network slice subnet termination request carries the identities of the mutually bound NSI, S-NSSAI, SNSI, and SNSSI. SNSMF then sends the network slice termination subnet request to SNSSMF.

And the SNSSMF can request to release the binding relation among the SNSSI, the S-NSSAI, the NSI and the SNSI based on the network slice termination subnet.

Specifically, after receiving the network slice subnet termination request, the 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 SNSSMF stores the binding relationship of S-NSSAI, NSI, SNSI and SNSSI, finds the corresponding SNSSI based on the identification of SNSSI, and determines whether the network slice service corresponding to S-NSSAI is the last service related to SNSSI. And if the network slice service corresponding to the S-NSSAI is the last service associated with the SNSSI, determining that the SNSSI only binds the network slice service requested to be shut down. And the SNSSMF determines whether the NSI is the last NSI associated with the SNSSI, and if the NSI is the last NSI associated with the SNSSI, the SNSSI can be determined to only bind the NSI bound by the network slice service which requests to be shut down. And finally, the SNSSMF determines whether the SNSI is the last SNSI associated with the SNSSI, and if the SNSI is the last SNSI associated with the SNSSI, the SNSSI can be determined to only bind the SNSI bound by the network slice service requesting to be shut down. At this time, SNSSMF releases the binding relationship among SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all the binding relationship of SNSSI, i.e. releasing SNSSI.

Because the released SNSSI is not bound with any NSI, SNSI and network slicing service, when an operator opens a new network slicing service, the operator can simply change the SNSSI, and then the changed SNSSI is bound with the identifier of the new network slicing service, the NSI bound with the identifier of the network slicing service and the SNSI bound with the identifier of the network slicing service, so that a new SSNSI does not need to be created for the new network slicing service, and the opening efficiency of the network slicing service is further improved.

Optionally, the step of releasing the binding relationship among the SNSI, the S-NSSAI, and the NSI includes:

determining a termination type of the SNSI;

when the termination type of the SNSI is SNSI reservation, releasing the binding relationship among the SNSI, the S-NSSAI and the NSI;

and under the condition that the termination type of the SNSI is termination of the SNSI, removing the binding relationship among the SNSI, the S-NSSAI and the NSI, and deleting the record corresponding to the SNSI.

SNSMF stores the termination type of the network slice instance SNSI. The termination types of SNSI include both retention SNSI and termination 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 reserve the SNSI; if the user confirms that the SNSI has no value available, the termination type may be set to terminate the SNSI. Furthermore, a function of setting a termination type of SNSI for the SNSMF deployment may be deployed, on which standard parameters characterizing the SNSI having a usable value are deployed. If the actual parameters in the SNSI in the SNSMF acquired by the function are larger than the standard parameters, the SNSI can be determined to have available value, at the moment, the function sends a request for reserving the SNSI to the SNSMF, and the SNSMF sets the termination type of the SNSI as the reserved SNSI; if the actual parameter in the SNSI in the SNSMF acquired by the function is less than or equal to the standard parameter, the function sends a request for terminating the SNSI to the SNSMF, and the SNSMF sets the termination type of the SNSI as the termination SNSI. The standard parameter may be a network capability parameter of the SNSI, the network capability parameter is classified into a numerical type and an enumerated type according to a value type, for example, parameters which can be expressed by specific values such as rate and network delay may be classified as numerical type parameters, and non-numerical type parameters which are usually expressed by strong, medium, and low values such as isolation, reliability, and security may be classified as enumerated type parameters.

The SNSMF firstly determines the termination type of the SNSI, and if the termination type of the SNSI is SNSI reservation, the binding relationship among the SNSI, the S-NSSAI and the NSI is released. Disassociation refers to the deletion of the identity of the NSI and the S-NSSAI. And if the termination type of the SNSI is termination of the SNSI, removing the binding relationship among the SNSI, the S-NSSAI and the NSI, and deleting the record corresponding to the SNSI. Deleting the record corresponding to the SNSI means deleting all records corresponding to the SNSI, deleting a record corresponding to the sni-bound NSI, and deleting a record corresponding to the SNSI-bound S-NSSAI.

In this embodiment, the SNSMF determines, by the termination type of the SNSI, whether to retain the record corresponding to the SNSI or delete the record corresponding to the SNSI, thereby deleting the record corresponding to the SNSI reasonably.

Optionally, before step S201, the method further includes:

receiving a deleting instruction which is sent by the NSMF and carries the S-NSSAI;

deleting the service configuration of the network slice service corresponding to the S-NSSAI, and sending the deletion instruction to the SNSSMF so that the SNSSMF deletes the service configuration.

When receiving a network slice service shutdown request, the NSMF deletes service configuration corresponding to the network slice service requested to be shutdown. And the NSMF generates a deleting instruction according to the identifier S-NSSAI of the network slice service requested to be closed, and sends the deleting instruction to the SNSMF. And the SNSMF analyzes the deleting instruction to obtain the S-NSSAI, so that the service configuration of the network slicing service corresponding to the S-NSSAI is deleted. And the SNSMF sends the deletion instruction to the SNSSMF so that the SNSSMF deletes the service configuration of the network slice service corresponding to the S-NSSAI.

The function of not sharing power and the function of sharing network have the characteristic of sharing layer by layer. Therefore, after deleting the service configuration of the network slice service corresponding to the S-NSSAI, the NSMF notifies the NSSMF connected to the NSMF and the SNSMF to delete the service configuration of the network slice service corresponding to the S-NSSAI; after the SNSMF deletes the service configuration of the network slicing service corresponding to the S-NSSAI, the SNSMF and the MANO connected with the SNSMF are informed to delete the service configuration of the network slicing service corresponding to the S-NSSAI.

In the embodiment, the SNSMF deletes the service configuration of the network slicing service corresponding to the S-NSSAI, so that more resources can be released, the network rate of the SNSMF is increased, and the activation efficiency of the subsequent network slicing service is increased.

Referring to fig. 3, fig. 3 is a flowchart of a processing method of another network slicing service according to an embodiment of the present invention, which is applied to SNSSMF, and the method includes:

step S301, receiving a network slice subnet termination request sent by SNSMF, wherein the network slice subnet termination request carries an S-NSSAI, an NSI identifier, an SNSI identifier and an SNSSI identifier which are bound with each other.

Step S302, when the network slice service corresponding to the S-NSSAI is determined to be the last service related to the SNSSI, the NSI is the last NSI related to the SNSSI, and the SNSI is determined to be the last SNSI related to the SNSSI according to the S-NSSAI, the NSI, the SNSI and the SNSSI, the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI is released.

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 identity of NSI, the identity of S-NSSAI, SNSI and the identity of SNSSI. It is understood that the network slice subnet termination request carries the identities of the mutually bound NSI, S-NSSAI, SNSI, and SNSSI. And the SNSMF sends the network slice termination subnet request to the SNSSMF. SNSMF then sends a network slice subnet termination request to SNSSMF.

Specifically, after receiving the network slice subnet termination request, the 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 SNSSMF stores the binding relationship of S-NSSAI, NSI, SNSI and SNSSI, finds the corresponding SNSSI based on the identification of SNSSI, and determines whether the network slice service corresponding to S-NSSAI is the last service related to SNSSI. And if the network slice service corresponding to the S-NSSAI is the last service related to the SNSSI, determining that the SNSSI only binds the network slice service which is requested to be shut down. And the SNSSMF determines whether the NSI is the last NSI associated with the SNSSI, and if the NSI is the last NSI associated with the SNSSI, the SNSSI can be determined to only bind the NSI bound by the network slice service which requests to be shut down. And finally, the SNSSMF determines whether the SNSI is the last SNSI associated with the SNSSI, and if the SNSI is the last SNSI associated with the SNSSI, the SNSSI can be determined to only bind the NSSI bound by the network slice service requesting to be shut down. At this time, SNSSMF releases the binding relationship among SNSSI, S-NSSAI, NSI and SNSI, thereby releasing all the binding relationship of SNSSI, i.e. releasing SNSSI.

In this embodiment, the released SNSSI does not bind any NSI, SNSI, and network slicing service, and when an operator opens a new network slicing service, the operator may simply change 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, and thus it is not necessary to create a new SSNSI for the new network slicing service, and the opening efficiency of the network slicing service is further improved.

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

and sending a virtual network element instance termination request to a virtualized resource orchestration management function (MANO) so that the MANO releases the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI.

The SNSSMF also stores the identifiers of the NSI, the S-NSSAI and the SNSI, the identifiers of the SNSSI and the binding relationship among the virtual network element instances, and the identifiers of the NSI, the S-NSSAI and the SNSI, the identifiers of the SNSSI and the virtual network element instances are bound with each other. The virtual network element instance comprises a network service instance NS or a virtualized network element instance VNF.

After SNSSMF releases the binding relationship among SNSSI, S-NSSAI, NSI and SNSI, SNSMF generates a virtual network element instance termination request based on the binding relationship among the identification of NSI, the identification of S-NSSAI, the identification of SNSI, the identification of SNSSI and the identification of virtual network element instance. It can be understood that the virtual network element instance termination request carries an identifier of an NSI, an identifier of an S-NSSAI, an identifier of an SNSI, an identifier of an SNSSI, and an identifier of a virtual network element instance that are bound to each other. SNSSMF sends the virtual network element instance termination request to the MANO.

The MANO releases the binding relation among the SNSSI, the S-NSSAI, the NSI, the SNSI and the virtual network element instance based on the virtual network element instance termination request.

Specifically, after receiving the network element instance termination request, the MANO analyzes the virtual network element instance termination request to obtain an NSI identifier, an S-NSSAI identifier, an SNSI identifier, an SNSSI identifier and a virtual network element instance identifier. The MANO stores the binding relation of the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI, firstly finds the corresponding virtual network element instance based on the virtual network element instance identification, and determines whether the network slicing 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 only binds the network slice service requesting for shutdown. And the MANO determines whether the NSI is the last NSI associated with the virtual network element instance, and if the NSI is the last NSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the NSI bound by the network slice service requesting to be shut down. And the MANO determines whether the SNSI is the last SNSI associated with the virtual network element instance, and if the SNSI is the last SNSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the SNSI bound by the network slice service requesting to be shut down. And finally, the MANO determines whether the SNSSI is the last SNSSI associated with the virtual network element instance, and if the SNSSI is the last SNSSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the SNSSI bound by the network slice service requesting to be shut down. At this time, the MANO releases the binding relationship among the virtual network element instance, the SNSSI, the S-NSSAI, the NSI and the SNSI, thereby releasing all the binding relationship of the virtual network element instance, namely releasing the virtual network element instance.

Because the released virtual network element instance is not bound with any NSI, SNSI, SNSSI and network slicing service, when an operator opens a new network slicing service, the operator can simply change the virtual network element instance, and then the changed virtual network element instance is bound with the identifier of the new network slicing service, the NSI bound with the identifier of the network slicing service, the SNSI bound with the identifier of the network slicing service and the SNSSI bound with the identifier of the network slicing service, so that the new virtual network element instance is not required to be created for the new network slicing service, and the opening efficiency of the network slicing service is further improved.

Optionally, the step of releasing the binding relationship among the SNSSI, the S-NSSAI, the NSI, and the SNSI includes:

determining a termination type of the SNSSI;

when the termination type of the SNSSI is SNSSI reservation, removing the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI;

and under the condition that the termination type of the SNSSI is termination of the SNSSI, removing the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI, and deleting the record corresponding to the SNSSI.

SNSSMF stores the termination type of the network slice instance SNSSI. The termination types of SNSSI include both reserved SNSSI and terminated 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 the SNSSI; if the user confirms that the SNSSI does not have available value, the termination type may be set to terminate the SNSSI. In addition, a function of the termination type of the SNSSI can be set for the SNSSMF deployment, and standard parameters which characterize the SNSSI to have available value are deployed on the function. If the actual parameters in the SNSSI in the SNSSMF acquired by the function are larger than the standard parameters, the SNSSI can be determined to have available value, at the moment, the function sends a request for keeping the SNSSI to the SNSMF, and the SNSSMF sets the termination type of the SNSSI as keeping the SNSSI; if the actual parameters in the SNSSI in the SNSSMF acquired by the function are less than or equal to the standard parameters, the function sends a request for stopping the SNSSI to the SNSSMF, and the SNSSMF sets the type of stopping the SNSSI as the type of stopping the SNSSI. The standard parameter may be a network capability parameter of SNSSI, the network capability parameter is divided into a numerical type and an enumerated type parameter according to a value type, for example, parameters which can be expressed by specific values such as speed and network delay may be classified as numerical type parameters, and non-numerical type parameters which are usually expressed by strong, medium, and low values such as isolation, reliability, and security may be classified as enumerated type parameters.

The SNSSMF determines the termination type of the SNSSI, and if the termination type of the SNSSI is the reserved SNSSI, the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI is released. Disassociation refers to the deletion of the NSI identity, SNSI identity, and S-NSSAI. And if the termination type of the SNSSI is termination of the SNSSI, removing the binding relationship among the SNSSI, the SNSI, the S-NSSAI and the NSI, and deleting the record corresponding to the SNSSI. Deleting the record corresponding to the SNSSI refers to deleting all records corresponding to the SNSSI, deleting the record corresponding to the sni-bound NSI, deleting the record corresponding to the SNSI-bound SNSI, and deleting the record corresponding to the SNSI-bound S-NSSAI.

In this embodiment, the SNSSMF determines whether to keep the record corresponding to the SNSSI or delete the record corresponding to the SNSSI according to the termination type of the SNSSI, so as to reasonably delete the record of the SNSSI.

Optionally, before step S301, the method further includes:

receiving a deleting instruction which is sent by the SNSMF and carries the S-NSSAI;

and deleting the service configuration of the network slice service corresponding to the S-NSSAI, and sending the deletion instruction to the MANO so that the MANO deletes the service configuration.

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

The function of not sharing power and the function of sharing network have the characteristic of sharing layer by layer. Therefore, after deleting the service configuration of the network slicing service corresponding to the S-NSSAI, the SNSSMF informs the connection MANO of deleting the service configuration of the network slicing service corresponding to the S-NSSAI.

In the embodiment, the SNSSMF deletes the service configuration of the network slicing service corresponding to the S-NSSAI, so that more resources can be released, the network rate of the SNSSMF is increased, and the activation efficiency of the subsequent network slicing service is increased.

Referring to fig. 4, fig. 4 is a flowchart of a processing method for a network slicing service according to another embodiment of the present invention, which is applied to a MANO, and the method includes:

step S401, receiving a virtual network element instance termination request sent by SNSSMF, wherein the virtual network element termination request carries an S-NSSAI, an NSI identifier, an SNSI identifier, an SNSSI identifier and an identifier of a virtual network element instance which are bound with each other, and the virtual network element instance comprises a network service instance NS or a virtualized network element instance VNF;

after SNSSMF releases the binding relationship among SNSSI, S-NSSAI, NSI and SNSI, SNSMF generates a virtual network element instance termination request based on the binding relationship among the identification of NSI, the identification of S-NSSAI, the identification of SNSI, the identification of SNSSI and the identification of virtual network element instance. The virtual network element instance comprises 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 an identifier of an NSI, an identifier of an S-NSSAI, an identifier of an SNSI, an identifier of an SNSSI, and an identifier of a virtual network element instance that are bound to each other. SNSSMF sends the virtual network element instance termination request to the MANO.

Step S402, when the network slice service corresponding to the S-NSSAI is determined to be 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 NSI identifier, the SNSI identifier, the NSSI identifier and the virtual network element instance identifier, the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI is released.

Specifically, after receiving the virtual network element instance termination request, the MANO analyzes the virtual network element instance termination request to obtain an NSI identifier, an S-NSSAI identifier, an SNSI identifier, an SNSSI identifier and a virtual network element instance identifier. The MANO stores the binding relation of the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI, firstly finds the corresponding virtual network element instance based on the virtual network element instance identification, and determines whether the network slicing 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 only binds the network slice service requesting for shutdown. And the MANO determines whether the NSI is the last NSI associated with the virtual network element instance, and if the NSI is the last NSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the NSI bound by the network slice service requesting to be shut down. And the MANO determines whether the SNSI is the last SNSI associated with the virtual network element instance, and if the SNSI is the last SNSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the SNSI bound by the network slice service requesting to be shut down. And finally, the MANO determines whether the SNSSI is the last SNSSI associated with the virtual network element instance, and if the SNSSI is the last SNSSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the SNSSI bound by the network slice service requesting to be shut down. At this time, the MANO releases the binding relationship among the virtual network element instance, the SNSSI, the S-NSSAI, the NSI and the SNSI, thereby releasing all the binding relationship of the virtual network element instance, namely releasing the virtual network element instance.

Step S403, sending the termination result of the virtual network element instance to the SNSSMF.

And after removing the binding relation among the SNSSI, the S-NSSAI, the NSI and the SNSI, the MANO sends a virtual network element instance termination result to the SNSSMF. The termination result of the virtual network element instance is whether the virtual network element instance is unbound. The SNSSMF receives the termination result of the virtual network element instance, sends the termination result of the network slice subnet of the SNSSMF and the termination result of the virtual network element instance to the SNSMF, and finally sends the termination result of the network slice subnet of the SNSMF, the termination result of the network slice subnet of the SNSMF and the termination result of the virtual network element instance to the NSMF.

In this embodiment, because the released virtual network element instance is not bound to any NSI, SNSI, SNSSI, or network slicing service, when an operator opens a new network slicing service, the operator may simply change the virtual network element instance, 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, without creating a new virtual network element instance for the new network slicing service, thereby further improving the opening efficiency of the network slicing service.

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

determining a termination type of the virtual network element instance;

removing the binding relation among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI under the condition that the termination type of the virtual network element instance is the reserved virtual network element instance;

and under the condition that the termination type of the virtual network element instance is termination of the virtual network element instance, removing the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI, and deleting the record of the virtual network element instance.

The MANO stores the termination type of the virtual network element instance. The termination type of the virtual network element instance includes both a reserved virtual network element instance and a terminated 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 the available value, the termination type can be set as the termination virtual network element instance. In addition, a function for setting the termination type of the virtual network element instance can be deployed for the MANO, and standard parameters for representing the available value of the virtual network element instance are deployed on the function. If the actual parameters in the virtual network element instance in the MANO acquired by the function are larger than the standard parameters, the virtual network element instance can be determined to have available value, at the moment, the function sends a request for reserving the virtual network element instance to the MANO, and the MANO sets the termination type of the virtual network element instance as the reserved virtual network element instance; if the actual parameter in the virtual network element instance in the MANO acquired by the function is less than or equal to the standard parameter, the function sends a request for terminating SNSSI to SNSSMF, and the MANO sets the termination type of the virtual network element instance as the termination of the virtual network element instance. The standard parameter may be a network capability parameter of a virtual network element instance, the network capability parameter is divided into a numerical type and an enumeration type parameter according to a value type, for example, parameters which can be represented by specific values such as rate and network delay may be classified as numerical type parameters, and non-numerical type parameters which are generally represented by strong, medium, and low values such as isolation, reliability, and security may be classified as enumeration type parameters.

The MANO firstly determines the termination type of the virtual network element instance, and if the termination type of the virtual network element instance is the reserved virtual network element instance, the binding relationship among the virtual network element instance, the SNSSI, the S-NSSAI, the NSI and the SNSI is released. Disassociation refers to the deletion of the NSI identity, SNSI identity, SNSSI identity and S-NSSAI. And if the termination type of the virtual network element instance is termination of the virtual network element instance, removing the binding relationship among the virtual network element instance, the SNSSI, the SNSI, the S-NSSAI and the NSI, and deleting the record corresponding to the virtual network element instance. Deleting the record corresponding to the virtual network element instance means deleting all records corresponding to the virtual network element instance, deleting the record corresponding to the NSI bound to the virtual network element instance, deleting the record corresponding to the SNSI bound to the virtual network element instance, deleting the record corresponding to the SNSSI bound to the virtual network element instance, and deleting the record corresponding to the S-NSSAI bound to the virtual network element instance.

In this embodiment, the MANO determines, through the termination type of the virtual network element instance, whether to retain the record corresponding to the virtual network element instance or delete the record corresponding to the virtual network element instance, so as to reasonably delete the record of the virtual network element instance.

Optionally, before step S401, the method further includes:

receiving a deletion instruction which is sent by the SNSSMF and carries the S-NSSAI;

and deleting the service configuration of the network slice service corresponding to the S-NSSAI.

After deleting the service configuration of the network slicing service corresponding to the S-NSSAI, the SNSSMF sends a deletion instruction to the MANO. And the MANO analyzes the deletion instruction to obtain SNSSAI, thereby deleting the service configuration of the network slice service corresponding to the S-NSSAI and releasing more resources on the MANO.

Referring to fig. 5, fig. 5 is a flowchart of a processing method of a further network slicing service according to an embodiment of the present invention, where the method is applied to the NSMF, and the method includes:

step S501, receiving a service shutdown request which is sent by a communication service management function CSMF and carries S-NSSAI.

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

Step S502, under the condition that the network slice service corresponding to the S-NSSAI is the last service associated with the network slice instance NSI bound by the S-NSSAI, removing the binding relationship between the S-NSSAI and the NSI.

After receiving a network slice service shutdown request, the NSMF deletes the service configuration of the network slice service represented by the S-NSSAI. The NSMF stores a binding relationship between the S-NSSAI and an identifier of the network slice instance NSI, and the 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 the S-NSSAI is the last service associated with the NSI, it can be determined that the NSI only binds the network slice service requested to be closed, and at this time, the NSMF releases the binding relationship between the S-NSSAI and the NSI, so that the NSI is released from the binding relationship, and the NSI can be used by the subsequent network slice service of the operator.

Step S503, sending a network slice termination request to the SNSMF so that the SNSMF releases the binding relationship among SNSI, S-NSSAI and NSI.

Step S504, receiving a target termination result sent by SNSMF, wherein under the condition that SNSSMF receives a virtual network element instance termination result sent by MANO, a network slice subnet termination result of a shared network and the virtual network element instance termination result are sent to SNSMF, and the target termination result comprises a virtual network element instance termination result, a network slice subnet termination result of the shared network and a network slice termination result of the shared network;

after NSMF sends the network slice termination request to SNSMF, SNSMF releases the binding relationship between SNSI, NSI and S-NSSAI. And the SNSMF sends a network slice subnet termination request to the SNSSMF so that the SNSSMF releases the binding relationship among SNSSI, SNSI, NSI and S-NSSAI. SNSSMF sends a virtual network element instance termination request to the MANO, so that the MANO releases the binding relationship among the virtual network element instance, SNSSI, SNSI, NSI and S-NSSAI. And the MANO sends the termination result of the virtual network element instance to the SNSSMF. The SNSSMF receives the termination result of the virtual network element instance, and sends the termination result of the network slice subnet of the SNSSMF and the termination result of the virtual network element instance to the SNSMF, and the SNSMF finally sends the termination result of the network slice subnet of the SNSMF, the termination result of the network slice subnet of the SNSMF and the termination result of the virtual network element instance to the NSMF, namely the NSMF receives the target termination result of the SNSMF, which 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.

And step S505, sending the target termination result to the CSMF.

And after receiving the target termination result, the NSMF sends the target termination result to the CSMF. The target termination result refers to the network slice termination result of the shared network, and the NSMF needs to send the network slice termination result of the unshared network to the CSMF.

Specifically, the NSMF sends a network slice subnet termination request of the non-shared network to the NSSMF while sending a network slice termination request of the shared network to the SNSMF.

The network slice subnet termination request of the unshared network carries the identifications of the mutually bound NSI, the identification of the S-NSSAI and the identification of the network slice subnet instance NSSI of the unshared network. And after receiving the network slice subnet termination request, the NSSMF analyzes the network slice subnet termination request to obtain the NSI identifier, the S-NSSAI identifier and the NSSI identifier. The NSSMF stores the binding relationship of the S-NSSAI, the NSI and the NSSI, firstly, the NSSMF finds the corresponding NSSI based on the NSSI identification, and determines whether the network slice service corresponding to the S-NSSAI is the last service related to 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 only binds the network slice service requested to be closed. The NSSMF determines whether the NSI is the last NSI associated with the NSSI, and if the NSI is the last NSI associated with the NSSI, it may determine that the NSSI only binds to the NSI bound by the network slice service requesting to close, and at this time, the NSSMF releases the binding relationship among the NSSI, the S-NSSAI, and the NSI, thereby releasing all the binding relationships of the NSSI, that is, the NSSI is released. The NSSMF stores the termination type of the NSSI, and if the termination type of the NSSI is the reserved NSSI, the binding relationship among the NSSI, the S-NSSAI and the NSI is released; if the termination type of the NSSI is termination NSSI, removing the binding relationship among the NSSI, the S-NSSAI and the NSI, and deleting the record corresponding to the NSSI.

After NSSMF releases NSSI, NSSMF generates a virtual network element instance termination request based on the binding relationship among the NSI identifier, the S-NSSAI identifier, the NSSI identifier and the virtual network element instance identifier. The virtual network element instance comprises 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 identities of the mutually bound NSI, S-NSSAI, NSSI, and virtual network element instance identity. The NSSMF then sends a virtual network element instance termination request to the MANO.

The MANO releases the NSSI, S-NSSAI, NSI and the binding relationship between the virtual network element instances based on the virtual network element instance termination request.

Specifically, after receiving the virtual network element instance termination request, the MANO analyzes the virtual network element instance termination request to obtain an NSI identifier, an S-NSSAI identifier, an NSSI identifier and a virtual network element instance identifier. The MANO stores the binding relation of the virtual network element instance, the S-NSSAI, the NSI and the NSSI, firstly finds the corresponding virtual network element instance based on the virtual network element instance identification, and determines whether the network slicing 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 only binds the network slice service requesting for shutdown. And the MANO determines whether the NSI is the last NSI associated with the virtual network element instance, and if the NSI is the last NSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the NSI bound by the network slice service requesting to be shut down. And the MANO determines whether the NSSI is the last NSSI associated with the virtual network element instance, and if the NSSI is the last NSSI associated with the virtual network element instance, the MANO can determine that the virtual network element instance only binds the NSSI bound by the network slice service requesting to be shut down. At this time, the MANO releases the binding relationship among the virtual network element instance, the NSSI, the S-NSSAI and the NSI, thereby releasing all the binding relationship of the virtual network element instance, namely releasing the virtual network element instance. The MANO releases the binding relationship among the virtual network element instance, the NSSI, the S-NSSAI, and the NSI according to the termination type of the virtual network element instance, and the specific principle refers to the above description and is not described again. It should be noted that the binding relationship between the MANO released virtual network element instance, NSSI, S-NSSAI, and NSI relates to the release of a virtual network element instance of a non-shared network, while the binding relationship between the MANO released virtual network element instance, SNSSI, S-NSSAI, NSI, and SNSI relates to the release of a virtual network element instance of a shared network, and the two virtual network element instances are not the same. The virtual network element instances of the shared network may be represented by a first virtual network element instance and the virtual network element instances of the non-shared network may be represented by a second virtual network element instance.

And after the binding relation among the NSSI, the S-NSSAI and the NSI is released, the MANO sends a virtual network element instance termination result to the NSSMF. The termination result of the virtual network element instance is whether the virtual network element instance is unbound. The NSSMF receives the virtual network element instance termination result, and sends the network slice subnet termination result and the virtual network element instance termination result to the NSMF, and the NSMF finally sends the network slice termination result, the network slice subnet termination result and the virtual network element instance termination result to the NSMF. I.e., the NSMF gets the network slice termination result for the unshared network.

The NSMF aggregates the network slice termination results of the non-shared network and the network slice termination results of the shared network and sends the network slice termination results of the non-shared network to the CSMF, so that a user can know the instance termination results on each function based on the CSMF.

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

determining a termination type of the NSI;

removing the binding relationship between the S-NSSAI and the NSI under the condition that the termination type of the NSI is reserved NSI;

and under the condition that the termination type of the NSI is termination NSI, removing the binding relationship between the S-NSSAI and the NSI, and deleting the record corresponding to the NSI.

The NSMF stores the termination type of the NSI. Termination types of NSI include both retention NSI and termination NSI. The termination type may be set manually, and if the user confirms that the NSI has a usable value, the termination type may be set to reserve the NSI; if the user confirms that the NSI does not have value available, the termination type may be set to terminate the NSI. In addition, a function of the termination type of the NSI may be set for the NSMF deployment, on which standard parameters characterizing the NSI having a usable value are deployed. If the actual parameters in the NSI in the NSMF acquired by the function are larger than the standard parameters, determining that the NSI has available value, sending a request for reserving the NSI to the NSMF by the function at the moment, and setting the termination type of the NSI as reserved NSI by the NSMF; if the actual parameter in the NSI in the NSMF acquired by the function is less than or equal to the standard parameter, the function sends a request for terminating the NSI to the NSMF, and the NSMF sets the termination type of the NSI as the termination NSI. The standard parameter may be a network capability parameter of the NSI, the network capability parameter is classified into a numerical type and an enumerated type according to a value type, for example, parameters which can be expressed by specific values such as rate and network delay may be classified as numerical type parameters, and non-numerical type parameters which are expressed by strong, medium and low values such as isolation, reliability and safety may be classified as enumerated type parameters.

The NSMF determines the termination type of the NSI, and if the termination type of the NSI is reserved NSI, the binding relationship between the NSI and the S-NSSAI is released. Disassociating refers to deleting the S-NSSAI. And if the termination type of the NSI is termination NSI, removing the binding relationship between the NSI and the S-NSSAI and deleting the record corresponding to the NSI. Deleting the record corresponding to the NSI means deleting all the records corresponding to the NSI and deleting the record corresponding to the S-NSSAI to which the NSI is bound.

In this embodiment, the NSMF determines, according to the termination type of the NSI, whether to retain the record corresponding to the NSI or delete the record corresponding to the NSI, so as to reasonably delete the record of the NSI.

Based on the above embodiments, the processing method of the network slicing service provided by the present invention is briefly described. Referring to fig. 6, fig. 6 is an interaction flowchart of a method for processing a network slicing service according to an embodiment of the present invention, where the method includes:

and S1, CSMF sends the service closing request carrying the identification S-NSSAI of the network slice service requesting closing to NSMF.

And the S2 and the NSMF interact with the NSSMF, the SNSMF, the SNSSMF and the MANO in sequence, so that the service configuration corresponding to the S-NSSAI is deleted.

S3, if S-NSSAI is the last service associated with NSI, the NSMF selects 1 of the 2 termination types to release NSI; a retention of NSI: removing the binding relation between the S-NSSAI and the NSI; b termination of NSI: and removing the binding relation between the S-NSSAI and the NSI and deleting the record corresponding to the NSI.

The NSMF sends a network slice subnet termination request for the non-shared network (network slice subnet termination request includes S-NSSAI, NSI ID, NSSI ID) to the NSSMF to perform S4a-S9a, and sends a network slice termination request for the shared network (network slice termination request includes S-NSSAI, NSI ID, SNSI ID) to the SNSMF to perform S4b-S12b, i.e., steps S4a-S9a are performed in parallel with steps S4b-S12 b.

S4a, NSMF sends the network slice subnet termination request of the unshared network to NSSMF, and the network slice subnet termination request carries S-NSSAI, NSI ID and NSSI ID.

S5a, NSSMF releasing NSI according to 1 of the 2 termination types of NSSI if S-NSSAI is the last service of NSSI association and NSI is the last NSI of NSSI association; a retention NSSI: removing the binding relationship of S-NSSAI, NSI and NSSI; b termination of NSSI: and removing the binding relation among the S-NSSAI, the NSI and the NSSI and deleting the record corresponding to the NSSI.

S6a, NSSMF sends the termination request of virtual network element instance (network service NS/virtual network element VNF) to MANO, the termination request of virtual network element instance carries S-NSSAI, NSI ID, NSSI ID and NS ID/VNF ID.

S7a, if S-NSSAI, NSI, NSSI are the last service, the last NSI and the last NSSI associated with the NS/VNF instance, the MANO releases the virtual network element instance according to 1 of 2 termination types of the virtual network element instance; a reservation of NS/VNF: removing the binding relation of NS/VNF, S-NSSAI, NSI and NSSI; b termination of NS/VNF: removing the binding relation between the NS/VNFS-NSSAI, the NSI and the NSSI, and deleting the record corresponding to the NS/VNF;

s8a, the MANO informs the NSSMF network service NS/virtualized network element VNF termination result.

S9a, NSSMF informs the NSMF of the network slice subnet termination result for the unshared network.

And S4b, the NSMF sends a network slice termination request of the shared network to the SNSMF, and the network slice termination request of the shared network carries S-NSSAI, NSI ID and SNSI ID.

S5b, if S-NSSAI, NSI are the last service and last NSI associated with SNSI, respectively, SNSMF releases SNSI according to 1 of 2 termination types of SNSI; a, reserving SNSI: removing the binding relationship between S-NSSAI, NSI and SNSI; b termination of SNSI: and removing the binding relation among the S-NSSAI, the NSI and the SNSI, and deleting the record corresponding to the SNSI.

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

S7b, if S-NSSAI, NSI, SNSI are SNSSI associated last service, last NSI and last SNSI, SNSSMF releases SNSSI according to 1 of 2 termination types of SNSSI; a, keeping SNSSI: removing the binding relationship of SNSSI, S-NSSAI, NSI and SNSI; b termination of SNSSI: removing the binding relation of SNSSI, S-NSSAI, NSI and SNSI and deleting the record corresponding to SNSSI.

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

S9b, if S-NSSAI, NSI, SNSI, SNSSI are the last service, last NSI, last SNSI and last SNSSI associated with the NS/VNF instance, respectively, the MANO releases the NS/VNF according to 1 of 2 termination types of the NS/VNF; a reservation of NS/VNF: removing the binding relation between NS/VNF, SNSSI, S-NSSAI, NSI and SNSI; b termination of NS/VNF: and removing the binding relation among the NS/VNF, the SNSSI, the S-NSSAI and the NSI and the SNSI, and deleting the record corresponding to the NS/VNF.

S10b, MANO informs SNSSMF network service NS/virtualization network element VNF termination result.

S11b, SNSSMF informs SNSMF of the network slice subnet termination result of the shared network.

S12b, SNSMF informs the NSMF of the network slice termination result of the shared network.

And S13, the NSMF summarizes the network slice subnet termination result of the unshared network and the network slice termination result of the shared network.

And S14, NSMF informs CSMF of the result of the network slice service shutdown, and carries a service identifier S-NSSAI.

The embodiment of the invention also provides the SNSMF. Referring to fig. 7, fig. 7 is a structural diagram of SNSMF according to an embodiment of the present invention. Since the principle of solving the problem of 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 achieved technical effect can refer to the above description, and repeated parts are not repeated.

As shown in fig. 7, SNSMF700 includes:

a first receiving module 701, configured to receive a network slice termination request sent by a network slice management function NSMF of a non-shared network, where the network slice termination request carries a network slice service identifier S-NSSAI requesting to close, 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 the SNSI, the S-NSSAI, and the NSI are bound to each other;

a first removing module 702, configured to remove a binding relationship between the SNSI, the S-NSSAI, and the NSI when 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 according to the S-NSSAI, the identifier of the NSI, and the identifier of the SNSI.

Optionally, SNSMF700 includes:

and the sending module is used for sending a network slice subnet termination request to a network slice subnet management function SNSSMF of the shared network so as to enable the SNSSMF to remove the binding relationship among the SNSSI, the S-NSSAI, the NSI and the SNSI of the network slice subnet of the shared network.

Optionally, SNSMF700 includes:

a determining module, configured to determine a termination type of the SNSI;

a first releasing module 702, further configured to release the binding relationship among the SNSI, the S-NSSAI, and the NSI if the termination type of the SNSI is SNSI reservation;

the first removing module 702 is further configured to, if the termination type of the SNSI is termination SNSI, remove the binding relationship among the SNSI, the S-NSSAI, and the NSI, and delete the record corresponding to the SNSI.

Optionally, SNSMF700 includes:

a first receiving module 701, further configured to receive a deletion instruction carrying the S-NSSAI sent by the NSMF;

and the deleting module is used for deleting the service configuration of the network slice service corresponding to the S-NSSAI and sending the deleting instruction to the SNSSMF so that the SNSSMF deletes the service configuration.

The embodiment of the invention also provides an SNSSMF. Referring to fig. 8, fig. 8 is a structural diagram of an SNSSMF according to an embodiment of the present invention. Since the principle of solving the problem of the SNSSMF is similar to the processing method of the network slicing service in the embodiment of the present invention, the implementation of the SNSSMF and the achieved technical effect can refer to the above description, and the repeated parts are not repeated.

As shown in fig. 8, SNSSMF800 includes:

a second receiving module 801, configured to receive a network slice subnet termination request sent by an SNSMF, where the network slice subnet termination request carries an identifier of an S-NSSAI, an identifier of an NSI, an identifier of an SNSI, and an identifier of an SNSSMF that are bound to each other;

a second removing module 802, configured to remove the binding relationship among the SNSSI, the S-NSSAI, the NSI, and the SNSI when it is determined 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 according to the S-NSSAI, the NSI identifier, the SNSI identifier, and the SNSSI identifier.

Optionally, SNSSMF800 further includes:

a sending module, configured to send a virtual network element instance termination request to a virtualized resource orchestration management function MANO, so that the MANO releases a binding relationship among a virtual network element instance, the S-NSSAI, the NSI, the SNSI, and the SNSSI.

Optionally, SNSSMF800 further includes:

a determining module, configured to determine a termination type of the SNSSI;

a second releasing module 802, configured to release the binding relationship among the SNSSI, the S-NSSAI, the NSI, and the SNSI if the termination type of the SNSSI is the reserved SNSSI;

a second removing module 802, configured to, if the termination type of the SNSSI is termination of the SNSSI, remove the binding relationship among the SNSSI, the S-NSSAI, the NSI, and the SNSI, and delete the record corresponding to the SNSSI.

Optionally, the SNSSMF800 further includes:

a second receiving module 801, configured to receive the deletion instruction carrying the S-NSSAI sent by the SNSMF;

and the deleting module is used for deleting the service configuration of the network slicing service corresponding to the S-NSSAI and sending the deleting instruction to the MANO so that the MANO deletes the service configuration.

The embodiment of the invention also provides a MANO. Referring to FIG. 9, FIG. 9 is a block diagram of a MANO provided by an embodiment of the present invention. Because the principle of MANO solving the problem is similar to the method for processing the network slicing service in the embodiment of the present invention, the implementation of MANO and the achieved technical effect can refer to the above description, and the repeated parts are not described again.

As shown in FIG. 9, MANO900 includes:

a third receiving module 901, configured to receive a virtual network element instance termination request sent by an SNSSMF, where the virtual network element termination request carries an identifier of an S-NSSAI, an identifier of an NSI, an identifier of an SNSI, an identifier of an SNSSI, and an identifier of a virtual network element instance that are bound to each other, and the virtual network element instance includes a network service instance NS or a virtualized network element instance VNF;

a third removing module 902, configured to remove the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI, 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 NSI identifier, the SNSI identifier, the NSSI identifier, and the virtual network element instance identifier;

a first sending module 903, configured to send a virtual network element instance termination result to the SNSSMF.

Optionally, the MANO900 further comprises:

a determining module, configured to determine a termination type of the virtual network element instance;

a third removing module 902, configured to remove the binding relationship among 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 a reserved virtual network element instance;

a third removing module 902, configured to remove, when the termination type of the virtual network element instance is a termination virtual network element instance, the binding relationship among 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.

Optionally, the MANO900 further comprises:

a third receiving module 901, configured to receive the deletion instruction carrying the S-NSSAI sent by the SNSSMF;

and the deleting module is used for deleting the service configuration of the network slicing service corresponding to the S-NSSAI.

The embodiment of the invention also provides the NSMF. Referring to fig. 10, fig. 10 is a structural diagram of an NSMF according to an embodiment of the present invention. Since the principle of the NSMF to solve the problem is similar to the method for processing the network slice service in the embodiment of the present invention, reference may be made to the above description for implementing the NSMF and achieving the technical effect, and repeated parts are not described in detail.

As shown in fig. 10, the NSMF1000 includes:

a fourth receiving module 1001, configured to receive a service shutdown request sent by the CSMF of communications service management function and indicating S-NSSAI;

a fourth removing module 1002, configured to remove a binding relationship between the S-NSSAI and the NSI when the network slice service corresponding to the S-NSSAI is a last service associated with the network slice instance NSI bound by the S-NSSAI;

a second sending module 1003, configured 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 1004 is further configured to receive a target termination result sent by SNSMF, where, when SNSSMF receives a virtual network element instance termination result sent by MANO, the target termination result includes a virtual network element instance termination result, a shared network slice subnet termination result, and a shared network slice termination result;

and the second sending module is used for sending the target termination result to the CSMF.

Optionally, the NSMF1000 further includes:

a determining module for determining a termination type of the NSI;

a fourth releasing module 1002, configured to release the binding relationship between the S-NSSAI and the NSI if the termination type of the NSI is a reserved NSI;

a fourth removing module 1002, configured to, if the termination type of the NSI is termination NSI, remove the binding relationship between the S-NSSAI and the NSI, and delete the record corresponding to the NSI.

Optionally, the NSMF1000 further includes:

a deleting module, configured to delete the service configuration of the network slice service corresponding to the S-NSSAI;

a sending module, configured 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.

Optionally, as shown in fig. 7, an embodiment of the present invention further provides a network device 1100, which includes a processor 1101, a memory 1102, and a program or an instruction stored in the memory 1102 and executable on the processor 1101, where the program or the instruction is executed by the processor 1101 to implement each process of the foregoing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

An embodiment of the present invention further provides a computer-readable storage medium, where a program or an instruction is stored on the computer-readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of any one of the method embodiments in fig. 2 to fig. 6, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A processing method of network slice service is applied to a network slice management function SNSMF of a shared network, and is characterized in that the method comprises the following steps:

2. The method of claim 1, wherein the step of unbinding the binding relationship between the SNSI, the S-NSSAI, and the NSI further comprises, after the step of unbinding the binding relationship between the SNSI, the S-NSSAI, and the NSI:

3. The method of claim 1, wherein the step of unbinding the binding relationship between the SNSI, the S-NSSAI, and the NSI comprises:

determining a termination type of the SNSI;

4. The method according to any of claims 1-3, wherein the step of receiving a network slice termination request sent by a network slice management function NSMF of the non-shared network is preceded by the step of:

5. A processing method of a network slice service is applied to SNSSMF, and is characterized by comprising the following steps:

receiving a network slice subnet termination request sent by SNSMF, wherein the network slice subnet termination request carries an S-NSSAI identifier, an NSI identifier, an SNSI identifier and an SNSSI identifier which are bound with each other;

6. The method of claim 5, wherein the step of unbinding the binding relationship among the SNSSI, the S-NSSAI, the NSI, and the SNSI is further followed by:

and sending a virtual network element instance termination request to a virtualized resource arrangement management function (MANO) so that the MANO releases the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI.

7. The method of claim 5, wherein said step of unbinding said binding relationship among said SNSSI, said S-NSSAI, said NSI and said SNSI comprises:

determining a termination type of the SNSSI;

removing the binding relation among the SNSSI, the S-NSSAI, the NSI and the SNSI under the condition that the termination type of the SNSSI is reserved;

8. The method according to any of claims 5-7, wherein the step of receiving a network slice subnet termination request sent by the SNSMF is preceded by the step of:

9. A processing method of network slicing service is applied to MANO, and is characterized in that the method comprises the following steps:

when determining 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 identification of the NSI, the identification of the SNSI, the identification of the NSSI and the identification of the virtual network element instance, removing the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI;

10. The method of claim 9, wherein the step of unbinding the binding relationship among 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;

removing the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI and the SNSSI under the condition that the termination type of the virtual network element instance is a reserved virtual network element instance;

11. The method according to claim 9 or 10, wherein the step of receiving the virtual network element instance termination request sent by the SNSSMF is preceded by the step of:

12. A processing method of network slice service is applied to NSMF, and is characterized in that the method comprises the following steps:

sending the target termination result to the CSMF.

13. The method of claim 12, wherein said step of unbinding the binding relationship between the S-NSSAI and the NSI comprises:

determining a termination type of the NSI;

14. The method according to claim 12 or 13, wherein before the step of releasing 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 S-NSSAI bound network slice instance NSI, the method further comprises:

deleting the service configuration of the network slice service corresponding to the S-NSSAI;

and sending a deleting 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.

15. An SNSMF, comprising:

16. An SNSSMF, comprising:

a second receiving module, configured to receive a network slice subnet termination request sent by an SNSMF, where the network slice subnet termination request carries an identifier of an S-NSSAI, an identifier of an NSI, an identifier of an SNSI, and an identifier of an SNSSMF, which are bound to each other;

17. A MAMO, comprising:

a third releasing module, configured to release the binding relationship among the virtual network element instance, the S-NSSAI, the NSI, the SNSI, 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 NSI identifier, the SNSI identifier, the NSSI identifier, and the virtual network element instance identifier;

18. An NSMF, comprising:

19. A network device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method for processing a network slicing service according to any one of claims 1 to 4, or implementing the steps of the method for processing a network slicing service according to any one of claims 5 to 8, or implementing the steps of the method for processing a network slicing service according to any one of claims 9 to 11, or implementing the steps of the method for processing a network slicing service according to any one of claims 12 to 14.

20. A computer-readable storage medium, characterized in that a program or instructions are stored thereon, which, when being executed by a processor, carry out the steps of the method for processing of a network slicing service according to any one of claims 1 to 4, or carry out the steps of the method for processing of a network slicing service according to any one of claims 5 to 8, or carry out the steps of the method for processing of a network slicing service according to any one of claims 9 to 11, or carry out the steps of the method for processing of a network slicing service according to any one of claims 12 to 14.