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

Abstract

There are many ambiguities in the 3GPP specifications regarding how to handle the NSSRG features. [Solution] A method in a user equipment (UE) communicating with a communication device, the method includes transmitting a registration request message, the registration request message including a requested Network Slice Selection Assistance Information (NSSAI), the requested NSSAI including a first Single Network Slice Selection Assistance Information (S-NSSAI), the first S-NSSAI and a second S-NSSAI of a pending NSSAI associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.

Description

[Technical Field]

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

[0002] Network Slice Simultaneous Registration Groups (NSSRGs) will be introduced to 5GS in Release 17. The NSSRG feature provides 3GPP operators with a mechanism to limit the combinations of simultaneously registered network slices. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.1.0 (2021-12) [Non-patent document 2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V17.3.0 (2021-12) [Non-patent document 3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V17.3.0 (2021-12) [Non-patent document 4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V17.3.0 (2021-12) Summary of the Invention [Problem to be solved by the invention]

[0004] However, there are many ambiguities in the 3GPP specifications regarding how to handle the NSSRG functionality.

[0005] For example, the present disclosure provides a solution to this problem. [Means for solving the problem]

[0006] In an aspect of the present disclosure, a method for a user equipment (UE) communicating with a communications device includes transmitting a Registration Request message, the Registration Request message including a Requested Network Slice Selection Assistance Information (NSSAI), the Requested NSSAI including a first Single Network Slice Selection Assistance Information (S-NSSAI), and the first S-NSSAI and a second S-NSSAI of a Pending NSSAI associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.

[0007] In an aspect of the present disclosure, a user equipment (UE) includes means for communicating with a communication device and means for transmitting a Registration Request message. The Registration Request message includes a Requested Network Slice Selection Assistance Information (NSSAI). The Requested NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.

[0008] In an aspect of the disclosure, a method of a communications apparatus communicates with a user equipment (UE). The method includes transmitting a message, the message including an Allowed Network Slice Selection Assistance Information (NSSAI). The Allowed NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.

[0009] In an aspect of the disclosure, a communications apparatus includes means for communicating with a user equipment (UE). The communications apparatus includes means for transmitting a message. The message includes an Allowed Network Slice Selection Assistance Information (NSSAI). The Allowed NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.

[0010] In an aspect of the present disclosure, a method of a communications device transmits a first message including a Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The method receives a Registration Request message including a Requested NSSAI. The Requested NSSAI includes a second S-NSSAI. The method checks whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. If the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, the method transmits a second message including a Configured NSSAI.

[0011] In an aspect of the present disclosure, a communications device includes means for transmitting a first message including a Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The communications device includes means for receiving a Registration Request message including a Requested NSSAI. The Requested NSSAI includes a second S-NSSAI. The communications device includes means for verifying whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The communications device includes means for transmitting a second message including a Configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a signaling diagram of a first example of the first aspect (NSSRG confirmation for S-NSSAI in Pending NSSAI at UE). [Figure 2] Figure 2 is a signaling diagram of a second example of the first aspect (confirmation of NSSRG for S-NSSAI in pending NSSAI in AMF). [Figure 3] Figure 3 is a signaling diagram of a first example of the second aspect (NSSRG confirmation for S-NSSAI in pending NSSAI for other access in AMF). [Figure 4]FIG. 4 is a diagram showing an outline of the system. [Figure 5] FIG. 5 is a block diagram illustrating a User Equipment (UE). [Figure 6] FIG. 6 is a block diagram illustrating an (R)AN node. [Figure 7] FIG. 7 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 8] FIG. 8 is a block diagram showing a radio unit (RU). [Figure 9] FIG. 9 is a block diagram showing a distributed unit (DU). [Figure 10] FIG. 10 is a block diagram showing a centralized unit (CU). [Figure 11] FIG. 11 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 12] FIG. 12 is a block diagram illustrating a Policy Control Function (PCF). [Figure 13] FIG. 13 is a block diagram illustrating the Authentication Server Function (AUSF). [Figure 14] FIG. 14 is a block diagram illustrating Unified Data Management (UDM). [Figure 15] FIG. 15 is a block diagram illustrating a Network Slice-Specific Authentication and Authorization Function (NSSAAF). DETAILED DESCRIPTION OF THE INVENTION

[0013] <abbreviation> For purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following apply: Abbreviations defined in this specification take precedence over the definition of the same abbreviation in Non-Patent Document 1 if the same abbreviation appears in that document.

[0014] 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-NG Non-Geographically selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function 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 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 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 InterWorking 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 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 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 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 SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name. SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SSC Session and Service Continuity SSCMSP Session and Service Continuity 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 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 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 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

[0015] <Definition> For purposes of this specification, the terms and definitions given in Non-Patent Document 1 and the following apply: Terms defined in this specification take precedence over the definition of the same term in Non-Patent Document 1, if any.

[0016] <General Overview> Those skilled in the art will appreciate that elements in the figures may be shown in simplified form and not necessarily drawn to scale. Furthermore, with respect to the structure of a device, one or more components of the device may be represented by conventional symbols in the figures, and the figures may show only certain details relevant to understanding aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0017] To promote an understanding of the principles of the present disclosure, reference will now be made to embodiments illustrated in the drawings and specific language will be used to describe those principles. It will nevertheless be understood that no limitation on the scope of the present disclosure is intended thereby. Such alterations 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.

[0018] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method comprising a list of steps not only includes those steps, but may also include other steps not expressly listed or inherent in such process or method. Similarly, the reference to one or more devices, entities, subsystems, elements, structures, or components preceded by "comprises" does not, absent further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the phrases "in an embodiment," "in another embodiment," and similar terms may all refer to the same embodiment, but do not necessarily do so.

[0019] 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.

[0020] 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 "the" include plural references unless the context clearly dictates otherwise.

[0021] As used herein, information refers to data and knowledge, as data is meaningful information and represents values ​​attributed to parameters. Furthermore, knowledge refers to an understanding of an abstract or concrete concept. It should be noted that this exemplary system is simplified to facilitate explanation of the subject matter of the present disclosure and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are contemplated as being within the scope of the present disclosure.

[0022] Each aspect and the elements included in each aspect described below can be implemented independently or in combination with each other, and the aspects include different novel features, and therefore contribute to achieving different objectives or solving different problems and achieving different advantages.

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

[0024] A method for a user equipment (UE) according to an example aspect of the present disclosure includes receiving a message including a reserved Network Slice Selection Assistance Information (NSSAI). The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). If a registration procedure using the second S-NSSAI is triggered, the method includes verifying whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. If the first S-NSSAI and the second S-NSSAI are associated with at least one common NSSRG value, the method includes transmitting a registration request message including the second S-NSSAI.

[0025] A method of a communications apparatus according to an exemplary aspect of the present disclosure includes transmitting a first message including a reserved Network Slice Selection Assistance Information (NSSAI). The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a registration request message including a Requested NSSAI. The Requested NSSAI includes a second S-NSSAI. The method includes verifying whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. If the first S-NSSAI and the second S-NSSAI are not associated with at least one common NSSRG value, the method includes transmitting a second message including a Configured NSSAI.

[0026] 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 is configured to receive a message including reserved Network Slice Selection Assistance Information (NSSAI). The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to, when a registration procedure using the second S-NSSAI is triggered, verify whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The at least one hardware processor is configured to, when the first S-NSSAI and the second S-NSSAI are associated with at least one common NSSRG value, transmit a registration request message including the second S-NSSAI.

[0027] 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 is configured to transmit a first message including a reserved Network Slice Selection Assistance Information (NSSAI). The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to receive a registration request message including a requested NSSAI. The requested NSSAI includes a second S-NSSAI. The at least one hardware processor is configured to verify whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The at least one hardware processor is configured to transmit a second message including the configuration NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with at least one common NSSRG value.

[0028] <First aspect> The Network Slice Simultaneous Registration Group (NSSRG) is introduced in 5GS in Release 17. The NSSRG function provides 3GPP operators with a mechanism to restrict the combination of network slices that can be simultaneously registered to an end user. According to current 3GPP specifications, NSSRG information (e.g., information indicating or related to an NSSRG) is provided from 5GC to the UE, and the UE selects a network slice based on the NSSRG information. However, the 3GPP specifications are unclear regarding what 5GC should do if the UE retains an old configured network slice (e.g., an old configured NSSAI) and / or old NSSRG information. In this case, the NSSRG function does not function properly.

[0029] For example, this aspect focuses on a problem when AMF 70 detects, based on NSSRG information, that an S-NSSAI in a Requested NSSAI in a Registration Request message from UE 3 includes an S-NSSAI that is not compatible with an S-NSSAI in a Pending NSSAI at AMF 70. For example, this aspect provides a solution to this problem.

[0030] For example, when the S-NSSAI in the Requested NSSAI and the S-NSSAI in the Reserved NSSAI cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of the configuration NSSAI and NSSRG information in the UE 3 is not up to date. For example, the AMF 70 detects that at least one of the configuration NSSAI and NSSRG information in the UE 3 is old. In this case, the AMF 70 provides at least one of the configuration NSSAI and NSSRG information to the UE 3 to refresh the data in the UE 3.

