Enhancement for user equipment network slice management

By introducing permitted NSSAI modification, managing denied NSSAI, and improving NSSAI mapping technology in User Equipment (UE), the problems of UE access to unpermitted network slices and insufficient cross-PLMN mapping are solved, enabling fast access and optimized network slice management, and improving user experience.

CN118921648APending Publication Date: 2024-11-08APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411312325.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-10-14
Filing Date
2022-11-01
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the prior art, when accessing network slices, user equipment (UE) cannot quickly obtain access to the desired non-permitted network slices, and the management of rejected network slices and NSSAI mapping across public terrestrial mobile networks (PLMNs) is insufficient, resulting in unpredictable behavior and poor user experience.

Method used

The technology introduces a feature that allows user equipment (UE) to initiate modifications to permitted NSSAI, manages rejected NSSAI, improves NSSAI mapping across different PLMNs, and manages permitted NSSAI for equivalent PLMNs. It also optimizes network slicing access through mobility registration update processes and timer mechanisms.

Benefits of technology

It enables UEs to quickly access desired network slices, optimizes network slice management, improves user experience, and reduces unpredictable behavior.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921648A_ABST
    Figure CN118921648A_ABST
Patent Text Reader

Abstract

The invention relates to enhancements for user equipment network slice management. A user equipment (UE) is configured to transmit a registration request message to a network, the registration request message including a request to register to a set of one or more single network slice selection assistance information (S-NSSAI); receiving a response to the registration request message, the response indicating that a request to register to the group of one or more S-NSSAIs is rejected; and locally storing the set of one or more S-NSSAIs in a list of rejected NSSAIs at the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application date of November 1, 2022, application number 202211354280.7, and titled "Enhancement for User Equipment Network Slice Management".

[0002] Priority claim / incorporation by reference

[0003] This application claims priority to U.S. Provisional Application Serial No. 63 / 263,412, filed on November 2, 2021, entitled “Enhancements for User Equipment Network Slice Management,” the entire contents of which are incorporated herein by reference. Background Art

[0004] A user equipment (UE) may be connected to a network where multiple network slices are deployed. Generally speaking, a network slice refers to an end-to-end logical network that is configured to provide specific services and / or have specific network characteristics. Each network slice may be isolated from each other but run on a shared network infrastructure. Therefore, each network slice may share network resources but facilitate different functions. Summary of the invention

[0005] Some exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: transmitting a registration request message to a network, the registration request message including a request to register to a set of one or more single network slice selection assistance information (S-NSSAI); receiving a response to the registration request message, the response indicating that the request to register to the set of one or more S-NSSAI is rejected; and locally storing the set of one or more S-NSSAI in a rejected NSSAI list at the UE.

[0006] Other exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: registering to a first public land mobile network (PLMN); establishing a packet data unit (PDU) session on a first single network slice selection assistance information (S-NSSAI), the first S-NSSAI corresponding to the PLMN; registering to a second PLMN; receiving an allowed NSSAI corresponding to the second PLMN, the allowed NSSAI including a second S-NSSAI, wherein the first S-NSSAI is mapped to the second S-NSSAI; and updating the S-NSSAI associated with the PDU session from the first S-NSSAI to the second S-NSSAI.

[0007] Other exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: registering to a first public land mobile network (PLMN); establishing a packet data unit (PDU) session on a first single network slice selection assistance information (S-NSSAI), the first S-NSSAI corresponding to a VPLMN; registering to a home PLMN (HPLMN); receiving an allowed NSSAI corresponding to the HPLMN, wherein the allowed NSSAI does not include an S-NSSAI that matches the first S-NSSAI; and releasing the PDU session unless a predetermined condition is met.

[0008] Another exemplary embodiment relates to a method performed by a user equipment (UE). The method includes: registering to a home public land mobile network (HPLMN); receiving allowed network slice selection assistance information (NSSAI) of the HPLMN; receiving a TAI list including tracking area identities (TAIs) belonging to the HPLMN; receiving a configuration update command (CUC) including an updated TAI list including TAIs belonging to an equivalent PLMN (EPLMN); and storing the allowed NSSAI in the allowed NSSAI list for the EPLMN. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0010] Figure 2 Exemplary network architectures are shown according to various exemplary embodiments.

[0011] Figure 3 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0012] Figure 4 An exemplary base station according to various exemplary embodiments is shown.

[0013] Figure 5 A signaling diagram of UE-initiated allowed network slice selection assistance information (NSSAI) modification according to various exemplary embodiments is shown.

[0014] Figure 6 A signaling diagram for UE-initiated allowed NSSAI modification according to various exemplary embodiments is shown.

[0015] Figure 7 A signaling diagram for S-NSSAI Rejection according to various exemplary embodiments is shown. DETAILED DESCRIPTION

[0016] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements have the same reference numerals. The exemplary embodiments introduce various enhancements to network slicing. In one aspect, the exemplary embodiments relate to network slice access. In another aspect, the exemplary embodiments relate to how a user equipment (UE) manages rejected network slice selection assistance information (NSSAI). In another aspect, the exemplary embodiments relate to NSSAI mapping. In another aspect, the exemplary embodiments relate to how a UE manages allowed NSSAI for an equivalent public land mobile network (EPLMN). Each of these exemplary aspects is described in more detail below.

[0017] The exemplary embodiments are described with respect to UE. However, the use of the term "UE" is for illustrative purposes only. The exemplary embodiments can be utilized with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any suitable electronic component.

[0018] The exemplary embodiments are also described with reference to a fifth generation (5G) network that supports network slicing. In general, network slicing refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice can be configured to provide a specific set of capabilities and / or features. Therefore, the physical infrastructure of a 5G network can be sliced ​​into multiple virtual networks, each of which is configured for a different purpose. Throughout the specification, references to network slicing may represent any type of end-to-end logical network that is configured for a specific purpose and implemented on a 5G physical infrastructure.

[0019] Those skilled in the art will appreciate that 5G may support a variety of different use cases, such as enhanced mobile broadband (eMBB), enhanced machine type communication (eMTC), high performance machine type communication (HMTC), industrial Internet of Things (IIoT), massive Internet of Things (MIoT), ultra-reliable low latency communication (URLLC), vehicle-to-everything (V2X), etc. Each type of use case may involve a variety of different types of applications and / or services. A network slice may be characterized by the type of use case, the type of application and / or service, or the entity that provides the application and / or service via a network slice. In addition, an operator may deploy multiple network slices for different vertical applications, and operator-specific applications may use different network slices. However, any examples in this specification that characterize network slices in a particular manner are provided for illustrative purposes only. Throughout the specification, references to network slices may represent any type of end-to-end logical network that is configured for a specific purpose and implemented on a 5G physical infrastructure.

[0020] A network slice may be identified by a single network slice selection assistance information (S-NSSAI). Each S-NSSAI instance may be associated with a public land mobile network (PLMN) and may include a slice service type (SST) and a slice descriptor (SD). SST may identify the expected behavior of the corresponding network slice in terms of services, functions, and features. Those skilled in the art will appreciate that SST may be associated with a standardized SST value. SD may identify any one or more entities associated with a network slice. For example, SD may indicate an owner or entity (e.g., an operator) that manages a network slice and / or an entity (e.g., a third party, an entity that provides applications or services, etc.) that provides applications / services via a network slice. In some embodiments, the same entity may own a network slice and provide services (e.g., operator services). Throughout the specification, S-NSSAI refers to a single network slice, and the terms "NSSAI" or "S-NSSAI" may be used to refer to one or more network slices interchangeably.

