User device, communication device, user device method, and communication device method

Abstract

An example aspect of the present disclosure includes a method in a user equipment (UE), the method including communicating with a communications device, the method including transmitting a first S-NSSAI included in a Pending NSSAI to the communications device.

Description

[Technical Field]

[0001] The present disclosure relates to a user equipment (UE) method, a communication device method, a UE, and a communication device. [Background technology]

[0002] The Network Slice-Specific Authentication and Authorization (NSSAA) procedure was introduced in 3GPP Release 16. This procedure allows for network slice-specific authentication and authorization to be performed by an AAA server (which may be located in an external network).

[0003] When a UE requests access to one or more S-NSSAIs, the serving PLMN performs the NSSAA procedure for one or more S-NSSAIs of the HPLMN that are the target of the NSSAA procedure based on the subscription information. When the UE sends a Registration Request message including one or more S-NSSAIs in the Requested NSSAI that are the target of the NSSAA procedure, the AMF sends a Registration Accept message including a list of Pending NSSAIs (or the Pending NSSAIs) that include one or more network slices (e.g., one or more S-NSSAIs) that are the target of the NSSAA procedure. After the UE registration procedure is completed, the AMF initiates the NSSAA procedure for one or more S-NSSAIs in the Pending NSSAI. If the NSSAA procedure is successful, the AMF notifies the UE that one or more S-NSSAIs in the Pending NSSAI are now available for use and causes the UE to delete the one or more S-NSSAIs from the Pending NSSAI storage in the UE and place them in the Allowed NSSAI storage in the UE.

[0004] One or more 3GPP specifications further define a mechanism by which a registration procedure can be initiated by the UE while an NSSAA procedure is ongoing, in which case, in accordance with 3GPP TS 24.501 [5], the UE does not include in the Requested NSSAI one or more S-NSSAIs that the UE has stored in the Pending NSSAI.

[0005] 3GPP Release 17 introduced the Network Slice Based Cell Reselection feature. This feature allows a UE to perform cell reselection based on one or more network slices managed in the NAS layer within the UE. Because support for one or more S-NSSAIs of each cell may be limited, the UE may use the Network Slice Based Cell Reselection feature to tune to the correct cell based on the S-NSSAIs of interest to the UE. When the NAS layer within the UE decides to perform Network Slice Based Cell Reselection, the NAS layer within the UE notifies the AS layer of the UE of one or more Network Slice Access Stratum (AS) Groups (NSAGs) and their priorities. The AS layer of the UE may then perform cell reselection by referencing the supported NSAGs of one or more neighboring cells on the SIBs that the UE can receive, based on the NSAGs and their priorities received from the NAS layer.

[0006] Basically, there are two cases how the NAS layer in the UE selects one or more NSAGs: Based on one or more S-NSSAIs in the Allowed NSSAI, in which the UE seeks the best cell to maximally support one or more S-NSSAIs in the Allowed NSSAI. Based on a new set of one or more S-NSSAIs. This is the case when the UE is trying to register with a new set of one or more S-NSSAIs with Requested NSSAIs that differ from the current Allowed NSSAIs. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TR 21.905:“Vocabulary for 3GPP Specifications”.V17.1.0(2021-12)

[0008] [Non-patent document 2] 3GPP TS 23.501: “System architecture for the 5G System(5GS)”.V17.5.0(2022-06)

[0009] [Non-patent document 3] 3GPP TS 23.502:“Procedures for the 5G System(5GS)”.V17.5.0(2022-06)

[0010] [Non-patent document 4] 3GPP TS 23.503:“Policy and charging control framework for the 5G System(5GS)Stage 2”.V17.5.0(2022-06)

[0011] [Non-patent document 5] 3GPP TS 24.501:“Non-Access-Stratum(NAS)protocol for 5G System(5GS)Stage 3”.V17.7.1(2022-06)

[0012] [Non-patent document 6] 3GPP TS 37.340:“Evolved Universal Terrestrial Radio Access(E-UTRA)and NR Multi-connectivity stage 2”.V17.1.0(2022-06)

[0013] [Non-Patent Document 7] 3GPP TS 38.423: “NG-RAN Xn Application Protocol (XnAP)” V17.1.0 (2022-06) Summary of the Invention [Problem to be solved by the invention]

[0014] The current 3GPP specifications are unclear in one or more situations, such as with respect to a cell reselection function based on network slicing and NSAG.

[0015] For example, if the NAS layer of the UE initiates a network slice-based cell reselection function based on a new set of one or more S-NSSAIs, the new set of one or more S-NSSAIs are included in the Requested NSSAIs of the Registration Request message when the UE initiates a registration procedure after network slice-based cell reselection.

[0016] However, if an NSSAA procedure is in progress for one or more network slices (or one or more S-NSSAIs) from a Pending NSSAI and the UE is no longer interested in one or more S-NSSAIs in the Pending NSSAI, there is no way for the UE to indicate to the AMF that it is no longer interested in one or more S-NSSAIs in the Pending NSSAI and wishes to withdraw the Pending NSSAIs. NSSAA procedures for one or more S-NSSAIs of a Pending NSSAI that the UE is no longer interested in are meaningless and may cause strain on the network. Furthermore, this may result in inefficient network resource usage. Network resources for one or more S-NSSAIs of a Pending NSSAI may be unnecessarily maintained in the network without being used.

[0017] In addition, there are essentially two cases for the UE behavior in the above situation according to, for example, one or more 3GPP specifications: Regardless of the UE's intention, a new set of one or more S-NSSAIs must be requested by the UE while the UE has one or more S-NSSAIs in the Pending NSSAIs. Even if the UE does not want to include one or more S-NSSAIs of the Pending NSSAIs in the Allowed NSSAIs, the UE may have to wait for the NSSAA procedure to be completed and, after network slice-based cell reselection, initiate a new registration procedure without including one or more S-NSSAIs from the Pending NSSAIs in the Requested NSSAIs. For example, there is a case where one or more UE S-NSSAIs in the Requested NSSAI of a new registration procedure and one or more S-NSSAIs in the Pending NSSAIs do not share at least one common NSSRG value, and the UE must wait until the NSSAA procedure for the Pending NSSAI is completed and, after network slice-based cell reselection, initiate a new registration procedure without including one or more S-NSSAIs from the Pending NSSAIs in the Requested NSSAIs.

[0018] In the first case, this may result in inefficient network resource usage: network resources for one or more S-NSSAIs from a Pending NSSAI are unnecessarily maintained in the network without being used.

[0019] In the second case, this may cause unnecessary service degradation for all services that use the new set of one or more S-NSSAIs, as it will cause delays in service activation.

[0020] For example, when a UE moves out of its current Registration Area (RA), the UE may not be able to use the network slice-based cell reselection function even if one or more new candidate cells support the network slice-based cell reselection function.

[0021] According to 3GPP TS 23.501 [2], the AMF provides the UE with NSAG information only for the TA of the RA. As a result, the UE may not know the NSAG information for one or more cells located outside the RA.

[0022] As a result, the UE may have no choice but to use existing cell selection mechanisms when traversing an RA boundary, even if network slice-based cell reselection functionality is well deployed in the operator network.

[0023] This may result in unnecessary service termination for all services that use one or more S-NSSAIs in the Allowed NSSAI, as the UE is unable to select a cell suitable for one or more S-NSSAIs in the Allowed NSSAI based on the network slice-based cell reselection function when the UE crosses an RA boundary. [Means for solving the problem]

[0024] A method for a user equipment (UE) according to an example aspect of the present disclosure includes communicating with a communication device, the method including transmitting a first Single NSSAI (S-NSSAI) included in Pending Network Slice Selection Assistance Information (NSSAI) to the communication device.

[0025] A method for a user equipment (UE) according to an example aspect of the present disclosure includes communicating with a communications device, the method including transmitting, to the communications device, information indicating that the UE is not interested in an S-NSSAI included in a Pending NSSAI.

[0026] A method for a communications device according to an exemplary aspect of the present disclosure includes receiving a first S-NSSAI included in a Pending NSSAI, and aborting an NSSAA procedure for the first S-NSSAI.

[0027] A user equipment (UE) according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to communicate with a communication device, and to transmit a first S-NSSAI included in a Pending NSSAI to the communication device.

[0028] A user equipment (UE) according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to communicate with a communication device, and the at least one hardware processor configured to transmit information to the communication device indicating that the UE is not interested in an S-NSSAI included in a Pending NSSAI.

[0029] A communications apparatus according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory, the at least one hardware processor configured to receive a first S-NSSAI included in a Pending NSSAI, and to abort an NSSAA procedure for the first S-NSSAI. [Brief explanation of the drawings]

[0030] [Figure 1] FIG. 1 is a signaling diagram of a first example of an exemplary first embodiment. [Figure 2] FIG. 10 is a signaling diagram of a second example of the exemplary first embodiment. [Figure 3] FIG. 10 is a signaling diagram of a first example of an exemplary second embodiment. [Figure 4] FIG. 1 is a diagram illustrating a system overview. [Figure 5] FIG. 2 is a block diagram showing a UE. [Figure 6] FIG. 1 is a block diagram illustrating an (R)AN node. [Figure 7]FIG. 1 illustrates a system overview of an (R)AN node based on the O-RAN architecture. [Figure 8] FIG. 1 is a block diagram showing an RU. [Figure 9] FIG. 1 is a block diagram showing a DU. [Figure 10] FIG. 2 is a block diagram showing a CU. [Figure 11] FIG. 1 is a block diagram of an AMF. [Figure 12] FIG. 2 is a block diagram illustrating a PCF. [Figure 13] FIG. 2 is a block diagram illustrating an AUSF. [Figure 14] FIG. 2 is a block diagram illustrating a UDM. [Figure 15] FIG. 1 is a block diagram of an NSSF. DETAILED DESCRIPTION OF THE INVENTION

[0031] Abbreviation For the purposes of this document, 3GPP TR 21.905 [1] and the following abbreviations apply. Abbreviations defined in this document take precedence over definitions of the same abbreviations in 3GPP TR 21.905 [1], if any. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function (AMF) AMF-NG Non-Geographically Selected Access and Mobility Management Function (Non-Geographically selected AMF) ANDSF Access Network Discovery and Selection Function ARFCN Absolute radio-frequency channel number AS Access Stratum ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name (DN Name) DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN (Fully Qualified Domain Name) GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed (roaming) IAB Integrated Access and Backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network (Local Area DN) LBO Local Break Out (roaming) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM (Man in the Middle) MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol N3IWF Non-3GPP Inter Working Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access-Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NPN Non-Public Network NR New Radio NSAG Network Slice Access Layer Group (NSAG) NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice Specific Authentication and Authorization Function (NSSAA Function) NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PCO Protocol Configuration Options PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network (PNI-NPN) PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE (Quality of Experience) RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number SA NR Standalone New Radio (Standalone NR) SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SIB System Information Block SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN Name Serving Network Name SNPN Stand-alone Non-Public Network (Stand-alone NPN) S-NSSAI Single Network Slice Selection Assistance Information (Single NSSAI) SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy (SSC Mode Selection Policy) SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association (TNL Association) TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier (UL Classifier) UPF User Plane Function UPSI UE Policy Section Identifier URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited Public Land Mobile Network (Visited PLMN) W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0032] definition For the purposes of this document, the terms and definitions in 3GPP TR 21.905 [1] and below apply. Terms defined in this document take precedence over any definition of the same term in 3GPP TR 21.905 [1].

[0033] general Those skilled in the art will understand that elements in the figures are illustrated for simplicity and may not necessarily be drawn to scale. Further, with respect to the configuration of a device, one or more components of the device may be represented in the figures by conventional symbols, and the figures may show only certain details relevant to an understanding of aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein.

[0034] For the purposes of promoting an understanding of the principles of the present disclosure, reference will be made to the embodiments illustrated in the drawings and specific language will be used to describe them. It will, however, be understood that no limitation of the scope of the disclosure is thereby intended. Such changes and further modifications in the illustrated systems, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, are to be construed as being within the scope of the present disclosure.

[0035] The terms "comprises," "including," or any other variations thereof, are intended to cover non-exclusive inclusions, such that a process or method comprising a list of steps does not include only those steps, but may also include other steps not expressly listed or inherent in such process or method. Similarly, the term "comprising" precedes one or more devices or entities or subsystems or elements or structures or components, and does not, without further constraints, exclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, appearances of the phrases "in an embodiment," "in another embodiment," and similar language may, but do not necessarily, all refer to the same embodiment.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0037] In the following specification and claims, reference will be made to a number of terms that may be defined to have the following meanings: The singular forms "a," "an," and "said" include plural references unless the context clearly dictates otherwise.

[0038] As used herein, information is associated with data and knowledge, since data is meaningful information and represents values ​​attributed to parameters. Further knowledge refers to an understanding of abstract or concrete concepts. It should be noted that this exemplary system is simplified to facilitate explanation of the disclosed subject matter and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations can be used in addition to or instead of the system to practice the exemplary aspects disclosed herein, and all such aspects are considered to be within the scope of the present disclosure.

[0039] Each of the exemplary aspects described below and the elements included in each exemplary aspect may be implemented independently or in combination with one another. These exemplary aspects include different novel features. As such, these exemplary aspects contribute to achieving different objectives or solving different problems, and to obtaining different advantages.

[0040] An exemplary object of the present disclosure is to provide a method and apparatus that can solve the above problems.

[0041] The following list describes the intended interpretation of terms used in this disclosure: -Subscribed S-NSSAI, multiple Subscribed S-NSSAIs, or one or more Subscribed S-NSSAIs: This can be equal to a list of S-NSSAIs within a Subscribed NSSAI. -Can be equal to an Allowed S-NSSAI, multiple Allowed S-NSSAIs, or one or more Allowed S-NSSAIs: a list of S-NSSAIs within the Allowed S-NSSAI. -Configured S-NSSAI, Configured S-NSSAIs, or one or more Configured S-NSSAIs: The Configured S-NSSAI may be equal to a list of S-NSSAIs within the Configured NSSAI. -Rejected S-NSSAI, multiple Rejected S-NSSAIs, or one or more Rejected S-NSSAIs: This may be equal to a list of S-NSSAIs within the Rejected NSSAI. -It may be equal to a Pending S-NSSAI, multiple Pending S-NSSAIs, or a list of S-NSSAIs within one or more Pending S-NSSAIs:Pending NSSAIs.

[0042] Cell reselection based on a network slice can be expressed as network slice based cell reselection.

[0043] Exemplary First Aspect When the NAS layer of UE3 (UE NAS301) initiates a network slice-based cell reselection function based on one or more S-NSSAIs in the Allowed NSSAI, one or more NSAGs and their priorities are selected based on both one or more S-NSSAIs in the Allowed NSSAI and one or more S-NSSAIs in the Pending NSSAI.

[0044] First example of the first exemplary embodiment: A first example of the exemplary first aspect discloses a method in which a UE NAS301 selects one or more NSAGs and NSAG priorities (or one or more NSAG priorities) based on both an Allowed NSSAI and a Pending NSSAI for cell reselection based on a network slice, and transmits the selected one or more NSAGs and NSAG priorities (or NSAG priorities) to an AS layer of the UE (UE AS302).

[0045] After the NSSAA procedure is completed, the UE NAS301 checks the Allowed NSSAI, and if there is a difference from before the NSSAA procedure, the UE NAS301 selects an NSAG and NSAG priority based on the Allowed NSSAI since there is no Pending NSSAI at the moment, and the UE NAS301 sends the selected NSAG and NSAG priority to the UE's AS layer (UE AS302).

[0046] Hereinafter, detailed processing of the first example of the first exemplary embodiment will be described with reference to FIG.

[0047] Step 1. UE NAS301 sends a Registration Request message to AMF70, including S-NSSAI#1 and S-NSSAI#2 in the Requested NSSAI.

[0048] Step 2. The AMF 70 sends a Registration Accept message to the UE NAS 301, including the Configured NSSAI, Allowed NSSAI, Pending NSSAI and NSAG priority.

[0049] The Configured NSSAIs include S-NSSAI#1 with associated NSAG#1, S-NSSAI#2 with associated NSAG#2, and S-NSSAI#3 with associated NSAG#3. Since S-NSSAI#1 is the network slice that UE3 is allowed to use, Allowed NSSAI includes S-NSSAI#1.

