CN112996013B

CN112996013B - Slice management method, device and system

Info

Publication number: CN112996013B
Application number: CN201911292611.7A
Authority: CN
Inventors: 毛斌宏; 阳志明; 田海波; 周平利; 李凌; 张英彬; 邱诗鹏; 石彦彬; 喻琦; 云龙
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2019-12-16
Filing date: 2019-12-16
Publication date: 2022-06-07
Anticipated expiration: 2039-12-16
Also published as: CN112996013A

Abstract

The disclosure relates to a slice management method, device and system, and relates to the technical field of communication. The method of the present disclosure comprises: receiving slice deactivation information sent by a service system, wherein the slice deactivation information comprises: selecting auxiliary information S-NSSAI for a single network slice; determining a network function related to slice access control according to the S-NSSAI; network functions related to slice access control include: at least one of a policy control function PCF, an access and mobility management function AMF; and changing the state flag bit of the S-NSSAI configured by the network function into a deactivation state through an interface between the S-NSSAI and the network function.

Description

Slice management method, device and system

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for managing slices.

Background

In the 5G technology, a network is divided into a plurality of network slices, and the network slices can not interfere with each other to provide different application services for users.

The user can subscribe the leased network slice, and after the network slice is activated, the user can access the network slice to realize corresponding services. When the user has arrears or the contract expires, the whole network slice needs to be deactivated.

Disclosure of Invention

The inventor finds that: in the prior art, when a whole Network Slice needs to be deactivated, only Slice identifiers S-NSSAI (Single Network Slice Selection Assistance Information) configured on all NFs (Network functions) corresponding to the Network Slice can be deleted, and a Slice management system needs to maintain a relationship between S-NSSAI and NSFs (Network Slice Instance); after a slice tenant pays a fee or renews a contract, the network slice needs to be reactivated and the S-NSSAI on all the NF needs to be reconfigured, and the slice-level activating and deactivating mode relates to the consistency maintenance of the configuration and the instance relation of a plurality of NF, and is easy to make mistakes and low in efficiency.

One technical problem to be solved by the present disclosure is: the efficiency and accuracy of slice deactivation are improved.

According to some embodiments of the present disclosure, there is provided a slice management method, including: receiving slice deactivation information sent by a service system, wherein the slice deactivation information comprises: selecting auxiliary information S-NSSAI for a single network slice; determining a network function related to slice access control according to the S-NSSAI; network functions related to slice access control include: at least one of a policy control function PCF, an access and mobility management function AMF; and changing the state flag bit of the S-NSSAI configured by the network function into a deactivation state through an interface between the S-NSSAI and the network function.

In some embodiments, determining a network function related to slice access control from S-NSSAI comprises: searching a corresponding network slice instance NSI according to the S-NSSAI; and determining the network function related to the slice access control according to the network function corresponding to the NSI.

In some embodiments, further comprising: receiving slice reactivation information sent by a service system, wherein the slice reactivation information comprises: S-NSSAI; determining a network function related to slice access control according to the S-NSSAI; and changing the state flag bit of the S-NSSAI configured by the network function into the activated state through the interface with the network function.

In some embodiments, further comprising: receiving a slice ordering request sent by a service system, wherein the slice ordering request comprises: S-NSSAI; creating an NSI or selecting an NSI from already created NSIs; determining all corresponding network functions according to the NSI; and configuring S-NSSAI in all network functions through interfaces between the S-NSSAI and the network functions, and configuring the state flag bit of the S-NSSAI into an activated state.

In some embodiments, further comprising: receiving slice termination information sent by a service system, wherein the slice termination comprises the following steps: S-NSSAI; determining all corresponding network functions according to the S-NSSAI; the S-NSSAI configured for all network functions is removed through an interface with each network function.

In some embodiments, where the network function related to slice access control comprises a PCF, the method further comprises: PCF receives a registration request sent by a terminal; the registration request carries an identifier of the terminal; PCF determines the network slice selection strategy NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in PCF; the PCF sends the NSSP to the terminal.

