Network slice management method, electronic device, and computer program product

Abstract

Provided in embodiments of the present disclosure are a network slice management method, an electronic device, and a computer program product. A slice selection request is received by a first network function from a second network function; and the first network function performs network slice management on the basis of the slice selection request.

Description

Network slicing management methods, electronic devices and computer program products

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to Chinese patent application CN202510351529.6, filed on March 24, 2025, entitled “Network Slice Management Method, Electronic Device and Computer Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a network slicing management method, electronic device, and computer program product. Background Technology

[0004] Currently, in 5G systems, the terminal side needs to support the reception, transmission, and processing of network slice-related information, including Request for Network Slice Selection Assistant Information (NSSAI), allowed NSSAI, rejected NSSAI, partially allowed NSSAI, partially rejected NSSAI, and Network Slice Selection Representation Group (NSSRG). However, network slicing is essentially a logical division of network resources. The terminal only needs to match application traffic to the corresponding single-network slice selection assistant information (S-NSSAI) according to the Usage Rule Selection Procedure (URSP) rules. The network side introduces network slicing-related network functions such as Network Slice Selection Function (NSSF), Network Slice Specific Authentication Function (NSSAAF), and Network Slice Access Control Function (NSACF). The interaction interfaces between different network functions are relatively complex, and the logical division between network functions is not simple and clear enough.

[0005] Therefore, the current 5G system suffers from the problem of high complexity in supporting network slicing. Summary of the Invention

[0006] This disclosure provides a network slicing management method, an electronic device, and a computer program product.

[0007] According to one embodiment of this disclosure, a network slice management method is provided, comprising: a first network function receiving a slice selection request from a second network function; and the first network function performing network slice management based on the slice selection request.

[0008] According to another embodiment of this disclosure, a network slice management method is provided, comprising: a fourth network function determining a first network function; the fourth network function sending a slice selection request to the first network function, so that the first network function performs network slice management based on the slice selection request.

[0009] According to another embodiment of this disclosure, a network slice management method is provided, comprising: a fifth network function determining a first network function; the fifth network function sending a slice selection request to the first network function, so that the first network function performs network slice management based on the slice selection request.

[0010] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0011] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0012] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0013] Figure 1 is a hardware structure block diagram of a mobile terminal for a network slicing management method according to an embodiment of the present disclosure;

[0014] Figure 2 is a flowchart of a network slice management method according to an embodiment of the present disclosure;

[0015] Figure 3 is another flowchart of the network slice management method according to an embodiment of the present disclosure;

[0016] Figure 4 is another flowchart of the network slice management method according to an embodiment of the present disclosure;

[0017] Figure 5 is a structural block diagram of a network device according to an embodiment of the present disclosure;

[0018] Figure 6 is a flowchart illustrating the NRF-based TAI slice support information acquisition process of this disclosure embodiment.

[0019] Figure 7 is a flowchart illustrating the active acquisition of TAI slice information according to an embodiment of this disclosure;

[0020] Figure 8 is a flowchart illustrating the proactive provision of TAI slice support information according to an embodiment of this disclosure.

[0021] Figure 9 is a registration flowchart of the interaction between CMF / AMF and Slice NF according to an embodiment of this disclosure;

[0022] Figure 10 is a flowchart of the PDU session establishment process for CMF / AMF and Slice NF interaction according to an embodiment of this disclosure;

[0023] Figure 11 is a flowchart of the PDU session establishment process for SMF and Slice NF interaction according to an embodiment of this disclosure. Detailed Implementation

[0024] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of the embodiments of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0026] In related technologies, the 5G system architecture consists of the following Network Functions (NFs): User Equipment (UE), Radio Access Network (RAN), Access and Mobility Management Function (AMF), which includes UE mobility management, reachability management, connection management, and registration management functions. The AMF terminates the RAN Control Plane (CP) interface N2 and the Non-Access Stratum (NAS) interface N1, and provides NAS encryption and integrity protection. It also distributes messages to the corresponding NFs through the appropriate interfaces. Unified Data Management (UDM) manages the UE's subscription profiles. Subscription data can be stored in the Unified Data Repository (UDR). Subscription information includes access and mobility subscription data required for UE registration and mobility management, slice selection subscription data required for slice selection, SMF selection, and session management subscription data required for PDU session establishment. Other NFs, such as the AMF and SMF, retrieve subscription data from the UDM. The Network Slice Selection Function (NSSF) supports the following functions: selecting the set of network slice instances to serve the UE; determining the allowed NSSAI and, if necessary, mapping to the Home Public Land Mobile Network (HPLMN) S-NSSAI; determining the configured NSSAI and, if necessary, mapping to the HPLMN S-NSSAI; and possibly determining the AMF set used to serve the UE by querying the Network Repository Function (NRF) or by determining a list of candidate AMFs based on configuration. The Session Management Function (SMF) includes the following functions: session establishment, modification, and release; UE IP address allocation and management; selection and control of User Plane (UP) functions, etc. The User Plane Function (UPF) serves as an anchor point for intra / inter-Radio Access Technology (RAT) mobility and an external PDU session point for Data Network (DN) interconnection.The UPF also routes and forwards packets according to the instructions of the SMF. When the UE is in idle mode, it also buffers downlink (DL) data. The Policy Control Function (PCF) supports a unified policy framework for managing network behavior. The PCF provides access management policies to the AMF, session management policies to the SMF, or UE policies to the UE through the AMF. The PCF can access the UDR to obtain subscription information related to policy decisions.

[0027] The method embodiments provided in this application can be executed in a mobile terminal, computer terminal, or similar computing device. Taking a mobile terminal as an example, FIG1 is a hardware structure block diagram of a mobile terminal for the network slicing management method of this disclosure. As shown in FIG1, the mobile terminal may include one or more (only one is shown in FIG1) processors 102 (processor 102 may include, but is not limited to, processing devices such as microprocessors MCUs or programmable logic devices FPGAs) and a memory 104 for storing data. The mobile terminal may also include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that the structure shown in FIG1 is only illustrative and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG1, or have a different configuration than shown in FIG1.

[0028] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the network slicing management method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0029] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0030] This embodiment provides a network slice management method. Figure 2 is a flowchart of the network slice management method according to this embodiment. As shown in Figure 2, the process includes the following steps:

[0031] In step S202, the first network function receives a slice selection request from the second network function.

[0032] In the embodiments disclosed herein, the first network function, the second network function, the third network function, the fourth network function, and the fifth network function may be the same type of network function in a specific scenario. In such a scenario, they may also be the same network function among the same type of network functions. The descriptions of the first to the fifth functions are only for differentiation in different scenarios and steps, and are not substantially different limitations.

