Communication device method, user device method, communication device, and user device

Abstract

There are many ambiguities in the 3GPP specifications regarding how to handle the NSSRG features. [Solution] A method of a communications apparatus includes communicating with a user equipment (UE) and transmitting a registration accept message when a first Single Network Slice Selection Assistance Information (S-NSSAI) of a requested Network Slice Selection Assistance Information (NSSAI) in a registration request message in a first access and a second S-NSSAI of an authorized NSSAI in a second access do not associate with a common Network Slice Simultaneous Registration Group (NSSRG) value, the registration accept message including a configured NSSAI.

Description

Technical Field

[0001] This disclosure relates to a method for a communication device, a method for a user equipment (UE), a communication device, and a UE.

Background Art

[0002] A Network Slice Simultaneous Registration Group (NSSRG) is introduced into 5GS in Release 17. The NSSRG function provides a mechanism for restricting combinations of network slices to be simultaneously registered to 3GPP operators.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the 3GPP specification contains many unclear descriptions regarding how to handle NSSRG functionality.

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

[0006] In aspects of this disclosure, the communication device method communicates with user equipment (UE) and sends a Registration Accept message if the first Single Network Slice Selection Assistance Information (S-NSSAI) of the Requested Network Slice Selection Assistance Information (NSSAI) in the Registration Request message in the first access and the second S-NSSAI of the Allowed NSSAI in the second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value. The Registration Accept message includes a Configured NSSAI.

[0007] In aspects of this disclosure, a method of user equipment (UE) transmits a Registration Request message in a first access. The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The method receives a Registration Accept message if the first Single Network Slice Selection Assistance Information (S-NSSAI) of the Requested NSSAI in the Registration Request message and the second S-NSSAI of the Allowed NSSAI in a second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value. The Registration Accept message includes Configured NSSAI.

[0008] In aspects of this disclosure, the communication device includes means for communicating with user equipment (UE), and means for sending a Registration Accept message when the first Single Network Slice Selection Assistance Information (S-NSSAI) of the Requested Network Slice Selection Assistance Information (NSSAI) in the Registration Request message in the first access and the second S-NSSAI of the Allowed NSSAI in the second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value. The Registration Accept message includes Configured NSSAI.

[0009] In aspects of this disclosure, user equipment (UE) includes means for transmitting a Registration Request message in a first access. The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The UE includes means for receiving a Registration Accept message if the first Single Network Slice Selection Assistance Information (S-NSSAI) of the Requested NSSAI in the Registration Request message and the second S-NSSAI of the Allowed NSSAI in a second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value. The Registration Accept message includes Configured NSSAI. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a signaling diagram of a first example of the first embodiment (verification of NSSRG regarding S-NSSAI in Pending NSSAI at UE). [Figure 2] Figure 2 is a signaling diagram of a second example of the first embodiment (confirmation of NSSRG regarding S-NSSAI in pending NSSAI at AMF). [Figure 3] Figure 3 is a signaling diagram of the first example of the second embodiment (NSSRG confirmation regarding S-NSSAI in the pending NSSAI for other access in AMF). [Figure 4] Figure 4 is a diagram showing the system overview. [Figure 5] Figure 5 is a block diagram showing User Equipment (UE). [Figure 6] FIG. 6 is a block diagram showing an (R) AN node. [Figure 7] FIG. 7 is a diagram showing an overview of a system of an (R) AN node based on an 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 showing an Access and Mobility Management Function (AMF). [Figure 12] FIG. 12 is a block diagram showing a Policy Control Function (PCF). [Figure 13] FIG. 13 is a block diagram showing an Authentication Server Function (AUSF). [Figure 14] FIG. 14 is a block diagram showing a Unified Data Management (UDM). [Figure 15] FIG. 15 is a block diagram showing a Network Slice-Specific Authentication and Authorization Function (NSSAAF). [0]]

BEST MODE FOR CARRYING OUT THE INVENTION

[0011] <Abbreviations> For the purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following are applicable. The abbreviations defined in this specification shall take precedence over the definitions of the same abbreviations in Non-Patent Document 1, if any.

[0012] 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

[0013] <Definition> For the purposes of this specification, the terms and definitions given in Non-Patent Document 1, as well as the following, shall apply. In the event that a term is used herein, the definition of that term in Non-Patent Document 1 shall take precedence over that definition.

[0014] <General Overview> Those skilled in the art will understand that the elements in the figures are simplified and do not necessarily have to be drawn to scale. Furthermore, with respect to the structure of the device, one or more components of the device may be represented in the figures by ordinary symbols, and the figures may show only certain details appropriate for understanding aspects of this disclosure, so as not to obscure figures with details that would be readily apparent to those skilled in the art who benefit from the description herein.

[0015] To facilitate understanding of the principles of this disclosure, we will refer here to the embodiments shown in the figures and use specific terminology to describe those principles. Nevertheless, it will be understood that this is not intended to limit the scope of this disclosure. Such modifications and further alterations to the shown systems, as well as such further applications of the principles of this disclosure that a person skilled in the art would ordinarily conceive, should be construed as being within the scope of this disclosure.

[0016] The terms “equipped with,” “possessing,” or any other variation thereof are intended to cover non-exclusive inclusion, so that a process or method comprising a list of steps may include not only those steps but also other steps not explicitly enumerated or inherent in such process or method. Similarly, one or more devices, entities, subsystems, elements, structures, or components beginning with “equipped with” does not, unless further restricted, exclude the existence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, where the phrases “in another aspect,” “in another aspect,” and similar terms appear, they may, but may not necessarily, refer to the same aspect.

[0017] Unless otherwise specified, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art to which this disclosure pertains. The systems, methods, and examples provided herein are illustrative and not intended to limit the scope of this disclosure.

[0018] In the following specification and claims, numerous terms may be defined as having the following meanings: The singular forms "a," "an," and "the" include plural references unless otherwise specifically defined in the context.

[0019] Since data is meaningful information representing values ​​resulting from parameters, the information used herein is associated with data and insights. Furthermore, insights mean an understanding of abstract or concrete concepts. Note that the exemplary system presented here is simplified for the sake of facilitating the explanation of the subject matter of this disclosure and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement the embodiments disclosed herein, and all such embodiments are assumed to be within the scope of this disclosure.

[0020] Each of the embodiments, and the elements included in each of the embodiments described below, can be implemented independently or in combination with each other. These embodiments include novel features that are distinct from each other. Therefore, these embodiments contribute to achieving objectives or solving different problems, and contribute to obtaining different advantages.

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

[0022] A method of a communication device according to an exemplary embodiment of the present disclosure performs a registration procedure using first Single Network Slice Selection Assistance Information (S-NSSAI) in one access. The method receives a registration request message containing a second S-NSSAI in another access. 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 at least one common NSSRG value, the method sends a message containing a Configured NSSAI.

[0023] A user equipment (UE) method according to an exemplary embodiment of the present disclosure performs a registration procedure using first Single Network Slice Selection Assistance Information (S-NSSAI) in one access. The method sends a registration request message containing a second S-NSSAI in another access. The method receives a message containing 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.

[0024] A communication device according to an exemplary embodiment of the present disclosure includes a memory and at least one hardware processor connected to the memory. The at least one hardware processor is configured to perform a registration procedure using first Single Network Slice Selection Assistance Information (S-NSSAI) in one access. The at least one hardware processor is configured to receive a registration request message containing a second S-NSSAI in another access. The at least one hardware processor is configured to determine 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 send a message containing a configuration NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with at least one common NSRG value.

[0025] An exemplary user equipment (UE) of the present disclosure includes memory and at least one hardware processor connected to the memory. The at least one hardware processor is configured to perform a registration procedure using first Single Network Slice Selection Assistance Information (S-NSSAI) in one access. The at least one hardware processor is configured to send a registration request message containing a second S-NSSAI in another access. The at least one hardware processor is configured to receive a message containing 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.

[0026] <First aspect> The Network Slice Simultaneous Registration Group (NSSRG) will be introduced in 5GS in Release 17. The NSSRG function provides 3GPP operators with a mechanism to limit the combinations of network slices that are registered to end users simultaneously. According to the current 3GPP specification, NSSRG information (e.g., information indicating an NSSRG or information related to an NSSRG) is provided from 5GC to UE, and the UE selects network slices based on the NSSRG information. However, the 3GPP specification is not clear on what 5GC should do if the UE retains older configured network slices (e.g., older configured NSSAI) and / or older NSSRG information. In this case, the NSSRG function will not work properly.

[0027] For example, this embodiment focuses on the problem when AMF70 detects, based on NSSRG information, that an S-NSSAI in the Requested NSSAI within a Registration Request message from UE3 contains an S-NSSAI that is not compatible with an S-NSSAI in the Pending NSSAI in AMF70. For example, this embodiment provides a solution to this problem.