[0021] The UE may be configured to perform any of a variety of different tasks. Thus, the UE may be configured to utilize one or more network slices. To provide an example, the UE may utilize a different second network slice for one or more operator services (e.g., voice, multimedia messaging service (MMS), Internet, etc.) and for third-party services. However, the configuration purpose of network slices is beyond the scope of the exemplary embodiments. The exemplary embodiments are not limited to any particular type of network slice.

[0022] Examples described herein may refer to the terms “allowed NSSAI,” “configured NSSAI,” “requested NSSAI,” and “denied NSSAI.” Before discussing example enhancements, a brief description of each of these terms and how they relate to each other is provided below.

[0023] Those skilled in the art will appreciate that the term "allowed NSSAI" refers to the S-NSSAI provided by the network that the UE can use in the serving PLMN for a particular registration area. As will be described in detail below, the allowed NSSAI can be provided by the network to the UE during a registration process (e.g., a mobility registration update process or any other appropriate type of registration process). Due to the relationship between the registered NSSAI and the allowed NSSAI, in some embodiments, the term "registered network slice" can be used interchangeably with the allowed NSSAI to refer to the same concept.

[0024] In order to track the allowed NSSAI, the UE may operate a list of allowed NSSAIs stored locally at the UE, or any other appropriate mechanism may be adopted. The number of network slices that can be regarded as allowed NSSAIs of the UE may be limited to a predetermined maximum number of allowed NSSAIs. For example, the 3GPP specification limits the maximum number of allowed NSSAIs to a length of 8 S-NSSAIs. However, the exemplary embodiment is not limited to an allowed NSSAI with a maximum length of 8 S-NSSAIs, and may be applied to any appropriate maximum number of allowed NSSAIs. In some cases, when the S-NSSAI is stored locally as an allowed NSSAI, the UE may attempt to establish a packet data unit (PDU) session on the S-NSSAI. However, when the S-NSSAI is not regarded as part of the allowed NSSAI, the UE may ignore the upper layer request for the S-NSSAI and the UE may not initiate PDU session establishment on the network slice.

[0025] Those skilled in the art will understand that the term "configured NSSAI" refers to an S-NSSAI that is provided in the UE and is applicable to one or more PLMNs. In order to track the configured NSSAI, the UE may operate a list of configured NSSAIs stored locally at the UE, or any other appropriate mechanism may be adopted. When the network slice is stored locally as a configured NSSAI, the value of the S-NSSAI is known to the UE. When the network slice is not stored locally as a configured NSSAI, the UE may not know the value of the S-NSSAI. The number of configured NSSAIs may be limited to a predetermined maximum number of configured NSSAIs. For example, the 3GPP specification limits the maximum number of configured NSSAIs to a length of 16 S-NSSAIs. However, the exemplary embodiment is not limited to a maximum number of configured NSSAIs of length 16 S-NSSAIs, and may be applied to any appropriate number. In some embodiments, the term "subscribed network slice" may be used interchangeably with the configured NSSAI to refer to the same concept.

[0026] During operation, the number of configured NSSAIs stored locally at the UE may be greater than the number of allowed NSSAIs stored locally at the UE. Therefore, there may be one or more S-NSSAIs that are considered by the UE as configured NSSAIs rather than part of the allowed NSSAIs. For example, S-NSSAI-A may be part of the configured NSSAI list stored locally at the UE rather than part of the allowed NSSAI list stored locally at the UE. In such a configuration, the UE will not initiate PDU session establishment on S-NSSAI-A because S-NSSAI-A is not part of the allowed NSSAI list. Throughout this specification, any reference to "S-NSSAI-A" is provided solely to distinguish one network slice from other network slices and is not intended to limit the exemplary embodiments in any way.

[0027] Those skilled in the art will appreciate that the term "requested NSSAI" refers to the NSSAI provided by the UE to the network during the registration process. The network may then determine whether to allow the UE to register to each requested S-NSSAI. For example, the UE may store the S-NSSAI-A as part of the configured NSSAI. The UE may then transmit a registration request message to the network, indicating that the UE wishes to register to one or more network slices, such as S-NSSAI-A, etc. In response, the network may indicate that the requested S-NSSAI is an allowed NSSAI. The UE may then store the S-NSSAI-A in the allowed NSSAI list.

[0028] Alternatively, in response to the requested NSSAI, the network may indicate that the request for the S-NSSAI-A was rejected. To provide some examples, the rejection may be due to a lack of available resources in the registration area or due to an inability to verify the UE's access to a particular network slice. The UE may then consider the S-NSSAI-A to be a "rejected NSSAI". To track rejected NSSAIs, the UE may operate a list of rejected NSSAIs stored locally at the UE, or any other appropriate mechanism may be employed. In some cases, the UE may be configured to omit or ignore rejected NSSAIs during other operations and / or processes. For example, under certain conditions, the UE may not attempt to register on a network slice that is stored locally as part of the rejected NSSAI.

[0029] The above examples provide a general overview of the relationship between the terms “allowed NSSAI,” “configured NSSAI,” “requested NSSAI,” and “denied NSSAI.” These examples are not intended to limit the scope of these terms or the exemplary embodiments in any way.

[0030] Some of the exemplary embodiments are described in conjunction with a scenario in which the UE wishes to access a network slice that is not part of the allowed NSSAI. To provide an example, consider a scenario in which the UE is deployed within a PLMN and remains stationary for a relatively long duration. At deployment, an application that requires connectivity to S-NSSAI-A may be downloaded to the UE. However, S-NSSAI-A is not part of the allowed NSSAI. Due to the stable behavior of the UE, the UE may not be triggered to initiate a registration process. As a result, the UE may not be able to obtain access to the desired network slice (e.g., S-NSSAI-A) for an unreasonable amount of time.

[0031] In conventional cases, such as in the examples provided above, even though the desired network slice is not part of the allowed NSSAI, the UE may not trigger a change to the allowed NSSAI, and the UE may not be able to obtain access to the desired network slice within an unreasonable period of time. As will be described in detail below, in one aspect, the exemplary embodiments introduce techniques that enable the UE to initiate a modification of the allowed NSSAI. These techniques may allow the UE to quickly obtain access to the desired network slice even when the network slice is not part of the allowed NSSAI.

[0032] In another aspect, exemplary embodiments relate to managing rejected NSSAI stored locally at the UE. Typically, the UE does not register to a network slice stored in a rejected NSSAI list. There are various conditions that may trigger the UE to remove a network slice from the rejected NSSAI list. However, it is recognized that under normal circumstances, there may be scenarios where the UE should be able to access a particular network slice that was previously rejected, but nothing triggers the UE to remove the network slice from the rejected NSSAI list. Therefore, the UE may prevent itself from registering to a network slice that is actually available to the UE and allowing the UE to be used. As will be described in detail below, exemplary embodiments introduce techniques that enable the UE to remove entries from the rejected NSSAI stored locally at the UE.