[0033] In one exemplary embodiment, the first network function is a Slice Network Function (SNF), and the second network function includes at least one of the following: Connection Management Function (CMF); Access and Mobility Management Function (AMF); Session Management Function (SMF).

[0034] In one exemplary embodiment, the slice selection request includes at least one of the following: User Equipment ID (UE ID); Registration Area; Requested Single Network Slice Selection Assistance Information (S-NSSAI); Tracking Area; Subscribed Network Slice Information.

[0035] In one exemplary embodiment, the method further includes: a first network function sending a data request to a unified data management network element (UDM) and receiving a data response from the UDM, wherein the data request carries a UE ID and / or a request for S-NSSAI, and the data response carries subscribed network slice information.

[0036] In one exemplary embodiment, the contracted network slice information includes at least one of the following: one or more contracted S-NSSAIs; one or more contracted default S-NSSAIs; one or more contracted S-NSSAIs that require Network Slice Specific Authentication and Authorization (NSSAA); network slice concurrent registration group (NSSRG) information; one or more data network names (DNNs) supported by the contracted S-NSSAI; an indication of whether the requested S-NSSAI is a contracted S-NSSAI; an indication of whether the requested S-NSSAI is a default S-NSSAI; and an indication of whether the requested S-NSSAI requires NSAA.

[0037] Step S204: The first network function performs network slice management based on the slice selection request.

[0038] In an exemplary embodiment, a first network function performs network slice management based on a slice selection request, including at least one of the following: the first network function performs S-NSSAI selection; the first network function determines that the S-NSSAI is an allowed S-NSSAI or a partially allowed S-NSSAI, wherein the partially allowed S-NSSAI includes a corresponding Tracking Area Identity (TAI) list; the first network function performs network slice access control (NSAC) when the S-NSSAI requires network slice access control (NSAC), in roaming scenarios, the Visitor Public Land Mobile Network (VPLMN) Slice NF sends an NSAC request to the HPLMN Slice NF and receives an NSAC response from the HPLMN Slice NF, wherein the NSAC request carries a UE ID and / or a requested S-NSSAI, and the NSAC response carries an NSAC result indication; the first network function performs network slice-specific authentication and authorization when the S-NSSAI requires NSSAA, in roaming scenarios, the VPLMN... The Slice NF sends an NSSAA request to the HLMN Slice NF and receives an NSSAA response from the HLMN Slice NF. The NSSAA request carries the UE ID and / or a request for S-NSSAI, and the NSSAA response carries an NSSAA result indication. If the S-NSSAI requires NSAC and / or NSSAA, and the NSAC and / or NSSAA execution result indication is successful, the first network function allows the corresponding S-NSSAI. The first network function stores the allowed S-NSSAI and / or partially allowed S-NSSAI, as well as the corresponding NSAC and / or NSSAA execution results.

[0039] In one exemplary embodiment, the method further includes: when the second network function is CMF or AMF, the first network function sends a first message to the second network function, the first message including at least one of the following: UE ID; allowed network slice selection assistance information (NSSAI); partially allowed NSSAI; wherein the NSSAI includes multiple S-NSSAIs; the partially allowed S-NSSAI contains a corresponding tracking area identifier (TAI) list.

[0040] In one exemplary embodiment, the method further includes: when the second network function is SMF, the first network function sends a second message to the second network function, the second message indicating whether the requested S-NSSAI is an allowed S-NSSAI or a partially allowed S-NSSAI.

[0041] In one exemplary embodiment, the method further includes: when the second network function is CMF or AMF, the first network function sends a third message to the second network function, the third message being used to request TAI slice support information; the first network function receives a first response message from the second network function.

[0042] In one exemplary embodiment, the third message includes at least one of the following: one or more tracking area identifiers (TAIs); a request indication for TAI slice support information.

[0043] In one exemplary embodiment, the first response message includes at least one of the following: one or more TAIs; a list of S-NSSAIs supported by each TAI.

[0044] In one exemplary embodiment, the method further includes: when the second network function is CMF or AMF, the first network function sends a fourth message to the network storage function NRF, the fourth message being used to query the TAI slice support information of the CMF or AMF; the first network function receives a second response message from the network storage function.

[0045] In one exemplary embodiment, the fourth message includes at least one of the following: identification information of CMF or AMF; one or more tracking area identifiers (TAIs); and a request indication for TAI slice support information.

[0046] In one exemplary embodiment, the second response message includes at least one of the following: one or more TAIs; a list of S-NSSAIs supported by each TAI.

[0047] In one exemplary embodiment, the method further includes: a first network function sending a fifth message to a third network function, the fifth message being used to subscribe to changes in TAI slice support information; and the first network function receiving a sixth message from the third network function, the sixth message being used to indicate changes in TAI slice support information.

[0048] In one exemplary embodiment, the third network function includes at least one of the following: NRF; CMF; AMF.

[0049] In one exemplary embodiment, when the third network function is CMF or AMF, the fifth message includes at least one of the following: one or more tracking area identifiers (TAIs); a subscription indication for changes in TAI slice support information; or, when the third network function is NRF, the fifth message includes at least one of the following: identification information of CMF or AMF; one or more tracking area identifiers (TAIs); a subscription indication for changes in TAI slice support information; or, when the third network function is CMF or AMF, the sixth message includes at least one of the following: one or more tracking area identifiers (TAIs); a list of S-NSSAIs supported by each TAI; or, when the third network function is NRF, the sixth message includes at least one of the following: identification information of CMF or AMF; one or more tracking area identifiers (TAIs); a list of S-NSSAIs supported by each TAI.

[0050] This embodiment provides a network slice management method. Figure 3 is another flowchart of the network slice management method according to this embodiment. As shown in Figure 3, the process includes the following steps:

[0051] Step S302: The fourth network function determines the first network function.

[0052] In one exemplary embodiment, the first network function is a Slice Network Function (SNF), and the fourth network function includes at least one of the following: a Connection Management Function (CMF); and an Access and Mobility Management Function (AMF).

[0053] In one exemplary embodiment, the fourth network function determines the first network function by: the fourth network function sending a seventh message to a network storage function (NRF) to request the determination of the first network function, the seventh message including at least one of the following: a user identifier (UE ID); a tracking area identifier (TAI) of the UE; the fourth network function receiving an eighth message from the NRF, the eighth message being used to indicate the determined first network function, the eighth message including at least one of the following: identification information of the determined first network function; address information of the determined first network function; UE information supported by the determined first network function; and tracking area (TA) supported by the determined first network function.

[0054] In step S304, the fourth network function sends a slice selection request to the first network function so that the first network function can perform network slice management based on the slice selection request.

[0055] In one exemplary embodiment, the slice selection request includes at least one of the following information: User Equipment ID (UE ID); Registration Area; Tracking Area; Subscribed Network Slice Information.