[0050] Here, the NSAG information in the Registration Accept message may include the relationship between the S-NSSAI and the NSAG (i.e., S-NSSAI#1 with associated NSAG#1, S-NSSAI#2 with associated NSAG#2, and S-NSSAI#3 with associated NSAG#3).

[0051] The Pending NSSAI includes S-NSSAI#2 because S-NSSAI#2 is the subject of an NSSAA procedure based on subscriber data in the home network (HPLMN).

[0052] The NSAG priority indicates the priority between NSAGs. For example, the NSAG priority may indicate that NSAG#2 has a higher priority than NSAG#1.

[0053] Step 3. Upon receiving the Registration Accept message in step 2, the UE NAS 301 selects an NSAG and an NSAG priority based on both one or more S-NSSAIs in the Allowed NSSAIs and one or more S-NSSAIs in the Pending NSSAIs. That is, the UE NAS 301 assumes that the NSSAA procedure for all one or more S-NSSAIs in the Pending NSSAIs will be completed successfully. For example, the UE NAS 301 may select NSAG#1 and NSAG#2 as NSAGs based on the Allowed NSSAIs and the Pending NSSAIs. For example, the UE NAS 301 may select or determine that NSAG#2 has a higher priority than NSAG#1 as an NSAG priority based on at least one of the Allowed NSSAIs, the Pending NSSAIs, and the NSAG priority.

[0054] Step 4. The UE NAS 301 sends a Registration Complete message to the AMF 70, including the Chosen NSAG and the Chosen NSAG priority.

[0055] The Chosen NSAGs include one or more NSAGs selected in step 3. The Chosen NSAG Priorities include the NSAG Priorities determined in step 3. The Chosen NSAGs may be expressed as selected NSAGs or derived NSAGs. The Chosen NSAG Priorities may be expressed as selected NSAG Priorities or derived NSAG Priorities or determined NSAG Priorities.

[0056] For example, the Chosen NSAG may include NSAG#1 and NSAG#2. For example, the Chosen NSAG priority may include an NSAG priority indicating that NSAG#2 has a higher priority than NSAG#1.

[0057] Upon receiving the Registration Complete message, the AMF 70 stores the Chosen NSAG and the Chosen NSAG priority in the UE context of the AMF 70. The AMF 70 (e.g., the AMF 70 as the initial AMF) may send the Chosen NSAG and the Chosen NSAG priority to the target AMF during the Registration with AMF re-allocation procedure in accordance with 3GPP TS 23.502 [3].

[0058] The AMF 70 may notify the RAN 5 (e.g., a RAN node) of the Chosen NSAG and the Chosen NSAG priority each time the AMF 70 becomes associated with the RAN 5. For example, an Initial Context Setup request message, a UE Context Modification Request message, a Connection Establishment Indication message, an AMF CP Relocation Indication message, a UE Information Transfer message, a UE Context Suspend Response message, a UE Context Resume Response message, a Handover Command message, a Handover Request message, a Path Switch Acknowledge message, a Downlink RAN ​​Status Transfer message, a Handover Success message, a Downlink RAN ​​Early Status Transfer message, a Paging message, or any other existing or new NGAP message includes the Chosen NSAG and the Chosen NSAG priority and forwards them from the AMF 70 to the RAN 5. The AMF 70 may also activate or deactivate network slice support and priority-based handover in the RAN 5 by including new parameters or flags in the above messages between the AMF 70 and the RAN 5, with the purpose of activating or deactivating consideration of network slice support and priority by the RAN 5 in connected mode mobility, i.e., in selecting a handover to a target cell or selecting an RRC connection release by redirection to the target cell. The RAN 5 may then use the Chosen NSAG and Chosen NSAG priority to select one or more candidate cells for the handover procedure.The one or more candidate cells for handover may be selected based on at least one combination of support for one or more NSAGs in the one or more candidate cells and measured signal strength measured and reported by the UE 3. For example, the RAN 5 may handover the UE 3 to the selected one or more candidate cells when performing the handover. For example, if the Chosen NSAG includes NSAG#1 and NSAG#2, RAN5 may select one or more candidate cells that support at least one of NSAG#1 and NSAG#2 (e.g., RAN5 may select one or more candidate cells that support at least one of S-NSSAI#1 associated with NSAG#1 and S-NSSAI#2 associated with NSAG#2).

[0059] Also, for example, assume that the Chosen NSAG includes NSAG#1 and NSAG#2, and the measured signal strength of one cell supporting NSAG#1 (e.g., one cell supporting S-NSSAI#1 associated with NSAG#1) is higher than the measured signal strength of another cell supporting NSAG#2 (e.g., another cell supporting S-NSSAI#2 associated with NSAG#2). In this case, RAN5 may select one cell supporting NSAG#1 as one or more candidate cells.

[0060] Furthermore, when RAN5 selects one or more candidate cells, RAN5 may take into consideration the Chosen NSAG priority. For example, assume that the Chosen NSAG priority indicates that the priority of NSAG#2 is higher than the priority of NSAG#1. In this case, if RAN5 finds, as one or more candidate cells, one cell that supports NSAG#1 (e.g., one cell that supports S-NSSAI#1 associated with NSAG#1) and another cell that supports NSAG#2 (e.g., another cell that supports S-NSSAI#2 associated with NSAG#2), RAN5 may select the other cell.

[0061] The source RAN 5 (e.g., the RAN 5 that receives the Chosen NSAG and Chosen NSAG priority from the AMF 70 and performs the handover procedure) may notify the target RAN 5 of the Chosen NSAG and Chosen NSAG priority. For example, a Handover Request message, an SN Status Transfer message, a RAN Paging message, and an Early Status Transfer message, or any other existing or new XnAP message, includes the Chosen NSAG and Chosen NSAG priority and transfers them from the source RAN 5 to the target RAN 5.

[0062] For example, the target RAN 5 may use the Chosen NSAG and Chosen NSAG priority to select one or more candidate cells for the handover procedure in the same manner as described above.

[0063] The target AMF receiving the Chosen NSAG and Chosen NSAG priority may perform one or more processes in the same manner as AMF 70 described above.

[0064] Step 5. The UE NAS 301 notifies the UE AS 302 of the selected NSAGs (e.g., NSAG#1 and NSAG#2) and the NSAG priority (e.g., the NSAG priority indicating that NSAG#2 has a higher priority than NSAG#1).

[0065] Step 6. The UE AS302 may perform cell reselection based on the network slice based on the selected NSAG (e.g., NSAG#1 and NSAG#2) and NSAG priority received in step 5.

[0066] In one example, the UE 3 applies a network slice-based cell reselection procedure when the UE 3 transitions to a CM-IDLE mode (e.g., when the network (e.g., AMF 70) explicitly releases the current N1 signaling connection by initiating signaling within the network, or when an RLF is detected within the UE 3 or the network and the UE 3 or the network locally releases the N1 signaling connection). The UE 3 may also apply the same procedure defined herein when the UE 3 transitions to an RRC-INACTIVE state. The NAS layer within the UE (e.g., UE NAS 301) may initiate a network slice-based cell reselection function (or network slice-based cell reselection) at any time.

[0067] Step 7. The NSSAA procedure is performed for S-NSSAI#2 between the UE NAS 301 and the AAA 201. Step 7 may be performed after step 4 and before step 5. Furthermore, the order of step 7 and the set of steps 4 and 5 may be interchanged. The AAA may be referred to as the AAA server.

[0068] Step 8. After the NSSAA procedure is completed, the UE NAS 301 may reselect (or select) an NSAG and determine the NSAG priority based on the Allowed NSSAIs only if the NSSAA procedure in step 7 failed, i.e., if one or more S-NSSAIs from the Pending NSSAIs failed in the NSSAA procedure. If the NSSAA procedure in step 7 is successful for all one or more S-NSSAIs from the Pending NSSAIs and all one or more S-NSSAIs from the Pending NSSAIs have been added to the Allowed NSSAIs of the UE 3 by the network (e.g., AMF 70), the UE NAS 301 does not perform the selection of an NSAG and NSAG priority again, as there is no difference as input for the NSAG selection performed in step 3.

[0069] Step 9. The UE NAS 301 may send a NAS message including the Chosen NSAG and the Chosen NSAG priority to the AMF 70. The Chosen NSAG includes one or more NSAGs selected in step 8. The Chosen NSAG priority includes the NSAG priority determined in step 8. For example, the NAS message may be a Registration Request message, a Registration Complete message, an Authentication response message, a UL NAS transport message, a Service request message, a Configuration update complete message, an Identity response message, a Notification response message, a Security mode complete message, a Network slice-specific authentication complete message, or any other existing or new NAS message that conveys the Chosen NSAG and Chosen NSAG priority to AMF70.

[0070] For example, upon receiving the NAS message in step 9, the AMF 70 may notify the RAN 5 of the Chosen NSAG and the Chosen NSAG priority, as in step 4.

[0071] For example, the RAN 5 may use the Chosen NSAG and Chosen NSAG priority to select one or more candidate cells for the handover procedure, similar to step 4.

[0072] For example, the source RAN 5 (e.g., the RAN 5 that receives the Chosen NSAG and Chosen NSAG priority from the AMF 70 and performs the handover procedure) may notify the target RAN 5 of the Chosen NSAG and Chosen NSAG priority in the same manner as in step 4.

[0073] For example, when AMF 70 receives a NAS message, AMF 70 may perform one or more processes similar to step 4.

[0074] Step 10. UE NAS301 may notify UE AS302 of the selected NSAG (e.g., Chosen NSAG, including NSAG#1, determined in step 8), i.e., in this example, the NSSAA procedure for S-NSSAI#2 has failed.

[0075] The NSAG priority (e.g., the Chosen NSAG priority determined in step 8) may also be signaled to the UE AS 302. For example, even if there is only one NSAG being signaled, the NSAG priority may also be signaled to the UE AS 302.

[0076] Step 11. The UE AS302 may perform cell reselection based on the network slice based on the NSAG (e.g., NSAG#1) received in step 10.

[0077] Variation 1 of the first example of the first exemplary embodiment: When UE3 roams to a visited PLMN (VPLMN) and UE3 has a Configured NSSAI for the VPLMN, UE3 performs cell reselection based on a network slice based on one or more S-NSSAIs intended to be set as the Requested NSSAI for the Registration Request message (e.g., one or more S-NSSAIs included in the Configured NSSAI for the VPLMN).

[0078] Variation 2 of the first example of the first exemplary embodiment: In step 1, when an RRC connection is established or has been established, the current RAN 501 (e.g., a RAN node that has established or is establishing an RRC connection with the UE 3) may inform the UE AS 302 of one or more supported NSAGs supported by one or more current cells using an RRC Setup message, an RRC Reestablishment message, an RRC Reject message, or any existing or new RRC message. The one or more supported NSAGs may indicate one or more NSAGs supported by one or more current cells. The current cell may be controlled by the current RAN 501. The current RAN 501 may be a RAN or a RAN node serving the UE 3.

[0079] When the UE AS302 receives one or more supported NSAGs, the UE AS302 notifies the UE NAS301 of this.

[0080] When the UE NAS301 selects one or more NSAGs and NSAG priorities, the UE NAS301 refers to one or more supported NSAGs in step 3. If one or more Chosen NSAGs in step 3 are included in one or more supported NSAGs received from the current RAN501, the UE NAS301 does not activate cell reselection based on network slices by not sending any NSAGs and their priorities to the UE AS302.

[0081] Variation 3 of the first example of the first exemplary embodiment: In one example, the UE NAS301 sends a Pending NSSAI for 3GPP access only (one or more S-NSSAIs subject to an NSSAA procedure are requested via 3GPP access) to the UE AS302 for cell reselection based on a network slice.

[0082] For example, the UE AS302 may use the Pending NSSAI for 3GPP access together with the selected NSAG and NSAG priority received in step 5 for cell reselection based on the network slice. For example, the UE AS302 may reselect one or more cells that support one or more S-NSSAIs in the Pending NSSAI for 3GPP access in step 6.

[0083] For example, the UE NAS 301 may inform the UE AS 302 in step 5 of the selected NSAG and NSAG priority for the 3GPP access.

[0084] For example, in step 3, the UE NAS301 may select an NSAG and an NSAG priority based on both one or more S-NSSAIs in the Allowed NSSAI for 3GPP access and one or more S-NSSAIs in the Pending NSSAI for 3GPP access (e.g., the UE NAS301 may select an NSAG for 3GPP access and an NSAG priority for 3GPP access). Then, in step 5, the UE NAS301 may notify the UE AS302 of the selected NSAG and NSAG priority for 3GPP access. The UE AS302 may perform network slice-based cell reselection based on the NSAG for 3GPP access and the NSAG priority for 3GPP access.

[0085] In one example, UE NAS301 sends a Pending NSSAI for 3GPP access (one or more S-NSSAIs subject to an NSSAA procedure are requested via 3GPP access) and a Pending NSSAI for non-3GPP access (one or more S-NSSAIs subject to an NSSAA procedure are requested via non-3GPP access) to UE AS302 for cell reselection based on a network slice.

[0086] For example, the UE AS302 may use the Pending NSSAI for 3GPP access and the Pending NSSAI for non-3GPP access together with the selected NSAG and NSAG priority received in step 5 for network slice-based cell reselection. For example, in step 6, the UE AS302 may reselect one or more cells that support at least one of the one or more S-NSSAIs in the Pending NSSAI for 3GPP access and the one or more S-NSSAIs in the Pending NSSAI for non-3GPP access.

[0087] For example, in step 5, the UE NAS 301 may notify the UE AS 302 of the selected NSAG and NSAG priority for at least one of the 3GPP access and the non-3GPP access.

[0088] For example, in step 3, the UE NAS 301 may select an NSAG and an NSAG priority by considering at least one of one or more S-NSSAIs in the Allowed NSSAI for 3GPP access, one or more S-NSSAIs in the Pending NSSAI for 3GPP access, one or more S-NSSAIs in the Allowed NSSAI for non-3GPP access, and one or more S-NSSAIs in the Pending NSSAI for non-3GPP access (e.g., the UE NAS 301 may select at least one of an NSAG for 3GPP access, an NSAG priority for 3GPP access, an NSAG for non-3GPP access, and an NSAG priority for non-3GPP access). Then, in step 5, the UE NAS 301 may notify the UE AS 302 of at least one of the NSAG for 3GPP access, the NSAG priority for 3GPP access, the NSAG for non-3GPP access, and the NSAG priority for non-3GPP access. The UE AS302 may perform cell reselection based on a network slice based on at least one of an NSAG for 3GPP access, an NSAG priority for 3GPP access, an NSAG for non-3GPP access, and an NSAG priority for non-3GPP access.

[0089] Variation 4 of the first example of the first exemplary embodiment: If one or more S-NSSAIs from the Requested NSSAIs or Pending NSSAIs are rejected for Network Slice Admission Control (NSAC) reasons, i.e., because the network slice quota has been reached or exceeded, in step 2 during Registration Accept or in step 7 during the UE Configuration Update procedure, the UE NAS 301 still considers such one or more S-NSSAIs for network slice-based cell reselection, and the UE NAS 301 selects NSAGs and NSAG priorities and provides the NSAGs and NSAG priorities for such one or more S-NSSAIs to the UE AS 302 in step 5 or step 10. The UE NAS 301 may receive information regarding the NSAC (e.g., information indicating that the network slice quota has been reached or exceeded (i.e., no S-NSSAIs are available because the maximum number of UEs has been reached)) from one or more network nodes (e.g., the AMF 70 or the SMF). For example, even if one or more S-NSSAIs in the Requested NSSAI or Pending NSSAI are rejected for NSAC reason, the UE NAS301 may still consider such one or more S-NSSAIs for cell reselection based on the network slice, and the UE NAS301 may select an NSAG and an NSAG priority in step 3 or step 8 and provide the NSAG and the NSAG priority for such one or more S-NSSAIs to the UE AS302 in step 5 or step 10. For example, regardless of the result or status of NSAC, the UE NAS301 may select an NSAG and an NSAG priority in step 3 or step 8 and provide the NSAG and the NSAG priority for such one or more S-NSSAIs to the UE AS302 in step 5 or step 10.

[0090] Variation 5 of the first example of the first exemplary embodiment: After the NSAG and NSAG priority are selected in step 3 or step 8, the UE AS302 may send the NSAG and NSAG priority to the newly selected RAN5 via an RRC message as the Chosen NSAG and Chosen NSAG priority.

[0091] See step 4 for how the new RAN5 uses the Chosen NSAG and Chosen NSAG priority.

[0092] For example, the UE AS302 includes the Chosen NSAG and the Chosen NSAG priority in an RRC Setup Request message, an RRC Setup Complete message, an RRC Reconfiguration message, or any other existing or new RRC message, and sends at least one of these messages to the newly selected RAN5.

[0093] Variation 6 of the first example of the first exemplary embodiment: When a cell reselection based on a network slice is performed by the UE AS302 in steps 6 and 11, the UE AS302 may scan or monitor NSAG information transmitted by SIB (e.g., SIB16) and / or dedicated signaling in the current cell and in one or more neighboring cells. As defined in 3GPP TS 37.340 [6], if a cell is configured as a Master Node (MN) for multi-connectivity, the MN may transmit (i.e., broadcast) NSAG information supported by one or more associated Secondary Nodes (one or more SNs) for multi-connectivity in addition to the NSAG information supported by the MN. The NSAG information may indicate one or more NSAGs or may be information related to one or more NSAGs. The NSAG information supported by one or more associated SNs may indicate one or more NSAGs and at least one of their priorities related to the SNs. When the MN broadcasts NSAG information supported by one or more SNs, the MN may broadcast the NSAG information together with information indicating the associated SN(s). The information indicating the associated SN(s) may be a frequency band, a physical cell identity, or an ARFCN.

[0094] If the UE AS302 receives NSAG information (e.g., one or more NSAGs) via a SIB (e.g., SIB16) and / or dedicated signaling of the current cell configured as the MN, and the NSAGs supported by one or more SNs (e.g., one or more NSAGs may be indicated by the NSAG information) best match the one or more NSAGs received from the UE NAS301, the UE3 may remain in the current cell because one or more S-NSSAIs (or services related to one or more S-NSSAIs) related to one or more NSAGs supported by one or more SNs can be provisioned by multi-connection with one or more SNs when PDU sessions related to one or more S-NSSAIs are established.

[0095] For example, if the UE AS302 receives NSAG information (e.g., one or more NSAGs) through a SIB (e.g., SIB16) and / or dedicated signaling of a neighboring cell, and one or more NSAGs supported by the MN or SN for one or more neighboring cells (e.g., one or more NSAGs may be indicated by the NSAG information of one or more neighboring cells) best match the one or more NSAGs received from the UE NAS301, the UE3 may reselect one or more neighboring cells because the S-NSSAI (one or more services associated with the S-NSSAI) associated with the NSAGs supported by the MN or one or more SNs for one or more neighboring cells can be provisioned by multi-connection with the MN and one or more SNs when a PDU session for the S-NSSAI is established.

[0096] For example, the UE AS302 may perform cell reselection based on a network slice based on broadcasted NSAG information for one or more SNs.

[0097] An MN may obtain NSAG information of one or more associated SNs from a local configuration or via the XnAP protocol defined in 3GPP TS 38.423 [7], and may broadcast the NSAG information of one or more associated SNs. The NSAG information of one or more associated SNs may include one or more NSAGs supported by the one or more associated SNs, NSAG priorities associated with the supported NSAG(s), and other related information.

[0098] For example, the SN may send an Xn Setup message, an Xn Setup Response message, an NG-RAN node Configuration Update message, an NG-RAN node Configuration Update Acknowledge message, a Mobility Change request message, a Mobility Change Acknowledge message message, or any other existing or new XnAP message to the MN, which message includes one or more NSAGs supported by the SN, NSAG priorities associated with the one or more supported NSAGs, and other relevant information.

[0099] Variation 7 of the first example of the first exemplary embodiment: In one example, the AMF 70 sends an indicator indicating whether the NSAG procedure is applicable to the Pending NSSAI (or one or more S-NSSAIs in the Pending NSSAI) to the UE 3 in an existing NAS message or a new NAS message during an existing NAS procedure (e.g., a Registration Accept message during an initial registration procedure or a regular and mobility registration procedure). If the indicator indicates that the NSAG procedure is not applicable to one or more S-NSSAIs in the Pending NSSAI, the UE NAS 301 does not send the one or more S-NSSAIs in the Pending NSSAI (or NSAGs related to one or more S-NSSAIs in the Pending NSSAI) to the UE AS 302 for the slice-based cell reselection procedure. For example, if the indicator indicates that the NSAG procedure is not applicable to S-NSSAI#2 in the Pending NSSAI, the UE NAS301 may not transmit at least one of NSAG#2 associated with the Pending NSSAI and S-NSSAI#2 to the UE AS302 in step 5 (or the UE NAS301 may transmit at least one of NSAG#1 and an NSAG priority associated with NSAG#1 to the UE AS302 in step 5). For example, if the indicator indicates that the NSAG procedure is applicable to S-NSSAI#2 in the Pending NSSAI, the UE NAS301 may transmit at least one of NSAG#2 associated with the Pending NSSAI and S-NSSAI#2 to the UE AS302 in step 5 (e.g., the UE NAS301 may transmit at least one of NSAG#1, NSAG#2, and an NSAG priority associated with at least one of NSAG#1 and NSAG#2 to the UE AS302 in step 5). For example, the UE AS302 may use the Pending NSSAI, similar to Variation 3 of the first example of the exemplary first aspect.

[0100] In one example, the AMF 70 sends an indicator for each S-NSSAI in the Pending NSSAI. The UE 3 performs the NSAG procedure as defined above in this variant for each S-NSSAI as indicated by the indicator. For example, if the Pending NSSAI includes S-NSSAI#4 and S-NSSAI#5, the indicator may indicate that the NSAG procedure is not applicable to S-NSSAI#4 and that the NSAG procedure is applicable to S-NSSAI#5. The AMF 70 may set the indicator based on an operator policy, a local configuration within the AMF 70, or the like. If the indicator indicates that the NSAG procedure is not applicable to S-NSSAI#4 and that the NSAG procedure is applicable to S-NSSAI#5, the UE NAS 301 may send at least one of the NSAG associated with S-NSSAI#5 and the NSAG priority associated with S-NSSAI#5 to the UE AS 302. The UE AS302 may then perform a slice-based cell reselection procedure based on at least one of the NSAG associated with S-NSSAI#5 and the NSAG priority associated with S-NSSAI#5.

[0101] The above modification can be applied to the second example of the illustrative first aspect.

[0102] According to the first example of the exemplary first aspect and the modified example of the first example of the exemplary first aspect, the above-mentioned problems can be solved.

[0103] For example, the first example of the exemplary first aspect and the variant of the first example of the exemplary first aspect can solve the problem of one or more situations that are unclear in the current 3GPP specifications.

[0104] For example, the first example of the exemplary first aspect and the variant of the first example of the exemplary first aspect can solve the problem of there being one or more unclear situations regarding the cell reselection function based on the network slice, NSAG, etc.

[0105] For example, the first example of the exemplary first aspect and the variant example of the first example of the exemplary first aspect can solve the problem that it is unclear how one or more S-NSSAIs in a Pending NSSAI of a UE should be used when the UE initiates a cell reselection function based on a network slice.

[0106] Additionally, for example, the first example of the exemplary first aspect and the variant of the first example of the exemplary first aspect can solve the problem that it is unclear how the source RAN selects candidate cells for handover.

[0107] For example, the first example of the exemplary first aspect and the modified example of the first example of the exemplary first aspect can solve the problem that it is not clear how the source RAN 5 selects one or more candidate cells for handover by having the RAN select one or more candidate cells taking into account the NSAGs and NSAG priorities.

[0108] Second example of the exemplary first embodiment: A second example of the exemplary first aspect discloses a method in which the UE NAS301 initially selects an NSAG and an NSAG priority based on an Allowed NSSAI for cell reselection based on a network slice, even though the UE NAS301 has a Pending NSSAI in the UE storage.

[0109] After all one or more NSSAA procedures are completed, the UE NAS301 reselects the NSAG and NSAG priority based on the Allowed NSSAI again if one or more S-NSSAIs from the Pending NSSAI are successful for one or more NSSAA procedures, and the UE NAS301 sends the selected NSAG and NSAG priority to the UE's AS layer (UE AS302).

[0110] Hereinafter, detailed processing of the second example of the exemplary first aspect will be described with reference to FIG.

[0111] Steps 1 and 2 are the same as steps 1 and 2 in FIG. 1 for the first example of the first exemplary embodiment.

[0112] Step 3. Upon receiving the Registration Accept message in step 2, the UE NAS301 selects an NSAG and an NSAG priority based on one or more S-NSSAIs in the Allowed NSSAIs. For example, the UE NAS301 may select NSAG#1 as the NSAG. For example, the UE NAS301 may select or determine that NSAG#2 has a higher priority than NSAG#1 as the NSAG priority. For example, the UE NAS301 may select an NSAG and an NSAG priority based on one or more S-NSSAIs in the Allowed NSSAIs before the NSSAA procedure for one or more S-NSSAIs in the Pending NSSAI is completed. For example, the UE NAS301 may select an NSAG and an NSAG priority based on one or more S-NSSAIs in the Allowed NSSAIs before the NSSAA procedure for S-NSSAI#2 in the Pending NSSAI is completed. For example, the UE NAS301 may select an NSAG and an NSAG priority based on one or more S-NSSAIs in the Allowed NSSAI after the NSSAA procedure for one or more S-NSSAIs in the Pending NSSAI is successfully completed. For example, the UE NAS301 may select an NSAG and an NSAG priority based on one or more S-NSSAIs in the Allowed NSSAI after the NSSAA procedure for S-NSSAI#2 in the Pending NSSAI is successfully completed.

[0113] Step 4 is the same as step 4 in Fig. 1 for the first example of the exemplary first aspect. For example, the UE NAS 301 may send a Registration Complete message including the Chosen NSAG and the Chosen NSAG priority to the AMF 70.

[0114] The Chosen NSAGs include one or more NSAGs selected in step 3. The Chosen NSAG Priorities include the NSAG priorities determined in step 3.

[0115] For example, the Chosen NSAG may include NSAG #1. For example, the Chosen NSAG priority may include an NSAG priority indicating that NSAG #2 has a higher priority than NSAG #1.

[0116] AMF 70 may perform one or more of the same processes as in FIG.

[0117] Step 5. The UE NAS 301 notifies the UE AS 302 of the selected NSAG (eg, NSAG#1).

[0118] The NSAG priority may also be signaled to the UE AS 302. For example, even if there is only one NSAG being signaled, the NSAG priority may also be signaled to the UE AS 302.

[0119] Step 6. The UE AS302 may perform network slice-based cell reselection based on the selected NSAG (e.g., NSAG#1) received in step 5.

[0120] Step 7. The NSSAA procedure is performed for S-NSSAI#2 between the UE NAS 301 and the AAA 201. Step 7 may be performed after step 4 and before step 5. Furthermore, the order of step 7 and the set of steps 4 and 5 may be interchanged.

[0121] Step 8. After the NSSAA procedure is completed, the UE NAS301 may reselect (or select) an NSAG and NSAG priority based on the Allowed NSSAI (e.g., at least one of S-NSSAI#1 and S-NSSAI#2) if the NSSAA procedure in step 7 is successful. If all one or more NSSAA procedures fail in step 7, the UE NAS301 does not perform the NSAG and NSAG priority selection again because there is no difference as input for the NSAG selection performed in step 3. For example, the UE NAS301 may select NSAG#1 and NSAG#2 as the NSAGs. For example, the UE NAS301 may select or determine that NSAG#2 has a higher priority than NSAG#1 as the NSAG priority. The Allowed NSSAI in step 8 may include at least S-NSSAI#2 because the NSSAA procedure for S-NSSAI#2 was successfully completed. The Allowed NSSAIs in step 8 may include at least S-NSSAI#1 and S-NSSAI#2 since the NSSAA procedure for S-NSSAI#2 was completed successfully.

[0122] Step 9 is the same as step 9 in Fig. 1 for the first example of the first exemplary aspect. For example, the Chosen NSAG may include NSAG#1 and NSAG#2. For example, the Chosen NSAG priority may include an NSAG priority indicating that NSAG#2 has a higher priority than NSAG#1.

[0123] Step 10. The UE NAS 301 may notify the UE AS 302 of the selected NSAG (e.g., NSAG#1 and NSAG#2) and NSAG priority (e.g., NSAG priority indicating that NSAG#2 has a higher priority than NSAG#1).

[0124] Step 11. The UE AS302 may perform cell reselection based on the network slice based on the NSAGs (e.g., NSAG#1 and NSAG#2) and NSAG priority (e.g., NSAG priority indicating that NSAG#2 has a higher priority than NSAG#1) received in step 10.

[0125] Variation 1 of the second example of the first exemplary embodiment: In step 8, if one or more NSSAA procedures are successfully performed for one or more S-NSSAIs and the UE NAS301 recognizes that one or more S-NSSAIs newly added to the Allowed NSSAIs are not supported by the current cell, then in step 11, a network slice-based cell reselection is performed and the UE NAS301 suppresses any services on the newly added S-NSSAI or S-NSSAIs until the UE3 confirms that the newly selected cell supports the NSAGs of the newly added S-NSSAI or S-NSSAIs.

[0126] Based on information received from the current cell (e.g., system information) and information included in the Registration Accept message of step 2, UE NAS301 may recognize that one or more S-NSSAIs newly added to the Allowed NSSAIs are not supported by the current cell. For example, assume that UE NAS301 receives a Registration Accept message in step 2, and UE3 receives system information from the current cell (e.g., the current RAN) including information related to NSAG#1 (e.g., this information indicates that the current cell supports NSAG#1 or supports S-NSSAI#1 related to NSAG#1).

[0127] In this case, if the NSSAA procedure for S-NSSAI#2 included in the Pending NSSAI is successfully executed, UE3 receives an Allowed NSSAI that includes at least S-NSSAI#2.

[0128] In this case, UE3 recognizes based on the system information that the current cell does not support NSAG#2 or S-NSSAI#2 associated with NSAG#2.

[0129] UE NAS301 may then suppress any services on S-NSSAI#2 until network slice-based cell reselection is performed in step 11 and UE3 confirms that the newly selected cell supports NSAG for S-NSSAI#2. For example, UE3 may perform network slice-based cell reselection to a cell that supports NSAG for S-NSSAI#2, and then UE3 may start using one or more services on S-NSSAI#2.

[0130] According to the second example of the exemplary first aspect and the modified example of the second example of the exemplary first aspect, the above-mentioned problems can be solved.

[0131] For example, the first example of the exemplary first aspect and the variant of the first example of the exemplary first aspect can solve the problem of one or more situations that are unclear in the current 3GPP specifications.

[0132] For example, the second example of the exemplary first aspect and the variant of the second example of the exemplary first aspect can solve the problem of there being one or more unclear situations regarding the cell reselection function based on the network slice and regarding the NSAG.

[0133] For example, the second example of the exemplary first aspect and the variant of the second example of the exemplary first aspect can solve the problem that it is unclear how one or more S-NSSAIs in a Pending NSSAI of a UE should be used when the UE initiates a cell reselection function based on a network slice.

[0134] Additionally, for example, the second example of the exemplary first aspect and the variant of the second example of the exemplary first aspect may solve the problem of it being unclear how the source RAN selects one or more candidate cells for handover.

[0135] For example, the second example of the exemplary first aspect and the variant of the second example of the first aspect can solve the problem that it is not clear how the source RAN selects one or more candidate cells for handover by having the RAN select one or more candidate cells taking into account the NSAGs and the priorities of the NSAGs.

[0136] Exemplary Second Embodiment When the NAS layer of UE3 (UE NAS301) initiates a network slice-based cell reselection function based on a new set of one or more S-NSSAIs, the new set of one or more S-NSSAIs are included in the Requested NSSAI of the Registration Request message when the UE initiates a registration procedure after network slice-based cell reselection.

[0137] This exemplary aspect discloses a method in which a UE 3 triggers the withdrawal of one or more S-NSSAIs from Pending NSSAIs in a network, for example, an AMF 70.

[0138] First example of exemplary second embodiment: A first example of the exemplary second aspect discloses a method for revoke one or more S-NSSAIs in a Pending NSSAI by a UE 3.

[0139] When the NSSAA procedure is in progress and the UE 3 is no longer interested in one or more S-NSSAIs in the Pending NSSAI, the UE NAS 301 sends a Registration Request message including one or more S-NSSAIs in the Withdrawing NSSAI to the AMF 70. The Withdrawing NSSAI indicates to the AMF 70 that the UE 3 is no longer interested in such one or more S-NSSAIs in the Withdrawing NSSAI.

[0140] Detailed processing of the first example of the exemplary second aspect will be described later with reference to FIG.

[0141] Steps 1 and 2 are the same as steps 1 and 2 in FIG. 1 for the first example of the first exemplary embodiment.

[0142] Step 3. NSSAA procedure is performed between UE NAS 301 and AAA 201 for S-NSSAI#2 in Pending NSSAI.

[0143] Step 4. UE NAS301 selects NSAGs and NSAG priorities based on a new set of one or more S-NSSAIs. In this example, S-NSSAI#3 is referred to as the new set of one or more S-NSSAIs. For example, an application in UE3 associated with S-NSSAI#3 is activated, and user data is buffered in UE3 for transmission to an associated application server in the external network. UE NAS301 may then select NSAGs and NSAG priorities based on S-NSSAI#3. S-NSSAI#3 may be associated with NSAG#3. UE NAS301 may select NSAG#3 and an NSAG priority for NSAG#3. For example, UE3 may perform one or more processes in step 4 while UE3 has a Pending NSSAI including S-NSSAI#2. For example, UE3 may perform one or more processes in step 4 when an NSSAA procedure for S-NSSAI#2 is in progress.

[0144] Step 5. The UE NAS 301 notifies the UE AS 302 of the selected NSAG (eg, NSAG#3).

[0145] Even if there is only one NSAG being advertised, the NSAG priority (eg, the NSAG priority for NSAG#3) may also be advertised to the UE AS302.

[0146] Step 6. The UE AS302 may perform network slice-based cell reselection based on the selected NSAG (e.g., NSAG#3) received in step 5.

[0147] Step 7. When the network slice-based cell reselection is completed in step 6, the UE NAS301 sends a Registration Request message including S-NSSAI#3 in the Requested NSSAI and S-NSSAI#2 in the Withdrawing NSSAI to the AMF70. For example, if the UE3 has a Pending NSSAI including S-NSSAI#2 (or if the NSSAA procedure for S-NSSAI#2 is in progress), the UE NAS301 may send a Registration Request message including S-NSSAI#3 in the Requested NSSAI and S-NSSAI#2 in the Withdrawing NSSAI to the AMF70. For example, the UE NAS301 may perform one or more processes in step 7 to cancel the Pending NSSAI including S-NSSAI#2 (or release resources for the Pending NSSAI in the network) (e.g., the UE NAS301 may send a Withdrawing NSSAI including S-NSSAI#2).

[0148] For example, UE NAS301 may perform one or more processes in step 7 without waiting for the completion of the NSSAA procedure for S-NSSAI#2 (e.g., UE NAS301 may send a Withdrawing NSSAI including S-NSSAI#2).

[0149] For example, according to one or more current 3GPP standards, there is no way to indicate that a Pending NSSAI is canceled, even if the UE 3 (or a user of the UE 3) is no longer interested in the Pending NSSAI (e.g., the UE 3 is interested in another service on one or more S-NSSAIs that are different from the one or more S-NSSAIs in the Pending NSSAI).

[0150] Therefore, one or more resources maintained for a Pending NSSAI that the UE 3 is not interested in and the NSSAA procedures for the Pending NSSAI may be pointless or wasteful, resulting in inefficient network resource usage.

[0151] Also, consider the case where UE3 is interested in S-NSSAI#3 and is no longer interested in S-NSSAI#2 in the Pending NSSAI, and S-NSSAI#2 and S-NSSAI#3 do not share at least one common NSSRG value.

[0152] In this case, UE3 may not be able to send the Requested NSSAI containing S-NSSAI#3 even if UE3 is no longer interested in S-NSSAI#2 because S-NSSAI#2 and S-NSSAI#3 do not share at least one common NSSRG value (or because UE3 may not determine whether S-NSSAI#2 and S-NSSAI#3 share at least one common NSSRG value or may not determine the contents of the Requested NSSAI when S-NSSAI#2 is in the Pending NSSAI or before the NSSAA procedure for S-NSSAI#2 has successfully completed), thus causing a delay in service activation for all services that use S-NSSAI#3, which may result in unnecessary service degradation.

[0153] According to step 7 of this exemplary embodiment, UE NAS301 sends a Withdrawing NSSAI that includes S-NSSAI#2 to indicate the withdrawal of S-NSSAI#2 or a Pending NSSAI (or to indicate that UE3 is no longer interested in S-NSSAI#2 or a Pending NSSAI). In addition, UE NAS301 sends a Requested NSSAI that includes S-NSSAI#3.

[0154] For example, UE NAS301 may perform one or more processes of step 7 (e.g., UE NAS301 may send a Withdrawing NSSAI including S-NSSAI#2) without checking whether one or more S-NSSAIs in the Withdrawing NSSAI and one or more S-NSSAIs in the Requested NSSAI of step 7 share at least one common NSSRG value (e.g., without checking whether S-NSSAI#2 and S-NSSAI#3 share at least one common NSSRG value).

[0155] The Withdrawing NSSAI includes one or more S-NSSAIs that are in the Pending NSSAIs in UE storage but that the UE wants to remove from the Pending NSSAI. The Withdrawing NSSAI may also include one or more S-NSSAIs that are in the Pending NSSAIs in UE storage but that the UE is not interested in.

[0156] For example, UE3 may delete the Pending NSSAI after sending the Withdrawing NSSAI (or if UE3 has sent the Withdrawing NSSAI). For example, UE3 may abort the NSSAA procedure after sending the Withdrawing NSSAI (or if UE3 has sent the Withdrawing NSSAI). For example, UE3 may abort the NSSAA procedure for S-NSSAI#2 after sending the Withdrawing NSSAI (or if UE3 has sent the Withdrawing NSSAI). For example, if UE3 sends a Withdrawing NSSAI including S-NSSAI#2, UE3 may delete the Pending NSSAI including S-NSSAI#2 or delete S-NSSAI#2 from the Pending NSSAI. For example, UE NAS301 may send a Registration Request message including a Withdrawing NSSAI whenever UE NAS301 is able to send a Registration Request message. For example, the UE NAS 301 may send a Registration Request message including a Withdrawing NSSAI at any time. For example, the UE NAS 301 may send a Registration Request message including a Withdrawing NSSAI whenever the UE 3 has a Pending NSSAI.

[0157] When AMF70 receives a Registration Request message including a Withdrawing NSSAI, AMF70 aborts the NSSAA procedure for one or more S-NSSAIs set in the Withdrawing NSSAI.

[0158] For example, assume that the Withdrawing NSSAI includes S-NSSAI#2. In this case, AMF70 may abort the NSSAA procedure for S-NSSAI#2. For example, assume that AMF70 receives a Registration Request message including a Withdrawing NSSAI, and that the Withdrawing NSSAI includes S-NSSAI#2. In this case, AMF70 may abort the NSSAA procedure for S-NSSAI#2 if the NSSAA procedure for S-NSSAI#2 is in progress. In this case, AMF70 may abort the NSSAA procedure for S-NSSAI#2 if AMF70 determines that the NSSAA procedure for S-NSSAI#2 is in progress.

[0159] When AMF70 receives a Registration Request message including a Withdrawing NSSAI and the NSSAA procedure has been completed successfully for one or more S-NSSAIs set in the Withdrawing NSSAI, AMF70 removes one or more S-NSSAIs from the Allowed NSSAIs. For example, assume that the Withdrawing NSSAI includes S-NSSAI#2 and the NSSAA procedure has been completed successfully for S-NSSAI#2 (or that AMF70 receives a Withdrawing NSSAI that includes S-NSSAI#2 and the NSSAA procedure has been completed successfully for S-NSSAI#2 when the AMF receives the Withdrawing NSSAI). In this case, AMF70 may remove S-NSSAI#2 from the Allowed NSSAI in AMF70, or AMF70 may not add S-NSSAI#2 to the Allowed NSSAI in AMF70. For example, AMF70 may send the Allowed NSSAI to UE3 without S-NSSAI#2, and UE3 may update the Allowed NSSAI in UE3 based on the Allowed NSSAI received without S-NSSAI#2.

[0160] If AMF70 receives a Registration Request message including a Withdrawing NSSAI and the NSSAA procedure is completed unsuccessfully for one or more S-NSSAIs set in the Withdrawing NSSAI, AMF70 retains one or more S-NSSAIs in the Rejected NSSAIs (for example, AMF70 may include one or more S-NSSAIs in the Rejected NSSAIs, or move one or more S-NSSAIs from Pending NSSAIs to Rejected NSSAIs), or maintains the status of the NSSAA procedure for the Withdrawing NSSAI. For example, AMF70 may send the Rejected NSSAI to UE3. For example, assume that the Withdrawing NSSAI includes S-NSSAI#2 and the NSSAA procedure for S-NSSAI#2 fails. In this case, AMF70 may either retain S-NSSAI#2 as a Rejected NSSAI or maintain the status of the NSSAA procedure for the Withdrawing NSSAI (e.g., AMF70 may retain information indicating that the NSSAA procedure for S-NSSAI#2 failed as a status).

[0161] The UE 3 does not consider one or more S-NSSAIs in the Withdrawing NSSAI for the NSSRG procedure, i.e., the UE 3 does not check whether one or more S-NSSAIs in the Withdrawing NSSAI share at least one common NSSRG value (or at least one common NSSRG group) with one or more S-NSSAIs in the Requested NSSAI in the Registration Request message. The UE 3 may check whether one or more S-NSSAIs in the Withdrawing NSSAI share at least one common NSSRG value with one or more S-NSSAIs in the Requested NSSAI in the Registration Request message.

[0162] Note that the Withdrawing NSSAI may be expressed in other ways. For example, the Withdrawing NSSAI may be expressed as an abandon NSSAI, an Abandoning NSSAI, an Unrequested NSSAI, or any other notation of an NSSAI that is part of a Pending NSSAI but includes one or more S-NSSAIs that the UE 3 is no longer interested in. For example, the Withdrawing NSSAI may be expressed as any other notation of an NSSAI that includes one or more S-NSSAIs that are not added to the Allowed NSSAIs for the UE 3 after the NSSAA procedure is successful for one or more S-NSSAIs.

[0163] Step 8. The AMF 70 sends a Registration Accept message to the UE NAS 301, including the Configured NSSAI, Allowed NSSAI, Pending NSSAI and NSAG priority. The Configured NSSAIs include S-NSSAI#1 with associated NSAG#1, S-NSSAI#2 with associated NSAG#2, and S-NSSAI#3 with associated NSAG#3.

[0164] Here, the NSAG information in the Registration Accept message may include the relationship between the S-NSSAI and the NSAG (i.e., S-NSSAI#1 with associated NSAG#1, S-NSSAI#2 with associated NSAG#2, and S-NSSAI#3 with associated NSAG#3).

[0165] Allowed NSSAIs include S-NSSAI#3.

[0166] The NSAG priority indicates the priority between NSAGs.

[0167] After the successful registration procedure according to step 7 and step 8, UE3 may only have S-NSSAI#3 in the Allowed NSSAI in the storage of UE3.

[0168] For example, when UE3 receives a Registration Accept message, UE3 may delete the Pending NSSAI. For example, when UE3 receives a Registration Accept message, UE3 may delete the Pending NSSAI that includes S-NSSAI#2, or may delete S-NSSAI#2 from the Pending NSSAI.

[0169] For example, AMF 70 may send a request to delete a Pending NSSAI or a request to delete one or more S-NSSAIs included in a Withdrawing NSSAI from the Pending NSSAI. For example, AMF 70 may send a request when it receives a Withdrawing NSSAI from UE 3. The request may be included in a Registration Accept message or any other NAS message. When UE 3 receives a request to delete a Pending NSSAI that includes S-NSSAI#2 or a request to delete S-NSSAI#2 from a Pending NSSAI, UE 3 may delete the Pending NSSAI or may delete S-NSSAI#2 from the Pending NSSAI.

[0170] When the AMF 70 applies the NSSRG procedure to the Allowed NSSAI, the AMF 70 does not check one or more S-NSSAIs in the Withdrawing NSSAI. That is, the AMF 70 does not check whether one or more S-NSSAIs in the Withdrawing NSSAI share at least one common NSSRG group (or at least one common NSSRG value) with one or more S-NSSAIs in the Allowed NSSAI. For example, the AMF 70 may not consider the NSSRG values ​​of one or more S-NSSAIs in the Withdrawing NSSAI to determine the contents of the Allowed NSSAI (that is, one or more S-NSSAIs in the Allowed NSSAIs of the Registration Request message in step 8 and one or more S-NSSAIs in the Withdrawing NSSAI may or may not share at least one common NSSRG value).

[0171] If AMF70 successfully increases the UE count by performing a NumOfUEsUpdate service operation for one or more S-NSSAIs in the Withdrawing NSSAI (for example, if AMF70 successfully increases the UE count by performing a NumOfUEsUpdate service operation for S-NSSAI#2), AMF70 may initiate a NumOfUEsUpdate service operation for each of one or more S-NSSAIs in the Withdrawing NSSAI to decrease the UE count in the NSACF (for example, AMF70 may initiate a NumOfUEsUpdate service operation for S-NSSAI#2 to decrease the UE count in the NSACF).

[0172] Variation 1 of the first example of the second exemplary embodiment: In one example, the Withdrawing NSSAI can be sent from the UE 3 to the AMF 70 by another NAS message, such as a Registration complete message, an Identity Response message, an Authentication response message, a UL NAS TRANSPORT message, a De-registration request message, a Configuration update complete message, a Network slice-specific authentication complete message, or other existing NAS message, or a new NAS message defined for canceling a Pending NSSAI. In this case, the AMF 70 sends a response by any existing NAS message or a new NAS message. For example, the UE NAS 301 may send the above message including the Withdrawing NSSAI whenever the UE NAS 301 is able to send the above message. For example, the UE NAS 301 may send the above message including the Withdrawing NSSAI at any time. For example, the UE NAS 301 may send the above message including the Withdrawing NSSAI whenever the UE 3 has a Pending NSSAI.

[0173] Variation 2 of the first example of the second exemplary embodiment: In another example, in step 7, instead of indicating in Withdrawing NSSAI one or more S-NSSAIs from Pending NSSAIs that UE 3 is no longer interested in, UE 3 may use, in the NAS message to AMF 70, for example, a new parameter called "pending off," or any other representation of the parameter, to indicate that UE 3 is no longer interested in one or more S-NSSAIs from Pending NSSAIs, so that AMF 70 will not include the S-NSSAIs in the Allowed NSSAIs for the UE if the NSSAA procedure for the one or more S-NSSAIs is successful. This use case is applicable when UE 3 is no longer interested in all of one or more S-NSSAIs from Pending NSSAIs. Therefore, in such a case, UE 3 may use a single flag in the NAS message to AMF 70 instead of listing all of one or more S-NSSAIs from Pending NSSAIs in Withdrawing NSSAI.

[0174] For example, if AMF 70 receives a “pending off” parameter, AMF 70 may perform one or more processes that are the same as step 7.

[0175] For example, if AMF70 receives a "Pending Off" parameter, AMF70 may abort the NSSAA procedure for at least one of one or more S-NSSAIs in the Pending NSSAI.

[0176] For example, if AMF70 receives a "Pending Off" parameter and the NSSAA procedure is completed successfully for one or more S-NSSAIs in the Pending NSSAI, AMF70 may remove one or more S-NSSAIs from the Allowed NSSAIs.

[0177] For example, if AMF70 receives a "pending off" parameter and the NSSAA procedure fails for one or more S-NSSAIs in the Pending NSSAI, AMF70 may retain one or more S-NSSAIs in the Rejected NSSAIs (e.g., AMF70 may include one or more S-NSSAIs in the Rejected NSSAIs, or move one or more S-NSSAIs from Pending NSSAIs to Rejected NSSAIs), or may maintain the status of the NSSAA procedure for one or more S-NSSAIs.

[0178] Variation 3 of the first example of the second exemplary embodiment: In one example, during an existing NAS procedure, the AMF 70 sends an indicator in an existing NAS message or a new NAS message (e.g., in a Registration Accept message during the initial registration procedure or the periodic and mobility registration procedures) to the UE 3 indicating whether the NSSRG procedure is applicable to the Pending NSSAI. If the indicator indicates that the NSSRG procedure is not applicable to one or more S-NSSAIs in the Pending NSSAI, the UE NAS 301 does not check whether one or more S-NSSAIs in the Pending NSSAI share a common NSSRG value with one or more S-NSSAIs in the Requested NSSAI or Allowed NSSAI, i.e., does not check whether the NSSRG procedure applies to one or more S-NSSAIs in the Pending NSSAI and one or more S-NSSAIs in the Requested NSSAI or Allowed NSSAI. If the indicator indicates that the NSSRG procedure is applicable to the Pending NSSAI, the UE NAS 301 also applies the NSSRG procedure to one or more S-NSSAIs of the Pending NSSAI, i.e., the UE 3 checks whether one or more S-NSSAIs in the Requested or Allowed NSSAIs and one or more S-NSSAIs in the Pending NSSAI share at least one common NSSRG value. The indicator may indicate that the NSSRG procedure is applicable to each S-NSSAI in the Pending NSSAI.

[0179] If the indicator indicates that the NSSRG procedure is not applicable to S-NSSAI#2 in the Pending NSSAI, UE NAS301 may not check whether S-NSSAI#2 and one or more S-NSSAIs in the Requested NSSAI or Allowed NSSAI share at least one common NSSRG value.

[0180] For example, in this case, UE NAS301 may include S-NSSAI#2 and one or more S-NSSAIs from the Requested NSSAI or the Allowed NSSAI in any NAS message, even if S-NSSAI#2 and one or more S-NSSAIs from the Requested NSSAI or the Allowed NSSAI do not share at least one common NSSRG value.

[0181] The Withdrawing NSSAI may include at least one of one or more S-NSSAIs of the Pending NSSAI.

[0182] Also, if the indicator indicates that the NSSRG procedure is not applicable to S-NSSAI#2 in the Pending NSSAI and UE NAS301 wants to include S-NSSAI#2 in the Withdrawing NSSAI (e.g., UE3 is no longer interested in S-NSSAI#2 in the Pending NSSAI), UE NAS301 may not check whether S-NSSAI#2 and one or more S-NSSAIs in the Requested NSSAI or Allowed NSSAI share at least one common NSSRG value.

[0183] Therefore, if the indicator indicates that the NSSRG procedure is not applicable to S-NSSAI#2 in the Pending NSSAI, in step 7, UE NAS301 may send a Registration Request message including a Requested NSSAI including S-NSSAI#3 and a Withdrawing NSSAI including S-NSSAI#2, even if S-NSSAI#2 and S-NSSAI#3 do not share at least one common NSSRG value.

[0184] Variation 4 of the first example of the second exemplary embodiment: In step 2 or 8, if one or more neighboring TAs configure one or more NSAGs for one or more S-NSSAIs in the Configured NSSAI for each one or more TAs, the AMF 70 may include in the Registration Accept message a combination of one or more NSAGs (e.g., one or more NSAGs associated with one or more neighboring TAs) and a TAC of one or more neighboring TAs located outside the current RA. For example, the AMF 70 may include in the Registration Accept message or any NAS message one or more combinations of one or more TACs of one or more neighboring TAs located outside the current RA and one or more NSAGs associated with one or more neighboring TAs. The AMF 70 may transmit the Registration Accept message or any NAS message to the UE NAS 301. The one or more combinations may be expressed as NSAG information of one or more neighboring TAs, or NSAG information of one or more neighboring TAs outside the current RA, or NSAG information for one or more TAs that are not within the RA but are located near the RA. The AMF 70 may obtain one or more combinations from another network node (e.g., another AMF). The AMF 70 may store one or more combinations. The AMF 70 may determine one or more combinations based on local configuration or operator policy. The NSAG information of one or more nearby TAs may include NSAG priorities associated with one or more NSAGs associated with the one or more nearby TAs. That is, AMF70 may include NSAG information (e.g., one or more NSAGs) of one or more TAs that are not within the RA but are located near the RA in the Registration Accept message, and the one or more NSAGs may be associated with one or more TAs. The NSAG information of one or more nearby TAs outside the current RA is used by UE3 to select or reselect a cell based on a network slice-based cell reselection function when UE3 moves from the RA. For example, UE NAS301 may send the NSAG information of one or more nearby TAs to UE AS302, and UE AS302 may select or reselect a cell based on the network slice-based cell reselection function using the NSAG information of one or more nearby TAs.

[0185] If the UE 3 is moving from the current RA and the UE 3 (e.g., UE AS 302) is able to scan for one or more candidate cells that transmit or broadcast one or more NSAGs and associated TACs via a SIB (e.g., SIB16) and / or dedicated signaling, the UE AS 302 may check whether the broadcasted NSAGs and associated TACs match one or more NSAGs and NSAG priorities provided by the UE NAS 301. If at least one of the one or more NSAGs and NSAG priorities matches, the UE 3 may tune to that cell (e.g., the UE AS 302 may select or reselect that cell) and initiate a registration procedure (e.g., the UE NAS 301 may initiate a registration procedure in that cell).

[0186] For example, the UE 3 may determine that the UE 3 can scan for one or more candidate cells that transmit or broadcast one or more NSAGs and associated TACs based on the NSAG information of one or more nearby TAs. For example, the UE 3 may scan for one or more candidate cells that transmit or broadcast one or more NSAGs and one or more TACs indicated by the NSAG information of one or more nearby TAs.

[0187] If the NSAG and NSAG priorities do not match, the UE 3 selects a cell based on the existing cell selection mechanism and initiates the registration procedure.

[0188] The above-described modifications can be applied to the first exemplary embodiment.

[0189] According to the first example of the exemplary second aspect and the modified example of the first example of the exemplary second aspect, it is possible to solve the above-mentioned problems.

[0190] For example, the first example of the exemplary first aspect and the variant of the first example of the exemplary first aspect can solve the problem of one or more situations that are unclear in the current 3GPP specifications.

[0191] For example, the first example of the exemplary second aspect and a variant example of the first example of the exemplary second aspect can solve the problem of there being one or more unclear situations regarding cell reselection functions based on network slices, NSAG, etc.

[0192] For example, the first example of the exemplary second aspect and a variant of the first example of the exemplary second aspect can solve the problem that an NSSAA procedure for one or more S-NSSAIs of Pending NSSAIs that the UE is no longer interested in may be meaningless.

[0193] For example, the first example of the exemplary second aspect and the variant of the first example of the exemplary second aspect can solve the problem that NSSAA procedures for one or more S-NSSAIs of Pending NSSAIs that the UE is no longer interested in may cause a load on the network.

[0194] For example, the first example of the exemplary second aspect and a variant of the first example of the exemplary second aspect can solve a problem that an NSSAA procedure for one or more S-NSSAIs of a Pending NSSAI that the UE is no longer interested in may cause inefficient network resource usage. For example, the first example of the exemplary second aspect and a variant of the first example of the exemplary second aspect can solve a problem that network resources for one or more S-NSSAIs of a Pending NSSAI may be unnecessarily maintained in the network without being used.

[0195] For example, the first example of the second exemplary aspect and the variant of the first example of the second exemplary aspect can solve the problem of potentially causing delays in service activation and potentially causing unnecessary service degradation for all services that use the new set of one or more S-NSSAIs.

[0196] For example, the first example of the second exemplary aspect and the variant example of the first example of the second exemplary aspect can solve the problem that when a UE crosses an RA boundary, the UE cannot select a cell suitable for one or more S-NSSAIs in the Allowed NSSAI based on a cell reselection function based on a network slice, which may cause unnecessary service termination for all services that use one or more S-NSSAIs in the Allowed NSSAI.

[0197] System Overview FIG. 4 illustrates schematically a mobile (cellular or wireless) telecommunications system 1 to which the above exemplary aspects are applicable.

[0198] The telecommunications system 1 represents a system overview capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices", 3) communicating with other UEs 3 or service servers in a data network 20 via respective (R)AN nodes 5 and a core network 7.

[0199] The (R)AN node 5 supports any radio access, including 5G radio access technology (RAT), E-UTRA radio access technology, beyond 5G RAT, 6G RAT, and non-3GPP RAT, including wireless local area network (WLAN) technology defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0200] The (R)AN node 5 can be divided into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some example aspects, each of the units are connected to each other, and the (R)AN node 5 can be constructed by adopting an architecture defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.

[0201] The (R)AN node 5 may be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions may be allocated to support communications. In some example aspects, user traffic may be distributed across multiple user plane functions, with user traffic on each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This divided architecture is sometimes referred to as "dual connectivity" or "multi-connectivity."

[0202] The (R)AN node 5 may also support communications using satellite access. In some exemplary aspects, the (R)AN node 5 may support satellite access and terrestrial access.

[0203] The (R)AN node 5 can also be considered an access node for non-wireless access, which includes fixed-line access defined by the Broadband Forum (BBF) and optical access defined by the Innovative Optical and Wireless Network (IOWN).

[0204] The core network 7 may include logical nodes (or "functions") for supporting communications in the telecommunications system 1. For example, the core network 7 may be a 5GC that includes control plane functions and user plane functions, among other functions. Each function within a logical node may be considered a network function. A network function may be provided to another node by adapting an SBA.

[0205] By adapting network virtualization techniques defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed in a distributed, redundant, stateless, and scalable manner, providing services from several locations and several running instances of each location. The core network 7 can support an NPN, which can be an SNPN or a Public Network Integrated NPN (PNI-NPN).

[0206] As is known, a UE 3 may move in and out of areas (i.e., radio cells) served by an (R)AN node 5 as the UE 3 moves within the geographic area covered by the telecommunications system 1. To track the UE 3 and facilitate movement between different (R)AN nodes 5, the core network 7 includes at least one AMF 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0207] The core network 7 also includes, among other things, an SMF 71, a UPF 72, a PCF 73, an AUSF 74, a UDM 75, and an NSSF 76. When a UE 3 is roaming in a visited PLMN (VPLMN), the home PLMN (HPLMN) of the UE 3 provides the roaming UE 3 with the UDM 75, and at least some of the functionality of the SMF 71, UPF 72, and PCF 73.

[0208] The UE 3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface, etc.). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5 and (R)AN node interfaces (e.g., a so-called "Xn" interface, etc.). Each (R)AN node 5 is also connected to nodes within the core network 7 (e.g., so-called core network nodes) via appropriate interfaces (e.g., one or more so-called "N2" / "N3" interfaces, etc.). The core network 7 also provides connectivity to a data network 20. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. In cases where the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by the data network 20. The UE 3 may connect to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types. The data network may include an AAA 201.

[0209] The "Uu" interface may include the control plane of the Uu interface and the user plane of the Uu interface.

[0210] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection.

[0211] The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a layered structure with RRC, PDCP, RLC, and MAC sublayers over the physical connection.

[0212] For example, the following messages are communicated over the RRC layer to support AS signaling: RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the RRC Setup Request message: -establishmentCause and ue-Identity ue-Identity may have the value ng-5G-S-TMSI-Part1 or randomValue. RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the RRC Setup message: -masterCellGroup and radioBearerConfig RRC setup complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the RRC setup complete message: -guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0213] The UE 3 and the AMF 70 are connected via an appropriate interface (such as the so-called N1 interface). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface can be established via 3GPP access and non-3GPP access. For example, the following messages are communicated via the N1 interface: -registration request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the registration request message: -5GS registration type, ngKSI, 5GS mobile identity, non-current native NAS key set identifier, 5GMM capabilities, UE security capabilities, Requested NSSAI, last visited registered TAI, S1 UE network capabilities, uplink data status, PDU session status, MICO indication, UE status, additional GUTI, allowed PDU session status, UE usage configuration, requested DRX parameters, EPS NAS message container, LADN indication, payload container type, payload container, network slicing indication, 5GS update type, mobile station class mark 2, supported codecs, NAS message container, EPS bearer context status, requested extended DRX parameters, T3324 value, UE radio capability ID, requested mapped NSSAI, requested information, requested WUS support information, N5GC indication, and requested NB-N1 mode DRX parameters. Registration accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the registration accept message: -5GS Registration Result, 5G-GUTI, Equivalent PLMN, TAI List, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS Network Capability Support, PDU Session Status, PDU Session Reactivation Result, PDU Session Reactivation Result Error Cause, LADN Information, MICO Indication, Network Slicing Indication, Service Area List, T3512 Value, Non-3GPP Registration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Inclusion Mode, Operator Defined Access Category Definition, Negotiate DRX Parameters, Non-3GPP NW Policy, EPS Bearer Context Status, Negotiate Extended DRX Parameters, T3447 Value, T3448 Value, T3324 Value, UE Radio Capability ID, UE Radio Capability ID Removal Indication, Pending NSSAI, encryption key data, CAG information list, truncated 5G-S-TMSI configuration, negotiated WUS support information, negotiated NB-N1 mode DRX parameters, and extended rejected NSSAI. Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the Registration Complete message: -SOR transparent container Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be included together in the Authentication Request message: -ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge), and EAP message. Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be entered together in the Authentication Response message: -Authentication Response message identification information, Authentication Response parameters, and EAP message. Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be entered together in the Authentication Result message: -ngKSI, EAP Message and ABBA. Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be input together in the Authentication Failure message: -Authentication Failure message identification information, 5GMM cause and Authentication Failure parameters. Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be input together in the Authentication Reject message: -EAP messages Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be input together in the Service Request message: -ngKSI, Service Type, 5G-S-TMSI, Uplink Data Status, PDU Session Status, Allowed PDU Session Status, NAS Message Container. Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be entered together in the Service Accept message: -PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be input together into the Service Reject message: -5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list. -Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be entered together in the Configuration Update Command message: -Configuration update instruction, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Network full name, Network short name, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO instruction, Network slicing instruction, Configured NSSAI, Rejected NSSAI, Operator-defined access category definition, SMS instruction, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion instruction, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration instruction and Extended rejected NSSAI. -Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the exemplary aspects of the present disclosure, the following parameters may be taken together in the Configuration Update Complete message: -Configuration Update Complete message identification information

[0214] User Equipment (UE) FIG. 5 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit and receive signals to and from one or more connected nodes via one or more antennas 32. The UE 3 may further include a user interface 34 for inputting and outputting information from and to an external device. Although not necessarily shown in the figure, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as needed. The software may be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 in accordance with software stored in the memory 36. The software includes, among other things, an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3). The controller 33 interoperates with one or more Universal Subscriber Identity Modules (USIMs) 35. If multiple USIMs 35 are installed, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0215] The UE 3 may, for example, support NPN, and the NPN may be SNPN or PNI-NPN.

[0216] UE3 may be, for example, an item of production or manufacturing equipment and / or energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power plants, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or application systems thereof, tools, dies or molds, rolls, conveying equipment, elevators, material handling equipment, textile machinery, sewing equipment, printing and / or related machinery, paper converting equipment, chemical machinery, mining machinery and / or construction machinery and / or related equipment, machinery and / or implements for agriculture, forestry and / or fisheries, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the foregoing equipment or machinery, etc.).

[0217] UE3 may be, for example, an item of transportation equipment (e.g., transportation equipment such as rolled materials, automobiles, motorcycles, bicycles, trains, buses, carts, human-powered vehicles, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).

[0218] The UE 3 may be, for example, an item of information and communications equipment (eg, information and communications equipment such as electronic computers and related equipment, communications and related equipment, electronic components, etc.).

[0219] The UE3 may be, for example, a refrigerator, a refrigerator application product, an item of goods and / or service industry equipment, a vending machine, an automated service machine, an office machine or device, a consumer electronic device and an electronic device (e.g., a consumer electronic device such as an audio device, a video device, a speaker, a radio, a television, a microwave oven, a rice cooker, a coffee machine, a dishwasher, a washing machine, a dryer, an electronic fan or related device, a vacuum cleaner, etc.).

[0220] The UE 3 may be, for example, an electrical application system or device (eg, an X-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, an electronic power application device, or the like).

[0221] UE3 may be, for example, an electronic lamp, lighting fixture, measuring equipment, analyzer, tester, or surveying or sensing equipment (e.g., surveying or sensing equipment such as a smoke alarm, a motion sensor, a radio frequency tag, etc.), a watch or clock, inspection equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, etc.

[0222] UE 3 may be, for example, a wirelessly equipped personal digital assistant or related equipment (eg, a wireless card or module designed to be attached to or inserted into another electronic device (eg, a personal computer, electrical measuring instrument)).

[0223] The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below in relation to the "internet of things (IoT)."

[0224] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable these devices to collect and exchange data with each other and with other communicating devices. IoT devices may comprise automated machines that follow software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or inactive for long periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be embedded in non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0225] It will be appreciated that IoT technologies may be implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory.

[0226] It will be appreciated that an IoT device may also be referred to as a Machine-Type Communication (MTC) device, a Machine-to-Machine (M2M) communication device, or a Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0227] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).

[0228] The UE3 may be a car, a connected car, an autonomous car, a vehicle device, a motorcycle, or a V2X (Vehicle to Everything) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-person communication module, and a vehicle-to-network communication module).

[0229] (R)AN Node FIG. 6 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, 5G beyond base station, 6G base station). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from one or more connected UEs 3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 in accordance with software stored in memory 55. The software may be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0230] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling (e.g., directly or indirectly) between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72. The signaling may include, for example, appropriately formatted signaling messages related to the radio connection and connectivity with the core network 7 (for a particular UE 3), in particular related to connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages over the N2 reference point) and Xn application protocol (XnAP) messages (i.e., messages over the Xn reference point), etc. Such signaling may also include, for example, broadcast information (e.g., master information and system information) when transmitting.

[0231] When implemented, the controller 54 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0232] The (R)AN node 5 may support NPN, which may be an SNPN or a PNI-NPN.