In some embodiments, the PCF determining, according to the identity of the terminal and the status flag bit of each S-NSSAI configured in the PCF, the NSSP of the terminal comprises: PCF determines available S-NSSAI of the terminal according to the identification of the terminal; PCF inquires the status flag bit of the available S-NSSAI of the terminal, and deletes the corresponding S-NSSAI from NSSP under the condition that the status flag bit indicates the deactivation status.

In some embodiments, where the network function related to slice access control comprises an AMF, the method further comprises: the AMF receives a Protocol Data Unit (PDU) session creation request message sent by a terminal; the PDU session creation request message includes: S-NSSAI; AMF inquires the status flag bit of S-NSSAI; and under the condition that the status flag bit indicates the deactivation status, the AMF sends the information of the session establishment failure to the terminal.

According to other embodiments of the present disclosure, there is provided a slice management apparatus including: a receiving module, configured to receive slice deactivation information sent by a service system, where the slice deactivation information includes: selecting auxiliary information S-NSSAI for a single network slice; a network function determining module for determining a network function related to slice access control according to the S-NSSAI; network functions related to slice access control include: at least one of a policy control function PCF, an access and mobility management function AMF; and the state changing module is used for changing the state flag bit of the S-NSSAI configured by the network function into a deactivation state through an interface between the state changing module and the network function.

In some embodiments, the network function determination module is configured to find a corresponding network slice instance NSI according to the S-NSSAI; and determining the network function related to the slice access control according to the network function corresponding to the NSI.

In some embodiments, the receiving module is further configured to receive slice reactivation information sent by a service system, where the slice reactivation information includes: S-NSSAI; the network function determining module is also used for determining the network function related to slice access control according to the S-NSSAI; the state changing module is also used for changing the state flag bit of the S-NSSAI configured by the network function into the activated state through the interface with the network function.

In some embodiments, further comprising: a slice instance determination module; the receiving module is further configured to receive a slice ordering request sent by the service system, where the slice ordering request includes: S-NSSAI; the slice example determining module is used for creating NSI or selecting NSI from already created NSI; the network function determining module is also used for determining all corresponding network functions according to the NSI; the state changing module is also used for configuring S-NSSAI in all network functions through interfaces between the state changing module and each network function, and configuring the state flag bit of the S-NSSAI into an activated state.

In some embodiments, the receiving module is further configured to receive slice termination information sent by the service system, where the slice termination includes: S-NSSAI; the network function determining module is also used for determining all corresponding network functions according to the S-NSSAI; the state changing module is also used for deleting the S-NSSAI configured by all the network functions through the interfaces between the state changing module and the network functions.

According to still other embodiments of the present disclosure, there is provided a system for managing slices, including: a management device of the slice of any of the foregoing embodiments; and a network function related to slice access control for receiving configuration of the management apparatus of the slice through an interface with the management apparatus of the slice, and changing the status flag bit of the S-NSSAI to a deactivated state; network functions related to slice access control include: a policy control function PCF, an access and mobility management function AMF.

In some embodiments, in the case that the network function related to slice access control includes a PCF, the PCF is configured to receive a registration request sent by the terminal; the registration request carries an identifier of the terminal; determining a network slice selection strategy NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in the PCF; the NSSP is sent to the terminal.

In some embodiments, the PCF is configured to determine an S-NSSAI available to the terminal based on the identity of the terminal; and inquiring the state flag bit of the available S-NSSAI of the terminal, and deleting the corresponding S-NSSAI from the NSSP under the condition that the state flag bit represents the deactivation state.

In some embodiments, in the case that the network function related to slice access control includes an AMF, the AMF is configured to receive a protocol data unit, PDU, session creation request message transmitted by the terminal; the PDU session creation request message includes: S-NSSAI; inquiring the state flag bit of the S-NSSAI; and under the condition that the status flag bit indicates a deactivation status, sending information of session establishment failure to the terminal.

According to still further embodiments of the present disclosure, there is provided a system for managing slices, including: a processor; and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform a method of managing slices as in any of the preceding embodiments.

According to further embodiments of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the steps of the method for managing slices of any of the preceding embodiments.