[0056] In one exemplary embodiment, the method further includes: the fourth network function sending a ninth message to the NRF, the message including at least one of the following: a list of TAs supported by the fourth network function; TAI slice support information of the fourth network function; and TAI network slice access layer group (NSAG) support information of the fourth network function.

[0057] In one exemplary embodiment, the method further includes: a fourth network function sending TAI slice support information to a first network function.

[0058] In one exemplary embodiment, the method further includes: a fourth network function receiving a fifth message from a first network function, the fifth message being used to subscribe to changes in TAI slice support information; and the fourth network function sending a sixth message to the first network function, the sixth message being used to indicate changes in TAI slice support information.

[0059] In one exemplary embodiment, the method further includes: a fourth network function selecting auxiliary information NSSAI and / or partially allowed NSSAI based on allowed network slices, and adjusting the registration area; or, the fourth network function adjusting allowed NSSAI and / or partially allowed NSSAI based on the registration area.

[0060] In one exemplary embodiment, the method further includes: a fourth network function sending a tracking area (TA) and a registration area to a session management function (SMF).

[0061] This embodiment provides a network slice management method. Figure 4 is another flowchart of the network slice management method according to this embodiment. As shown in Figure 4, the process includes the following steps:

[0062] Step S402: The fifth network function determines the first network function.

[0063] In one exemplary embodiment, the first network function is Slice Network Function (SNF), and the fifth network function is Session Management Function (SMF).

[0064] In one exemplary embodiment, the fifth network function determines the first network function by: the fifth network function sending a tenth message to the network storage function (NRF), the tenth message being used to request the determination of the first network function, the tenth message including at least one of the following: UE ID; Tracking Area Identifier (TAI); SMF serving area; Registration Area; Requested Single Network Slice Selection Assistance Information (S-NSSAI); Data Network Name (DNN). The fifth network function receives an eleventh message from the NRF, the eleventh message being used to indicate the determined first network function, the eleventh message including at least one of the following: identification information of the determined first network function; address information of the determined first network function; UE information supported by the determined first network function; Tracking Area (TA) supported by the determined first network function.

[0065] In step S404, the fifth network function sends a slice selection request to the first network function so that the first network function can perform network slice management based on the slice selection request.

[0066] In one exemplary embodiment, the slice selection request includes at least one of the following: User Equipment ID; Registration Area; Requested Single Network Slice Selection Assistance Information (S-NSSAI); Tracking Area.

[0067] In one exemplary embodiment, the method further includes: a fifth network function sending a twelfth message to the NRF, the twelfth message being used to request the determination of a User Plane Function (UPF), the twelfth message including at least one of the following: the target network function (NF) type is UPF; service area information of the SMF; a requested S-NSSAI; a requested DNN. The fifth network function receives a thirteenth message from the NRF, the thirteenth message being used to indicate the determined UPF, the thirteenth message including at least one of the following: UPF identification information; UPF address information; UPF supported capability information; UPF service area information.

[0068] In one exemplary embodiment, the method further includes: a fifth network function sending a fourteenth message to the UPF, the fourteenth message including at least one of the following: a requested S-NSSAI; a requested DNN.

[0069] In one exemplary embodiment, the method further includes: the fifth network function sending a fifteenth message to the unified data management network element UDM, the fifteenth message being used to request subscribed network slice information; and the UDM sending a third response message to the fifth network function, wherein the fifteenth message contains the UE ID and the third response message contains the subscribed slice information.

[0070] In this embodiment of the disclosure, the first to fifteenth messages are all information transmitted during different NF interactions. The first to fifteenth messages are only used to distinguish the corresponding different processes and are not intended to make substantial distinctions or limitations. The specific content of each message is determined according to the transmission requirements and the different NFs being transmitted.

[0071] This disclosure provides a network slice management method in which a first network function receives a slice selection request from a second network function; the first network function then performs network slice management based on the slice selection request. This solves the problem of high complexity in network slice support in related technologies, achieving the effect of reducing the overall complexity of network slices and improving the efficiency of network slice selection and management.

[0072] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of the embodiments of this disclosure, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of this disclosure.

[0073] This embodiment also provides a network slice management device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0074] In this embodiment, the network slice management device may include different modules. The naming and functional division of these modules can be chosen in different ways according to the actual situation. No specific restrictions are imposed here, as long as the steps of the network slice management method in the above method embodiment can be implemented.

[0075] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0076] This disclosure also provides a network device. FIG5 is a structural block diagram of the network device according to an embodiment of this disclosure. As shown in FIG5, the network device 500 includes a receiver 501, a transmitter 502 and a processor 503. The network device 500 is used to execute the steps of the above-described model access method embodiment through at least one of the receiver 501, transmitter 502 and processor 503.

[0077] This disclosure also provides a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0078] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0079] This disclosure also provides an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0080] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0081] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0082] In one exemplary embodiment, the computer program product described above includes a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this application.

[0083] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0084] Obviously, those skilled in the art should understand that the modules or steps of the embodiments of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of this disclosure are not limited to any particular combination of hardware and software.

[0085] To enable those skilled in the art to better understand the technical solutions of the embodiments of this disclosure, the following description is provided in conjunction with different embodiments.

[0086] Example 1

[0087] In this embodiment of the disclosure, the Slice Network Function (SNF) obtains TAI slice support information in three ways: NRF query, Slice NF actively requests from CMF / AMF, and CMF / AMF actively provides it to Slice NF.

[0088] The first method: Slice NF is obtained through NRF.

[0089] Figure 6 is a flowchart illustrating the NRF-based TAI slice support information acquisition process of this disclosure. As shown in Figure 6, the process includes the following steps:

[0090] S1. CMF to NRF: The CMF calls NRF services such as Nnrf Network Function Management NF Registration Request (Nnrf_NFManagement_NFRegister_Request) or Nnrf Network Function Management NF Update Request (Nnrf_NFManagement_NFUpdate_Request) to register / update its capabilities / information with the NRF. This information (i.e., the ninth message in the above embodiment) may carry NF Type = "CMF", NF ID = "CMF ID", a list of supported TAs, TAI slice support information (including one or more TAIs and the S-NSSAI(s) supported by each TAI (CMF and / or Access Network (AN))), and TAI NSAG support information (including one or more TAIs and the NSAG information supported by each TAI).

[0091] S2, NRF: NRF stores / updates the information received above.

[0092] S3, NRF to CMF:

[0093] Returns a registration or update success indication: Nnrf_NFManagement_NFRegister / Update_Response, which is the Nnrf Network Function Management NF registration response (Nnrf_NFManagement_NFRegister_Response) or the Nnrf Network Function Management NF update response (Nnrf_NFManagement_NFUpdate_Response).