[0233] The current RAN 501 and the candidate RAN 502 may have the same components as the (R)AN node 5. The (R)AN node 5 may also be referred to as a RAN node, a RAN, an (R)AN, etc.

[0234] System overview of (R)AN Node 5 based on O-RAN architecture FIG. 7 illustrates schematically an (R)AN node 5 based on an O-RAN architecture to which aspects of the (R)AN node 5 are applicable.

[0235] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is divided into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Central Unit (CU) 62. In some exemplary aspects, each unit can be combined. For example, the RU 60 may be combined with the DU 61 as a combined / combined unit, and the DU 61 may be combined with the CU 62 as another combined / combined unit. Any functionality described in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the combined / combined unit. Furthermore, the CU 62 can be separated into two functional units, such as a CU Control Plane (CP) and a CU User Plane (UP). The CU CP has the control plane function in the (R)AN node 5. The CU UP has the user plane function in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface “E1.”

[0236] The UE 3 and each serving RU 60 are connected via an appropriate air interface "Uu". Each RU 60 is connected to a DU 61 via an appropriate interface (e.g., a so-called "fronthaul", "open fronthaul", "F1" interface, etc.). Each DU 61 is connected to a CU 62 via an appropriate interface (e.g., a so-called "midhaul", "open midhaul", "E2" interface, etc.). Each CU 62 is also connected to a node in the core network 7 (e.g., a so-called core network node) via an appropriate interface (e.g., a so-called "backhaul", "open backhaul", one or more "N2" / "N3" interfaces, etc.). Furthermore, the user plane part of the DU 61 may also be connected to the core network node 7 via an appropriate interface or interfaces "N3".