[0031] For example, the present embodiment also discloses a method for processing a registration procedure when the S-NSSAI of the Requested NSSAI in the Registration Request message does not belong to or share any common NSSRG values ​​with the S-NSSAI in the Reserved NSSAI.

[0032] For example, the present embodiment also discloses a method for processing a registration procedure when the S-NSSAI of the requesting NSSAI in the registration request message belongs to or shares at least one common NSSRG value with the S-NSSAI in the pending NSSAI.

[0033] <First Example of First Aspect> A first example of the first aspect discloses a method in which UE3 checks whether an S-NSSAI in a reserved NSSAI and an S-NSSAI in a requested NSSAI in a registration request message belong to or share at least one common NSSRG value.

[0034] The detailed process of the first example of the first embodiment is described below with reference to FIG.

[0035] 1) UE3 is configured to support the NSSRG procedure. UE3 initiates the registration procedure to register S-NSSAI1 and S-NSSAI2 by sending a registration request message with the requested NSSAIs set to S-NSSAI1 and S-NSSAI2. The requested NSSAIs may include one or more S-NSSAIs. For example, S-NSSAI1 follows the NSSAA procedure.

[0036] 2) When AMF 70 receives a registration request message including S-NSSAI1 and S-NSSAI2 in the request NSSAI, AMF 70 identifies that S-NSSAI1 is subject to NSSAA procedures. For example, AMF 70 may identify that S-NSSAI1 is subject to NSSAA procedures based on a local configuration in AMF 70 or an operator policy, or information received from another network node. AMF 70 marks S-NSSAI1 as a reserved NSSAI, AMF 70 determines that S-NSSAI2 is allowed to be used for UE3, and AMF 70 sends a registration accept message including S-NSSAI1 in the reserved NSSAI and S-NSSAI2 in the allowed NSSAI. The registration accept message may additionally include at least one of a configured NSSAI and NSSRG information. The NSSRG information may be information indicating an NSSRG or information related to an NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) shares an NSSRG value or NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG. The NSSRG information may be referred to as an NSSRG.

[0037] AMF 70 may recognize that UE 3 has a reserved NSSAI that includes S-NSSAI1.

[0038] 3) Upon receiving the registration accept message, UE3 stores the pending NSSAI and the allowed NSSAI. If the registration accept message includes at least one of the configured NSSAI and the NSSRG information, UE3 stores at least one of the configured NSSAI and the NSSRG information. UE3 sends a registration complete message. For example, when UE3 receives the registration accept message, UE3 may send a registration complete message.

[0039] 4a) In step 4a, UE3 has S-NSSAI1 in its reserved NSSAI. For example, UE3 may have a reserved NSSAI that includes S-NSSAI1. In addition, for example, UE3 may have an authorized NSSAI that includes S-NSSAI2.

[0040] 4b) In step 4b, AMF70 has S-NSSAI1 in its reserved NSSAI. For example, AMF70 may have a reserved NSSAI that includes S-NSSAI1.

[0041] 5) AMF 70 initiates the NSSAA procedure for S-NSSAI 1 as defined in Non-Patent Document 3.

[0042] 6) UE3 gets a trigger to register S-NSSAI2. UE3 checks the NSSRG information regarding whether S-NSSAI1 and S-NSSAI2 in the suspended NSSAIs at UE3 share at least one common NSSRG value (e.g., UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, or UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value, or UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG). UE3 keeps S-NSSAI1 in the suspended NSSAI during the NSSAA procedure. Steps 6 to 8 may be performed during the NSSAA procedure for S-NSSAI1. Determining whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value may be referred to as determining whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value.

[0043] 7) If S-NSSAI1 and S-NSSAI2 in the pending NSSAIs at UE3 belong to at least one common NSSRG value (e.g., if S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or if S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, or if S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, or if S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value), UE3 initiates the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI2. UE3 may initiate the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI1 and S-NSSAI2.

[0044] For example, if S-NSSAI1 is associated with NSSRG1 (or NSSRG value 1) and S-NSSAI2 is associated with NSSRG1 (or NSSRG value 1), UE3 determines that S-NSSAI1 and S-NSSAI2 belong to, share, or are associated with a common NSSRG (or common NSSRG value) and initiates the registration procedure by sending a registration request message including a request NSSAI that includes S-NSSAI2.

[0045] If S-NSSAI1 and S-NSSAI2 in the pending NSSAIs at UE3 do not belong to a common NSSRG value (for example, if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG, or if S-NSSAI1 and S-NSSAI2 do not share a common NSSRG value, or if S-NSSAI1 and S-NSSAI2 do not share a common NSSRG, or if S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG value), UE3 has several options to choose from.

[0046] For example, if S-NSSAI1 is associated with NSSRG1 (or NSSRG value 1) and S-NSSAI2 is associated with NSSRG2 (or NSSRG value 2), UE3 may determine that S-NSSAI1 and S-NSSAI2 do not belong to, share, or are not associated with a common NSSRG (or common NSSRG value) and may take one of the following options:

[0047] See below for options that UE3 does:

[0048] -Since S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG value, UE3 does not initiate the registration procedure (e.g., UE3 does not send a registration request message including a requested NSSAI set in S-NSSAI2).

[0049] UE3 initiates the registration procedure by sending a registration request message including a requested NSSAI configured with another S-NSSAI that belongs to a common NSSRG value with S-NSSAI1. For example, UE3 may initiate the registration procedure by sending a registration request message including a requested NSSAI configured with S-NSSAI3 that belongs to (or shares) a common NSSRG value with S-NSSAI1 and is different from S-NSSAI2. UE3 may select another S-NSSAI from the configured NSSAIs based on the NSSRG information.

[0050] UE3 aborts the NSSAA procedure for S-NSSAI1, and after the completion of the abort of the NSSAA procedure for S-NSSAI1, UE3 initiates the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI2. For example, UE3 may initiate the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI2 after the completion of the abort of the NSSAA procedure for S-NSSAI1. For example, UE3 may remove S-NSSAI1 from the pending NSSAIs and set S-NSSAI1 to a rejected NSSAI after the completion of the abort of the NSSAA procedure for S-NSSAI1.

[0051] UE3 waits for the completion of the NSSAA procedure for S-NSSAI1. After the completion of the NSSAA procedure for S-NSSAI1, UE3 initiates the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI2. That is, S-NSSAI1 is not included in the requested NSSAI. This means that UE3 removes S-NSSAI1 from the allowed NSSAIs in UE3. Alternatively, UE3 removes S-NSSAI1 from the allowed NSSAIs in UE3 after the completion of the NSSAA procedure for S-NSSAI1. For example, if UE3 receives an allowed NSSAI including S-NSSAI1 after the completion of the NSSAA procedure for S-NSSAI1, UE3 may abandon the allowed NSSAI, remove S-NSSAI1 from the allowed NSSAI, or set S-NSSAI1 to a rejected NSSAI.

[0052] 8) The registration procedure continues from step 4 in section 4.2.2.2.2 of Non-Patent Document 3.

[0053] In step 7, if UE3 initiates the registration procedure by sending a registration request message including a request NSSAI set in S-NSSAI2, the registration procedure may continue from step 4 in section 4.2.2.2.2 of non-patent document 3.

[0054] In step 7, if UE3 initiates the registration procedure by sending a registration request message including a requested NSSAI configured with another S-NSSAI belonging to a common NSSRG value with S-NSSAI1, the registration procedure may continue from step 4 in section 4.2.2.2.2 of non-patent document 3.

[0055] In step 7, if UE3 initiates the registration procedure by sending a registration request message including the requested NSSAI set in S-NSSAI2 after completing the abort of the NSSAA procedure for S-NSSAI1, the registration procedure may continue from step 4 in section 4.2.2.2.2 of non-patent document 3.

[0056] In step 7, if UE3 initiates the registration procedure by sending a registration request message including a requested NSSAI set in S-NSSAI2 after completing the NSSAA procedure for S-NSSAI1, the registration procedure may continue from step 4 in section 4.2.2.2.2 of non-patent document 3.

[0057] For example, if S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG values, UE 3 may detect or determine that at least one of the configuration NSSAI and NSSRG information at UE 3 is not up to date. In this case, UE 3 may request at least one of the latest configuration NSSAI and latest NSSRG information from the 5GC and receive at least one of the latest configuration NSSAI and latest NSSRG information.

[0058] According to a first example of the first aspect, for example, a solution to an unclear description in the 3GPP specifications regarding how to process NSSRGs can be provided.

[0059] According to a first example of the first aspect, for example, a method for processing a registration procedure when the S-NSSAI of a Requested NSSAI in a Registration Request message does not belong to or share any common NSSRG values ​​with the S-NSSAI in the Reserved NSSAI may be provided.

[0060] According to a first example of the first aspect, for example, a method for processing a registration procedure when an S-NSSAI of a Requested NSSAI in a Registration Request message belongs to or shares at least one common NSSRG value with an S-NSSAI in a Reserved NSSAI may be provided.

