Method of user equipment (UE), UE, method of communication device and communication device
By checking and processing the correlation between NSSAI and NSSRG between user equipment and communication equipment, the problem of fuzzy description of NSSRG feature processing in the 3GPP specification is solved, ensuring the accuracy of network slice selection and the smooth progress of the registration process, and improving the system stability and efficiency.
Patent Information
- Application Number
- CN202380029613.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-24
- Filing Date
- 2023-03-17
- Publication Date
- 2024-11-08
AI Technical Summary
In the 3GPP specification, there is a vague description of the processing of NSSRG features, resulting in the network slice registration group that cannot work properly when the user equipment maintains the old network slice configuration and NSSRG information.
Check whether the suspended NSSAI and the requested NSSAI are registered simultaneously with at least one common network slice by sending and receiving a registration request message between the user equipment (UE) and the communication device, including the requested network slice selection assistance information (NSSAI). Group values (NSSRGs) are associated and send a registration request message in the case of association, or a configuration message in the case of not association.
It solves the problem that NSSRG features cannot work properly under the old configuration, ensures the accuracy of network slice selection and the smooth progress of the registration process, and improves the stability and efficiency of the system.
Smart Images

Figure CN118923154A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a method of a user equipment (UE), a UE, a method of a communication device, and a communication device. Background Art
[0002] NSSRG (Network Slice Simultaneous Registration Group) was introduced to 5GS in Release 17. The NSSRG feature provides 3GPP operators with a mechanism to restrict the combinations of network slices to be registered simultaneously.
[0003] Citation List
[0004] Non-patent literature
[0005] [Non-patent document 1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. V17.1.0 (2021-12)
[0006] [Non-patent document 2] 3GPP TS23.501: "System architecture for the 5G System (5GS)". V17.3.0 (2021-12)
[0007] [Non-patent document 3] 3GPP TS23.502: "Procedures for the 5G System (5GS)". V17.3.0 (2021-12)
[0008] [Non-patent document 4] 3GPP TS23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V17.3.0 (2021-12) Summary of the invention
[0009] Technical issues
[0010] However, there are many ambiguous descriptions in the 3GPP specification(s) on how to handle the NSSRG feature.
[0011] For example, the present disclosure provides a solution to this problem.
[0012] Solution to the problem
[0013] In an aspect of the present disclosure, a method of a user equipment (UE) includes: communicating with a communication device; and sending a registration request message. The registration request message includes requested network slice selection assistance information (i.e., requested NSSAI). The requested NSSAI includes first single network slice selection assistance information (i.e., first S-NSSAI). The first S-NSSAI and a second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value (i.e., at least one common NSSRG value).
[0014] In an aspect of the present disclosure, a user equipment, i.e., UE, includes: a component for communicating with a communication device; and a component for sending a registration request message. The registration request message includes requested network slice selection assistance information, i.e., requested NSSAI. The requested NSSAI includes first single network slice selection assistance information, i.e., first S-NSSAI. The first S-NSSAI and a second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0015] In an aspect of the present disclosure, a method of a communication device includes: communicating with a user equipment (UE). The method includes: sending a message. The message includes allowed network slice selection assistance information (i.e., allowed NSSAI). The allowed NSSAI includes first single network slice selection assistance information (i.e., first S-NSSAI). The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value (i.e., at least one common NSSRG value).
[0016] In an aspect of the present disclosure, a communication device includes: a component for communicating with a user equipment, i.e., a UE. The communication device includes: a component for sending a message. The message includes allowed network slice selection assistance information, i.e., allowed NSSAI. The allowed NSSAI includes a first single network slice selection assistance information, i.e., a first S-NSSAI. The first S-NSSAI and a second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0017] In an aspect of the present disclosure, a method of a communication device includes: sending a first message including pending network slice selection assistance information, i.e., pending NSSAI. The pending NSSAI includes first single network slice selection assistance information, i.e., first S-NSSAI. The method includes: receiving a registration request message including a requested NSSAI. The requested NSSAI includes a second S-NSSAI. The method includes: checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value. The method includes: sending a second message including a configured NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
[0018] In an aspect of the present disclosure, a communication device includes: a component for sending a first message including pending network slice selection assistance information, i.e., pending NSSAI. The pending NSSAI includes a first single network slice selection assistance information, i.e., a first S-NSSAI. The communication device includes: a component for receiving a registration request message including a requested NSSAI. The requested NSSAI includes a second S-NSSAI. The communication device includes: a component for checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value. The communication device includes: a component for sending a second message including a configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 is a signalling diagram of a first example of the first aspect (NSSRG check in UE with S-NSSAI(s) in suspended NSSAI).
[0020] Figure 2 2 is a signalling diagram of a second example of the first aspect (NSSRG check in AMF utilizing (one or more than one) S-NSSAI in suspended NSSAI).
[0021] Figure 3 2 is a signalling diagram of a first example of the second aspect (NSSRG check in AMF utilizing (one or more than one) S-NSSAI in a suspended NSSAI for other accesses).
[0022] Figure 4 is a block diagram illustrating an overview of the system.
[0023] Figure 5 is a block diagram illustrating a user equipment (UE).
[0024] Figure 6 is a block diagram of an example (R)AN node.
[0025] Figure 7 is a diagram illustrating a system overview of an (R)AN node based on an O-RAN architecture.
[0026] Figure 8 is a block diagram illustrating a radio unit (RU).
[0027] Fig. 9 is a block diagram illustrating a distributed unit (DU).
[0028] Fig.10 is a block diagram illustrating a centralized unit (CU).
[0029] Fig.11 is a block diagram illustrating an access and mobility management function (AMF).
[0030] Fig.12 is a block diagram illustrating a Policy Control Function (PCF).
[0031] Fig.13 is a block diagram illustrating an Authentication Server Function (AUSF).
[0032] Fig.14 is a block diagram illustrating unified data management (UDM).
[0033] Fig.15 is a block diagram illustrating the Network Slice Specific Authentication and Authorization Function (NSSAAF). DETAILED DESCRIPTION
[0034] <Abbreviation>
[0035] For the purpose of this document, the abbreviations given in Non-Patent Document 1 and below apply. Abbreviations defined in this document take precedence over the definition of the same abbreviations in Non-Patent Document 1 (if any).
[0036] 4G-GUTI 4G Globally Unique Temporary UE Identifier
[0037] 5GC 5G Core Network
[0038] 5GLAN 5G Local Area Network
[0039] 5GS 5G System
[0040] 5G-AN 5G Access Network
[0041] 5G-AN PDB 5G access network packet delay budget
[0042] 5G-EIR 5G-Equipment Identification Register
[0043] 5G-GUTI 5G Globally Unique Temporary Identifier
[0044] 5G-BRG 5G Broadband Home Gateway
[0045] 5G-CRG 5G Cable Home Gateway
[0046] 5G GM 5G Master Clock
[0047] 5G-RG 5G Home Gateway
[0048] 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier
[0049] 5G VN 5G Virtual Network
[0050] 5QI 5G QoS Identifier
[0051] AF Application Function
[0052] AMF Access and Mobility Management Function
[0053] AMF-G Geographically Selected Access and Mobility Management Function
[0054] AMF-NG Non-geo-selective Access and Mobility Management Function
[0055] ANDSF Access Network Discovery and Selection Function
[0056] AS Access Layer
[0057] ATSSS access traffic guidance, switching, and splitting
[0058] ATSSS-LL ATSSS Low Level
[0059] AUSF authentication server function
[0060] AUTN Authentication Token
[0061] BCCH Broadcast Control Channel
[0062] BMCA Best Master Clock Algorithm
[0063] BSF binding support function
[0064] CAG Closed Access Group
[0065] CAPIF 3GPP Northbound API Common API Framework
[0066] CHF billing function
[0067] CN PDB Core Network Packet Delay Budget
[0068] CP Control Plane
[0069] DAPS Dual Active Protocol Stack
[0070] DL Downlink
[0071] DN Data Network
[0072] DNAI DN Access Identifier
[0073] DNN data network name
[0074] DRX Discontinuous Reception
[0075] DS-TT Device-side TSN Converter
[0076] ePDG Evolved Packet Data Gateway
[0077] EBI EPS bearer logo
[0078] EPS Evolved Packet System
[0079] EUI Extended Unique Identifier
[0080] FAR forwarding action rule
[0081] FN-BRG Fixed Broadband RG
[0082] FN-CRG Fixed Network Cable RG
[0083] FN-RG Fixed Network RG
[0084] FQDN Fully Qualified Domain Name
[0085] GFBR Guaranteed Streaming Bit Rate
[0086] GMLC Gateway Mobile Location Center
[0087] GPSI General Public Subscription Identifier
[0088] GUAMI Globally Unique AMF Identifier
[0089] GUTI Globally Unique Temporary UE Identifier
[0090] HPLMN Home Public Land Mobile Network
[0091] HR Home Router (Roaming)
[0092] IAB Integration Access and Postbacks
[0093] IMEI / TAC IMEI type allocation code
[0094] IPUPS PLMN Inter-UP Security
[0095] I-SMF Intermediate SMF
[0096] I-UPF Intermediate UPF
[0097] LADN Local Area Data Network
[0098] LBO Local Flow Offload (Roaming)
[0099] LMF Location Management Function
[0100] LoA Automation Level
[0101] LPP LTE Positioning Protocol
[0102] LRF location search function
[0103] MCC Mobile Country Code
[0104] MCX Mission Critical Services
[0105] MDBV Maximum data burst volume
[0106] MFBR Maximum Streaming Bit Rate
[0107] MICO Only mobile terminals initiate connections
[0108] MITM
[0109] MNC Mobile Network Code
[0110] MPS Multimedia Priority Service
[0111] MPTCP Multipath TCP Protocol
[0112] N3IWF Non-3GPP Interworking Function
[0113] N3GPP Non-3GPP Access
[0114] N5CW WLAN side does not have 5G capability
[0115] NAI Network Access Identifier
[0116] NAS Non-Access Stratum
[0117] NEF Network Exposure Function
[0118] NF Network Function
[0119] NGAP Next Generation Application Protocol
[0120] NID Network Identifier
[0121] NPN Non Public Network
[0122] NR New Radio
[0123] NRF Network Repository Features
[0124] NSI ID Network Slice Instance Identifier
[0125] NSSAA Network Slice Specific Authentication and Authorization
[0126] NSSAAF Network Slice Specific Authentication and Authorization Function
[0127] NSSAI Network Slice Selection Assistance Information
[0128] NSSF network slice selection function
[0129] NSSP network slice selection strategy
[0130] NSSRG Network Slicing Simultaneous Registration Group
[0131] NW-TT Network-side TSN converter
[0132] NWDAF network data analysis function
[0133] PCF Policy Control Function
[0134] PCO Protocol Configuration Options
[0135] PDB Packet Delay Budget
[0136] PDR Group Detection Rules
[0137] PDU Protocol Data Unit
[0138] PEI Persistent Equipment Identifier
[0139] PER Packet Error Rate
[0140] PFD Packet Flow Description
[0141] PLMN Public Land Mobile Network
[0142] PNI-NPN Public Network Integrated Non-Public Network
[0143] PPD Paging Policy Differential
[0144] PPF Paging Process Flag
[0145] PPI Paging Policy Indicator
[0146] PSA PDU Session Anchor
[0147] PTP Precision Time Protocol
[0148] QFI QoS Flow Identifier
[0149] QoE Quality of Experience
[0150] RACS Radio Capability Signaling Optimization
[0151] (R)AN (Radio) Access Network
[0152] RAT Radio Access Technology
[0153] RG Home Gateway
[0154] RIM Remote Interference Management
[0155] RQA Reflective QoS Attribute
[0156] RQI Reflective QoS Indicator
[0157] RSN Redundant Sequence Number
[0158] SA NR Independent New Radio
[0159] SBA Service-Based Architecture
[0160] SBI Service-Based Interface
[0161] SCP Service Communication Proxy
[0162] SD Slice Specifier
[0163] SEAF safety anchor function
[0164] SEPP Security Edge Protection Proxy
[0165] SMF session management functions
[0166] SMSF Short Message Service Function
[0167] SN Serial Number
[0168] SN Name Service Network Name
[0169] SNPN Standalone Non Public Network
[0170] S-NSSAI Single Network Slice Selection Auxiliary Information
[0171] SSC Session and Service Continuity
[0172] SSCMSP Session and Service Continuity Mode Selection Policy
[0173] SST Slice / Service Type
[0174] SUCI Subscription Hidden Identifier
[0175] SUPI Subscription Persistent Identifier
[0176] SV Software Version
[0177] TMSI Temporary Mobile Subscriber Identity
[0178] TNAN Trusted Non-3GPP Access Network
[0179] TNAP Trusted Non-3GPP Access Point
[0180] TNGF Trusted Non-3GPP Gateway Function
[0181] TNL Transport Network Layer
[0182] TNLA Transport Network Layer Association
[0183] TSC Time Sensitive Communications
[0184] TSCAI TSC Auxiliary Information
[0185] TSN Time Sensitive Network
[0186] TSN GM TSN Master Clock
[0187] TSP Traffic Steering Strategy
[0188] TT TSN Converter
[0189] TWIF Trusted WLAN Intercommunication Function
[0190] UCMF UE radio capability management function
[0191] UDM Unified Data Management
[0192] UDR Unified Data Repository
[0193] UDSF unstructured data storage function
[0194] UE User Equipment
[0195] UL Uplink
[0196] UL CL Uplink Classifier
[0197] UPF User Plane Function
[0198] UPSI UE Policy Part Identifier
[0199] URLLC Ultra-Reliable Low Latency Communications
[0200] URRP-AMF UE reachability request parameters of AMF
[0201] URSP UE routing strategy
[0202] VID VLAN identifier
[0203] VLAN Virtual Local Area Network
[0204] VPLMN Visited Public Land Mobile Network
[0205] W-5GAN Wired 5G Access Network
[0206] W-5GBAN Wired BBF Access Network
[0207] W-5GCAN Wired 5G Cable Access Network
[0208] W-AGF Wired Access Gateway Function
[0209] <Definition>
[0210] For the purpose of this document, the terms and definitions given in Non-Patent Document 1 and below apply. The terms defined in this document take precedence over the definitions of the same terms in Non-Patent Document 1, if any.
[0211] <Overall>
[0212] Those skilled in the art will appreciate that the elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. Furthermore, one or more components of a device may have been represented in the drawings by conventional symbols with respect to the construction of the device, and the drawings may show only those specific details relevant to understanding aspects of the present disclosure so as not to obscure the drawings with details that would be readily apparent to those skilled in the art having the benefit of the description herein.
[0213] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the aspects illustrated in the accompanying drawings, and specific language will be used to describe these aspects. However, it will be understood that this is not intended to limit the scope of the present disclosure. Such changes and further modifications in the illustrated system and such further applications of the principles of the present disclosure that would normally occur to one skilled in the art will be construed as being within the scope of the present disclosure.
[0214] The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion such that a process or method that comprises a series of steps does not comprise only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by "comprises ... a" do not exclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components without more constraints. The phrases "in an aspect," "in another aspect," and similar language that appear throughout this specification may, but do not necessarily, all refer to the same aspect.
[0215] Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs.The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.
[0216] In the following specification and claims, reference will be made to a number of terms which may be defined to have the following meanings: The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.
[0217] As used herein, information is associated with data and knowledge because data is meaningful information and represents values attributed to parameters. Further knowledge means understanding of abstract or concrete concepts. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of the present disclosure. In addition to or in place of the system, other devices, systems, and configurations may be used to implement the aspects disclosed herein, and all such aspects are considered to be within the scope of the present disclosure.
[0218] The various aspects described below and the elements included in the various aspects can be implemented independently or in combination with each other. These aspects include novel features that are different from each other. Therefore, these aspects help to achieve the purpose or solve different problems from each other, and help to obtain different advantages from each other.
[0219] An exemplary object of the present disclosure is to provide a method and an apparatus that can solve the above problems.
[0220] A method of a user equipment (UE) according to an example aspect of the present disclosure includes: receiving a message including pending network slice selection assistance information (NSSAI). The pending NSSAI includes first single network slice selection assistance information (S-NSSAI). The method includes: in a case where a registration procedure using a second S-NSSAI is triggered, checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group (NSSRG) value. The method includes: in a case where the first S-NSSAI and the second S-NSSAI are associated with at least one common NSSRG value, sending a registration request message including the second S-NSSAI.
[0221] A method of a communication device according to an example aspect of the present disclosure includes sending a first message including pending network slice selection assistance information (NSSAI). The pending NSSAI includes first single network slice selection assistance information (S-NSSAI). The method includes receiving a registration request message including a requested NSSAI. The requested NSSAI includes a second S-NSSAI. The method includes checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group (NSSRG) value. The method includes sending a second message including a configured NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with at least one common NSSRG value.
[0222] A user equipment (UE) according to an example aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a message including pending network slice selection assistance information (NSSAI). The pending NSSAI includes a first single network slice selection assistance information (S-NSSAI). The at least one hardware processor is configured to check whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group (NSSRG) value when a registration process using the second S-NSSAI is triggered. The at least one hardware processor is configured to send a registration request message including the second S-NSSAI when the first S-NSSAI and the second S-NSSAI are associated with at least one common NSSRG value.
[0223] A communication device according to an example aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to send a first message including pending network slice selection assistance information (NSSAI). The pending NSSAI includes a first single network slice selection assistance information (S-NSSAI). The at least one hardware processor is configured to receive a registration request message including a requested NSSAI. The requested NSSAI includes a second S-NSSAI. The at least one hardware processor is configured to check 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 second message including the configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with at least one common NSSRG value.
[0224] <First aspect>
[0225] NSSRG (Network Slice Simultaneous Registration Group) was introduced to 5GS in Release 17. The NSSRG feature provides a mechanism to (one or more) 3GPP operators to limit the combination of network slices to be registered to an end user simultaneously. According to the current (one or more) 3GPP specifications, NSSRG information (e.g., information indicating or information related to the NSSRG) is provided from the 5GC to the UE, and the UE selects (one or more) network slices based on the NSSRG information. However, it is unclear in the (one or more) 3GPP specifications what the 5GC should do if the UE retains (one or more) old configured network slices (e.g., old configured NSSAI) and / or old NSSRG information. In this case, the NSSRG feature does not work properly.
[0226] For example, this aspect focuses on a problem in a case where the AMF 70 detects, based on the NSSRG information, that (one or more) S-NSSAIs in the requested NSSAIs in the registration request message from the UE 3 include (one or more) S-NSSAIs that are incompatible with (one or more) S-NSSAIs in the suspended NSSAIs in the AMF 70. For example, this aspect provides a solution to the problem.
[0227] For example, since (one or more than one) S-NSSAI in the requested NSSAI and (one or more than one) S-NSSAI in the pending NSSAI cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of the configured NSSAI and NSSRG information in the UE 3 is not the latest information. For example, the AMF 70 detects that at least one of the configured NSSAI and NSSRG information in the UE 3 is expired. In this case, the AMF 70 provides at least one of the configured NSSAI and NSSRG information to the UE 3 to refresh the data in the UE 3.
[0228] For example, this aspect also discloses a method for handling a registration process in a case where the (one or more) S-NSSAI of the requested NSSAI in the registration request message and the (one or more) S-NSSAI in the pending NSSAI do not belong to or share any common NSSRG value.
[0229] For example, this aspect also discloses a method for handling a registration process when (one or more) S-NSSAIs of a requested NSSAI in a registration request message and (one or more) S-NSSAIs in a pending NSSAI belong to or share at least one common NSSRG value.
[0230] <First Example of the First Aspect:>
[0231] A first example of the first aspect discloses a method in which the UE 3 checks whether the S-NSSAI(s) in the pending NSSAI and the requested NSSAI in the registration request message belong to or share at least one common NSSRG value.
[0232] The following references Figure 1 The detailed processing of the first example of the first aspect is explained.
[0233] 1) UE 3 is configured to support the NSSRG procedure. UE 3 initiates a registration procedure to register S-NSSAI 1 and S-NSSAI 2 by sending a Registration Request message with the requested NSSAI set to S-NSSAI 1 and S-NSSAI 2. The requested NSSAI may include one or more than one S-NSSAI. For example, S-NSSAI 1 is subject to the NSSAA procedure.
[0234] 2) When AMF 70 receives a registration request message including S-NSSAI 1 and S-NSSAI 2 in the requested NSSAI, AMF 70 identifies that S-NSSAI 1 is subject to the NSSAA procedure. For example, AMF 70 may identify that S-NSSAI 1 is subject to the NSSAA procedure based on a local configuration in AMF 70 or a policy of an operator or information received from other network nodes. AMF 70 marks S-NSSAI 1 as a suspended NSSAI, AMF 70 determines that S-NSSAI 2 is allowed for UE 3, and AMF 70 sends a registration accept message including S-NSSAI 1 in the suspended NSSAI and S-NSSAI 2 in the allowed NSSAI. The registration accept message may also include at least one of the configured NSSAI and NSSRG information. The NSSRG information may be information indicating the NSSRG or information related to the NSSRG. For example, UE 3 may understand which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG based on NSSRG information. For example, UE 3 may understand which network slice(s) (e.g., (one or more than one) S-NSSAI) share an NSSRG value or NSSRG based on NSSRG information. For example, UE 3 may understand which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG based on NSSRG information. NSSRG information may be referred to as NSSRG.
[0235] AMF 70 may know that UE 3 has a suspended NSSAI including S-NSSAI 1.
[0236] 3) Upon receiving the registration accept message, UE 3 stores the suspended NSSAI and the allowed NSSAI. In the case where the registration accept message includes at least one of the configured NSSAI and NSSRG information, UE 3 stores at least one of the configured NSSAI and NSSRG information. UE 3 sends a registration complete message. For example, in the case where UE 3 receives the registration accept message, UE 3 may send a registration complete message.
[0237] 4a) At step 4a, UE 3 has S-NSSAI 1 in the pending NSSAI. For example, UE 3 may have a pending NSSAI including S-NSSAI 1. Also, for example, UE 3 may have an allowed NSSAI including S-NSSAI 2.
[0238] 4b) At step 4b, the AMF 70 has S-NSSAI 1 in the pending NSSAI. For example, the AMF 70 may have a pending NSSAI including S-NSSAI 1.
[0239] 5) As defined in non-patent document 3, AMF 70 initiates the NSSAA procedure for S-NSSAI 1.
[0240] 6) UE 3 obtains a trigger for registering S-NSSAI 2. UE 3 checks the NSSRG information to determine whether S-NSSAI 1 and S-NSSAI 2 in the suspended NSSAI in UE 3 share at least one common NSSRG value (for example, UE 3 checks whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG based on the NSSRG information, or UE 3 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG value based on the NSSRG information, or UE 3 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG based on the NSSRG information). UE 3 keeps S-NSSAI 1 in the suspended NSSAI during the NSSAA procedure. Steps 6 to 8 may be performed during the NSSAA procedure for S-NSSAI 1. Checking whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value may be referred to as checking whether S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value.
[0241] 7) If S-NSSAI 1 and S-NSSAI 2 in the suspended NSSAI in UE 3 belong to at least one common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value), UE 3 initiates the registration procedure by sending a registration request message including a requested NSSAI with S-NSSAI 2 set. UE 3 may initiate the registration procedure by sending a registration request message including a requested NSSAI with S-NSSAI 1 and S-NSSAI 2 set.
[0242] For example, in a case where S-NSSAI 1 is associated with NSSRG 1 (or NSSRG value 1) and S-NSSAI 2 is associated with NSSRG 1 (or NSSRG value 1), UE 3 determines that S-NSSAI 1 and S-NSSAI 2 belong to a common NSSRG (or a common NSSRG value) or share a common NSSRG (or a common NSSRG value) or are associated with a common NSSRG (or a common NSSRG value), and initiates a registration procedure by sending a registration request message including a requested NSSAI, wherein the requested NSSAI includes S-NSSAI 2.
[0243] If S-NSSAI 1 and S-NSSAI 2 in the suspended NSSAI in UE 3 do not belong to a common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 do not share a common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 do not share a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value), UE 3 has several options to take.
[0244] For example, in a case where S-NSSAI 1 is associated with NSSRG 1 (or NSSRG value 1) and S-NSSAI 2 is associated with NSSRG 2 (or NSSRG value 2), UE 3 determines that S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG (or a common NSSRG value) or do not share a common NSSRG (or a common NSSRG value) or are not associated with a common NSSRG (or a common NSSRG value), and may perform one of the following options.
[0245] See below for the options UE 3 takes:
[0246] - Since S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG value, UE 3 does not initiate a registration procedure (eg, UE 3 does not send a Registration Request message including a requested NSSAI with S-NSSAI 2 set).
[0247] -UE 3 initiates the registration procedure by sending a registration request message including a requested NSSAI set with another S-NSSAI that belongs to a common NSSRG value with S-NSSAI 1. For example, UE 3 may initiate the registration procedure by sending a registration request message including a requested NSSAI set with S-NSSAI 3 that is different from S-NSSAI 2 and belongs to (or shares) a common NSSRG value with S-NSSAI 1. UE 3 may select the other S-NSSAI from the configured NSSAIs based on the NSSRG information.
[0248] -UE 3 aborts the NSSAA procedure for S-NSSAI 1, and UE 3, after aborting the completion of the NSSAA procedure for S-NSSAI 1, initiates the registration procedure by sending a Registration Request message including a requested NSSAI set with S-NSSAI 2. For example, UE 3, after aborting the completion of the NSSAA procedure for S-NSSAI 1, may initiate the registration procedure by sending a Registration Request message including a requested NSSAI set with S-NSSAI 2. For example, UE 3, after aborting the completion of the NSSAA procedure for S-NSSAI 1, may delete S-NSSAI 1 from the pending NSSAIs and set S-NSSAI 1 to the rejected NSSAI.
[0249] -UE 3 waits for the completion of the NSSAA procedure for S-NSSAI 1. After the completion of the NSSAA procedure for S-NSSAI 1, UE 3 initiates the registration procedure by sending a registration request message including the requested NSSAI with S-NSSAI 2 set. That is, S-NSSAI 1 is not included to the requested NSSAI. This means that UE 3 deletes S-NSSAI 1 from the allowed NSSAIs in UE 3. Alternatively, UE 3 deletes S-NSSAI 1 from the allowed NSSAIs in UE 3 after the completion of the NSSAA procedure for S-NSSAI 1. For example, in the case that UE 3 receives an allowed NSSAI including S-NSSAI 1 after the completion of the NSSAA procedure for S-NSSAI 1, UE 3 may discard the allowed NSSAI or delete S-NSSAI 1 from the allowed NSSAI or set S-NSSAI 1 to the rejected NSSAI.
[0250] 8) The registration process continues from step 4 in Section 4.2.2.2.2 of Non-Patent Document 3.
[0251] In the case where UE 3 initiates the registration procedure by sending a registration request message including a requested NSSAI in which S-NSSAI 2 is set in step 7, the registration procedure may continue from step 4 in section 4.2.2.2.2 of non-patent document 3.
[0252] In the case where UE 3 initiates the registration process by sending a registration request message including a requested NSSAI set with another S-NSSAI (the other S-NSSAI belonging to a common NSSRG value with S-NSSAI 1) in step 7, the registration process can continue from step 4 in Section 4.2.2.2.2 of non-patent document 3.
[0253] In the case where UE 3 initiates the registration process by sending a registration request message including a requested NSSAI in which S-NSSAI 2 is set after aborting completion of the NSSAA process for S-NSSAI 1 in step 7, the registration process can continue from step 4 in Section 4.2.2.2.2 of non-patent document 3.
[0254] In the case where UE 3 initiates the registration procedure by sending a registration request message including a requested NSSAI with S-NSSAI 2 set after completion of the NSSAA procedure for S-NSSAI 1 in step 7, the registration procedure may continue from step 4 in Section 4.2.2.2.2 of non-patent document 3.
[0255] For example, in the case where S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value, UE 3 may detect or determine that at least one of the configured NSSAI and NSSRG information in UE 3 is not the latest information. In this case, UE 3 may request at least one of the latest configured NSSAI and the latest NSSRG information from 5GC, and receive at least one of the latest configured NSSAI and the latest NSSRG information.
[0256] According to a first example of the first aspect, for example, a solution may be provided for an ambiguous description of how to handle NSSRG in (one or more than one) 3GPP specifications.
[0257] According to a first example of the first aspect, for example, a method for handling a registration process may be provided in which (one or more) S-NSSAIs of a requested NSSAI in a registration request message and (one or more) S-NSSAIs in a pending NSSAI do not belong to or share any common NSSRG value.
[0258] According to a first example of the first aspect, for example, a method for handling a registration process may be provided when (one or more) S-NSSAIs of a requested NSSAI in a registration request message and (one or more) S-NSSAIs in a suspended NSSAI belong to or share at least one common NSSRG value.
[0259] <Variation 1 of the First Example of the First Aspect:>
[0260] In one example, in step 1, UE 3 sends only S-NSSAI 1 in the registration request message. In this case, UE 3 and AMF 70 have S-NSSAI 1 in the suspended NSSAI. In step 6, UE 3 receives a trigger to register to S-NSSAI 2, and the processing in step 6 may be performed. For example, UE 3 may select (one or more than one) S-NSSAI from the configured NSSAIs, and include the selected (one or more than one) S-NSSAI in the requested NSSAI in the registration request message. For example, a subset of the configured NSSAI may be provided in the requested NSSAI. For example, the subset of the configured NSSAI may be the requested NSSAI. Variation 1 of the first example of the first aspect may be applied to the second example of the first aspect below. For example, in the case where UE 3 has a suspended NSSAI, the subset of the configured NSSAI provided in the requested NSSAI and the suspended NSSAI may be associated with at least one common NSSRG value.
[0261] For example, in the case where UE 3 (e.g., in step 6) initiates a registration procedure, UE 3 may determine or check whether UE 3 has a pending NSSAI. In the case where UE 3 determines or checks that UE 3 has a pending NSSAI and UE 3 initiates a registration procedure using a requested NSSAI (e.g., UE 3 initiates a registration procedure by sending a registration request message including the requested NSSAI), UE 3 may determine or check whether a subset of the configured NSSAI provided in the requested NSSAI and the pending NSSAI are associated with at least one common NSSRG value.
[0262] In the event that UE 3 (e.g., in step 6) determines or detects that the subset of configured NSSAI provided in the requested NSSAI and the pending NSSAI are associated with at least one common NSSRG value, UE 3 may proceed with the registration procedure using the requested NSSAI (e.g., UE 3 may send a registration request message including the requested NSSAI. This process may be performed in step 7). The following process (or subsequent process) may be performed in conjunction with Figure 1 Same as step 8.
[0263] <Second Example of the First Aspect:>
[0264] A second example of the first aspect discloses a method in which AMF 70 checks whether (one or more) S-NSSAIs in a pending NSSAI and (one or more) S-NSSAIs in a requested NSSAI in a registration request message share at least one common NSSRG value. In the event that (one or more) S-NSSAIs in a pending NSSAI and (one or more) S-NSSAIs in a requested NSSAI do not share any common NSSRG value, then AMF 70 provides the configured NSSAI and NSSRG to UE 3 to refresh the configuration data in UE 3.
[0265] The following references Figure 2 The detailed processing of the second example of the first aspect will be described.
[0266] 1) UE 3 is configured to support the NSSRG procedure. UE 3 initiates a registration procedure to register S-NSSAI 1 and S-NSSAI 2 by sending a Registration Request message with the requested NSSAI set to S-NSSAI 1 and S-NSSAI 2. The requested NSSAI may include one or more than one S-NSSAI. For example, S-NSSAI 1 is subject to the NSSAA procedure.
[0267] 2) When AMF 70 receives a registration request message including S-NSSAI 1 and S-NSSAI 2 in the requested NSSAI, AMF 70 identifies that S-NSSAI 1 is subject to the NSSAA procedure. For example, AMF 70 may identify that S-NSSAI 1 is subject to the NSSAA procedure based on a local configuration in AMF 70 or a policy of an operator or information received from other network nodes. AMF 70 marks S-NSSAI 1 as a suspended NSSAI, AMF 70 determines that S-NSSAI 2 is allowed for UE 3, and AMF 70 sends a registration accept message including S-NSSAI 1 in the suspended NSSAI and S-NSSAI 2 in the allowed NSSAI. The registration accept message may also include at least one of the configured NSSAI and NSSRG information. The NSSRG information may be information indicating the NSSRG or information related to the NSSRG. For example, UE 3 may understand which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG based on the NSSRG information. For example, UE 3 may understand which network slice(s) (e.g., (one or more than one) S-NSSAI) share the NSSRG value or NSSRG based on the NSSRG information. For example, UE 3 may understand which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG based on the NSSRG information.
[0268] The AMF 70 may store the NSSRG information. For example, the AMF 70 may understand which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG based on the NSSRG information. For example, the AMF 70 may understand which network slice(s) (e.g., (one or more than one) S-NSSAI) share the NSSRG value or NSSRG based on the NSSRG information. For example, the AMF 70 may understand which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG based on the NSSRG information.
[0269] AMF 70 may pre-store NSSRG information, or may receive NSSRG information from other network nodes, or may create NSSRG information based on local configuration in AMF 70 or an operator's policy or information received from other network nodes.
[0270] AMF 70 may know that UE 3 has a suspended NSSAI including S-NSSAI 1.
[0271] 3) Upon receiving the registration accept message, UE 3 stores the suspended NSSAI and the allowed NSSAI. In the case where the registration accept message includes at least one of the configured NSSAI and NSSRG information, UE 3 stores at least one of the configured NSSAI and NSSRG information. UE 3 sends a registration complete message. For example, in the case where UE 3 receives the registration accept message, UE 3 may send a registration complete message.
[0272] 4a) At step 4a, UE 3 has S-NSSAI 1 in the pending NSSAI. For example, UE 3 may have a pending NSSAI including S-NSSAI 1. Also, for example, UE 3 may have an allowed NSSAI including S-NSSAI 2.
[0273] 4b) At step 4b, the AMF 70 stores S-NSSAI 1 in the pending NSSAI. For example, the AMF 70 may have a pending NSSAI including S-NSSAI 1.
[0274] 5) As defined in non-patent document 3, AMF 70 initiates the NSSAA procedure for S-NSSAI 1.
[0275] 6) UE 3 obtains a trigger to register S-NSSAI 2. UE 3 initiates the registration procedure by sending a Registration Request message including the requested NSSAI set to S-NSSAI 2.
[0276] UE 3 maintains S-NSSAI 1 in the suspended NSSAI during the NSSAA procedure. Steps 6 to 9 may be performed during the NSSAA procedure for S-NSSAI 1.
[0277] 7) Upon receiving the registration request message from UE 3, AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG value (for example, AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG based on the NSSRG information, or AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG value based on the NSSRG information, or AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG based on the NSSRG information, or AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value based on the NSSRG information). Checking whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG value may be referred to as checking whether S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value.
[0278] Depending on the result of the check in step 7, one of steps 8a, 8b, 8c and 8d occurs.
[0279] 8a) If S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value), and S-NSSAI 2 is allowed for UE 3, then AMF 70 sends a registration accept message to UE 3, the registration accept message including at least one of NSSRG information, S-NSSAI 2 set to the allowed NSSAI, and S-NSSAI 1 set to the suspended NSSAI. The registration accept message may also include the configured NSSAI. For example, AMF 70 may send a registration accept message including NSSRG information, allowed NSSAI (the allowed NSSAI including S-NSSAI 2), and suspended NSSAI (the suspended NSSAI including S-NSSAI 1) to UE 3.
[0280] UE 3 may store the allowed NSSAI and the suspended NSSAI. For example, UE 3 may refresh or update data in UE 3 (eg, the configured NSSAI and NSSRG information previously stored in UE 3) using at least one of the received configured NSSAI and the received NSSRG information.
[0281] 8b) If S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 do not share a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value), and S-NSSAI 2 is allowed for UE 3, and AMF 70 decides that S-NSSAI 2 has higher priority than S-NSSAI 1 for UE 3, then AMF 70 sends a Registration Accept message to UE 3, the Registration Accept message including the configured NSSAI, the NSSRG information, the S-NSSAI 2 set to the allowed NSSAI, and the S-NSSAI set to the rejected NSSAI. 1. For example, AMF 70 may send a registration acceptance message including a configured NSSAI, NSSRG information, an allowed NSSAI (the allowed NSSAI includes S-NSSAI 2), and a rejected NSSAI (the rejected NSSAI includes S-NSSAI 1) to UE 3. For example, AMF 70 may store information related to the priority of (one or more) S-NSSAI, or may receive the information from other network nodes, and AMF 70 may decide the priority of (one or more) S-NSSAI based on the information. For example, AMF 70 may decide the priority of (one or more) S-NSSAI based on the local configuration of AMF 70 or the policy of the operator.
[0282] Upon receiving the registration accept message including S-NSSAI 1 in the rejected NSSAI from AMF 70, since S-NSSAI 1 is in the suspended NSSAI stored in UE 3, UE 3 removes S-NSSAI 1 from the suspended NSSAI and stores S-NSSAI 1 to the rejected NSSAI. In addition, UE 3 may initiate an abort process for the ongoing NSSAA procedure for S-NSSAI 1. UE 3 may store S-NSSAI 2 in the allowed NSSAI. For example, UE 3 may refresh or update data in UE 3 (e.g., the configured NSSAI and NSSRG information previously stored in UE 3) using at least one of the received configured NSSAI and the received NSSRG information.
[0283] For example, UE 3 may maintain the ongoing NSSAA procedure for S-NSSAI 1. In this case, if UE 3 receives an Allowed NSSAI including S-NSSAI 1 after completion of the NSSAA procedure for S-NSSAI 1, UE 3 may not update the Allowed NSSAI in UE 3 based on the received Allowed NSSAI including S-NSSAI 1. In this case, UE 3 may discard the received Allowed NSSAI and maintain S-NSSAI 1 in the Rejected NSSAI.
[0284] 8c) If S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 do not share a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value), and S-NSSAI 2 is allowed for UE 3, and AMF 70 decides that S-NSSAI 1 has higher priority than S-NSSAI 2 for UE 3, then AMF 70 sends a Registration Accept message to UE 3, the Registration Accept message including the configured NSSAI, the NSSRG information, the S-NSSAI 2 set to the Rejected NSSAI, and the S-NSSAI set to the Suspended NSSAI. 1. For example, AMF 70 may send a registration accept message including a configured NSSAI, NSSRG information, a rejected NSSAI (the rejected NSSAI includes S-NSSAI 2), and a suspended NSSAI (the suspended NSSAI includes S-NSSAI 1) to UE 3.
[0285] Upon receiving the Registration Accept message including S-NSSAI 2 in the Rejected NSSAI from the AMF 70, since S-NSSAI 2 is in the Allowed NSSAI stored in the UE 3, the UE 3 removes S-NSSAI 2 from the Allowed NSSAI and stores S-NSSAI 2 in the Rejected NSSAI. The UE 3 may store S-NSSAI 1 in the Suspended NSSAI. For example, the UE 3 may refresh or update data in the UE 3 (e.g., the Configured NSSAI and NSSRG information previously stored in the UE 3) using at least one of the received Configured NSSAI and the received NSSRG information.
[0286] 8d) If S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value (for example, if S-NSSAI 1 and S-NSSAI 2 do not share a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG value, or if S-NSSAI 1 and S-NSSAI 2 do not belong to a common NSSRG, or if S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value), the AMF 70 sends a registration reject message to the UE 3, which registration reject message includes the configured NSSAI, the NSSRG information, and at least one of S-NSSAI 1 and S-NSSAI 2 set to the rejected NSSAI. For example, AMF 70 may send a registration reject message including the configured NSSAI, NSSRG information, and rejected NSSAI (the rejected NSSAI includes S-NSSAI 1 and S-NSSAI 2) to UE 3.
[0287] Upon receiving the registration reject message including S-NSSAI 1 and S-NSSAI 2 in the rejected NSSAI from AMF 70, since S-NSSAI 1 is in the suspended NSSAI in UE 3 and S-NSSAI 2 is in the allowed NSSAI in UE 3, UE 3 removes S-NSSAI 1 from the suspended NSSAI, removes S-NSSAI 2 from the allowed NSSAI, and stores S-NSSAI 1 and S-NSSAI 2 to the rejected NSSAI. In addition, UE 3 initiates an abort process for the ongoing NSSAA procedure for S-NSSAI 1. For example, UE 3 may refresh or update data in UE 3 (e.g., the configured NSSAI and NSSRG information previously stored in UE 3) using at least one of the received configured NSSAI and the received NSSRG information.
[0288] For example, UE 3 may maintain the ongoing NSSAA procedure for S-NSSAI 1. In this case, if UE 3 receives an Allowed NSSAI including S-NSSAI 1 after completion of the NSSAA procedure for S-NSSAI 1, UE 3 may not update the Allowed NSSAI in UE 3 based on the received Allowed NSSAI including S-NSSAI 1. In this case, UE 3 may discard the received Allowed NSSAI and maintain S-NSSAI 1 in the Rejected NSSAI.
[0289] 9) If a registration accept message is sent from AMF 70 to UE 3 in step 8, UE 3 may send a registration complete message to AMF 70 to complete the registration process.
[0290] For example, in the case where the AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG value, the AMF 70 may detect or determine that at least one of the configured NSSAI and NSSRG information in the UE 3 is not the latest information. In this case, the AMF 70 may send a registration accept message or a registration reject message as described in steps 8b, 8c or 8d.
[0291] The configured NSSAI sent in step 8a, 8b, 8c or 8d may be the same as the configured NSSAI sent in step 2.
[0292] The configured NSSAI sent in step 8a, 8b, 8c or 8d may be different from the configured NSSAI sent in step 2. In this case, the AMF 70 may create a new configured NSSAI or update the configured NSSAI sent in step 2 based on the local configuration in the AMF 70 or the operator's policy or information received from other network nodes, and may send the new configured NSSAI or the updated configured NSSAI in steps 8a, 8b, 8c or 8d. The AMF 70 may request the new configured NSSAI or the updated configured NSSAI from other network nodes, and may receive the new configured NSSAI or the updated configured NSSAI from other network nodes. Then, the AMF 70 may send the new configured NSSAI or the updated configured NSSAI in steps 8a, 8b, 8c or 8d.
[0293] The NSSRG information sent in step 8a, 8b, 8c or 8d may be the same as the NSSRG information sent in step 2.
[0294] The NSSRG information sent in step 8a, 8b, 8c or 8d may be different from the NSSRG information sent in step 2. In this case, the AMF 70 may create new NSSRG information or update the NSSRG information sent in step 2 based on the local configuration in the AMF 70 or the operator's policy or information received from other network nodes, and may send the new NSSRG information or the updated NSSRG information in step 8a, 8b, 8c or 8d.
[0295] AMF 70 may request new NSSRG information or updated NSSRG information from other network nodes, and may receive new NSSRG information or updated NSSRG information from other network nodes. Then, AMF 70 may send new NSSRG information or updated NSSRG information in steps 8a, 8b, 8c or 8d.
[0296] For example, in the case where UE 3 has a pending NSSAI, and S-NSSAI 2 of the requested NSSAI in the registration request message and the pending NSSAI (e.g., S-NSSAI 1 in the pending NSSAI) are not associated with any common NSSRG value, AMF 70 may send a new configured NSSAI by using a registration reject message or a registration accept message (or AMF 70 may include the new configured NSSAI in a registration reject message or a registration accept message).
[0297] For example, in a case where the AMF 70 has a pending NSSAI, and the S-NSSAI2 of the requested NSSAI in the Registration Request message and the pending NSSAI (e.g., S-NSSAI 1 in the pending NSSAI) are not associated with any common NSSRG value, the AMF 70 may send a new configured NSSAI by using a Registration Reject message or a Registration Accept message (or the AMF 70 may include the new configured NSSAI in a Registration Reject message or a Registration Accept message).
[0298] According to a second example of the first aspect, for example, a solution may be provided for an ambiguous description of how to handle NSSRG in (one or more than one) 3GPP specifications.
[0299] According to a second example of the first aspect, for example, a method for handling a registration process may be provided in which (one or more) S-NSSAIs of a requested NSSAI in a registration request message and (one or more) S-NSSAIs in a pending NSSAI do not belong to or share any common NSSRG value.
[0300] According to a second example of the first aspect, for example, a method for handling a registration process may be provided when (one or more) S-NSSAIs of a requested NSSAI in a registration request message and (one or more) S-NSSAIs in a suspended NSSAI belong to or share at least one common NSSRG value.
[0301] For example, in the case where S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value, there is a possibility that at least one of the configured NSSAI and NSSRG information stored in UE 3 is not the latest information. By checking whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value, AMF 70 can detect or determine whether at least one of the configured NSSAI and NSSRG information in UE 3 may not be the latest information (or may be old information). In the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value (for example, AMF 70 detects or determines that at least one of the configured NSSAI and NSSRG information in UE 3 may not be the latest information), AMF 70 sends at least one of the configured NSSAI and NSSRG information to refresh or update at least one of the configured NSSAI and NSSRG information stored in UE 3. According to a second example of the first aspect, for example, when S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value and the NSSRG feature can work normally, the latest information for performing the NSSRG feature (for example, configured NSSAI and NSSRG information) is provided from AMF 70 to UE 3.
[0302] <Variation 1 of the Second Example of the First Aspect>
[0303] In steps 8b and 8d, the AMF 70 may initiate an AMF triggered slice specific authorization revocation procedure. The AMF triggered slice specific authorization revocation procedure may be one of the following outlined procedures:
[0304] -AMF 70 sends an AAA protocol Revoke Authorization Request message including S-NSSAI 1 and GPSI to NSSAAF 76 for UE 3 to request the revocation of authorization of S-NSSAI 1.
[0305] -AMF 70 sends a message including S-NSSAI 1 and GPSI to the AAA server for S-NSSAI 1, for UE3 to request revocation of authorization of S-NSSAI 1.
[0306] <Variation 2 of the Second Example of the First Aspect>
[0307] For example, the AMF 70 may know the content of the configured NSSAI for the UE 3 or know that the UE 3 has the configured NSSAI. For example, in the case where the AMF 70 (for example, in step 6) receives a registration request message including the requested NSSAI from the UE 3, the AMF 70 (for example, in step 7) may determine or check whether the subset of the configured NSSAI provided in the requested NSSAI and the suspended NSSAI (for example, the suspended NSSAI for the UE 3) are associated with at least one common NSSRG value. Based on the determination or check, the AMF 70 may perform one of steps 8a to 8d. For example, in the case where the AMF 70 determines that the subset of the configured NSSAI provided in the requested NSSAI and the suspended NSSAI are associated with at least one common NSSRG value, the AMF 70 may perform the processing in step 8a (for example, the AMF 70 may send a registration accept message in step 8a). For example, in the event that AMF 70 determines that a subset of the configured NSSAI provided in the requested NSSAI and the pending NSSAI are not associated with at least one common NSSRG value, AMF 70 may proceed with one of steps 8b to 8d (e.g., AMF 70 may send a Registration Accept message in step 8b, or AMF 70 may send a Registration Accept message in step 8c, or AMF 70 may send a Registration Reject message in step 8d).
[0308] <Second Aspect>
[0309] NSSRG (Network Slice Simultaneous Registration Group) was introduced to 5GS in Release 17. The NSSRG feature provides a mechanism to (one or more) 3GPP operators to limit the combination of network slices to be registered to an end user simultaneously. According to the current (one or more) 3GPP specifications, NSSRG information (e.g., information indicating or information related to the NSSRG) is provided from the 5GC to the UE, and the UE selects (one or more) network slices based on the NSSRG information. However, it is unclear in the (one or more) 3GPP specifications what the 5GC should do if the UE retains (one or more) old configured network slices (e.g., old configured NSSAI) and / or old NSSRG information. In this case, the NSSRG feature does not work properly.
[0310] For example, this aspect focuses on a problem in a case where the AMF 70 detects, based on the NSSRG information, that (one or more) S-NSSAIs in the requested NSSAIs in the registration request message from the UE 3 include (one or more) S-NSSAIs that are incompatible with (one or more) S-NSSAIs in the allowed NSSAIs for another access type in the AMF 70. For example, this aspect provides a solution to the problem.
[0311] For example, since (one or more) S-NSSAIs in the requested NSSAI and (one or more) S-NSSAIs in the allowed NSSAI for another access type cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of the configured NSSAI and NSSRG information in the UE 3 is not the latest information. For example, the AMF 70 detects that at least one of the configured NSSAI and NSSRG information in the UE 3 is expired. In this case, the AMF 70 provides the configured NSSAI information and NSSRG information to the UE 3 to refresh the data in the UE 3.
[0312] For example, this aspect also discloses a method for handling a registration process when (one or more) S-NSSAIs of a requested NSSAI in a registration request message do not belong to or share any common NSSRG value with (one or more) S-NSSAIs of an allowed NSSAI for another access type.
[0313] <First Example of the Second Aspect:>
[0314] A first example of the second aspect discloses a method in which AMF 70 checks whether (one or more) S-NSSAIs in the allowed NSSAIs on one access type and (one or more) requested NSSAIs in a registration request message on another access type share at least one common NSSRG value. In the case where (one or more) S-NSSAIs in the allowed NSSAIs on one access and (one or more) S-NSSAIs in the requested NSSAIs on another access do not share a common NSSRG value, then AMF 70 sends a registration accept message containing the configured NSSAI and NSSRG information to UE 3 to refresh the configuration data in UE 3.
[0315] The following references Figure 3 To illustrate the detailed processing of the first example of the second aspect.
[0316] 1) UE 3 is registered on one access (e.g., 3GPP access 501), and S-NSSAI 1 is in the allowed NSSAI in UE 3. For example, UE 3 has an allowed NSSAI including S-NSSAI 1 for 3GPP access. For example, AMF 70 has an allowed NSSAI including S-NSSAI 1 for 3GPP access. UE 3 is configured to perform a registration procedure on one access (e.g., 3GPP access) and another access (e.g., non-3GPP access 502). For example, UE 3 and AMF 70 may perform a registration procedure using S-NSSAI 1 on 3GPP access, and UE 3 and AMF 70 may have an allowed NSSAI including S-NSSAI 1. AMF 70 may know that UE 3 has an allowed NSSAI including S-NSSAI 1.
[0317] 2) UE 3 obtains a trigger for a registration procedure for S-NSSAI 2 on another access (eg, non-3GPP access 502 or N3GPP access 502).
[0318] 3) UE 3 sends a Registration Request message including S-NSSAI 2 in the Requested NSSAI on non-3GPP access.
[0319] 4) Upon receiving the Registration Request message, AMF 70 checks whether S-NSSAI 1 in the allowed NSSAI on the 3GPP access and S-NSSAI 2 in the requested NSSAI in the Registration Request message belong to at least one common NSSRG value (for example, AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG based on the NSSRG information, or AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value based on the NSSRG information, or UE 3 checks whether S-NSSAI 1 and S-NSSAI 2 belong to at least one common NSSRG based on the NSSRG information, or AMF 70 checks whether S-NSSAI 1 and S-NSSAI 2 are associated with at least one common NSSRG value based on the NSSRG information).
[0320] AMF 70 may pre-store NSSRG information, or may receive NSSRG information from other network nodes, or may create NSSRG information based on local configuration in AMF 70 or an operator's policy or information received from other network nodes.
[0321] For example, the AMF 70 may understand which network slice (e.g., S-NSSAI) belongs to which NSSRG value or NSSRG based on the NSSRG information. For example, the AMF 70 may understand which network slice(s) (e.g., (one or more than one) S-NSSAI) share the NSSRG value or NSSRG based on the NSSRG information. For example, the AMF 70 may understand which network slice (e.g., S-NSSAI) is associated with which NSSRG value or NSSRG based on the NSSRG information.
[0322] Depending on the results of the inspection, there are two options to take.
[0323] Option 1:
[0324] This is an option for the AMF 70 to reject the Registration Request message due to the absence of a common NSSRG value between S-NSSAI 1 in the requested NSSAI and S-NSSAI 2 in the allowed NSSAI on the 3GPP access.
[0325] 5a) AMF 70 sends a registration reject message to UE 3, the registration reject message including at least one of the configured NSSAI, NSSRG information, and S-NSSAI 2 set to the rejected NSSAI. For example, in the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 do not belong to or share a common NSSRG or a common NSSRG value (or in the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG or any common NSSRG value), AMF 70 may send a registration reject message including the configured NSSAI, NSSRG information, and the rejected NSSAI (the rejected NSSAI including S-NSSAI 2).
[0326] Upon receiving the registration reject message, UE 3 stores at least one of the configured NSSAI, NSSRG information, and S-NSSAI 2 set to the rejected NSSAI. For example, UE 3 may refresh or update data in UE 3 (e.g., the configured NSSAI and NSSRG information previously stored in UE 3) using at least one of the received configured NSSAI and the received NSSRG information.
[0327] Option 2:
[0328] This is an option for AMF 70 to accept the Registration Request with S-NSSAI 2. When S-NSSAI 2 is accepted, since there is no common NSSRG value between S-NSSAI 1 and S-NSSAI 2, AMF 70 updates S-NSSAI 1 to reject on non-3GPP access.
[0329] 5b) AMF 70 sends a Registration Accept message to UE 3, the Registration Accept message including the configured NSSAI, NSSRG information and S-NSSAI 2 set to the allowed NSSAI. For example, in the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 do not belong to or share a common NSSRG or a common NSSRG value (or in the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 are not associated with any common NSSRG or any common NSSRG value), AMF 70 may send a Registration Accept message including the configured NSSAI, NSSRG information and the allowed NSSAI (the allowed NSSAI includes S-NSSAI 2). For example, AMF 70 may send the Registration Accept message on a non-3GPP access.
[0330] Upon receiving the registration accept message, UE 3 stores at least one of the configured NSSAI, NSSRG information, and S-NSSAI 2 set to the allowed NSSAI. For example, UE 3 may refresh or update data in UE 3 (e.g., the configured NSSAI and NSSRG information previously stored in UE 3) using at least one of the received configured NSSAI and the received NSSRG information.
[0331] 6b) UE 3 sends a registration complete message to AMF 70. For example, in the case where UE 3 receives a registration accept message from AMF 70, UE 3 may send a registration complete message to AMF 70. For example, UE 3 may send a registration complete message on a non-3GPP access.
[0332] 7b) AMF 70 sends a UE configuration update command message to UE 3 on 3GPP access, the UE configuration update command message including at least one of the configured NSSAI, NSSRG information, and S-NSSAI 1 set to the rejected NSSAI. For example, AMF 70 may send a UE configuration update command message including the configured NSSAI, NSSRG information, and the rejected NSSAI (the rejected NSSAI includes S-NSSAI1). For example, AMF 70 may send the UE configuration update command message after receiving the registration complete message in step 6b. For example, AMF 70 may send the UE configuration update command message after sending the registration accept message in step 5b.
[0333] Upon receiving the UE Configuration Update Command message, UE 3 stores at least one of the configured NSSAI, NSSRG information, and S-NSSAI 1 set to the rejected NSSAI for 3GPP access.
[0334] For example, UE 3 may delete S-NSSAI 1 from allowed NSSAIs for 3GPP access, and store rejected NSSAIs including S-NSSAI 1 for 3GPP access.
[0335] For example, UE 3 may use at least one of the received configured NSSAI and the received NSSRG information to refresh or update data in UE 3 (eg, the configured NSSAI and NSSRG information previously stored in UE 3).
[0336] 8b) UE 3 sends a UE configuration update complete message to AMF 70 on 3GPP access. For example, when UE 3 receives a UE configuration update command message from AMF 70, UE 3 may send a UE configuration update complete message to AMF 70.
[0337] AMF 70 may create a new configured NSSAI or update a configured NSSAI previously sent to UE 3 based on a local configuration in AMF 70 or an operator's policy or information received from other network nodes, and may send the new configured NSSAI or the updated configured NSSAI in steps 5a, 5b or 7b.
[0338] AMF 70 may request a new configured NSSAI or an updated configured NSSAI from other network nodes, and may receive a new configured NSSAI or an updated configured NSSAI from other network nodes. Then, AMF 70 may send a new configured NSSAI or an updated configured NSSAI in steps 5a, 5b, or 7b.
[0339] For example, the configured NSSAI in step 5a or step 5b may be configured for non-3GPP access. For example, the configured NSSAI in step 5b and step 7b may be configured to be common for 3GPP access and non-3GPP access. For example, the configured NSSAI in step 5a and step 7b may be configured to be different between 3GPP access and non-3GPP access. For example, the configured NSSAI in steps 5a and 5b may be used for non-3GPP access, and the configured NSSAI in step 7b may be used for 3GPP access.
[0340] AMF 70 may create new NSSRG information or update NSSRG information previously sent to UE 3 based on local configuration in AMF 70 or the operator's policy or information received from other network nodes, and may send the new NSSRG information or the updated NSSRG information in steps 5a, 5b or 7b.
[0341] AMF 70 may request new NSSRG information or updated NSSRG information from other network nodes, and may receive new NSSRG information or updated NSSRG information from other network nodes. Then, AMF 70 may send new NSSRG information or updated NSSRG information in steps 5a, 5b or 7b.
[0342] For example, the NSSRG information in step 5a or step 5b may be configured for non-3GPP access. For example, the NSSRG information in step 5b and step 7b may be configured to be common for 3GPP access and non-3GPP access. For example, the NSSRG information in step 5a and step 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 used for non-3GPP access, and the NSSRG information in step 7b may be used for 3GPP access.
[0343] For example, in the case where AMF 70 determines in step 4 that S-NSSAI 1 and S-NSSAI 2 belong to a common NSSRG value, AMF 70 may send a registration acceptance message including allowed NSSAIs for non-3GPP access (the allowed NSSAIs including S-NSSAI 2) to UE 3.
[0344] For example, in the case where UE 3 already has an allowed NSSAI for 3GPP access, and S-NSSAI 2 of the requested NSSAI in the registration request message and the allowed NSSAI (e.g., S-NSSAI 1 in the allowed NSSAI) are not associated with any common NSSRG value, AMF 70 may send the new configured NSSAI by using a registration reject message or a registration accept message (or AMF 70 may include the new configured NSSAI in a registration reject message or a registration accept message).
[0345] For example, in a case where AMF 70 already has an allowed NSSAI for 3GPP access, and S-NSSAI 2 of the requested NSSAI in the registration request message and the allowed NSSAI (e.g., S-NSSAI 1 in the allowed NSSAI) are not associated with any common NSSRG value, AMF 70 may send a new configured NSSAI by using a registration reject message or a registration accept message (or AMF 70 may include the new configured NSSAI in a registration reject message or a registration accept message).
[0346] For example, in a case where the AMF 70 already has an allowed NSSAI for 3GPP access, and the S-NSSAI 2 of the requested NSSAI in the registration request message on the non-3GPP access and the allowed NSSAI for 3GPP access (e.g., S-NSSAI 1 in the allowed NSSAI) are not associated with any common NSSRG value, the AMF 70 may send a new configured NSSAI by using a Registration Reject message or a Registration Accept message (or the AMF 70 may include the new configured NSSAI in a Registration Reject message or a Registration Accept message).
[0347] For example, in the case where UE 3 (or AMF 70) already has an allowed NSSAI for other accesses, and the S-NSSAI 2 of the requested NSSAI in the registration request message on the current access and the allowed NSSAI for other accesses (e.g., S-NSSAI 1 in the allowed NSSAI) are not associated with any common NSSRG value, AMF 70 may send a new configured NSSAI by using a Registration Reject message or a Registration Accept message (or AMF 70 may include the new configured NSSAI in a Registration Reject message or a Registration Accept message).
[0348] The registration accept message in step 5b may include information indicating that a UE configuration update command message will be sent. In the case where UE 3 receives this information, UE 3 may not send a registration request message including a requested NSSAI (the requested NSSAI includes S-NSSAI 1) or other NAS messages related to S-NSSAI 1 on 3GPP access until UE 3 receives the UE configuration update command message.
[0349] According to a first example of the second aspect, for example, a solution may be provided for an ambiguous description of how to handle NSSRG in (one or more than one) 3GPP specifications.
[0350] According to a first example of the second aspect, for example, a method for handling a registration process may be provided when (one or more) S-NSSAIs of a requested NSSAI in a registration request message on one access do not belong to or share any common NSSRG value with (one or more) S-NSSAIs of allowed NSSAIs for another access.
[0351] According to a first example of the second aspect, for example, a method for handling a registration process may be provided in which (one or more) S-NSSAIs of a requested NSSAI in a registration request message on one access belong to or share at least one common NSSRG value with (one or more) S-NSSAIs of an allowed NSSAI for another access.
[0352] For example, in the case where S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value, there is a possibility that at least one of the configured NSSAI and NSSRG information stored in UE 3 is not the latest information. By checking whether S-NSSAI 1 and S-NSSAI 2 share at least one common NSSRG value, AMF 70 can detect or determine whether at least one of the configured NSSAI and NSSRG information in UE 3 may not be the latest information (or may be old information). In the case where AMF 70 determines that S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value (for example, AMF 70 detects or determines that at least one of the configured NSSAI and NSSRG information in UE 3 may not be the latest information), AMF 70 sends at least one of the configured NSSAI and NSSRG information to refresh or update at least one of the configured NSSAI and NSSRG information stored in UE 3. According to a first example of the second aspect, for example, when S-NSSAI 1 and S-NSSAI 2 do not share at least one common NSSRG value and the NSSRG feature can work normally, the latest information for performing the NSSRG feature (e.g., configured NSSAI and NSSRG information) is provided from AMF 70 to UE 3.
[0353] <Variation 1 of First Example of Second Aspect>
[0354] Although this example illustrates a situation where UE 3 sends a registration request message to AMF 70 on non-3GPP access and UE 3 has an allowed NSSAI on 3GPP access, the first example of the second aspect is also valid for a situation where UE 3 sends a registration request message to AMF 70 on 3GPP access and UE 3 has an allowed NSSAI on non-3GPP access.
[0355] <Variation 2 of First Example of Second Aspect>
[0356] Steps 7b and 8b may occur before steps 5b and 6b. Step 7b may be performed after step 5b. Step 5b may be performed after step 7b.
[0357] <System Overview>
[0358] Figure 4 There is schematically illustrated a telecommunication system 1 for mobile (cellular or wireless) devices to which the above aspects are applicable.
[0359] The telecommunications system 1 represents an overview of a system in which end-to-end communications are possible. For example, a UE 3 (or user equipment, "mobile device" 3) communicates with other UEs 3 or service servers in a data network 20 via various (R)AN nodes 5 and a core network 7.
[0360] The (R)AN node 5 supports any radio access including 5G radio access technology (RAT), E-UTRA radio access technology, beyond 5G RAT, 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).
[0361] The (R)AN node 5 may be split into a radio unit (RU), a distributed unit (DU), and a centralized unit (CU). In some aspects, each of the units may be connected to each other and construct the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.
[0362] The (R)AN node 5 may be split into a control plane function and a user plane function. In addition, multiple user plane functions may be assigned to support communications. In some aspects, user traffic may be distributed to multiple user plane functions, and user traffic passing through each user plane function may be aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be referred to as "dual connectivity" or "multiple connectivity".
[0363] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support satellite access and terrestrial access.
[0364] Additionally, the (R)AN node 5 may also be referred to as an access node for non-wireless access. Non-wireless access includes fixed line access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Networks (IOWN).
[0365] The core network 7 may include logical nodes (or "functions") for supporting communications in the telecommunications system 1. For example, the core network 7 may be a 5G core network (5GC), which includes control plane functions and user plane functions and other functions. Each function in the logical node may be considered a network function. The network function may be provided to another node by adapting a service-based architecture (SBA).
[0366] Network functions may be deployed as distributed, redundant, stateless and scalable providing services from several locations and several execution instances in each location by adapting network virtualization technologies as defined by European Telecommunications Standards Institute Network Function Virtualization (ETSI NFV).
[0367] The 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).
[0368] As is well known, when the UE 3 is moving around in the geographical area covered by the telecommunication system 1, the UE 3 may enter and leave areas (i.e., radio cells) served by the (R)AN nodes 5. In order to keep track of the UE 3 and facilitate mobility between different (R)AN nodes 5, the core network 7 includes at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 coupled to the core network 7. In some core networks, instead of the AMF 70, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used.
[0369] The core network 7 also includes 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, among others. When the UE 3 is roaming to a visited public land mobile network (VPLMN), the home public land mobile network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functions of the SMF 71, UPF 72, and PCF 73 to the UE 3 roaming away.
[0370] The UE 3 and the corresponding serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Adjacent (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 the like). Each (R)AN node 5 is also connected to a node in the core network 7 (such as a so-called core network node, etc.) via an appropriate interface (such as a so-called (one or more than one) "N2" / "N3" interface and / or the like). A connection to a data network 20 is also provided from the core network 7. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. In the case where the data network 20 is provided by a PLMN operator or a mobile virtual network operator (MVNO), an IP Multimedia Subsystem (IMS) service may be provided by the data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or an unstructured data type.
[0371] The "Uu" interface may include a control plane of the Uu interface and a user plane of the Uu interface.
[0372] The user plane of the Uu interface is responsible for transmitting user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers through a physical connection.
[0373] The control plane of the Uu interface is responsible for establishing, modifying and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC and MAC sublayers through a physical connection.
[0374] For example, the following messages are communicated through the RRC layer to support AS signaling.
[0375] -RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects in the present disclosure, the following parameters may be included together in the RRC Setup Request message.
[0376] --establishmentCause and ue-Identity. ue-Identity can have the value of ng-5G-S-TMSI-Part1 or randomValue.
[0377] -RRC setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the RRC setup message.
[0378] --masterCellGroup and radioBearerConfig
[0379] -RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects in the present disclosure, the following parameters may be included together in the RRC Setup Complete message.
[0380] --guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity
[0381] UE 3 and AMF 70 are connected via an appropriate interface (e.g., the so-called N1 interface and / or the like). The N1 interface is responsible for providing communication between UE 3 and AMF 70 to support NAS signaling. The N1 interface can be established on 3GPP access and on non-3GPP access. For example, the following messages are communicated via the N1 interface.
[0382] -Registration Request message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Request message.
[0383] --5GS Registration Type, ngKSI, 5GS Mobile Identity, Non-Current Local NAS Key Set Identifier, 5GMM Capabilities, UE Security Capabilities, Requested NSSAI, Last Visited Registration TAI, S1 UE Network Capabilities, Uplink Data Status, PDU Session Status, MICO Indication, UE Status, Additional GUTI, Allowed PDU Session Status, UE Usage Settings, Requested DRX Parameters, EPS NAS Message Container, LADN Indication, Payload Container Type, Payload Container, Network Slicing Indication, 5GS Update Type, Mobile Station Class Tag 2, Supported Codecs, NAS Message Container, EPS Bearer Context Status, Requested Extended DRX Parameters, T3324 Value, UE Radio Capability ID, Requested Mapped NSSAI, Requested Additional Information, Requested WUS Assistance Information, N5GC Indication, and Requested NB-N1 Mode DRX Parameters.
[0384] -Registration Accept message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Accept message.
[0385] --5GS Registration Result, 5G-GUTI, Equivalent PLMN, 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 Deregistration Timer Value, T3502 Value, Emergency Number List, Extended Emergency Number List, SOR Transparent Container, EAP Message, NSSAI Include Mode, Operator Defined Access Class Definition, Negotiated DRX Parameters, Non-3GPP NW Policy, EPS Bearer Context Status, Negotiated Extended DRX Parameters, T3447 Value, T3448 Value, T3324 Value, UE Radio Capability ID, UE Radio Capability ID Removal Indication, Pending NSSAI, Encryption Key Data, CAG Information List, Truncated 5G-S-TMSI Configuration, Negotiated WUS Assistance Information, Negotiated NB-N1 Mode DRX Parameters, and Extended Rejected NSSAI.
[0386] -Registration Complete message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the Registration Complete message.
[0387] --SOR transparent container.
[0388] -Authentication Request message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be included together in the authentication request message.
[0389] --ngKSI, ABBA, authentication parameter RAND (5G authentication challenge), authentication parameter AUTN (5G authentication challenge) and EAP message.
[0390] -Authentication response message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the authentication response message.
[0391] --Authentication response message identifier, authentication response parameters and EAP message.
[0392] -Authentication Result message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Authentication Result message.
[0393] --ngKSI, EAP messages and ABBA.
[0394] -Authentication failure message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters can be filled together in the authentication failure message.
[0395] --Authentication failure message identifier, 5GMM reason and authentication failure parameters.
[0396] -Authentication Reject message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the authentication reject message.
[0397] --EAP message.
[0398] -Service Request Message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Service Request message.
[0399] --ngKSI, service type, 5G-S-TMSI, uplink data status, PDU session status, allowed PDU session status, NAS message container.
[0400] -Service Accept message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters can be filled together in the Service Accept message.
[0401] --PDU session status, PDU session reactivation result, PDU session reactivation result error reason, EAP message and T3448 value.
[0402] -Service Reject Message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in this disclosure, the following parameters may be filled together in the Service Reject Message.
[0403] --5GMM reason, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.
[0404] -Configuration Update Command message: This message is sent from AMF 70 to UE 3. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be filled together in the Configuration Update Command message.
[0405] --Configuration update indication, 5G-GUTI, TAI list, allowed NSSAI, service area list, full name of network, short name of network, local time zone, world time and local time zone, network daylight saving time, LADN information, MICO indication, network slicing indication, configured NSSAI, rejected NSSAI, operator-defined access class definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID removal indication, 5GS registration result, truncated 5G-S-TMSI configuration, additional configuration indication and extended rejected NSSAI.
[0406] -Configuration Update Complete message: This message is sent from UE 3 to AMF 70. In addition to the parameters disclosed by the aspects in the present disclosure, the following parameters may be filled together in the Configuration Update Complete message.
[0407] --Configuration update completion message identifier.
[0408] <User Equipment (UE)>
[0409] Figure 5 3 is a block diagram illustrating the main components of UE 3 (mobile device 3). As shown, UE 3 includes a transceiver circuit 31, which is operable to transmit signals to and receive signals from connected (one or more) nodes via one or more antennas 32. In addition, UE 3 may include a user interface 34 for inputting information from the outside or outputting information to the outside. Although not necessarily shown in this figure, UE 3 can have all the common functions of a traditional mobile device, and this can be appropriately provided by any one or any combination of hardware, software and firmware. For example, the software can be pre-installed in the memory and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). Controller 33 controls the operation of UE 3 according to the software stored in memory 36. The software includes an operating system 361 and a communication control module 362 having at least a transceiver control module 3621, as well as other. The communication control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes (such as (R)AN node 5 and AMF70, etc.). Such signaling may, for example, include appropriately formatted signaling messages related to access and mobility management procedures (for UE 3) (e.g., registration request messages and associated response messages). The controller 33 communicates with one or more universal subscriber identity modules (USIM) 35. If multiple USIM35s are equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIM 35s simultaneously.
[0410] The UE 3 may, for example, 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).
[0411] UE 3 can, for example, be a device for production or manufacturing and / or an energy-related machine (for example, equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal generators; nuclear power generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil pressure equipment; pneumatic equipment; metal processing machinery; manipulators; robots and / or their application systems; tools; injection molding molds or die-casting molds; reels; conveying equipment; lifting equipment; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper processing machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or tools for agriculture, forestry and / or fisheries; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems of any of the aforementioned equipment or machinery; etc.).
[0412] UE 3 may be, for example, a transportation device (e.g., a transportation device such as: a rolling stock; a motor vehicle; a motorcycle; a bicycle; a train; a bus; a cart; a rickshaw; a ship and other watercraft; an airplane; a rocket; a satellite; a drone; a balloon; etc.).
[0413] UE 3 may be, for example, an information and communication device (eg, information and communication devices such as: electronic computers and related devices; communication and related devices; electronic components; etc.).
[0414] UE 3 can be, for example, a refrigerator, a product using a refrigerator, a trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, consumer electronics and electronic equipment (for example, consumer electronic equipment such as the following: audio equipment; video equipment; speakers; radios; televisions; microwave ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers; electronic fans or related equipment; vacuum cleaners; etc.).
[0415] UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as: x-ray system; particle accelerator; radioisotope device; sonic wave device; electromagnetic application device; electronic power application device; etc.).
[0416] UE 3 can be, for example, an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a mapping or sensing instrument (e.g., a mapping or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag; etc.), a watch or clock, a laboratory instrument, an optical device, a medical device and / or system, a weapon, a piece of cutlery, a hand tool, or the like.
[0417] UE 3 may be, for example, a wirelessly 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 such as a personal computer, electrical measuring machine, etc.
[0418] UE 3 may be a part of or a device that provides applications, services and solutions related to the “Internet of Things (IoT)” described below using various wired and / or wireless communication technologies.
[0419] IoT devices (or "things") may be equipped with appropriate electronics, software, sensors, network connections, and / or the like that make it possible for these devices to 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 the need for human supervision or interaction. IoT devices may also remain stationary and / or inactive for long periods of time. IoT devices may be implemented as part of (usually) stationary equipment. IoT devices may also be embedded in non-stationary equipment (e.g., vehicles), or attached to animals or people to be monitored / tracked.
[0420] It will be appreciated that IoT technology may be implemented on any communication device that can connect to a communication network for sending / receiving data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.
[0421] It will be appreciated that IoT devices are sometimes also referred to as Machine Type Communication (MTC) devices or Machine to Machine (M2M) communication devices or Narrowband IoT UEs (NB-IoT UEs).It will be appreciated that the UE 3 may support one or more than one IoT or MTC applications.
[0422] UE 3 may be a smart phone or a wearable device (eg, smart glasses, a smart watch, a smart ring, or a hearable device).
[0423] UE 3 can be a car, a connected car, or an autonomous car, or a vehicle device, or a motorcycle, or a V2X (vehicle to everything) 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).
[0424] <(R)AN Node>
[0425] Figure 6 is a block diagram illustrating the main components of an exemplary (R)AN node 5 (e.g., a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations 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 (one or more) 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 a memory 55. For example, the software may be pre-installed in the memory and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 551 and a communication control module 552 having at least a transceiver control module 5521, among other things.
[0426] The communication control module 552 (using its transceiver control submodule) is responsible for (e.g., directly or indirectly) handling (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes (such as UE 3, another (R)AN node 5, AMF 70 and UPF 72, etc.). This signaling may, for example, include appropriately formatted signaling messages (e.g., RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages over the N2 reference point) and Xn Application Protocol (XnAP) messages (i.e., messages over the Xn reference point), etc., related to the radio connection (for a specific UE 3) and the connection with the core network 7, and in particular related to connection establishment and maintenance, etc. Such signaling may, for example, also include broadcast information (e.g., master information and system information) in the case of transmission.
[0427] The controller 54 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or mobile trajectory estimation when implemented.
[0428] The (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).
[0429] <System Overview of (R)AN Node 5 Based on O-RAN Architecture>
[0430] Figure 7 The (R)AN node 5 of the O-RAN architecture to which the (R)AN node 5 is applicable is schematically illustrated.
[0431] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is split into a radio unit (RU) 60, a distributed unit (DU) 61, and a centralized unit (CU) 62. In some aspects, the units can be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, and the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any function in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) can be implemented in the above integrated / combined unit. In addition, the CU 62 can be divided into two functional units such as a CU control plane (CP) and a CU user plane (UP). The CU CP has a control plane function in the (R)AN node 5. The CU UP has a user plane function in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as a so-called "E1" interface and / or the like).
[0432] The UE 3 and the corresponding serving RU 60 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as a so-called "fronthaul", "open fronthaul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as a so-called "midhaul", "open midhaul", "E2" interface and / or the like). Each CU 62 is also connected to a node in the core network 7 (such as a so-called core network node, etc.) via an appropriate interface (such as a so-called "backhaul", "open backhaul", (one or more than one) "N2" / "N3" interface and / or the like). In addition, the user plane part of the DU 61 may also be connected to the core network node 7 via an appropriate interface (such as a so-called (one or more than one) "N3" interface and / or the like).
[0433] According to the functions split between RU 60, DU 61 and CU 62, each unit provides some of the functions provided by (R)AN node 5. For example, RU 60 may provide functions for communicating with UE 3 over an air interface, DU 61 may provide functions for supporting MAC layer and RLC layer, and CU 62 may provide functions for supporting PDCP layer, SDAP layer and RRC layer.
[0434] <Radio Unit (RU)>
[0435] Figure 86 is a block diagram illustrating the main components of an exemplary RU 60 (e.g., the RU portion of a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations for 6G)). As shown, the RU 60 includes a transceiver circuit 601 that is operable to transmit signals to and receive signals from connected (one or more) UEs 3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or network elements via a network interface 603 (directly or indirectly). The controller 604 controls the operation of the RU 60 according to software stored in the memory 605. For example, the software may be pre-installed in the memory and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521, among others.
[0436] The communication control module 6052 (using its transceiver control submodule) is responsible for handling (e.g., directly or indirectly) signaling between the RU 60 and other nodes or units (such as a UE 3, another RU 60, and a DU 61, etc.). This signaling may, for example, include appropriately formatted signaling messages related to the radio connection (for a particular UE 3) and the connection with the RU 60, and in particular to the MAC layer and the RLC layer.
[0437] The controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or mobile trajectory estimation when implemented.
[0438] RU 60 can support non-public network (NPN). NPN can be stand-alone non-public network (SNPN) or public network integrated NPN (PNI-NPN).
[0439] As described above, the RU 60 may be integrated / combined into an integrated / combined unit with the DU 61. Any functions described for the RU 60 may be implemented in the above integrated / combined unit.
[0440] <Distributed Unit (DU)>
[0441] Fig. 961 (e.g., the DU portion of a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations for 6G)). As shown, the device includes a transceiver circuit 611 that is operable to transmit signals to and receive signals from other nodes or units (including RU 60) via a network interface 612. A controller 613 controls the operation of DU 61 according to software stored in a memory 614. For example, the software may be pre-installed in the memory 614 and / or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421, among others. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between DU 61 and other nodes or units (such as RU 60 and other nodes and units, etc.).
[0442] DU 61 can support non-public network (NPN). NPN can be stand-alone non-public network (SNPN) or public network integrated NPN (PNI-NPN).
[0443] As described above, the RU 60 may be integrated / combined as an integrated / combined unit with the DU 61 or the CU 62. Any functions described for the DU 61 may be implemented in one of the above integrated / combined units.
[0444] <Centralized Unit (CU)>
[0445] Fig.10 62 (e.g., the CU portion of a base station ("eNB" in LTE, "gNB" in 5G, base stations beyond 5G, base stations of 6G)). As shown, the device includes a transceiver circuit 621, which is operable to transmit signals to other nodes or units (including DU 61) and receive signals from these other nodes or units via a network interface 622. The controller 623 controls the operation of the CU 62 according to the software stored in the memory 624. For example, the software can be pre-installed in the memory 624 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421, as well as other. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units (such as DU 61 and other nodes and units, etc.).
[0446] The CU 62 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).
[0447] As described above, the CU 62 may be integrated / combined with the DU 61 as an integrated / combined unit. Any functions described for the CU 62 may be implemented in the above integrated / combined unit.
[0448] <amf>
[0449] Fig.11 70 is a block diagram illustrating the main components of AMF 70. As shown, the device includes a transceiver circuit 701, which is operable to transmit signals to other nodes (including UE 3, NSSAAF 76) via a network interface 702 and receive signals from these other nodes. A controller 703 controls the operation of AMF 70 according to the software stored in the memory 704. For example, the software can be pre-installed in the memory 704 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421, as well as other. The communication control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signaling between AMF 70 and other nodes (such as UE 3 (for example, via (R) AN node 5) and other core network nodes (including core network nodes in the HPLMN of UE 3 when UE 3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages related to access and mobility management procedures (for the UE 3) (eg registration request messages and associated response messages).
[0450] AMF 70 can support non-public networks (NPN). NPN can be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). AMF 7001 and AMF 7002 can have the same components as AMF 70.
[0451] <pcf>
[0452] Fig.12 73 is a block diagram illustrating the main components of PCF 73. As shown, the device includes a transceiver circuit 731, which is operable to transmit signals to other nodes (including AMF 70) via a network interface 732 and receive signals from these other nodes. The controller 733 controls the operation of PCF 73 according to the software stored in the memory 734. For example, the software can be pre-installed in the memory 734 and / or can be downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421, as well as others. The communication control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signaling between PCF 73 and other nodes (such as AMF 70 and other core network nodes (including core network nodes in the HPLMN of UE 3 when UE 3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages (eg, according to HTTP restful methods of a service-based interface) relating to policy management procedures (for the UE 3).
[0453] PCF 73 may support a non-public network (NPN). NPN may be a stand-alone non-public network (SNPN) or a public network integrated NPN (PNI-NPN). PCF 7301 and PCF 7302 may have the same components as PCF 73.
[0454] <ausf>
[0455] Fig.13 74 is a block diagram illustrating the main components of the AUSF 74. As shown, the device includes a transceiver circuit 741, which is operable to transmit signals to other nodes (including UDM 75) via a network interface 742 and receive signals from these other nodes. The controller 743 controls the operation of the AUSF 74 according to the software stored in the memory 744. For example, the software can be pre-installed in the memory 744 and / or can be downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes an operating system 7441 and a communication control module 7442 having at least a transceiver control module 74421, as well as others. The communication control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signaling between the AUSF 74 and other nodes (such as the AMF 70 and other core network nodes (including the core network nodes in the HPLMN of UE 3 when UE3 is roaming into) etc.). Such signalling may, for example, comprise appropriately formatted signalling messages (eg, according to HTTP restful methods of a service-based interface) relating to policy management procedures (for the UE 3).
[0456] The AUSF 74 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).
[0457] <udm>
[0458] Fig.14 75 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751, which is operable to transmit signals to other nodes (including AMF 70) and receive signals from these other nodes via a network interface 752. The controller 753 controls the operation of the UDM 75 according to the software stored in the memory 754. For example, the software can be pre-installed in the memory 754 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421, as well as other. The communication control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling between the UDM 75 and other nodes (such as AMF 70 and other core network nodes (including core network nodes in the VPLMN of UE 3 when UE 3 is roaming away) etc.). Such signalling may for example comprise appropriately formatted signalling messages (eg according to HTTP restful methods of a service based interface) related to mobility management procedures (for the UE 3).
[0459] The UDM 75 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).
[0460] <nssaaf>
[0461] Fig.15 76 is a block diagram illustrating the main components of the NSSAAF 76. As shown, the device includes a transceiver circuit 761, which is operable to transmit signals to other nodes (including AMF 70, AAA agent (AAA-P)) via a network interface 762 and receive signals from these other nodes. The controller 763 controls the operation of the NSSAAF 76 according to the software stored in the memory 764. For example, the software can be pre-installed in the memory 764 and / or can be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421, as well as others. The communication control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signaling between the NSSAAF 76 and other nodes (such as AMF 70 and other core network nodes (including core network nodes in the VPLMN of UE 3 when UE3 is roaming away) etc.). Such signalling may for example comprise appropriately formatted signalling messages (eg according to HTTP restful methods of a service based interface) related to mobility management procedures (for the UE 3).
[0462] The NSSAAF 76 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).
[0463] All or part of the exemplary aspects disclosed above may be described as, but not limited to, the following.
[0464] 5.5.1.2.2 Initial Registration Initiation
[0465] If the S-NSSAI is neither in the rejected NSSAI nor associated to (one or more) S-NSSAIs in the rejected NSSAI, the subset of configured NSSAIs provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAIs applicable to the current PLMN. Additionally, if NSSRG information is available, the subset of configured NSSAIs provided in the requested NSSAI shall be associated with at least one common NSSRG value. If the UE has a pending NSSAI, the subset of configured NSSAIs provided in the requested NSSAI and the pending NSSAI shall be associated with at least one common NSSRG value. If the UE already has an allowed NSSAI for other accesses, all (one or more) S-NSSAIs in the requested NSSAI for the current access shall share at least a common NSSRG value for all (one or more) S-NSSAIs of the allowed NSSAIs for other accesses. If the UE is simultaneously performing a registration procedure on other accesses, the UE shall include an S-NSSAI that shares at least a common NSSRG value across all access types.
[0466] 5.5.1.2.3 5GMM common process initiation
[0467] The AMF may include the newly configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message in the following cases:
[0468] a) The REGISTRATION REQUEST message does not include the requested NSSAI, and the initial registration request is not for access service in the SNPN;
[0469] b) The Registration Request message includes a requested NSSAI, which contains an S-NSSAI that is invalid in the serving PLMN;
[0470] c) the REGISTER REQUEST message includes a Requested NSSAI containing S-NSSAI(s) with incorrect mapped S-NSSAI(s);
[0471] d) the Registration Request message includes the Network Slicing Indication IE with the Default Configured NSSAI Indication bit set to "Requested NSSAI created from Default Configured NSSAI"; or
[0472] e) Any two S-NSSAIs of the requested NSSAI in the Registration Request message are not associated with any common NSSRG value.
[0473] f) If the UE has a pending NSSAI, the S-NSSAI of the requested NSSAI in the Registration Request message and the pending NSSAI are not associated with a common NSSRG value.
[0474] g) If the UE already has an allowed NSSAI for other accesses, then the S-NSSAI of the requested NSSAI in the Registration Request message on the current access and the allowed NSSAI are not associated with a common NSSRG value.
[0475] 5.5.1.3.2 Mobility and Periodic Registration Update Initiation
[0476] If the S-NSSAI is neither in the rejected NSSAI nor associated to (one or more) S-NSSAIs in the rejected NSSAI, the subset of configured NSSAIs provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAIs applicable to the PLMN. Additionally, if NSSRG information is available, the subset of configured NSSAIs provided in the requested NSSAI shall be associated with at least one common NSSRG value. If the UE has a pending NSSAI, the subset of configured NSSAIs provided in the requested NSSAI and the pending NSSAI shall be associated with at least one common NSSRG value. If the UE already has an allowed NSSAI for other accesses, all (one or more) S-NSSAIs in the requested NSSAI for the current access shall share at least the common NSSRG value for all (one or more) S-NSSAIs of the allowed NSSAIs for other accesses. If the UE is simultaneously performing a registration procedure on other accesses, the UE shall include an S-NSSAI that shares at least a common NSSRG value across all access types.
[0477] 5.5.1.3.3 5GMM common process initiation
[0478] The AMF may include the newly configured NSSAI for the current PLMN in the Registration Accept message in the following cases:
[0479] a) The Registration Request message does not include the requested NSSAI and the UE is not registered for access services in the SNPN;
[0480] b) The Registration Request message includes a requested NSSAI, which contains an S-NSSAI that is invalid in the serving PLMN;
[0481] c) The Registration Request message includes a requested NSSAI that contains an incorrect S-NSSAI; d) The Registration Request message includes a Network Slicing Indication IE in which the Default Configured NSSAI Indication bit is set to "Requested NSSAI created from the Default Configured NSSAI";
[0482] e) the Registration Request message includes the requested mapped NSSAI; or
[0483] f) Any two S-NSSAIs of the requested NSSAI in the Registration Request message are not associated with any common NSSRG value.
[0484] f) If the UE has a pending NSSAI, the S-NSSAI of the requested NSSAI in the Registration Request message and the pending NSSAI are not associated with a common NSSRG value.
[0485] g) If the UE already has an allowed NSSAI for other accesses, then the S-NSSAI of the requested NSSAI in the Registration Request message on the current access and the allowed NSSAI are not associated with a common NSSRG value.
[0486] <Modifications and Replacements>
[0487] Detailed aspects have been described above. As will be appreciated by those skilled in the art, many modifications and substitutions may be made to the above aspects while still benefiting from the disclosures embodied in these aspects. Many of these substitutions and modifications will now be described only by way of example.
[0488] In the above description, for ease of understanding, the UE 3 and the network device are described as having multiple discrete modules (such as a communication control module, etc.). Although these modules may be provided in this way for certain applications, for example, in the case where an existing system has been modified to implement the present disclosure, in other applications, such as in a system designed from the outset to take advantage of the present inventive features, these modules may be built into the entire operating system or code, and therefore these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware, or a mixture of these.
[0489] Each controller may include any suitable form of processing circuitry, including (but not limited to) for example: one or more hardware-implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memory / cache (program and / or data); processing registers; communications buses (e.g., control, data and / or address buses); direct memory access (DMA) functionality; hardware or software-implemented counters, pointers and / or timers; and / or the like.
[0490] In the above aspects, a plurality of software modules are described. As will be appreciated by those skilled in the art, software modules may be provided in compiled or uncompiled form and may be supplied to UE 3 and network devices as signals over a computer network or on a recording medium. In addition, one or more dedicated hardware circuits may be used to perform the functions performed by part or all of the software. However, the use of software modules is preferred because software modules facilitate updating UE 3 and network devices to update their functions.
[0491] In the above aspects, 3GPP radio communication (radio access) technology is used. However, according to the above aspects, any other radio communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technologies (e.g., BBF access, cable access, optical access, etc.) can also be used.
[0492] Items of user equipment may include, for example, communication devices such as mobile phones, smart phones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine type communication (MTC) devices may also be connected to a network. For simplicity, the present application refers to mobile devices (or UEs) in the description, but it will be understood that the described techniques may be implemented on any communication device (mobile and / or generally stationary) that can be connected to a communication network for sending / receiving data, regardless of whether such a communication device is controlled by human input or by software instructions stored in a memory.
[0493] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
[0494] As will be appreciated by those skilled in the art, the present disclosure can be embodied as methods and systems.Therefore, the present disclosure can take the form of a complete hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.
[0495] It will be understood that each frame of the block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that these instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in the flow chart and / or one or more frames of the block diagram. A general-purpose processor can be a microprocessor, but in an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, for example, multiple microprocessors, one or more microprocessors, or any other such configuration.
[0496] The method or algorithm described in conjunction with the examples disclosed herein can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium can be integrated with the processor. The processor and the storage medium can reside in an ASIC.
[0497] The foregoing description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
[0498] Although the present disclosure has been particularly shown and described with reference to the exemplary aspects of the present disclosure, the present disclosure is not limited to these aspects. It will be understood by those of ordinary skill in the art that various changes in form and detail may be made herein without departing from the spirit and scope of the present disclosure as defined in this document. For example, the above aspects are not limited to 5GS, and these aspects may also be applied to communication systems other than 5GS (e.g., 6G systems, systems beyond 5G).
[0499] <Supplementary Notes>
[0500] The whole or part of the exemplary aspects disclosed above may be described as, but not limited to, the following supplementary notes.
[0501] Supplementary Note 1. A method for a user equipment (UE), the method comprising:
[0502] receiving a message including pending network slice selection assistance information, i.e., pending NSSAI,
[0503] The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI;
[0504] In case a registration procedure using a second S-NSSAI is triggered, checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0505] In case the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value, a registration request message including the second S-NSSAI is sent.
[0506] Supplementary Note 2. A method of a communication device, the method comprising:
[0507] sending a first message including pending network slice selection assistance information, i.e., pending NSSAI,
[0508] The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI;
[0509] receiving a registration request message including a requested NSSAI,
[0510] The requested NSSAI includes a second S-NSSAI;
[0511] checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0512] In a case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, sending a second message including the configured NSSAI.
[0513] Supplementary Note 3. A user equipment, namely, UE, includes:
[0514] means for receiving a message comprising pending network slice selection assistance information, i.e. pending NSSAI,
[0515] The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI;
[0516] means for checking, if a registration procedure using a second S-NSSAI is triggered, whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0517] Means for sending a registration request message including the second S-NSSAI if the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value.
[0518] Supplementary Note 4. A communication device, comprising:
[0519] means for sending a first message comprising pending network slice selection assistance information, i.e. pending NSSAI,
[0520] The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI;
[0521] means for receiving a registration request message comprising a requested NSSAI,
[0522] The requested NSSAI includes a second S-NSSAI;
[0523] means for checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0524] Means for sending a second message including the configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
[0525] Supplementary Note 5. A method of a communication device, the method comprising:
[0526] Performing a registration procedure using a first single network slice selection assistance information, i.e., a first S-NSSAI, on an access;
[0527] receiving, on another access, a registration request message including a second S-NSSAI;
[0528] checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0529] In a case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, a message including the configured NSSAI is sent.
[0530] Supplementary Note 6. A method for a user equipment (UE), the method comprising:
[0531] Performing a registration procedure using a first single network slice selection assistance information, i.e., a first S-NSSAI, on an access;
[0532] sending a registration request message including the second NSSAI on another access; and
[0533] A message including a configured NSSAI is received when the first S-NSSAI and the second S-NSSAI are not associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0534] Supplementary Note 7. A communication device, comprising:
[0535] means for performing a registration procedure using a first single network slice selection assistance information, i.e., a first S-NSSAI, on an access;
[0536] means for receiving, on another access, a registration request message including a second S-NSSAI;
[0537] means for checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and
[0538] Means for sending a message including the configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
[0539] Supplementary Note 8. A user equipment, namely, UE, includes:
[0540] means for performing a registration procedure using a first single network slice selection assistance information, i.e., a first S-NSSAI, on an access;
[0541] means for sending a registration request message including a second NSSAI on another access; and
[0542] A component for receiving a message including a configured NSSAI when the first S-NSSAI and the second S-NSSAI are not associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0543] <Supplementary Note 2>
[0544] Supplementary Note 1. A method for a user equipment (UE), the method comprising:
[0545] Communicate with a communication device; and
[0546] Send a registration request message,
[0547] The registration request message includes the requested network slice selection assistance information, i.e., the requested NSSAI.
[0548] The requested NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and
[0549] The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0550] Supplementary Note 2. The method according to Supplementary Note 1 further includes:
[0551] The pending NSSAI is received from the communication device.
[0552] Supplementary Note 3. A user equipment, namely, UE, includes:
[0553] means for communicating with a communication device; and
[0554] A component used to send a registration request message,
[0555] The registration request message includes the requested network slice selection assistance information, i.e., the requested NSSAI.
[0556] The requested NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and
[0557] The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0558] Supplementary Note 4. The UE according to Supplementary Note 3, further comprising:
[0559] Means for receiving the pending NSSAI from the communications device.
[0560] Supplementary Note 5. A method of a communication device, the method comprising:
[0561] Communicating with a user equipment (UE); and
[0562] Send a message,
[0563] The message includes allowed network slice selection auxiliary information, i.e. allowed NSSAI,
[0564] The allowed NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and
[0565] The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0566] Supplementary Note 6. According to the method described in Supplementary Note 5,
[0567] The message includes the suspended NSSAI, and
[0568] The message is a registration acceptance message.
[0569] Supplementary Note 7. The method according to Supplementary Note 5 or 6,
[0570] The communication device has the suspended NSSAI.
[0571] Supplementary Note 8. A communication device, comprising:
[0572] means for communicating with a user equipment (UE); and
[0573] A widget for sending messages.
[0574] The message includes allowed network slice selection auxiliary information, i.e. allowed NSSAI,
[0575] The allowed NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and
[0576] The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
[0577] Supplementary Note 9. The communication device according to Supplementary Note 8,
[0578] The message includes the suspended NSSAI, and
[0579] The message is a registration acceptance message.
[0580] Supplementary Note 10. The communication device according to Supplementary Note 8 or 9,
[0581] The communication device has the suspended NSSAI.
[0582] Although the present invention has been particularly shown and described with reference to exemplary embodiments of the present invention, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that various changes in form and details may be made herein without departing from the spirit and scope of the present invention as defined by the claims.
[0583] This application is based upon and claims the benefit of priority from Indian Provisional Patent Application No. 202211016659, filed on March 24, 2022, the disclosure of which is incorporated herein in its entirety by reference.
[0584] Reference numerals list
[0585] 1Telecommunications System
[0586] 3UE
[0587] 5(R)AN Node
[0588] 7Core Network
[0589] 20Data Network
[0590] 31 Transceiver Circuit
[0591] 32 antennas
[0592] 33 Controller
[0593] 34 User Interface
[0594] 35USIM
[0595] 36 Memory
[0596] 51 transceiver circuit
[0597] 52 antenna
[0598] 53 Network Interface
[0599] 54 Controller
[0600] 55 Memory
[0601] 60RU
[0602] 61DU
[0603] 62CU
[0604] 70AMF
[0605] 71SMF
[0606] 72UPF
[0607] 73PCF
[0608] 74AUSF
[0609] 75UDM
[0610] 76NSSAAF
[0611] 361 Operating System
[0612] 362 Communication Control Module
[0613] 501 3GPP Access
[0614] 502 3GPP Access
[0615] 551 Operating System
[0616] 552 Communication Control Module
[0617] 601 transceiver circuit
[0618] 602 Antenna
[0619] 603 Network Interface
[0620] 604 Controller
[0621] 605 Memory
[0622] 611 transceiver circuit
[0623] 612 Network Interface
[0624] 613 Controller
[0625] 614 Memory
[0626] 621 transceiver circuit
[0627] 622 network interface
[0628] 623 Controller
[0629] 624 Memory
[0630] 701 transceiver circuit
[0631] 702 Network Interface
[0632] 703 Controller
[0633] 704 Memory
[0634] 731 transceiver circuit
[0635] 732 network interface
[0636] 733 Controller
[0637] 734 Memory
[0638] 741 transceiver circuit
[0639] 742 network interfaces
[0640] 743 Controller
[0641] 744 Memory
[0642] 751 transceiver circuit
[0643] 752 network interface
[0644] 753 Controller
[0645] 754 Memory
[0646] 761 transceiver circuit
[0647] 762 network interfaces
[0648] 763 Controller
[0649] 764 Memory
[0650] 3621 Transceiver Control Module
[0651] 5521 transceiver control module
[0652] 6051 Operating System
[0653] 6052 Communication Control Module
[0654] 6141 Operating System
[0655] 6142 Communication Control Module
[0656] 6241 Operating System
[0657] 6242 Communication Control Module
[0658] 7041 Operating System
[0659] 7042 Communication Control Module
[0660] 7341 Operating System
[0661] 7342 Communication Control Module
[0662] 7441 Operating System
[0663] 7442 Communication Control Module
[0664] 7541 Operating System
[0665] 7542 Communication Control Module
[0666] 7641 Operating System
[0667] 7642 Communication Control Module
[0668] 60521 Transceiver Control Module
[0669] 61421 Transceiver Control Module
[0670] 62421 Transceiver Control Module
[0671] 70421 Transceiver Control Module
[0672] 73421 Transceiver Control Module
[0673] 74421 Transceiver Control Module
[0674] 75421 Transceiver Control Module
[0675] 76421 Transceiver Control Module< / nssaaf> < / udm> < / ausf> < / pcf> < / amf>
Claims
1. A method for a user equipment (UE), the method include: Communicate with a communication device; as well as Send a registration request message, The registration request message includes the requested network slice selection assistance information, i.e., the requested NSSAI. The requested NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
2. The method according to claim 1, further comprising: include: The pending NSSAI is received from the communication device.
3. A user equipment, namely UE, include: Components for communicating with a communication device; as well as A component used to send a registration request message, The registration request message includes the requested network slice selection assistance information, i.e., the requested NSSAI. The requested NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
4. The UE according to claim 3, further comprising: include: Means for receiving the pending NSSAI from the communications device.
5. A method for a communication device, the method include: Communicate with user equipment, i.e. UE; as well as Send a message, The message includes allowed network slice selection auxiliary information, i.e. allowed NSSAI, The allowed NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
6. The method according to claim 5, in, The message includes the pending NSSAI, and The message is a registration acceptance message.
7. The method according to claim 5 or 6, in, The communication device has the pending NSSAI.
8. A communication device, include: A component for communicating with a user equipment, UE; as well as A widget for sending messages. The message includes allowed network slice selection auxiliary information, i.e. allowed NSSAI, The allowed NSSAI includes the first single network slice selection auxiliary information, i.e., the first S-NSSAI, and The first S-NSSAI and the second S-NSSAI in the suspended NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value.
9. The communication device according to claim 8, in, The message includes the pending NSSAI, and The message is a registration acceptance message.
10. The communication device according to claim 8 or 9, in, The communication device has the pending NSSAI.
11. A method for a communication device, the method include: sending a first message including pending network slice selection assistance information, i.e., pending NSSAI, The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI; receiving a registration request message including a requested NSSAI, The requested NSSAI includes a second S-NSSAI; checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and In a case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value, sending a second message including the configured NSSAI.
12. A communication device, include: means for sending a first message comprising pending network slice selection assistance information, i.e. pending NSSAI, The suspended NSSAI includes first single network slice selection auxiliary information, i.e., first S-NSSAI; means for receiving a registration request message comprising a requested NSSAI, The requested NSSAI includes a second S-NSSAI; means for checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common network slice simultaneous registration group value, i.e., at least one common NSSRG value; and Means for sending a second message including the configured NSSAI if the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