[0028] For example, if the S-NSSAI in the requested NSSAI and the S-NSSAI in the pending NSSAI cannot be registered simultaneously, the AMF70 detects that at least one of the configuration NSSAI and NSSRG information in UE3 is not up-to-date. For example, the AMF70 detects that at least one of the configuration NSSAI and NSSRG information in UE3 is outdated. In this case, the AMF70 provides at least one of the configuration NSSAI and NSSRG information to UE3 to refresh the data in UE3.

[0029] For example, this embodiment also discloses a method for processing a registration procedure when the S-NSSAI of a request NSSAI in a registration request message does not belong to or shares any common NSSRG values ​​with the S-NSSAI in a pending NSSAI.

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

[0031] <First example of the first aspect> A first example of the first aspect discloses a method by which UE3 can determine whether an S-NSSAI in a pending NSSAI and an S-NSSAI in a request NSSAI in a registration request message belong to or share at least one common NSSRG value.

[0032] A detailed process of the first example of the first embodiment is described below with reference to Figure 1.

[0033] 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 NSSAI set for S-NSSAI1 and S-NSSAI2. The requested NSSAI may include one or more S-NSSAIs. For example, S-NSSAI1 follows the NSSAA procedure.

[0034] 2) When AMF70 receives a registration request message that includes S-NSSAI1 and S-NSSAI2 as requested NSSAIs, AMF70 identifies that S-NSSAI1 complies with the NSSAA procedure. For example, AMF70 may identify that S-NSSAI1 complies with the NSSAA procedure based on its local configuration or operator policy, or information received from other network nodes. AMF70 marks S-NSSAI1 as a pending NSSAI, and AMF70 decides that S-NSSAI2 is permitted for use for UE3, and sends a Registration Accept message that includes S-NSSAI1 as a pending NSSAI and S-NSSAI2 as an allowed NSSAI. The Registration Accept message may also include at least one of the configuration NSSAI and NSSRG information. The NSSRG information may be information indicating or related to the NSSRG. For example, UE3 can understand, based on NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, UE3 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) share which NSSRG values ​​or NSSRGs. For example, UE3 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) are associated with which NSSRG values ​​or NSSRGs. NSSRG information can be referred to as NSSRG.

[0035] AMF70 can recognize that UE3 has a pending NSSAI, including S-NSSAI1.

[0036] 3) Upon receiving a registration approval message, UE3 stores the pending NSSAI and authorized NSSAI. If the registration approval message includes at least one of the configuration NSSAI and NSSRG information, UE3 stores at least one of the configuration NSSAI and NSSRG information. UE3 then sends a Registration Complete message. For example, if UE3 receives a registration approval message, UE3 may send a Registration Complete message.

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

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

[0039] 5) AMF70 initiates the NSSAA procedure for S-NSSAI1 as defined in Non-Patent Document 3.

[0040] 6) UE3 obtains a trigger to register S-NSSAI2. UE3 checks the NSSRG information to determine whether S-NSSAI1 and S-NSSAI2, which are pending NSSAIs in UE3, share at least one common NSSRG value (for example, UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, or UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or UE3 checks based on the NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG). UE3 maintains S-NSSAI1 as a pending NSSAI during the NSSAA procedure. Steps 6-8 may occur during the NSSAA procedure for S-NSSAI1. The verification of whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value can be referred to as the verification of whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value.

[0041] 7) If S-NSSAI1 and S-NSSAI2 in the pending NSSAI in UE3 belong to at least one common NSSRG value (for example, 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 will initiate the registration procedure by sending a registration request message containing the requested NSSAI set in S-NSSAI2.

[0042] 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 that includes the request NSSAI, including S-NSSAI2.

[0043] If S-NSSAI1 and S-NSSAI2 in a pending NSSAI in 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 take.

[0044] 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 decide that S-NSSAI1 and S-NSSAI2 do not belong to, share, or are not associated with a common NSSRG (or common NSSRG value), and then perform one of the following options:

[0045] See below for the options available in UE3:

[0046] -Since S-NSSAI1 and S-NSSAI2 do not belong to a common NSSRG value, UE3 will not initiate the registration procedure (for example, UE3 will not send a registration request message containing the requested NSSAI set in S-NSSAI2).

[0047] -UE3 initiates the registration procedure by sending a registration request message that includes a requested NSSAI set in another S-NSSAI belonging to the same NSSRG value as S-NSSAI1. For example, UE3 may initiate the registration procedure by sending a registration request message that includes a requested NSSAI set in a different S-NSSAI3 that belongs to (or shares) the same NSSRG value as S-NSSAI1, but is different from S-NSSAI2. UE3 may select a different S-NSSAI from the configuration NSSAI based on the NSSRG information.

[0048] -UE3 aborts the NSSAA procedure for S-NSSAI1, and after the abortion of the NSSAA procedure for S-NSSAI1 is complete, UE3 starts the registration procedure by sending a registration request message containing the requested NSSAI set in S-NSSAI2. For example, after the abortion of the NSSAA procedure for S-NSSAI1 is complete, UE3 may start the registration procedure by sending a registration request message containing the requested NSSAI set in S-NSSAI2. For example, after the abortion of the NSSAA procedure for S-NSSAI1 is complete, UE3 may remove S-NSSAI1 from the pending NSSAIs and set S-NSSAI1 as a rejected NSSAI.

[0049] -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 that includes 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 NSSAI in UE3. Alternatively, UE3 removes S-NSSAI1 from the allowed NSSAI in UE3 after the completion of the NSSAA procedure for S-NSSAI1. For example, if UE3 receives an allowed NSSAI that includes S-NSSAI1 after the completion of the NSSAA procedure for S-NSSAI1, UE3 may relinquish the allowed NSSAI, remove S-NSSAI1 from the allowed NSSAI, or set S-NSSAI1 as a denied NSSAI.

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

[0051] If in step 7 UE3 initiates the registration procedure by sending a registration request message containing the requested NSSAI set in S-NSSAI2, the registration procedure may continue from step 4 in section 4.2.2.2.2 of Non-Patent Literature 3.

[0052] If in step 7 UE3 initiates the registration procedure by sending a registration request message containing a requested NSSAI set in 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.

[0053] If, in step 7, UE3 initiates the registration procedure by sending a registration request message containing the requested NSSAI set in S-NSSAI2 after completing the termination 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.

[0054] If, in step 7, UE3 initiates the registration procedure by sending a registration request message containing the 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.

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

[0056] According to a first example of the first embodiment, for example, a solution can be provided for unclear descriptions in the 3GPP specification regarding methods for processing NSSRGs.

[0057] According to a first example of the first embodiment, for example, a method can be provided for processing a registration procedure when the S-NSSAI of the request NSSAI in the registration request message does not belong to any common NSSRG value with the S-NSSAI in the pending NSSAI or does not share any common NSSRG value.

[0058] According to a first example of the first embodiment, for example, a method can be provided for processing a registration procedure when the S-NSSAI of the request NSSAI in the registration request message belongs to or shares at least one common NSSRG value with the S-NSSAI in the pending NSSAI.

[0059] <Variation 1 of the first example of the first aspect> In one example, in step 1, UE3 sends only S-NSSAI1 in the registration request message. In this case, UE3 and AMF70 have S-NSSAI1 in their pending NSSAI. In step 6, UE3 may receive a trigger to register S-NSSAI2 and perform the process in step 6. For example, UE3 may select an S-NSSAI from the configuration NSSAI and include the selected S-NSSAI in the request NSSAI within the registration request message. For example, a subset of the configuration NSSAI may be provided in the request NSSAI. For example, a subset of the configuration NSSAI may be the request NSSAI. Variation 1 of the first example of the first embodiment may apply to the second example of the first embodiment below. For example, if UE3 has pending NSSAI, the subset of the configuration NSSAI and the pending NSSAI provided in the request NSSAI may be associated with at least one common NSSRG value.

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

[0061] If UE3 determines or confirms (for example, in step 6) that a subset of configuration NSSAIs and pending NSSAIs provided in the request NSSAI relate to at least one common NSRG value, UE3 may use the request NSSAI to perform a registration procedure (for example, UE3 may send a registration request message containing the request NSSAI; this process may occur in step 7). The following process (or subsequent process) may be the same as step 8 in Figure 1.

[0062] <Second example of the first aspect> A second example of the first aspect discloses a method by which AMF70 determines whether the S-NSSAI in the pending 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 pending NSSAI and the S-NSSAI in the request NSSAI do not share any common NSSRG values, AMF70 provides the configuration NSSAI and NSSRG to the UE3 to refresh the configuration data in the UE3.

[0063] A detailed process of a second example of the first embodiment is described below with reference to Figure 2.

[0064] 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 NSSAI set for S-NSSAI1 and S-NSSAI2. The requested NSSAI may contain one or more S-NSSAIs. For example, S-NSSAI1 follows the NSSAA procedure.

[0065] 2) When AMF70 receives a registration request message that includes S-NSSAI1 and S-NSSAI2 as requested NSSAIs, AMF70 identifies that S-NSSAI1 complies with the NSSAA procedure. For example, AMF70 may identify that S-NSSAI1 complies with the NSSAA procedure based on its local configuration or operator policy, or information received from other network nodes. AMF70 marks S-NSSAI1 as a pending NSSAI, and AMF70 decides that S-NSSAI2 is permitted for use for UE3, and AMF70 sends a registration approval message that includes S-NSSAI1 as a pending NSSAI and S-NSSAI2 as an permitted NSSAI. The registration approval message may also include at least one of the configuration NSSAI and NSSRG information. The NSSRG information may be information indicating or related to the NSSRG. For example, UE3 can understand, based on NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, UE3 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) share which NSSRG value or NSSRG. For example, UE3 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) are associated with which NSSRG value or NSSRG.