[0061] <Modification 1 of the first example of the first aspect> In one example, in step 1, UE 3 sends only S-NSSAI1 in a registration request message. In this case, UE 3 and AMF 70 have S-NSSAI1 in their reserved NSSAIs. In step 6, UE 3 may receive a trigger to register with S-NSSAI2 and perform the process in step 6. For example, UE 3 may select an S-NSSAI from the configuration NSSAIs and include the selected S-NSSAI in the request NSSAI in the registration request message. For example, a subset of the configuration NSSAIs may be provided in the request NSSAI. For example, the subset of the configuration NSSAIs may be the request NSSAI. Variant 1 of the first example of the first aspect may be applied to the second example of the first aspect below. For example, if UE 3 has reserved NSSAIs, the subset of the configuration NSSAIs provided in the request NSSAI and the reserved NSSAIs may be associated with at least one common NSSRG value.

[0062] For example, when UE3 initiates a registration procedure (e.g., in step 6), UE3 may determine or confirm whether UE3 has a pending NSSAI. When UE3 determines or confirms that UE3 has a pending NSSAI and UE3 initiates the registration procedure using the request NSSAI (e.g., UE3 initiates the registration procedure by sending a registration request message including the request NSSAI), UE3 may determine or confirm whether the subset of configuration NSSAIs provided in the request NSSAI and the pending NSSAI are associated with at least one common NSSRG value.

[0063] If the UE 3 determines or confirms (e.g., in step 6) that the subset of configured NSSAIs provided in the request NSSAI and the reserved NSSAI are associated with at least one common NSSRG value, the UE 3 may perform a registration procedure using the request NSSAI (e.g., the UE 3 may send a registration request message including the request NSSAI. This process may be performed in step 7). The following process (or subsequent processes) may be the same as step 8 in Figure 1.

[0064] <Second Example of First Aspect> A second example of the first aspect discloses a method in which the AMF 70 checks whether the S-NSSAI in the reserved NSSAI and the S-NSSAI in the request NSSAI in the registration request message share at least one common NSSRG value. If the S-NSSAI in the reserved NSSAI and the S-NSSAI in the request NSSAI do not share any common NSSRG value, the AMF 70 provides the configuration NSSAI and NSSRG to the UE 3 to refresh the configuration data in the UE 3.

[0065] The detailed process of the second example of the first embodiment is described below with reference to FIG.

[0066] 1) UE3 is configured to support the NSSRG procedure. UE3 initiates the registration procedure to register S-NSSAI1 and S-NSSAI2 by sending a Registration Request message with Requested NSSAIs set to S-NSSAI1 and S-NSSAI2. The Requested NSSAIs may include one or more S-NSSAIs. For example, S-NSSAI1 follows the NSSAA procedure.

[0067] 2) When AMF 70 receives a registration request message including S-NSSAI1 and S-NSSAI2 in the request NSSAI, AMF 70 identifies that S-NSSAI1 is subject to NSSAA procedures. For example, AMF 70 may identify that S-NSSAI1 is subject to NSSAA procedures based on a local configuration in AMF 70 or an operator policy, or information received from another network node. AMF 70 marks S-NSSAI1 as a reserved NSSAI, AMF 70 determines that S-NSSAI2 is authorized for use for UE3, and AMF 70 sends a registration accept message including S-NSSAI1 in the reserved NSSAI and S-NSSAI2 in the authorized NSSAI. The registration accept message may additionally include at least one of a configured NSSAI and NSSRG information. The NSSRG information may be information indicating an NSSRG or information related to an NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) shares an NSSRG value or NSSRG. For example, the UE 3 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG.

[0068] The AMF 70 may store NSSRG information. For example, the AMF 70 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the AMF 70 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) shares an NSSRG value or NSSRG. For example, the AMF 70 may understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG.

[0069] The AMF 70 may pre-store the NSSRG information, may receive the NSSRG information from other network nodes, or may create the NSSRG information based on local configuration or operator policy in the AMF 70, or information received from other network nodes.

[0070] AMF 70 may recognize that UE 3 has a reserved NSSAI that includes S-NSSAI1.

[0071] 3) Upon receiving the registration accept message, UE3 stores the pending NSSAI and the allowed NSSAI. If the registration accept message includes at least one of the configured NSSAI and the NSSRG information, UE3 stores at least one of the configured NSSAI and the NSSRG information. UE3 sends a registration complete message. For example, when UE3 receives the registration accept message, UE3 may send a registration complete message.

[0072] 4a) In step 4a, UE3 has S-NSSAI1 in its reserved NSSAI. For example, UE3 may have a reserved NSSAI that includes S-NSSAI1. In addition, for example, UE3 may have an authorized NSSAI that includes S-NSSAI2.

[0073] 4b) In step 4b, AMF 70 stores S-NSSAI1 in a reserved NSSAI. For example, AMF 70 may have a reserved NSSAI that includes S-NSSAI1.

[0074] 5) AMF 70 initiates the NSSAA procedure for S-NSSAI 1 as defined in Non-Patent Document 3.

[0075] 6) UE3 gets a trigger to register S-NSSAI2. UE3 starts the registration procedure by sending a registration request message including the request NSSAI set to S-NSSAI2.

[0076] UE3 keeps S-NSSAI1 as a pending NSSAI during the NSSAA procedure. Steps 6 to 9 may be performed during the NSSAA procedure for S-NSSAI1.

[0077] 7) Upon receiving a registration request message from UE3, AMF70 checks whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value (for example, AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value, AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value). Checking whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value may be referred to as checking whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value.

[0078] Depending on the outcome of the check in step 7, one of steps 8a, 8b, 8c, and 8d is performed.

[0079] 8a) If S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value (e.g., if S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, or if S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value, or if S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or if S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value), and if S-NSSAI2 is authorized for use for UE3, AMF70 sends a registration accept message to UE3 including at least one of the NSSRG information, S-NSSAI2 set as the authorized NSSAI, and S-NSSAI1 set as the suspended NSSAI. The registration accept message may also include a configured NSSAI. For example, AMF 70 may send a registration accept message to UE 3 including NSSRG information, an allowed NSSAI including S-NSSAI2, and a pending NSSAI including S-NSSAI1.

[0080] The UE 3 may store the granted NSSAI and the pending NSSAI. For example, the UE 3 may use the received configuration NSSAI and / or the received NSSRG information to refresh or update data at the UE 3 (e.g., the configuration NSSAI and NSSRG information previously stored at the UE 3).

[0081] 8b) If S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (for example, if S-NSSAI1 and S-NSSAI2 do not share a common NSSRG, or if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG value, or if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG, or if S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG value), and if S-NSSAI2 is authorized for use for UE3 and AMF70 determines that S-NSSAI2 has a higher priority than S-NSSAI1 for UE3, AMF70 sends a registration accept message to UE3 including at least one of the configured NSSAI, NSSRG information, S-NSSAI2 set to the allowed NSSAI, and S-NSSAI1 set to the rejected NSSAI. For example, AMF 70 may send a registration accept message to UE 3 including a configured NSSAI, NSSRG information, an allowed NSSAI including S-NSSAI2, and a rejected NSSAI including S-NSSAI1. For example, AMF 70 may store information related to the priority of the S-NSSAI or may receive that information from another network node, and AMF 70 may determine the priority of the S-NSSAI based on the information. For example, AMF 70 may determine the priority of the S-NSSAI based on a local configuration of AMF 70 or an operator policy.

[0082] When the UE 3 receives a Registration Accept message from the AMF 70 including the S-NSSAI1 in the Rejected NSSAI because the S-NSSAI1 is in the Pending NSSAI stored in the UE 3, the UE 3 removes the S-NSSAI1 from the Pending NSSAI and stores the S-NSSAI1 in the Rejected NSSAI. In addition, the UE 3 may initiate an abort process for the ongoing NSSAA procedure for the S-NSSAI1. The UE 3 may store the S-NSSAI2 in the Allowed NSSAI. For example, the UE 3 may use at least one of the received Configuration NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g., the Configuration NSSAI and NSSRG information previously stored in the UE 3).

[0083] For example, UE3 may maintain an ongoing NSSAA procedure for S-NSSAI1. In this case, if UE3 receives an Authorized NSSAI including S-NSSAI1 after completing the NSSAA procedure for S-NSSAI1, UE3 may not update the Authorized NSSAI at UE3 based on the received Authorized NSSAI including S-NSSAI1. In this case, UE3 may discard the received Authorized NSSAI and maintain S-NSSAI1 as a Rejected NSSAI.

[0084] 8c) If S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (for example, if S-NSSAI1 and S-NSSAI2 do not share a common NSSRG, or if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG value, or if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG, or if S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG value), and if S-NSSAI2 is authorized for use for UE3 and AMF70 determines that S-NSSAI1 has a higher priority than S-NSSAI2 for UE3, AMF70 sends a registration accept message to UE3 including at least one of the configured NSSAI, NSSRG information, S-NSSAI2 set to rejected NSSAI, and S-NSSAI1 set to suspended NSSAI. For example, the AMF 70 may send a registration accept message to the UE 3 including the configured NSSAI, the NSSRG information, a rejected NSSAI including S-NSSAI2, and a pending NSSAI including S-NSSAI1.