In the disclosure, a slice identifier S-NSSAI is obtained according to slice deactivation information sent by a service system, at least one of PCF and AMF is determined according to the S-NSSAI, and the state flag bit of the S-NSSAI in the network function related to slice access control is changed into a deactivation state. The method disclosed by the invention only changes the state flag bit of the S-NSSAI aiming at the network function related to slice access control, and in the slice deactivation process, most of the S-NSSAI configuration data of the NF is unchanged, so that the number of NF configurations can be reduced, the efficiency is high, and errors are not easy to occur. The slice deactivation can flexibly and rapidly realize the state change of the network slice only by setting the S-NSSAI state flag bit of at least one of the AMF and the PCF, the S-NSSAI on all the NF is not required to be deleted, the S-NSSA on all the NF is not required to be reconfigured when the slice is reactivated, the service use of the whole network slice can be rapidly limited or recovered, and the requirement of the future slice operation maintenance can be met.

The method disclosed by the invention can reduce the service risk brought by frequent configuration of the slicing parameters on one hand, and can also reduce the maintenance workload of the slicing instance relationship and the complexity of slicing management on the other hand. The method can meet the flexible requirement of network deactivation, improve the service slice configuration efficiency, reduce configuration abnormity and meet the requirements of slice operation, maintenance and management for a large number of clients facing third-party industries in the future.

Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 illustrates a flow diagram of a method of managing slices of some embodiments of the present disclosure.

Fig. 2 shows a flow diagram of a method of managing slices of further embodiments of the present disclosure.

Fig. 3 shows a flow diagram of a method of managing slices of further embodiments of the present disclosure.

Fig. 4 shows a flow diagram of a method of managing slices of still further embodiments of the present disclosure.

Fig. 5 shows a flow diagram of a method of managing slices of further embodiments of the present disclosure.

Fig. 6 shows a flow diagram of a method of managing slices of still further embodiments of the present disclosure.

Fig. 7 shows a schematic structural diagram of a management apparatus of slices of some embodiments of the present disclosure.

Fig. 8 illustrates a structural schematic diagram of a system for managing slices of some embodiments of the present disclosure.

Fig. 9 shows a schematic structural diagram of a system for managing slices of further embodiments of the present disclosure.

Fig. 10 shows a schematic structural diagram of a system for managing slices according to further embodiments of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

The present disclosure proposes a slice management method, which is described below with reference to fig. 1.

Fig. 1 is a flow chart of some embodiments of a slice management method of the present disclosure. As shown in fig. 1, the method of this embodiment includes: steps S102 to S106.

In step S102, slice deactivation information sent by the service system is received.

The slice deactivation information includes: S-NSSAI. And when the user arrears or the contract expires, the service system sends slice deactivation information.

In step S104, a network function related to slice access control is determined from the S-NSSAI.

For example, network functions related to slice access control include: at least one of a Policy Control Function (PCF), and an Access and Mobility Management Function (AMF). Network functions related to slice access control may enable denial of user access from the beginning of a user access slice.

In some embodiments, the corresponding NSI is found from the S-NSSAI; and determining the network function related to the slice access control according to the network function corresponding to the NSI. The correspondence of S-NSSAI to NSI is stored in the slice management system, and NSI corresponds to a plurality of NFs, from which network functions related to slice access control are determined.

In step S106, the status flag bit of the S-NSSAI configured by the network function is changed to a deactivated status through the interface with the network function.

And a status flag bit iFlag corresponding to S-NSSAI is added in NF related to slice access control, and the iFlag can identify whether a network slice corresponding to S-NSSAI is in an activated or deactivated state. For example, iFLag ═ 1 indicates activation; iFlag-0 indicates deactivation. The S-NSSAI in the NF relevant to slice access control does not need to be deleted, only the status flag bit is needed, and the S-NSSAI does not need to be reconfigured when the slice is reactivated subsequently. The NF corresponding to the NSI has many other NFs besides AMF and PCF, and the S-NSSAI of these NFs may not be deleted or the status flag bit may be modified.

Further embodiments of the slice management method of the present disclosure are described below in conjunction with fig. 2.

Fig. 2 is a flow chart of other embodiments of a slice management method of the present disclosure. As shown in fig. 2, the method of this embodiment includes: steps S202 to S208.