[0237] Depending on the functionality divided among the RU 60, DU 61, and CU 62, each unit provides a portion of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality for supporting the MAC and RLC layers, and the CU 62 may provide functionality for supporting the PDCP, SDAP, and RRC layers.

[0238] Radio Unit (RU) FIG. 8 is a block diagram illustrating the main components of an exemplary RU 60, e.g., the RU portion of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a 5G beyond base station, or a 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from one or more connected UEs 3 via one or more antennas 602 and to transmit and receive signals to and from other network nodes or units (directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 according to software stored in memory 605. The software may be pre-installed in the memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0239] The communication control module 6052 is responsible for handling (e.g., directly or indirectly) signaling between the RU 60 and other nodes or units, such as the UE 3, other RUs 60, and the DU 61. The signaling may include, for example, appropriately formatted signaling messages relating to the radio connection and connectivity with the RU 60 (for a particular UE 3), in particular the MAC and RLC layers.

[0240] When implemented, the controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.

[0241] The RU 60 may support an NPN, which may be a Stand-alone Non-Public (SNPN) or a PNI-NPN.

[0242] As mentioned above, the RU 60 may be integrated / combined with the DU 61 as an integrated / combined unit, and any function described for the RU 60 may be implemented in the integrated / combined unit.

[0243] Distribution Unit (DU) FIG. 9 is a block diagram illustrating the main components of an exemplary DU 61, e.g., a DU section of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a 5G beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in memory 614. The software may be pre-installed in memory 614 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0244] The DU 61 may support NPN, and the NPN may be SNPN or PNI-NPN.