[0085] When receiving a registration accept message from AMF70 including S-NSSAI2 in the Rejected-NSSAI because S-NSSAI2 is in the Allowed-NSSAIs stored in UE3, UE3 removes S-NSSAI2 from the Allowed-NSSAIs and stores S-NSSAI2 in the Rejected-NSSAI. UE3 may store S-NSSAI1 in the Reserved-NSSAI. For example, UE3 may use at least one of the received Configuration-NSSAI and the received NSSRG information to refresh or update data in UE3 (e.g., Configuration-NSSAI and NSSRG information previously stored in UE3).

[0086] 8d) If S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (e.g., if S-NSSAI1 and S-NSSAI2 do not share a common NSSRG, if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG value, if S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG, or if S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG value), the AMF 70 sends a Registration Reject message to the UE 3, including at least one of the configured NSSAI, the NSSRG information, and S-NSSAI1 and S-NSSAI2 set as the rejected NSSAI. For example, the AMF 70 may send a Registration Reject message to the UE 3, including the configured NSSAI, the NSSRG information, and a rejected NSSAI including S-NSSAI1 and S-NSSAI2.

[0087] Because S-NSSAI1 is in the pending NSSAIs at UE3 and S-NSSAI2 is in the permitted NSSAIs at UE3, upon receiving a Registration Reject message from AMF70 including S-NSSAI1 and S-NSSAI2 in the Rejected NSSAI, UE3 removes S-NSSAI1 from the pending NSSAIs, removes S-NSSAI2 from the permitted NSSAIs, and stores S-NSSAI1 and S-NSSAI2 in the Rejected NSSAIs. In addition, UE3 initiates an abort process for the ongoing NSSAA procedure for S-NSSAI1. For example, UE3 may use at least one of the received Configuration NSSAI and the received NSSRG information to refresh or update data at UE3 (e.g., Configuration NSSAI and NSSRG information previously stored at UE3).

[0088] For example, UE3 may maintain an ongoing NSSAA procedure for S-NSSAI1. In this case, if UE3 receives an Authorized NSSAI including S-NSSAI1 after completing the NSSAA procedure for S-NSSAI1, UE3 may not update the Authorized NSSAI at UE3 based on the received Authorized NSSAI including S-NSSAI1. In this case, UE3 may discard the received Authorized NSSAI and maintain S-NSSAI1 as a Rejected NSSAI.

[0089] 9) If a registration acknowledgement message is sent from AMF 70 to UE 3 in step 8, UE 3 may send a registration completion message to AMF 70 to complete the registration procedure.

[0090] For example, if AMF 70 determines that S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG values, AMF 70 may detect or determine that at least one of the configured NSSAI and NSSRG information in UE 3 is not up to date. In this case, AMF 70 may send a registration accept message or a registration reject message as referred to in step 8b, 8c, or 8d.

[0091] The configuration NSSAI sent in step 8a, 8b, 8c, or 8d may be the same as the configuration NSSAI sent in step 2.

[0092] The configuration NSSAI sent in step 8a, 8b, 8c, or 8d may be different from the configuration NSSAI sent in step 2. In this case, AMF 70 may create a new configuration NSSAI or update the configuration NSSAI sent in step 2 based on a local configuration or an operator's policy in AMF 70, or information received from other network nodes, and may send the new or updated configuration NSSAI in step 8a, 8b, 8c, or 8d. AMF 70 may request a new or updated configuration NSSAI from other network nodes, and may receive the new or updated configuration NSSAI from other network nodes. AMF 70 may then send the new or updated configuration NSSAI in step 8a, 8b, 8c, or 8d.

[0093] The NSSRG information sent in step 8a, 8b, 8c, or 8d may be the same as the NSSRG information sent in step 2.

[0094] The NSSRG information sent in step 8a, 8b, 8c, or 8d may be different from the NSSRG information sent in step 2. In this case, AMF 70 may create new NSSRG information or update the NSSRG information sent in step 2 based on local configuration or operator policy in AMF 70, or information received from other network nodes, and may send the new or updated NSSRG information in step 8a, 8b, 8c, or 8d.

[0095] The AMF 70 may request new or updated NSSRG information from other network nodes, and may receive new or updated NSSRG information from other network nodes. The AMF 70 may then transmit the new or updated NSSRG information in steps 8a, 8b, 8c, or 8d.

[0096] For example, if UE3 has a reserved NSSAI and the S-NSSAI2 of the requested NSSAI in the registration request message and the reserved NSSAI (e.g., S-NSSAI1 in the reserved NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration accept message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration accept message).

[0097] For example, if AMF70 has a reserved NSSAI and the S-NSSAI2 of the requested NSSAI in the registration request message and the reserved NSSAI (e.g., S-NSSAI1 in the reserved NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration acceptation message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration acceptation message).

[0098] According to a second example of the first aspect, for example, a solution to an unclear description in the 3GPP specifications regarding how to process NSSRGs can be provided.

[0099] According to a second example of the first aspect, for example, a method for processing a registration procedure when the S-NSSAI of a Requested NSSAI in a Registration Request message does not belong to or share any common NSSRG values ​​with the S-NSSAI in the Reserved NSSAI can be provided.

[0100] According to a second example of the first aspect, for example, a method for processing a registration procedure when an S-NSSAI of a Requested NSSAI in a Registration Request message belongs to or shares at least one common NSSRG value with an S-NSSAI in a Reserved NSSAI may be provided.

[0101] For example, if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, at least one of the configuration NSSAI and NSSRG information stored in UE 3 may not be up to date. By checking whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, AMF 70 can detect or determine whether at least one of the configuration NSSAI and NSSRG information in UE 3 may not be up to date (or may be out of date). If AMF 70 determines that S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (e.g., if AMF 70 detects or determines that at least one of the configuration NSSAI and NSSRG information in UE 3 may not be up to date), AMF 70 sends at least one of the configuration NSSAI and NSSRG information to refresh or update at least one of the configuration NSSAI and NSSRG information stored in UE 3. According to a second example of the first aspect, for example, up-to-date information for performing the NSSRG function (e.g., configured NSSAI and NSSRG information) is provided from AMF70 to UE3 when S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, and the NSSRG function can function properly.

[0102] <Modification 1 of the second example of the first aspect> In steps 8b and 8d, the AMF 70 may initiate an AMF triggered Slice-Specific Authorization Revocation procedure. The AMF triggered Slice-Specific Authorization Revocation procedure may be one of the procedures outlined below:

[0103] The AMF 70 sends an AAA protocol Revoke Auth request message to the NSSAAF 76, including the S-NSSAI1 and the GPSI for the UE 3 requesting revocation of authorization for the S-NSSAI1.

[0104] AMF 70 sends a message to the AAA server for S-NSSAI1 including S-NSSAI1 and the GPSI for UE3 requesting revocation of authorization for S-NSSAI1.

[0105] <Modification 2 of the second example of the first aspect> For example, AMF70 may recognize the contents of the configuration NSSAI for UE3, or that UE3 has a configuration NSSAI. For example, when AMF70 receives a registration request message including a request NSSAI from UE3 (e.g., in step 6), AMF70 may determine or confirm (e.g., in step 7) whether a subset of the configuration NSSAI provided in the request NSSAI and a reserved NSSAI (e.g., a reserved NSSAI for UE3) are associated with at least one common NSSRG value. In response to the determination or confirmation, AMF70 may perform one of steps 8a to 8d. For example, when AMF70 determines that the subset of the configuration NSSAI provided in the request NSSAI and the reserved NSSAI are associated with at least one common NSSRG value, AMF70 may perform the process in step 8a (e.g., AMF70 may send a registration accept message in step 8a). For example, if AMF70 determines that the subset of configured NSSAIs provided in the request NSSAI and the reserved NSSAI do not relate to at least one common NSSRG value, AMF70 may perform a process in one of steps 8b to 8d (for example, AMF70 may send a registration accept message in step 8b, AMF70 may send a registration accept message in step 8c, or AMF70 may send a registration reject message in step 8d).

[0106] <Second aspect> The Network Slice Simultaneous Registration Group (NSSRG) is introduced in 5GS in Release 17. The NSSRG function provides 3GPP operators with a mechanism to restrict the combination of network slices that can be simultaneously registered to an end user. According to current 3GPP specifications, NSSRG information (e.g., information indicating or related to an NSSRG) is provided from 5GC to the UE, and the UE selects a network slice based on the NSSRG information. However, the 3GPP specifications are unclear regarding what 5GC should do if the UE retains an old configured network slice (e.g., an old configured NSSAI) and / or old NSSRG information. In this case, the NSSRG function does not function properly.