[0066] The AMF70 can store NSSRG information. For example, the AMF70 can understand, based on the NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the AMF70 can understand, based on the NSSRG information, which network slices (e.g., S-NSSAI) share which NSSRG value or NSSRG. For example, the AMF70 can understand, based on the NSSRG information, which network slices (e.g., S-NSSAI) are associated with which NSSRG value or NSSRG.

[0067] The AMF70 can either store NSSRG information in advance, receive NSSRG information from other network nodes, or create NSSRG information based on the local configuration or operator policies of the AMF70, or information received from other network nodes.

[0068] AMF70 can recognize that UE3 has a pending NSSAI, including S-NSSAI1.

[0069] 3) Upon receiving a registration approval message, UE3 stores the pending NSSAI and authorized NSSAI. If the registration approval message includes at least one of the configuration NSSAI and NSSRG information, UE3 stores at least one of the configuration NSSAI and NSSRG information. UE3 then sends a registration completion message. For example, if UE3 receives a registration approval message, UE3 may send a registration completion message.

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

[0071] 4b) In step 4b, the AMF70 stores S-NSSAI1 in the reserved NSSAI. For example, the AMF70 may have a reserved NSSAI that includes S-NSSAI1.

[0072] 5) AMF70 initiates the NSSAA procedure for S-NSSAI1 as defined in Non-Patent Document 3.

[0073] 6) UE3 receives a trigger to register S-NSSAI2. UE3 initiates the registration process by sending a registration request message to S-NSSAI2 that includes the requested NSSAI set.

[0074] During the NSSAA procedure, UE3 maintains S-NSSAI1 as a pending NSSAI. Steps 6-9 may be performed during the NSSAA procedure on S-NSSAI1.

[0075] 7) Upon receiving a registration request message from UE3, AMF70 verifies whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value (for example, AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value, AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value). The verification of whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG value can be referred to as the verification of whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value.

[0076] Depending on the results of the verification in step 7, one of steps 8a, 8b, 8c, and 8d will be performed.

[0077] 8a) If S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value (for example, 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 S-NSSAI2 is permitted for use for UE3, AMF70 sends a registration approval message to UE3 that includes at least one of the following: NSSRG information, S-NSSAI2 set as an permitted NSSAI, and S-NSSAI1 set as a pending NSSAI. The registration approval message may also include a configuration NSSAI. For example, AMF70 may send a registration approval message to UE3 that includes NSSRG information, an authorized NSSAI including S-NSSAI2, and a pending NSSAI including S-NSSAI1.

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

[0079] 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 S-NSSAI2 is permitted for use for UE3, and AMF70 determines that S-NSSAI2 has a higher priority than S-NSSAI1 for UE3, AMF70 sends a registration approval message to UE3 that includes at least one of the following: configuration NSSAI, NSSRG information, S-NSSAI2 set as permitted NSSAI, and S-NSSAI1 set as denied NSSAI. For example, AMF70 may send a registration approval message to UE3 that includes configuration NSSAI, NSSRG information, authorized NSSAI including S-NSSAI2, and denied NSSAI including S-NSSAI1. For example, AMF70 may store information related to the priority of S-NSSAI or receive such information from other network nodes, and AMF70 may determine the priority of S-NSSAI based on that information. For example, AMF70 may determine the priority of S-NSSAI based on AMF70's local configuration or operator policy.

[0080] Since S-NSSAI1 is in a pending NSSAI stored in UE3, if UE3 receives a registration approval message from AMF70 that includes S-NSSAI1 in a rejected NSSAI, UE3 removes S-NSSAI1 from the pending NSSAI and stores S-NSSAI1 in the rejected NSSAI. In addition, UE3 may initiate an abort process for any ongoing NSSAA procedures regarding S-NSSAI1. UE3 may store S-NSSAI2 in an authorized NSSAI. For example, UE3 may use at least one of the received configuration NSSAI and NSSRG information to refresh or update data in UE3 (e.g., configuration NSSAI and NSSRG information previously stored in UE3).

[0081] For example, UE3 may maintain an ongoing NSSAA procedure for S-NSSAI1. In this case, if UE3 receives an authorization NSSAI containing S-NSSAI1 after the completion of the NSSAA procedure for S-NSSAI1, UE3 does not need to update the authorization NSSAI in UE3 based on the received authorization NSSAI containing S-NSSAI1. In this case, UE3 may relinquish the received authorization NSSAI and maintain S-NSSAI1 as a denial NSSAI.

[0082] 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 S-NSSAI2 is permitted for use for UE3, and AMF70 determines that S-NSSAI1 has a higher priority than S-NSSAI2 for UE3, AMF70 sends a registration approval message to UE3 that includes at least one of the following: configured NSSAI, NSSRG information, S-NSSAI2 set as denied NSSAI, and S-NSSAI1 set as pending NSSAI. For example, AMF70 may send a registration approval message to UE3 that includes configuration NSSAI, NSSRG information, rejection NSSAI including S-NSSAI2, and pending NSSAI including S-NSSAI1.

[0083] Since S-NSSAI2 is in the authorized NSSAI stored in UE3, when UE3 receives a registration approval message from AMF70 that includes S-NSSAI2 in the denied NSSAI, UE3 removes S-NSSAI2 from the authorized NSSAI and stores S-NSSAI2 in the denied NSSAI. UE3 may store S-NSSAI1 in the pending NSSAI. For example, UE3 may use at least one of the received configuration NSSAI and NSSRG information to refresh or update data in UE3 (e.g., configuration NSSAI and NSSRG information previously stored in UE3).

[0084] 8d) 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), AMF70 sends a Registration Reject message to UE3 that includes at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI1 and S-NSSAI2 set as denial NSSAI. For example, AMF70 may send a Registration Reject message to UE3 that includes configuration NSSAI, NSSRG information, and denial NSSAI including S-NSSAI1 and S-NSSAI2.

[0085] If UE3 receives a registration rejection message from AMF70 that includes S-NSSAI1 and S-NSSAI2 in the Rejected NSSAI, because S-NSSAI1 is in the Pending NSSAI in UE3 and S-NSSAI2 is in the Allowed NSSAI in UE3, UE3 removes S-NSSAI1 from the Pending NSSAI and S-NSSAI2 from the Allowed NSSAI and stores S-NSSAI1 and S-NSSAI2 in the Rejected NSSAI. In addition, UE3 initiates a termination process for any ongoing NSSAA procedures for S-NSSAI1. For example, UE3 may use at least one of the received Configuration NSSAI and NSSRG information to refresh or update data in UE3 (e.g., Configuration NSSAI and NSSRG information previously stored in UE3).

[0086] For example, UE3 may maintain an ongoing NSSAA procedure for S-NSSAI1. In this case, if UE3 receives an authorization NSSAI containing S-NSSAI1 after the completion of the NSSAA procedure for S-NSSAI1, UE3 does not need to update the authorization NSSAI in UE3 based on the received authorization NSSAI containing S-NSSAI1. In this case, UE3 may relinquish the received authorization NSSAI and maintain S-NSSAI1 as a denial NSSAI.

[0087] 9) If a registration approval message is sent from AMF70 to UE3 in step 8, UE3 may send a registration completion message to AMF70 to complete the registration procedure.

[0088] For example, if AMF70 determines that S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG values, AMF70 may detect or determine that at least one of the configuration NSSAI and NSSRG information in UE3 is not up-to-date. In this case, AMF70 may send a registration approval message or a registration rejection message as referred to in steps 8b, 8c, or 8d.

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

[0090] The configuration NSSAI transmitted in step 8a, 8b, 8c, or 8d may differ from the configuration NSSAI transmitted in step 2. In this case, AMF70 may create a new configuration NSSAI or update the configuration NSSAI transmitted in step 2 based on the local configuration or operator policy in AMF70 or information received from other network nodes, and transmit the new or updated configuration NSSAI in step 8a, 8b, 8c, or 8d. AMF70 may request a new or updated configuration NSSAI from other network nodes and receive a new or updated configuration NSSAI from other network nodes. AMF70 may then transmit the new or updated configuration NSSAI in step 8a, 8b, 8c, or 8d.

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