[0094] S4. Slice NF to NRF: The Slice NF or other NFs invoke NRF services such as Nnrf Network Function Discovery Request (Nnrf_NFDiscovery_Request) or Nnrf Network Function Data Request (Nnrf_NFData_Request) to query the NRF for TAI slice support information for the CMF. The request message (i.e., the fourth message in the above embodiments) may carry NF Type="CMF", NF ID="CMF ID", one or more TAIs, and a TAI slice support information request indication.

[0095] S5, NRF to Slice NF: NRF queries local storage information and returns an Nnrf Network Function Discovery Response (Nnrf_NFDiscovery_Response) or an Nnrf Network Function Data Response (Nnrf_NFData_Response). The message may contain one or more TAIs and the S-NSSAI(s) supported by each TAI (CMF and / or AN).

[0096] S6. Slice NF to NRF: The Slice NF or other NFs call NRF services such as Nnrf Network Function Management Status Subscription (Nnrf_NFManagment_NFStatusSubscribe) or Nnrf Network Function Management Data Subscription (Nnrf_NFData_Subscribe) to subscribe to the NRF for changes in TAI slice support information for the CMF. The request message (i.e., the fifth message in the above embodiments) may contain NF Type="CMF", NF ID="CMF ID", one or more TAIs, and a TAI slice support information change subscription indication.

[0097] S7, NRF->Slice NF: When the TAI slice support information of CMF changes, NRF notifies the subscribed Slice NF or other NFs. NRF sends Nnrf Network Function Management Status Notification (Nnrf_NFManagement_NFStatusNotify) or Nnrf Network Function Management Data Notification (Nnrf_NFData_Notify) to the Slice NF or other NFs. The message (i.e., the sixth message in the above embodiment) may contain NF Type="CMF", NF ID="CMF ID", one or more TAIs, and S-NSSAI(s) supported by each TAI (CMF and / or AN).

[0098] The second method: Slice NF actively requests information.

[0099] Figure 7 is a flowchart illustrating the active acquisition of TAI slice information according to an embodiment of this disclosure. As shown in Figure 7, it includes the following steps:

[0100] S1. Slice NF to CMF: The Slice NF or other NFs invoke CMF services such as Ncmf Event Exposure Request (Ncmf_EventExposure_Request), Ncmf Data Exposure Request (Ncmf_DataExposure_Request), or Ncmf Slice Request (Ncmf_Slice_Request) to obtain TAI slice support information from the CMF. The request message (i.e., the third message in the above embodiments) may carry one or more TAI slice support information request indications.

[0101] S2, CMF to Slice NF: CMF responses such as Ncmf event exposure response (Ncmf_EventExposure_Response), Ncmf data exposure response (Ncmf_DataExposure_Response), or Ncmf slice response (Ncmf_Slice_Response) contain one or more TAIs and S-NSSAI(s) supported by each TAI (CMF and / or AN).

[0102] S3. Slice NF to CMF: The Slice NF or other NFs call CMF services such as Ncmf_EventExposure_Subscribe, Ncmf_DataExposure_Subscribe, or Ncmf_Slice_Subscribe to subscribe to TAI slice support information changes from the CMF. The request message (i.e., the fifth message in the above embodiments) may contain one or more TAIs, TAI slice support information change subscription instructions.

[0103] S4. CMF to Slice NF: When the TAI slice support information of the CMF changes, the CMF notifies the subscribed Slice NF or other NFs. The CMF sends an Ncmf event exposure notification (Ncmf_EventExposure_Notify), Ncmf data exposure notification (Ncmf_DataExposure_Notify), or Ncmf slice notification (Ncmf_Slice_Notify) to the Slice NF or other NFs. The message (i.e., the sixth message in the above embodiment) may contain one or more TAIs and the S-NSSAI(s) supported by each TAI (CMF and / or AN).

[0104] The third method: CMF / AMF proactively provides information.

[0105] Figure 8 is a flowchart illustrating the proactive provision of TAI slice support information according to an embodiment of this disclosure. As shown in Figure 8, it includes the following steps:

[0106] S1, CMF to Slice NF: The CMF invokes Slice NF services such as Nsnf_NSSAIAvailability_Update to provide TAI slice support information to the Slice NF. The message may contain NF Type="CMF", NF ID="CMF ID", one or more TAIs, and the S-NSSAI(s) supported by each TAI (CMF and / or AN).

[0107] S2, Slice NF to CMF: Slice NF stores the information sent by CMF. The Slice NF reply message may contain one or more TAIs and the S-NSSAI(s) authorized for each TAI, one or more TAIs and the S-NSSAI(s) restricted for each TAI.

[0108] S3, CMF to Slice NF: CMF calls Slice NF services such as Nsnf_NSSAIAvailability_Subscribe to subscribe to slice availability information changes from the Slice NF. The request message may contain one or more TAIs, one or more S-NSSAIs, and a slice availability information change subscription indication.

[0109] S4. Slice NF to CMF: When the availability information of a slice subscribed to by a CMF changes, the Slice NF notifies the subscribed CMF. The Slice NF sends an Nsnf network slice availability notification (Nsnf_NSSAIAvailability_Notify) to the CMF. The message may contain one or more TAIs and S-NSSAI(s) for each TAI that are authorized to support / restrict usage, as well as S-NSSAIs for status changes.

[0110] Example 2

[0111] In this embodiment of the disclosure, the CMF / AMF and Slice NF interact to obtain the registration process of allowed NSSAI and the Protocol Data Unit (PDU) session establishment process.

[0112] Figure 9 is a registration flowchart of the interaction between CMF / AMF and Slice NF according to an embodiment of this disclosure. As shown in Figure 9, it includes the following steps:

[0113] S1, UE to CMF / AMF:

[0114] The UE initiates the registration process by sending a registration request message to the CMF / AMF. The registration request message does not contain the requested NSSAI information.

[0115] S2, CMF to (Registration Management Function, RMF) or AMF:

[0116] CMF sends a registration request message to RMF / AMF, but the registration request message does not contain the requested NSSAI information.

[0117] S3, RMF / AMF to CMF:

[0118] RMF / AMF replies with a registration acceptance message to CMF. The registration acceptance message does not contain the accepted NSSAI information or only partially accepted NSSAI information.

[0119] S4, CMF / AMF: Slice NF selection.

[0120] Slice NF is responsible for network slicing-related functions, such as network slice selection, NSSAA, NSAC, etc.

[0121] CMF / AMF selection: Slice NF

[0122] 1) CMF / AMF may query Slice NF by calling NRF services such as Nnrf_NFDiscovery_Request. The request message (i.e., the seventh message in the above embodiment) may carry UE ID (such as Subscription Permanent Identifier (SUPI)), current TAI, etc. The NRF reply is such as Nnrf_NFDiscovery_Response. The reply message (i.e., the eighth message in the above embodiment) may carry the selected Slice NF ID, Slice NF address information, UE information supported by Slice NF, TA information supported by Slice NF, etc.