[0107] For example, this aspect focuses on a problem when AMF 70 detects, based on NSSRG information, that an S-NSSAI in a request NSSAI in a registration request message from UE 3 includes an S-NSSAI that cannot coexist with an S-NSSAI in an allowed NSSAI for another access type in AMF 70. For example, this aspect provides a solution to this problem.

[0108] For example, when the S-NSSAI in the request NSSAI and the S-NSSAI in the authorization NSSAI for another access type cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of the configuration NSSAI and NSSRG information in the UE 3 is not up to date. For example, the AMF 70 detects that at least one of the configuration NSSAI and NSSRG information in the UE 3 is old. In this case, the AMF 70 provides the configuration NSSAI information and NSSRG information to the UE 3 to refresh the data in the UE 3.

[0109] For example, the present embodiment also discloses a method for processing a registration procedure when the S-NSSAI of a requesting NSSAI in a registration request message does not belong to or share any common NSSRG values ​​with the S-NSSAI in an authorized NSSAI for another access type.

[0110] <First example of the second aspect> A first example of the second aspect discloses a method in which the AMF 70 checks whether an S-NSSAI in an authorized NSSAI in one access type and an S-NSSAI in a requested NSSAI in a registration request message in another access type share at least one common NSSRG value. If the S-NSSAI in the authorized NSSAI in one access and the S-NSSAI in the requested NSSAI in another access do not share a common NSSRG value, the AMF 70 sends a registration accept message including the configuration NSSAI and NSSRG information to the UE 3 to refresh the configuration data in the UE 3.

[0111] The detailed process of the first example of the second embodiment is described below with reference to FIG.

[0112] 1) UE3 is registered in one access (e.g., 3GPP access 501), and S-NSSAI1 is in the authorized NSSAI in UE3. For example, UE3 has an authorized NSSAI including S-NSSAI1 for 3GPP access. For example, AMF70 has an authorized NSSAI including S-NSSAI1 for 3GPP access. UE3 is configured to perform a registration procedure in one access (e.g., 3GPP access) and another access (e.g., non-3GPP access 502). For example, UE3 and AMF70 may perform a registration procedure using S-NSSAI1 in 3GPP access, and UE3 and AMF70 may have an authorized NSSAI including S-NSSAI1. AMF70 may recognize that UE3 has an authorized NSSAI including S-NSSAI1.

[0113] 2) UE3 gets a trigger for registration procedure for S-NSSAI2 in another access (e.g., non-3GPP access 502 or N3GPP access 502).

[0114] 3) In non-3GPP access, UE3 sends a registration request message including S-NSSAI2 in the request NSSAI.

[0115] 4) Upon receiving the registration request message, AMF70 checks whether S-NSSAI1, which is in the allowed NSSAIs in 3GPP access, and S-NSSAI2, which is in the requested NSSAI in the registration request message, belong to at least one common NSSRG value (for example, AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, UE3 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or AMF70 checks based on NSSRG information whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value).

[0116] The AMF 70 may pre-store the NSSRG information, may receive the NSSRG information from other network nodes, or may create the NSSRG information based on local configuration or operator policy in the AMF 70, or information received from other network nodes.

[0117] For example, AMF 70 may understand which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG based on the NSSRG information. For example, AMF 70 may understand which network slice (e.g., S-NSSAI) shares an NSSRG value or NSSRG based on the NSSRG information. For example, AMF 70 may understand which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG based on the NSSRG information.

[0118] Depending on the outcome of the check, there are two options:

[0119] Option 1: This is an option in which AMF70 rejects the registration request message because there is no common NSSRG value between S-NSSAI1 in the requesting NSSAI and S-NSSAI2 in the authorized NSSAI in 3GPP access.

[0120] 5a) The AMF 70 sends a registration reject message including at least one of the configuration NSSAI, the NSSRG information, and the S-NSSAI2 set as the rejected NSSAI to the UE 3. For example, if the AMF 70 determines that the S-NSSAI1 and the S-NSSAI2 do not belong to or share a common NSSRG or a common NSSRG value (or if the AMF 70 determines that the S-NSSAI1 and the S-NSSAI2 are not associated with any common NSSRG or any common NSSRG value), the AMF 70 may send a registration reject message including the configuration NSSAI, the NSSRG information, and the rejected NSSAI including the S-NSSAI2.

[0121] Upon receiving the registration reject message, the UE 3 stores at least one of the configuration NSSAI, the NSSRG information, and the S-NSSAI2 set to the reject NSSAI. For example, the UE 3 may use the received configuration NSSAI and / or the received NSSRG information to refresh or update data at the UE 3 (e.g., the configuration NSSAI and NSSRG information previously stored at the UE 3).

[0122] Option 2: This is an option where AMF 70 approves a registration request with S-NSSAI2. When S-NSSAI2 is approved, AMF 70 updates S-NSSAI1 in non-3GPP access to be rejected because there is no common NSSRG value between S-NSSAI1 and S-NSSAI2.

[0123] 5b) The AMF 70 sends a registration accept message including the configured NSSAI, NSSRG information, and S-NSSAI2 set as the authorized NSSAI to the UE 3. For example, if the AMF 70 determines that the S-NSSAI1 and S-NSSAI2 do not belong to or share a common NSSRG or common NSSRG value (or if the AMF 70 determines that the S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG or any common NSSRG value), the AMF 70 may send a registration accept message including the configured NSSAI, NSSRG information, and an authorized NSSAI including the S-NSSAI2. For example, the AMF 70 may send a registration accept message in non-3GPP access.

[0124] Upon receiving the registration accept message, the UE 3 stores at least one of the configuration NSSAI, the NSSRG information, and the S-NSSAI2 set to the authorized NSSAI. For example, the UE 3 may use the received configuration NSSAI and / or the received NSSRG information to refresh or update data in the UE 3 (e.g., the configuration NSSAI and NSSRG information previously stored in the UE 3).

[0125] 6b) The UE 3 sends a registration complete message to the AMF 70. For example, if the UE 3 receives a registration accept message from the AMF 70, the UE 3 may send a registration complete message to the AMF 70. For example, the UE 3 may send the registration complete message in non-3GPP access.

[0126] 7b) The AMF 70 sends a UE Configuration Update Command message including at least one of the configuration NSSAI, the NSSRG information, and the S-NSSAI1 set to the reject NSSAI to the UE 3 in the 3GPP access. For example, the AMF 70 may send the UE Configuration Update Command message including the configuration NSSAI, the NSSRG information, and the reject NSSAI including the S-NSSAI1. For example, the AMF 70 may send the UE Configuration Update Command message after receiving the registration complete message in step 6b. For example, the AMF 70 may send the UE Configuration Update Command message after sending the registration accept message in step 5b.

[0127] Upon receiving the UE Configuration Update Command message, the UE3 stores at least one of the configuration NSSAI, the NSSRG information, and the S-NSSAI1 set to Reject NSSAI for 3GPP access.

[0128] For example, UE3 may remove S-NSSAI1 from the allowed NSSAI for 3GPP access and store a rejected NSSAI including S-NSSAI1 for 3GPP access.

[0129] For example, the UE3 may use at least one of the received configuration NSSAI and the received NSSRG information to refresh or update data in the UE3 (e.g., configuration NSSAI and NSSRG information previously stored in the UE3).

[0130] 8b) The UE 3 sends a UE Configuration Update Complete message to the AMF 70 in 3GPP access. For example, if the UE 3 receives a UE Configuration Update Command message from the AMF 70, the UE 3 may send a UE Configuration Update Complete message to the AMF 70.

[0131] The AMF70 may create a new configuration NSSAI or update a configuration NSSAI previously sent to the UE3 based on local configuration or operator policy in the AMF70 or information received from other network nodes, and may send the new or updated configuration NSSAI in steps 5a, 5b, or 7b.

[0132] The AMF 70 may request a new or updated configuration NSSAI from another network node, and may receive a new or updated configuration NSSAI from another network node. The AMF 70 may then send the new or updated configuration NSSAI in step 5a, 5b, or 7b.

[0133] For example, the NSSAI configured in step 5a or step 5b may be configured for non-3GPP access. For example, the NSSAI configured in step 5b and step 7b may be configured to be common to 3GPP access and non-3GPP access. For example, the NSSAI configured in step 5a and step 7b may be configured to be different between 3GPP access and non-3GPP access. For example, the NSSAI configured in steps 5a and 5b may be for non-3GPP access, and the NSSAI configured in step 7b may be for 3GPP access.

[0134] The AMF 70 may create new NSSRG information or update NSSRG information previously sent to the UE 3 based on local configuration or operator policy in the AMF 70, or information received from other network nodes, and may send the new or updated NSSRG information in steps 5a, 5b, or 7b.

[0135] The AMF 70 may request new or updated NSSRG information from other network nodes, and may receive new or updated NSSRG information from other network nodes. The AMF 70 may then transmit the new or updated NSSRG information in steps 5a, 5b, or 7b.