[0092] The NSSRG information transmitted in step 8a, 8b, 8c, or 8d may differ from the NSSRG information transmitted in step 2. In this case, the AMF70 may create new NSSRG information or update the NSSRG information transmitted in step 2 based on the local configuration or operator policy in the AMF70, or information received from other network nodes, and may transmit the new or updated NSSRG information in step 8a, 8b, 8c, or 8d.

[0093] AMF70 may request new or updated NSSRG information from other network nodes, and may receive new or updated NSSRG information from other network nodes. Then, in step 8a, 8b, 8c, or 8d, AMF70 may transmit the new or updated NSSRG information.

[0094] For example, if UE3 has a pending NSSAI and the S-NSSAI2 of the request NSSAI in the registration request message and the pending NSSAI (e.g., S-NSSAI1 in the pending NSSAI) are not related to any common NSSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

[0095] For example, if AMF70 has a pending NSSAI and the S-NSSAI2 of the request NSSAI in the registration request message and the pending NSSAI (e.g., S-NSSAI1 in the pending NSSAI) are not related to any common NSSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

[0096] According to a second example of the first embodiment, for example, a solution can be provided for unclear descriptions in the 3GPP specification regarding methods for processing NSSRGs.

[0097] According to a second example of the first embodiment, for example, a method can be provided for processing a registration procedure when the S-NSSAI of the request NSSAI in the registration request message does not belong to any common NSSRG value with the S-NSSAI in the pending NSSAI or does not share any common NSSRG value.

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

[0099] For example, if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, then at least one of the configuration NSSAI and NSSRG information stored in UE3 may not be up-to-date. By checking whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, AMF70 can detect or determine whether at least one of the configuration NSSAI and NSSRG information in UE3 may not be up-to-date (or may be outdated). If AMF70 determines that S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (for example, if AMF70 detects or determines that at least one of the configuration NSSAI and NSSRG information in UE3 may not be up-to-date), AMF70 transmits at least one of the configuration NSSAI and NSSRG information to refresh or update the configuration NSSAI and NSSRG information stored in UE3. According to a second example of the first embodiment, for example, the latest information for performing the NSSRG function (e.g., configuration NSSAI and NSSRG information) is provided from AMF70 to UE3 if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, and the NSSRG function can function properly.

[0100] <Variation 1 of the second example of the first embodiment> In steps 8b and 8d, AMF70 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:

[0101] -AMF70 sends an AAA protocol Revoke Auth request message to NSSAAF76, including GPSI for S-NSSAI1 and UE3 requesting the revocation of authorization for S-NSSAI1.

[0102] -AMF70 sends a message to the AAA server for S-NSSAI1, including GPSI for S-NSSAI1 and UE3 requesting the revocation of the authorization for S-NSSAI1.

[0103] <Variation 2 of the second example of the first embodiment> For example, AMF70 may recognize the contents of the configuration NSSAI for UE3, or that UE3 has a configuration NSSAI. For example, if AMF70 receives a registration request message from UE3 (for example, in step 6) that includes a request NSSAI, AMF70 may determine or confirm (for example, in step 7) whether the subset of configuration NSSAI provided in the request NSSAI and the pending NSSAI (for example, the pending NSSAI for UE3) relate to at least one common NSRRG value. Depending on that determination or confirmation, AMF70 may perform one of steps 8a to 8d. For example, if AMF70 determines that the subset of configuration NSSAI provided in the request NSSAI and the pending NSSAI relate to at least one common NSRRG value, AMF70 may perform the process in step 8a (for example, AMF70 may send a registration approval message in step 8a). For example, if AMF70 determines that the subset of configuration NSSAIs provided in the request NSSAI and the pending NSSAIs 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 approval message in step 8b, AMF70 may send a registration approval message in step 8c, or AMF70 may send a registration rejection message in step 8d).

[0104] <Second aspect> The Network Slice Simultaneous Registration Group (NSSRG) will be introduced in 5GS in Release 17. The NSSRG function provides 3GPP operators with a mechanism to limit the combinations of network slices that are registered to end users simultaneously. According to the current 3GPP specification, NSSRG information (e.g., information indicating an NSSRG or information related to an NSSRG) is provided from 5GC to UE, and the UE selects network slices based on the NSSRG information. However, the 3GPP specification is not clear on what 5GC should do if the UE retains older configuration network slices (e.g., older configuration NSSAI) and / or older NSSRG information. In this case, the NSSRG function will not work properly.

[0105] For example, this embodiment focuses on the problem when AMF70 detects, based on NSSRG information, that an S-NSSAI in a request NSSAI within a registration request message from UE3 contains an S-NSSAI that cannot coexist with an S-NSSAI in an authorization NSSAI for a different access type in AMF70. For example, this embodiment provides a solution to this problem.

[0106] For example, if an S-NSSAI in a request NSSAI and an S-NSSAI in an authorization NSSAI for another access type cannot be registered simultaneously, AMF70 detects that at least one of the configuration NSSAI and NSSRG information in UE3 is not up-to-date. For example, AMF70 detects that at least one of the configuration NSSAI and NSSRG information in UE3 is outdated. In this case, AMF70 provides the configuration NSSAI and NSSRG information to UE3 to refresh the data in UE3.

[0107] For example, this embodiment also discloses a method for handling a registration procedure when the S-NSSAI of a request NSSAI in a registration request message does not belong to or shares any common NSSRG values ​​with the S-NSSAI in a permission NSSAI for another access type.

[0108] <First example of the second aspect> A first example of the second aspect discloses how AMF70 can determine whether an S-NSSAI in an authorization NSSAI for one access type and an S-NSSAI in a request NSSAI in a registration request message for another access type share at least one common NSSRG value. If the S-NSSAI in an authorization NSSAI for one access and an S-NSSAI in a request NSSAI for another access do not share a common NSSRG value, AMF70 sends a registration approval message containing configuration NSSAI and NSSRG information to the UE3 to refresh the configuration data in the UE3.

[0109] A detailed process of the first example of the second embodiment is described below with reference to Figure 3.

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

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

[0112] 3) In non-3GPP access, UE3 sends a registration request message that includes S-NSSAI2 in the requested NSSAI.

[0113] 4) Upon receiving a registration request message, AMF70 verifies whether S-NSSAI1, which is in the authorized NSSAI 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 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG, AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, UE3 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 belong to at least one common NSSRG, or AMF70 verifies based on NSSRG information whether S-NSSAI1 and S-NSSAI2 are associated with at least one common NSSRG value).

[0114] The AMF70 can either store NSSRG information in advance, receive NSSRG information from other network nodes, or create NSSRG information based on the local configuration or operator policies of the AMF70, or information received from other network nodes.

[0115] For example, AMF70 can understand, based on NSSRG information, which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG. For example, AMF70 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) share which NSSRG value or NSSRG. For example, AMF70 can understand, based on NSSRG information, which network slices (e.g., S-NSSAI) are associated with which NSSRG value or NSSRG.

[0116] Depending on the results of the verification, there are two options to be taken.

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

[0118] 5a) AMF70 sends a registration denial message to UE3 that includes at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI2 set as a denial NSSAI. For example, if AMF70 determines that S-NSSAI1 and S-NSSAI2 do not belong to or share a common NSSRG or common NSSRG value (or if AMF70 determines that S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG or common NSSRG value), AMF70 may send a registration denial message that includes the configuration NSSAI, NSSRG information, and a denial NSSAI including S-NSSAI2.

[0119] When UE3 receives a registration rejection message, it stores at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI2 set in the rejection NSSAI. For example, UE3 may use at least one of the received configuration NSSAI and NSSRG information to refresh or update data in UE3 (e.g., configuration NSSAI and NSSRG information previously stored in UE3).

[0120] Option 2: This is an option where AMF70 approves the registration request that has S-NSSAI2. When S-NSSAI2 is approved, AMF70 updates S-NSSAI1 to be rejected for non-3GPP access because there is no common NSSRG value between S-NSSAI1 and S-NSSAI2.

[0121] 5b) AMF70 sends a registration approval message to UE3 that includes the configuration NSSAI, NSSRG information, and S-NSSAI2 set as the authorized NSSAI. For example, if AMF70 determines that S-NSSAI1 and S-NSSAI2 do not belong to or share a common NSSRG or common NSSRG value (or if AMF70 determines that S-NSSAI1 and S-NSSAI2 are not associated with any common NSSRG or common NSSRG value), AMF70 may send a registration approval message that includes the configuration NSSAI, NSSRG information, and the authorized NSSAI including S-NSSAI2. For example, AMF70 may send a registration approval message in non-3GPP access.