[0123] 2) OAM configures Slice NF information to CMF / AMF, and CMF / AMF may select Slice NF through OAM's configuration.

[0124] S5, CMF / AMF to Slice NF:

[0125] S5a, CMF / AMF, and UDN interact to obtain contracted slice information.

[0126] S5b and CMF / AMF call Slice NF services such as Nsnf_NSSelection_Get to select a network slice. The request message may contain UE ID, NF type, NF ID, current TA, NSSAI allowed by another access type, (potential) registered area, subscribed slice information (such as subscribed S-NSSAI(s), subscribed default S-NSSAI(s), subscribed S-NSSAA-required S-NSSAI(s), NSSRG information, etc.). CMF / AMF may call UDM services to obtain the aforementioned parameters from UDM before sending this request message.

[0127] S6, Slice NF to UDM:

[0128] The Slice NF calls the UDM's services, such as the subscription data management get request (Nudm_SDM_Get Request). The Nudm_SDM_Get Request (i.e., the data request sent by the first network function to the UDM in the above embodiment) contains a UE ID (such as SUPI).

[0129] UDM responses, such as the subscription data management get response (Nudm_SDM_Get response), include the data response of the UDM response in the above embodiment. The response message contains information such as the subscribed slice information (e.g., subscribed S-NSSAI(s), subscribed default S-NSSAI(s), subscribed S-NSSAI(s) that require NSSAA, NSSRG information, etc.).

[0130] S7, Slice NF:

[0131] S7a. Based on one or more of the aforementioned parameters, Slice NF determines that allowed NSSAI contains one or more S-NSSAIs and / or partially allowed NSSAI contains one or more S-NSSAIs, and each S-NSSAI corresponds to a TAI list (indicating that the S-NSSAI is allowed only if it is in the TAI list).

[0132] S7b. If S-NSSAI requires NSAC, the Slice NF performs NSAC on that S-NSSAI. In roaming scenarios, the VPLMN Slice NF may call services of the HPLMN Slice NF such as the NSNF Network Slice Access Control (NSAC) User Equipment Count Update Request (Nsnf_NSAC_NumOfUEsUpdate_Request). The request message may contain the UE ID (such as SUPI) and the HPLMN S-NSSAI. The HPLMN Slice NF responds with an NSNF Network Slice Access Control (NSAC) User Equipment Count Update Response (Nsnf_NSAC_NumOfUEsUpdate_Response), and the response message contains the NSAC result, such as a success indication.

[0133] S7c. If the S-NSSAI requires NSSAA, the Slice NF performs NSSAA on the S-NSSAI. In roaming scenarios, the VPLMN Slice NF may call services of the HPLMN Slice NF such as the NSNF Network Slice Selection Authorization (NSSAA) authentication request. The request message may contain the UE ID (such as SUPI) and the HPLMN S-NSSAI. The HPLMN Slice NF responds with an NSNF Network Slice Selection Authorization (NSSAA) authentication response (Nsnf_NSSAA_Authenticate_Response), and the response message contains the NSSAA result, such as a success indication.

[0134] For S-NSSAIs that require NSAC and / or NSSAA, the S-NSSAI can only be included in the allowed NSSAI or partially allowed NSSAI if the NSAC and / or NSSAA results are successful.

[0135] S7d and Slice NF may store allowed NSSAI, partially allowed NSSAI, NSSAA results of S-NSSAI, and UE IDs (such as SUPI) locally.

[0136] S8, Slice NF to CMF / AMF:

[0137] The Slice NF response is similar to the Nsnf network slice selection get response (Nsnf_NSSelection_Get Response) (i.e., the first message in the above embodiment). The message may contain the UE ID (e.g., SUPI), allowed NSSAI, and partially allowed NSSAI.

[0138] S9, CMF / AMF:

[0139] S9a and CMF / AMF may adjust the registration region based on allowed NSSAI and / or partially allowed NSSAI.

[0140] S9b and CMF / AMF may adjust allowed NSSAI and / or partially allowed NSSAI depending on the registration region.

[0141] CMF / AMF stores allowed NSSAI, partially allowed NSSAI, and registered regions in the UE context.

[0142] S10, CMF / AMF to UE:

[0143] The CMF / AMF sends a registration acceptance message to the UE. This message contains the registration area, but does not include allowed NSSAI or partially allowed NSSAI.

[0144] Figure 10 is a flowchart of the PDU session establishment process for CMF / AMF and Slice NF interaction according to an embodiment of this disclosure. As shown in Figure 10, it includes the following steps:

[0145] S1, UE to CMF / AMF:

[0146] The UE initiates a PDU session establishment request. The UE sends a PDU session establishment request to the CMF / AMF, and the request message contains parameters such as PDU session ID, S-NSSAI, and DNN.

[0147] S2, CMF / AMF:

[0148] The CMF / AMF determines whether the requested S-NSSAI is included in the allowed NSSAIs or the partially allowed NSSAIs, and whether the current TA allows the S-NSSAI (for example, if the S-NSSAI is included in the partially allowed NSSAIs, the CMF needs to determine whether the current TA is in the list of allowed TAIs for that S-NSSAI). If the current TA does not allow the partially allowed S-NSSAI, the CMF / AMF can allow the establishment of the PDU session and send an instruction to the SMF to activate the PDU session after it is successfully established (i.e., release the user plane of the PDU session).

[0149] If the requested S-NSSAI is not included in the allowed NSSAI / partially allowed NSSAI, the CMF / AMF replies to the UE PDU with a session establishment denial message containing an indication that the requested S-NSSAI is not allowed.

[0150] CMF / AMF selects the SMF based on S-NSSAI and / or DNN. CMF / AMF can call NRF services such as Nnrf_NFDiscovery to query the SMF.

[0151] S3, CMF / AMF to SMF:

[0152] CMF / AMF sends a PDU session establishment request to SMF, and the request message contains S-NSSAI and DNN.

[0153] S4, SMF: UPF selection.

[0154] SMF selects a UPF based on S-NSSAI. SMF can invoke NRF services such as Nnrf_NFDiscovery_Request to select a UPF. The request message may contain information such as the destination NF type (UPF), SMF service area information, S-NSSAI, and DNN. The NRF response, such as Nnrf_NFDiscovery_Response, contains information about the selected UPF, such as UPF ID, UPF address, supported capabilities, and UPF service area information.

[0155] S5, SMF to UPF:

[0156] SMF establishes an N4 session with UPF. SMF may send S-NSSAI and DNN to UPF, and UPF allocates resources on the corresponding slice for the PDU session based on S-NSSAI and / or DNN.