In step S202, a slice subscription request sent by the service system is received.

The slice ordering request includes: S-NSSAI. After the user transacts the slice subscription, the service system sends a slice subscription request.

In step S204, an NSI is created or selected from the already created NSI.

And storing the created or selected NSI and the S-NSSAI in an associated way.

In step S206, all corresponding network functions are determined according to the NSI.

In step S208, S-NSSAI is configured in all network functions through interfaces with the respective network functions, and a status flag bit of S-NSSAI is configured to be in an activated state.

The status flag may be set only for the NF related to slice access control, and the status flag may not be configured for other NFs.

Still further embodiments of the slice management methods of the present disclosure are described below in conjunction with fig. 3.

Fig. 3 is a flow chart of still further embodiments of the slice management method of the present disclosure. As shown in fig. 3, the method of this embodiment includes: steps S302 to S306.

In step S302, slice reactivation information sent by the service system is received.

The slice reactivation information includes: S-NSSAI. Under the conditions of user payment or contract renewal and the like, the slice can be reactivated, and the business system can send slice reactivation information.

In step S304, a network function related to slice access control is determined from the S-NSSAI.

In step S306, the status flag bit of the S-NSSAI configured by the network function is changed to the activated status through the interface with the network function.

In the case of deactivation, the status flag of the NF relating to slice access control is changed to deactivation, and in the case of reactivation, the status flag of the NF relating to slice access control is changed to activated again. No configuration of other NFs, nor reconfiguration of the S-NSSAI is required.

Still further embodiments of the disclosed slice management method are described below in conjunction with fig. 4.

Fig. 4 is a flow chart of still other embodiments of the slice management method of the present disclosure. As shown in fig. 4, the method of this embodiment includes: steps S402 to S406.

In step S402, slice termination information sent by the service system is received.

Slice termination includes: S-NSSAI. In the event that the user terminates the contract and no longer uses slices, the service system may send slice termination information.

In step S404, all corresponding network functions are determined according to the S-NSSAI.

In step S406, the S-NSSAIs configured by all network functions are deleted through interfaces with the respective network functions.

Since the slice is no longer applied, the S-NSSAI configured on all NFs can be deleted.

The method of the above embodiment only needs to configure or delete the slice parameters of all NFs when the network slice is ordered or terminated, and maintains the relationship between the S-NSSAI and the NSI instance. In the process of slice deactivation and reactivation, the state flag bit of the S-NSSAI is changed only aiming at the network function related to slice access control, and the S-NSSAI configuration data of most NF is not changed, so that the number of NF configurations can be reduced, the efficiency is high, and errors are not easy to occur. The slice deactivation and reactivation only need to set the S-NSSAI status flag bit of at least one of AMF and PCF, the change of the network slice status can be flexibly and rapidly realized, the S-NSSAI on all NF is not needed to be deleted, the S-NSSA on all NF is not needed to be reconfigured when the slice is reactivated, the service use of the whole network slice can be rapidly limited or recovered, and the requirement of future slice operation maintenance can be met.

The method of the embodiment can reduce the business risk brought by frequent configuration of the slicing parameters on one hand, and can also reduce the maintenance workload of the slicing instance relation on the other hand, and reduce the complexity of slicing management. The method can meet the flexible requirement of network deactivation, improve the service slice configuration efficiency, reduce configuration abnormity and meet the requirements of slice operation, maintenance and management for a large number of clients facing third-party industries in the future.

In the case where the network function associated with slice access control comprises a PCF in which the state flag bit of the S-NSSAI is configured to deactivate, the PCF will control access to the network slice by the user. Still further embodiments of the slice management methods of the present disclosure are described below in conjunction with fig. 5.

Fig. 5 is a flow chart of still further embodiments of the slice management method of the present disclosure. As shown in fig. 5, after step S106, the method further includes: steps S502 to S506.

In step S502, the PCF receives the registration request sent by the terminal.

The registration request carries an identifier of the terminal. Before a user's terminal accesses a slice to establish a PDU (Protocol Data Unit) session, initial registration needs to be performed through the terminal.