[0122] Upon receiving a registration approval message, UE3 stores at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI2 set in the authorization NSSAI. For example, UE3 may use at least one of the received configuration NSSAI and NSSRG information to refresh or update data in UE3 (e.g., configuration NSSAI and NSSRG information previously stored in UE3).

[0123] 6b) UE3 sends a registration completion message to AMF70. For example, if UE3 receives a registration approval message from AMF70, UE3 may send a registration completion message to AMF70. For example, UE3 may send a registration completion message in non-3GPP access.

[0124] 7b) The AMF70 sends a UE Configuration Update Command message to the UE3 via 3GPP access, which includes at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI1 set as a rejection NSSAI. For example, the AMF70 may send a UE Configuration Update Command message which includes configuration NSSAI, NSSRG information, and rejection NSSAI including S-NSSAI1. For example, the AMF70 may send a UE Configuration Update Command message after receiving a registration completion message in step 6b. For example, the AMF70 may send a UE Configuration Update Command message after sending a registration approval message in step 5b.

[0125] When UE3 receives a UE configuration update command message, it stores at least one of the following: configuration NSSAI, NSSRG information, and S-NSSAI1, which is set to deny 3GPP access.

[0126] For example, UE3 may remove S-NSSAI1 from the allowed NSSAI for 3GPP access and store a denied NSSAI that includes S-NSSAI1 for 3GPP access.

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

[0128] 8b) UE3 sends a UE Configuration Update Complete message to AMF70 during 3GPP access. For example, if UE3 receives a UE Configuration Update command message from AMF70, UE3 may send a UE Configuration Update Complete message to AMF70.

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

[0130] AMF70 may request a new or updated configuration NSSAI from other network nodes and may receive a new or updated configuration NSSAI from other network nodes. Then, in step 5a, 5b, or 7b, AMF70 may transmit the new or updated configuration NSSAI.

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

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

[0133] AMF70 may request new or updated NSSRG information from other network nodes, and may receive new or updated NSSRG information from other network nodes. Then, in step 5a, 5b, or 7b, AMF70 may transmit the new or updated NSSRG information.

[0134] 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 both 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.

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

[0136] For example, if UE3 already has an authorization NSSAI for 3GPP access, and the S-NSSAI2 of the request NSSAI in the registration request message and the authorization NSSAI (e.g., S-NSSAI1 in the authorization NSSAI) are not related to any common NSSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

[0137] For example, if AMF70 already has an authorization NSSAI for 3GPP access, and the S-NSSAI2 of the request NSSAI in the registration request message and the authorization NSSAI (e.g., S-NSSAI1 in the authorization NSSAI) are not related to any common NSSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

[0138] For example, if AMF70 already has an authorization NSSAI for 3GPP access, and the S-NSSAI2 of the request NSSAI in the registration request message for non-3GPP access and the authorization NSSAI for 3GPP access (e.g., S-NSSAI1 in the authorization NSSAI) are not related to any common NSSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

[0139] For example, if UE3 (or AMF70) already has an authorization NSSAI for other access, and the S-NSSAI2 of the request NSSAI in the registration request message for the current access and the authorization NSSAI for the other access (e.g., S-NSSAI1 in the authorization NSSAI) are not related to any common NSRG value, AMF70 may send a new configuration NSSAI by using a registration rejection message or a registration approval message (or AMF70 may include the new configuration NSSAI in a registration rejection message or a registration approval message).

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

[0141] According to the first example of the second embodiment, for example, a solution can be provided for unclear descriptions in the 3GPP specification regarding methods for processing NSSRGs.

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

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

[0144] For example, if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, then at least one of the configuration NSSAI and NSSRG information stored in UE3 may not be up-to-date. By checking whether S-NSSAI1 and S-NSSAI2 share at least one common NSSRG value, AMF70 can detect or determine whether at least one of the configuration NSSAI and NSSRG information in UE3 may not be up-to-date (or may be outdated). If AMF70 determines that S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value (for example, if AMF70 detects or determines that at least one of the configuration NSSAI and NSSRG information in UE3 may not be up-to-date), AMF70 transmits at least one of the configuration NSSAI and NSSRG information to refresh or update the configuration NSSAI and NSSRG information stored in UE3. According to the first example of the second embodiment, for example, the latest information for performing the NSSRG function (e.g., configuration NSSAI and NSSRG information) is provided from AMF70 to UE3 if S-NSSAI1 and S-NSSAI2 do not share at least one common NSSRG value, and the NSSRG function can function properly.

[0145] <Variation 1 of the first example of the second aspect> This example illustrates a situation where UE3 sends a registration request message to AMF70 for non-3GPP access while UE3 has authorized NSSAI for 3GPP access. Similarly, the first example of the second embodiment is effective for a situation where UE3 sends a registration request message to AMF70 for 3GPP access while UE3 has authorized NSSAI for non-3GPP access.

[0146] <Variation 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.

[0147] <System Overview> Figure 4 schematically shows a mobile (cellular or wireless) telecommunications system 1 to which the above embodiment can be applied.

[0148] Telecommunication system 1 represents a system overview capable of end-to-end communication. For example, UE3 (or user equipment, "mobile device" 3) communicates with other UE3 or service servers within the data network 20 via its respective (R)AN node 5 and core network 7.

[0149] (R)AN Node 5 supports any radio access, including non-3GPP RATs such as 5G radio access technology (RAT), E-UTRA radio access technology, Beyond5G RAT, 6G RAT, and wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

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

[0151] (R)AN node 5 may be separated into control plane functions and user plane functions. Furthermore, multiple user plane functions may be assigned to support communications. In some embodiments, user traffic may be distributed across multiple user plane functions, and the user traffic in each user plane function is aggregated at both UE3 and (R)AN node 5. This separation architecture may be called "dual connectivity" or "multi-connectivity".

[0152] (R)AN node 5 may also support communications using satellite access. In some embodiments, (R)AN node 5 may support both satellite and ground access.

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

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

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

[0156] Core network 7 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).

[0157] As is well known, when a UE3 is moving around the geographic area covered by the telecommunications system 1, the UE3 may move in and out of the area (i.e., radio cell) serviced by the (R)AN node 5. To maintain tracking of the UE3 and facilitate movement between various (R)AN node 5, the core network 7 includes at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN node 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.

[0158] The core network 7 also includes, in particular, 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 UE3 roams to the Visited Public Land Mobile Network (VPLMN), the UE3's Home Public Land Mobile Network (HPLMN) provides the roaming-out UE3 with the UDM 75, as well as at least some of the functions of SMF 71, UPF 72, and PCF 73.

[0159] UE3 and each Serving(R)AN node 5 are connected via appropriate air interfaces (e.g., so-called "Uu" interfaces and / or equivalents). Neighboring(R)AN nodes 5 are connected to each other via appropriate(R)AN node 5-to-(R)AN node interfaces (such as so-called "Xn" interfaces and / or equivalents). Each(R)AN node 5 is also connected to nodes in the core network 7 (such as so-called core network nodes) via appropriate interfaces (such as so-called "N2" / "N3" interfaces and / or equivalents). Connection from the core network 7 is also provided to the data network 20. The data network 20 may be the internet, a public network, an external network, a private network, or the internal network of the 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. UE3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.

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

[0161] The user plane of the Uu interface is responsible for transmitting user traffic between UE3 and Serving(R)AN node 5. The user plane of the Uu interface may have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers via physical connections.

[0162] The Uu interface control plane is responsible for establishing, modifying, and releasing connections between UE3 and Serving(R)AN node 5. The Uu interface control plane may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers via physical connections.

[0163] For example, the following message is communicated at the RRC layer to support AS signaling.

[0164] - RRC setup request message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be included in the RRC setup request message. --Establishment Cause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or a random value.

[0165] -RRC setup message: This message is sent from (R)AN node 5 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be included in the RRC setup message. --Master Cell Group and Radio Bearer Config

[0166] - RRC setup complete message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this disclosure, the following parameters may also be included in the RRC setup complete message. --Guami Type, IAB Node Indication, Idle Meas Available, Mobility State, ng-5G-S-TMSI-Part2, Registered AMF, Selected PLMN Identity

[0167] The UE3 and AMF70 are connected via an appropriate interface (e.g., the so-called N1 interface and / or equivalent). The N1 interface is responsible for providing communication between the UE3 and AMF70 to support NAS signaling. The N1 interface can be established for both 3GPP and non-3GPP access. For example, the following messages are communicated over the N1 interface:

[0168] -Registration request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may also be included 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, 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 ID.ID), Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.

[0169] -Registration approval message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this manner, the following parameters may also be included in the registration approval 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 valueThe following are included: value, 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.

[0170] -Registration completion message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this manner, the following parameters may also be included in the registration completion message. --SOR transparent container.

[0171] - Authentication request message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be included in the authentication request message. --ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge), and EAP message.

[0172] - Authentication response message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be present in the authentication response message. --Authentication response message identity, authentication response parameter, and EAP message.