[0033] On the other hand, exemplary embodiments relate to NSSAI mapping. Different PLMNs may interpret the same S-NSSAI value in different ways. It has been confirmed that during the mobility of the UE from the home PLMN (HPLMN) to the visited PLMN (VPLMN) or vice versa, the UE does not fully consider the mapping of the S-NSSAI. This may lead to inconsistencies between the UE and the network in how to interpret the S-NSSAI value, which may lead to unpredictable behavior and poor user experience by accidentally deleting PDU sessions. Therefore, it may be necessary to map S-NSSAI values ​​across PLMNs to ensure that the S-NSSAI value is fully interpreted. As will be described in detail below, exemplary embodiments introduce techniques configured to improve the way in which the UE manages S-NSSAI mapping across different PLMNs.

[0034] In another aspect, exemplary embodiments relate to a UE managing allowed NSSAI for EPLMN. It is confirmed that when managing allowed NSSAI, the UE does not fully consider tracking area identities (TAIs) belonging to different PLMNs. As will be described in detail below, exemplary embodiments introduce techniques configured to improve the manner in which the UE manages allowed NSSAI for EPLMN. Each of the exemplary enhancements described herein can be used independently of each other, in conjunction with currently implemented network slicing mechanisms, future implementations of network slicing mechanisms, or independently of other network slicing mechanisms. Specific examples of each of these exemplary enhancements are described in detail below.

[0035] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for purposes of illustration, only an example with a single UE 110 is provided.

[0036] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular networks, wireless local area networks (WLAN), etc.), and UE 110 may also communicate with the network via a wired connection. With respect to the exemplary embodiment, UE 110 may establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with 5G NR RAN 120.

[0037] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, nodes, cells, or base stations (e.g., Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0038] Those skilled in the art will appreciate that any relevant process may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider, where the UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, the UE 110 may be associated with a particular base station (e.g., a next generation Node B (gNB) 120A).

[0039] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 may refer to an interconnected set of components that manage the operation and traffic of a cellular network. It may include an evolved packet core (EPC) and / or a fifth generation core (5GC). The cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140. The IMS 150 may generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 may generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0040] Figure 2 An exemplary network architecture 200 is shown in accordance with various exemplary embodiments. The following description will provide a general overview of the various components of the exemplary architecture 200. The description of the architecture 200 will be followed by a more detailed description of specific operations performed by the components with respect to the exemplary embodiments.

[0041] Those skilled in the art will appreciate that the components of the exemplary architecture 200 may be relatively Figure 1 The network arrangement 100 resides in various physical and / or virtual locations. These locations may include: within an access network (e.g., RAN 120), within a core network 130, as well as within a Figure 1 Individual components outside the positions described, etc.

[0042] exist Figure 2In the embodiment of the present invention, various components are shown as being connected via connections labeled Nx (e.g., N1, N2, N11). It will be understood by those skilled in the art that each of these connections (or interfaces) is defined in the 3GPP specifications. The exemplary architecture 200 uses these connections in the manner in which they are defined in the 3GPP specifications. In addition, although these interfaces are referred to as connections throughout the specification, it should be understood that these interfaces do not need to be direct wired connections or wireless connections, for example, these interfaces can communicate via intermediate hardware and / or software components. To provide an example, the UE 110 can exchange signals with the gNB 120A via radio. However, in the architecture 200, the UE 110 is shown as having a connection to the AMF 205. The connection or interface is not a direct communication link between the UE 110 and the AMF 205, but rather a connection facilitated by intermediate hardware and software components. Therefore, throughout the specification, the terms "connection" and "interface" are used interchangeably to describe the Nx interface between various components.

[0043] The architecture 200 includes a UE 110 and a 5G NR RAN 120. The UE 110 and the 5G NR RAN 120 are connected to an access and mobility management function (AMF) 205. The AMF 205 is generally responsible for connection and mobility management in the 5G NR RAN 120. Those skilled in the art will appreciate that the AMF 205 is a control plane function and may perform operations related to registration management and connection management. For example, the AMF 205 may perform operations related to registration management between the UE 110 and the core network 130. The exemplary embodiment is not limited to an AMF performing the above operations. Those skilled in the art will appreciate the various different types of operations that the AMF may perform. In addition, reference to a single AMF 205 is for illustrative purposes only, and an actual network arrangement may include any appropriate number of AMFs.

[0044] AMF 205 is connected to session management function (SMF) 210. SMF 210 can perform operations related to session management, such as but not limited to session establishment, session release, IP address allocation, policy and QoS execution, etc. During operation, UE 110 and SMF 210 can exchange PDU session establishment requests and PDU session establishment responses. The exemplary embodiment is not limited to the SMF performing the above operations. Those skilled in the art will understand the various different types of operations that SMF can perform. In addition, reference to a single SMF 210 is only for illustrative purposes, and the actual network arrangement may include any appropriate number of SMFs.

[0045] Figure 3 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1100 is used to describe the UE 110. The UE 110 may include a processor 305, a memory arrangement 310, a display device 315, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, etc.

[0046] The processor 305 may be configured to execute multiple engines of the UE 110. For example, the engines may include an allowed NSSAI engine 335, a rejected NSSAI engine 340, and an NSSAI mapping engine 345. The allowed NSSAI engine 335 may perform various operations related to managing allowed NSSAI stored locally at the UE 110, including but not limited to initiating modifications to allowed NSSAI and managing allowed NSSAI for EPLMNs. The rejected NSSAI engine 340 may perform various operations related to managing rejected NSSAI stored locally at the UE 110. The NSSAI mapping engine 345 may perform various operations related to tracking NSSAI mappings across different PLMNs.

[0047] The engines 335 to 345 described above are each provided as an application (e.g., program) executed by the processor 305 for illustrative purposes only. The functions associated with the engines 335 to 345 may also be represented as separate combined components of the UE 110, or may be modular components coupled to the UE 110, such as integrated circuits with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as one application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 305 is shared between two or more processors (such as a baseband processor and an application processor). The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0048] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 315 may be a hardware component configured to display data to a user, and the I / O device 320 may be a hardware component that enables a user to input. The display device 315 and the I / O device 320 may be separate components or may be integrated together (such as a touch screen). The transceiver 325 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN (not shown in the figure), traditional RAN (not shown in the figure), WLAN (not shown in the figure), etc. Therefore, the transceiver 325 can operate on a variety of different frequencies or channels (e.g., a continuous frequency group).

[0049] Figure 4 An exemplary base station 400 is shown in accordance with various exemplary embodiments. Base station 400 may represent a gNB 120A or any other access node that a UE 110 may use to establish a connection and manage network operations.

[0050] The base station 400 may include a processor 405, a memory arrangement 410, an input / output (I / O) device 415, a transceiver 420, and other components 425. These other components 425 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports for electrically connecting the base station 400 to other electronic devices, and the like.

[0051] The processor 405 may be configured to execute multiple engines of the base station 400. For example, the engines may include a network slicing engine 430. The network slicing engine 430 may perform various operations related to enabling network slicing, including but not limited to facilitating communication between the UE 110 and various network components (e.g., AMF 205, SMF 210, etc.).

[0052] The above-described engine 430 as an application (e.g., program) executed by the processor 405 is merely exemplary. The functions associated with the engine 430 may also be represented as a separate combined component of the base station 400, or may be a modular component coupled to the base station 400, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuits for receiving signals and processing circuits for processing signals and other information. In addition, in some base stations, the functions described for the processor 305 are split between multiple processors (e.g., baseband processors, application processors, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0053] The memory 410 may be a hardware component configured to store data related to operations performed by the base station 400. The I / O device 415 may be a hardware component or port that enables a user to interact with the base station 400. The transceiver 420 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 420 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies). Thus, the transceiver 420 may include one or more components (e.g., a radio component) to enable data exchange with various networks and UEs.