[0245] As mentioned above, the RU 60 may be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any function in the description of the DU 61 may be implemented in one of the above integrated / combined units.

[0246] Central Unit (CU) FIG. 10 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU portion of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a 5G beyond base station, or a 6G base station). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in memory 624. The software may be pre-installed in memory 624 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0247] The CU 62 may support NPN, which may be SNPN or PNI-NPN.

[0248] As mentioned above, the CU 62 may be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description of the CU 62 may be implemented in the integrated / combined unit.

[0249] AMF 11 is a block diagram illustrating the main components of the AMF 70. As shown, the device includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including UE 3, NSSF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in memory 704. The software may be pre-installed in memory 704 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for processing (generating / sending / receiving) signaling between the AMF 70 and other nodes, such as the UE 3 (e.g., via (R)AN node 5) and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3).

[0250] The AMF 70 may support NPN, which may be SNPN or PNI-NPN. The AMF 7001 and AMF 7002 may have the same components as the AMF 70.

[0251] PCF 12 is a block diagram illustrating the major components of the PCF 73. As shown, the device includes a transceiver circuit 731 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in memory 734. The software may be pre-installed in the memory 734 and / or may be downloaded, for example, over a telecommunications network or from a removable data storage device (e.g., a removable data storage device (RMD)). The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP convenience methods based on service-based interfaces) related to policy management procedures (for the UE 3).