[0157] S6, SMF to CMF / AMF:

[0158] SMF replies to PDU session establishment accept message to CMF / AMF, which contains S-NSSAI and DNN.

[0159] S7, CMF / AMF to UE:

[0160] The CMF / AMF replies to the UE with a PDU session establishment acceptance message, which includes S-NSSAI and DNN.

[0161] Example 3

[0162] In this embodiment of the disclosure, the SMF and Slice NF interact to obtain the PDU session establishment process indicating whether S-NSSAI allows the process.

[0163] Figure 11 is a flowchart of the PDU session establishment process for SMF and Slice NF interaction according to an embodiment of this disclosure. As shown in Figure 11, it includes the following steps:

[0164] S1, UE to CMF / AMF:

[0165] The UE initiates a PDU session establishment request. The UE sends a PDU session establishment request to the CMF / AMF, and the request message contains parameters such as PDU session ID, requested S-NSSAI, and DNN.

[0166] S2, CMF / AMF:

[0167] The CMF / AMF selects the SMF based on the S-NSSAI requested by the UE. The CMF / AMF may invoke NRF services such as Nnrf_NFDiscovery to select the SMF based on the S-NSSAI and / or DNN.

[0168] S3, CMF / AMF to SMF:

[0169] The CMF / AMF sends a PDU session establishment request to the SMF, and the request message includes the requested S-NSSAI and DNN. The CMF / AMF may also send the current TA and registered region to the SMF.

[0170] S4, SMF: Slice NF selection.

[0171] 1) The SMF may query the Slice NF by calling an NRF service such as Nnrf_NFDiscovery_Request. The request message (i.e., the tenth message in the above embodiment) may carry the UE ID (e.g., SUPI), the current TAI, the SMF service area, the registration area, the requested S-NSSAI, DNN, and other information. The NRF reply, such as Nnrf_NFDiscovery_Response, may carry the selected Slice NF ID, the address information of the Slice NF, the UE information supported by the Slice NF, and the area information supported by the Slice NF.

[0172] 2) OAM configures Slice NF information to SMF, and SMF may select Slice NF through OAM's configuration.

[0173] S5, SMF to Slice NF:

[0174] S5a, SMF and UDM interact (i.e., in the above embodiment, SMF sends the fifteenth message to UDM, the fifteenth message is used to request / query the subscribed network slice information) to obtain the subscribed slice information.

[0175] S5b: The SMF calls the Slice NF service, such as Nsnf_NSSelection_Get, to select a slice or verify whether the slice is allowed. The request message may contain the UE ID (e.g., SUPI), NF type (SMF), NF ID, current TA, registered region, requested S-NSSAI, subscribed network slice information (e.g., subscribed S-NSSAI(s), subscribed default S-NSSAI(s), subscribed S-NSSAI(s) requiring NSAAA, NSSRG information, etc.), and DNN. The SMF may call the UDM service to obtain the aforementioned parameters from the UDM before sending this request message. The S-NSSAI sent by the SMF to the Slice NF is the S-NSSAI requested by the UE.

[0176] S6, Slice NF to UDM:

[0177] Slice NF calls UDM services such as subscription data management get request (Nudm_SDM_Get Request), and the request message contains UE ID (such as SUPI) and the requested S-NSSAI.

[0178] UDM responses, such as the Subscription Data Management Get response (Nudm_SDM_Get response), contain information such as the subscribed network slice (e.g., subscribed S-NSSAI(s), subscribed default S-NSSAI(s), subscribed S-NSSAI(s) requiring NSAAA, NSSRG information, DNNs supported by the subscribed S-NSSAI, etc.). The UDM response message may also include indications of whether the requested S-NSSAI is a subscribed S-NSSAI, whether the requested S-NSSAI is a default S-NSSAI, and whether the requested S-NSSAI requires NSAAA.

[0179] S7, Slice NF:

[0180] Slice NF determines whether the S-NSSAI is allowed, such as whether the S-NSSAI is an allowed S-NSSAI or a partially allowed S-NSSAI (containing the corresponding TAI list, indicating that the S-NSSAI is only allowed if it is in the TAI list).

[0181] S7a. If S-NSSAI requires NSAC, the Slice NF performs NSAC on that S-NSSAI. In roaming scenarios, the VPLMN Slice NF may call services of the HPLMN Slice NF such as the NSNF Network Slice Access Control (NSAC) User Equipment Count Update Request (Nsnf_NSAC_NumOfUEsUpdate_Request). The request message may contain the UE ID (such as SUPI) and the HPLMN S-NSSAI. The HPLMN Slice NF responds with an NSNF Network Slice Access Control (NSAC) User Equipment Count Update Response (Nsnf_NSAC_NumOfUEsUpdate_Response), and the response message contains the NSAC result, such as a success indication.

[0182] S7b. If the S-NSSAI requires NSSAA, the Slice NF performs NSSAA on the S-NSSAI. In roaming scenarios, the VPLMN Slice NF may call services of the HPLMN Slice NF such as the NSNF Network Slice Selection Authorization (NSSAA) Authentication Request (Nsnf_NSSAA_Authenticate_Request). The request message may contain the UE ID (such as SUPI) and the HPLMN S-NSSAI. The HPLMN Slice NF responds with an NSNF Network Slice Selection Authorization (NSSAA) Authentication Response (Nsnf_NSSAA_Authenticate_Response), which includes the NSSAA result, such as a success indication.

[0183] For S-NSSAIs that require NSAC and / or NSSAA, the S-NSSAI can only be allowed if the NSAC and / or NSSAA results are successful.

[0184] S7c and Slice NF may store the UE's allowed NSSAI (containing one or more allowed S-NSSAIs) and partially allowed NSSAI (containing one or more partially allowed S-NSSAIs, and each S-NSSAI corresponds to a TAI list, indicating that the S-NSSAI is allowed only if it is in the TAI list), and the NSSAA result of the S-NSSAI.

[0185] S8, Slice NF to SMF:

[0186] The Slice NF response is similar to the Nsnf network slice selection get response (Nsnf_NSSelection_Get Response) (i.e., the second message in the above embodiment). The message may contain the UE ID (such as SUPI), S-NSSAI permission indication such as the S-NSSAI being allowed or the S-NSSAI being partially allowed (and the corresponding list of allowed TAIs).

[0187] S9, SMF:

[0188] If it is a partially allowed S-NSSAI, the SMF needs to determine whether the current TA is in the corresponding allowed TAI list for that S-NSSAI. If the current TA does not allow the partially allowed S-NSSAI, the SMF can allow the establishment of the PDU session and activate the PDU session after the PDU session is successfully established (i.e., release the user plane of the PDU session).