[0136] For example, the NSSRG information in step 5a or step 5b may be configured for non-3GPP access. For example, the NSSRG information in steps 5b and 7b may be configured to be common to 3GPP access and non-3GPP access. For example, the NSSRG information in steps 5a and 7b may be configured to be different between 3GPP access and non-3GPP access. For example, the NSSRG information in steps 5a and 5b may be for non-3GPP access, and the NSSRG information in step 7b may be for 3GPP access.

[0137] For example, in step 4, if AMF70 determines that S-NSSAI1 and S-NSSAI2 belong to a common NSSRG value, AMF70 may send a registration accept message to UE3 including an authorized NSSAI for non-3GPP access including S-NSSAI2.

[0138] For example, if UE3 already has an authorized NSSAI for 3GPP access and the S-NSSAI2 of the requested NSSAI in the registration request message and the authorized NSSAI (e.g., S-NSSAI1 in the authorized NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration accept message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration accept message).

[0139] For example, if AMF70 already has an authorized NSSAI for 3GPP access and the S-NSSAI2 of the requested NSSAI in the registration request message and the authorized NSSAI (e.g., S-NSSAI1 in the authorized NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration acceptation message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration acceptation message).

[0140] For example, if AMF70 already has an authorized NSSAI for 3GPP access, and the S-NSSAI2 of the requested NSSAI in the registration request message in non-3GPP access and the authorized NSSAI for 3GPP access (e.g., S-NSSAI1 in the authorized NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration acceptation message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration acceptation message).

[0141] For example, if UE3 (or AMF70) already has an authorized NSSAI for another access, and the requested NSSAI S-NSSAI2 in the registration request message in the current access and the authorized NSSAI for the other access (e.g., S-NSSAI1 in the authorized NSSAI) are not associated with any common NSSRG value, AMF70 may send a new configured NSSAI by using a registration rejection message or a registration acceptation message (or AMF70 may include the new configured NSSAI in the registration rejection message or the registration acceptation message).

[0142] The registration accept message in step 5b may include information indicating that a UE configuration update command message will be sent. If UE3 receives this information, UE3 may not send a registration request message including the request NSSAI including S-NSSAI1 or other NAS messages related to S-NSSAI1 in 3GPP access until UE3 receives the UE configuration update command message.

[0143] According to a first example of the second aspect, for example, a solution can be provided to an unclear description in the 3GPP specifications regarding how to process NSSRG.

[0144] According to a first example of the second aspect, for example, a method for processing a registration procedure can be provided when the S-NSSAI of a request NSSAI in a registration request message in one access does not belong to or share any common NSSRG values ​​with the S-NSSAI in an authorization NSSAI for another access.

[0145] According to a first example of the second aspect, for example, a method for processing a registration procedure when an S-NSSAI of a request NSSAI in a registration request message in one access belongs to or shares at least one common NSSRG value with an S-NSSAI in an authorization NSSAI for another access can be provided.

[0146] For example, if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, at least one of the configuration NSSAI and NSSRG information stored in UE 3 may not be up to date. By checking whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, AMF 70 can detect or determine whether at least one of the configuration NSSAI and NSSRG information in UE 3 may not be up to date (or may be out of date). If AMF 70 determines that S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (e.g., if AMF 70 detects or determines that at least one of the configuration NSSAI and NSSRG information in UE 3 may not be up to date), AMF 70 sends at least one of the configuration NSSAI and NSSRG information to refresh or update at least one of the configuration NSSAI and NSSRG information stored in UE 3. According to a first example of the second aspect, for example, up-to-date information for performing the NSSRG function (e.g., configured NSSAI and NSSRG information) is provided from AMF70 to UE3 when S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, and the NSSRG function can function properly.

[0147] <Modification 1 of the first example of the second aspect> This example describes a situation in which UE3 sends a registration request message to AMF70 in non-3GPP access while UE3 has an authorized NSSAI in 3GPP access, but similarly, the first example of the second aspect is effective for a situation in which UE3 sends a registration request message to AMF70 in 3GPP access while UE3 has an authorized NSSAI in non-3GPP access.

[0148] <Modification 2 of the first example of the second aspect> Steps 7b and 8b may be performed before steps 5b and 6b. Step 7b may be performed after step 5b. Step 5b may be performed after step 7b.

[0149] <System Overview> FIG. 4 shows a schematic diagram of a mobile (cellular or wireless) telecommunications system 1 to which the above aspects are applicable.

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

[0151] 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 as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0152] The (R)AN node 5 may be separated into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some aspects, each of the units may be connected to each other to form the (R)AN node 5 by employing an architecture such as that defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as the O-RU, O-DU, and O-CU, respectively.

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

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

[0155] In addition, the (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0156] The core network 7 may include logical nodes (or "functions") that support communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes, among other functions, control plane functions and user plane functions. Each function in a logical node may be considered a network function. A network function may be provided to another node by adapting a Service Based Architecture (SBA).

[0157] By applying network virtualization technologies such as those defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed as distributed, redundant, stateless, and scalable, providing services from several locations and providing several execution instances at each location.

[0158] The core network 7 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

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

[0160] The core network 7 also includes, among other things, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, an Authentication Server Function (AUSF) 74, a Unified Data Management (UDM) 75, and a Network Slice-Specific Authentication and Authorization Function (NSSAAF) 76. When a UE 3 roams into a visited Public Land Mobile Network (VPLMN), the home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionality of the SMF 71, UPF 72, and PCF 73 to the roaming-out UE 3.

[0161] The UE 3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5-to-(R)AN node interfaces (e.g., a so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (e.g., so-called core network nodes) via appropriate interfaces (e.g., a so-called "N2" / "N3" interface and / or the like). From the core network 7, a connection is also provided 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. If 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 that data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.

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

[0163] 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.

[0164] 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 hierarchical structure with RRC, PDCP, RLC, and MAC sublayers depending on the physical connection.

[0165] For example, the following messages are communicated in the RRC layer to support AS signaling:

[0166] - 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 aspects of the present disclosure, the following parameters may be included together in the RRC Setup Request message: --establishmentCause and ue-Identity. The ue-Identity may have the value of ng-5G-S-TMSI-Part1 or a random value.

[0167] RRC Setup Message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup message: --Master cell group (masterCellGroup) and radio bearer configuration (radioBearerConfig)

[0168] - 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 aspects of the present disclosure, the following parameters may be included together in the RRC Setup Complete message: --guami type (guami-Type), iab node indication (iab-NodeIndication), idle measurement available (idleMeasAvailable), mobility state (mobilityState), ng-5G-S-TMSI-Part2 (ng-5G-S-TMSI-Part2), registered AMF (registeredAMF), selected PLMN identity (selectedPLMN-Identity)

[0169] The UE 3 and the AMF 70 are connected via an appropriate interface (e.g., a so-called N1 interface and / or the like). 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 in 3GPP access and non-3GPP access. For example, the following messages are communicated on the N1 interface:

[0170] Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by 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 capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability IDID), Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.

[0171] Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration accept message: --5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature 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 de-registration timer value, T3502 value, Emergency number list list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 valuevalue, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI.

[0172] Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the registration complete message: --SOR transparent container.

[0173] -Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by 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.

[0174] Authentication Response Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication response message: Authentication response message identity, authentication response parameters, and EAP message.

[0175] Authentication Result Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Authentication Result Message: --ngKSI, EAP message, and ABBA.

[0176] Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Authentication Failure Message: --Authentication failure message identity, 5GMM cause, and authentication failure parameter.

[0177] -Authentication Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication rejection message: --EAP message.

[0178] - Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present 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.

[0179] - Service Authorization Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Authorization Message: --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0180] - Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Rejection Message: --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0181] Configuration Update Command Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Configuration Update Command message: --Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI.

[0182] Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the configuration update complete message: --Configuration update complete message identity.

[0183] <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 signals to and receive signals from a connection node via one or more antennas 32. The UE 3 may also include a user interface 34 for inputting and outputting information from an external device. Although not necessarily illustrated, 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. For example, the software may be pre-installed in memory and / or downloaded 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 communications control module 362 (using its transceiver control module 3621) is responsible for handling (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 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. In the case of multiple USIMs 35, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0184] The UE 3 may, for example, support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0185] UE3 may be, for example, an item of production or manufacturing equipment and / or an item of energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, 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, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machinery, printing machinery and / or related machinery, paper converting machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, agricultural, forestry, and / or fishing machinery and / or implements, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, fittings, and / or application systems for any of the foregoing equipment or machines).

[0186] UE 3 may be, for example, an item of transportation equipment (e.g., vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).

[0187] 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.).

[0188] The UE3 may be, for example, a refrigeration machine, a refrigeration machine application product, an item of commercial and / or service industry equipment, a vending machine, an automated service machine, an office machine or device, a consumer electronic device and appliance (e.g., consumer electronic appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners, etc.).

[0189] The UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, a power application device, etc.).

[0190] The UE3 may be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a tester, or a surveying or detecting device (e.g., a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, or other surveying or detecting device), a watch or wall clock, laboratory equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, or the like.

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

[0192] 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 with respect to the "Internet of Things (IoT)."