[0173] - Authentication result message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may also be present in the authentication result message. --ngKSI, EAP message, and ABBA.

[0174] - Authentication failure message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may also be present in the authentication failure message. --Authentication failure message identity, 5GMM cause, and authentication failure parameter.

[0175] - Authentication denial message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be present in the authentication denial message. --EAP message.

[0176] - Service request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be present in the service request message. --ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.

[0177] - Service authorization message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this manner, the following parameters may also be present in the service authorization message. --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0178] - Denial of Service Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this manner, the following parameters may also be present in the denial of service message. --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0179] -Configuration update command message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may also be present 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.

[0180] -Configuration update complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may also be present in the configuration update complete message. --Configuration update complete message identity.

[0181] <User Equipment (UE)> Figure 5 is a block diagram showing the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31, which is operable to transmit signals to and receive signals from connected nodes via one or more antennas 32. Furthermore, UE3 may include a user interface 34 for inputting or outputting information externally. Although not necessarily shown in the figure, UE3 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 UE3 according to the software stored in memory 36. The software includes, in particular, an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for processing (generating / transmitting / receiving) signaling and uplink / downlink data packets between the UE3 and other nodes such as the (R)AN node 5 and AMF70. Such signaling may include appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. If there are multiple USIMs 35, the controller 33 may activate only one USIM 35 or multiple USIMs 35 simultaneously.

[0182] UE3 can support, for example, Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0183] UE3 may be, for example, items of equipment for production or manufacturing, and / or items of energy-related machinery (e.g., boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power 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 their application systems, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machinery, printing machinery and / or related machinery, paperwork machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, machinery and / or equipment for agriculture, forestry and / or fishing, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the aforementioned equipment or machinery).

[0184] UE3 can be, for example, transportation equipment items (e.g., vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other vessels, aircraft, rockets, satellites, drones, balloons and other transportation equipment).

[0185] UE3 can be, for example, an item of information and communication equipment (e.g., electronic computers and related equipment, communication and related equipment, electronic components, and other information and communication equipment).

[0186] UE3 may include, for example, refrigeration machines, refrigeration machine applications, items of commercial and / or service industry equipment, vending machines, automated service machines, office machines or equipment, consumer electronics and electronic devices (e.g., consumer electronic devices 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.).

[0187] UE3 may be, for example, an electrical application system or device (e.g., an electrical application system or device such as an X-ray system, particle accelerator, radioisotope device, sound wave device, electromagnetic application device, power application device, etc.).

[0188] UE3 may include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or surveying or detection equipment (such as smoke detectors, human alarm sensors, motion sensors, wireless tags, etc.), wristwatches or wall clocks, laboratory equipment, optical devices, medical equipment and / or systems, weapons, cutlery items, hand tools, or similar items.

[0189] UE3 could be, for example, a wireless-equipped personal digital assistant or related device (such as a wireless card or module designed to be attached to or inserted into another electronic device, e.g., a personal computer, an electrical measuring instrument).

[0190] UE3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below in relation to the Internet of Things (IoT).

[0191] An Internet of Things (IoT) device (or "Thing") may include appropriate electronics, software, sensors, network connectivity, and / or similar, so that it can collect and exchange data with each other and with other communication devices. IoT devices may include automated devices that follow software instructions stored in internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices may also remain stationary and / or stopped for extended periods. IoT devices may be implemented as part of (generally) fixed equipment. IoT devices may also be incorporated into non-fixed equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0192] Whether such communication devices are controlled by human input or by software instructions stored in memory, it will be understood that IoT technology can be implemented on any communication device that can connect to a communication network for sending / receiving data.

[0193] It will be understood that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band IoT UEs (NB-IoT UEs). It will be understood that UE3 can support one or more IoT or MTC applications.

[0194] UE3 can be a smartphone or a wearable device (e.g., smart glasses, a smartwatch, a smart ring, or a hearable device).

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

[0196] <(R)AN node> Figure 6 is a block diagram showing the main components of an exemplary (R)AN node 5, for example, a base station ("eNB" in LTE, "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is 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 via a network interface 53 (directly or indirectly). A controller 54 controls the operation of the (R)AN node 5 according to software stored in memory 55. 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 software includes, in particular, an operating system 551 and a communication control module 552 having at least a transceiver control module 5521.

[0197] 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 (such as RRC connection establishment messages and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages at the N2 reference point), Xn application protocol (XnAP) messages (i.e., messages at the Xn reference point), etc., regarding the radio connection and connection to the core network 7 for a specific UE 3, particularly regarding connection establishment and maintenance. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

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

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

[0200] <System overview of (R)AN node 5 based on the O-RAN architecture> FIG. 7 schematically shows the (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.

[0201] A (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 embodiments, each unit may be combined. For example, RU 60 may be integrated / coupled with DU 61 as an integration / coupling unit, and DU 61 may be integrated / coupled with CU 62 as another integration / coupling unit. Any function in the description of a unit (e.g., one of RU 60, DU 61, and CU 62) may be implemented in the above integration / coupling unit. Furthermore, CU 62 may be separated into two functional units, such as a Control plane (CP) and a User plane (UP). CU CP has control plane functionality in (R)AN node 5. CU UP has user plane functionality in (R)AN node 5. Each CU CP is connected to a CU UP via an appropriate interface (such as the so-called "E1" interface and / or similar).

[0202] UE3 and each serving RU60 are connected via appropriate air interfaces (e.g., so-called "Uu" interfaces and / or similar). Each RU60 is connected to DU61 via appropriate interfaces (such as so-called "fronthaul," "open fronthaul," "F1" interfaces, and / or similar). Each DU61 is connected to CU62 via appropriate interfaces (such as so-called "midhaul," "open midhaul," "E2" interfaces, and / or similar). Each CU62 is also connected to nodes in the core network 7 (such as so-called core network nodes) via appropriate interfaces (such as so-called "backhaul," "open backhaul," "N2" / "N3" interfaces, and / or similar). In addition, the user plane portion of DU61 may also be connected to core network node 7 via appropriate interfaces (such as so-called "N3" interfaces and / or similar).

[0203] Depending on the functions separated between RU60, DU61, and CU62, each unit provides a portion of the functions provided by (R)AN node 5. For example, RU60 may provide the function to communicate with UE3 on the air interface, DU61 may provide the function to support the MAC and RLC layers, and CU62 may provide the function to support the PDCP, SDAP, and RRC layers.

[0204] <Radio Unit (RU)> Figure 8 is a block diagram showing the main components of the RU portion of an exemplary RU60, for example, a base station ("eNB" in LTE, "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the RU60 includes a transceiver circuit 601 which is operable to transmit signals to and receive signals from connected UE3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or network units via the network interface 603 (directly or indirectly). The controller 604 controls the operation of the RU60 according to software stored in memory 605. 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 software includes, in particular, an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521.

[0205] The communication control module 6052 (using its transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between RU60 and other nodes or units such as UE3, another RU60, and DU61 (for example, directly or indirectly). The signaling may include appropriately formatted signaling messages relating to the radio connection and connectivity with RU60 (for a particular UE3), particularly concerning the MAC and RLC layers.

[0206] The controller 604, once implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0207] The RU60 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0208] As described above, RU60 can be integrated / coupled to DU61 as an integration / coupling unit. Any functions described in the description of RU60 can be implemented in the above integration / coupling unit.

[0209] <Distributed Unit (DU)> Figure 9 is a block diagram showing the main components of the DU portion of an exemplary DU61, for example, a base station ("eNB" in LTE, "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the device includes a transceiver circuit 611, which is operable to transmit signals to and receive signals from other nodes or units (including RU60) via a network interface 612. A controller 613 controls the operation of the DU61 according to 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, in particular, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 is responsible for processing (generating / transmitting / receiving) signaling between DU61 and other nodes or units such as RU60 and other nodes and units, using its transceiver control module 61421.

[0210] DU61 can support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0211] As described above, RU60 can be integrated / connected to DU61 or CU62 as an integration / connection part. Any function in the description of DU61 can be implemented in one of the above integration / connection parts.

[0212] <Centralized Unit (CU)> FIG. 10 is a block diagram showing the main components of an exemplary CU62, for example, the CU part of a base station (such as "eNB" in LTE, "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621, and the transceiver circuit 621 is operable to transmit signals to other nodes or units (including DU61) and receive signals from other nodes or units (including DU61) via a network interface 622. A controller 623 controls the operation of CU62 according to software stored in a memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded via a telecommunication network or from a removable data storage device (RMD). The software particularly includes an operating system 6241 and a communication 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 processing (generating / sending / receiving) signaling between CU62 and other nodes or units such as DU61 and other nodes or units.

[0213] CU62 can support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0214] As described above, CU62 can be integrated / connected to DU61 as an integration / connection unit. Any function in the description of CU62 can be implemented in the above integration / connection unit.

[0215] <amf> Figure 11 is a block diagram showing the main components of the AMF70. As shown, the device includes a transceiver circuit 701, which is operable to transmit signals to and receive signals from other nodes (including UE3 and NSSAAF76) via a network interface 702. A controller 703 controls the operation of the AMF70 according to software stored in memory 704. For example, the software may be pre-installed in memory 704 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, in particular, an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 is responsible for processing (generating / transmitting / receiving) signaling between the AMF 70 and other nodes, such as UE3 (e.g., via (R)AN node 5) and other core network nodes, including the core network node in HPLMN of UE3 when UE3 is roaming in. Such signaling may include appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for UE3).

[0216] The AMF70 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AMF7001 and AMF7002 may have the same components as the AMF70.

[0217] <pcf> Figure 12 is a block diagram showing the main components of PCF73. As shown, the device includes a transceiver circuit 731, which is operable to transmit signals to and receive signals from other nodes (including AMF70) via a network interface 732. A controller 733 controls the operation of PCF73 according to software stored in memory 734. For example, the software may be pre-installed in 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, in particular, an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / transmitting / receiving) signaling between the PCF73 and other nodes, such as the AMF70 and other core network nodes, including the core network node in the HPLMN of the UE3 when the UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) relating to policy management procedures (about the UE3).