[0189] SMF selects a UPF based on S-NSSAI. SMF can invoke an NRF service such as Nnrf_NFDiscovery_Request to select a UPF. The request message (i.e., the twelfth message in the above embodiment) may contain information such as the destination NF type (UPF), SMF service area information, S-NSSAI, and DNN. The NRF response, such as Nnrf_NFDiscovery_Response (i.e., the thirteenth message in the above embodiment), contains information about the selected UPF, such as UPF ID, UPF address, UPF supported capabilities, and UPF service area information.

[0190] If the requested S-NSSAI is not allowed, the SMF replies to the UE PDU with a session establishment denial message, which contains an indication that the requested S-NSSAI is not allowed.

[0191] S10, SMF to UPF:

[0192] The SMF establishes an N4 session with the UPF (i.e., the SMF sends the fourteenth message to the UPF in the above embodiment). The SMF may send the S-NSSAI and DNN to the UPF, and the UPF allocates resources on the corresponding slice for the PDU session based on the S-NSSAI and / or DNN.

[0193] S11, SMF to CMF / AMF:

[0194] SMF replies to PDU session establishment accept message to CMF / AMF, which contains S-NSSAI and DNN.

[0195] S12, CMF / AMF to UE:

[0196] The CMF / AMF replies to the UE with a PDU session establishment acceptance message, which includes S-NSSAI and DNN.

[0197] In summary, this disclosure provides a network slice management method that simplifies network slicing. From the terminal side, support for network slices only requires matching application traffic to the corresponding S-NSSAI according to URSP rules. From the network side, Slice NF is introduced as the sole network function for handling all network slice-related functions.

[0198] The network slice management method provided in this disclosure includes the following operations for a Slice NF: querying the NRF for TAI slice support information from the CMF / AMF; subscribing to changes in TAI slice support information from the NRF / CMF / AMF; receiving a notification of changes in TAI slice support information from the NRF / CMF / AMF; requesting TAI slice support information from the CMF / AMF; querying the UDM for subscribed slice information; receiving a slice selection request from the CMF / AMF / SMF, which may include a registered region and S-NSSAI; performing slice selection, determining whether the slice is allowed, NSSAA, and NSAC (including interactions between the VPLMN Slice NF and HPLMN Slice NF); sending a partially allowed NSSAI to the CMF / AMF; and sending an S-NSSAI permission indication to the SMF. For CMF / AMF, the following operations are included: registering supported TAI slice support information, a list of supported TAs, and TAI NSAG support information with the NRF; providing TAI slice support information to the Slice NF; receiving TAI slice support information change subscriptions from the Slice NF; sending TAI slice support information change notifications to the Slice NF; performing Slice NF selection; sending the registered region to the Slice NF; adjusting the registered region based on allowed NSSAI and / or partially allowed NSSAI; adjusting allowed NSSAI and / or partially allowed NSSAI based on the registered region; and sending the current TA and registered region to the SMF. For SMF, the following operations are included: performing UPF selection based on S-NSSAI; sending the S-NSSAI to the UPF; performing Slice NF selection; querying the UDM for subscribed slice information; and sending the S-NSSAI, registered region, and current TA to the Slice NF.

[0199] In this embodiment of the disclosure, the executing entity of the network slice management method is not limited to Slice NF, CMF / AMF, SMF, etc. in the above embodiments, but can also be NRF, UDM, UPF, etc., which will not be elaborated here.

[0200] The above description is merely a preferred embodiment of this disclosure and is not intended to limit the scope of this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the protection scope of this disclosure.

Claims

1. A network slice management method, comprising: The first network function receives a slice selection request from the second network function; The first network function performs network slice management based on the slice selection request.

2. The method according to claim 1, wherein, The first network function is Slice NF, and the second network function includes at least one of the following: Connection Management Function (CMF); Access and Mobility Management Function (AMF); Session Management Function (SMF).

3. The method according to claim 1, wherein, The slice selection request includes at least one of the following: User Equipment Identifier (UE ID); Registration Area; Requested Single Network Slice Selection Assistance Information (S-NSSAI); Tracking Area; Subscribed Network Slice Information.

4. The method according to claim 1, wherein, Also includes: The first network function sends a data request to the unified data management network element (UDM) and receives a data response from the UDM. The data request carries the UE ID and / or the requested S-NSSAI, and the data response carries the subscribed network slice information.

5. The method according to claim 4, wherein, The contracted network slice information includes at least one of the following: One or more signed S-NSSAIs; one or more signed default S-NSSAIs; one or more signed S-NSSAIs requiring Network Slice Specific Authentication Authorization (NSSAA); Network Slice Registration Group (NSSRG) information; one or more Data Network Names (DNNs) supported by the signed S-NSSAI; whether the requested S-NSSAI is a signed S-NSSAI; whether the requested S-NSSAI is a default S-NSSAI; whether the requested S-NSSAI requires an NSAA.

6. The method according to claim 1, wherein, The first network function performs network slice management based on the slice selection request, including at least one of the following: The first network function performs S-NSSAI selection; The first network function determines that S-NSSAI is an allowed S-NSSAI or a partially allowed S-NSSAI, wherein the partially allowed S-NSSAI includes a corresponding Tracking Area Identifier (TAI) list; The first network function performs network slice access control when the S-NSSAI requires network slice access control (NSAC). In roaming scenarios, the visited public land mobile network slice function (VPLMN Slice NF) sends an NSAC request to the home public land mobile network (HPLMN Slice NF) and receives an NSAC response from the HPLMN Slice NF. The NSAC request carries the UE ID and / or the requested S-NSSAI, and the NSAC response carries an NSAC result indication. The first network function performs network slice-specific authentication and authorization when the S-NSSAI requires NSAA. In roaming scenarios, the VPLMN Slice NF sends an NSAA request to the HLMN Slice NF and receives an NSAA response from the HLMN Slice NF. The NSAA request carries the UE ID and / or the requested S-NSSAI, and the NSAA response carries an NSAA result indication. If the S-NSSAI requires NSAC and / or NSSAA, and the execution result of the NSAC and / or NSSAA indicates success, the first network function allows the corresponding S-NSSAI. The first network function stores the allowed S-NSSAI and / or the partially allowed S-NSSAI, as well as the corresponding NSAC and / or NSSAA execution results.

7. The method according to claim 2, wherein, Also includes: When the second network function is the CMF or the AMF, the first network function sends a first message to the second network function, the first message including at least one of the following: UE ID; Allowed Network Slice Selection Assistance Information (NSSAI); Partially Allowed NSSAI; The NSSAI includes multiple S-NSSAIs; the partially allowed S-NSSAIs contain a list of corresponding Tracking Area Identifiers (TAIs).

8. The method according to claim 2, wherein, Also includes: When the second network function is the SMF, the first network function sends a second message to the second network function, the second message indicating whether the requested S-NSSAI is an allowed S-NSSAI or a partially allowed S-NSSAI.