[0054] During operation, UE 110 may desire to gain access to a network slice that is not part of the allowed NSSAI for any of a number of different reasons. To provide some examples, an application may be installed on UE 110, or a particular feature may be activated by upper layers of UE 110 that requires connectivity to a particular network slice. Under normal circumstances, if the desired network slice is not part of the allowed NSSAI, UE 110 may not be able to gain access to the desired network slice for an unreasonable amount of time.

[0055] In one aspect, the exemplary embodiments introduce techniques to enable a UE to initiate modification of the allowed NSSAI. Signaling diagram 500 illustrates an example of a UE-initiated allowed NSSAI modification where a desired network slice is part of the configured NSSAI but not part of the allowed NSSAI. Signaling diagram 600 illustrates an example of a UE-initiated allowed NSSAI modification where a desired network slice is not part of the configured NSSAI or the allowed NSSAI. These techniques may allow a UE 110 to quickly gain access to a desired network slice even when the network slice is not part of the allowed NSSAI.

[0056] Figure 5 A signaling diagram 500 of a UE-initiated allowed NSSAI modification according to various exemplary embodiments is shown. The signaling diagram 500 includes a UE 110, an AMF 205, and an SMF 210. In some examples, when describing operations performed by the UE 110, reference may be made to an application processor and a baseband processor. However, these examples are not intended to limit the exemplary embodiments in any way. The UE 110 may use any suitable combination of hardware, software, and / or firmware to perform the operations described herein.

[0057] In 505, UE 110 identifies that the desired network slice (e.g., S-NSSAI-A) is part of the configured NSSAI but not part of the allowed NSSAI. To provide an example, consider a scenario in which UE 110 is deployed within a PLMN and has been provided with an allowed NSSAI by the network. S-NSSAI-A is provided to UE 110 and has been stored locally as the configured NSSAI. However, at this point, S-NSSAI-A is not part of the allowed NSSAI. An application mapped to S-NSSAI-A may subsequently be installed on UE 110. However, exemplary embodiments are not limited to such scenarios, and UE 110 may wish to gain access to a desired network slice for any appropriate reason.

[0058] Continuing with the example provided above, in some embodiments, the application processor may determine that a new application has been installed that requires connectivity to the S-NSSAI-A. The application processor may then send a request to the baseband processor to access the desired S-NSSAI-A. The baseband processor may detect that UE 110 is subscribed to the S-NSSAI-A but not registered to the S-NSSAI-A.

[0059] In 510, UE 110 triggers a mobility registration update procedure to register with the desired network slice. As will be described in detail below in conjunction with 515, UE 110 may transmit a registration request message to AMF 205 as part of the mobility registration update procedure, the registration request message including a requested NSSAI including the desired network slice (e.g., S-NSSAI-A).

[0060] The one or more trigger conditions for the mobility registration update procedure in 510 are configured to balance the network slices on which the UE 110 has registered and the functionality and / or user experience of the desired network slices. As described above, an exemplary trigger condition for the mobility registration update procedure may include an upper layer (e.g., application processor) request for an NSSAI that includes one or more S-NSSAIs that are not present in the locally stored allowed NSSAIs but are included as part of the locally stored configured NSSAIs. In other words, the mobility registration update procedure may be triggered in response to detecting that the UE 110 is subscribed to but not registered to one or more S-NSSAIs corresponding to applications running on the UE 110.

[0061] One or more trigger conditions may also include a condition related to currently stored allowed NSSAIs. One exemplary trigger condition may be that the number of stored allowed NSSAIs is less than a predetermined maximum number of allowed NSSAIs. Another exemplary trigger condition may be that the S-NSSAI contained in the allowed NSSAI list does not include an S-NSSAI corresponding to a new application or feature as indicated in the upper layer request for NSSAI. When the currently registered network slice does not match the NSSAI requested by the upper layer, this may indicate that the UE 110 is maintaining a registration with an S-NSSAI that is unlikely to be utilized by the UE 110.

[0062] The one or more triggering conditions may also include conditions related to a 5G mobility management (5GMM) operating mode of the UE 110. Those skilled in the art will appreciate that the UE 110 may be configured in one of a plurality of different 5GMM operating modes. When the UE 110 is in a 5GMM connected mode, the UE 110 may not trigger a mobility registration update procedure to register with a desired network slice. However, when the UE 110 is in a 5GMM idle mode, the UE 110 may trigger a registration procedure to register the UE 110 with a desired network slice.

[0063] In 515, UE 110 transmits a registration request message to AMF 205. The registration request message may include a requested NSSAI (e.g., S-NSSAI-A) containing the desired network slice. In 520, AMF 205 transmits a registration accept message to UE 110. The registration accept message may include an allowed NSSAI containing the desired network slice S-NSSAI-A. At this point, UE 110 is now registered to S-NSSAI-A and a PDU session can be established on the network slice. Therefore, in 525, UE 110 transmits a PDU session establishment request to SMF 210 to establish a PDU session on the network slice S-NSSAI-A.

[0064] Continuing with the above example, in some embodiments, the baseband processor may send an updated list of allowed NSSAIs to the application processor. The application processor may then detect that S-NSSAI-A is available for the corresponding application and send a request to the baseband processor to establish a data call with a remote server on S-NSSAI-A.

[0065] In 530, SMF 210 transmits a registration accept message to UE 110, indicating that a PDU session has been established on network slice S-NSSAI-A. However, the PDU session establishment process mentioned above is provided for illustration purposes only. The exemplary enhancements described in signaling diagram 500 are directed to modifying the allowed NSSAI, and what happens after UE 110 registers to the desired network slice is beyond the scope of the exemplary embodiment.

[0066] Figure 6 A signaling diagram 600 of a UE-initiated allowed NSSAI modification according to various exemplary embodiments is shown. The signaling diagram 600 includes a UE 110, an AMF 205, and an SMF 210. In some examples, when describing operations performed by the UE 110, reference may be made to an application processor and a baseband processor. However, these examples are not intended to limit the exemplary embodiments in any way. The UE 110 may use any suitable combination of hardware, software, and / or firmware to perform the operations described herein.

[0067] In 605, UE 110 identifies that a desired network slice (e.g., S-NSSAI-A) is not part of the configured NSSAI. To provide an example, consider a scenario in which UE 110 is deployed within a PLMN, a configured NSSAI has been prepared, and an allowed NSSAI is provided by the network. However, S-NSSAI-A is not prepared for UE 110. An application mapped to S-NSSAI-A is subsequently installed on UE 110, however, S-NSSAI-A is not part of the NSSAI configured for UE 110. Example embodiments are not limited to such scenarios, and UE 110 may wish to gain access to a desired network slice for any appropriate reason.

[0068] Continuing with the example described above, in some embodiments, the application processor may determine that a new application has been installed that requires connectivity to the S-NSSAI-A. The application processor may then send a request to the baseband processor to access the desired S-NSSAI-A. The baseband processor may then detect that UE 110 is not subscribed to the S-NSSAI-A.