[0218] PCF73 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). PCF7301 and PCF7302 may have the same components as PCF73.

[0219] <ausf> Figure 13 is a block diagram showing the main components of AUSF74. As shown, the device includes a transceiver circuit 741, which is operable to transmit signals to and receive signals from other nodes (including UDM75) via a network interface 742. A controller 743 controls the operation of AUSF74 according to 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, in particular, an operating system 7441 and a communication control module 7442 having at least a transceiver control module 74421. The communication control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / transmitting / receiving) signaling between AUSF74 and other nodes, such as AMF70 and other core network nodes, including the core network node in the HPLMN of UE3 when UE3 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 (about UE3).

[0220] AUSF74 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0221] <udm> Figure 14 is a block diagram showing the main components of the UDM 75. As shown, the device includes a transceiver circuit 751, which is 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 according to 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, in particular, an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421. The communication control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / transmitting / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes, including the core network node in the VPLMN of the UE3 when the UE3 is roaming out. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) relating to mobility management procedures (about the UE3).

[0222] The UDM75 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0223] <nssaaf> Figure 15 is a block diagram showing the main components of NSSAAF76. As shown, the device includes a transceiver circuit 761 which is operable to transmit signals to and receive signals from other nodes (including AMF70 and AAA Proxy (AAA-P)) via a network interface 762. A controller 763 controls the operation of NSSAAF76 according to 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, in particular, 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 / transmitting / receiving) signaling between NSSAAF76 and other nodes, such as AMF70 and other core network nodes, including the core network node in the VPLMN of UE3 when UE3 is roaming out. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) relating to mobility management procedures (for UE3).

[0224] NSSAAF76 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0225] Exemplary aspects of the above disclosure may be described, but are not limited to, the following:

[0226] 5.5.1.2.2 Initial registration begins The subset of configuration NSSAI provided in a request NSSAI consists of one or more S-NSSAI in configuration NSSAI applicable to the current PLMN, if the S-NSSAI is neither in a reject NSSAI f nor related to an S-NSSAI in a reject NSSAI. In addition, if NSSRG information is available, the subset of configuration NSSAI provided in a request NSSAI shall be related to at least one common NSSRG value. If the UE has a pending NSSAI, the subset of configuration NSSAI provided in the request NSSAI and the pending NSSAI shall be related to at least one common NSSRG value. If the UE already has an authorization NSSAI for other accesses, all S-NSSAI in the request NSSAI for the current access shall share at least an NSSRG value common to all S-NSSAI in the authorization NSSAI for the other accesses. If the UE is simultaneously performing registration procedures for other accesses, the UE shall include S-NSSAI that share at least one common NSSRG value across all access types.

[0227] 5.5.1.2.3 5GMM Common Procedure Start AMF may include a new configuration NSSAI for the current PLMN in the REGISTRATION ACCEPT message in the following cases:

[0228] a) If the REGISTRATION REQUEST message does not contain a requested NSSAI and the initial registration request is not for an installed service in SNPN,

[0229] b) If the REGISTRATION REQUEST message contains a request NSSAI that is not valid in the serving PLMN,

[0230] c) If the REGISTRATION REQUEST message contains a requested NSSAI that includes an S-NSSAI with an inaccurate mapping S-NSSAI,

[0231] d) If the REGISTRATION REQUEST message contains a network slicing indication IE with a default configuration NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI", or

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

[0233] f) If the UE has a pending NSSAI and the S-NSSAI of the requested NSSAI within the REGISTRATION REQUEST message and the pending NSSAI are not associated with a common NSSRG value.

[0234] g) If the UE already has a permitted NSSAI for another access and the S-NSSAI of the requested NSSAI within the REGISTRATION REQUEST message for the current access and the permitted NSSAI are not associated with a common NSSRG value

[0235] 5.5.1.3.2 Mobility and periodic registration update start The subset of configuration NSSAI provided in a request NSSAI consists of one or more S-NSSAI in configuration NSSAI applicable to this PLMN, if the S-NSSAI is neither in a rejection NSSAI nor related to an S-NSSAI in a rejection NSSAI. In addition, if NSSRG information is available, the subset of configuration NSSAI provided in a request NSSAI shall be related to at least one common NSSRG value. If the UE has a pending NSSAI, the subset of configuration NSSAI provided in the request NSSAI and the pending NSSAI shall be related to at least one common NSSRG value. If the UE already has an authorization NSSAI for other accesses, all S-NSSAI in the request NSSAI for the current access shall share at least an NSSRG value common to all S-NSSAI in the authorization NSSAI for the other accesses. If the UE is simultaneously performing registration procedures for other accesses, the UE shall include S-NSSAI that share at least one common NSSRG value across all access types.

[0236] 5.5.1.3.3 5GMM Common Procedure Start AMF may include a new configuration NSSAI for the current PLMN in the REGISTRATION ACCEPT message in the following cases:

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

[0238] b) If the REGISTRATION REQUEST message contains a request NSSAI that is not valid in the serving PLMN,

[0239] c) If the REGISTRATION REQUEST message contains a request NSSAI that includes an inaccurate S-NSSAI, d) If the REGISTRATION REQUEST message contains a network slicing display IE that has a default configuration NSSAI display bit set to "Request NSSAI created from default configuration NSSAI",

[0240] e) If the registration request message included a request mapping NSSAI,

[0241] f) If any two S-NSSAIs in the REGISTRATION REQUEST message are not related to any common NSSRG value.

[0242] f) When UE has a pending NSSAI, and the S-NSSAI and pending NSSAI of the requested NSSAI in the REGISTRATION REQUEST message are not related to a common NSSRG value.

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

[0244] <Corrections and Alterations> Detailed embodiments are described above. Those skilled in the art will understand that numerous modifications and substitutions can be made to the above embodiments, still benefiting from the disclosure as embodied herein. Numerous such substitutions and modifications are described herein merely as examples.

[0245] In the above description, the UE3 and network device are described as having a number of separate modules (such as communication control modules) for ease of understanding. These modules may thus be provided, for example, in a system designed from the outset to take the features of the invention into consideration, for other applications, for example, in an existing system that has been modified to implement the disclosure, but these modules may not be recognizable as separate entities, as they may be built within an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a combination thereof.

[0246] Each controller may include, but is not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (for programs 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 similar.

[0247] In the above embodiments, numerous 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 supplied to the UE3 and network devices as signals on a computer network or on a recording medium. Furthermore, some or all of the functions performed by 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 UE3 and network devices in order to facilitate updates to the UE3 and network devices.

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

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

[0250] Various other modifications are obvious to those skilled in the art, and therefore no further details are provided here.

[0251] As those skilled in the art will understand, this disclosure can be embodied as a method and a system. Accordingly, this disclosure may take the form of a complete hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0252] It will be understood that each block in a block diagram can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device to generate a machine, and as a result, instructions executed through the processor of the computer or other programmable data processing device generate means for implementing the functions / actions specified in the blocks or blocks(s) of the flowchart and / or block diagram. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a computing device, e.g., multiple microprocessors, one or more microprocessors, or any other combination of such configurations.

[0253] Methods or algorithms described in connection with the examples disclosed herein may be directly embodied in hardware, software modules executed by a processor, or a combination of both. The software modules may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. The storage medium may be connected to the processor so 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 storage medium may reside in an ASIC.

[0254] The prior description relating to the examples of this disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to such examples will be readily apparent to a person skilled in the art, and the general principles set forth herein may be applied to other examples without departing from the spirit or scope of this disclosure. Accordingly, this disclosure is not intended to be limited to the examples shown herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