9. The method according to claim 2, wherein, Also includes: When the second network function is the CMF or the AMF, the first network function sends a third message to the second network function, the third message being used to request TAI slice support information; The first network function receives a first response message from the second network function.

10. The method according to claim 9, wherein, The third message includes at least one of the following: One or more tracking area identifiers (TAIs); the TAI slices support information request indications.

11. The method according to claim 9, wherein, The first response message includes at least one of the following: One or more TAIs; a list of S-NSSAIs supported by each TAI.

12. The method according to claim 2, wherein, Also includes: When the second network function is the CMF or the AMF, the first network function sends a fourth message to the network storage function NRF, the fourth message being used to query the TAI slice support information of the CMF or the AMF; The first network function receives a second response message from the network storage function.

13. The method according to claim 12, wherein, The fourth message includes at least one of the following: The identification information of the CMF or the AMF; one or more tracking area identifiers (TAIs); and a request indication for TAI slice support information.

14. The method according to claim 12, wherein, The second response message includes at least one of the following: One or more TAIs; a list of S-NSSAIs supported by each TAI.

15. The method according to claim 1, wherein, Also includes: The first network function sends a fifth message to the third network function, the fifth message being used to subscribe to changes in TAI slice support information; The first network function receives a sixth message from the third network function, the sixth message being used to indicate changes in the TAI slice support information.

16. The method according to claim 15, wherein, The third network function includes at least one of the following: NRF; CMF; AMF.

17. The method according to claim 16, wherein, When the third network function is the CMF or the AMF, the fifth message includes at least one of the following: one or more Tracking Area Identifiers (TAIs); a change subscription indication for the TAI slice support information; Alternatively, if the third network function is the NRF, the fifth message includes at least one of the following: identification information of the CMF or the AMF; one or more Tracking Area Identifiers (TAIs); a change subscription indication for the TAI slice support information; Alternatively, if the third network function is the CMF or the AMF, the sixth message includes at least one of the following: one or more Tracking Area Identifiers (TAIs); a list of S-NSSAIs supported by each TAI; Alternatively, if the third network function is the NRF, the sixth message includes at least one of the following: identification information of the CMF or the AMF; one or more tracking area identifiers (TAIs); and a list of S-NSSAIs supported by each TAI.

18. A network slice management method, comprising: The fourth network function determines the first network function; The fourth network function sends a slice selection request to the first network function, so that the first network function can perform network slice management based on the slice selection request.

19. The method according to claim 18, wherein, The first network function is Slice NF, and the fourth network function includes at least one of the following: Connectivity Management Function (CMF); Access and Mobility Management Function (AMF).

20. The method according to claim 18, wherein, The slice selection request includes at least one of the following: User Equipment Identifier (UE ID); Registration Area; Tracking Area; Subscribed Network Slice Information.

21. The method according to claim 18, wherein, The fourth network function determines the first network function, including: The fourth network function sends a seventh message to the network storage function (NRF), the seventh message being used to request the determination of the first network function, the seventh message including at least one of the following: user identifier (UE ID); UE tracking area identifier (TAI); The fourth network function receives an eighth message from the NRF, the eighth message being used to indicate the determined first network function, the eighth message including at least one of the following: identification information of the determined first network function; address information of the determined first network function; UE information supported by the determined first network function; and tracking area (TA) supported by the determined first network function.

22. The method according to claim 18, wherein, Also includes: The fourth network function sends a ninth message to the NRF, the ninth message including at least one of the following: The fourth network function supports a list of TAs; the fourth network function supports TAI slices; and the fourth network function supports TAI network slice access layer group (NSAG).

23. The method according to claim 18, wherein, Also includes: The fourth network function sends TAI slice support information to the first network function.

24. The method according to claim 18, wherein, Also includes: The fourth network function receives a fifth message from the first network function, the fifth message being used to subscribe to changes in TAI slice support information; The fourth network function sends a sixth message to the first network function, the sixth message being used to indicate changes in the TAI slice support information.

25. The method according to claim 18, wherein, Also includes: The fourth network function selects auxiliary information NSSAI and / or partially allowed NSSAI based on the allowed network slices, and adjusts the registration area; Alternatively, the fourth network function may adjust the allowed NSSAI and / or the partially allowed NSSAI based on the registered region.

26. The method according to claim 18, wherein, Also includes: The fourth network function sends the tracking area (TA) and registration area to the session management function (SMF).

27. A network slice management method, comprising: The fifth network function determines the first network function; The fifth network function sends a slice selection request to the first network function, so that the first network function can perform network slice management based on the slice selection request.

28. The method according to claim 27, wherein, The first network function is Slice Network Function (SNF), and the fifth network function is Session Management Function (SMF).

29. The method according to claim 27, wherein, The slice selection request includes at least one of the following: User Equipment Identifier (UE ID); Registration Area; Requested Single Network Slice Selection Assistance Information (S-NSSAI); Tracking Area.

30. The method according to claim 27, wherein, The fifth network function determines the first network function, including: The fifth network function sends a tenth message to the network storage function (NRF), the tenth message being used to request the determination of the first network function, the tenth message including at least one of the following: user identifier (UE ID); tracking area identifier (TAI); service area of ​​the SMF; registration area; requested single network slice selection assistance information (S-NSSAI); data network name (DNN); The fifth network function receives an eleventh message from the NRF, the eleventh message being used to indicate the determined first network function, the eleventh message including at least one of the following: identification information of the determined first network function; address information of the determined first network function; UE information supported by the determined first network function; and tracking area (TA) supported by the determined first network function.

31. The method according to claim 27, wherein, Also includes: The fifth network function sends a twelfth message to the NRF, the twelfth message being used to request the determination of the User Plane Function (UPF), the twelfth message including at least one of the following: the destination network function (NF) type is UPF; service area information of the SMF; requested S-NSSAI; requested DNN; The fifth network function receives a thirteenth message from the NRF, the thirteenth message being applied to indicate the identified UPF, the thirteenth message including at least one of the following: the UPF's identification information; the UPF's address information; the UPF's supported capabilities information; and the UPF's service area information.

32. The method according to claim 27, wherein, Also includes: The fifth network function sends a fourteenth message to the UPF, the fourteenth message including at least one of the following: Requested S-NSSAI; Requested DNN.

33. The method according to claim 27, wherein, Also includes: The fifth network function sends a fifteenth message to the unified data management network element (UDM), the fifteenth message being used to request subscribed network slice information. The UDM sends a third response message to the fifth network function, wherein the fifteenth message contains the UE ID and the third response message contains subscribed slice information.

34. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 33.

35. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, performs the steps of the method of any one of claims 1 to 33.

36. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1 to 33.

Images