In step S504, the PCF determines the NSSP (Network Slice Selection Policy) of the terminal according to the identifier of the terminal and the status flag bits of each S-NSSAI configured in the PCF.

In some embodiments, the PCF determines the S-NSSAI available to the terminal based on the identity of the terminal. PCF inquires the status flag bit of the available S-NSSAI of the terminal, and deletes the corresponding S-NSSAI from NSSP under the condition that the status flag bit indicates the deactivation status. If PCF sets status flag bit of S-NSSAI of slice to iFlag ═ 0, PCF filters S-NSSAI of the slice from slice selection strategy NSSP, and terminal can not select the slice to carry out PDU conversation without sending down to terminal, thus achieving the purpose of controlling terminal access to deactivated network slice.

In step S506, the PCF transmits the NSSP to the terminal.

In the case where the network function related to slice access control includes an AMF, which controls user access to a network slice, the status flag bit of the S-NSSAI in the AMF is configured to be deactivated. Still further embodiments of the slice management methods of the present disclosure are described below in conjunction with fig. 6.

Fig. 6 is a flow chart of still further embodiments of the slice management method of the present disclosure. As shown in fig. 6, after step S106, the method further includes: steps S602 to S606.

In step S602, the AMF receives a PDU session creation request message sent by the terminal.

The PDU session creation request message includes: S-NSSAI;

in step S604, AMF queries the status flag bit of S-NSSAI.

In step S606, in the case where the status flag bit indicates the deactivated status, the AMF sends information of session establishment failure to the terminal.

And under the condition that the status flag bit of the S-NSSAI indicates the deactivation status, the AMF refuses the PDU session establishment request of the terminal. When the status flag bit of the S-NSSAI indicates an activated status, the AMF performs a subsequent PDU session establishment procedure, which may refer to the prior art and is not described herein again.

The PCF mainly controls the network slice access of the terminal during initial registration of the terminal, and if the state flag bit of the S-NSSAI available to the terminal during initial registration indicates that the S-NSSAI is activated, the NSSP includes the S-NSSAI, and the terminal stores the S-NSSAI, and then initiates a PDU session request for a slice corresponding to the S-NSSAI. If the subsequent user arrears or the contract expires, the status flag bit of the S-NSSAI is changed to be deactivated, but the terminal still considers that the S-NSSAI is in an active state, and a PDU session request is still initiated, at this time, the AMF is required to control the access of the terminal.

The method of the embodiment sets the status flag bit of the S-NSSAI in the PCF and/or the AMF, and can realize the rejection of the access of the terminal user of the deactivated network slice without changing the S-NSSAI configuration data of most NF under the condition of deactivating the network slice, thereby improving the configuration efficiency and the accuracy.

The present disclosure also provides a slice management apparatus, which is described below with reference to fig. 7.

Fig. 7 is a block diagram of some embodiments of a management device for slices of the present disclosure. As shown in fig. 7, the apparatus 70 of this embodiment includes: a receiving module 710, a network function determining module 720, and a status changing module 730.

The receiving module 710 is configured to receive slice deactivation information sent by a service system, where the slice deactivation information includes: the single network slice selects the side information S-NSSAI.

The network function determining module 720 is configured to determine a network function related to slice access control according to the S-NSSAI; network functions related to slice access control include: a policy control function PCF, an access and mobility management function AMF.

In some embodiments, the network function determination module 720 is configured to find a corresponding network slice instance NSI according to the S-NSSAI; and determining the network function related to the slice access control according to the network function corresponding to the NSI.

The status change module 730 is configured to change the status flag bit of the S-NSSAI configured by the network function to a deactivated status through an interface with the network function.

In some embodiments, the receiving module 710 is further configured to receive slice reactivation information sent by the service system, where the slice reactivation information includes: S-NSSAI; the network function determining module 720 is further configured to determine a network function related to slice access control according to the S-NSSAI; the status change module 730 is further configured to change the status flag bit of the S-NSSAI configured by the network function to the activated status through the interface with the network function.