[0252] The PCF73 may support NPN, which may be SNPN or PNI-NPN. The PCF7301 and PCF7302 may have the same components as the PCF73.

[0253] AUSF 13 is a block diagram illustrating the major components of the AUSF 74. As shown, the device includes a transceiver circuit 741 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the AUSF 74 in accordance with software stored in memory 744. The software may be pre-installed in memory 744 and / or may be downloaded, for example, over a telecommunications network or from a removable data storage device (e.g., a removable data storage device (RMD)). The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the AUSF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP convenience methods based on service-based interfaces) related to policy management procedures (for the UE 3).

[0254] The AUSF74 may support NPN, which may be SNPN or PNI-NPN.

[0255] UDM FIG. 14 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in memory 754. The software may be pre-installed in the memory 754 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for processing (generating / sending / receiving) signaling between the UDM 75 and other nodes, for example, the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to mobility management procedures (for example, HTTP convenience methods based on service-based interfaces).

[0256] The UDM 75 may support NPN, which may be SNPN or PNI-NPN.

[0257] NSSF 15 is a block diagram illustrating the main components of the NSSF 76. As shown, the device includes a transceiver circuit 761 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with software stored in a memory 764. The software may be pre-installed in the memory 764 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for processing (generating / sending / receiving) signaling between the NSSF 76 and other nodes, for example, the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages (for UE 3) related to mobility management procedures (for example, HTTP convenience methods based on service-based interfaces).

[0258] The NSSF 76 may support an NPN, which may be an SNPN or a PNI-NPN.

[0259] The exemplary aspects disclosed above may be described in whole or in part as follows, but are not limited thereto.

[0260] 5.3.4.3.4 Cell reselection based on network slices When one or more S-NSSAIs are associated with one or more NSAGs, the UE can perform network slice-based cell reselection as described in TS38.300

[27] , TS38.304

[50] , TS38.331

[28] , and TS24.501

[47] .

[0261] When providing NSAG information to a UE, the AMF must also provide NSAG priority information for the NSAGs provided in the NSAG information. The AMF determines the NSAG priority information based on the operator's policy. If the UE receives NSAG priority information from the AMF, the UE shall use the NSAG priority information provided by the AMF for cell reselection, as described below. If the UE does not receive any NSAG priority information from the AMF, the UE shall not use network slice-based cell reselection at all.

[0262] The UE NAS provides the NSAGs and their priorities received from the AMF for the Allowed NSSAIs and S-NSSAIs in the Pending NSSAI for 3GPP access to the UE AS as inputs to cell reselection. If the UE NAS provides the NSAGs and their priorities for one or more S-NSSAIs from the Pending NSSAIs and one or more S-NSSAIs from the Pending NSSAIs to the UE AS but one or more S-NSSAIs are rejected, the UE NAS updates the UE AS again with the NSAGs and their priorities for only the Allowed NSSAIs. This does not apply if the UE intends to register with a new set of S-NSSAIs with a Requested NSSAI that is different from the current Allowed NSSAIs. In this case, the UE NAS provides the NSAGs and their priorities received from the AMF for the S-NSSAIs in the Requested NSSAI and the Pending NSSAI for 3GPP access, if stored in the UE, to the UE AS layer, which can trigger cell reselection before sending a Registration Request including the new Requested NSSAI.

[0263] Note: How the UE NAS provides the NSAG priority to the UE AS is based on the internal UE interface and is not specified.

[0264] 4.6 Network Slicing 4.6.1 General 5GS supports network slicing as described in 3GPP TS 23.501 [8]. Within a PLMN or SNPN, a network slice is identified by an S-NSSAI, which consists of a slice / service type (SST) and a slice differentiator (SD). The inclusion of the SD in the S-NSSAI is optional. A set of one or more S-NSSAIs is called an NSSAI. The following NSSAIs are defined in 3GPP TS 23.501 [8]: a) configured NSSAI b) Requested NSSAI c) allowed NSSAI d) Subscribed S-NSSAIs e) pending NSSAI, and f) abandon NSSAI

[0265] The following NSSAIs are defined in this document: a) Rejected NSSAI of the current PLMN or SNPN b) Rejected NSSAI in the current registration area c) rejected NSSAIs that have failed or expired; and d) Maximum number of rejected NSSAIs reached by UE

[0266] In a roaming scenario, the rejected NSSAI of the current PLMN or SNPN, or the rejected NSSAI of the current registration area, or the rejected NSSAI of the maximum number of UEs reached, includes one or more S-NSSAIs of the current PLMN and, if available, a set of one or more mapped S-NSSAIs. The S-NSSAI included in the rejected NSSAI of the failed or expired NSSAI is the HPLMN S-NSSAI.

[0267] In the case of a PLMN, the serving PLMN may configure the UE with a configured NSSAI for each PLMN and with NSSRG information if the UE indicates that it supports subscription-based restrictions on concurrent registration of network slice capabilities. In addition, the HPLMN may configure the UE with a single default configured NSSAI and consider the default configured NSSAI valid in PLMNs where the UE has neither a configured NSSAI nor an allowed NSSAI.

[0268] NOTE 1: It is expected that the value or values ​​used in the default configured NSSAI will typically be determined by all roaming partners, e.g., values ​​standardized by 3GPP or other organizations. In the case of an SNPN, the SNPN may configure the UE with the configured NSSAI applicable to the SNPN and, if the UE is not registering or has registered for onboarding services in the SNPN, with the NSSRG information if the UE indicates that it supports subscription-based restrictions on concurrent registrations of network slicing functions. In addition, the credential holder may configure a single default configured NSSAI associated with a selected entry in the "Subscriber Data List" or PLMN subscription, and consider that default configured NSSAI to be valid in SNPNs where the UE has neither a configured NSSAI nor an allowed NSSAI. If the UE is registering or has registered for onboarding services in the SNPN, the serving SNPN shall not provide the configured NSSAI to the UE.

[0269] The allowed NSSAIs and rejected NSSAIs of the current registration area are managed independently for each access type, i.e., for 3GPP access or non-3GPP access, and are applicable to the registration area. If the UE does not have a valid registration area, the rejected NSSAIs of the current registration area are applicable to the tracking area from which they are received. If a registration area contains TAIs belonging to different PLMNs that are equivalent PLMNs, the allowed NSSAIs and rejected NSSAIs of the current registration area are applicable to these PLMNs within this registration area.

[0270] An allowed NSSAI associated with a registration area that contains a TAI belonging to a different PLMN that is an equivalent PLMN may be used to form a Requested NSSAI for any of the equivalent PLMNs when the UE is outside the registration area in which it received the allowed NSSAI.

[0271] If a network slice-specific authentication and authorization procedure is initiated for one or more S-NSSAIs in the Requested NSSAI, or if a network slice-specific authentication and authorization procedure is ongoing for one or more S-NSSAIs, these one or more S-NSSAIs are included in the Pending NSSAI. When the network slice-specific authentication and authorization procedure is completed for an S-NSSAI that was in the Pending NSSAI, the S-NSSAI is moved to an allowed NSSAI or a rejected NSSAI depending on the result of the procedure. The AMF sends the updated allowed NSSAI to the UE via the same access as the requested S-NSSAI. The AMF sends the updated rejected NSSAI via either 3GPP access or non-3GPP access. The Pending NSSAI is managed regardless of the access type. That is, the Pending NSSAI is applicable to both 3GPP and non-3GPP accesses of the current PLMN, even if it is sent via only one of the accesses. If a registration area includes TAIs belonging to different PLMNs that are equivalent PLMNs, the Pending NSSAI is applicable to these PLMNs within this registration area. If the UE is no longer interested in an S-NSSAI in the pending NSSAI, the UE initiates a mobility registration procedure, and in a registration request message, the UE sends an abandon NSSAI that includes one or more pending S-NSSAIs that the UE is no longer interested in.

[0272] A rejected NSSAI for the current PLMN or SNPN is applicable to the entire registered PLMN or SNPN. The AMF shall send a rejected NSSAI for the current PLMN only if the registration area consists of TAIs belonging only to the registered PLMN. If the UE receives a rejected NSSAI for the current PLMN and the registration area also contains TAIs belonging to a different PLMN, the UE shall treat the rejected NSSAI received for the current PLMN as applicable to the entire registered PLMN.

[0273] The rejected NSSAI of a failed or expired NSSAA includes one or more S-NSSAIs that have failed network slice-specific authentication and authorization or whose authorization has expired, and is applicable to the entire registered PLMN or SNPN.

[0274] The rejected NSSAI for the maximum number of UEs reached is applicable to the entire registered PLMN or SNPN and the access type for which the rejected NSSAI was sent. The AMF shall send the rejected NSSAI with the rejection reason "One or more S-NSSAIs are unavailable due to the maximum number of UEs reached" when one or more S-NSSAIs indicating that the maximum number of UEs has been reached are indicated. If timer T3526 associated with the S-NSSAI is started when the rejected NSSAI for the maximum number of UEs reached is received, the UE may remove one or more S-NSSAIs from the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "One or more S-NSSAIs are unavailable due to the maximum number of UEs reached" when timer T3526 associated with one or more S-NSSAIs expires. When one or more S-NSSAIs are removed from the rejected NSSAI for the maximum number of UEs reached, timer T3526 associated with the removed S-NSSAI or S-NSSAIs shall be stopped if running. The UE does not stop timer T3526 if the UE selects an E-UTRA cell connected to the EPC.

[0275] If the UE has received rejected NSSAIs for the maximum number of UEs reached, and the registration area contains TAIs belonging to different PLMNs that are equivalent PLMNs, the UE shall treat the received rejected NSSAIs for the maximum number of UEs reached as applicable to these equivalent PLMNs when the UE is within this registration area.

[0276] NOTE 2: Based on local policy, if the UE wants to register to the slice identified by this S-NSSAI, the UE may remove the S-NSSAI from the rejected NSSAIs of the failed or expired NSSAA.

[0277] NOTE 3: Based on the network local policy, if an S-NSSAI is requested by the UE based on that local policy, the network slice specific authentication and authorization procedure may be initiated by the AMF of the S-NSSAI within the rejected NSSAI of the failed or expired NSSAI.

[0278] NOTE 4: To ensure that at least one PDU session can be established to access the service even if network slice-specific authentication and authorization fails, it is recommended that at least one S-NSSAI in the default Configured NSSAI or at least one default S-NSSAI be exempt from network slice-specific authentication and authorization.

[0279] NOTE 5: To ensure that at least one PDU session can be established to access the service, it is recommended that at least one S-NSSAI within the default configured NSSAI or the subscribed S-NSSAI marked as the default S-NSSAI be exempt from network slice admission control.

[0280] NOTE 6: The rejected NSSAI can be provided by the network either via the rejected NSSAI IE or the extended rejected NSSAI IE.

[0281] 4.6.2 Mobility Management Aspects 4.6.2.1 General Upon registering to a PLMN or SNPN (excluding the registration procedure for periodic registration update, the initial registration for onboarding services in an SNPN, and the registration procedure for mobility registration update when registered for onboarding services in an SNPN), the UE shall send a Requested NSSAI to the AMF if: the Requested NSSAI contains one or more S-NSSAIs of the allowed NSSAIs of the PLMN or SNPN, or the configured NSSAI of the PLMN or SNPN, and corresponds to one or more network slices to which the UE intends to register, i.e. a) The UE has a configured NSSAI for the current PLMN or SNPN; b) The UE has an allowed NSSAI for the current PLMN or SNPN, or c) The UE has neither an allowed NSSAI for the current PLMN or SNPN nor a configured NSSAI for the current PLMN or SNPN, and has a default configured NSSAI. In this case, the UE indicates to the AMF that the Requested NSSAI is created from the default configured NSSAI.

[0282] In addition to the S-NSSAI included in the NSSAI mentioned above, the Requested NSSAI may be formed based on one or more S-NSSAIs available in the UE (see subclause 5.5.1.3.2 for further details). In a roaming scenario, the UE shall also provide one or more mapping S-NSSAIs for the Requested NSSAI, if available. The AMF shall verify whether the Requested NSSAI is allowed based on the subscribed S-NSSAI in the UE subscription and optionally one or more mapping S-NSSAIs provided by the UE, and if allowed, the AMF shall provide the UE with the allowed NSSAI for the PLMN or SNPN, and, if available, one or more mapping S-NSSAIs of the allowed NSSAI for the PLMN or SNPN. The AMF shall ensure that there is no more than one S-NSSAI of an allowed NSSAI mapped to the same S-NSSAI of an HPLMN or SNPN. In the following cases: a) If all S-NSSAIs included in the Requested NSSAI are rejected or the Requested NSSAI was not included by the UE, b) If one or more default S-NSSAIs do not exist or all subscribed S-NSSAIs marked as default are not permitted, and c) the UE has not registered or is not registered for onboarding services in the SNPN, and the UE has not registered or is not registered for emergency services; The AMF may reject a registration request (see subsections 5.5.1.2.5 and 5.5.1.3.5 for further details).

[0283] The set of one or more network slices for a UE can be changed at any time while the UE is registered to a PLMN or SNPN, and the change can be initiated by the network or the UE. In this case, the allowed NSSAI and associated registration area can be changed during the registration procedure or the generic UE configuration update procedure. The configured NSSAI and rejected NSSAI can be changed during the registration procedure or the generic UE configuration update procedure. The default configured NSSAI can be changed by sending a UE parameter update transparent container to the UE during the NAS transport procedure. The pending NSSAI can also be changed during the registration procedure. Furthermore, using the generic UE configuration update procedure, the network can trigger a registration procedure to update the allowed NSSAI. If the UE is no longer interested in an S-NSSAI in the pending NSSAI, the UE initiates a mobility registration procedure, and the UE sends an abandon NSSAI in a registration request message, including one or more pending S-NSSAIs that the UE is no longer interested in. When the UE needs to send a requested NSSAI to the AMF, the S-NSSAIs in the Requested NSSAI shall share at least one common NSSRG group. The S-NSSAIs in the abandon NSSAI shall not be considered in the NSSRG procedure. When the AMF receives a registration request message including an abandon NSSAI, the AMF removes one or more S-NSSAIs present in the abandon NSSAI from the pending NSSAI list. The UE may abort the NSSAA procedure for one or more S-NSSAIs present in the abandon NSSAI. The AMF sends a registration accept message including the latest allowed NSSAI. The newly allowed one or more S-NSSAIs shall share at least one NSSRG value.If the 5GS Registration Type IE indicates "Mobility Registration Update", a procedure to change the slice or slices to which the UE is currently registered has not been initiated, and the UE is still within the current registration area, then the UE in NB-N1 mode shall not include the Requested NSSAI during the registration procedure. If the 5GS Registration Type IE indicates "SNPN Onboarding Registration" or the UE is registered for onboarding services in the SNPN, then the UE shall not include the Requested NSSAI during the registration procedure.