[0069] In 610, AMF 205 transmits a configured NSSAI including a desired network slice (e.g., S-NSSAI-A) to UE 110. AMF 205 may transmit the configured NSSAI to UE 110 in response to an explicit request of UE 110 or in response to other conditions experienced by UE 110 and / or the network. In one example, UE 110 performs an initial registration with the NR network to receive the configured NSSAI. In another example, the UE receives a newly configured NSSAI due to a switch from an LTE radio access technology (RAT) to a 5G NR RAT. In another example, in response to a user subscribing to a desired network slice, the network transmits the newly configured NSSAI in a registration accept message or a configuration update command (CUC). However, exemplary embodiments are not limited to these examples and UE 110 may receive the configured NSSAI in any suitable manner.

[0070] In 615, UE 110 identifies that the desired network slice (e.g., S-NSSAI-A) is part of the configured NSSAI but not part of the allowed NSSAI. In 620, UE 110 triggers a mobility registration update procedure to register to the desired network slice. As will be described in detail below in conjunction with 625, UE 110 may transmit a registration request message to AMF 205 as part of the registration procedure, the registration request message including a requested NSSAI including the desired network slice (e.g., S-NSSAI-A).

[0071] The one or more triggering conditions of the mobility registration update procedure in 620 are configured to balance the functionality and / or user experience of the currently registered network slice and the desired network slice. As described above, an exemplary triggering condition of the mobility registration update procedure may include receiving from the network one of the configured NSSAIs previously requested by the upper layer (e.g., application processor). In other words, the mobility registration update procedure may be triggered in response to detecting that the UE 110 is now subscribed to the network slice previously requested by the upper layer.

[0072] The one or more trigger conditions may also include conditions related to currently stored allowed NSSAIs. An exemplary trigger condition may be that the number of stored allowed NSSAIs is less than a predetermined maximum number of allowed NSSAIs. Another exemplary trigger condition may be that the allowed NSSAI list contains an S-NSSAI that is not included in the upper layer request for NSSAI.

[0073] The one or more trigger conditions may also include conditions related to the 5GMM operating mode of the UE 110. When the UE 110 is in the 5GMM connected mode, the UE 110 may not trigger the mobility registration update procedure to register to the desired network slice. However, when the UE 110 is in the 5GMM idle mode, the UE 110 may trigger the registration procedure to register the UE 110 to the desired network slice.

[0074] In 625, UE 110 transmits a registration request message to AMF 205. The registration request message may include a requested NSSAI (e.g., S-NSSAI-A) containing the desired network slice. In 630, AMF 205 transmits a registration accept message to UE 110. The registration accept message may include an allowed NSSAI containing the desired network slice S-NSSAI-A. At this point, UE 110 is now registered to S-NSSAI-A and a PDU session can be established on that network slice. Therefore, in 635, UE 110 transmits a PDU session establishment request to SMF 210 to establish a PDU session network slice S-NSSAI.

[0075] Continuing with the above example, in some embodiments, the baseband processor may send an updated list of allowed NSSAIs to the application processor. The application processor may then detect that S-NSSAI-A is available for the corresponding application and send a request to the baseband processor to establish a data call with a remote server on S-NSSAI-A.

[0076] In 640, SMF 210 transmits a registration accept message to UE 110, indicating that a PDU session has been established on network slice S-NSSAI-A. However, the PDU session establishment process mentioned above is provided for illustration purposes only. The exemplary enhancements described in signaling diagram 600 are directed to modifying the allowed NSSAI, and what happens after UE 110 registers to the desired network slice is beyond the scope of the exemplary embodiment.

[0077] As described above, one of the triggering conditions for the UE-initiated allowed NSSAI modification may be a 5GMM idle mode. For example, the UE 110 may initiate a mobility registration update procedure in 5GMM idle mode to register to a new NSSAI list based on i) a change in network slice requested by a policy upper layer and / or ii) an updated configured NSSAI list received by the UE 110 as part of a configuration update command (CUC) or a registration accept message.

[0078] In some embodiments, for an initial registration accepted by the network, if the registration accept message includes a network slice indication IE with the network slice subscription change indication set to "Network slice subscription changed", or includes a configured NSSAI IE with a newly configured NSSAI for the current PLMN, the UE 110 may wait until it enters 5GMM idle mode, and then the UE 110 may initiate a mobility registration update procedure to register to the new NSSAI group based on the newly configured NSSAI.

[0079] In some embodiments, for a mobility registration update accepted by the network, if a newly configured NSSAI for the current PLMN is included, the AMF 205 may also include a mapped S-NSSAI of the configured NSSAI for the current PLMN (if available) in the registration accept message, and the UE 110 may wait until it enters 5GMM idle mode, and the UE 110 may initiate a registration process for the mobility registration update to register to the new NSSAI group based on the newly configured NSSAI.

[0080] In some embodiments, the triggering condition of the mobility registration update procedure may also include the state of the 5G system (5GS) mobility management timer. In this example, the timer is referred to as "T3540", which is defined in various 3GPP specifications. The exemplary embodiment introduces a technique for using this timer for the allowed NSSAI modification procedure initiated by the exemplary UE. However, the exemplary embodiment is not limited to the T3540 timer and a new timer may be introduced for this purpose or any other appropriate mechanism may be adopted.

[0081] In one example, if UE 110 receives a configuration update command (CUC) message that does not indicate "registration requested" in the registration request bit of the configuration update indication IE, UE 110 may start T3540. Upon expiration of T3540 (and return to zero or multiple other triggering conditions), UE 110 may initiate a mobility registration update procedure to register with the network slice based on the newly configured NSSAI. For example, in the context of signaling diagram 600, UE 110 may receive a CUC message in 610 and start T3540. In 620, UE 110 may trigger a mobility registration update procedure based at least in part on the expiration of T3540.

[0082] Timer T3540 may also be used to release the N1 non-access stratum (NAS) signaling connection. In some embodiments, the start of T3540 may be triggered if i) there is no CUC message indicating "registration requested" in the registration request bit of the configuration update indication IE, ii) user plane resources for the PDU session are not set up, and / or iii) no emergency PDU session is established.

[0083] After T3540 starts, UE 110 may be triggered to stop the timer and perform specific operations. For example, based on an indication from a lower layer that an access layer connection has been released, UE 110 may stop T3540 and perform a new registration process. In another example, based on an indication from a lower layer that user plane resources have been set for a PDU session, the UE may stop T3540 and may send user data via the user plane. In this scenario, a new registration process may be performed when UE 110 moves to 5GMM idle mode. In another example, based on a request to perform emergency service fallback received from an upper layer when UE 110 is configured with 3GPP access or an emergency PDU session is established, UE 110 may stop T3540 and locally release the N1 NAS signaling connection.

[0084] In signaling diagrams 500 to 600, UE 110 does not have to wait for network or mobility conditions to trigger network slice registration for a desired network slice. Instead, the exemplary embodiments provide fast access to a desired network slice by enabling UE 110 to initiate modification of the allowed NSSAI when UE 110 wishes to access a network slice that is not part of the allowed NSSAI.

[0085] In another aspect, an exemplary embodiment relates to managing a UE 110 with a rejected NSSAI. As described above, the AMF 205 may reject a requested network slice during a registration process. For example, the AMF 205 may transmit a message including a rejection reason code in response to a requested S-NSSAI. The rejection reason code may indicate a reason for the rejection, such as, for example, S-NSSAI is not available in the current PLMN, S-NSSAI is not available in the current registration area, etc.

[0086] UE 110 may operate a rejected NSSAI list stored locally at UE 110. Generally, if the S-NSSAI is stored as part of the rejected NSSAI list, UE 110 may not register with the network slice. For example, if the S-NSSAI is part of the rejected NSSAI list, UE 110 may ignore or omit the S-NSSAI requested by upper layers for subsequent operations.