[0193] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, allowing them to collect and exchange data with each other and with other communicating devices. IoT devices may comprise autonomous 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 idle for long periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0194] It will be understood that IoT technology may be implemented on any communication device that can connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0195] It will be appreciated that an IoT device is sometimes referred to as a Machine-Type Communication (MTC) device or 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.

[0196] 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).

[0197] The UE3 may be a car, a connected car, an autonomous vehicle, a vehicle device, a motorcycle, or a Vehicle to Everything (V2X) 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).

[0198] <(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, a base station for Beyond 5G, or a base station for 6G). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from 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 according to software stored in memory 55. For example, the software may be pre-installed in the memory and / or downloaded 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.

[0199] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling 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, either directly or indirectly. The signaling may include, for example, properly formatted signaling messages related to the radio connection and connection with the core network 7 for a particular UE 3, especially those related to connection establishment and maintenance, such as RRC connection establishment messages and other RRC messages, NG Application Protocol (NGAP) messages (i.e., messages based on the N2 reference point), Xn Application Protocol (XnAP) messages (i.e., messages based on the Xn reference point), etc. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

[0200] The controller 54 is also configured (by software or hardware) to process related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented.

[0201] (R)AN node 5 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0202] <System Overview of (R)AN Node 5 Based on O-RAN Architecture> Figure 7 schematically shows the (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.

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

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

[0205] Depending on the functionality split between 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 supporting the MAC and RLC layers, and the CU 62 may provide functionality supporting the PDCP, SDAP, and RRC layers.

[0206] <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 (eNB in ​​LTE, gNB in ​​5G, Beyond 5G base station, 6G base station). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from an attached UE 3 via one or more antennas 602, and to transmit and receive signals to and from other network nodes or network portions via a network interface 603 (directly or indirectly). A controller 604 controls the operation of the RU 60 according to software stored in memory 605. For example, the software may be pre-installed in the memory and / or downloaded 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.

[0207] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling between (e.g., directly or indirectly) the RU 60 and other nodes or units, such as the UE 3, another RU 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.

[0208] 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.

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

[0210] As described above, the RU 60 may be integrated / combined with the DU 61 as an integration / combination unit. Any function described for the RU 60 may be implemented in the integration / combination unit.

[0211] <Distributed Unit (DU)> FIG. 9 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU portion of a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including 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. For example, the software may be pre-installed in memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication 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.

[0212] The DU 61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

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

[0214] <Centralized 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 base station for Beyond 5G, or a base station for 6G). 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 according to software stored in memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded 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 communication 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.

[0215] CU 62 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0216] As described above, the CU 62 may be integrated / combined with the DU 61 as an integration / combination unit. Any functionality described for the CU 62 may be implemented in the integration / combination unit.

[0217] <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, NSSAAF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in memory 704. For example, the software may be pre-installed in the memory 704 and / or downloaded 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 handling (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 nodes, such as other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0218] The AMF 70 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AMF 7001 and AMF 7002 may have the same components as the AMF 70.

[0219] <pcf> 12 is a block diagram illustrating the main 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. For example, the software may be pre-installed in the memory 734 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory 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 in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to policy management procedures (for the UE 3).

[0220] The PCF 73 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The PCF 7301 and PCF 7302 may have the same components as the PCF 73.

[0221] <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 UDMs 75) via a network interface 742. A controller 743 controls the operation of the AUSF 74 in accordance with software stored in memory 744. For example, the software may be pre-installed in memory 744 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory 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 in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to policy management procedures (for the UE 3).

[0222] The AUSF 74 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0223] <udm> 14 is a block diagram illustrating the major 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. For example, the software may be pre-installed in memory 754 and / or downloaded 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 handling (generating / sending / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to mobility management procedures (for the UE 3).

[0224] The UDM 75 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0225] <nssaaf> 15 is a block diagram illustrating the main components of the NSSAAF 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, AAA Proxy (AAA-P)) via a network interface 762. A controller 763 controls the operation of the NSSAAF 76 in accordance with software stored in memory 764. For example, the software may be pre-installed in memory 764 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421. The communication control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NSSAAF 76 and other nodes such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to mobility management procedures (for the UE 3).

[0226] The NSSAAF 76 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0227] All or part of the exemplary aspects of the above disclosure may be described as follows, but are not limited to the following.

[0228] 5.5.1.2.2 Initial Registration Start The subset of configuration NSSAIs provided in the request NSSAI shall consist of one or more S-NSSAIs in the configuration NSSAIs applicable to the current PLMN if the S-NSSAI is neither in the rejected NSSAI f nor associated with an S-NSSAI in the rejected NSSAI. In addition, if NSSRG information is available, the subset of configuration NSSAIs provided in the request NSSAI shall be associated with at least one common NSSRG value. If the UE has reserved NSSAIs, the subset of configuration NSSAIs provided in the request NSSAI and the reserved NSSAIs shall be associated with at least one common NSSRG value. If the UE already has authorized NSSAIs for other accesses, all S-NSSAIs in the request NSSAI for the current access shall share at least an NSSRG value that is common to all S-NSSAIs of authorized NSSAIs for the other accesses. If the UE is simultaneously performing a registration procedure in other accesses, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types.

[0229] 5.5.1.2.3 5GMM common procedure initiation The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message in the following cases:

[0230] a) If the REGISTRATION REQUEST message does not include a request NSSAI and the initial registration request is not for a built-in service in the SNPN,

[0231] b) If the REGISTRATION REQUEST message contains a requested NSSAI that includes an S-NSSAI that is not valid in the serving PLMN,

[0232] c) If the REGISTRATION REQUEST message contains a Requested NSSAI that includes an S-NSSAI with an incorrect mapping S-NSSAI,

[0233] d) If the REGISTRATION REQUEST message contained a Network Slicing Indication IE with the Default Configuration NSSAI Indication bit set to "Request NSSAI created from Default Configuration NSSAI", or

[0234] e) If any two S-NSSAIs of the requested NSSAIs in the REGISTRATION REQUEST message are not associated with any common NSSRG value.

[0235] f) If the UE has a pending NSSAI, and the S-NSSAI of the requesting NSSAI in the REGISTRATION REQUEST message and the pending NSSAI do not associate with a common NSSRG value.

[0236] g) If the UE already has an authorized NSSAI for another access, and the S-NSSAI of the request NSSAI in the REGISTRATION REQUEST message in the current access and the authorized NSSAI do not relate to a common NSSRG value.

[0237] 5.5.1.3.2 Mobility and Periodic Registration Renewal Initiation The subset of configuration NSSAIs provided in the Request NSSAI shall consist of one or more S-NSSAIs in the configuration NSSAIs applicable to this PLMN if the S-NSSAI is neither in the Rejected NSSAI nor associated with an S-NSSAI in the Rejected NSSAI. In addition, if NSSRG information is available, the subset of configuration NSSAIs provided in the Request NSSAI shall be associated with at least one common NSSRG value. If the UE has Reserved NSSAIs, the subset of configuration NSSAIs provided in the Request NSSAI and the Reserved NSSAIs shall be associated with at least one common NSSRG value. If the UE already has Authorized NSSAIs for other accesses, all S-NSSAIs in the Request NSSAI for the current access shall share at least an NSSRG value that is common to all S-NSSAIs of Authorized NSSAIs for the other accesses. If the UE is simultaneously performing a registration procedure in other accesses, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types.

[0238] 5.5.1.3.3 5GMM common procedure initiation The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message in the following cases:

[0239] a) If the REGISTRATION REQUEST message does not include a request NSSAI and the UE is not registered for the onboard service in the SNPN,

[0240] b) If the REGISTRATION REQUEST message contains a requested NSSAI that includes an S-NSSAI that is not valid in the serving PLMN,

[0241] c) if the REGISTRATION REQUEST message contained a Request-NSSAI that contained an incorrect S-NSSAI; d) if the REGISTRATION REQUEST message contained a Network Slicing Indication IE with the Default Configuration-NSSAI Indication bit set to "Request-NSSAI created from Default Configuration-NSSAI";

[0242] e) If the REGISTRATION REQUEST message contained a Request Mapping NSSAI, or

[0243] f) If any two S-NSSAIs of the requested NSSAIs in the REGISTRATION REQUEST message are not associated with any common NSSRG value.

[0244] f) If the UE has a pending NSSAI and the S-NSSAI and the pending NSSAI of the Requested NSSAI in the REGISTRATION REQUEST message do not associate with a common NSSRG value.

[0245] g) If the UE already has an authorized NSSAI for another access, and the S-NSSAI and the authorized NSSAI of the request NSSAI in the REGISTRATION REQUEST message in the current access do not relate to a common NSSRG value.

[0246] <Modifications and Replacements> Detailed embodiments have been described above. Still, those skilled in the art will appreciate that numerous modifications and alternatives may be made to the above embodiments while having the benefit of the disclosure embodied herein. By way of example only, many such alternatives and modifications are now described.