[0284] The AMF shall not include the allowed NSSAI during a registration procedure where the 5GS Registration Type IE indicates "Mobility Registration Update" unless the allowed NSSAI has changed for the UE. The UE shall consider the last received allowed NSSAI valid until the UE receives a new allowed NSSAI. The AMF shall not include the allowed NSSAI during a registration procedure where the 5GS Registration Type IE indicates "SNPN Onboarding Registration" or during a registration procedure where the UE is registered with an onboarding service in the SNPN.

[0285] 5.5.1.3.2 Mobility and Periodic Registration Update Initiation A UE in 5GMM-REGISTERED state shall initiate the registration procedure for mobility and periodic registration updates by sending a REGISTRATION REQUEST message to the AMF if: a) If the UE detects that the current TAI is not in the list of tracking areas that the UE previously registered with the AMF; b) When the periodic registration update timer T3512 expires in 5GMM-IDLE mode, c) if the UE receives a CONFIGURATION UPDATE COMMAND message indicating "registration requested" in the Registration Requested bit of the Configuration Update Indication IE as specified in subclause 5.4.4.3; d) When a UE in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state receives a paging or the UE receives a NOTIFICATION message with an access type indicating 3GPP access over non-3GPP access for a PDU session associated with a 3GPP access;

[0286] NOTE 1: As an implementation option, the MUSIM UE is allowed not to respond to a page based on information available in the paging message, such as a voice service indication. e) During an inter-system change from S1 mode to N1 mode, if the UE had previously initiated an attach procedure or a tracking area update procedure while in S1 mode; f) if the UE receives an "RRC connection failed" indication from lower layers and has no signaling pending (i.e., the lower layers request NAS signaling connection resumption), except as specified in subclause 5.3.1.4; g) If the UE changes its 5GMM capabilities or its S1 UE network capabilities, or both; h) When the usage configuration of the UE is changed, i) When it is necessary to change one or more slices to which the UE is currently registered, j) When the UE changes UE-specific DRX parameters: k) If a UE in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state receives a request from higher layers to establish an emergency PDU session or perform emergency service fallback, l) When the UE needs to register with the SMS over NAS, indicates a change in requirements for using the SMS over NAS, or deregisters from the SMS over NAS; m) if the UE needs to indicate the PDU session status to the network after performing a local release of one or more PDU sessions as specified in subclause 6.4.1.5 and 6.4.3.5, n) When a UE in 5GMM-IDLE mode changes its radio capabilities for NG-RAN or E-UTRAN, o) the UE receives a fallback indication from the lower layers and there is no signaling pending (i.e. the lower layers request NAS signaling connection resumption, see subclause 5.3.1.4 and 5.3.1.2); p) Blank, q) If the UE needs to request new LADN information: r) if the UE needs to request the use of MICO mode, or needs to stop using MICO mode, or needs to request the use of a new T3324 value; s) When a UE in 5GMM-CONNECTED mode with an RRC inactive indication belongs to an equivalent PLMN of the registered PLMN and enters a cell in its current registration area that does not belong to the registered PLMN; t) If the UE receives a SERVICE REJECT message or a DL NAS TRANSPORT message via 3GPP, and the 5GMM cause value is set to #28 "Restricted Service Area", u) if the UE needs to request the use of eDRX, if changes in the eDRX usage conditions in the UE require different extended DRX parameters, or if the use of eDRX needs to be stopped;

[0287] NOTE 2: A change in eDRX usage status in the UE may include, for example, a change in the UE configuration, a change in requirements from higher layers, or a low battery level in the UE. v) When a UE supporting 5G-SRVCC changes Mobile Station Class Mark 2 or supported codec from NG-RAN to UTRAN, w) If a UE in the 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state decides to request a new network slice after being rejected due to the absence of a requested allowed network slice, or decides to request one or more S-NSSAIs that have been removed from the maximum number of rejected NSSAIs reached for the UE; x) When the UE is not in NB-N1 mode and the UE radio capability ID applicable to the current UE radio configuration changes due to the expiration of a network-assigned UE radio capability ID by the serving PLMN or SNPN; y) If the UE receives a REGISTRATION REJECT message with 5GMM cause value #3, #6, or #7 without integrity protection on another access, z) if the UE needs to request a new encryption key for encrypted broadcast assistance data; za) If, during manual CAG selection, the UE selects a CAG-ID that is not included in the "allowed CAG list" of the selected PLMN or a CAG-ID of a PLMN for which there is no entry in the "CAG information list", or if the UE does not select a CAG-ID and selects a PLMN for which an entry in the "CAG information list" contains the indication that the UE is only allowed to access 5GS via the CAG cell, zb) When the UE needs to start, stop or change the conditions for using WUS assistance information or PEIPS assistance information, zc) When the UE changes UE-specific DRX parameters in NB-N1 mode: zd) When a UE in 5GMM-CONNECTED mode with an RRC inactive indication enters a new cell that has a different RAT in the current TAI list or is not in the current TAI list, ze) if the UE has sent a NOTIFICATION RESPONSE message via non-3GPP access in response to receiving a NOTIFICATION message via non-3GPP access as specified in subclause 5.6.3.1 and the UE has entered the 5GMM-REGISTERED.NORMAL-SERVICE state or the 5GMM-REGISTERED.NON-ALLOWED-SERVICE state (as described in subclause 5.3.5.2) via 3GPP access, zf) If a UE that supports UAS services is not registered for UAS services and needs to register for 5GS for UAS services, zg) If a UE supporting MINT needs to perform mobility registration procedures and periodic registration updates to register with a PLMN that offers disaster roaming, zh) If a MUSIM UE supporting paging timing collision control needs to request a new 5G-GUTI allocation and the UE is not registered for emergency services,

[0288] NOTE 3: Based on the implementation, the MUSIM UE may request a new 5G-GUTI allocation (e.g., if the lower layers request a change in the timing of the paging occasion). zi) If the network supports paging restriction and the 5GMM-REGISTERED.NON-ALLOWED-SERVICE state must request the network to remove the paging restriction, zj) If the UE changes its 5GS Preferred CIoT network behavior or EPS Preferred CIoT network behavior, zk) A UE in 5GMM-REGISTERED.NO-CELL-AVAILABLE state that has one or more S-NSSAIs in its pending NSSAIs finds a suitable cell according to 3GPP TS 38.304

[28] , or zl) if the UE is registered for disaster roaming services and receives a request from higher layers to establish an emergency PDU session or perform emergency service fallback; and zm) When the UE is no longer interested in the S-NSSAI contained in the stored pending list.

[0289] 8.2.6.1 Message Definition The REGISTRATION REQUEST message is sent by the UE to the AMF. See Table 1 and Table 2. Message type: REGISTRATION REQUEST Enabled: Dual Direction: UE to network [Table 1] [Table 2]

[0290] 8.2.6.31 Abandon NSSAI If the S-NSSAI is stored in the Pending NSSAI and the UE is no longer interested in the S-NSSAI, the UE shall include this IE.

[0291] Variations and Substitutions Detailed exemplary embodiments have been described above. As will be appreciated by those skilled in the art, several modifications and alternatives may be made to the above exemplary embodiments while still benefiting from the disclosure embodied therein. By way of example, only some of these alternatives and modifications are described herein.

[0292] In the above description, for ease of understanding, the UE 3 and network devices are described as having several separate modules (such as a communications control module). While these modules may be provided in this manner for specific applications, such as when an existing system is modified to implement the present disclosure, in other applications, such as systems designed from the beginning with the features of the present invention in mind, these modules may not be identifiable as separate entities because they may be incorporated into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a combination thereof.

[0293] Each controller may comprise any suitable form of processing circuitry, including (but not limited to), for example, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control, data, and / or address buses), direct memory access (DMA) functionality, hardware or software-implemented counters, pointers, and / or timers, etc. In the above exemplary embodiment, several software modules have been described. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be provided to the UE 3 and network devices as signals over a computer network or on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates updating the UE 3 and network devices to update their functionality.

[0294] In the above exemplary embodiment, 3GPP wireless communication (radio access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) may also be used in accordance with the above exemplary embodiment.

[0295] Items of user equipment may include, for example, communication devices such as mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, etc. Such mobile (or generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application will refer to mobile devices (or UE) in the description, but it will be understood that the described techniques may be implemented on any communication device (mobile and / or generally fixed) that can connect to a communication network to send and receive data, regardless of whether such communication device is controlled by human input or software instructions stored in memory.

[0296] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0297] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and a system, and therefore may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0298] It will be understood that each block of the block diagrams may be implemented by computer program instructions. These computer program instructions may be provided to a general-purpose computer, a special-purpose computer, or a processor of another programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0299] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0300] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0301] Although the present disclosure has been particularly shown and described with reference to exemplary embodiments thereof, the present disclosure is not limited to these embodiments. Those skilled in the art will understand that various changes in form and details can be made without departing from the spirit and scope of the present disclosure as defined herein. For example, the above exemplary embodiments are not limited to 5GS, but are also applicable to communication systems other than 5GS (e.g., 6G systems, 5G beyond systems).

[0302] Additional notes All or part of the exemplary aspects disclosed above may be described in the following appendices, but are not limited thereto.

[0303] Appendix 1 1. A method for a user equipment (UE), comprising: Communicating with the AMF; selecting a first NSAG and a first NSAG priority based on the Allowed NSSAI and the Pending NSSAI; A method comprising:

[0304] Appendix 2 The first NSAG and the first NSAG priority are selected in a NAS layer of the UE; The method described in Appendix 1.

[0305] Appendix 3 performing a first cell reselection based on the first NSAG and the first NSAG priority; 3. The method of claim 1 or 2, further comprising:

[0306] Appendix 4 performing the first cell reselection includes performing the first cell reselection based on a first NSAG, a first NSAG priority, and a Pending NSSAI for at least one of 3GPP access and non-3GPP access. The method described in Appendix 3.

[0307] Appendix 5 receiving information about NSAGs supported by the cell; If the NSAG indicated by the information includes the first NSAG, the first cell reselection is not performed; 5. The method of claim 3 or 4, further comprising:

[0308] Appendix 6 The first cell reselection is performed in the AS of the UE; 6. The method of any one of appendixes 3 to 5.

[0309] Appendix 7 Sending the first NSAG and the first NSAG priority to the AMF The method according to any one of Appendix 1 to Appendix 6, further comprising:

[0310] Appendix 8 The first NSAG and the first NSAG priority are sent to another AMF; The method described in Appendix 7.

[0311] Appendix 9 the first NSAG and the first NSAG priority are transmitted to a Radio Access Network (RAN) node; The method according to any one of Supplementary Notes 1 to 8.

[0312] Appendix 10 At least one of the first NSAG and the first NSAG priority is used to select a cell for handover; The method according to any one of Supplementary Notes 1 to 9.

[0313] Appendix 11 selecting a second NSAG and a second NSAG priority based on the Allowed NSSAI if the NSSAA procedure for the S-NSSAI included in the Pending NSSAI fails; Sending the second NSAG and the second NSAG priority to the AMF; The method according to any one of Appendixes 1 to 10, further comprising:

[0314] Appendix 12 The second NSAG and the second NSAG priority are selected in a NAS layer of the UE. The method described in Appendix 11.

[0315] Appendix 13 performing a second cell reselection based on the second NSAG and the second NSAG priority; 13. The method of claim 11 or 12, further comprising:

[0316] Appendix 14 The second cell reselection is performed in the AS of the UE. The method described in Appendix 13.

[0317] Appendix 15 The second NSAG and the second NSAG priority are sent to another AMF; The method according to any one of Supplementary Notes 11 to 14.

[0318] Appendix 16 the second NSAG and the second NSAG priority are transmitted to the RAN node; The method according to any one of Supplementary Notes 11 to 15.

[0319] Appendix 17 At least one of the second NSAG and the second NSAG priority is used to select a cell for handover; The method according to any one of Supplementary Notes 11 to 16.

[0320] Appendix 18 When the UE roams to the VPLMN, performing a third cell reselection based on the S-NSSAI included in the Configured NSSAI for the VPLMN. The method according to any one of Appendix 1 to Appendix 17, further comprising:

[0321] Appendix 19 The first NSAG and first NSAG priority are selected regardless of the status of the NSAC. The method according to any one of Supplementary Notes 1 to 18.

[0322] Appendix 20 1. A method for a user equipment (UE), comprising: Communicating with the AMF; selecting a first NSAG and a first NSAG priority based on the first Allowed NSSAI after successful completion of the NSSAA procedure for the S-NSSAI included in the Pending NSSAI; Including, The first Allowed NSSAI includes S-NSSAI, method.

[0323] Appendix 21 selecting a second NSAG and a second NSAG priority based on the second Allowed NSSAI before selecting the first NSAG and the first NSAG priority; and the second Allowed NSSAI does not include an S-NSSAI; 21. The method described in Appendix 20.

[0324] Appendix 22 The second NSAG and the second NSAG priority are selected in a NAS layer of the UE. 21. The method described in Appendix 21.

[0325] Appendix 23 performing a second cell reselection based on the second NSAG and the second NSAG priority; 23. The method of claim 21 or 22, further comprising:

[0326] Appendix 24 The second cell reselection is performed in the AS of the UE. 24. The method described in Appendix 23.

[0327] Appendix 25 Sending the second NSAG and the second NSAG priority to the AMF 25. The method according to any one of appendices 21 to 24, further comprising:

[0328] Appendix 26 The second NSAG and the second NSAG priority are sent to another AMF; The method described in Appendix 25.

[0329] Appendix 27 the second NSAG and the second NSAG priority are transmitted to the RAN node; The method according to any one of Supplementary Notes 21 to 26.

[0330] Appendix 28 At least one of the second NSAG and the second NSAG priority is used to select a cell for handover; The method according to any one of Supplementary Notes 21 to 27.

[0331] Appendix 29 The first NSAG and the first NSAG priority are selected in a NAS layer of the UE; 29. The method of any one of Supplementary Notes 20 to 28.

[0332] Appendix 30 performing a first cell reselection based on the first NSAG and the first NSAG priority; 30. The method of any one of claims 20 to 29, further comprising:

[0333] Appendix 31 performing the first cell reselection includes performing the first cell reselection based on a first NSAG, a first NSAG priority, and a Pending NSSAI for at least one of 3GPP access and non-3GPP access. 31. The method described in Appendix 30.

[0334] Appendix 32 receiving information about NSAGs supported by the cell; When the NSAG indicated by the information includes the first NSAG, the first cell reselection is not performed; 32. The method of claim 30 or 31, further comprising:

[0335] Appendix 33 The first cell reselection is performed in the AS of the UE; 33. The method of any one of claims 30 to 32.

[0336] Appendix 34 Sending the first NSAG and the first NSAG priority to the AMF 34. The method of any one of claims 20 to 33, further comprising:

[0337] Appendix 35 The first NSAG and the first NSAG priority are sent to another AMF; 35. The method of any one of Supplementary Notes 20 to 34.

[0338] Appendix 36 the first NSAG and the first NSAG priority are transmitted to the RAN node; 36. The method of any one of Supplementary Notes 20 to 35.

[0339] Appendix 37 At least one of the first NSAG and the first NSAG priority is used to select a cell for handover; 37. The method of any one of Supplementary Notes 20 to 36.

[0340] Appendix 38 When the UE roams to the VPLMN, performing a third cell reselection based on an S-NSSAI included in the Configured NSSAI for the VPLMN; 38. The method of any one of Claims 20 to 37, further comprising:

[0341] Appendix 39 The first NSAG and first NSAG priority are selected regardless of the status of the NSAC. 39. The method of any one of Supplementary Notes 20 to 38.

[0342] Appendix 40 1. A method for a communication device, comprising: receiving a first NSAG and a first NSAG priority; transmitting a first NSAG and a first NSAG priority; A method comprising:

[0343] Appendix 41 transmitting the first NSAG and the first NSAG priority includes transmitting the first NSAG and the first NSAG priority to another communication device; 41. The method described in Appendix 40.

[0344] Appendix 42 transmitting the first NSAG and the first NSAG priority includes transmitting the first NSAG and the first NSAG priority to a RAN node. 41. The method described in Appendix 40.

[0345] Appendix 43 At least one of the first NSAG and the second NSAG is used to select a cell for handover; 43. The method of any one of claims 40 to 42.

[0346] Appendix 44 receiving a second NSAG and a second NSAG priority; transmitting a second NSAG and a second NSAG priority; 44. The method of any one of claims 40 to 43, further comprising:

[0347] Appendix 45 transmitting the second NSAG and the second NSAG priority includes transmitting the second NSAG and the second NSAG priority to another communication device; The method described in Appendix 44.

[0348] Appendix 46 transmitting the second NSAG and the second NSAG priority includes transmitting the second NSAG and the second NSAG priority to the RAN node; The method described in Appendix 45.

[0349] Appendix 47 At least one of the first NSAG and the second NSAG is used to select a cell for handover; 47. The method of any one of claims 44 to 46.