[0087] The UE 110 may not register on a network slice stored in the rejected NSSAI list until the network slice is removed from the rejected NSSAI list. Under normal circumstances, the UE 110 cannot delete the S-NSSAI from the rejected NSSAI list in a timely manner. This may lead to a scenario where the S-NSSAI-A is rejected by the network during the registration process, but since then conditions have changed and the rejection reason is no longer true. In such a scenario, the UE 110 should be able to access the network slice, but since nothing triggered the UE 110 to remove the S-NSSAI from the rejected NSSAI list, the UE 110 continues to behave as if the network slice is not available. As will be described in detail below, the exemplary embodiments introduce techniques for handling rejected NSSAI that enable the UE 110 to avoid the types of scenarios described above that may occur under normal circumstances.

[0088] Figure 7 A signaling diagram 700 for S-NSSAI rejection according to various exemplary embodiments is shown. The signaling diagram 700 includes a UE 110 and an AMF 205. The signaling diagram 700 will provide a general overview of network slice rejection and is used to provide an exemplary enhanced context for managing rejected NSSAI at the UE 110. In this example, references to PLMN_1 and S-NSSAI-A are not intended to limit the exemplary embodiments in any way. Instead, PLMN_1 is used to distinguish one PLMN from other PLMNs. Similarly, S-NSSAI-A is used to distinguish one S-NSSAI from other S-NSSAIs.

[0089] In 705, UE 110 transmits a registration request message to AMF 205. The registration request message may include a requested NSSAI including at least S-NSSAI-A.

[0090] In 710, the AMF 205 transmits a response to the registration request message (e.g., registration accept, registration reject, etc.) including an indication of the rejected network slice. For example, the response may include a rejection reason code associated with the S-NSSAI-A, indicating why the network did not accept the UE 110's registration request for the S-NSSAI-A. To provide some examples, the rejection reason code may indicate that the S-NSSAI is not available in the current PLMN or the S-NSSAI is not available in the current registration area. In other examples, the rejection reason code may indicate that a network slice quota has been reached. However, these examples are provided for illustrative purposes only, and the basis for the network rejecting the network slice is beyond the scope of the exemplary embodiments.

[0091] One of the exemplary techniques involves a scenario where UE 110 is registered in PLMN_1 and has a rejected NSSAI list for PLMN_1. For example, UE 110 may receive a rejected NSSAI for PLMN_1 in 710 of signaling diagram 700.

[0092] UE 110 also receives a network slice indication IE with the network slice subscription change indication set to “network slice subscription changed” in the Registration Accept message or the CUC message. In response, UE 110 may be triggered to perform a mobility registration on PLMN_1.

[0093] On the network side, a change in the subscription information of UE 110 may be detected. The change may indicate that UE 110 is now allowed to access a previously rejected network slice (e.g., S-NSSAI-A). However, under normal circumstances, UE 110 may not be triggered to delete the rejected NSSAI list for the current PLMN (e.g., PLMN_1). In addition, there may be no direct mechanism by which the network can request UE 110 to delete the rejected NSSAI. Therefore, even if UE 110 should be able to access S-NSSAI-A because the network slice is no longer considered a rejected NSSAI on the network side, UE 110 may still be unable to access the network slice because the network slice has not been removed from the rejected NSSAI list.

[0094] The exemplary embodiment introduces a technique in which when UE 110 receives an indication of a subscription information change from the network, UE 110 deletes a rejected NSSAI (if any). To provide an example, when UE 110 receives a network slice indication IE with a network slice subscription change indication set to "network slice subscription has changed" in a registration accept message or a CUC message, UE 110 may delete the network slice information of each of the PLMNs (excluding the current PLMN) for which UE 110 has stored slice information, and UE 110 may also delete any rejected NSSAI (if any).

[0095] Another exemplary technique relates to a scenario in which UE 110 is registered to PLMN_1 and has a rejected NSSAI list for PLMN_1. For example, UE 110 may receive a rejected NSSAI for PLMN_1 in 710 of signaling diagram 700. UE 110 also performs an inter-RAT (IRAT) transition from N1 mode to S1 mode and remains in a 5G MM registration state. Those skilled in the art will appreciate that N1 mode is a mode in which UE 110 is allowed to access a 5G core network via a 5G access network, while S1 mode is a mode that UE 110 applies to both a 5G system (5GS) and an evolved packet system (EPS). Due to changes in user subscription, one or more network slices stored in the rejected NSSAI list for PLMN_1 are no longer considered as rejected NSSAI by the 5GS network. In response, UE 110 performs an IRAT transition to move to N1 mode and trigger mobility registration.

[0096] On the network side, a change in the subscription information of UE 110 may be detected. The change may indicate that UE 110 is now allowed to access the previously rejected network slice (e.g., S-NSSAI-A). In conventional cases, when IRAT transitions to S1 mode, UE 110 may not delete the rejected NSSAI for PLMN_1, and therefore, when IRAT transitions to N1 mode, UE 110 may not include the rejected NSSAI. Therefore, UE 110 cannot obtain access to the network slice that was previously rejected but is now removed from the rejected NSSAI by the network.

[0097] The exemplary embodiment introduces a technique in which when UE 110 performs an IRAT transition from N1 mode to S1 mode and UE 110 is not registered with the current PLMN through another access, the rejected NSSAI for the current PLMN and the rejected NSSAI for failed or revoked network slice specific authentication and authorization (NSSAA) should be deleted by UE 110. In another technique, when UE 110 performs an IRAT transition from N1 to S1 mode, the rejected NSSAI for the current registration area corresponding to the access type should be deleted by UE 110.

[0098] Another exemplary technique involves a scenario where UE 110 is registered in PLMN_1 and has a rejected NSSAI list for PLMN_1. For example, UE 110 may receive a rejected NSSAI for PLMN_1 in 710 of signaling diagram 700.

[0099] UE 110 also receives a CUC message with the Registration Request bit of the Configuration Update Indication IE set to "Registration Requested" and containing no other parameters. In response, UE 110 may trigger a mobility registration on PLMN_1.

[0100] On the network side, the allowed NSSAI may change. Under normal circumstances, UE 110 may not delete the rejected NSSAI for the current PLMN, and it may be desirable for UE 110 to delete the allowed NSSAI. However, in the above scenario, UE 110 may not use the rejected NSSAI for subsequent registrations, which may result in the user still being unable to access the slice despite the change in the allowed NSSAI on the network side.

[0101] The exemplary embodiment introduces a technique whereby if UE 110 receives a CUC message with the Registration Request bit of the Configuration Update Indication IE set to "Registration Requested" and containing no other parameters, UE 110 may delete the rejected NSSAI.

[0102] Another exemplary technique involves two different scenarios. In one scenario, UE 110 is registered in PLMN_1 and has a rejected NSSAI list for PLMN_1. For example, UE 110 may receive a rejected NSSAI for PLMN_1 in 710 of signaling diagram 700. UE 110 then attempts to perform mobility registration on a different PLMN (e.g., PLMN_2) and receives a registration rejection message with reason code #62 (e.g., no available network slice) and a rejected NSSAI list for PLMN_2. UE 110 remains in a 5GMM registered state.