[0247] In the above description, the UE 3 and network devices are described for ease of understanding as having a number of separate modules (such as a communications control module). These modules may be provided in this manner for particular applications, for example, where an existing system is modified to implement the present disclosure; in other applications, for example, in a system designed with inventive features in mind from the beginning; however, these modules may not be recognizable as separate entities because they may be built into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a mixture of these.

[0248] Each controller may comprise any suitable form of processing circuitry, including, but not limited to, 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 buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, and / or the like.

[0249] In the above embodiments, a number of software modules have been described. Those skilled in the art will understand that 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 the software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred for updating the functions of the UE 3 and network devices, as they facilitate updating the UE 3 and network devices.

[0250] In the above embodiment, 3GPP wireless communication (radio access) technology is used, but 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.) can also be used in accordance with the above embodiment.

[0251] Items of user equipment may include, for example, communication devices such as mobile phones, smartphones, user devices, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (and even 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 UEs) in the description, but it will be understood that the described techniques may be implemented on any (mobile and / or generally fixed) communication device that can connect to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

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

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

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

[0255] 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 in 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 integrated into the processor. The processor and the storage medium may reside in an ASIC.

[0256] The previous description of examples of the present disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the 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 set forth herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0257] Although the present disclosure has been shown and described in detail with reference to exemplary embodiments thereof, the present disclosure is not limited to such embodiments. It will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined herein. For example, the above embodiments are not limited to 5GS, and the embodiments may also be applied to communication systems other than 5GS (e.g., 6G systems, Beyond 5G systems).

[0258] <Additional Notes> All or part of the exemplary aspects of the above disclosure may be described as, but are not limited to, the following supplementary notes.

[0259] Supplementary Note 1. A method for a user equipment (UE), the method comprising: receiving a message containing pending Network Slice Selection Assistance Information (NSSAI); The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), If a registration procedure using a second S-NSSAI is triggered, checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; If the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value, sending a registration request message including the second S-NSSAI. method.

[0260] Appendix 2. A method for a communication device, the method comprising: Sending a first message including a reserved Network Slice Selection Assistance Information (NSSAI); The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), receiving a registration request message including a request NSSAI; the request NSSAI includes a second S-NSSAI; determining whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; sending a second message including a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value; method.

[0261] Supplementary Note 3. A user equipment (UE), the UE comprising: a means for receiving a message including a reserved Network Slice Selection Assistance Information (NSSAI), the means comprising: The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI); and means for determining whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value when a registration procedure using a second S-NSSAI is triggered; means for transmitting a registration request message including the second S-NSSAI if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value; UE equipped with.

[0262] Supplementary Note 4. A communication device, the communication device comprising: a means for transmitting a first message including a reserved Network Slice Selection Assistance Information (NSSAI), The reserved NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI); and a means for receiving a registration request message including a request NSSAI, The request NSSAI includes a second S-NSSAI; means for determining whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; means for transmitting a second message including a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value; A communication device comprising:

[0263] Appendix 5. A method for a communication device, the method comprising: In a certain access, a registration procedure is performed using a first Single Network Slice Selection Assistance Information (S-NSSAI); receiving, in another access, a registration request message including a second S-NSSAI; determining whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; sending a message including a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value; method.

[0264] Supplementary Note 6. A method for a user equipment (UE), the method comprising: In a certain access, a registration procedure is performed using a first Single Network Slice Selection Assistance Information (S-NSSAI); In another access, sending a registration request message including the second S-NSSAI; receiving a message including a configuration NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; method.

[0265] Supplementary Note 7. A communication device, the communication device comprising: A means for performing a registration procedure using a first Single Network Slice Selection Assistance Information (S-NSSAI) at an access; means for receiving, at another access, a registration request message including the second S-NSSAI; means for determining whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; means for transmitting a message including a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value; A communication device comprising:

[0266] Supplementary Note 8. A user equipment (UE), the UE comprising: A means for performing a registration procedure using a first Single Network Slice Selection Assistance Information (S-NSSAI) at an access; means for transmitting, at another access, a registration request message including the second S-NSSAI; means for receiving a message including a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; UE equipped with.

[0267] <Appendix 2> Appendix 1. communicating with a communication device; Send a registration request message, The registration request message includes a requested Network Slice Selection Assistance Information (NSSAI); The request NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), The first S-NSSAI and the second S-NSSAI of the reserved NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; A method for a user equipment (UE).

[0268] Appendix 2. and further receiving the pending NSSAI from the communication device. The method described in Appendix 1.

[0269] Appendix 3. means for communicating with a communication device; means for sending a registration request message; Equipped with The registration request message includes a requested Network Slice Selection Assistance Information (NSSAI); The request NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), The first S-NSSAI and the second S-NSSAI of the reserved NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; User equipment (UE).

[0270] Appendix 4. means for receiving the pending NSSAI from the communication device; UE as described in Appendix 3.

[0271] Appendix 5. communicating with a user equipment (UE); Send a message, The message includes an authorized Network Slice Selection Assistance Information (NSSAI), The authorized NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), The first S-NSSAI and the second S-NSSAI of the reserved NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; Method of communication device.

[0272] Appendix 6. the message includes the pending NSSAI; The message is a registration approval message. The method described in Appendix 5.

[0273] Appendix 7. The communication device has the reserved NSSAI. 7. The method according to claim 5 or 6.

[0274] Appendix 8. means for communicating with a user equipment (UE); a means for sending a message; Equipped with The message includes an authorized Network Slice Selection Assistance Information (NSSAI), The authorized NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI), The first S-NSSAI and the second S-NSSAI of the reserved NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; Communication equipment.

[0275] Appendix 9. the message includes the pending NSSAI; The message is a registration approval message. 9. The communications device of claim 8.

[0276] Appendix 10. The communication device has the reserved NSSAI. 10. The communication device according to claim 8 or 9.

[0277] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0278] This application claims priority from Indian Provisional Patent Application No. 202211016659, filed on March 24, 2022, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0279] 1. Telecommunications Systems 3UE 5 (R)AN nodes 7 Core Network 20 Data Network 31 Transceiver Circuit 32 Antenna 33 Controller 34 User Interface 35 USIM 36 memory 51 Transceiver circuit 52 Antenna 53 Network Interface 54 Controller 55 memory 60RU 61 DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 AUSF 75 UDM 76 NSSAAF 361 Operating Systems 362 Communication Control Module 501 3GPP Access 502 3GPP Access 551 Operating Systems 552 Communication Control Module 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 memory 611 Transceiver Circuit 612 Network Interface 613 Controller 614 memory 621 Transceiver Circuit 622 network interface 623 Controller 624 memory 701 Transceiver Circuit 702 network interface 703 Controller 704 memory 731 Transceiver Circuit 732 network interface 733 Controller 734 memory 741 Transceiver Circuit 742 network interfaces 743 Controller 744 memory 751 Transceiver Circuit 752 network interfaces 753 Controller 754 memory 761 Transceiver Circuit 762 network interfaces 763 Controller 764 memory 3621 Transceiver Control Module 5521 Transceiver Control Module 6051 Operating System 6052 Communication Control Module 6141 Operating System 6142 Communication Control Module 6241 Operating System 6242 Communication Control Module 7041 Operating System 7042 Communication Control Module 7341 Operating System 7342 Communication Control Module 7441 Operating System 7442 Communication Control Module 7541 Operating Systems 7542 Communication Control Module 7641 Operating System 7642 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 73421 Transceiver Control Module 74421 Transceiver Control Module 75421 Transceiver Control Module 76421 Transceiver Control Module< / nssaaf> < / udm> < / ausf> < / pcf> < / amf>

Claims

1. Determining whether a first Single Network Slice Selection Assistance Information (S-NSSAI) and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; sending a Registration Request message if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value; the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); the Requested NSSAI includes the first S-NSSAI; A method for a user device.

2. A means for determining whether a first Single Network Slice Selection Assistance Information (S-NSSAI) and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; means for transmitting a Registration Request message if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value; Equipped with the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); the Requested NSSAI includes the first S-NSSAI; User equipment.

3. means for receiving the pending NSSAI from a communication device; 3. The user device of claim 2.

4. determining whether a first Single Network Slice Selection Assistance Information (S-NSSAI) and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; sending a message if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value; the message includes Allowed Network Slice Selection Assistance Information (NSSAI); the Allowed NSSAI includes the first S-NSSAI; Method of communication device.

5. A method for determining whether a first Single Network Slice Selection Assistance Information (S-NSSAI) and a second S-NSSAI of a Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value; means for transmitting a message if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value; Equipped with the message includes Allowed Network Slice Selection Assistance Information (NSSAI); the Allowed NSSAI includes the first S-NSSAI; Communication equipment.

6. the message includes the Pending NSSAI; the message is a Registration Accept message; The communication device according to claim 5 .

7. the communication device has means for storing the pending NSSAI; 7. The communication device according to claim 5 or 6.

8. The communication device, comprising: means for receiving a Registration Request message; the Registration Request message includes a Requested NSSAI; the Requested NSSAI includes the first S-NSSAI; 7. The communication device according to claim 5 or 6.

Images