In some embodiments, further comprising: a slice instance determination module 740; the receiving module 710 is further configured to receive a slice subscription request sent by a service system, where the slice subscription request includes: S-NSSAI; the slice instance determination module 740 is used to create an NSI or select an NSI from already created NSIs; the network function determining module 720 is further configured to determine all corresponding network functions according to the NSI; the state change module 730 is further configured to configure S-NSSAI in all network functions through interfaces with the respective network functions, and configure a state flag bit of S-NSSAI to an activated state.

In some embodiments, the receiving module 710 is further configured to receive slice termination information sent by the service system, where the slice termination includes: S-NSSAI; the network function determining module 720 is further configured to determine all corresponding network functions according to the S-NSSAI; the status change module 730 is further configured to delete S-NSSAI configured by all network functions through interfaces with the respective network functions.

The present disclosure also provides a system for managing slices, which is described below in conjunction with fig. 8.

Fig. 8 is a block diagram of some embodiments of a management system for slices of the present disclosure. As shown in fig. 8, the system 8 of this embodiment includes: a management device 70 of the slices of any of the foregoing embodiments; and a network function related to slice access control, the network function related to slice access control comprising: at least one of PCF82, AMF 84.

The slice access control-related network function is configured to change the status flag bit of the S-NSSAI to a deactivated state by receiving a configuration of the management device of the slice through an interface with the management device of the slice.

In some embodiments, where the network functions related to slice access control include PCF82, PCF82 is configured to receive a registration request sent by a terminal; the registration request carries an identifier of the terminal; determining a network slice selection strategy NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in the PCF 82; the NSSP is sent to the terminal.

In some embodiments, PCF82 is configured to determine an S-NSSAI available to the terminal based on the identity of the terminal; and inquiring the state flag bit of the available S-NSSAI of the terminal, and deleting the corresponding S-NSSAI from the NSSP under the condition that the state flag bit represents the deactivation state.

In some embodiments, in case that the network function related to slice access control includes the AMF84, the AMF84 is configured to receive a protocol data unit PDU session creation request message transmitted by the terminal; the PDU session creation request message includes: S-NSSAI; inquiring the state flag bit of the S-NSSAI; and under the condition that the status flag bit indicates a deactivation status, sending information of session establishment failure to the terminal.

The management system of slices in embodiments of the present disclosure may each be implemented by various computing devices or computer systems, described below in conjunction with fig. 9 and 10.

Fig. 9 is a block diagram of some embodiments of a management system for slices of the present disclosure. As shown in fig. 9, the system 90 of this embodiment includes: a memory 910 and a processor 920 coupled to the memory 910, the processor 920 configured to perform a method of slice management in any of the embodiments of the present disclosure based on instructions stored in the memory 910.

Memory 910 may include, for example, system memory, fixed non-volatile storage media, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), a database, and other programs.

Fig. 10 is a block diagram of still further embodiments of a system for slice management according to the present disclosure. As shown in fig. 10, the system 100 of this embodiment includes: the memory 1010 and the processor 1020 are similar to the memory 910 and the processor 920, respectively. An input output interface 1030, a network interface 1040, a storage interface 1050, and the like may also be included. These

interfaces

1030, 1040, 1050 and the memory 1010 and the processor 1020 may be connected via a bus 1060, for example. The input/output interface 1030 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 1040 provides a connection interface for various networking devices, such as a database server or a cloud storage server. The storage interface 1050 provides a connection interface for external storage devices such as an SD card and a usb disk.

As will be appreciated by one of skill in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A method of slice management, comprising:

receiving slice deactivation information sent by a service system, wherein the slice deactivation information comprises: selecting auxiliary information S-NSSAI for a single network slice;

determining a network function related to slice access control according to the S-NSSAI; the network functions related to slice access control include: at least one of a policy control function PCF, an access and mobility management function AMF;

changing the state flag bit of the S-NSSAI configured by the network function into a deactivated state through an interface with the network function.

2. The slice management method according to claim 1,

the determining a network function related to slice access control according to the S-NSSAI includes:

searching a corresponding network slice instance NSI according to the S-NSSAI;

and determining the network function related to slice access control according to the network function corresponding to the NSI.

3. The slice management method according to claim 1, further comprising:

receiving slice reactivation information sent by a service system, wherein the slice reactivation information comprises: the S-NSSAI;

determining a network function related to slice access control according to the S-NSSAI;

changing the state flag bit of the S-NSSAI configured by the network function to an activated state through an interface with the network function.

4. The slice management method according to claim 2, further comprising:

receiving a slice ordering request sent by a service system, wherein the slice ordering request comprises: the S-NSSAI;

creating the NSI or selecting the NSI from already created NSIs;

determining all corresponding network functions according to the NSI;

and configuring the S-NSSAI in all network functions through interfaces between the S-NSSAI and the network functions, and configuring the status flag bit of the S-NSSAI into an activated state.

5. The slice management method according to claim 1, further comprising:

receiving slice termination information sent by a service system, wherein the slice termination comprises: the S-NSSAI;

determining all corresponding network functions according to the S-NSSAI;

deleting the S-NSSAI configured by all network functions through interfaces with the respective network functions.

6. The slice management method according to claim 1,

in a case where the network function related to slice access control comprises a PCF, the method further comprises:

the PCF receives a registration request sent by a terminal; the registration request carries the identifier of the terminal;

the PCF determines a network slice selection strategy NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in the PCF;

and the PCF sends the NSSP to the terminal.

7. The slice management method according to claim 6,

the PCF determines the NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in the PCF, and the method comprises the following steps:

the PCF determines the available S-NSSAI of the terminal according to the identification of the terminal;

and the PCF inquires the state flag bit of the S-NSSAI available for the terminal, and deletes the corresponding S-NSSAI from the NSSP under the condition that the state flag bit represents the deactivation state.

8. The slice management method according to claim 1,

in a case where the slice access control related network function includes an AMF, the method further includes:

the AMF receives a Protocol Data Unit (PDU) session creation request message sent by a terminal; the PDU session creation request message includes: S-NSSAI;

the AMF inquires the state flag bit of the S-NSSAI;

and under the condition that the status flag bit represents a deactivation status, the AMF sends information of session establishment failure to the terminal.

9. A management apparatus of slices, comprising:

a receiving module, configured to receive slice deactivation information sent by a service system, where the slice deactivation information includes: selecting auxiliary information S-NSSAI for a single network slice;

a network function determining module, configured to determine a network function related to slice access control according to the S-NSSAI; the network functions related to slice access control include: at least one of a policy control function PCF, an access and mobility management function AMF;

and the state changing module is used for changing the state flag bit of the S-NSSAI configured by the network function into a deactivation state through an interface between the state changing module and the network function.

10. A system for managing slices, comprising: a management device of the slices of claim 9; and

a network function related to slice access control, configured to receive configuration of the management device of the slice through an interface with the management device of the slice, and change the status flag bit of the S-NSSAI to a deactivated status;

the network functions related to slice access control include: a policy control function PCF, an access and mobility management function AMF.

11. The system for managing slices of claim 10, wherein,

in the case that the network function related to slice access control comprises a PCF, the PCF is used for receiving a registration request sent by a terminal; the registration request carries the identifier of the terminal; determining a network slice selection strategy NSSP of the terminal according to the identification of the terminal and the status flag bit of each S-NSSAI configured in the PCF; and sending the NSSP to the terminal.

12. The system for managing slices of claim 11, wherein,

the PCF is used for determining the available S-NSSAI of the terminal according to the identification of the terminal; and inquiring the state flag bit of the available S-NSSAI of the terminal, and deleting the corresponding S-NSSAI from the NSSP under the condition that the state flag bit represents the deactivation state.

13. The system for managing slices of claim 10, wherein,

in the case that the network function related to slice access control comprises an AMF, the AMF is used for receiving a Protocol Data Unit (PDU) session creation request message sent by a terminal; the PDU session creation request message includes: S-NSSAI; inquiring the state flag bit of the S-NSSAI; and under the condition that the status flag bit represents the deactivation status, sending information of session establishment failure to the terminal.

14. A system for managing slices, comprising:

a processor; and

a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform the method of managing slices of any of claims 1-8.

15. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the steps of the method of any one of claims 1-8.