[0103] In the above exemplary scenario, after an unsuccessful registration in a new PLMN, it may be desirable for UE 110 to delete the rejected NSSAI upon deregistration. However, in conventional cases, UE 110 may not delete the rejected NSSAI and may retain the rejected NSSAI for PLMN_1 and the rejected NSSAI for PLMN_2.

[0104] In the second scenario, UE 110 is already registered in PLMN_1 and receives a rejection cause code #62 with a rejected NSSAI containing all network slices rejected for PLMN_1. When receiving cause code #62 on the current PLMN, UE 110 may not have any other network slices to register and UE 110 may disable N1 mode. In response, UE 110 performs an IRAT transition to S1 mode.

[0105] In the above exemplary scenario, after an unsuccessful registration in the current PLMN due to a 5GMM reason other than cause code #62, it is desirable for UE 110 to delete the rejected NSSAI when canceling the registration. However, in the above scenario, UE 110 does not delete the rejected NSSAI and may retain the rejected NSSAI for PLMN_1.

[0106] The exemplary embodiment introduces a technique for NSSAI storage, wherein when UE 110 enters a 5GMM deregistered state after an unsuccessful registration for a current PLMN due to a 5GMM reason other than cause code #62 (e.g., no network slice available), unless N1 mode is disabled as part of handling cause code #62, UE 110 may delete the rejected NSSAI for the current PLMN and the rejected NSSAI for failed or revoked NSSAA. In another technique, when UE 110 enters a 5GMM deregistered state or a 5GMM registered state after an unsuccessful registration to a new PLMN, UE 110 may delete the rejected NSSAI for the current PLMN and the rejected NSSAI for failed or revoked NSSAA.

[0107] In another aspect, exemplary embodiments relate to NSSAI mapping. NSSAI with similar functionality may have different values ​​across different PLMNs. Each S-NSSAI in the HPLMN is mapped to a corresponding S-NSSAI in the VPLMN, depending on the policy and configuration of the VPLMN operator. It is confirmed that during UE mobility from the HPLMN to the VPLMN or vice versa, the UE 110 may not fully consider the NSSAI mapping. This may lead to inconsistencies between the UE and the network, which may result in unpredictable behavior (e.g., release of PDU sessions, etc.) and a poor user experience.

[0108] To provide an example, consider a scenario where UE 110 is registered in the HPLMN and has an ongoing PDU session with S-NSSAI-A but no corresponding mapped S-NSSAI. UE 110 then roams to a VPLMN, registers on the VPLMN, and receives an allowed NSSAI including S-NSSAI-B and the corresponding mapped NSSAI S-NSSAI-A. Under normal circumstances, UE 110 may not update the local S-NSSAI associated with the PDU session, resulting in an inconsistency between UE 110 and the network.

[0109] To provide another example, consider a scenario where UE 110 is registered in a VPLMN and has an ongoing PDU session with S-NSSAI-B and a corresponding mapped S-NSSAI as S-NSSAI-A. UE 110 then returns to the HPLMN, registers on the HPLMN, and receives an allowed NSSAI with S-NSSAI-A but without a corresponding mapped S-NSSAI. Under normal circumstances, UE 110 may not update the local S-NSSAI associated with the PDU session, resulting in an inconsistency between UE 110 and the network.

[0110] As will be described in detail below, the exemplary embodiments introduce techniques configured to improve the manner in which a UE manages NSSAI mappings across different PLMNs. For an active PDU session in UE 110, if the allowed NSSAI includes a HPLMN S-NSSAI that matches the HPLMN S-NSSAI of the PDU session (e.g., the mapped S-NSSAI, if available), the UE 110 shall locally update the S-NSSAI associated with the PDU session to the corresponding S-NSSAI received in the allowed NSSAI. If the allowed NSSAI does not include a HPLMN S-NSSAI that matches the HPLMN S-NSSAI of the PDU session (e.g., the mapped S-NSSAI, if available), the UE 110 may perform a local release of the PDU session, except for emergency PDU sessions (if any), and PDU sessions (if any) established when the UE 110 is registered for a new user bootstrap service in a standalone non-public network (SNPN).

[0111] In some embodiments, AMF 205 may also determine which PDU session is no longer supported based on the new allowed NSSAI, and it will indicate in the PDU session status IE which PDU session is released locally on the network side or trigger SMF 210 to initiate release via 5G session management signaling. In some exemplary embodiments, if the network slice (e.g., S-NSSAI) is no longer available under the same AMF, the AMF indicates to the SMF which PDU session ID corresponding to the relevant S-NSSAI will be released and the SMF releases the PDU session. In other exemplary embodiments, if the network slice (e.g., S-NSSAI) is no longer available when the AMF changes (e.g., due to a registration area change), the new AMF indicates to the old AMF that the PDU session corresponding to the relevant S-NSSAI will be released. The old AMF notifies the corresponding SMF to release the indicated PDU session. Then, the new AMF modifies the PDU session status accordingly. After receiving the session status in the registration accept message, the PDU session context is released locally in the UE.

[0112] In another aspect, an exemplary embodiment relates to a UE managing allowed NSSAIs for an equivalent PLMN (EPLMN). It is determined that when managing allowed NSSAIs, the UE does not adequately account for TAIs belonging to different PLMNs. To provide an example, consider a scenario in which a UE 110 is registered in an HPLMN, has allowed NSSAIs, and a TAI list containing TAIs belonging to the HPLMN. The UE 110 subsequently receives a CUC message containing an updated TAI list containing TAIs belonging to a different PLMN that is an EPLMN, and there are now new allowed NSSAIs. Under normal circumstances, the UE 110 may not update the allowed NSSAI lists associated with those EPLMNs.

[0113] The exemplary embodiments introduce techniques configured to improve the manner in which a UE manages allowed NSSAIs for EPLMNs. If the UE 110 receives a new TAI list in a CUC message, the UE 110 may treat the new TAI list as valid and the old TAI list as invalid. Otherwise, the UE 110 may treat the old TAI list as a value. If the new TAI list includes TAIs belonging to different PLMNs that are EPLMNs, and if the UE 110 includes an allowed locally stored NSSAI, the UE 110 may store the allowed NSSAI in each of the allowed NSSAIs associated with each of the EPLMNs. Therefore, if the UE 110 including the stored allowed NSSAI receives a CUC message having a registration area including an updated TAI list with different PLMNs, the UE 110 may store the allowed NSSAI in each of the allowed NSSAIs associated with each of the PLMNs.

[0114] Example

[0115] In a first embodiment, a method includes: receiving a registration request message including requested network slice selection assistance information (NSSAI) from a user equipment (UE), the NSSAI including single network slice selection assistance information (S-NSSAI); determining whether the UE is allowed to register with the S-NSSAI; and based on determining whether the UE is allowed to register with the S-NSSAI, transmitting a response to the registration request message to the UE.

[0116] In a second embodiment, the method according to the first embodiment further includes registering the UE with the S-NSSAI when the UE is allowed to register with the S-NSSAI, wherein the response includes a registration accept message indicating that the S-NSSAI is an allowed S-NSSAI.

[0117] In a third embodiment, the method according to the first embodiment, wherein the response includes a registration reject message indicating a cause code for rejection when the UE is not allowed to register with the S-NSSAI.

[0118] In a fourth embodiment, a network function is configured to perform any one of the methods described in the first to third embodiments.

[0119] In a fifth embodiment, one or more processors are configured to perform any one of the methods described in the first to third embodiments.