[0255] While this disclosure has been described in detail with reference to exemplary embodiments thereof, this disclosure is not limited to such embodiments. Those skilled in the art will understand that various modifications in form and detail are possible without departing from the intent and scope of this disclosure as defined herein. For example, the embodiments described above are not limited to 5GS, and are applicable to other communication systems (e.g., 6G systems, Beyond 5G systems).

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

[0257] Note 1. A method for user equipment (UE), wherein the method is A message containing pending network slice selection assistance information (NSSAI) is received. The aforementioned pending NSSAI includes the first Single Network Slice Selection Assistance Information (S-NSSAI), When a registration procedure using the second S-NSSAI is triggered, it is checked 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, a registration request message including the second S-NSSAI is sent. method.

[0258] Note 2. A method for a communication device, wherein the method is Send a first message containing Network Slice Selection Assistance Information (NSSAI), The aforementioned pending NSSAI includes the first Single Network Slice Selection Assistance Information (S-NSSAI), Upon receiving a registration request message containing a request for NSSAI, The aforementioned request NSSAI includes a second S-NSSAI, We 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. If the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, a second message including the configuration NSSAI is sent. method.

[0259] Note 3. User equipment (UE), where the UE is A means for receiving a message containing pending network slice selection assistance information (NSSAI), The aforementioned reserved NSSAI includes means, which include first Single Network Slice Selection Assistance Information (S-NSSAI), When a registration procedure using a second S-NSSAI is triggered, 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, If the first S-NSSAI and the second S-NSSAI are related to the at least one common NSSRG value, means for sending a registration request message including the second S-NSSAI, A UE equipped with

[0260] Note 4. A communication device, wherein the communication device is A means for transmitting a first message including pending network slice selection assistance information (NSSAI), The aforementioned reserved NSSAI includes means, which include first Single Network Slice Selection Assistance Information (S-NSSAI), A means for receiving a registration request message including a request NSSAI, The aforementioned request NSSAI includes means, including a second S-NSSAI, A 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, A means for sending a second message including a configuration NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, A communication device equipped with the following features.

[0261] Note 5. A method for a communication device, wherein the method is In a certain access, a registration procedure is performed using the first Single Network Slice Selection Assistance Information (S-NSSAI), In another access, a registration request message including a second S-NSSAI was received. We 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. If the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, a message including the configuration NSSAI is sent. method.

[0262] Note 6. User equipment (UE) method, wherein the method is In a certain access, a registration procedure is performed using the first Single Network Slice Selection Assistance Information (S-NSSAI), In another access, a registration request message including a second S-NSSAI is sent, 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, a message containing the configuration NSSAI is received. method.

[0263] Note 7. A communication device, wherein the communication device is In a certain access, a means for performing a registration procedure using the first Single Network Slice Selection Assistance Information (S-NSSAI), In another access, means for receiving a registration request message including a second S-NSSAI, A 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, A means for sending a message including a configuration NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, A communication device equipped with the following features.

[0264] Note 8. User equipment (UE), wherein the UE is In a certain access, a means for performing a registration procedure using the first Single Network Slice Selection Assistance Information (S-NSSAI), In another access, means for sending a registration request message including a second S-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, means for receiving a message containing the configuration NSSAI, A UE equipped with

[0265] <Note 2> Note 1. Communicates with user equipment (UE), If the first Single Network Slice Selection Assistance Information (S-NSSAI) in the requested Network Slice Selection Assistance Information (NSSAI) within the registration request message in the first access, and the second S-NSSAI in the authorized NSSAI in the second access, do not relate to a common Network Slice Simultaneous Registration Group (NSSRG) value, then a registration approval message is sent. The aforementioned registration approval message includes the configuration NSSAI, Methods for communication devices.

[0266] Note 2. The aforementioned communication device is an Access and Mobility Management Function (AMF). The method described in Appendix 1.

[0267] Note 3. In the first access, a registration request message is sent, The registration request message includes Network Slice Selection Assistance Information (NSSAI), If the first Single Network Slice Selection Assistance Information (S-NSSAI) of the requested NSSAI in the registration request message and the second S-NSSAI of the permitted NSSAI in the second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value, then a registration approval message is received. The aforementioned registration approval message includes the configuration NSSAI, User Equipment (UE) method.

[0268] Note 4. Means for communicating with user equipment (UE), A means for sending a registration approval message when the first Single Network Slice Selection Assistance Information (S-NSSAI) of the requested Network Slice Selection Assistance Information (NSSAI) in the registration request message during the first access, and the second S-NSSAI of the authorized NSSAI during the second access, are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value. Equipped with, The aforementioned registration approval message includes the configuration NSSAI, Communication device.

[0269] Note 5. The aforementioned communication device is an Access and Mobility Management Function (AMF). The communication device described in Appendix 4.

[0270] Note 6. In the first access, a means for sending a registration request message, The registration request message includes means, which include Network Slice Selection Assistance Information (NSSAI), If the first Single Network Slice Selection Assistance Information (S-NSSAI) of the requested NSSAI in the registration request message and the second S-NSSAI of the permitted NSSAI in the second access are not related to a common Network Slice Simultaneous Registration Group (NSSRG) value, then a means for receiving a registration approval message is provided. Equipped with, The aforementioned registration approval message includes the configuration NSSAI, User equipment (UE).

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

[0272] This application claims priority based on Indian Provisional Patent Application No. 202211016660, filed on 24 March 2022, and incorporates all of its disclosures herein. [Explanation of Symbols]

[0273] 1. Telecommunications Systems 3 UE 5 (R)AN Node 7 Core Network 20 Data Networks 31 Transceiver Circuit 32 Antennas 33 Controllers 34 User Interface 35 USIM 36 memory 51 Transceiver Circuit 52 Antennas 53 Network Interfaces 54 Controllers 55 memory 60 RU 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 Interfaces 613 Controller 614 memory 621 Transceiver Circuit 622 Network Interfaces 623 Controller 624 memory 701 Transceiver Circuit 702 Network Interface 703 Controller 704 memory 731 Transceiver Circuit 732 Network Interfaces 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 Systems 6142 Communication control module 6241 Operating Systems 6242 Communication control module 7041 Operating System 7042 Communication control module 7341 Operating Systems 7342 Communication control module 7441 Operating Systems 7442 Communication control module 7541 Operating Systems 7542 Communication control module 7641 Operating Systems 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. The registration procedure in 3GPP® access is performed with a user device having Allowed Network Slice Selection Assistance Information (NSSAI) including a first Single Network Slice Selection Assistance Information (S-NSSAI), In non-3GPP access, a Registration Request message containing a second S-NSSAI in the Requested NSSAI is received from the user device. It is determined whether the first S-NSSAI in the Allowed NSSAI and the second S-NSSAI in the Requested NSSAI in the Registration Request message are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. A Registration Accept message is sent to the user device. The Registration Accept message includes a new Configured NSSAI if the first S-NSSAI in the 3GPP access and the second S-NSSAI in the non-3GPP access are not related to a common NSSRG value. Methods for communication devices.

2. In 3GPP access, a registration procedure is performed with a communication device using Allowed Network Slice Selection Assistance Information (NSSAI) which includes a first Single Network Slice Selection Assistance Information (S-NSSAI), In non-3GPP access, a Registration Request message including a second S-NSSAI is sent to the communication device in the Requested NSSAI. Upon receiving a Registration Accept message from the aforementioned communication device, The Registration Accept message includes a new Configured NSSAI if the first S-NSSAI in the 3GPP access and the second S-NSSAI in the non-3GPP access are not related to a common NSSRG value. User device method.

3. Means for performing a registration procedure in 3GPP access with a user device having Allowed Network Slice Selection Assistance Information (NSSAI) including a first Single Network Slice Selection Assistance Information (S-NSSAI), In non-3GPP access, means for receiving a Registration Request message from the user device that includes a second S-NSSAI in the Requested NSSAI, A means for determining whether the first S-NSSAI in the Allowed NSSAI and the second S-NSSAI in the Requested NSSAI in the Registration Request message are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value, means for sending a Registration Accept message to the user device Equipped with, The Registration Accept message includes a new Configured NSSAI if the first S-NSSAI in the 3GPP access and the second S-NSSAI in the non-3GPP access are not related to a common NSSRG value. Communication device.

4. The aforementioned communication device is an Access and Mobility Management Function (AMF). The communication device according to claim 3.

5. A means for performing a registration procedure with a communication device using Allowed Network Slice Selection Assistance Information (NSSAI) including a first Single Network Slice Selection Assistance Information (S-NSSAI) in 3GPP access, In non-3GPP access, means for sending a Registration Request message including a second S-NSSAI to the communication device in the Requested NSSAI, means for receiving a Registration Accept message from the aforementioned communication device Equipped with, The Registration Accept message includes a new Configured NSSAI if the first S-NSSAI in the 3GPP access and the second S-NSSAI in the non-3GPP access are not related to a common NSSRG value. User device.

Images