[0350] Appendix 48 1. A method for a RAN node, comprising: receiving a first NSAG and a first NSAG priority; selecting a cell for handover based on the first NSAG and the first NSAG priority; A method comprising:

[0351] Appendix 49 Performing a handover to a cell 49. The method of claim 48, further comprising:

[0352] Appendix 50 A user equipment (UE), means for communicating with a communication device; means for selecting a first NSAG and a first NSAG priority based on the Allowed NSSAI and the Pending NSSAI; A user equipment (UE) comprising:

[0353] Appendix 51 The first NSAG and the first NSAG priority are selected in a NAS layer of the UE; UE as described in Appendix 50.

[0354] Appendix 52 means for performing a first cell reselection based on the first NSAG and the first NSAG priority; 52. The UE of claim 50 or 51, further comprising:

[0355] Appendix 53 means for performing a first cell reselection based on a first NSAG, a first NSAG priority, and a Pending NSSAI for at least one of 3GPP access and non-3GPP access; 53. The UE of claim 52, further comprising:

[0356] Appendix 54 means for receiving information regarding NSAGs supported by the cell; means for not performing a first cell reselection when the first NSAG is included in the NSAG indicated by the information; 54. The UE of claim 52 or 53, further comprising:

[0357] Appendix 55 The first cell reselection is performed in the AS of the UE; 55. The UE of any one of Supplementary Notes 52 to 54.

[0358] Appendix 56 means for transmitting the first NSAG and the first NSAG priority to the communication device 56. The UE of any one of Claims 50 to 55, further comprising:

[0359] Appendix 57 the first NSAG and the first NSAG priority are transmitted to another communication device; UE as described in Appendix 56.

[0360] Appendix 58 58. The UE of any one of Supplementary Notes 50 to 57, wherein the first NSAG and the first NSAG priority are transmitted to a RAN node.

[0361] Appendix 59 At least one of the first NSAG and the first NSAG priority is used to select a cell for handover; 59. The UE of any one of Supplementary Notes 50 to 58.

[0362] Appendix 60 means for selecting a second NSAG and a second NSAG priority based on the Allowed NSSAI if an NSSAA procedure for an S-NSSAI included in the Pending NSSAI fails; means for transmitting the second NSAG and the second NSAG priority to the communication device; 59. The UE of claim 50 or 59, further comprising:

[0363] Appendix 61 The second NSAG and the second NSAG priority are selected in a NAS layer of the UE. UE as described in Appendix 60.

[0364] Appendix 62 means for performing a second cell reselection based on the second NSAG and the second NSAG priority; 62. The UE of claim 60 or 61, further comprising:

[0365] Appendix 63 The second cell reselection is performed in the AS of the UE. UE as described in Appendix 62.

[0366] Appendix 64 the second NSAG and the second NSAG priority are transmitted to another communication device; 64. The UE of any one of Supplementary Notes 60 to 63.

[0367] Appendix 65 the second NSAG and the second NSAG priority are transmitted to the RAN node; 65. The UE of any one of Supplementary Notes 60 to 64.

[0368] Appendix 66 At least one of the second NSAG and the second NSAG priority is used to select a cell for handover; 66. The UE of any one of Clauses 60 to 65.

[0369] Appendix 67 and means for performing a third cell reselection based on an S-NSSAI included in a Configured NSSAI for the VPLMN when the UE roams to the VPLMN. 67. The UE of any one of Claims 50 to 66, further comprising:

[0370] Appendix 68 The first NSAG and first NSAG priority are selected regardless of the status of the NSAC. 68. The UE of any one of Supplementary Notes 50 to 67.

[0371] Appendix 69 A user equipment (UE), means for communicating with a communication device; means for selecting a first NSAG and a first NSAG priority based on a first Allowed NSSAI after successful completion of an NSSAA procedure for an S-NSSAI included in the Pending NSSAI; Equipped with The first Allowed NSSAI includes S-NSSAI, User Equipment (UE).

[0372] Appendix 70 means for selecting a second NSAG and a second NSAG priority based on the second Allowed NSSAI before selecting the first NSAG and the first NSAG priority; Furthermore, The second Allowed NSSAI does not include the S-NSSAI; UE as described in Appendix 69.

[0373] Appendix 71 The second NSAG and the second NSAG priority are selected in a NAS layer of the UE. UE as described in Appendix 70.

[0374] Appendix 72 means for performing a second cell reselection based on the second NSAG and the second NSAG priority; 72. The UE of claim 70 or 71, further comprising:

[0375] Appendix 73 The second cell reselection is performed in the AS of the UE. UE as described in Appendix 72.

[0376] Appendix 74 means for transmitting the second NSAG and the second NSAG priority to the communication device; 74. The UE of any one of Supplementary Notes 70 to 73, further comprising:

[0377] Appendix 75 the second NSAG and the second NSAG priority are transmitted to another communication device; UE as described in Appendix 74.

[0378] Appendix 76 the second NSAG and the second NSAG priority are transmitted to the RAN node; 76. The UE of any one of Supplementary Notes 70 to 75.

[0379] Appendix 77 At least one of the second NSAG and the second NSAG priority is used to select a cell for handover; 77. The UE of any one of Supplementary Notes 70 to 76.

[0380] Appendix 78 The first NSAG and the first NSAG priority are selected in a NAS layer of the UE; 6. The UE of claim 69 or 77.

[0381] Appendix 79 means for performing a first cell reselection based on the first NSAG and the first NSAG priority; 79. The UE of any one of Claims 69 to 78, further comprising:

[0382] Appendix 80 performing the first cell reselection includes performing the first cell reselection based on a first NSAG, a first NSAG priority, and a Pending NSSAI for at least one of 3GPP access and non-3GPP access. UE as described in Appendix 79.

[0383] Appendix 81 means for receiving information regarding NSAGs supported by the cell; means for not performing a first cell reselection when the first NSAG is included in the NSAG indicated by the information; 81. The UE of claim 79 or 80, further comprising:

[0384] Appendix 82 The first cell reselection is performed in the AS of the UE; 82. The UE of any one of Supplementary Notes 79 to 81.

[0385] Appendix 83 means for transmitting the first NSAG and the first NSAG priority to the communication device 83. The UE of any one of Claims 69 to 82, further comprising:

[0386] Appendix 84 the first NSAG and the first NSAG priority are transmitted to another communication device; 84. The UE of any one of Supplementary Notes 69 to 83.

[0387] Appendix 85 the first NSAG and the first NSAG priority are transmitted to the RAN node; 8. The UE of any one of Supplementary Notes 69 to 84.

[0388] Appendix 86 At least one of the first NSAG and the first NSAG priority is used to select a cell for handover; 86. The UE of any one of Supplementary Notes 69 to 85.

[0389] Appendix 87 and means for performing a third cell reselection based on an S-NSSAI included in a Configured NSSAI for the VPLMN when the UE roams to the VPLMN. 87. The UE of any one of Claims 69 to 86, further comprising:

[0390] Appendix 88 The first NSAG and first NSAG priority are selected regardless of the status of the NSAC. 87. The UE of any one of Supplementary Notes 69 to 87.

[0391] Appendix 89 A communication device, means for receiving a first NSAG and a first NSAG priority; means for transmitting a first NSAG and a first NSAG priority.

[0392] Appendix 90 means for transmitting the first NSAG and the first NSAG priority to another communication device; 90. The communication device of claim 89, further comprising:

[0393] Appendix 91 means for transmitting the first NSAG and the first NSAG priority to a RAN node; 90. The communication device of claim 89, further comprising:

[0394] Appendix 92 At least one of the first NSAG and the second NSAG is used to select a cell for handover; 92. A communication device according to any one of Supplementary Notes 89 to 91.

[0395] Appendix 93 means for receiving a second NSAG and a second NSAG priority; means for transmitting a second NSAG and a second NSAG priority; 93. The communication device of any one of Supplementary Notes 89 to 92, further comprising:

[0396] Appendix 94 transmitting the second NSAG and the second NSAG priority includes transmitting the second NSAG and the second NSAG priority to another communication device; 94. The communications device of claim 93.

[0397] Appendix 95 transmitting the second NSAG and the second NSAG priority includes transmitting the second NSAG and the second NSAG priority to the RAN node; 95. The communications device of claim 94.

[0398] Appendix 96 At least one of the first NSAG and the second NSAG is used to select a cell for handover; 96. A communication device according to any one of Supplementary Notes 93 to 95.

[0399] Appendix 97 A RAN node, means for receiving a first NSAG and a first NSAG priority; means for selecting a cell for handover based on the first NSAG and the first NSAG priority.

[0400] Appendix 98 Means for performing a handover to a cell - Patent application 98. The RAN node of claim 97, further comprising:

[0401] Appendix 99 1. A method for a user equipment (UE), comprising: communicating with a communication device; transmitting, to the communication device, a first S-NSSAI included in a Pending NSSAI; A method comprising:

[0402] Appendix 100 Transmitting the first S-NSSAI includes transmitting the first S-NSSAI after performing cell reselection based on the network slice; 99. The method described in Appendix 99.

[0403] Appendix 101 A network slice-based cell reselection is performed for the second S-NSSAI, The second S-NSSAI is different from the first S-NSSAI, 101. The method of claim 100.

[0404] Appendix 102 transmitting the first S-NSSAI includes transmitting a Requested NSSAI that includes the first S-NSSAI and the second S-NSSAI; 102. The method of claim 101.

[0405] Appendix 103 The first S-NSSAI and the Requested NSSAI are included in the registration request message. 103. The method of claim 102.

[0406] Appendix 104 transmitting the first S-NSSAI includes transmitting the first S-NSSAI if the UE has a Pending NSSAI; 104. The method of any one of claims 99 to 103.

[0407] Appendix 105 A method for a user equipment (UE), communicating with a communication device; transmitting, to the communication device, information indicating that the UE is not interested in the S-NSSAI included in the Pending NSSAI; Including, a method.

[0408] Appendix 106 1. A method for a communication device, comprising: receiving a first S-NSSAI included in a Pending NSSAI; Discontinuing the NSSAA procedures of the first S-NSSAI; A method comprising:

[0409] Appendix 107 The first S-NSSAI is included in the registration request message, The registration request message includes the Requested NSSAI, The Requested NSSAI includes a second S-NSSAI, The second S-NSSAI is different from the first S-NSSAI, 107. The method of claim 106.

[0410] Appendix 108 Cancelling an NSSAA procedure includes cancelling an NSSAA procedure if the NSSAA procedure is in progress; 108. The method of claim 106 or 107.

[0411] Appendix 109 Upon successful completion of the NSSAA procedure, remove the first S-NSSAI from the Allowed NSSAIs. 109. The method of any one of Clauses 106 to 108, further comprising:

[0412] Appendix 110 If the NSSAA procedure fails, include the first S-NSSAI in the Rejected NSSAI. 109. The method of any one of claims 106 to 109, further comprising:

[0413] Appendix 111 A user equipment (UE), means for communicating with a communication device; means for transmitting, to a communication device, a first S-NSSAI included in a Pending NSSAI; A user equipment (UE) comprising:

[0414] Appendix 112 means for transmitting a first S-NSSAI after performing a cell reselection based on a network slice; 112. The UE of claim 111, further comprising:

[0415] Appendix 113 A network slice-based cell reselection is performed for the second S-NSSAI, The second S-NSSAI is different from the first S-NSSAI, UE as described in Appendix 112.

[0416] Appendix 114 means for transmitting a Requested NSSAI including a first S-NSSAI and a second S-NSSAI; 114. The UE of claim 113, further comprising:

[0417] Appendix 115 The first S-NSSAI and the Requested NSSAI are included in the registration request message. UE as described in Appendix 114.

[0418] Appendix 116 means for transmitting a first S-NSSAI if the UE has a Pending NSSAI; A UE according to any one of Supplementary Notes 111 to 115.

[0419] Appendix 117 A user equipment (UE), means for communicating with a communication device; means for transmitting, to the communication device, information indicating that the UE is not interested in the S-NSSAI included in the Pending NSSAI; A user equipment (UE) comprising:

[0420] Appendix 118 A communication device, means for receiving a first S-NSSAI included in a Pending NSSAI; means for cancelling the NSSAA procedure of the first S-NSSAI; A communication device comprising:

[0421] Appendix 119 The first S-NSSAI is included in the registration request message, The registration request message includes the Requested NSSAI, The Requested NSSAI includes a second S-NSSAI, The second S-NSSAI is different from the first S-NSSAI, 19. The communications device of claim 118.

[0422] Appendix 120 A means to abort an NSSAA procedure if one is in progress. 119. The communication device of claim 118, further comprising:

[0423] Appendix 121 means for removing the first S-NSSAI from the Allowed NSSAIs upon successful completion of the NSSAA procedure; 121. The communication device of any one of Supplementary Notes 118 to 120, further comprising:

[0424] Appendix 122 If the NSSAA procedure fails, a means for including the first S-NSSAI in the Rejected NSSAI 122. The communication device of any one of Supplementary Notes 118 to 121, further comprising:

[0425] This application claims the benefit of priority to Indian Patent Application No. 202211043222 filed on July 28, 2022, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0426] 1 System 3UE 5 RAN 7 Core Network 20 Data Network

Claims

1. 1. A method for a user equipment (UE), comprising: communicating with a communication device; transmitting a first Single NSSAI (S-NSSAI) included in Pending Network Slice Selection Assistance Information (NSSAI) to the communication device; A method comprising:

2. 2. The method of claim 1, wherein transmitting the first S-NSSAI includes transmitting the first S-NSSAI after performing cell reselection based on a network slice.

3. The cell reselection based on the network slice is performed for a second S-NSSAI; and the second S-NSSAI is different from the first S-NSSAI; The method of claim 2.

4. transmitting the first S-NSSAI includes transmitting a Requested NSSAI including the first S-NSSAI and the second S-NSSAI; The method of claim 3.

5. The first S-NSSAI and the Requested NSSAI are included in a registration request message. The method of claim 4.

6. transmitting the first S-NSSAI includes transmitting the first S-NSSAI if the UE has the pending NSSAI; The method according to any one of claims 1 to 5.

7. A method for a user equipment (UE), communicating with a communication device; transmitting, to the communication device, information indicating that the UE is not interested in the S-NSSAI included in the Pending NSSAI; Including, a method.

8. 1. A method of a communication device, comprising: receiving a first S-NSSAI included in a Pending NSSAI; Aborting a Network Slice-Specific Authentication and Authorization (NSSAA) procedure of the first S-NSSAI; A method comprising:

9. the first S-NSSAI is included in a registration request message; the registration request message includes a Requested NSSAI; the Requested NSSAI includes a second S-NSSAI; the second S-NSSAI is different from the first S-NSSAI; The method of claim 8.

10. Aborting the NSSAA procedure includes aborting the NSSAA procedure if the NSSAA procedure is in progress.

10. The method according to claim 8 or 9.

11. If the NSSAA procedure is successfully completed, deleting the first S-NSSAI from Allowed NSSAIs. The method of any one of claims 8 to 10, further comprising:

12. If the NSSAA procedure fails, include the first S-NSSAI in a Rejected NSSAI. The method of any one of claims 8 to 11, further comprising:

13. A user equipment (UE), means for communicating with a communication device; means for transmitting a first S-NSSAI included in a Pending NSSAI to the communication device; A user equipment (UE) comprising:

14. means for transmitting the first S-NSSAI after performing cell reselection based on a network slice; The UE of claim 13 further comprising:

15. The cell reselection based on the network slice is performed for a second S-NSSAI; and the second S-NSSAI is different from the first S-NSSAI; 15. The UE of claim 14.

16. means for transmitting a Requested NSSAI including the first S-NSSAI and the second S-NSSAI; The UE of claim 15 further comprising:

17. The first S-NSSAI and the Requested NSSAI are included in a registration request message.

17. The UE of claim 16.

18. means for transmitting the first S-NSSAI if the UE has the pending NSSAI; 18. The UE according to any one of claims 13 to 17.

19. A user equipment (UE), means for communicating with a communication device; means for transmitting, to the communication device, information indicating that the UE is not interested in the S-NSSAI included in the Pending NSSAI; A user equipment (UE) comprising:

20. A communication device, means for receiving a first S-NSSAI included in a Pending NSSAI; means for terminating an NSSAA procedure of the first S-NSSAI; A communication device comprising:

21. the first S-NSSAI is included in a registration request message; the registration request message includes a Requested NSSAI; the Requested NSSAI includes a second S-NSSAI; the second S-NSSAI is different from the first S-NSSAI; 21. The communication device of claim 20.

22. means for terminating the NSSAA procedure if the NSSAA procedure is in progress; 22. The communication device according to claim 20 or 21, further comprising:

23. means for deleting the first S-NSSAI from Allowed NSSAIs if the NSSAA procedure is successfully completed; The communication device according to any one of claims 20 to 22, further comprising:

24. means for including the first S-NSSAI in a Rejected NSSAI if the NSSAA procedure fails; The communication device according to any one of claims 20 to 23, further comprising:

Images