[0120] In a sixth embodiment, a method includes: storing allowed network slice selection assistance information (NSSAI) for a user equipment (UE), the NSSAI including one or more single network slice selection assistance information (S-NSSAI); determining that at least one of the S-NSSAI is no longer an allowed NSSAI; and determining that there is a valid protocol data unit (PDU) session valid for at least one S-NSSAI.

[0121] In a seventh embodiment, the method according to the sixth embodiment further comprises indicating to a session management function (SMF) of the network that the PDU session is to be released.

[0122] In an eighth embodiment, the method according to the sixth embodiment further includes indicating to the UE that the PDU session is to be released.

[0123] In a ninth embodiment, the method of the sixth embodiment, wherein the indication comprises a registration accept message including a PDU session state information element.

[0124] In a tenth embodiment, according to the method described in the sixth embodiment, wherein the network function is a first access and mobility management function (AMF) to which the UE is currently registered, the method further includes instructing a second AMF to which the UE was previously registered to release the PDU session.

[0125] In an eleventh embodiment, a network function is configured to perform any one of the methods described in accordance with the sixth to tenth embodiments.

[0126] In a twelfth embodiment, one or more processors are configured to perform any one of the methods described in accordance with the sixth to tenth embodiments.

[0127] In a thirteenth embodiment, operations performed by a user equipment (UE) include: identifying that single network slice selection assistance information (S-NSSAI) is a configured NSSAI rather than an allowed NSSAI; initiating a mobility registration update process based on one or more trigger conditions; transmitting a registration request message to a network, the registration request message including a requested NSSAI including the S-NSSAI; receiving a response to the registration request message, the response indicating that the S-NSSAI is an allowed NSSAI; and establishing a packet data unit (PDU) session on the S-NSSAI.

[0128] In a fourteenth embodiment, the method according to the thirteenth embodiment further includes receiving a requested NSSAI list including the S-NSSAI from an application processor before the identifying, wherein the requested NSSAI list is received based on a new application, an activated feature, or an upper layer request.

[0129] In a fifteenth embodiment, the method according to the fourteenth embodiment, wherein one or more trigger conditions include detecting that the requested NSSAI list includes a network slice that is a configured NSSAI instead of an allowed NSSAI.

[0130] In a sixteenth embodiment, the method according to the fourteenth embodiment, wherein one or more trigger conditions include detecting that the allowed NSSAI received from the network at the non-access stratum (NAS) layer does not include a network slice that is not part of the requested NSSAI list received from the application processor at the NAS layer.

[0131] In a seventeenth embodiment, the method according to the thirteenth embodiment further includes receiving a newly configured NSSAI list from the network in a configuration update command (CUC) or a registration accept message before the identification, wherein the newly configured NSSAI is an S-NSSAI.

[0132] In an eighteenth embodiment, the method according to the seventeenth embodiment, wherein the one or more trigger conditions include detecting that the updated configured NSSAI list includes a network slice previously requested by an upper layer.

[0133] In a nineteenth embodiment, the method according to the seventeenth embodiment, wherein the one or more trigger conditions include detecting that the allowed NSSAI does not include a network slice that is part of a newly configured NSSAI list received from the network and that was previously requested by an upper layer.

[0134] In a twentieth embodiment, the method according to the thirteenth embodiment, wherein one or more triggering conditions include detecting that the number of network slices included in the stored allowed NSSAI list for a public land mobile network (PLMN) is less than a predetermined maximum number of allowed NSSAIs for the PLMN.

[0135] In a twenty-first embodiment, according to the method of the thirteenth embodiment, one or more trigger conditions include a UE fifth generation mobility management (5GMM) idle operation mode.

[0136] In a twenty-second embodiment, the method according to the thirteenth embodiment further includes starting a timer configured to trigger the release of an N1 non-access stratum (NSA) signaling connection in the following circumstances: i) a configuration update command (CUC) includes a newly configured NSSAI; ii) user plane resources for a packet data unit (PDU) session are not set; iii) an emergency PDU session is not established; and iv) the CUC does not include a registration request bit set to true in the registration request bit of a configuration update indication information element (IE).

[0137] In a twenty-third embodiment, the method according to the twenty-second embodiment, wherein the one or more triggering conditions include expiration of a timer.

[0138] In a twenty-fourth embodiment, a processor is configured to perform any one of the methods described in accordance with the thirteenth to twenty-third embodiments.

[0139] In a twenty-fifth embodiment, a user equipment is configured to perform any one of the methods described in accordance with the thirteenth to twenty-third embodiments.

[0140] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0141] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0142] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0143] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. One or more processors configured to: Storing allowed network slice selection assistance information NSSAI for the user equipment UE, the allowed NSSAI comprising one or more single network slice selection assistance information S-NSSAI; determining that at least one of the S-NSSAIs is no longer an allowed NSSAI; as well as It is determined that there is an active protocol data unit (PDU) session active for the at least one S-NSSAI.

2. The one or more processors of claim 1 , further configured to: Indicate to the network's session management function SMF that the PDU session is to be released.

3. The one or more processors of claim 1 , further configured to: Indicate to the UE that the PDU session is to be released.

4. The one or more processors of claim 3, wherein: The indication comprises a PDU session state information element IE.

5. The one or more processors of claim 4, wherein: The PDU Session Status IE is included in the Registration Accept message.

6. The one or more processors of claim 1, wherein: The one or more processors include a first access and mobility management function AMF of a network to which the UE is currently registered, and the one or more processors are further configured to: Indicate to the second AMF with which the UE was previously registered that the PDU session is to be released.

7. A method comprising: Storing allowed network slice selection assistance information NSSAI for the user equipment UE, the allowed NSSAI comprising one or more single network slice selection assistance information S-NSSAI; determining that at least one of the S-NSSAIs is no longer an allowed NSSAI; as well as It is determined that there is an active protocol data unit (PDU) session active for the at least one S-NSSAI.

8. The method according to claim 7, further comprising: Indicate to the network's session management function SMF that the PDU session is to be released.

9. The method according to claim 7, further comprising: Indicate to the UE that the PDU session is to be released.

10. The method according to claim 9, wherein: The indication comprises a PDU session state information element IE.

11. The method according to claim 10, wherein: The PDU Session Status IE is included in the Registration Accept message.

12. The method according to claim 7, wherein: The method is performed by a first access and mobility management function AMF of a network to which the UE is currently registered, and the method further includes: Indicate to the second AMF with which the UE was previously registered that the PDU session is to be released.

13. A network function of a cellular network, configured to: Storing allowed network slice selection assistance information NSSAI for the user equipment UE, the allowed NSSAI comprising one or more single network slice selection assistance information S-NSSAI; determining that at least one of the S-NSSAIs is no longer an allowed NSSAI; as well as It is determined that there is an active protocol data unit (PDU) session active for the at least one S-NSSAI.

14. The network function according to claim 13, further configured to: Indicate to the network's session management function SMF that the PDU session is to be released.

15. The network function according to claim 13, further configured to: Indicate to the UE that the PDU session is to be released.

16. The network function according to claim 15, wherein: The indication comprises a PDU session state information element IE.

17. The network function according to claim 16, wherein: The PDU Session Status IE is included in the Registration Accept message.

18. The network function according to claim 13, wherein: The network function includes a first access and mobility management function AMF of the cellular network to which the UE is currently registered, and the one or more processors are further configured to: Indicate to the second AMF with which the UE was previously registered that the PDU session is to be released.