UE method, UE, AMF method and AMF
By incorporating S-NSSAI with validity information, communication devices and UE can flexibly deploy network slices in non-uniform and time-limited areas, overcoming the limitations of existing 3GPP specifications.
Patent Information
- Application Number
- JP2024529764
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-22
- Filing Date
- 2022-11-28
- Publication Date
- 2024-11-13
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing 3GPP specifications are unable to meet new market demands for deploying network slices in areas that do not overlap with existing tracking areas and have limited lifetimes, leading to inflexible service provision and unclear components or structures.
A method for communication devices and user equipment (UE) that includes receiving and transmitting Single Network Slice Selection Assistance Information (S-NSSAI) with validity information, allowing for non-uniform deployment of network slices within tracking areas or for limited periods by using deployment areas and validity times.
Enables flexible and efficient deployment of network slices in restricted geographical areas for limited durations, addressing the limitations of current 3GPP specifications and enhancing service provision.
Smart Images

Figure 2024542225000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication device method, a User Equipment (UE) method, a communication device, a UE, a first communication device method, a communication terminal method, and a first communication device method. [Background technology]
[0002] According to non-patent document 2, during the registration procedure, the UE may obtain from the 5GC the network slice that it is authorized to use. [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.0.0 (2020-07) [Non-Patent Document 2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V17.2.0 (2021-09) [Non-Patent Document 3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V17.2.0 (2021-09) [Non-Patent Document 4] 3GPP TS 23.003: "Numbering, addressing and identification". V17.3.0 (2021-09) [Non-Patent Document 5] 3GPP TS 38.413: "NG Application Protocol (NGAP)". V16.7.0 (2021-10) [Non-Patent Document 6] IETF RFC 5580: "Carrying Location Objects in RADIUS and Diameter" Summary of the Invention [Problem to be solved by the invention]
[0004] The description in Non-Patent Document 2 means that when an authorized network slice is provided to a UE, the network slice is uniformly available for all cells within the assigned registration area. Note that a registration area includes a list of tracking areas.
[0005] On the other hand, there are new market requirements where network slices need to be deployed in areas that do not overlap with already deployed tracking areas and / or have a limited lifetime.
[0006] The latest 3GPP specifications cannot meet the new market demands mentioned above, so the 3GPP specifications need to be improved.
[0007] In order to flexibly provide services for network slices, problematic situations and unclear components or structures exist. [Means for solving the problem]
[0008] In an aspect of the disclosure, a method of a communications device includes receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid, and transmitting the S-NSSAI, the first information, and the second information.
[0009] In an aspect of the disclosure, a method in a User Equipment (UE) includes receiving a first message. The first message includes a Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The method includes determining whether the S-NSSAI is valid based on the first information and the second information. The method includes transmitting a second message if the S-NSSAI is valid. The second message includes the S-NSSAI.
[0010] In an aspect of the disclosure, a method for a communications device includes receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid, determining whether the S-NSSAI is valid based on the first information and the second information, and if the S-NSSAI is valid, transmitting first system information, where the first system information includes information indicating that the S-NSSAI is valid.
[0011] In an aspect of the present disclosure, a communications device includes means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid, and means for transmitting the S-NSSAI, the first information, and the second information.
[0012] In an aspect of the disclosure, a User Equipment (UE) includes means for receiving a first message. The first message includes a Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The UE includes means for determining whether the S-NSSAI is valid based on the first information and the second information. The UE includes means for transmitting a second message if the S-NSSAI is valid. The second message includes the S-NSSAI.
[0013] In an aspect of the disclosure, a communications device includes means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid, means for determining whether the S-NSSAI is valid based on the first information and the second information, and means for transmitting first system information if the S-NSSAI is valid, wherein the first system information includes information indicating that the S-NSSAI is valid.
[0014] In an aspect of the present disclosure, a method of a first communication device includes receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device, and transmitting at least one of information indicating that registration to a network slice related to the S-NSSAI is permitted and information indicating that registration to the network slice is not permitted to a communication terminal based on at least one of the information related to the validity time for the S-NSSAI and the information related to a validity area for the S-NSSAI.
[0015] In an aspect of the present disclosure, a method of a communication terminal includes sending a request message for a network slice to a first communication device, and receiving at least one of information related to an effective time for the network slice and information related to an effective area for the network slice from the first communication device.
[0016] In an aspect of the present disclosure, a method of a first communication device includes receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device, and transmitting at least one of information indicating that registration to a network slice related to the S-NSSAI is permitted based on at least one of the information related to the validity time for the S-NSSAI and the information related to a validity area for the S-NSSAI to a communication terminal.
[0017] In an aspect of the present disclosure, a method of a communication terminal includes sending a request message for a network slice to a first communication device, and receiving information from the first communication device indicating that registration with the network is permitted, the information including at least one of information related to a validity time for the network slice and information related to a validity area for the network slice.
[0018] In an aspect of the disclosure, a method of a first communication device includes receiving, from a second communication device, at least one of information related to a validity time for a network slice and information related to a validity area for the network slice, transmitting a first message related to at least one of the information related to a validity time for the network slice and the information related to a validity area for the network slice to a first base station, and receiving a second message from the first base station to confirm receipt of the first message by a first radio station.
[0019] In an aspect of the present disclosure, a method of a first communication device includes receiving, from a second communication device, at least one of information related to a validity time for a network slice and information related to a validity area for the network slice; receiving a first message from a first base station indicating that the first base station manages the network slice with at least one of a validity area and a validity time; and transmitting a second message to the first base station related to at least one of the validity time for the network slice and the validity area for the network slice. [Brief description of the drawings]
[0020] [Figure 1] Figure 1 is a signaling diagram relating to a first example of a first aspect (a procedure for provisioning a network slice to support localized services for a particular period of time). [Diagram 2] FIG. 2 is a signaling diagram for a first example of the first aspect (UE and network behavior after the UE is provided with a configured NSSAI). [Diagram 3] Figure 3 is a signaling diagram relating to a second example of the first aspect (a procedure for provisioning a network slice to support localized services in a specific period of time). [Figure 4] FIG. 4 is a signaling diagram for a second example of the first aspect (UE and network behavior after a temporary authorization NSSAI is provided to the UE). [Diagram 5] Figure 5 is a signaling diagram relating to a third example (provisioning of network slice information) of the first aspect. [Figure 6] FIG. 6 is a diagram showing an outline of the system. [Figure 7] FIG. 7 is a block diagram showing a user equipment (UE). [Figure 8] FIG. 8 is a block diagram illustrating an (R)AN node. [Figure 9] FIG. 9 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 10] FIG. 10 is a block diagram showing a Radio Unit (RU). [Figure 11] FIG. 11 is a block diagram showing a distributed unit (DU). [Figure 12] FIG. 12 is a block diagram showing a centralized unit (CU). [Figure 13] FIG. 13 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 14] FIG. 14 is a block diagram illustrating Unified Data Management (UDM). [Figure 15]FIG. 15 is a block diagram showing a network function (NF). [Figure 16] FIG. 16 shows the registration procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0021] <abbreviation> For purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following apply: An abbreviation defined in this specification takes precedence over the definition of the same abbreviation in Non-Patent Document 1 if such abbreviation exists.
[0022] 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function AS Access Stratum ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Planefff DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed (roaming) IAB Integrated access and backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out (roaming) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM Man In the Middle MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol N3IWF Non-3GPP InterWorking Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access-Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NPN Non-Public Network NR New Radio NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NTP Network Time Protocol NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name. SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited Public Land Mobile Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function
[0023] <Definition> For purposes of this specification, the terms and definitions given in Non-Patent Document 1 and the following apply. Terms defined in this specification take precedence over the definition of the same term in Non-Patent Document 1 if such term appears therein.
[0024] <General remarks> Those skilled in the art will appreciate that elements in the figures may be shown in simplified form and not necessarily drawn to scale. Further, with respect to the structure of a device, one or more components of the device may be represented by conventional symbols in the figures, and the figures may show only certain details appropriate to understanding aspects of the present disclosure, so as not to obscure the figures with details that will be readily apparent to one of ordinary skill in the art having the benefit of the description herein.
[0025] To promote an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the principles. It will nevertheless be understood that no limitation of the scope of the present disclosure is intended thereby. Such alterations 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, are to be construed as being within the scope of the present disclosure.
[0026] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method comprising a list of steps may include not only those steps, but also other steps not expressly listed or inherent in such process or method. Similarly, the term "comprising" preceding one or more devices, entities, subsystems, elements, structures, or components does not, absent further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the phrases "in an embodiment," "in another embodiment," and similar terms may all refer to the same embodiment, but do not necessarily do so.
[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.
[0028] In the following specification and claims, reference will be made to a number of terms that shall be defined to have the following meanings: The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.
[0029] Information as used herein refers to data and knowledge, when data is meaningful information and represents values attributed to parameters. Moreover, knowledge refers to an understanding of an abstract or concrete concept. It should be noted that the exemplary system is simplified to facilitate the description of the subject matter of the present disclosure and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are contemplated to be within the scope of the present disclosure.
[0030] Each of the aspects and elements included in each of the following aspects may be implemented independently or in combination with each other, and each aspect includes different novel features, and thus contributes to achieving different objectives or solving different problems and achieving different advantages.
[0031] An exemplary object of the present disclosure is to provide a method and apparatus that can solve the above problems.
[0032] A method for a communications device according to an example aspect of the present disclosure includes receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The method includes transmitting the S-NSSAI, the first information, and the second information.
[0033] A method in a User Equipment (UE) according to an example aspect of the present disclosure includes receiving a first message. The first message includes a Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The method includes determining whether the S-NSSAI is valid based on the first information and the second information. The method includes transmitting a second message if the S-NSSAI is valid. The second message includes the S-NSSAI.
[0034] A method of a communications device according to an example aspect of the disclosure includes receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The method includes determining whether the S-NSSAI is valid based on the first information and the second information. The method includes transmitting first system information if the S-NSSAI is valid. The first system information includes information indicating that the S-NSSAI is valid.
[0035] A communications apparatus according to an exemplary aspect of the disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The at least one hardware processor is configured to transmit the S-NSSAI, the first information, and the second information.
[0036] A User Equipment (UE) according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The at least one hardware processor is configured to determine whether the S-NSSAI is valid based on the first information and the second information. The at least one hardware processor is configured to transmit a second message if the S-NSSAI is valid. The second message includes the S-NSSAI.
[0037] A communication device according to an exemplary aspect of the present disclosure includes a memory and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The at least one hardware processor is configured to determine whether the S-NSSAI is valid based on the first information and the second information. The at least one hardware processor is configured to transmit first system information if the S-NSSAI is valid. The first system information includes information indicating that the S-NSSAI is valid.
[0038] A method of a first communication device according to an example aspect of the present disclosure includes receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device. The method includes transmitting, to a communication terminal, at least one of information indicating that registration in a network slice related to the S-NSSAI is permitted and information indicating that registration in the network slice is not permitted based on at least one of the information related to a validity time for the S-NSSAI and the information related to a validity area for the S-NSSAI.
[0039] A method of a communication terminal according to an example aspect of the present disclosure includes transmitting a request message for a network slice to a first communication device, the method including receiving at least one of information related to an effective time for the network slice and information related to an effective area for the network slice from the first communication device.
[0040] A method of a first communication device according to an example aspect of the present disclosure includes receiving, from a second communication device, information related to Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving, from the second communication device, at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI. The method includes transmitting, to a communication terminal, at least one of information indicating that registration in a network slice related to the S-NSSAI is permitted based on at least one of the information related to a validity time for the S-NSSAI and the information related to a validity area for the S-NSSAI.
[0041] A method for a communications terminal according to an example aspect of the present disclosure includes transmitting a request message for a network slice to a first communications device, the method including receiving information from the first communications device indicating that registration with the network is permitted, the information including at least one of information related to a validity time for the network slice and information related to a validity area for the network slice.
[0042] A method of a first communication device according to an example aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes transmitting a first message related to at least one of the information related to a validity time for the network slice and information related to a validity area for the network slice to a first base station. The method includes receiving a second message from the first base station to confirm receipt by the first wireless station of the first message.
[0043] A method of a first communication device according to an example aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes receiving, from a first base station, a first message indicating that the first base station manages the network slice with at least one of the validity area and the validity time. The method includes transmitting, to the first base station, a second message related to at least one of the validity time for the network slice and the validity area for the network slice.
[0044] A method of a first communication device according to an exemplary aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes transmitting a first message related to at least one of the information related to a validity time for the network slice and information related to a validity area for the network slice to a first base station. The method includes receiving a second message from the first base station for verifying receipt by the first radio station of the first message. The method includes transmitting at least one of the information related to the validity area and the information of the validity time to a communication terminal.
[0045] A method of a first communication device according to an exemplary aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes receiving, from a first base station, a first message indicating that the first base station manages the network slice with at least one of the validity area and the validity time. The method includes transmitting, to the first base station, a second message related to at least one of the validity time for the network slice and the validity area for the network slice. The method includes transmitting, to a communication terminal, at least one of the information related to the validity area and the information of the validity time.
[0046] A method of a first communication device according to an exemplary aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes transmitting a first message related to at least one of the information related to a validity time for the network slice and information related to a validity area for the network slice to a first base station. The method includes receiving a second message from the first base station for verifying receipt by the first radio station of the first message. The method includes transmitting the information related to the validity area and the validity time to a communication terminal.
[0047] A method of a first communication device according to an exemplary aspect of the present disclosure includes receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice. The method includes receiving, from a first base station, a first message indicating that the first base station manages the network slice with at least one of the validity area and the validity time. The method includes transmitting, to the first base station, a second message related to at least one of the validity time for the network slice and the validity area for the network slice. The method includes transmitting the information related to the validity area and the validity time to a communication terminal.
[0048] <First aspect> To enable Home Public Land Mobile Network (HPLMN) operators to provide procedures for deploying network slices that are dedicated to handling temporary events in small geographic areas or for limited durations with minimal required signaling, HPLMN operators require mechanisms in 3GPP TS 2010-010112, 3GPP TS 2010-010112, and other 3GPP specifications that support the deployment of network slices to handle temporary events in limited geographic locations. Typically, operators deploy network slices uniformly in tracking or registration areas for longer durations.
[0049] A first aspect discloses a mechanism that allows HPLMN operators to deploy network slices covering services that are deployed for a short period of time in a limited area. More specifically, it discloses procedures for supporting non-uniform deployment of network slices in tracking or registration areas or for a limited period of time to support services that are required for a short period of time in a limited geographic location.
[0050] For example, the first aspect can solve the above problems such as the inability of the latest 3GPP specifications to meet the above-mentioned new market demands.
[0051] <First Example of the First Aspect> A first example of the first aspect discloses a procedure in which the AMF 70 transmits a configured NSSAI including an S-NSSAI with a validity time and a deployment area to the UE 3. The deployment area may be, for example, a list of cell IDs, a list of Frequency Bands (FBs), a list of cell ID and FB combinations, a geographical area that maps to either a tracking area or a cell in which the S-NSSAI is deployed to provide a service. The deployment area may be a geographical area coded by GPS or any format, an area defined by an address (e.g., city, town, village, administrative district), or a building (e.g., ABC Stadium, ABC Station, ABC Building. Outside this deployment area (e.g., tracking area or cell), the service related to the S-NSSAI is not deployed, accessible, or available to the UE 3. The deployment area may be a location area in which the UE 3 can receive the service for the S-NSSAI.
[0052] The validity time may be a period during which the S-NSSAI is valid for a service. After this period, the service will not be provided to the UE 3. The validity time may be a time during which the S-NSSAI is valid for a service or invalid for a service (e.g., valid at 9:00 a.m., invalid at 10:00 a.m., valid at 3:00 p.m.). The validity time may be a period or duration during which the S-NSSAI is valid for a service or invalid for a service. The validity time may indicate a period during which the service is available for the S-NSSAI, i.e., a period during which the UE 3 can register with the S-NSSAI to receive the service associated with the S-NSSAI.
[0053] When the UE 3 receives the configured NSSAI, the UE 3 stores the configured NSSAI, i.e., the UE 3 stores the S-NSSAI together with the deployment area or validity period, or both if both are provided. The validity period can be a validity time or a validity duration. When the UE 3 gets a trigger to access a service related to the S-NSSAI, the UE 3 checks whether the current cell of the UE 3 belongs to the deployment area for the S-NSSAI, or whether the current time is less than the validity time for the S-NSSAI, or both factors if both the deployment area and the validity time are provided. If the S-NSSAI access criteria are met, the UE 3 sends a registration request message including the S-NSSAI in the request NSSAI during the registration procedure. When the AMF 70 receives the registration request message, the AMF 70 checks whether the UE 3 is accessing the S-NSSAI from the deployment area or within the validity period of the S-NSSAI, or with both factors if both are applicable. If the access criteria is met, the AMF 70 further processes the S-NSSAI and provides the S-NSSAI in the allowed NSSAI in a registration accept message or other existing NAS message if the registration procedure is successful. When the UE 3 receives the registration accept message, the UE 3 may establish a PDU session related to the S-NSSAI. When the UE 3 moves out of the deployment area, or the validity time for the S-NSSAI expires, or the validity time passes, at least one of the UE 3 and the network removes the S-NSSAI from the allowed NSSAI locally or removes the S-NSSAI with explicit NAS signaling (i.e., by sending an existing NAS message). The deployment area may be represented as a deployed area or a deployment zone. The validity time may be represented as a validity period or duration. The current time may be represented as a current date. For example, the validity time in the present disclosure (e.g., aspects included in the present disclosure) may be represented as follows: - In the time zone JST (Japan Standard Time), from 0:00 on January 1, 2022 to 23:59 on January 31, 2022 - From 17:00 to 19:00 every day - Every Monday
[0054] For example, when receiving a configured NSSAI (or an S-NSSAI in the configured NSSAI), the UE3 may start the validity time for the S-NSSAI. For the S-NSSAI, the UE3 has received the validity time, and the period is equal to the received validity time. The S-NSSAI in the configured NSSAI may be represented as the configured S-NSSAI.
[0055] The first example of the first aspect is disclosed with reference to FIGS. 1 and 2. FIG. 1 shows the provisioning of the configured NSSAI for the UE3, while FIG. 2 shows the UE3 and network behavior after the configured NSSAI is provided to the UE3.
[0056] When the S-NSSAI in the configured NSSAI is configured in the field of "valid timer" or "deployment zone", the UE may send the S-NSSAI in the requested NSSAI when the validity time is running (or has not expired) or when the UE is within the deployment zone of the S-NSSAI.
[0057] <Provisioning of the Configured NSSAI for the UE> 1. The UE3 sends a registration request message including a restricted slice support indicator to the AMF70. The restricted slice support indicator indicates that the UE3 supports the S-NSSAI in at least one of the deployment area and the validity time attributes. For example, the restricted slice support indicator may indicate that the UE3 supports the S-NSSAI in at least one of the deployment area and the validity time. The registration request message may be sent during the initial registration procedure, the mobility registration procedure, or the periodic registration procedure. The registration request message may include user identification information. The user identification information may indicate the identification information of the UE3. The registration request message may include the requested NSSAI.
[0058] 2. An authentication procedure may be performed. For example, the authentication procedure may be performed according to current 3GPP standards.
[0059] 3. A security mode command procedure may be performed. For example, a security mode command procedure may be performed according to current 3GPP standards.
[0060] 4. The AMF 70 invokes the Nudm_UECM_Registration service operation to register the AMF 70 with the UDM 75.
[0061] 5. The AMF 70 invokes the Nudm_SDM_GET service operation by sending a Nudm_SDM_GET request message.
[0062] 6. The UDM 75 sends a subscribe NSSAI including the S-NSSAI1 with at least one of a deployment area for the S-NSSAI1 and a validity time for the S-NSSAI1 to the AMF 70. The subscribe NSSAI may be associated with the UE 3.
[0063] For example, if a deployment area is applicable for the S-NSSAI for UE3, UDM75 sends a subscribe NSSAI including the S-NSSAI1 with the deployment area.
[0064] For example, if a validity time is applicable for the S-NSSAI for UE3, UDM75 sends a subscribe NSSAI including the S-NSSAI1 with the validity time.
[0065] For example, if the deployment area and validity time are applicable for the S-NSSAI for UE3, UDM75 sends a subscribe NSSAI including the S-NSSAI1 with at least one of the deployment area and validity time.
[0066] For example, if the deployment area and validity time are applicable for the S-NSSAI for UE3, UDM75 sends a subscribe NSSAI including the S-NSSAI1 with both the deployment area and validity time.
[0067] For example, UDM 75 may store information for determining whether at least one of a deployment area and a validity time is applicable for an S-NSSAI for UE 3.
[0068] For example, the UDM 75 may send a Nudm_SDM_GET response message that includes a subscribe NSSAI.
[0069] For example, when UDM 75 receives a Nudm_SDM_GET request message, UDM 75 may send a Nudm_SDM_GET response message that includes a subscribe NSSAI.
[0070] The deployment area may form one of the following examples or a combination of the following examples.
[0071] - A list of tracking areas. The list of tracking areas may be a list of TAIs. For example, a deployment area may indicate a list of TAs or TAIs for which the S-NSSAI is valid or available.
[0072] - A list of cell IDs. The cell IDs can be NR Cell Global Identity (NCGI) as defined in 3GPP TS 36.110, NR Cell Identity (NCI) as defined in 3GPP TS 36.110, E-UTRAN Cell Global Identifier (ECGI) as defined in 3GPP TS 36.110, or Global Cable Identifier (GCI) as defined in 3GPP TS 36.110. For example, the deployment area may indicate a list of cells or cell IDs for which the S-NSSAI is valid or available.
[0073] A list of Frequency Bands (FBs). For example, a deployment area may indicate a list of FBs for which the S-NSSAI is valid or available.
[0074] - A list of cell ID and FB combinations. For example, a deployment area may indicate a list of cell ID and FB combinations for which the S-NSSAI is valid or available.
[0075] A geographic area coded by Global Positioning System (GPS) format or any other format. For example, the deployment area may indicate a geographic area in which the S-NSSAI is valid or available.
[0076] -A city address (e.g., city, town, village, administrative district), zip code, building (e.g., place name such as Tokyo Stadium, Tokyo Station, etc.), or a building formed by a GPS location, or a location represented in a city and geospatial location format as defined in Non-Patent Document 6. For example, the deployment area may indicate a city address, zip code, building, etc. for which S-NSSAI is valid or available.
[0077] When the AMF 70 receives a subscribe NSSAI from the UDM 75, the AMF 70 may store the subscribe NSSAI.
[0078] The subscribed NSSAI may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0079] The UDM 75 may generate the subscribed NSSAI based on at least one of a local configuration in the UDM 75, an operator's policy, and an S-NSSAI to which the UE 3 subscribes.
[0080] For example, if UDM75 stores information indicating that UE3 subscribes to S-NSSAI1, UDM75 may generate a subscribe NSSAI for S-NSSAI1.
[0081] The deployment area may be represented as first information indicating where S-NSSAI1 is valid, and the validity time may be represented as second information indicating when S-NSSAI1 is valid.
[0082] 7. If the UE 3 indicates a restricted slice support indicator in the registration request message in step 1, the AMF 70 sends the S-NSSAI1 in the registration accept message together with at least one of the deployment area and validity time in the configured NSSAI. Otherwise, the AMF 70 does not provide the S-NSSAI1 in the configured NSSAI to the UE 3.
[0083] For example, if the deployment area and validity time are applicable to S-NSSAI1, AMF70 may send S-NSSAI1 along with at least one of the deployment area and validity time in the configured NSSAI in the registration accept message.
[0084] For example, if a deployment area is applicable for S-NSSAI1, AMF70 may send S-NSSAI1 along with the deployment area in the configured NSSAI in the registration accept message.
[0085] For example, if a validity time is applicable for S-NSSAI1, AMF70 may send S-NSSAI1 along with the validity time in the configured NSSAI in the registration accept message.
[0086] For example, the AMF 70 may store information for determining whether at least one of the deployment area and the validity time is applicable for the S-NSSAI for the UE 3.
[0087] For example, if UE3 does not indicate a restricted slice support indicator in the registration request message in step 1, AMF70 may send S-NSSAI1 in the registration accept message along with at least one of the deployment area and validity time in the configured NSSAI.
[0088] The AMF 70 may convert the received deployment area into a list of tracking areas (e.g., a list of TAIs) or a list of cell IDs. The AMF 70 may convert the received validity time into a validity time in another time format, e.g., a duration for the local time zone.
[0089] For example, the AMF 70 stores information that converts a received deployment area into a list of tracking areas (eg, a list of TAIs) or a list of cell IDs.
[0090] For example, AMF 70 may store information indicating that the location or position indicated by the deployment area includes cell 1 identified by TA1 or cell ID1, and convert the received deployment area into a list that includes TA1 or cell ID1.
[0091] For example, AMF 70 may store information indicating that the FB indicated by the deployment area is used in cell 1 identified by TA1 or cell ID1, and convert the received deployment area into a list including TA1 or cell ID1.
[0092] The restricted slice support indicator may indicate that the UE 3 supports receiving an S-NSSAI with at least one of a deployment area and a validity time in the configured NSSAI.
[0093] The contents of the constructed NSSAI may correspond to the contents of the subscribe NSSAI.
[0094] For example, if the subscribed NSSAI includes S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1, the constructed NSSAI may include S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1.
[0095] For example, the AMF 70 may determine the contents of the configured NSSAI. For example, the AMF 70 may send the configured NSSAI for the S-NSSAI included in the request NSSAI in step 1.
[0096] For example, it is assumed that in step 1, AMF 70 receives a request NSSAI including S-NSSAI1, and in step 6, AMF 70 receives a subscribe NSSAI including S-NSSAI1, a deployment area for S-NSSAI1, and a validity time for S-NSSAI1, and S-NSSAI2, a deployment area for S-NSSAI2, and a validity time for S-NSSAI2. In this case, AMF 70 may send a configured NSSAI including S-NSSAI1, a deployment area for S-NSSAI1, and a validity time for S-NSSAI1.
[0097] The configured NSSAI may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0098] 8. Upon receiving the registration accept message, the UE 3 stores the configured NSSAI.
[0099] 9. UE 3 may send a registration completion message. For example, UE 3 may send a registration completion message after step 7 or 8. For example, UE 3 may send a registration completion message corresponding to a registration acknowledgement message or any message received in step 7 or 8.
[0100] <UE and network behavior after the configured NSSAI is provided to the UE> 0. It is assumed that the UE3 and the 5GS have performed the registration procedure as shown in Figure 1 in the first example of the first aspect, which means that the UE3 may store the S-NSSAI1 in the configured NSSAI together with at least one of the deployment area and the validity time.
[0101] 1. When UE3 gets a trigger to access a service related to S-NSSAI1, UE3 checks whether the current cell of UE3 or the current location of UE3 belongs to a deployment area, or whether the current time is less than the valid time for S-NSSAI1, or both factors if both the deployment area and the valid time for S-NSSAI1 are provided. For example, when an application related to S-NSSAI1 in UE3 is activated, UE3 gets a trigger to access a service related to S-NSSAI1.
[0102] "The current cell of UE3 or the current location of UE3 belongs to the deployment area" may be expressed as a first criterion. "The current time is less than the valid time" may be expressed as a second criterion. At least one of the first criterion and the second criterion may be expressed as an S-NSSAI access criterion.
[0103] For example, if UE3 stores S-NSSAI1 in the configured NSSAI along with both the deployment area and validity time, UE3 may check whether at least one of the first criterion and the second criterion is met.
[0104] For example, if the UE 3 stores S-NSSAI1 in the configured NSSAI along with the deployment area, the UE 3 may check whether the first criterion is met.
[0105] For example, if the UE 3 stores the S-NSSAI1 in the configured NSSAI along with the validity time, the UE 3 may check whether the second criterion is met.
[0106] For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current cell of the UE 3 belongs to or is the same as the cell indicated by the deployment area. In this case, the UE may use a cell ID to check whether the current cell of the UE 3 belongs to or is the same as the cell indicated by the deployment area. For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current TA of the UE 3 belongs to or is the same as the TA indicated by the deployment area. In this case, the UE may use a TAI to check whether the current TA of the UE 3 belongs to or is the same as the TA indicated by the deployment area.
[0107] For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current location of the UE 3 belongs to or is the same as the location indicated by the deployment area.
[0108] For example, UE3 may obtain information indicating the current cell or the current TA from another node, such as (R)AN5.
[0109] For example, the UE 3 may obtain the current location of the UE 3 by using a GPS.
[0110] For example, the UE 3 may convert the location information indicated by the deployment area into information indicating a cell, and the UE 3 checks whether the current cell of the UE 3 belongs to the cell indicated by the converted information. The information indicating a cell may be a cell ID. For example, the UE 3 may store the information converted into the information indicating a cell. For example, the UE 3 may store a list including a cell ID and at least one combination of a TA, an FB, and a geographic area, etc.
[0111] For example, when the UE 3 checks whether the second criterion is met, the UE 3 may check whether the current time or the current date is within the time or period indicated by the validity time.
[0112] 2-1. If the S-NSSAI access criteria for S-NSSAI1 in step 1 is met, UE3 sends an RRC message to (R)AN5. The RRC message includes a NAS container. The NAS container includes a registration request message that includes S-NSSAI1 in the request NSSAI. The registration request message may include a user identity. The user identity may indicate the identity of UE3.
[0113] (R)AN5 may include an (R)AN node such as an NG-RAN node or a gNB.
[0114] For example, if the UE 3 determines that at least one of the first criterion and the second criterion is met, the UE 3 may transmit an RRC message.
[0115] For example, if the UE 3 determines that the first criterion is met, the UE 3 may transmit an RRC message.
[0116] For example, if the UE 3 determines that the second criterion is met, the UE 3 may transmit an RRC message.
[0117] For example, if the current cell of UE3 belongs to a deployment area and the current time is less than the validity time of S-NSSA1, or if both the deployment area and validity time of S-NSSAI1 are provided and both factors are met, UE3 sends an RRC message to (R)AN5, where the RRC message includes a NAS container including a registration request message with S-NSSAI1 in the requested NSSAI.
[0118] For example, if the current location of UE3 belongs to a deployment area and the current time is less than the validity time of S-NSSA1, or if both the deployment area and validity time of S-NSSAI1 are provided and both factors are met, UE3 sends an RRC message to (R)AN5, where the RRC message includes a NAS container including a registration request message with S-NSSAI1 in the requested NSSAI.
[0119] For example, it is assumed that the deployment area indicates area "Z1" and the validity time indicates "January 2022". If the UE 3 determines that the current cell (e.g., cell 1) of the UE 3 belongs to area "Z1" and the current date (e.g., "December 2021") does not exceed "January 2022", the UE 3 sends an RRC message. For example, the UE 3 may store information indicating that the area "Z1" includes cell 1 and may use this information to confirm the first criterion.
[0120] For example, UE3 may convert area "Z1" into information indicating a cell, and may determine whether a current cell belongs to or is the same as a cell indicated by the converted information. If UE3 determines that the current cell of UE3 belongs to or is the same as a cell indicated by the converted information and the current date (e.g., "December 2021") does not exceed "January 2022", UE3 sends an RRC message.
[0121] If the UE3 determines that the current cell of the UE3 does not belong to the area "Z1" or the current date (e.g., "February 2022") is beyond "January 2022", the UE3 does not send an RRC message. If the current date (e.g., "December 2021") is not beyond "January 2022", the UE3 may determine that the validity time has not expired. If the current date (e.g., "February 2022") is beyond "January 2022", the UE3 may determine that the validity time has expired.
[0122] For example, a "determination that the current date is within the valid time" may be expressed as a "determination that the current date is less than the valid time" or a "determination that the current date is prior to the valid time."
[0123] The deployment area may indicate where S-NSSAI1 is valid or available. If the deployment area indicates area "Z1", the deployment area may mean that S-NSSAI1 is valid or available in area "Z1".
[0124] The validity time may indicate a time when the S-NSSAI1 is valid or available for use. If the validity time indicates "January 2022", the validity time may mean that the S-NSSAI1 is valid or available until January 2022.
[0125] If the deployment area indicates a list of FBs, the deployment area may indicate the FBs in which S-NSSAI1 is valid or available. If the deployment area indicates "FB1", the deployment area may mean that S-NSSAI1 is valid or available in "FB1". For example, UE3 checks whether UE3 tunes to "FB1", and if UE3 determines that UE3 is currently tuned to "FB1", UE3 sends an RRC message.
[0126] If the deployment area indicates a list of cell ID and FB combinations, the deployment area may indicate the cell ID and FB combinations for which S-NSSAI1 is valid or available. If the deployment area indicates a combination of "Cell ID1" and "FB1", the deployment area may mean that S-NSSAI1 is valid or available in a cell that operates in "FB1" and is identified by "Cell ID1". For example, UE3 checks whether UE3 is located in a cell identified by "Cell ID1" and whether UE3 tunes to "FB1", and if UE3 determines that UE3 is located in a cell identified by "Cell ID1" and that UE3 is currently tuned to "FB1", UE3 sends an RRC message.
[0127] 2-2. Upon receiving the RRC message from the UE 3 in step 2-1, the (R)AN 5 sends an initial UE message to the AMF 70. The initial UE message includes user location information and a NAS PDU. The NAS PDU includes a registration request message including an S-NSSAI1 in the request NSSAI. The registration request message may include user identity information. The user identity information may indicate the identity of the UE 3. The user location information may include cell level information, e.g., cell ID, E-UTRA CGI, NR CGI, etc. The user location information may be used to provide location information of the UE 3.
[0128] 3. When the AMF 70 receives an initial UE message including a registration request message, the AMF 70 checks whether the UE 3 is accessing the S-NSSAI1 from the deployment area or within the validity time for the S-NSSAI1, or with both factors if both are applicable. If the AMF 70 checks whether the UE 3 is accessing the S-NSSAI1 from the deployment area, the AMF 70 may use the user location information. For example, the AMF 70 may use the user location information to check whether the UE 3 is inside the deployment area. If the AMF 70 checks whether the UE 3 is accessing the S-NSSAI1 within the validity time, the AMF 70 may use the network time provided by an NTP server to compare the validity time for the S-NSSAI1.
[0129] "UE3 accesses S-NSSAI1 from the deployment area" may be expressed as a third criterion. "UE3 accesses S-NSSAI1 within the valid time" may be expressed as a fourth criterion. At least one of the third criterion and the fourth criterion may be expressed as an access criterion.
[0130] For example, if the AMF 70 stores a subscribed NSSAI including S-NSSAI1 with both the deployment area and the validity time, the AMF 70 checks whether the UE 3 has accessed the S-NSSAI1 from the deployment area within the validity time.
[0131] For example, when AMF70 stores a subscribed NSSAI including S-NSSAI1 with both the deployment area and the validity time, AMF70 checks whether UE3 is accessing S-NSSAI1 from the deployment area or whether UE3 is accessing S-NSSAI1 within the validity time.
[0132] For example, if the AMF 70 stores a subscribed NSSAI including S-NSSAI1 along with the deployment area, the AMF 70 checks whether the UE 3 is accessing the S-NSSAI1 from the deployment area.
[0133] For example, if the AMF 70 stores a subscribe NSSAI including the S-NSSAI1 along with the validity time, the AMF 70 checks whether the UE 3 accesses the S-NSSAI1 within the validity time.
[0134] For example, it is assumed that the deployment area indicates "Cell ID1", the validity time indicates "January 2022", the user location information indicates "Cell ID1", and the current date is "December 2021". In this case, AMF 70 checks whether UE 3 is accessing S-NSSAI 1 from cell 1 identified by "Cell ID1" and whether the current date is not beyond "January 2022". In this case, AMF 70 determines that UE 3 is accessing S-NSSAI 1 from the deployment area (i.e., cell 1 identified by "Cell ID1") within the validity time.
[0135] For example, if the deployment area indicates information other than cell level information (e.g., cell ID), the AMF 70 may convert the information indicated by the deployment area into cell level information. For example, the AMF 70 may store the information to be converted into a cell ID. For example, the AMF 70 may store a list including the cell ID and at least one combination of a TA, an FB, and a geographic area, etc.
[0136] 4. If the access criteria are met, the AMF 70 further processes the S-NSSAI1 and provides the S-NSSAI1 to the UE 3 in an Authorization NSSAI in a Registration Accept message or other existing NAS message.
[0137] For example, if the access criteria are met and the registration procedure is successful in the AMF 70, the AMF 70 further processes the S-NSSAI1 and provides the S-NSSAI1 in the Authorized NSSAI. If the AMF 70 checks whether the UE 3 is accessing the S-NSSAI1 from the deployed area, whether it is related to the validity period of the S-NSSAI1, or whether it is related to both factors (the deployed area or the validity period of the S-NSSAI1), the AMF 70 processes the S-NSSAI1 and provides the S-NSSAI1 to the UE 3 in the Authorized NSSAI in a registration accept message or other NAS message.
[0138] For example, it is assumed that the deployment area indicates area "Z1" and the validity time indicates "January 2022." If the UE 3 is accessing the S-NSSAI1 from area "Z1" and the AMF 70 determines that the current date (e.g., "December 2021") does not exceed "January 2022," the AMF 70 processes the S-NSSAI1 and provides the S-NSSAI1 to the UE 3 in an authorization NSSAI in a registration acceptance message or other existing NAS message.
[0139] If AMF70 determines that UE3 is not accessing S-NSSAI1 from area "Z1" or the current date (e.g., "February 2022") is beyond "January 2022", AMF70 rejects S-NSSAI1. For example, if AMF70 rejects S-NSSAI1, AMF70 may send a registration rejection message including a rejected NSSAI including S-NSSAI1, or AMF70 may send a registration accept message including a rejected NSSAI including S-NSSAI1.
[0140] If the current date (e.g., "December 2021") does not exceed "January 2022", AMF 70 may determine that the validity time has not expired. If the current date (e.g., "February 2022") exceeds "January 2022", AMF 70 may determine that the validity time has expired.
[0141] 5. Once UE3 receives the registration approval message, UE3 may send a registration complete message to AMF70.
[0142] 6. UE3 may establish a PDU session related to S-NSSAI1. For example, after receiving a registration accept message including an authorized NSSAI including S-NSSAI1 in step 4 or after sending a registration complete message in step 5, UE3 may establish a PDU session related to S-NSSAI1. For example, in response to receiving a registration accept message including an authorized NSSAI including S-NSSAI1 in step 4 or after sending a registration complete message in step 5, UE3 may establish a PDU session related to S-NSSAI1.
[0143] 7. When UE3 moves out of the deployment area or the validity time for S-NSSAI1 expires or passes, at least one of UE3 and the network (e.g., AMF70) removes S-NSSAI1 from the allowed NSSAI locally or removes S-NSSAI1 from the allowed NSSAI with explicit NAS signaling (i.e., by sending an existing NAS message).
[0144] For example, if the UE 3 calculates a current location of the UE 3 and determines, based on the current location, that the UE 3 moves out of the deployment area, the UE 3 may remove the S-NSSAI1 from the allowed NSSAI.
[0145] For example, if UE3 determines, based on its current location, that UE3 is moving out of the deployment area, UE3 may initiate a procedure including sending an existing NAS message to remove S-NSSAI1 from the allowed NSSAI.
[0146] For example, the UE 3 may periodically transmit the current location of the UE 3 to the AMF 70. If the UE 3 receives a request to transmit the current location, the UE 3 may transmit the current location. In this case, the AMF 70 may determine whether the UE 3 moves out of the deployment area based on the current location. If the AMF 70 determines that the UE 3 moves out of the deployment area based on the current location, the AMF 70 may remove the S-NSSAI1 from the allowed NSSAI.
[0147] For example, if the AMF 70 determines that the UE 3 moves out of the deployment area based on the current location, the AMF 70 may initiate a procedure including sending an existing NAS message to remove the S-NSSAI1 from the authorized NSSAI. For example, the AMF may remove the S-NSSAI1 from the authorized NSSAI by updating the authorized NSSAI and send the updated authorized NSSAI to the UE 3.
[0148] If UE3 establishes a PDU session associated with S-NSSAI1, AMF70 initiates network requested PDU session release for roaming without roaming and roaming with local breakout procedure as described in section 4.3.4.2 of non-patent document 3.
[0149] For example, if AMF70 determines that UE3 has established a PDU session associated with S-NSSAI1, AMF70 may initiate a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0150] For example, if UE3 moves out of the deployment area and AMF70 determines that UE3 has established a PDU session associated with S-NSSAI1, AMF70 may initiate a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0151] For example, if AMF70 determines that the validity time for S-NSSAI1 has expired and UE3 has established a PDU session associated with S-NSSAI1, AMF70 may initiate a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0152] The AMF70 may determine that the UE3 has established a PDU session associated with the S-NSSAI1 by using local information in the AMF70 or by receiving information from another network node (e.g., an SMF or UDM).
[0153] For example, a communications device capable of AMF 70 may receive Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The communications device may transmit the S-NSSAI, the first information, and the second information.
[0154] For example, a User Equipment (UE) corresponding to UE3 may receive a first message. The first message may include a Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The UE may determine whether the S-NSSAI is valid based on the first information and the second information. If the S-NSSAI is valid, the UE may transmit a second message. The second message may include the S-NSSAI.
[0155] For example, a first communication device corresponding to AMF70 may receive information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device corresponding to UDM75. The first communication device may receive at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device. The first communication device may transmit at least one of information indicating that registration to a network slice related to the S-NSSAI is permitted and information indicating that registration to the network slice is not permitted to a communication terminal based on at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI.
[0156] For example, a communications terminal corresponding to UE 3 may send a request message for a network slice to a first communications device corresponding to AMF 70. The communications terminal may receive at least one of information related to a validity time for the network slice and information related to a validity area for the network slice from the first communications device.
[0157] According to the above, the above problems such as the inability of the latest 3GPP specifications to meet the above-mentioned new market demands can be solved.
[0158] <First variant of FIG. 1 in the first example of the first aspect> In one example, the AMF 70 may provide the configured NSSAI including the S-NSSAI along with at least one of the validity period of the S-NSSAI and the deployment area of the S-NSSAI in a configuration update command message or in any existing NAS message at any time. For example, the AMF 70 may initiate a UE configuration update procedure for access and mobility management related parameters as described in section 4.2.4.2 in 3GPP TS 215.230 to provide the configured NSSAI.
[0159] <First variant of FIG. 2 in the first example of the first aspect> In step 7, AMF70 may initiate a UE configuration update procedure for access and mobility management related parameters as described in section 4.2.4.2 in non-patent document 3 to remove S-NSSAI1 from the allowed NSSAI.
[0160] <Second variant of FIG. 2 in the first example of the first aspect> In step 7, the UE3 may initiate a registration procedure as described in section 4.2.2.2 in 3GPP TS 21.211 to remove the S-NSSAI1 from the allowed NSSAI.
[0161] <The third variant of FIG. 2 in the first example of the first aspect> If UE3 has established a PDU session associated with S-NSSAI1, then in step 7, UE3 may initiate a UE requested PDU session release for roaming without roaming and with local breakout procedure as described in section 4.3.4.2 in non-patent document 3. For example, in step 7, if UE3 determines based on local information at UE3 that UE3 has established a PDU session associated with S-NSSAI1, UE3 may initiate a UE requested PDU session release for roaming without roaming and with local breakout procedure to release the PDU session.
[0162] <The fourth variant of FIG. 2 in the first example of the first aspect> For example, by using the first example of the third aspect described below, if at least one of the deployment area and validity time for S-NSSAI1 is provisioned, in step 2-1, (R)AN5 may perform a validity check on the use of S-NSSAI1.
[0163] In step 2-1, when (R)AN5 receives an RRC message including S-NSSAI1, (R)AN5 checks whether UE3 is accessing S-NSSAI1 from the deployment area or within the validity time of S-NSSAI1, or with both factors if both are applicable. If (R)AN5 checks whether UE3 is accessing S-NSSAI1 from the deployment area, (R)AN5 may use cell information (e.g., cell ID) to check whether UE3 is inside the deployment area. If (R)AN5 checks whether UE3 is accessing S-NSSAI1 within the validity period, (R)AN5 may use network time provided by an NTP server to compare the validity time for S-NSSAI1.
[0164] For example, if (R)AN5 stores both the deployment area for S-NSSAI1 and the validity time for S-NSSAI1, (R)AN5 checks whether UE3 is accessing S-NSSAI1 from the deployment area within the validity time.
[0165] For example, if (R)AN5 stores both the deployment area for S-NSSAI1 and the validity time for S-NSSAI1, (R)AN5 checks whether UE3 is accessing S-NSSAI1 from the deployment area or whether UE3 is accessing S-NSSAI1 within the validity time.
[0166] For example, if (R)AN5 stores the deployment area for S-NSSAI1, (R)AN5 checks whether UE3 is accessing S-NSSAI1 from the deployment area.
[0167] For example, if (R)AN5 stores a validity time for S-NSSAI1, (R)AN5 checks whether UE3 accesses S-NSSAI1 within the validity time.
[0168] For example, assume that the deployment area indicates "Cell ID 1", the validity time indicates "January 2022", (R)AN5 recognizes that UE3 is in cell 1 identified by cell ID 1, and the current date is "December 2021". In this case, (R)AN5 checks whether UE3 is accessing S-NSSAI1 from cell 1 identified by "Cell ID 1" and whether the current date is not beyond "January 2022". In this case, (R)AN5 determines that UE3 is accessing S-NSSAI1 from the deployment area (i.e., cell 1 identified by "Cell ID 1") within the validity time.
[0169] For example, if (R)AN5 determines that UE3 is accessing S-NSSAI1 from the deployment area within the valid time, then in step 2-2, (R)AN5 sends an initial UE message.
[0170] For example, (R)AN5 may store information regarding where UE3 is located, or information indicating the cell in which UE3 is located.
[0171] For example, if the deployment area indicates information other than cell level information (e.g., cell ID), the (R)AN5 may convert the information indicated by the deployment area to cell level information. For example, the (R)AN5 may store the information to be converted to a cell ID. For example, the (R)AN5 may store a list including the cell ID and at least one combination of the TA, FB, and geographic area, etc.
[0172] For example, (R)AN5 may recognize the area or location in which the UE is located. For example, it is assumed that the deployment area indicates area "Z1" and the validity time indicates "January 2022". If (R)AN5 determines that UE3 is accessing S-NSSAI1 from area "Z1" and the current date (e.g., "December 2021") does not exceed "January 2022", then in step 2-2, (R)AN5 sends an initial UE message.
[0173] If (R)AN5 determines that UE3 is not accessing S-NSSAI1 from area "Z1" or that the current date (e.g., "February 2022") is beyond "January 2022", (R)AN5 may not send an initial UE message in step 2-2, or (R)AN5 may send an RRC rejection message to UE3.
[0174] If the current date (e.g., "December 2021") is not beyond "January 2022", (R)AN5 may determine that the validity time has not expired. If the current date (e.g., "February 2022") is beyond "January 2022", (R)AN5 may determine that the validity time has expired.
[0175] <Second aspect> To enable Home Public Land Mobile Network (HPLMN) operators to provide procedures for deploying network slices that are dedicated to handling temporary events in small geographic areas or for limited durations with minimal required signaling, HPLMN operators require mechanisms in 3GPP TS 2010-010112, 3GPP TS 2010-010112, and other 3GPP specifications that support the deployment of network slices to handle temporary events in limited geographic locations. Typically, operators deploy network slices uniformly in tracking or registration areas for longer durations.
[0176] A second aspect discloses a mechanism that allows an HPLMN operator to deploy network slices covering services deployed for a short period of time in a restricted area. More specifically, it discloses a procedure for supporting non-uniform deployment of network slices in a tracking area or registration area or for a limited period of time to support services required for a short period of time in a restricted geographic location by providing a temporary authorization NSSAI to the UE 3 during the registration procedure or by initiating a general UE configuration update procedure.
[0177] For example, the second aspect can solve the above problems, such as the inability of the latest 3GPP specifications to meet the above-mentioned new market demands.
[0178] <First Example of the Second Aspect> A first example of the second aspect discloses a procedure in which the AMF 70 transmits a temporary authorization NSSAI including an S-NSSAI with a validity time and a deployment area to the UE 3. The deployment area may be, for example, a list of cell IDs, a list of Frequency Bands (FBs), a list of combinations of cell IDs and FBs, a geographical area that maps to either a tracking area or a cell in which the S-NSSAI is deployed to provide a service. The deployment area may be a geographical area code according to GPS, an area defined by an address (e.g., city, town, village, administrative district), or a building (e.g., ABC Stadium, ABC Station, ABC Building). Such examples of deployment areas may be combined with each other for use. Outside this deployment area (e.g., tracking area or cell), the service related to the S-NSSAI is not deployed, accessible or available to the UE 3.
[0179] The validity time may be the period during which the S-NSSAI is valid for the service. After this period, the service will not be provided to the UE 3. The validity time may be the time during which the S-NSSAI is valid for the service or invalid for the service (e.g., valid at 9:00 AM, invalid at 10:00 AM, valid at 3:00 PM). The validity time may be the period or duration during which the S-NSSAI is valid for the service or invalid for the service.
[0180] When the UE3 receives the temporary authorization NSSAI, the UE3 stores the temporary authorization NSSAI, i.e., the UE3 stores the S-NSSAI together with the deployment area or the validity period, or both if both are provided. The validity period can be a period, a validity time, or a validity duration. When the UE3 gets a trigger to access a service related to the S-NSSAI, the UE3 checks whether the current cell of the UE3 belongs to the deployment area, or whether the current time is less than the validity time for the S-NSSAI, or both factors if both the deployment area and the validity time for the S-NSSAI are provided. If the S-NSSAI access criteria are met, the UE3 may establish a PDU session related to the S-NSSAI. If the current cell of the UE3 or the current location of the UE3 belongs to the deployment area, and the current time is less than the validity time of the S-NSSAI, or both factors are met if both the deployment area and the validity time of the S-NSSAI are provided, the UE3 may establish a PDU session related to the S-NSSAI.
[0181] The UE 3 may or may not include the temporary authorization S-NSSAI in the request NSSAI of the registration request message. The temporary authorization S-NSSAI may refer to the S-NSSAI included in the temporary authorization NSSAI.
[0182] When UE3 moves out of the deployment area, the validity period of the S-NSSAI expires, or the expiration time has passed, UE3 and the network may locally deactivate the PDU session or deactivate the PDU session through explicit NAS signaling (i.e., by sending an existing NAS message).
[0183] The first example of the second aspect is disclosed with reference to FIGS. 3 and 4. FIG. 3 shows the provisioning of a temporary permitted NSSAI for UE3, while FIG. 4 shows the behavior of UE3 and the network after the temporary permitted NSSAI is provided to UE3.
[0184] <Provisioning of a Temporary Permitted NSSAI for UE>[[]]END]] 1. UE3 sends a registration request message including a restricted slice support indicator and optionally S-NSSAI1 in the requested NSSAI to AMF70. The restricted slice support indicator indicates that UE3 supports the S-NSSAI in at least one of the deployment area and the validity period attributes. For example, the restricted slice support indicator may indicate that UE3 supports the S-NSSAI in at least one of the deployment area and the validity period attributes. The registration request message may be sent during an initial registration procedure, a mobility registration procedure, or a periodic registration procedure. The registration request message may include user identification information. The user identification information may indicate the identification information of UE3.
[0185] Steps 2-6 are the same as steps 2-6 in FIG. 1.
[0186] 7. If the UE 3 indicates a restricted slice support indicator in the registration request message in step 1, the AMF 70 sends the S-NSSAI1 to the UE 3 in the temporary authorization NSSAI in the registration accept message together with at least one of the deployment area and validity time, or both if both are applicable for the S-NSSAI1. Otherwise, the AMF 70 does not provide the S-NSSAI1 to the UE 3 in the temporary authorization NSSAI.
[0187] For example, if the deployment area and validity time are applicable to S-NSSAI1, AMF70 may send S-NSSAI1 together with at least one of the deployment area and validity time in the temporary grant NSSAI in the registration accept message.
[0188] For example, if a deployment area is applicable for S-NSSAI1, AMF70 may send S-NSSAI1 along with the deployment area in the temporary authorization NSSAI in the registration accept message.
[0189] For example, if a validity time is applicable for S-NSSAI1, AMF70 may send S-NSSAI1 along with the validity time in the temporary grant NSSAI in the registration accept message.
[0190] For example, the AMF 70 may store information for determining whether at least one of the deployment area and the validity time is applicable for the S-NSSAI for the UE 3.
[0191] For example, if UE3 does not indicate a restricted slice support indicator in the registration request message in step 1, AMF70 may send S-NSSAI1 in the registration accept message along with at least one of the deployment area and validity time in the temporary grant NSSAI.
[0192] In step 1, if the UE 3 provides the S-NSSAI1 in the Request NSSAI in the Registration Request message rather than providing a restricted slice support indicator, the AMF 70 provides the S-NSSAI1 in the Reject NSSAI in the Registration Accept message.
[0193] The AMF 70 may convert the received deployment area into a list of tracking areas (e.g., a list of TAIs) or a list of cell IDs. The AMF 70 may convert the received validity time into a validity time in another time format, e.g., a duration for the local time zone.
[0194] For example, the AMF 70 stores information that converts a received deployment area into a list of tracking areas (eg, a list of TAIs) or a list of cell IDs.
[0195] For example, AMF 70 may store information indicating that the location or position indicated by the deployment area includes cell 1 identified by TA1 or cell ID1, and convert the received deployment area into a list that includes TA1 or cell ID1.
[0196] For example, AMF 70 may store information indicating that the FB indicated by the deployment area is used in cell 1 identified by TA1 or cell ID1, and convert the received deployment area into a list including TA1 or cell ID1.
[0197] The restricted slice support indicator may indicate that the UE 3 supports receiving an S-NSSAI with at least one of a deployment area and a validity time in a temporary grant NSSAI.
[0198] The contents of the temporary authorization NSSAI may correspond to the contents of the subscribe NSSAI.
[0199] For example, if the subscribed NSSAI includes S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1, the temporary allowed NSSAI may include S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1.
[0200] For example, the AMF 70 may determine the contents of the temporary authorization NSSAI. For example, the AMF 70 may send a temporary authorization NSSAI for the S-NSSAI included in the request NSSAI in step 1. For example, it is assumed that in step 1, the AMF 70 receives a request NSSAI including S-NSSAI1, and in step 6, the AMF 70 receives a subscribe NSSAI including S-NSSAI1, a deployment area for S-NSSAI1, a validity time for S-NSSAI1, S-NSSAI2, a deployment area for S-NSSAI2, and a validity time for S-NSSAI2. In this case, the AMF 70 may send a temporary authorization NSSAI including S-NSSAI1, a deployment area for S-NSSAI1, and a validity time for S-NSSAI1.
[0201] The temporary permission NSSAI may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs, and a validity time for each of the one or more S-NSSAIs.
[0202] 8. Upon receiving the registration accept message, the UE 3 stores the temporary authorization NSSAI.
[0203] 9. The UE 3 may send a registration complete message. For example, the UE 3 may send a registration complete message after step 7 or 8.
[0204] <UE and network behavior after temporary authorization NSSAI is provided to the UE> 0. It is assumed that the UE3 and the 5GS have performed the registration procedure as shown in Figure 3 in the first example of the second aspect, which means that the UE3 may store the S-NSSAI1 in the temporary authorization NSSAI together with at least one of the deployment area and the validity time.
[0205] 1. When UE3 gets a trigger to access a service related to S-NSSAI1, UE3 checks whether a current cell of UE3 belongs to a deployment area, or whether a current time is less than a valid time for S-NSSAI1, or both factors if both the deployment area and the valid time for S-NSSAI are provided. For example, when UE3 gets a trigger to access a service related to S-NSSAI1, UE3 checks whether a current location of UE3 belongs to a deployment area, or whether a current time is less than a valid time for S-NSSAI1, or both factors if both the deployment area and the valid time for S-NSSAI are provided. For example, when an application related to S-NSSAI1 in UE3 is activated, UE3 gets a trigger to access a service related to S-NSSAI1.
[0206] "The current cell of UE3 or the current location of UE3 belongs to the deployment area" may be expressed as a first criterion. "The current time is less than the valid time" may be expressed as a second criterion. At least one of the first criterion and the second criterion may be expressed as an S-NSSAI access criterion.
[0207] For example, if the UE 3 stores the S-NSSAI1 in the temporary grant NSSAI along with both the deployment area and the validity time, the UE 3 may verify at least one of the first criterion and the second criterion.
[0208] For example, if the UE 3 stores the S-NSSAI1 in the temporary authorization NSSAI along with the deployment area, the UE 3 may verify the first criterion.
[0209] For example, if the UE 3 stores the S-NSSAI1 in the temporary grant NSSAI along with the validity time, the UE 3 may check the second criterion.
[0210] For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current cell of the UE 3 belongs to or is the same as the cell indicated by the deployment area. In this case, the UE may use a cell ID to check whether the current cell of the UE 3 belongs to or is the same as the cell indicated by the deployment area. For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current TA of the UE 3 belongs to or is the same as the TA indicated by the deployment area. In this case, the UE may use a TAI to check whether the current TA of the UE 3 belongs to or is the same as the TA indicated by the deployment area.
[0211] For example, when the UE 3 checks whether the first criterion is met, the UE 3 may check whether the current location of the UE 3 belongs to or is the same as the location indicated by the deployment area.
[0212] For example, UE3 may obtain information indicating the current cell or the current TA from another node, such as (R)AN5.
[0213] For example, the UE 3 may obtain the current location of the UE 3 by using a GPS.
[0214] For example, the UE 3 may convert the location information indicated by the deployment area into information indicating a cell, and the UE 3 checks whether the current cell of the UE 3 belongs to the cell indicated by the converted information. The information indicating a cell may be a cell ID. For example, the UE 3 may store the information converted into the information indicating a cell. For example, the UE 3 may store a list including a cell ID and at least one combination of a TA, an FB, and a geographic area, etc.
[0215] For example, when the UE 3 checks whether the second criterion is met, the UE 3 may check whether the current time or the current date is within the time or period indicated by the validity time.
[0216] 2. If the S-NSSAI access criteria for S-NSSAI1 in step 1 is met, the UE3 sends a PDU Session Establishment Request message including the S-NSSAI1 to initiate the UE requested PDU session establishment as described in section 4.3.2.2 of 3GPP TS 31.006.2010 (2010). If the UE3 checks whether the UE3 belongs to the deployed area, whether the current time is the validity time of S-NSSAI1, or whether the UE3 is related to both factors (deployed area or validity period of S-NSSAI1), the UE3 sends a PDU Session Establishment Request message including the S-NSSAI1 to initiate the UE requested PDU session establishment as described in section 4.3.2.2 of 3GPP TS 31.006.2010 (2010).
[0217] For example, if the UE 3 determines that at least one of the first criterion and the second criterion is met, the UE 3 may transmit a PDU session establishment request message.
[0218] For example, if the UE 3 determines that the first criterion is met, the UE 3 may send a PDU session establishment request message.
[0219] For example, if the UE 3 determines that the second criterion is met, the UE 3 may send a PDU session establishment request message.
[0220] For example, it is assumed that the deployment area indicates area "Z1" and the validity time indicates "January 2022". If the UE 3 determines that the current cell of the UE 3 (e.g., cell 1) or the current location of the UE 3 belongs to area "Z1" and the current date (e.g., "December 2021") does not exceed "January 2022", the UE 3 sends a PDU session establishment request message. For example, the UE 3 may store information indicating that the area "Z1" includes cell 1 or that the current location of the UE 3 belongs to area "Z1", and may use this information to confirm the first criterion.
[0221] For example, the UE 3 may convert the area "Z1" into information indicating a cell or location, and may determine whether the current cell or location belongs to or is the same as the cell or location indicated by the converted information. If the UE 3 determines that the current cell or location of the UE 3 belongs to or is the same as the cell or location indicated by the converted information and the current date (e.g., "December 2021") does not exceed "January 2022", the UE 3 sends a PDU session establishment request message.
[0222] If the UE3 determines that the current cell of the UE3 or the current location of the UE3 does not belong to the area "Z1" or that the current date (e.g., "February 2022") is beyond "January 2022", the UE3 does not send a PDU session establishment request message. If the current date (e.g., "December 2021") is not beyond "January 2022", the UE3 may determine that the validity time has not expired. If the current date (e.g., "February 2022") is beyond "January 2022", the UE3 may determine that the validity time has expired.
[0223] For example, a "determination that the current date is within the valid time" may be expressed as a "determination that the current date is less than the valid time" or a "determination that the current date is prior to the valid time."
[0224] The deployment area may indicate where S-NSSAI1 is valid or available. If the deployment area indicates area "Z1", the deployment area may mean that S-NSSAI1 is valid or available in area "Z1".
[0225] The validity time may indicate a time when the S-NSSAI1 is valid or available for use. If the validity time indicates "January 2022", the validity time may mean that the S-NSSAI1 is valid or available until January 2022.
[0226] If the deployment area indicates a list of FBs, the deployment area may indicate the FBs in which S-NSSAI1 is valid or available. If the deployment area indicates "FB1", the deployment area may mean that S-NSSAI1 is valid or available in "FB1". For example, UE3 checks whether UE3 tunes to "FB1", and if UE3 determines that UE3 is currently tuned to "FB1", UE3 sends a PDU session establishment request message.
[0227] If the deployment area indicates a list of cell ID and FB combinations, the deployment area may indicate the cell ID and FB combinations for which S-NSSAI1 is valid or available. If the deployment area indicates a combination of "Cell ID1" and "FB1", the deployment area may mean that S-NSSAI1 is valid or available in a cell that operates in "FB1" and is identified by "Cell ID1". For example, UE3 checks whether UE3 is located in a cell identified by "Cell ID1" and whether UE3 tunes to "FB1", and if UE3 determines that UE3 is located in a cell identified by "Cell ID1" and that UE3 is currently tuned to "FB1", UE3 sends a PDU session establishment request message.
[0228] 3. When UE3 moves out of the deployment area or the validity time for S-NSSAI1 expires or passes, at least one of UE3 and the network (e.g., AMF70) locally removes S-NSSAI1 from the temporary authorized NSSAI or removes S-NSSAI1 from the temporary authorized NSSAI with explicit NAS signaling (i.e., by sending an existing NAS message).
[0229] If UE3 establishes a PDU session associated with S-NSSAI1, AMF70 initiates network requested PDU session release for roaming without roaming and roaming with local breakout procedure as described in section 4.3.4.2 of non-patent document 3.
[0230] For example, if the UE 3 calculates a current location of the UE 3 and determines, based on the current location, that the UE 3 moves out of the deployment area, the UE 3 may remove the S-NSSAI1 from the temporary authorization NSSAI.
[0231] For example, if UE3 determines, based on its current location, that UE3 is moving out of the deployment area, UE3 may initiate a procedure including sending an existing NAS message to remove S-NSSAI1 from the temporary authorization NSSAI.
[0232] For example, the UE 3 may periodically transmit the current location of the UE 3 to the AMF 70. If the UE 3 receives a request to transmit the current location, the UE 3 may transmit the current location. In this case, the AMF 70 may determine whether the UE 3 moves out of the deployment area based on the current location. If the AMF 70 determines that the UE 3 moves out of the deployment area based on the current location, the AMF 70 may remove the S-NSSAI1 from the temporary authorization NSSAI.
[0233] For example, if the AMF 70 determines that the UE 3 moves out of the deployment area based on the current location, the AMF 70 may initiate a procedure including sending an existing NAS message to remove the S-NSSAI1 from the temporary authorization NSSAI. For example, the AMF may remove the S-NSSAI1 from the temporary authorization NSSAI by updating the temporary authorization NSSAI and send the updated temporary authorization NSSAI to the UE 3.
[0234] For example, if AMF70 determines that UE3 has established a PDU session associated with S-NSSAI1, AMF70 may initiate a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0235] For example, if UE3 moves out of the deployment area and AMF70 determines that UE3 has established a PDU session associated with S-NSSAI1, AMF70 may initiate a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0236] For example, if AMF70 determines that the validity time for S-NSSAI1 has expired and UE3 has established a PDU session associated with S-NSSAI1, AMF70 initiates a network requested PDU session release for no roaming and roaming with local breakout procedures.
[0237] The AMF70 may determine that the UE3 has established a PDU session associated with the S-NSSAI1 by using local information in the AMF70 or by receiving information from another network node (e.g., an SMF or UDM).
[0238] For example, a communications device capable of AMF 70 may receive Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The communications device may transmit the S-NSSAI, the first information, and the second information.
[0239] For example, a User Equipment (UE) corresponding to UE3 may receive a first message. The first message may include a Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The UE may determine whether the S-NSSAI is valid based on the first information and the second information. If the S-NSSAI is valid, the UE may transmit a second message. The second message may include the S-NSSAI.
[0240] For example, a first communication device corresponding to AMF70 may receive information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device corresponding to UDM75. The first communication device may receive at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device. The first communication device may transmit at least one of information indicating that registration in a network slice related to the S-NSSAI is permitted to a communication terminal based on at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI.
[0241] For example, a communications terminal corresponding to UE 3 sends a request message for a network slice to a first communications device corresponding to AMF 70. The communications terminal may receive information from the first communications device indicating that registration with the network is permitted, the information including at least one of information related to a validity time for the network slice and information related to a validity area for the network slice.
[0242] According to the above, the above problems such as the inability of the latest 3GPP specifications to meet the above-mentioned new market demands can be solved.
[0243] <First variant of FIG. 3 in the first example of the second aspect> In one example, the AMF 70 may provide a temporary authorized NSSAI including the S-NSSAI along with at least one of the validity period of the S-NSSAI and the deployment area of the S-NSSAI in a configuration update command message or in any existing NAS message at any time. For example, the AMF 70 may initiate a UE configuration update procedure for access and mobility management related parameters as described in section 4.2.4.2 in 3GPP TS 36.310 to provide a temporary authorized NSSAI.
[0244] <First variant of FIG. 4 in the first example of the second embodiment> In step 3, AMF70 may initiate a UE configuration update procedure for access and mobility management related parameters as described in section 4.2.4.2 in non-patent document 3 to remove S-NSSAI1 from the temporary authorized NSSAI.
[0245] <Second variant of FIG. 4 in the first example of the second aspect> In step 3, the UE3 may initiate a registration procedure as described in section 4.2.2.2 in 3GPP TS 21.211 to remove the S-NSSAI1 from the temporary authorized NSSAI.
[0246] <Third variant of FIG. 4 in the first example of the second aspect> When UE3 establishes a PDU session associated with S-NSSAI1, in step 3, UE3 may initiate the PDU session release of UE requests regarding roaming without roaming and local breakout procedures as described in item 4.3.4.2 in Non-Patent Document 3. For example, in step 7, when UE3 determines, based on the local information in UE3, that UE3 has established a PDU session associated with S-NSSAI1, UE3 may initiate the PDU session release of UE requests regarding roaming without roaming and local breakout procedures to release the PDU session.
[0247] <The third aspect> The third aspect discloses procedures for managing a network slice that may be available within a limited geographical area and for a limited period. More specifically, the third aspect discloses how network functions configure a network slice in AMF70 and (R)AN5 when the network slice provides services that are local, available for a limited period, or both. (R)AN5 may include (R)AN nodes such as NG-RAN nodes or gNBs.
[0248] For example, the third aspect can solve the above problems such as the fact that the latest 3GPP specifications cannot meet the above-mentioned new market requirements.
[0249] <The first example of the third aspect> The first example of the third aspect discloses the provisioning of network slice information for AMF70, (R)AN5, and UE3 when the network slice is conditionally available in a specific geographical area or for a limited period.
[0250] <Provisioning of network slice information for AMF:> A first example of the third aspect discloses that a network function (e.g., UDM 75 or other NF) that manages a network slice to provide services in a specific geographical area or during a restricted period transmits an existing message or a new message including the configured S-NSSAI, the deployment area for the S-NSSAI or the validity period for the S-NSSAI, or both the deployment area and the validity period to the AMF 70.
[0251] <Provisioning of network slice information to the (R)AN:> The AMF 70 transmits an existing NGAP message or a new NGAP message including the S-NSSAI, the deployment area or the valid time, or both the deployment area and the valid time to the (R)AN 5.
[0252] <Provisioning of network slice information to the UE:> Upon receiving an NGAP message (e.g., the first NGAP message or the fourth NGAP message described below) including the S-NSSAI, the deployment area or the valid time, or both the deployment area and the valid time, the (R)AN 5 converts the received deployment area into corresponding cells and stores S-NSSAI availability information for each cell together with the valid time. The (R)AN 5 broadcasts information related to the support of the S-NSSAI based on the stored S-NSSAI availability information. The S-NSSAI availability information may indicate whether the S-NSSAI is available.
[0253] When a validity period is provided, the (R)AN 5 broadcasts information related to the support of the S-NSSAI in the cells mapped from the deployment area. When a validity period is provided, the (R)AN 5 broadcasts information related to the support of the S-NSSAI at the location mapped from the deployment area. When a validity period is provided, the (R)AN 5 broadcasts information related to the support of the S-NSSAI during the validity period of the S-NSSAI.
[0254] Each of the three detailed procedures of the third embodiment is described below.
[0255] 1. A network function (NF) 77 (e.g., UDM 75 or other NF) that manages network slices to provide services in a specific geographical area or for a limited time period sends a first message to the AMF 70 including a configured S-NSSAI1, a deployment area for the S-NSSAI1 or a validity period for the S-NSSAI1, or both a deployment area and a validity period. The S-NSSAI1 may be associated with at least one of a deployment area and a validity period. The deployment area may be, for example, a list of cell IDs, a list of Frequency Bands (FBs), a list of cell ID and FB combinations, a geographical area that is mapped to either a tracking area or a cell in which the S-NSSAI1 is deployed to provide services.
[0256] Upon receiving the first message, the AMF 70 maps the deployment area to a tracking area and identifies the (R)AN 5 that manages the tracking area.
[0257] For example, the AMF 70 may store location information indicating the location of the tracking area, and the AMF 70 may map the deployment area to the tracking area based on the location information and the location identified by the deployment area.
[0258] For example, if AMF 70 stores information indicating that tracking area 1 includes cell 1 identified by cell ID 1, and a received deployment area indicates cell ID 1, AMF 70 may map the deployment area to tracking area 1.
[0259] For example, if AMF 70 stores information indicating that tracking area 1 operates in FB1 and a received deployment area indicates FB1, AMF 70 may map the deployment area to tracking area 1.
[0260] For example, if AMF 70 stores location "Z1" as location information for tracking area 1 and the received deployment area indicates location "Z1", AMF 70 may map the deployment area to tracking area 1.
[0261] For example, if the received deployment area indicates tracking area 1, AMF 70 may map the deployment area to information related to tracking area 1 stored in AMF 70.
[0262] For example, AMF 70 stores information indicating the tracking area managed by (R)AN 5, and AMF 70 can identify (R)AN 5 that manages the tracking area based on the information.
[0263] The first message may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0264] The NF77 may determine the content of the first message based on at least one of a local configuration in the UDM75, an operator's policy, and an S-NSSAI to which the UE3 subscribes.
[0265] For example, if the NF 77 stores information indicating that the UE 3 subscribes to the S-NSSAI 1, the UDM 75 may generate a subscribe NSSAI for the S-NSSAI 1.
[0266] The NF77 may periodically transmit the first message. When the NF77 receives a trigger to transmit the first message, the NF77 may transmit the first message. When the NF77 determines that a relationship between the S-NSSAI and at least one of the deployment area and the validity time is changed, the NF77 may transmit the first message.
[0267] 2. There are two ways for AMF 70 to send network slice information to (R)AN 5, e.g., option 1 and option 2. The network slice information may include an S-NSSAI1 and at least one of a deployment area and a validity period. The network slice information may include an S-NSSAI1 and at least one of a deployment area for the S-NSSAI1 and a validity period for the S-NSSAI1. The network slice information may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0268] <Option 1:> 2-1-1. AMF70 sends a first NGAP message (e.g., an existing NGAP message or a new NGAP message) including S-NSSAI1, a deployment area or a validity time, or both a deployment area and a validity time to (R)AN5.
[0269] The first NGAP message may include the S-NSSAI1 along with at least one of a deployment area for the S-NSSAI1 and a validity time for the S-NSSAI1.
[0270] The first NGAP message may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0271] The content of the first NGAP message may correspond to the content of the first message. For example, if the first message includes S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1, the first NGAP message may include S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1.
[0272] For example, the AMF 70 may determine the content of the first NGAP message. For example, the AMF 70 may include an S-NSSAI that the AMF 70 can process in the first NGAP message.
[0273] In one example, the first NGAP message may be an AMF CONFIGURATION UPDATE message.
[0274] In another example, when AMF 70 receives the first message in step 1, AMF 70 transmits the first NGAP message to (R)AN 5. In another example, when AMF 70 is triggered to transmit the first NGAP message based on a local configuration of AMF 70 or based on an operator's policy, AMF 70 transmits the first NGAP message to (R)AN 5. In another example, AMF 70 transmits the first NGAP message to (R)AN 5 periodically.
[0275] In another example, if AMF 70 knows in advance through the NGAP interface management procedure that (R)AN5 cannot process the associated information, AMF 70 does not transmit the associated information of S-NSSAI1, such as the deployment area or validity time, or both the deployment area and validity time, to (R)AN5 in the first NGAP message. For example, AMF 70 may know that (R)AN5 cannot process the associated information by exchanging capability information regarding (R)AN5 between AMF 70 and (R)AN5 through the NGAP interface management procedure.
[0276] 2-1-2. (R)AN5 receives the first NGAP message. (R)AN5 stores S-NSSAI1 and at least one of the deployment area for S-NSSAI1 and the validity time for S-NSSAI1, and maps them to cells managed by (R)AN5.
[0277] (R)AN5 then sends a second NGAP message (e.g., an existing NGAP message or a new NGAP message) to AMF70 to confirm that (R)AN5 has successfully received the network slice information.
[0278] In one example, the second NGAP message may be an AMF CONFIGURATION ACKNOLEDGE message.
[0279] For example, (R)AN5 may store location information indicating the location of a cell managed by (R)AN5, and (R)AN5 may map S-NSSAI1 and at least one of the deployment area and validity time to the cell based on the location information and the location indicated by the deployment area.
[0280] For example, if (R)AN5 stores cell ID1 that identifies cell 1 managed by (R)AN5, and the received deployment area indicates cell ID1, (R)AN5 may map S-NSSAI1 and at least one of the deployment area and validity time to cell 1.
[0281] For example, if (R)AN5 manages cell 1, (R)AN5 stores information indicating that cell 1 is operating on FB1, and the received deployment area indicates FB1, (R)AN5 may map S-NSSAI1 and at least one of the deployment area and validity time to cell 1.
[0282] For example, if (R)AN5 stores location "Z1" as location information of cell 1 managed by (R)AN5, and the received deployment area indicates location "Z1", (R)AN5 may map S-NSSAI1 and at least one of the deployment area and validity time to cell 1.
[0283] <Option 2:> 2-2-1. (R)AN5 sends a third NGAP message including a restricted slice support indicator to AMF70 as part of the NGAP interface management procedure. The restricted slice support indicator may indicate that (R)AN5 supports S-NSSAI with at least one of the attributes of deployment area and validity time. For example, the restricted slice support indicator may indicate that (R)AN5 supports S-NSSAI with at least one of the attributes of deployment area and validity time. The restricted slice support indicator may indicate that (R)AN5 supports receiving S-NSSAI with at least one of the attributes of deployment area and validity time as mentioned in step 2-2-2.
[0284] In one example, the third NGAP message may be a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.
[0285] 2-2-2. AMF70 sends a fourth NGAP message (e.g., an existing NGAP message or a new NGAP message) to (R)AN5 including S-NSSAI1, a deployment area for S-NSSAI1 or a validity time for S-NSSAI1, or both the deployment area and validity time.
[0286] The fourth NGAP message may include S-NSSAI1 along with at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1.
[0287] The fourth NGAP message may include one or more S-NSSAIs, a deployment area for each of the one or more S-NSSAIs and a validity time for each of the one or more S-NSSAIs.
[0288] The content of the fourth NGAP message may correspond to the content of the first message. For example, if the first message includes S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1, the fourth NGAP message may include S-NSSAI1 and at least one of a deployment area for S-NSSAI1 and a validity time for S-NSSAI1.
[0289] For example, the AMF 70 may determine the content of the fourth NGAP message. For example, the AMF 70 may include an S-NSSAI that the AMF 70 can process in the fourth NGAP message.
[0290] For example, if AMF 70 receives the first message in step 1 or the third NGAP message in step 2-2-1, AMF 70 may send a fourth NGAP message.
[0291] Upon receiving the fourth NGAP message, (R)AN5 stores the S-NSSAI1 and at least one of the deployment area and validity time, and maps them to cells managed by (R)AN5. For example, (R)AN5 may map the S-NSSAI1 and at least one of the deployment area and validity time to cells similar to the process in step 2-1-2.
[0292] In one example, the fourth NGAP message may be a NG SETUP RESPONSE message or a RAN CONFIGURATION UPDATE ACKNOLEDGE message.
[0293] In another example, if (R)AN5 does not indicate a restricted slice support indicator in the third NGAP message, AMF70 does not send the fourth NGAP message to (R)AN5.
[0294] In another example, if (R)AN5 does not indicate a restricted slice support indicator in the third NGAP message, AMF70 may send a fourth NGAP message to (R)AN5.
[0295] 3. A cell connected to (R)AN5 broadcasts support for S-NSSAI1 if the conditions match. In this example, the cell covers the deployment area, but the validity time does not match, so the cell does not broadcast support for S-NSSAI1.
[0296] For example, it is assumed that the current time is "November 2021", the deployment area for S-NSSAI1 indicates cell ID1 identifying cell 1, the validity time for S-NSSAI1 indicates "December 2021 to January 2022", and (R)AN5 (e.g., an (R)AN node, an NG-RAN node, or a gNB) manages cell 1.
[0297] That is, the deployment area indicates that S-NSSAI1 is valid or available in cell 1, and the validity time indicates that S-NSSAI1 is valid or available during the period from December 2021 to January 2022.
[0298] In this example, (R)AN5 determines that cell 1 belongs to or is the same as the cell indicated by the deployment area. In other words, (R)AN5 determines that cell 1 covers the deployment area. (R)AN5 determines that the current time (e.g., November 2021) is not within the valid time. Then, (R)AN5 does not broadcast system information including S-NSSAI1 in cell 1. Or, (R)AN5 broadcasts system information including information indicating that S-NSSAI1 is not available in cell 1.
[0299] For example, if UE3 receives system information including information indicating that S-NSSAI1 is not available, UE3 does not include S-NSSAI1 in the request NSSAI of the registration request message when UE3 initiates the registration procedure.
[0300] For example, if UE3 receives system information including information indicating that S-NSSAI1 is not available, UE3 does not initiate a PDU session establishment procedure for S-NSSAI1.
[0301] 4. As time passes, the effective time becomes effective (or valid). For example, the current time is "December 1, 2021."
[0302] 5. Since both the validity time and deployment area match, the cell broadcasts its support for S-NSSAI1.
[0303] For example, it is assumed that the current time is "December 1, 2021", the deployment area for S-NSSAI1 indicates cell ID1 identifying cell 1, the validity time for S-NSSAI1 indicates "December 2021 to January 2022", and (R)AN5 (e.g., an (R)AN node, an NG-RAN node, or a gNB) manages cell 1. In this example, (R)AN5 determines that cell 1 belongs to or is the same as the cell indicated by the deployment area. (R)AN5 determines that the current time (e.g., December 1, 2021) is within the validity time (or (R)AN5 determines that the validity time has not expired). Then, (R)AN5 broadcasts system information including S-NSSAI1 in cell 1. Or, (R)AN5 broadcasts system information including information indicating that S-NSSAI1 is available in cell 1.
[0304] For example, if UE3 receives system information including information indicating that S-NSSAI1 is available, UE3 includes S-NSSAI1 in the request NSSAI of the registration request message when UE3 initiates the registration procedure.
[0305] For example, if UE3 receives system information including information indicating that S-NSSAI1 is available, UE3 initiates a PDU session establishment procedure for S-NSSAI1.
[0306] 6. As time passes, the validity period becomes ineffective (or invalid). For example, the current period is "February 2022."
[0307] 7. Although the cell covers the deployment area, the cell does not broadcast support for S-NSSAI1 because the validity time does not match.
[0308] For example, it is assumed that the current time is "February 2022", the deployment area for S-NSSAI1 indicates cell ID1 identifying cell 1, the validity time for S-NSSAI1 indicates "December 2021 to January 2022", and (R)AN5 (e.g., an (R)AN node, an NG-RAN node, or a gNB) manages cell 1. In this example, (R)AN5 determines that cell 1 belongs to or is the same as the cell indicated by the deployment area. (R)AN5 determines that the current time (e.g., February 2022) is not within the validity time (or (R)AN5 determines that the validity time has expired). Then, (R)AN5 does not broadcast system information including S-NSSAI1 in cell 1. Or, (R)AN5 broadcasts system information including information indicating that S-NSSAI1 is not available in cell 1.
[0309] For example, if UE3 receives system information including information indicating that S-NSSAI1 is not available, UE3 does not include S-NSSAI1 in the request NSSAI of the registration request message when UE3 initiates the registration procedure.
[0310] For example, if UE3 receives system information including information indicating that S-NSSAI1 is not available, UE3 does not initiate a PDU session establishment procedure for S-NSSAI1.
[0311] For example, a communications device capable of (R)AN5 may receive Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid. The communications device may determine whether the S-NSSAI is valid based on the first information and the second information. The communications device may transmit first system information if the S-NSSAI is valid. The first system information may include information indicating that the S-NSSAI is valid.
[0312] For example, a first communication device corresponding to AMF70 may receive at least one of information related to a validity time for a network slice and information related to a validity area for the network slice from a second communication device corresponding to NF77. The first communication device may transmit a first message related to at least one of information related to a validity time for a network slice and information related to a validity area for the network slice to a first base station that may correspond to (R)AN5. The first communication device may receive a second message from the first base station for verifying reception of the first message by the first radio station. The first communication device may transmit at least one of information related to the validity area and information related to the validity time to a communication terminal that may correspond to UE3. The first communication device may transmit information related to the validity area and the validity time to a communication terminal that may correspond to UE3.
[0313] For example, a first communication device corresponding to AMF70 may receive at least one of information related to a validity time for a network slice and information related to a validity area for the network slice from a second communication device corresponding to NF77. The first communication device may receive a first message from a first base station corresponding to (R)AN5 indicating that the first base station manages the network slice with at least one of the validity area and the validity time. The first communication device may transmit a second message related to at least one of the validity time for the network slice and the validity area for the network slice to the first base station. The first communication device may transmit at least one of information related to the validity area and information on the validity time to a communication terminal corresponding to UE3. The first communication device may transmit information related to the validity area and the validity time to a communication terminal corresponding to UE3.
[0314] According to the above, the above problems such as the inability of the latest 3GPP specifications to meet the above-mentioned new market demands can be solved.
[0315] <System Overview> FIG. 6 illustrates diagrammatically a mobile (cellular or wireless) telecommunications system 1 to which the above aspects are applicable.
[0316] The telecommunication system 1 represents a system overview capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices" 3) communicating with other UEs 3 or service servers in a data network 20 via respective (R)AN nodes 5 and a core network 7.
[0317] 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) technologies as defined by the Institute of Electrical and Electronics Engineers (IEEE).
[0318] The (R)AN node 5 may be separated into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU), which in some aspects may be connected together to build the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, and the above units are referred to as O-RU, O-DU, and O-CU, respectively.
[0319] The (R)AN node 5 may be separated into a control plane function and a user plane function. Furthermore, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, with user traffic in each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This separated architecture may be referred to as "dual connectivity" or "multi-connectivity."
[0320] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support satellite and terrestrial access.
[0321] In addition, the (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).
[0322] The core network 7 may include logical nodes (or "functions") that support communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes control plane functions and user plane functions, among other functions. Each function in a logical node may be considered a network function. A network function may be provided to another node by adapting a Service Based Architecture (SBA).
[0323] By applying network virtualization technologies such as those defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed as distributed, redundant, stateless, and scalable, providing services from several locations and providing several execution instances at each location.
[0324] The core network 7 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0325] As is known, when the UE 3 is moving around the geographic area covered by the telecommunication system 1, the UE 3 may move in and out of areas (i.e., radio cells) served by the (R)AN nodes 5. To keep track of the UE 3 and facilitate movement between the various (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 connected to the core network 7. In some core networks, a mobility management entity (MME) or mobility management node for Beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.
[0326] The core network 7 also includes, among others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, a Network Data Analytics Function (NWDAF) 76, and a Network Function (NF) 77. When a UE 3 roams into a visited Public Land Mobile Network (VPLMN), the home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75, and at least some of the functionality of the SMF 71, UPF 72, and PCF 73 to the roaming-out UE 3.
[0327] The UE 3 and the respective serving (R)AN node 5 are connected via an appropriate air interface (e.g., the so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node 5 to (R)AN node interfaces (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via appropriate interfaces (such as the so-called "N2" / "N3" interfaces and / or the like). From the core network 7, a connection is also provided to a data network 20. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of the PLMN. If the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by that data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.
[0328] The "Uu" interface may include a control plane of the Uu interface and a user plane of the Uu interface.
[0329] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a hierarchical structure with SDAP, PDCP, RLC and MAC sub-layers over physical connections.
[0330] 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 sub-layers over the physical connections.
[0331] For example, the following messages are communicated in the RRC layer to support AS signaling:
[0332] - RRC SETUP REQUEST message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC SETUP REQUEST message: --establishmentCause and ue-Identity. The ue-Identity may have the value of ng-5G-S-TMSI-Part1 or a random value.
[0333] - RRC SETUP message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC SETUP message: --Master cell group (masterCellGroup) and radio bearer config (radioBearerConfig)
[0334] - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Complete message: --guami type, iab node indication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registered AMF, selectedPLMN-Identity
[0335] The UE 3 and the AMF 70 are connected via a suitable interface (e.g., a so-called N1 interface and / or the like). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface can be established in 3GPP access and non-3GPP access. For example, the following messages are communicated in the N1 interface:
[0336] - Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the Registration Request message: --5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability IDThe requested NB-N1 mode DRX parameters include: Requested NB-N1 mode Routing Information Requested ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.
[0337] - Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the Registration Accept Message: --5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 valueThe following are the received 5G-S-TMSI status information: T3324 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI.
[0338] - Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the registration complete message: --SOR transparent container.
[0339] -Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the Authentication Request message: --ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge), and EAP message.
[0340] -Authentication Response Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the authentication response message: --Authentication response message identity, Authentication response parameter, and EAP message.
[0341] -Authentication Result Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Authentication Result message: --ngKSI, EAP message, and ABBA.
[0342] -Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Authentication Failure Message: --Authentication failure message identity, 5GMM cause, and Authentication failure parameter.
[0343] -Authentication Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Authentication Rejection message: --EAP message.
[0344] - Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Service Request message: --ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.
[0345] - Service Authorization Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Service Authorization Message: --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.
[0346] - Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Service Rejection message: --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.
[0347] -Configuration Update Command Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the Configuration Update Command message: --Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion The following messages are displayed: 5GS registration result, 5GS registration indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI.
[0348] -Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be present together in the configuration update complete message:
[0349] --Configuration update complete message identity.
[0350] <User equipment (UE)> FIG. 7 is a block diagram showing the main components of a UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from a connection node via one or more antennas 32. In addition, the 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 the figure, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 according to the software stored in the memory 36. The software includes, among other things, an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes such as the (R)AN node 5 and the AMF 70. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE 3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. In case of multiple USIMs 35, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.
[0351] The UE 3 may, for example, support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0352] UE3 may be, for example, an item of production or manufacturing equipment and / or an item of energy-related machinery (e.g., equipment or machines such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metal processing machines, manipulators, robots and / or application systems thereof, tools, moulds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machines, printing machines and / or related machines, paper converting machines, chemical machinery, mining machinery and / or construction machinery and / or related equipment, agricultural, forestry and / or fishing machinery and / or implements, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, fittings, and / or application systems for any of the foregoing equipment or machines).
[0353] UE 3 may be, for example, an item of transportation equipment (e.g., vehicles, automobiles, motorbikes, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).
[0354] UE 3 may be, for example, an item of information and communications equipment (eg, information and communications equipment such as electronic computers and related equipment, communications and related equipment, electronic components, etc.).
[0355] The UE3 may be, for example, a refrigeration machine, a refrigeration machine application product, an item of commercial and / or service industry equipment, a vending machine, an automated service machine, an office machine or equipment, consumer electronic devices and appliances (e.g., consumer electronic appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners, etc.).
[0356] The UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, a power application device, etc.).
[0357] UE3 may be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a tester, or a surveying or detecting device (e.g., a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, or other surveying or detecting device), a watch or clock, laboratory equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, or the like.
[0358] UE 3 may be, for example, a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device (eg, a personal computer, electrical measurement machine)).
[0359] The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the "Internet of Things" (IoT).
[0360] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, allowing them to collect and exchange data with each other and with other communicating devices. IoT devices may comprise automated machines that follow software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or stopped for long periods of time. IoT devices may be implemented as part of a (generally) stationary apparatus. IoT devices may also be incorporated into non-stationary apparatus (e.g., vehicles) or attached to animals or people being monitored / tracked.
[0361] It will be understood that IoT technology may be implemented on any communication device that can connect to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.
[0362] It will be appreciated that an IoT device is sometimes also referred to as a Machine-Type Communication (MTC) device or a Machine-to-Machine (M2M) communication device, or a Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.
[0363] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).
[0364] The UE3 may be a car, a connected car, an autonomous vehicle, a vehicular device, a motorcycle, or a Vehicle to Everything (V2X) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-person communication module, and a vehicle-to-network communication module).
[0365] <(R)AN node> FIG. 8 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 station for Beyond 5G, base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 operable to transmit signals to and receive signals from an attached UE 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 downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communication control module 552 having at least a transceiver control module 5521.
[0366] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72, either directly or indirectly. The signaling may include, for example, properly formatted signaling messages regarding the radio connection and connection with the core network 7 for a specific UE 3, particularly regarding connection establishment and maintenance, such as RRC connection establishment messages and other RRC messages, NG Application Protocol (NGAP) messages (i.e., messages at the N2 reference point), Xn application protocol (XnAP) messages (i.e., messages at the Xn reference point), etc. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).
[0367] The controller 54 is also configured (by software or hardware) to process related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented.
[0368] (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).
[0369] <System overview of (R)AN node 5 based on the O-RAN architecture> FIG. 9 schematically shows (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.
[0370] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is separated into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Centralized Unit (CU) 62. In some aspects, the units may be combined. For example, the RU 60 may be combined / combined with the DU 61 as a combined / combined unit, and the DU 61 may be combined / combined with the CU 62 as another combined / combined unit. Any functionality in the description of a unit (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the combined / combined unit above. Furthermore, the CU 62 may be separated into two functional units, such as a CU Control plane (CP) and a CU User plane (UP). The CU CP has a control plane function in the (R)AN node 5. The CU UP has a user plane function in the (R)AN node 5. Each CU CP is connected to a CU UP via a suitable interface (such as a so-called "E1" interface and / or the like).
[0371] The UE 3 and the respective serving RU 60 are connected via a suitable air interface (e.g., a so-called "Uu" interface and / or the like). Each RU 60 is connected to a DU 61 via a suitable interface (such as a so-called "fronthaul", "open fronthaul", "F1" interface and / or the like). Each DU 61 is connected to a CU 62 via a suitable interface (such as a so-called "midhaul", "open midhaul", "E2" interface and / or the like). Each CU 62 is also connected to a node in the core network 7 (such as a so-called core network node) via a suitable interface (such as a so-called "backhaul", "open backhaul", "N2" / "N3" interface and / or the like). In addition, the user plane part of the DU 61 may also be connected to the core network node 7 via a suitable interface (such as a so-called "N3" interface and / or the like).
[0372] Depending on the functionality split between the RU 60, DU 61, and CU 62, each unit provides a part of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality supporting the MAC and RLC layers, and the CU 62 may provide functionality supporting the PDCP, SDAP, and RRC layers.
[0373] <Radio Unit (RU)> FIG. 10 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 station for Beyond 5G, base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from an attached UE 3 via one or more antennas 602, and to transmit and receive signals to and from other network nodes or parts via a network interface 603 (directly or indirectly). A controller 604 controls the operation of the RU 60 according to software stored in a memory 605. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521.
[0374] The communication control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling between (e.g., directly or indirectly) the RU 60 and other nodes or parts, such as the UE 3, another RU 60, and the DU 61. The signaling may include, for example, appropriately formatted signaling messages related to the radio connection and connectivity with the RU 60 (for a particular UE 3), in particular the MAC and RLC layers.
[0375] When implemented, the controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.
[0376] The RU 60 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0377] As described above, the RU 60 may be integrated / combined with the DU 61 as an integrated / combined unit. Any function described for the RU 60 may be implemented in the integrated / combined unit.
[0378] <Distributed Unit (DU)> FIG. 11 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU portion of a base station (eNB in LTE, gNB in 5G, base station for Beyond 5G, base station for 6G). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 according to software stored in memory 614. For example, the software may be pre-installed in memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.
[0379] The DU 61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0380] As mentioned above, the RU 60 may be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any functionality in the description of the DU 61 may be implemented in one of the integrated / combined units.
[0381] <Centralized Unit (CU)> FIG. 12 is a block diagram illustrating the main components of an exemplary CU 62, e.g., a CU portion of a base station (eNB in LTE, gNB in 5G, base station for Beyond 5G, base station for 6G). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 according to software stored in a memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.
[0382] The CU 62 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0383] As described above, the CU 62 may be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description of the CU 62 may be implemented in the integrated / combined unit.
[0384] <amf> 13 is a block diagram illustrating the main components of the AMF 70. As shown, the device includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 according to software stored in a memory 704. For example, the software may be pre-installed in the memory 704 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signaling between the AMF 70 and the UE 3 (e.g., via (R)AN node 5) and other nodes, such as other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE 3).
[0385] The AMF 70 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0386] <udm> 14 is a block diagram illustrating the main components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 according to software stored in a memory 754. For example, the software may be pre-installed in the memory 754 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to mobility management procedures (for the UE 3).
[0387] The UDM 75 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
[0388] <nf> FIG. 15 is a block diagram illustrating the main components of the NF 77. As shown, the device includes a transceiver circuit 771 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the NF 77 according to software stored in a memory 774. For example, the software may be pre-installed in the memory 774 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7741 and a communication control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / sending / receiving) signaling between the NF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) relating to mobility management procedures (for the UE 3).
[0389] The NF77 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NF77 may be one of the NFs defined in Section 4.2.2 of 3GPP TS 2011-01-13.
[0390] All or part of the exemplary aspects of the above disclosure may be described as follows, but are not limited to the following.
[0391] 4.2.2.2.2 General overview of registration
[0392] Figure 4.2.2.2.2-1: Registration procedure (see Figure 16)
[0393] 1. UE to (R)AN: AN message (AN parameters, Registration Request (registration type, SUCI or 5G-GUTI or PEI, [Last visited TAI (if available)], Security parameters, [Requested NSSAI], [Requested NSSAI mapping], [Default configured NSSAI indication], [UE Radio Capability Update], [UE MM Core Network Capabilities], [PDU Session State], [List of PDU Sessions to be activated], [Subsequent Request], [MICO Mode Preference], [Requested Active Time], [Requested DRX parameters for E-UTRA and NR], [Requested DRX parameters for NB-IoT], [Extended Idle Mode DRX parameters], [Requested LADN Information] DNN or indicator], [NAS Message Container], [Support for restriction of use of enhanced coverage], [Preferred network behavior], [UE paging capability information], [UE Policy Container (list of PSI, indication of UE support for ANDSP, and operating system identifier)], and [UE Radio Capability ID], [Release Request Indication], [Paging Restriction Information], PEI, [NSSRG Handling Support Indication], [PLMN with Disaster State] Restricted Slice Support Indicator)].
[0394] NOTE 1: The UE policy container and its usage are defined in TS 23.503
[20] .
[0395] In case of NG-RAN, the AN parameters include, for example, 5G-S-TMSI or GUAMI, selected PLMN ID (or PLMN ID and NID see clause 5.30 of TS 23.501 [2]), and NSSAI information, and also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the NSSAI information as part of the AN parameters depends on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter as specified in clause 5.15.9 of TS 23.501 [2].
[0396] The restricted slice support indicator indicates that the UE 3 supports S-NSSAI for at least one of the attributes of deployment area and validity time. For example, the restricted slice support indicator may indicate that the UE 3 supports S-NSSAI for at least one of the attributes of deployment area and validity time.
[0397] If the UE is an IAB node accessing 5GS, the AN parameter shall also include an IAB indication.
[0398] The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in RM-REGISTERED state and initiates the registration procedure for mobility or because the UE needs to update its capabilities or protocol parameters or needs to request a change in the set of network slices that the UE is allowed to use), a periodic registration update (i.e., the UE is in RM-REGISTERED state and initiates the registration procedure due to expiration of the periodic registration update timer see section 4.2.2.2.1), an emergency registration (i.e., the UE is in a limited service state), or a disaster roaming registration.
[0399] If the UE is using E-UTRA, the UE indicates in the RRC connection establishment signaling associated with the registration request that the UE supports CIoT 5GS optimization related to AMF selection.
[0400] If the UE is performing initial registration or disaster roaming registration, the UE shall indicate its UE identity in the registration request message as follows, which are listed in descending order of priority for registration on a PLMN:
[0401] i) If the UE has a valid EPS GUTI, the 5G-GUTI is mapped from the EPS GUTI.
[0402] ii) If available, the native 5G-GUTI assigned by the PLMN to which the UE is attempting to register;
[0403] iii) If available, the native 5G-GUTI assigned by the equivalent PLMN to the PLMN to which the UE is attempting to register;
[0404] iv) Native 5G-GUTI allocated by any other PLMN, if available.
[0405] NOTE 2: This could also be a 5G-GUTI allocated via another access type.
[0406] v) In all other cases, the UE shall include its SUCI in the registration request as specified in TS 33.501
[15] .
[0407] If the UE is registering with an SNPN, when the UE is performing initial registration, the UE shall indicate its UE identity in the registration request message as follows, listed in descending order of priority:
[0408] i) If available, a native 5G-GUTI assigned by the same SNPN to which the UE is attempting to register;
[0409] ii) If available, the native 5G-GUTI assigned by any other SNPN together with the NID of the SNPN that assigned the 5G-GUTI;
[0410] iii) In all other cases, the UE shall include its SUCI in the registration request as specified in TS 33.501
[15] .
[0411] If the UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as an additional GUTI. If multiple native 5G-GUTIs are available, the UE shall select a 5G-GUTI in descending order of priority among items (ii) to (iv) in the above list.
[0412] If the UE is sending a Registration Request message as an initial NAS message, the UE has a valid 5G NAS security context, and the UE needs to send non-cleartext IEs, the NAS message container shall be included (see clause 4.4.6 in TS 24.501
[25] ). If the UE does not need to send non-cleartext IEs, the UE shall send the Registration Request message without including a NAS message container.
[0413] If the UE does not have a valid 5G NAS security context, the UE shall send the Registration Request message without including a NAS message container. The UE shall include the entire Registration Request message (i.e. including the cleartext and non-cleartext IEs) in the NAS message container sent as part of the Security Mode Complete message in step 9b.
[0414] If the UE is initially registered with native 5G-GUTI (i.e. the UE is in RM-DEREGISTERED state), the UE shall indicate the related GUAMI information in the AN parameters. If the UE is initially registered with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.
[0415] If the UE is performing initial registration or mobility registration and CIoT 5GS optimization is supported, the UE shall indicate its preferred network behavior (see clause 5.31.2 of TS 23.501[2]). If S1 mode is supported, the preferred network behavior of the UE's EPC is included in the S1 UE network capabilities in the registration request message (see clause 8.2.6.1 of TS 24.501
[25] ).
[0416] For emergency registration, if the UE does not have a valid 5G-GUTI available, then SUCI shall be included, if the UE does not have a SUPI and a valid 5G-GUTI, then PEI shall be included, otherwise 5G-GUTI shall be included, which indicates the latest serving AMF.
[0417] The UE may provide UE usage settings based on the UE configuration as defined in clause 5.16.3.7 of TS 23.501 [2]. The UE shall provide the Requested-NSSAI as described in clause 5.15.5.2.1 of TS 23.501 [2] and, if the UE supports subscription-based constraints on concurrent registration of network slices and also takes into account the NSSRG information constraints as described in clause 5.15.12 of TS 23.501 [2], in case of initial registration or mobility registration update, the UE shall include the Requested-NSSAI mapping (if available), which is a mapping of each S-NSSAI of the Requested-NSSAI to the HPLMN S-NSSAI, so that the network can ensure that the S-NSSAI in the Requested-NSSAI is allowed based on the subscribed S-NSSAI. In case of inter-PLMN mobility, if the serving PLMN S-NSSAI corresponding to the established PDU session does not exist in the UE, the relevant HPLMN S-NSSAI associated with the established PDU session shall be provided in the Requested-NSSAI mapping as described in clause 5.15.5.2.1 of TS 23.501 [2].
[0418] If the UE is using a default configured NSSAI as defined in TS 23.501 [2], the UE shall include the default configured NSSAI indication.
[0419] If the UE supports allocation of WUS assistance information from the AMF, the UE may include UE paging capability information (see TS 23.501 [2]).
[0420] In case of mobility registration update, the UE shall include in the list of PDU sessions to be activated those PDU sessions for which there is pending uplink data. When the UE includes the list of PDU sessions to be activated, the UE shall indicate only those PDU sessions associated to the access related to the registration request. As specified in TS 24.501
[25] , the UE shall include in the list of PDU sessions to be activated those PDU sessions that are always on and accepted by the network, even if there is no pending uplink data for that PDU session.
[0421] NOTE 3: If the UE is outside the coverage area of the LADN, the PDU session corresponding to the LADN is not included in the list of PDU sessions to be activated.
[0422] The UE MM Core Network Function is provided by the UE and processed by the AMF as defined in clause 5.4.4a of TS 23.501 [2]. The UE includes in the UE MM Core Network Function an indication of whether the UE supports the request type flag "Handover" for the PDN connectivity request during the attach procedure as defined in clause 5.17.2.3.1 of TS 23.501 [2]. If the UE supports "Strict Periodic Registration Timer Indication", the UE indicates the UE capability of "Strict Periodic Registration Timer Indication" in the UE MM Core Network Function. If the UE supports CAG, the UE indicates the UE capability of "CAG Supported" in the UE MM Core Network Function. If a UE operating two or more USIMs supports one or more multi-USIM features and intends to use one or more multi-USIM features, the UE indicates one or more multi-USIM specific features as described in clause 5.38 of TS 23.501 [2] in the UE MM Core Network Function.
[0423] As described in clause 5.6.5 of TS 23.501 [2], the UE may provide either the LADN DNN or an indication of the requested LADN information.
[0424] If available, the last visited TAI shall be included to help the AMF generate a registration area for the UE.
[0425] The security parameters are used for authentication and integrity protection (see TS 33.501
[15] ). The requested NSSAI indicates network slice selection assistance information (as defined in clause 5.15 of TS 23.501 [2]). The PDU session status indicates a previously established PDU session in the UE. If the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status indicates an established PDU session of the current PLMN in the UE.
[0426] A subsequent request is included if the UE has pending uplink signaling and the UE does not include a list of activated PDU sessions or the registration type indicates that the UE wants to perform an emergency registration. In the initial registration and mobility registration update, the UE provides the UE request DRX parameters as defined in clause 5.4.5 of TS 23.501 [2]. To request extended idle mode DRX, the UE may provide the extended idle mode DRX parameters as defined in clause 5.31.7.2 of TS 23.501 [2].
[0427] As described in TS 23.501 [2], the UE provides a UE radio capability update indication.
[0428] The UE includes a MICO mode preference, and optionally includes a requested active time value if the UE wants to use MICO mode during active time.
[0429] The UE may indicate its service gap control capability in the UE MM core network function (see clause 5.31.16 of TS 23.501 [2]).
[0430] For a UE that has a running service gap timer in the UE, the UE shall not set a subsequent request indication or uplink data state in the registration request message, except for network access for barred priority services such as emergency services or exception reporting (see clause 5.31.16 of TS 23.501 [2]).
[0431] If the UE supports RACS and has assigned a UE Radio Capability ID, the UE shall indicate the UE Radio Capability ID as defined in clause 5.4.4.1a of TS 23.501 [2] as a non-cleartext IE.
[0432] The PEI may be obtained from the UE at initial registration, as described in section 4.2.2.2.1.
[0433] If the UE supports subscription-based restriction on concurrent registrations of the network slicing feature, the UE includes an NSSRG handling support indication according to clause 5.15.12 of TS 23.501 [2]. The AMF stores in the UE context whether the UE supports this feature.
[0434] If a UE in MUSIM mode wants to enter CM-IDLE state immediately after, for example, performing mobility registration or periodic registration, the UE provides paging restriction information, optionally including a release request indication.
[0435] When the UE is performing disaster roaming registration, if the UE does not have a valid 5G-GUTI indicating the PLMN with disaster state and the PLMN with disaster state is not the UE's HPLMN, or the PLMN with disaster state is the UE's HPLMN but the UE does not provide its SUCI, the UE may indicate the PLMN with disaster state.
[0436] 2. If the 5G-S-TMSI or GUAMI is not included or does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available.
[0437] The (R)AN selects the AMF as described in clause 6.3.5 of TS 23.501 [2]. If the UE is in a CM-CONNECTED state, the (R)AN may forward a registration request message to the AMF based on the UE's N2 connection.
[0438] If the (R)AN cannot select an appropriate AMF, the (R)AN forwards the registration request to an AMF configured in the (R)AN to perform AMF selection.
[0439] 3. (R)AN to new AMF: N2 message (N2 parameters, registration request (as described in step 1) and [LTE-M indication]).
[0440] If NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID see clause 5.30 of TS 23.501 [2]), location information and cell identity related to the cell in which the UE is camped, and a UE context request indicating that a UE context including security information needs to be set up in the NG-RAN.
[0441] If NG-RAN is used, the N2 parameter shall also include the establishment cause and shall include an IAB indication if an indication was received in the AN parameter in step 1.
[0442] A mapping of the requested NSSAI is provided only if available.
[0443] If the registration type indicated by the UE is periodic registration update, steps 4 to 19 may be omitted.
[0444] If the establishment cause is associated with a priority service (e.g., MPS, MCS), the AMF includes a Message Priority header to indicate the priority information. As specified in TS 29.500
[17] , other NFs relay the priority information by including the Message Priority header in their service-based interfaces.
[0445] The RAT type used by the UE is determined (see clause 4.2.2.2.1) and based on that the AMF decides whether the UE is performing inter-RAT mobility to or from NB-IoT. If the AMF receives an LTE-M indication, the AMF considers that the RAT type is LTE-M and stores the LTE-M indication in the UE context.
[0446] When a UE includes a preferred network behavior, this defines the network behavior that the UE requests to be supported and available in the network, as defined in clause 5.31.2 of TS 23.501 [2].
[0447] If the UE includes a preferred network behavior and what the UE has indicated it supports in the preferred network behavior is incompatible with the network support, the AMF shall reject the registration request with an appropriate cause value (e.g., one that avoids retries in this PLMN).
[0448] If there is a service gap timer running in the UE context in the AMF for the UE and the subsequent request indication or the uplink data status is not included in the registration request message, the AMF shall ignore the subsequent request indication and the uplink data status and shall not perform any action related to the status.
[0449] If the UE included the UE radio capability ID in step 1 and the AMF supports RACS, the AMF stores the radio capability ID in the UE context.
[0450] For NR satellite access, if the AMF can determine based on the selected PLMN ID and ULI (including cell ID) received from the gNB that the UE is attempting to register in a PLMN that is not authorized to operate in the current UE location, the AMF should reject the registration request with a suitable cause value and indicating the country of the UE location if known in the AMF. In other cases, for example if the AMF does not know the UE location with sufficient accuracy to make a final decision, the AMF may proceed with the registration procedure and initiate a UE location procedure as specified in clause 6.10.1 of TS 23.273
[51] to prepare to deregister the UE if the information received from the LMF indicates that the UE is registered in a PLMN that is not authorized to operate in the UE location.
[0451] NOTE 4: Location information may not be guaranteed to be accurate enough for the AMF to determine in all cases the country in which the UE is located.
[0452] NOTE 5: Some countries use multiple MCCs and some MCCs, such as 901, may be allowed in multiple countries, and thus the UE may register with a different MCC in the PLMN than the one returned to the UE.
[0453] Upon receiving a registration rejection for the country in which the UE is located, the UE shall attempt to register with a PLMN that is permitted to operate in the UE location as specified in TS 23.122
[22] .
[0454] For disaster roaming registration, based on the ULI (including cell ID) received from the NG-RAN, the PLMN with disaster state derived from the UE's 5G-GUTI, derived from the UE's SUCI, or indicated by the UE, and the local configuration, the AMF determines whether disaster roaming service can be provided. If the current location does not receive disaster roaming service or disaster roaming service is not provided for the PLMN with disaster state derived from the UE's 5G-GUTI, derived from the UE's SUCI, or indicated by the UE, the AMF should reject the registration request with a suitable cause value.
[0455] 4. [Conditional] From new AMF to old AMF: Namf_Communication_UEContextTransfer (full registration request) or from new AMF to UDSF: Nudsf_UnstructuredDataManagement_Query().
[0456] The new AMF determines the old AMF using the UE's 5G-GUTI. If the new AMF receives the NID in the registration request, the new AMF determines that the 5G-GUTI is assigned by the SNPN, and determines the old AMF using the SNPN's 5G-GUTI and NID.
[0457] (with UDSF deployment): If the UE's 5G-GUTI is included in the registration request and the serving AMF has changed since the last registration procedure, the new AMF and old AMF are in the same AMF set and UDSF is deployed, or the new AMF obtains the stored UE's SUPI and UE context directly from the UDSF using the Nudsf_UnstructuredDataManagement_Query service operation, or if UDSF is not deployed, the new AMF and old AMF may share the stored UE context via implementation-specific means. This also includes event subscription information by each NF consumer for a given UE. In this case, the new AMF uses the integrity protection full registration request NAS message to perform and check integrity protection.
[0458] (without UDSF deployment): If the UE's 5G-GUTI is included in the registration request and the serving AMF has changed since the last registration procedure, the new AMF may invoke a Namf_Communication_UEContextTransfer service operation in the old AMF, including a full registration request NAS message and access type that can be integrity protected, to request the UE's SUPI and UE context. For details of this service operation, see clause 5.2.2.2.2. In this case, the old AMF uses either the 5G-GUTI and integrity protected full registration request NAS message, or the SUPI and an indication from the new AMF that the UE is verified, to check the integrity protection when the context transfer service operation execution corresponds to the requested UE. The old AMF also forwards the event subscription information by each NF consumer for the UE to the new AMF. If the old AMF has not yet reported a non-zero MO exception data counter to the (H-)SMF, the context response also includes the MO exception data counter.
[0459] If the old AMF has a PDU session for another access type (different from the access type indicated in this step) and if the old AMF determines that there is no possibility to relocate the N2 interface to the new AMF, the old AMF returns the UE's SUPI and indicates that the registration request has been verified for integrity protection, but does not include the remaining UE context.
[0460] For inter-PLMN movement, the UE context information includes the HPLMN S-NSSAI corresponding to the authorized NSSAI for each access type without the authorized NSSAI of the old PLMN.
[0461] NOTE 6: If the new AMF successfully performs UE authentication after a previous integrity check failure in the old AMF, the new AMF sets an indication that the UE is verified according to step 9a.
[0462] Note 7: The NF consumer does not need to resubscribe to events regarding the new AMF after the UE has successfully registered with the new AMF.
[0463] If the new AMF has already received the UE context from the old AMF during the handover procedure, steps 4, 5 and 10 shall be skipped.
[0464] For emergency registration, if the UE identifies itself with a 5G-GUTI that is not known to the AMF, steps 4 and 5 are skipped and the AMF immediately requests a SUPI from the UE. If the UE identifies itself with a PEI, the SUPI request shall be skipped. The permission of emergency registration without user identity depends on local regulations.
[0465] 5. [Conditional] From old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE context in AMF (according to Table 5.2.2.2.2-1)) or from UDSF to new AMF: Nudsf_UnstructuredDataManagement_Query(). The old AMF may start an implementation-specific (guard) timer for the UE context.
[0466] If the UDSF is queried in step 4, it responds to the new AMF with a Nudsf_UnstructuredDataManagement_Query execution for the relevant context including the established PDU session, the old AMF includes the SMF information DNN, S-NSSAI and PDU session ID, active NGAP UE-TNLA binding in N3IWF / TNGF / W-AGF, the old AMF includes information about the NGAP UE-TNLA binding. If the old AMF is queried in step 4, it responds to the new AMF with a Namf_Communication_UEContextTransfer execution by including the UE's SUPI and UE context.
[0467] If the old AMF holds information about the established PDU session and it is not an initial registration, the old AMF includes SMF information, DNN, S-NSSAI, and PDU session ID.
[0468] If the old AMF holds the UE context established via the N3IWF, W-AGF, or TNGF, the old AMF includes the CM state via the N3IWF, W-AGF, or TNGF. If the UE is in CM-CONNECTED state via the N3IWF, W-AGF, or TNGF, the old AMF includes information about the NGAP UE-TNLA binding.
[0469] If the old AMF fails to verify the integrity of the registration request NAS message, the old AMF shall indicate an integrity verification failure. If the new AMF is configured to allow emergency services for unauthenticated UEs, the new AMF shall operate as follows.
[0470] If the UE has only an emergency PDU session, the AMF skips the authentication and security procedures or acknowledges that authentication may fail and continues the mobility registration update procedure, or
[0471] If the UE has both emergency and non-emergency PDU sessions and authentication fails, the AMF continues the mobility registration update procedure and deactivates all non-emergency PDU sessions as specified in clause 4.3.4.2.
[0472] Note 8: The new AMF may determine whether a PDU session is used for emergency services by checking whether the DNN matches the emergency DNN.
[0473] If the old AMF holds information about the AM policy association and information about the UE policy association (i.e., policy control request trigger to update the UE policy as defined in TS 23.503
[20] ), the old AMF includes information about the AM policy association, the UE policy association, and the PCF ID. In case of roaming, the V-PCF ID and the H-PCF ID are included.
[0474] If the old AMF was a consumer of the UE-related NWDAF service, the old AMF includes information about the active analysis subscription in the Namf_Communication_UEContextTransfer response, i.e., subscription correlation ID, NWDAF identifier (i.e., instance ID or set ID), analysis ID, and associated analysis specific data. The use of analysis information by the new AMF is specified in TS 23.288
[50] .
[0475] The handling of the UE radio capability ID in the new AMF during inter-PLMN movement is specified in TS 23.501 [2].
[0476] Note 9: If the new AMF uses UDSF for context retrieval, the interaction between the old AMF, new AMF, and UDSF due to simultaneous UE signaling in the old AMF is an implementation issue.
[0477] 6. [Conditional] New AMF to UE: Identity Request().
[0478] If the SUCI is not provided by the UE and is not obtained from the old AMF, the identity request procedure is initiated by the AMF sending an identity request message to the UE requesting the SUCI.
[0479] 7. [Conditional] UE to new AMF: identity response().
[0480] The UE responds with an Identity Response message containing the SUCI, which the UE derives by using the public key of the provisioned HPLMN as specified in TS 33.501
[15] .
[0481] 8. The AMF may decide to initiate UE authentication by invoking the AUSF. In that case, the AMF selects the AUSF based on the SUPI or SUCI as described in clause 6.3.4 of TS 23.501 [2].
[0482] If the AMF is configured to support emergency registration for an unauthenticated SUPI and the UE indicates a registration type of emergency registration, the AMF skips the authentication or the AMF acknowledges that the authentication may fail and continues the registration procedure.
[0483] 9a. If authentication is required, the AMF shall request it from the AUSF, and if the trace requirements for the UE are available in the AMF, the AMF shall provide the trace requirements to the AUSF in the request. When requested by the AMF, the AUSF shall perform authentication of the UE. The authentication is performed as described in TS 33.501
[15] . The AUSF shall select a UDM as described in clause 6.3.8 of TS 23.501 [2] and obtain the authentication data from the UDM.
[0484] Editor's Note: In case of disaster roaming registration, how the AUSF performs authentication of the UE is FFS (to be further studied).
[0485] Once the UE is authenticated, the AUSF provides relevant security-related information to the AMF. If the AMF provides the SUCI to the AUSF, the AUSF shall return the SUPI to the AMF only after successful authentication.
[0486] After successful authentication in the new AMF, triggered by an integrity check failure in the old AMF in step 5, the new AMF invokes step 4 above again and indicates that the UE is verified (i.e. via the reason parameter as specified in clause 5.2.2.2.2).
[0487] 9b If no NAS security context exists, NAS security initiation is performed as described in TS 33.501
[15] . If the UE did not have a NAS security context in step 1, the UE includes a Full Registration Request message as defined in TS 24.501
[25] .
[0488] As described in section 4.2.2.2.3, the AMF determines whether the registration request needs to be rerouted, where the initial AMF refers to the AMF.
[0489] 9c. If the 5G-AN requests a UE context, the AMF shall initiate an NGAP procedure to provide the 5G-AN with a security context as specified in TS 38.413
[10] . If the AMF also determines that EPS fallback is supported (e.g., based on the UE capability to support the request type flag "handover" for the PDN connectivity request during the attach procedure, subscription data, and local policy as defined in clause 5.17.2.3.1 of TS 23.501 [2]), the AMF shall send an indication that "redirection for EPS fallback of voice is possible" to the 5G-AN as specified in TS 38.413
[10] . Otherwise, the AMF shall indicate that "redirection for EPS fallback of voice is not possible". In addition, if trace requirements for the UE are available in the AMF, the AMF shall provide the trace requirements to the 5G-AN in the NGAP procedure.
[0490] 9d. The 5G-AN stores the security context and informs the AMF. The 5G-AN uses the security context to protect messages exchanged with the UE as described in TS 33.501
[15] .
[0491] 10. [Conditional] From new AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (e.g., PDU Session ID released due to unsupported slicing).
[0492] When the AMF is changed, the new AMF informs the old AMF that the UE's registration in the new AMF is complete by invoking the Namf_Communication_RegistrationStatusUpdate service operation.
[0493] If the authentication / security procedures fail, the registration shall be rejected and the new AMF shall call the Namf_Communication_RegistrationStatusUpdate service operation with a rejection indication to the old AMF. The old AMF shall continue as if the UE context transfer service operation had never been received.
[0494] If one or more of the S-NSSAIs used in the old registration area cannot be served in the target registration area, the new AMF determines which PDU sessions cannot be supported in the new registration area. The new AMF invokes the Namf_Communication_RegistrationStatusUpdate service operation with the rejected PDU session ID to the old AMF. The new AMF then modifies the PDU session status accordingly. The old AMF informs the corresponding SMF to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation.
[0495] If the new AMF has received information about the AM policy association and UE policy association in the UE context transfer in step 5 based on the local policy and decides not to use the PCF identified by the PCF ID for the AM policy association and UE policy association, the new AMF informs the old AMF that the AM policy association and UE policy association in the UE context are no longer used, and PCF selection is made in step 15.
[0496] If the new AMF receives information about the UE-related analysis subscription in the UE context transfer in step 5, the new AMF may take over the analysis subscription from the old AMF. Otherwise, if the new AMF decides to create a new analysis subscription instead, the new AMF may inform the old AMF that the analysis subscription (identified by the subscription correlation ID) is no longer needed, whereupon the old AMF may unsubscribe the NWDAF analysis subscription for the UE according to TS 23.288
[50] .
[0497] 11. [CONDITIONAL] New AMF to UE: Identity Request / Response (PEI).
[0498] If the PEI was not provided by the UE and was not obtained from the old AMF, the identity request procedure is initiated by the AMF sending an identity request message to the UE to obtain the PEI. The PEI shall be transferred encrypted unless the UE has performed an emergency registration and is not authenticated.
[0499] For emergency registration, the UE may include the PEI in the registration request, in which case the PEI lookup is skipped.
[0500] If the UE supports RACS as indicated in the UE MM core network functionality, the AMF shall use the UE's PEI to obtain the IMEI / TAC for the purpose of RACS operation.
[0501] 12. Optionally, the new AMF initiates the ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see clause 5.2.4.2.2).
[0502] PEI verification will be performed as described in Section 4.7.
[0503] For emergency registration, if the PEI is blocked, operator policy determines whether to continue or stop the emergency registration procedure.
[0504] 13. If step 14 is performed, the new AMF may select a UDM based on the SUPI, and then the UDM may select a UDR instance. See clause 6.3.9 of TS 23.501 [2].
[0505] The AMF selects the UDM as described in clause 6.3.8 of TS 23.501 [2].
[0506] 14a-c. If the AMF has changed since the last registration procedure, or if the UE provides a SUPI in the AMF that does not reference a valid context, or if the UE registers to the same AMF that the UE already registered to a non-3GPP access (i.e., the UE is registered through a non-3GPP access and initiates this registration procedure to add a 3GPP access), the new AMF registers to the UDM using Nudm_UECM_Registration for the access to which it is registered (and subscribes to be notified when the UDM deregisters this AMF). In this case, if the AMF does not have event exposure subscription information for this UE, the AMF indicates it to the UDM. Then, if the UDM has an existing applicable event exposure subscription for an event detected in the AMF (possibly obtained from the UDR) for either this UE or a group to which this UE belongs, the UDM calls the Namf_EventExposure_Subscribe service to recreate the event exposure subscription.
[0507] The AMF shall provide the "Homogeneous support of IMS voice over PS sessions" indication (see clause 5.16.3.3 of TS 23.501[2]) to the UDM. The "Homogeneous support of IMS voice over PS sessions" indication shall not be included unless the AMF has completed its evaluation of the AMF on its support of "IMS voice over PS sessions" as specified in clause 5.16.3.2 of TS 23.501[2].
[0508] During initial registration, if the AMF and UE support SRVCC from NG-RAN to UTRAN, the AMF provides the UE SRVCC functionality to the UDM.
[0509] If the AMF determines that only the UE SRVCC capability has changed, the AMF sends the UE SRVCC capability to the UDM.
[0510] NOTE 10: At this step, the AMF may not have all the information required to decide the setting of the IMS voice over PS session support indication (see clause 5.16.3.2 of TS 23.501 [2]) for this UE. Therefore, the AMF may send "Homogeneous support of IMS voice over PS sessions" later in this procedure.
[0511] If the AMF does not have subscription data for the UE, the AMF uses Nudm_SDM_Get to obtain access and mobility subscription data, SMF selection subscription data, UE context in SMF data, and LCS mobile origination. If the AMF already has subscription data for the UE, but the SoR update indicator in the UE context requests the AMF to obtain SoR information depending on the NAS registration type ("initial registration" or "emergency registration") (see Annex C of TS23.122
[22] ), the AMF uses Nudm_SDM_Get to obtain steering of roaming information. This requires that the UDM may obtain this information from the UDR by Nudr_DM_Query. After the response is successfully received, the AMF subscribes to be notified using Nudm_SDM_Subscribe when the requested data is modified, and the UDM may subscribe to the UDR by Nudr_DM_Subscribe. If GPSI is available in the UE subscription data, the GPSI is provided to the AMF in the access and mobility subscription data from the UDM. The UDM may provide an indication that subscription data for network slicing is updated for the UE. If the UE subscribes to MPS in the serving PLMN, the "MPS priority" is included in the access and mobility subscription data provided to the AMF. If the UE subscribes to MCX in the serving PLMN, the "MCX priority" is included in the access and mobility subscription data provided to the AMF. The UDM also provides an IAB operation permission indication to the AMF as part of the access and mobility subscription data. The AMF shall trigger the setup of the UE context in the NG-RAN, or, if the initial setup is in step 9c, a modification of the UE context in the NG-RAN, including an indication that the IAB node is authorized.
[0512] Editor's Note: In case of disaster roaming registration, how the UDM provides the applicable subscription data for disaster roaming services to the AMF is FFS (to be further considered).
[0513] The new AMF provides the UDM with the access type that the new AMF provides service to the UE, and the access type is set to "3GPP access". The UDM stores the associated access type with the serving AMF and does not remove AMF identity information associated with other access types, if any. The UDM may store in the UDR information provided in the AMF registration by Nudr_DM_Update.
[0514] If the UE is registered to the old AMF for access and the old AMF and the new AMF are in the same PLMN, the new AMF sends another / independent Nudm_UECM_Registration to update the UDM with the access type set to the access used in the old AMF after the old AMF relocation is completed successfully.
[0515] The new AMF creates a UE context for the UE after obtaining the access and mobility subscription data from the UDM. The access and mobility subscription data includes whether the UE is allowed to include NSSAI in the 3GPP access RRC connection establishment in clear text. The access and mobility subscription data may include enhanced coverage restriction information. If received from the UDM and the UE included support for restriction of the use of enhanced coverage in step 1, the AMF determines whether enhanced coverage is restricted for the UE as specified in clause 5.31.12 of TS 23.501 [2] and stores the updated enhanced coverage restriction information in the UE context.
[0516] The access and mobility subscription data may include NB-IoT UE priority.
[0517] The subscription data may include a service gap time parameter. If received from the UDM, the AMF stores this service gap time in the UE context in the AMF for the UE.
[0518] For emergency registration where the UE is not successfully authenticated, the AMF shall not register to the UDM.
[0519] The AMF shall enforce mobility restrictions as specified in clause 5.3.4.1.1 of TS 23.501 [2]. For emergency registration, the AMF shall not check for mobility restrictions, access restrictions, regional restrictions, or subscription restrictions. For emergency registration, the AMF shall ignore any unsuccessful registration response from the UDM and continue the registration procedure.
[0520] Note 11: Instead of the Nudm_SDM_Get service operation, the AMF may use the Nudm_SDM_Subscribe service operation with an immediate report indication to trigger the UDM to return the subscribe data immediately if the corresponding functionality is supported by both the AMF and the UDM.
[0521] 14d. If the UDM stores the associated access type (e.g. 3GPP) with the serving AMF as indicated in step 14a, it causes the UDM to initiate Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (e.g. 3GPP) access, if any. If the timer started in step 5 is not running, the old AMF may remove the UE context for the same access type. Otherwise, the AMF may remove the UE context for the same access type upon timer expiry. If the serving NF removal reason indicated by the UDM is initial registration, the old AMF shall invoke the Nsmf_PDUSession_ReleaseSMContext(SM context ID) service operation to all associated SMFs of the UE to notify that the UE is deregistered from the old AMF for the same access type, as described in clause 4.2.2.3.2. The SMF shall release the PDU session upon getting this notification.
[0522] If the old AMF established the AM policy association and UE policy association with the PCF and the old AMF did not transfer the PCF ID to the new AMF (e.g., the new AMF is in a different PLMN), the old AMF performs the AMF initiated policy association termination procedure as defined in subclause 4.16.3.2 and the AMF initiated UE policy association termination procedure as defined in subclause 4.16.13.1. In addition, if the old AMF transferred the PCF ID in the UE context but the new AMF indicated in step 10 that the AM policy association information and the UE policy association information in the UE context are not used, the old AMF performs the AMF initiated policy association termination procedure as defined in subclause 4.16.3.2 and the AMF initiated UE policy association termination procedure as defined in subclause 4.16.13.1.
[0523] If the old AMF has an N2 connection for the UE (e.g. because the UE was in RRC inactive state but has now moved to E-UTRAN or to an area not served by the old AMF), the old AMF shall perform AN release (see section 4.2.6) with a cause value indicating that the UE has already locally released the RRC connection in the NG-RAN.
[0524] If the UE context in the old AMF includes an authorized NSSAI including one or more S-NSSAIs that comply with NSAC, when the old AMF receives Nudm_UECM_DeregistrationNotification from the UDM, it sends an update request message for each S-NSSAI that complies with NSAC to the corresponding NSACF with the update flag parameter set to decrease (see Section 4.2.11.2).
[0525] Once the registration procedure is completed, if the AMF does not indicate in step 14a that the event exposure subscription is unavailable, the AMF starts synchronizing the event exposure subscription with the UDM.
[0526] NOTE 12: The AMF may initiate synchronization with the UDM at any given time based on local policies even if an event is available in the UE context (e.g., as received from the old AMF). This may be done during subscription change related events.
[0527] 14e. [Conditional] If the old AMF does not have a UE context for another access type (i.e., non-3GPP access), the old AMF unsubscribes the UDM for subscription data using Nudm_SDM_unsubscribe.
[0528] 15. When the AMF decides to initiate PCU communication, the AMF functions as follows:
[0529] If the new AMF decides to use the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF in step 5, the AMF contacts the (V-)PCF identified by the (V-)PCF ID to obtain the policy. If the AMF decides to perform PCF discovery and selection, the AMF selects a (V-)PCF and may select an H-PCF (for roaming scenarios) as described in clause 6.3.7.1 of TS 23.501 [2] according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3.
[0530] 16. [Optional] The new AMF establishes / modifies the AM policy association. For emergency registration, this step is skipped.
[0531] If the new AMF selects a new (V-)PCF in step 15, the new AMF performs AM policy association establishment with the selected (V-)PCF as defined in section 4.16.1.2.
[0532] If the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF is used, the new AMF performs AM policy association modification with the (V-)PCF as defined in clause 4.16.2.1.2.
[0533] When the AMF informs the PCF of mobility restrictions (e.g., UE location) for adjustment, or when the PCF updates the mobility restrictions itself according to some conditions (e.g., application in use, date and time), the PCF shall provide the updated mobility restrictions to the AMF. If the subscription information includes trace requirements, the AMF shall provide the trace requirements to the PCF.
[0534] If the AMF supports DNN substitution, the AMF provides the PCF with the authorized NSSAI and, if available, the mapping of the authorized NSSAI.
[0535] If the PCF supports DNN replacement, the PCF provides a trigger for DNN replacement to the AMF.
[0536] 17. [Conditional] From AMF to SMF: Nsmf_PDUSession_UpdateSMContext().
[0537] For an emergency registered UE (see TS 23.501[2]), this step applies if the registration type is a mobility registration update.
[0538] AMF calls Nsmf_PDUSession_UpdateSMContext (see Section 5.2.8.2.6) in the following scenarios:
[0539] - If the list of PDU sessions to be activated is included in the registration request in step 1, the AMF sends a Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the PDU session to activate the user plane connection of this PDU session. Steps from step 5 onwards described in subclause 4.2.3.2 are executed to complete the user plane connection activation without sending RRC inactive support information and without sending a MM NAS service accept from the AMF to the (R)AN described in step 12 of subclause 4.2.3.2. Once the user plane connection for the PDU session is activated, the AS layer in the UE indicates it to the NAS layer.
[0540] -If the AMF determines in step 3 that the UE is performing inter-RAT mobility to or from NB-IoT, the AMF sends a Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the UE PDU session so that the SMF can update the UE PDU session according to the "PDU Session Continuity on Inter-RAT Mobility" subscription data. Steps from step 5 onwards described in subclause 4.2.3.2 are performed without sending a MM NAS service acceptance from the AMF to the (R)AN described in step 12 of subclause 4.2.3.2.
[0541] When the serving AMF is changed, the new serving AMF informs the SMF for each PDU session that the new AMF has taken over responsibility for the signaling path to the UE, and the new serving AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using the SMF information received from the old AMF in step 5. It also indicates whether the PDU session is reactivated.
[0542] NOTE 13: When the UE moves into a different PLMN, the AMF in the serving PLMN may insert or change the V-SMF in the serving PLMN for the home routed PDU session. In this case, the same procedure as described in clause 4.23.3 applies for the V-SMF change as for the I-SMF change (i.e. by replacing the I-SMF with the V-SMF). If the same SMF is used during the change between PLMNs, session continuity may be supported depending on the operator policy.
[0543] The steps from step 5 onwards described in section 4.2.3.2 are performed. If an intermediate UPF insertion, removal or modification is performed for a PDU session that is not included in the "reactivated PDU session", the procedure is performed without N11 and N2 interaction to update the N3 user plane between the (R)AN and the 5GC.
[0544] AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to SMF in the following scenarios:
[0545] -If any PDU session state indicates to be released in the UE, the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF to release any network resources associated with the PDU session.
[0546] If the serving AMF is changed, the new AMF shall wait until step 18 is completed for all SMFs associated with the UE. Otherwise, steps 19 to 22 may continue in parallel with this step.
[0547] 18. [Conditional] If the new AMF and old AMF are in the same PLMN, the new AMF sends a UE context modification request to the N3IWF / TNGF / W-AGF as specified in TS 29.413
[64] .
[0548] When the AMF is changed and the old AMF indicates that the UE is in CM-CONNECTED state via the N3IWF, W-AGF, or TNGF, and the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association for the N3IWF / TNGF / W-AGF to which the UE is connected, which automatically releases the existing NGAP UE association between the old AMF and the N3IWF / TNGF / W-AGF.
[0549] 19. The N3IWF / TNGF / W-AGF sends a UE context modification response to the new AMF.
[0550] 19a. [Conditional] After the new AMF receives a response message from the N3IWF, W-AGF, or TNGF in step 19, the new AMF registers to the UDM using Nudm_UECM_Registration as in step 14a, but with the access type set to "non-3GPP access". The UDM stores the associated access type with the serving AMF and does not remove AMF identities associated with other access types, if any. The UDM may store in the UDR information provided in the AMF registration by Nudr_DM_Update.
[0551] 19b. [Conditional] If the UDM stores the associated access type (i.e. non-3GPP) with the serving AMF as indicated in step 19a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (i.e. non-3GPP) access. The old AMF will remove the UE context for the non-3GPP access.
[0552] 19c. Old AMF unsubscribes the UDM from subscription data using Nudm_SDM_unsubscribe.
[0553] 20a.Empty.
[0554] 21. New AMF to UE: Registration Authorization (5G-GUTI, Registration Area, Mobility Restriction, PDU Session State, Allowed NSSAI, Allowed NSSAI Mapping, Configured NSSAI for Serving PLMN, Configured NSSAI Mapping, NSSRG Information, Rejected S-NSSAI, On Hold NSSAI, On Hold NSSAI Mapping, Periodic Registration Update Timer, Active Time, Strict Periodic Registration Timer Indication, LADN Information, Authorized MICO Mode, Support Indication for IMS Voice in PS Session, Emergency Services Support Indicator, Authorized DRX Parameters for E-UTRA and NR, Authorized DRX Parameters for NB-IoT, [Extended Idle Mode DRX parameters], [Paging Time Window], [Network support for interworking without N26], [Access Stratum Connection Establishment NSSAI Inclusive Mode], [Network Slicing Subscription Change Indication], [Operator Defined Access Category Definition], [List of Equivalent PLMNs], [Improved Coverage Restriction Information], [Supported Network Behavior], [Service Gap Time], [UE Radio Capability ID for PLMN Allocation], [UE Radio Capability ID for PLMN Allocation Removal], [WUS Assistance Information], [Simplified 5G-S-TMSI Configuration], [Connection Release Support], [Paging Cause Indication Support for Voice Services], [Paging Restriction Support], [Reject Paging Request Support]).
[0555] If the UE indicates support for the restricted slice support indicator, the AMF shall include an optional field validity time or deployment zone, or both, in the configured NSSAI for each S-NSSAI. The validity time indicates the period during which the service is available for the S-NSSAI, i.e., the UE can register to the S-NSSAI to receive the service associated with the S-NSSAI. The deployment zone is the location area in which the UE can receive the service for the S-NSSAI.
[0556] If the Requested NSSAI does not contain an S-NSSAI that is mapped to an S-NSSAI of the HPLMN subject to network slice specific authentication and authorization, and the AMF determines that it cannot provide an S-NSSAI in the Authorized NSSAI for the UE in the current UE tracking area, and if it cannot further consider a default S-NSSAI that is not yet involved in the current UE registration procedure, the AMF shall reject the UE registration and shall include a list of rejected S-NSSAIs in the rejection message, each of which is accompanied by an appropriate rejection cause value.
[0557] The authorized NSSAI for the access type for the UE is included in the N2 message carrying the registration accept message. The authorized NSSAI includes only S-NSSAIs that do not require network slice specific authentication and authorization based on subscription information, and S-NSSAIs for which network slice specific authentication and authorization have previously been successful regardless of the access type based on the UE context in the AMF. The mapping of reserved NSSAIs is to map each S-NSSAI of reserved NSSAIs for the serving PLMN to the HPLMN S-NSSAI.
[0558] If the UE indicates that it supports network slice specific authentication and authorization procedures in the UE MM core network function in the registration request, the AMF shall include in the pending NSSAI the S-NSSAI that is mapped to the S-NSSAI of the HPLMN that has an indication in the subscription information that it is subject to network slice specific authentication and authorization, as described in clause 4.6.2.4 of TS 24.501
[25] . In such a case, the AMF shall then trigger the network slice specific authentication and authorization procedures specified in clause 4.2.9.2 in step 25, except for the S-NSSAI for which network slice specific authentication and authorization has already been initiated in another access type for the same S-NSSAI based on the network policy. The UE shall not attempt to re-register the S-NSSAI included in the list of pending NSSAIs until the network slice specific authentication and authorization procedures are completed, regardless of the access type.
[0559] If the UE does not indicate that it supports network slice-specific authentication and authorization procedures in the UE 5GMM core network function in the registration request and the Request NSSAI includes an S-NSSAI that is mapped to an HPLMN S-NSSAI that complies with network slice-specific authentication and authorization, the AMF includes the S-NSSAI in the Request NSSAI in the Reject S-NSSAI.
[0560] The following reasons may cause the S-NSSAI to be unavailable in an authorized NSSAI:
[0561] -All S-NSSAIs in the requesting NSSAI are subject to network slice specific authentication and authorization, or
[0562] -If no Request NSSAI was provided or no S-NSSAI in the Request NSSAI matches any of the Subscribe S-NSSAI, all S-NSSAIs marked as default in the Subscribe S-NSSAI are subject to network slice-specific authentication and authorization.
[0563] The AMF shall provide an empty Authorization NSSAI. Upon receiving the empty Authorization NSSAI and the Reserved NSSAI, the UE shall register in the PLMN but shall not attempt to use any services offered by the PLMN in any access, except for e.g. emergency services (see TS 24.501
[25] ), until the UE receives the Authorization NSSAI, pending completion of network slice specific authentication and authorization procedures.
[0564] The AMF stores the NB-IoT priority obtained in step 14 and associates it with the 5G-S-TMSI assigned to the UE.
[0565] If the registration request message received through 3GPP access does not include any paging restriction information, the AMF shall delete any paging restriction information stored for the UE and stop restricting paging accordingly.
[0566] If the registration request message received through the 3GPP access includes a release request indication,
[0567] The AMF updates the UE context with any received paging restriction information and then implements it in a network-triggered service request procedure as described in section 4.2.3.3.
[0568] The AMF does not establish user plane resources and triggers the AN release procedure as described in section 4.2.6 after completion of the registration procedure.
[0569] The AMF sends a registration accept message to the UE indicating that the registration request is accepted. The 5G-GUTI is included when the AMF assigns a new 5G-GUTI. When receiving a registration request message of type "Initial Registration", "Mobility Registration Update", or "Disaster Roaming Registration" from the UE, the AMF shall include the new 5G-GUTI in the registration accept message. When receiving a registration request message of type "Periodic Registration Update" from the UE, the AMF shall include the new 5G-GUTI in the registration accept message. If the UE is already in RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the registration accept for both registrations. If the 5G-GUTI is not included in the registration accept, the UE shall use the 5G-GUTI assigned to the existing registration for the new registration as well. If the AMF assigns a new registration area, the AMF shall send the registration area to the UE via the registration accept message. For disaster roaming registration, the AMF shall allocate a registration area limited to the area with disaster conditions as specified in clause 5.40 of TS 23.501 [2]. If no registration area is included in the registration accept message, the UE shall consider the old registration area as valid. If mobility restrictions apply for the UE and the registration type is not emergency registration, the mobility restrictions are included. The AMF indicates the established PDU session in the PDU session state to the UE. The UE shall locally remove any internal resources related to the PDU session that are not marked as established in the received PDU session state. If the AMF invokes the Nsmf_PDUSession_UpdateSMContext procedure for UP activation of the PDU session in step 18 and receives a rejection from the SMF, the AMF indicates to the UE the PDU session ID and the reason why the user plane resources were not activated. When a UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources related to a PDU session of the current PLMN that is not marked as established in the received PDU session state.If PDU session state information is present in the registration request, the AMF shall indicate the PDU session state to the UE.
[0570] If the RAT type is NB-IoT and the network is configured to use the control plane relocation indication procedure, the AMF shall include in the registration accept message the simplified 5G-S-TMSI configuration that a UE using control plane CIoT 5GS optimization shall use to create a simplified 5G-S-TMSI (see clause 5.31.4.3 of TS 23.501 [2]).
[0571] The allowed NSSAI provided in the registration authorization is valid in the registration area and applies to all PLMNs whose tracking area is included in the registration area. The mapping of the allowed NSSAI is to map each S-NSSAI of the allowed NSSAI to the HPLMN S-NSSAI. The mapping of the configured NSSAI is to map each S-NSSAI of the configured NSSAI for the serving PLMN to the HPLMN S-NSSAI.
[0572] If the UE indicates that it supports subscription-based restriction on concurrent registration of the network slicing function, the AMF shall include the NSSRG information defined in clause 5.15.12 of TS 23.501 [2], if available.
[0573] If the UE has not indicated that it supports subscription-based restriction on concurrent registrations of the network slicing function, and the subscription information for the UE includes SRG information and the AMF has provided the UE with a configured NSSAI, the configured NSSAI shall include the S-NSSAI in accordance with clause 5.15.12 of TS 23.501 [2].
[0574] The AMF shall include in the registration accept message the LADN information for the list of LADNs, as described in clause 5.6.5 of TS 23.501 [2], that are available within the registration area determined by the AMF for the UE. The AMF may include operator-defined access category definitions, as described in TS 24.501
[25] , to let the UE determine the applicable operator-specific access category definitions.
[0575] If the UE included the MICO mode in the registration request, the AMF responds with a registration accept message whether the MICO mode should be used. If the MICO mode is allowed for the UE, the AMF may include an active time value and / or a strict periodic registration timer indication in the registration accept message. The AMF determines the periodic registration update timer value, the active time value, and the strict periodic registration timer indication based on the local configuration, the expected UE behavior if available, the UE indicated preferences, the UE capabilities, the UE subscription information and the network policies, or any combination thereof, to enable UE power saving, as described in clause 5.31.7 of TS 23.501 [2]. If the UE indicates the UE capability of the strict periodic registration timer indication in the registration request message as described in step 1, the AMF decides to apply the strict periodic registration timer indication to the UE. If the AMF provides the UE with a periodic registration update timer value together with the strict periodic registration timer indication, the UE and the AMF start the periodic registration update timer after this step as described in clause 5.31.7.5 of TS 23.501 [2].
[0576] In case of registration via 3GPP access, the AMF sets the support indication of IMS voice in PS session as described in clause 5.16.3.2 of TS 23.501 [2]. To set the support indication of IMS voice in PS session, the AMF may need to perform the UE capability match request procedure in clause 4.2.8a to check the compatibility of the radio capabilities of the UE and NG-RAN related to IMS voice in PS. If the AMF does not receive the voice support match indicator from the NG-RAN in time, based on the implementation, the AMF may set the support indication of IMS voice in PS session and update it at a later stage.
[0577] During registration via 3GPP access, if the AMF obtains or determines the target NSSAI and the corresponding RFSP index according to a local configuration to enable the NG-RAN to redirect the UE to a cell supporting a network slice that is not available in the current TA as described in clause 5.3.4.3.3 of TS 23.501 [2], the AMF provides the target NSSAI and the corresponding RFSP index to the NG-RAN.
[0578] In case of registration via non-3GPP access, the AMF sets the IMS voice support indication in the PS session as described in clause 5.16.3.2a of TS 23.501 [2].
[0579] The emergency service support indicator informs the UE that emergency services are supported, i.e., the UE is enabled to request a PDU session for emergency services. If the AMF receives the "MPS priority" from the UDM as part of the access and mobility subscription data based on the operator policy, the "MPS priority" is included in the registration accept message to the UE to inform the UE whether the configuration of the access identity 1 is valid in the selected PLMN, as specified in TS 24.501
[25] . If the AMF receives the "MCX priority" from the UDM as part of the access and mobility subscription data based on the operator policy and the UE subscription to the MCX service, the "MCX priority" is included in the registration accept message to the UE to inform the UE whether the configuration of the access identity 2 is valid in the selected PLMN, as specified in TS 24.501
[25] . The acknowledge DRX parameter is defined in clause 5.4.5 of TS 23.501 [2]. If the UE includes the request DRX parameter for NB-IoT in the registration request message, the AMF includes the acknowledge DRX parameter for NB-IoT. The AMF configures network support for interworking without N26 parameters as described in clause 5.17.2.3.1 of TS 23.501 [2]. If the AMF approves the use of extended idle mode DRX, the AMF includes the extended idle mode DRX parameters and paging time window as described in clause 5.31.7.2 of TS 23.501 [2].
[0580] The network slicing subscription change indication is included if the UDM is intended to indicate to the UE that the subscription has changed. If the AMF includes a network slicing subscription change indication, the UE shall locally clear all network slicing configurations for all PLMNs and, if applicable, update the configuration for the current PLMN based on any received information.
[0581] As specified in clause 5.15.9 of TS 23.501 [2], the access stratum connection establishment NSSAI inclusion mode is included to instruct the UE which NSSAI, if any, to include in the access stratum connection establishment. The AMF may set the value to the mode of operation a, b, c defined in clause 5.15.9 of TS 23.501 [2] in 3GPP access only if it indicates that the NSSAI is allowed to be included in the RRC connection establishment authorization.
[0582] For a UE registered in a PLMN, the AMF may provide a list of equivalent PLMNs, which is processed as specified in TS 24.501
[25] . For a UE registered in a SNPN, the AMF shall not provide a list of equivalent PLMNs to the UE.
[0583] If the UE included support for restricting the use of enhanced coverage in step 1, the AMF sends the enhanced coverage restriction information to the NG-RAN in an N2 message. The AMF also sends the enhanced coverage restriction information to the UE in a registration accept message.
[0584] If the UE receives the enhanced coverage restriction information in the registration accept message, the UE shall store this information and shall use the value of the enhanced coverage restriction information to determine whether to use the enhanced coverage feature.
[0585] If the UE and the AMF have negotiated to enable the MICO mode and the AMF uses the extended connection timer, the AMF provides the extended connection time value to the NG-RAN in this step (see clause 5.31.7.3 of TS 23.501 [2]). The extended connection time value indicates the minimum time that the RAN should keep the UE in RRC-CONNECTED state despite inactivity.
[0586] If the UE includes a preferred network behavior in the UE registration request, the AMF indicates the CIoT 5GS optimizations that it supports and approves in the supported network behavior information (see clause 5.31.2 of TS 23.501 [2]).
[0587] The AMF may steer the UE out of 5GC by rejecting the registration request. Before steering the UE out of 5GC, the AMF should take into account the desired supporting network behavior (see clause 5.31.2 of TS 23.501 [2]) and the availability of EPC for the UE.
[0588] If the AMF authorizes the MICO mode and is aware that there may be mobile terminated data or signaling pending, the AMF shall maintain the N2 connection for at least the extended connection time as described in clause 5.31.7.3 of TS 23.501 [2] and provide the extended connection time value to the RAN.
[0589] The AMF includes the service gap time if it is present in the subscription information (steps 14a-c) or if the service gap time is updated by a subscriber data update notification to AMF procedure (see section 4.5.1) and the UE indicates UE service gap control capability.
[0590] If the UE receives a service gap time in the registration accept message, the UE shall store this parameter and apply the service gap control (see clause 5.31.16 of TS 23.501[2]).
[0591] If the network supports WUS grouping (see TS 23.501 [2]), the AMF shall send WUS assistance information to the UE. If the UE provided UE paging capability information in step 1, the AMF shall take it into account when determining the WUS assistance information.
[0592] If the UE and AMF support RACS as defined in clause 5.4.4.1a of TS 23.501 [2], and the AMF needs to configure the UE with a UE radio capability ID, and the AMF already has a UE radio capability other than the NB-IoT radio capability for the UE, the AMF may provide the UE radio capability ID for the UE radio capability to the UE, which the UCMF returns to the AMF in a Nucmf_assign service operation for this UE. Alternatively, if the UE and AMF support RACS, the AMF may provide an indication to the UE to delete any PLMN-assigned UE radio capability IDs in this PLMN (see clause 5.4.4.1a of TS 23.501 [2]).
[0593] If the UE is "CAG supported" and the AMF needs to update the UE's CAG information, the AMF may include the CAG information in the registration accept message as part of the mobility restriction.
[0594] If the UE indicates support for paging cause indication for voice service capability in the registration request message, and if the network supports and intends to apply paging cause indication for voice service capability for the UE, the AMF includes an indication that the UE supports paging cause indication for voice service capability in the N2 message conveying the registration accept message.
[0595] If the multi-USIM UE indicated support for one or more multi-USIM specific features in the UE 5GMM core network capabilities in step 1, the AMF shall indicate to the multi-USIM UE whether the corresponding one or more multi-USIM specific features described in clause 5.38 of TS 23.501 [2] are supported based on the network capabilities and preferences by the network (i.e. based on the local network policy) by providing one or more of connection release support, paging cause indication for voice service support, paging restriction support, and rejected paging request support indication. If the multi-USIM UE indicated support for paging cause indication for voice service capability, the AMF supporting paging cause indication for voice service shall include an indication in the N2 message that the UE supports paging cause indication for voice service capability. The AMF shall simply indicate paging restriction support together with either connection release support or rejected paging request support. The UE shall simply use the multi-USIM specific features indicated by the AMF as supported.
[0596] 21b. [OPTIONAL] The new AMF performs UE policy association establishment as defined in clause 4.16.11. For emergency registration, this step is skipped.
[0597] The new AMF sends a request to create an Npcf_UEPolicyControl to the PCF. The PCF sends a request to create an Npcf_UEPolicyControl to the new AMF.
[0598] The PCF triggers the UE configuration update procedure as defined in clause 4.2.4.3.
[0599] 22.[Conditional]UE to new AMF:registration completed().
[0600] In step 21, after receiving the [Configured NSSAI for Serving PLMN], [Configured NSSAI Mapping], [NSSRG Information] and any of the network slicing subscription change indication, or CAG information, if the UE has successfully updated itself, the UE sends a registration complete message to the AMF.
[0601] The UE sends a registration complete message to the AMF to inform whether a new 5G-GUTI has been assigned.
[0602] If a new 5G-GUTI is assigned, the UE passes the new 5G-GUTI to the lower layers of that 3GPP access when the lower layers (either 3GPP access or non-3GPP access) indicate to the UE's RM layer that the registration complete message has been successfully transferred across the air interface.
[0603] NOTE 14: The above is required because the NG-RAN may use the RRC inactive state and part of the 5G-GUTI is used to calculate paging frames (see TS 38.304
[44] and TS 36.304
[43] ). It is assumed that the registration completion is reliably signaled to the AMF after the 5G-AN acknowledges its receipt to the UE.
[0604] If the list of PDU sessions to be activated is not included in the registration request and the registration procedure was not started in the CM-CONNECTED state, the AMF shall release the signaling connection with the UE according to clause 4.2.6.
[0605] If a subsequent request is included in the registration request, the AMF should not release the signaling connection after the registration procedure is completed.
[0606] If the AMF is aware that any signaling is pending in the AMF or between the UE and the 5GC, the AMF should not release the signaling connection immediately after the registration procedure is completed.
[0607] If the PLMN-assigned UE radio capability ID is included in step 21, the AMF stores the PLMN-assigned UE radio capability ID in the UE context when receiving the registration complete message.
[0608] If the UE receives the PLMN assigned UE radio capability ID deletion indication in step 21, the UE shall delete the PLMN assigned UE radio capability ID for this PLMN.
[0609] 23. [Conditional] AMF to UDM: If the access and mobility subscription data provided by the UDM to the AMF in 14b includes steering of roaming information with an indication that the UDM requests the UE to acknowledge receipt of this information, the AMF provides the UE response to the UDM using Nudm_SDM_Info. For more information on handling of steering of roaming information, see TS 23.122
[22] .
[0610] 23a. For registration via 3GPP access, if the AMF does not release the signaling connection, the AMF sends RRC inactive support information to the NG-RAN.
[0611] For registration via non-3GPP access, if the UE is also in CM-CONNECTED state in 3GPP access, the AMF sends RRC inactive support information to the NG-RAN.
[0612] The AMF also uses the Nudm_SDM_Info service operation to provide a response to the UDM that the UE has received and acted upon the CAG information or network slicing subscription change indication (see steps 21 and 22).
[0613] 24. [Conditional] AMF to UDM: After step 14a, in parallel with any of the preceding steps, the AMF shall send the "Homogeneous support for IMS voice in PS sessions" indication to the UDM using Nudm_UECM_Update.
[0614] - if the AMF has evaluated the support of IMS voice in PS sessions (see clause 5.16.3.2 of TS 23.501 [2]), and
[0615] - if the AMF determines that it needs to update its homogeneous support for IMS voice in PS sessions (see clause 5.16.3.3 of TS 23.501 [2]).
[0616] 25. [Conditional] If the UE indicates that it supports network slice specific authentication and authorization procedures in the UE MM Core Network Function in the Registration Request and any S-NSSAI in the HPLMN are subject to network slice specific authentication and authorization, the related procedures are performed in this step (see clause 4.2.9.1). Once the network slice specific authentication and authorization procedures are completed for all S-NSSAIs, the AMF shall trigger a UE Configuration Update procedure to convey the authorized NSSAIs including the S-NSSAIs for which the network slice specific authentication and authorization was successful, and shall include any rejected NSSAIs with an appropriate rejection cause value.
[0617] If the tracking area of the registration area was previously assigned as an unauthorised area pending network slice specific authentication and authorization, the AMF shall remove the mobility restriction.
[0618] The AMF stores an indication that the network slice-specific authentication and authorization is successful in the UE context for any S-NSSAI of the HPLMN that is subject to the network slice-specific authentication and authorization.
[0619] If the AMF determines that upon completing the network slice specific authentication and authorization procedures, it cannot provide an S-NSSAI in the authorized NSSAI for a UE that is already successfully authenticated and authorized by the PLMN, and if a default S-NSSAI cannot be further considered, the AMF shall perform the network-initiated deregistration procedure described in clause 4.2.2.3.3 and shall include a list of rejected S-NSSAIs in the explicit deregistration request message, each of which is accompanied by an appropriate rejection cause value.
[0620] Mobility related event notifications to NF consumers are triggered at the end of this procedure if described in subclause 4.15.4.
[0621] <5.15.4.1.1 UE network slice configuration> The network slice configuration information includes one or more configured NSSAIs. The configured NSSAI may be configured by the serving PLMN and applied to the serving PLMN, or may be a default configured NSSAI configured by the HPLMN, which applies to any PLMN for which a specific configured NSSAI has not been provided to the UE. There is at most one configured NSSAI per PLMN.
[0622] NOTE 1: The value used in the default configured NSSAI is expected to be commonly determined by all roaming partners, e.g., by using values standardized by 3GPP or other organizations.
[0623] The default configured NSSAI, if it is configured in the UE, is used by the UE in the serving PLMN only if the UE does not have a configured NSSAI for the serving PLMN.
[0624] The configured NSSAI of a PLMN may include an S-NSSAI having a standard value or a PLMN-specific value.
[0625] The configured NSSAI for the serving PLMN includes S-NSSAI values that can be used in the serving PLMN and can be associated with a mapping of each S-NSSAI of the configured NSSAI to one or more corresponding HPLMN S-NSSAI values.
[0626] If the UE indicates support for the restricted slice support indicator, the AMF includes an optional field validity time or deployment zone, or both, in the configured NSSAI for each S-NSSAI. The validity time indicates the period during which services are available for the S-NSSAI, i.e. the UE can register to the S-NSSAI to receive services related to the S-NSSAI. The deployment zone is the location area in which the UE can receive services for the S-NSSAI. Upon receiving the configured S-NSSAI, the UE starts the validity time for the S-NSSAI for which the UE has received the validity time, and the period is equal to the received validity time.
[0627] The UE subscription may include network slice simultaneous registration group (NSSRG) information, in which case UE configuration is performed as described in clause 5.15.12.2.
[0628] The UE may be pre-configured with a default configured NSSAI. The UE may be provisioned / updated with the default configured NSSAI determined by the UDM in the HPLMN using the UE Parameter Update via UDM Control Plane procedure defined in clause 4.20 of TS 23.502 [3]. Each S-NSSAI in the default configured NSSAI may have a corresponding S-NSSAI as part of the subscribed S-NSSAI. As a result, if a subscribed S-NSSAI that is also present in the default configured NSSAI is updated, the UDM should update the default configured NSSAI in the UE.
[0629] In the HPLMN, the S-NSSAI in the configured NSSAI provided as described in subclause 5.15.4.2 shall match the subscribed S-NSSAI for the UE when it is provided to the UE. If the subscribed S-NSSAI is updated (i.e. some existing S-NSSAIs are removed and / or some new S-NSSAIs are added) and one or more are applicable to the serving PLMN where the UE is registered or the association mapping is updated as described in subclause 5.15.3, the AMF shall update the UE with the configured NSSAI and / or allowed NSSAI for the serving PLMN and / or the association mapping to the HPLMN S-NSSAI (see subclause 5.15.4.2). If the authorized NSSAI needs to be updated, as long as the AMF can determine a new authorized NSSAI (e.g., all S-NSSAIs in the old authorized NSSAI are removed from the subscribed S-NSSAI), the AMF shall provide the UE with the new authorized NSSAI and the association mapping for the HPLMN S-NSSAI, if the AMF cannot determine a new authorized NSSAI, the AMF shall not send any authorized NSSAI to the UE and indicate the UE to perform the registration procedure. If the UE is in CM-IDLE state, the AMF may trigger a network triggered service request or wait until the UE is in CM-CONNECTED state as described in clause 4.2.4.2 of TS 23.502 [3].
[0630] When providing a Request-NSSAI to the network upon registration, the UE in a given PLMN shall include and use only the S-NSSAI that applies to this PLMN. A mapping of the S-NSSAI of the Request-NSSAI to the HPLMN S-NSSAI may also be provided (see clause 5.15.4.1.2 for when this is required). The S-NSSAI in the Request-NSSAI is the part of the configured NSSAI and / or allowed NSSAI that is applicable for this PLMN if the configured NSSAI and / or allowed NSSAI are available. If the UE receives NSSRG information with the configured NSSAI, the UE shall include in the Request-NSSAI only the S-NSSAIs for which all the S-NSSAIs share a common NSSRG. If the configured NSSAI and allowed NSSAI for the PLMN are not available, the S-NSSAI in the Request-NSSAI shall correspond to the default configured NSSAI, if configured in the UE. Upon successful completion of the UE registration procedure in an access type, the UE obtains from the AMF an authorized NSSAI for this access type, including one or more S-NSSAIs, if required (see clause 5.15.4.1.2 for when this is required), and their mapping to the HPLMN S-NSSAI, that are valid for the current registration area and access type provided by the AMF where the UE registered and that can be used simultaneously by the UE (up to the maximum number of simultaneous network slice instances or PDU sessions).
[0631] The UE may also obtain one or more rejection NSSAIs with the cause and justification of the rejection from the AMF. - for the entire PLMN, or -About the current registration area It may be rejected.
[0632] While the UE remains RM-REGISTERED in a PLMN, regardless of the access type, the UE shall not attempt to register again to an S-NSSAI that is rejected for the entire PLMN until this rejected NSSAI is deleted as specified below.
[0633] While the UE remains RM-REGISTERED in a PLMN, the UE shall not attempt to register again to an S-NSSAI that is rejected in the current registration area until the UE moves out of the current registration area.
[0634] NOTE 2: Details and more cases of S-NSSAI rejection can be found in TS 24.501
[47] .
[0635] An S-NSSAI provided by the UE in a Request NSSAI that is neither an Allowed NSSAI nor provided as a Rejected S-NSSAI shall not be considered as rejected by the UE, i.e., the UE may request to register that S-NSSAI again the next time the UE sends a Request NSSAI.
[0636] The UE stores the (S-)NSSAI as follows:
[0637] -When the UE is provisioned with the configured NSSAI for the PLMN and / or the configured NSSAI to the HPLMN S-NSSAI, possibly NSSRG information for each S-NSSAI in the configured NSSAI (supported by the UE, if applicable), or when a network slicing subscription change requires the configuration to be removed,
[0638] --(if applicable) replacing any stored (old) configured NSSAI for this PLMN with a newly configured NSSAI for this PLMN;
[0639] --delete any stored association mapping of this old configured NSSAI for this PLMN to the HPLMN S-NSSAI and store the mapping of the configured NSSAI to the HPLMN S-NSSAI, if present and applicable;
[0640] --deleting any stored association NSSRG information for each S-NSSAI of the configured NSSAIs and storing association NSSRG information for each S-NSSAI of the configured NSSAIs, if present;
[0641] --delete any stored rejected S-NSSAI for this PLMN;
[0642] --The UE shall maintain the received configured NSSAI for the PLMN (if applicable) and the association mapping to the HPLMN S-NSSAI (if applicable) and the association NSSRG information for each S-NSSAI of the configured NSSAI (supported by the UE, if applicable) stored in the UE even when registering in another PLMN until a new configured NSSAI and / or association mapping for this PLMN is provisioned in the UE or the network slicing subscription is changed as described in clause 5.15.4.2. The number of configured NSSAIs and association mappings that continue to be stored in the UE for PLMNs other than the HPLMN is up to the UE implementation. The UE shall be able to store at least the configured NSSAI for the serving PLMN including any required mapping of the configured NSSAI for the serving PLMN to the HPLMN S-NSSAI and the default configured NSSAI.
[0643] -An authorized NSSAI received in a registration accept message or UE configuration update command applies to a PLMN if at least the TAI of this PLMN is included in the RA / TAI list included in this registration accept message or UE configuration update command. If the UE configuration update command includes an authorized NSSAI but not a TAI list, the last received RA / TAI list is applied to determine in which PLMN the authorized NSSAI is applicable. If received, the authorized NSSAI for the PLMN and access type and any association mapping of this authorized NSSAI to the HPLMN S-NSSAI shall be stored in the UE. The UE should store this authorized NSSAI and any association mapping of this authorized NSSAI to the HPLMN S-NSSAI even when the UE is turned off or until the network slicing subscription is changed as described in clause 5.15.4.2.
[0644] NOTE 3: It is up to the UE implementation whether the UE stores the allowed NSSAIs and any association mapping of the allowed NSSAIs to the HPLMN S-NSSAIs even when the UE is turned off.
[0645] If a new authorized NSSAI for the PLMN and any association mapping of the authorized NSSAI to the HPLMN S-NSSAI is received in an access type, the UE
[0646] --replace any stored (old) authorized NSSAIs and any associated mappings for these PLMNs and access types with this new authorized NSSAI,
[0647] — delete any stored association mapping of this old authorized NSSAI for this PLMN to the HPLMN S-NSSAI, and store the association mapping of this new authorized NSSAI to the HPLMN S-NSSAI, if any;
[0648] If received, an S-NSSAI that is rejected for the entire PLMN shall be stored in the UE while RM-REGISTERED in this PLMN, regardless of the access type or until the S-NSSAI is deleted.
[0649] If received, a rejected S-NSSAI for the current registration area shall be stored in the UE for the duration of RM-REGISTERED until the UE moves out of the current registration area or the S-NSSAI is deleted.
[0650] NOTE 4: The storage aspects of the rejected S-NSSAI are described in TS 24.501
[47] .
[0651] If received, the Pending NSSAI shall be stored in the UE as described in TS 24.501
[47] .
[0652] <5.15.5.2.1 Registration for a set of network slices> When a UE registers to a PLMN in an access type, the UE: - a configured NSSAI for this PLMN, - Authorized NSSAI for this PLMN and access type If you have either or both of the following: The UE shall provide to the network, at the AS layer and NAS layer under the conditions described in clause 5.15.9, a Request-NSSAI containing an S-NSSAI corresponding to the network slice on which the UE wishes to register, unless the S-NSSAI is stored in the UE in a Reserved-NSSAI.
[0653] The request NSSAI is - A default configured NSSAI (i.e., if the UE has neither a configured nor an allowed NSSAI for the serving PLMN); A configured NSSAI, as described below, or a subset thereof, for example, when the UE does not have an allowed NSSAI for an access type to the serving PLMN; - the authorized NSSAI or a subset thereof for the access type for which the request NSSAI is being sent, or - the authorized NSSAI or a subset thereof for the access type for which the request NSSAI is sent, plus one or more S-NSSAIs from the configured NSSAIs that are not already in the authorized NSSAI for the access type as described below It is assumed that the criterion is one of the following:
[0654] NOTE 1: If a UE wants to register only a subset of S-NSSAIs from the configured or authorized NSSAIs so that it can register in several network slices, e.g., to establish PDU sessions for several applications, and the UE uses URSP rules (including NSSP) or UE local configuration as defined in clause 6.1.2.2.1 of TS 23.503
[45] , the UE shall use the applicable URSP rules or UE local configuration to ensure that the S-NSSAI included in the Requested NSSAI does not conflict with the URSP rules or UE local configuration.
[0655] If the S-NSSAI in the configured NSSAI is configured with a validity timer or deployment zone field, the UE sends the S-NSSAI in the request NSSAI if the validity time is running or if the UE is in the deployment area of the S-NSSAI.
[0656] The subset of S-NSSAIs in the Configured NSSAI provided in the Requested NSSAI consists of one or more S-NSSAIs in the Configured NSSAI that are applicable to this PLMN, and if such an S-NSSAI is present, the corresponding S-NSSAI is not already present in the Allowed NSSAIs for the access type for this PLMN. The UE shall not include in the Requested NSSAI any S-NSSAI that is currently rejected by the network (i.e., rejected in the current registration area or rejected in the PLMN). For registration to a PLMN, if there is no configured or allowed NSSAI applicable to this PLMN, the S-NSSAI provided in the Request-NSSAI corresponds to the S-NSSAI in the configured NSSAI by default, unless the UE has an HPLMN S-NSSAI for the established PDU session, in which case the HPLMN S-NSSAI shall be provided in the mapping of the Request-NSSAI in the NAS REGISTER REQUEST message without the corresponding VPLMN S-NSSAI in the Request-NSSAI. If the UE has been provided with NSSRG information along with the configured NSSAI, the UE shall include only S-NSSAIs that share a common NSSRG in the Request-NSSAI (see clause 5.15.12.2).
[0657] If the UE is registered to the PLMN in an access type, the UE shall also indicate in the registration request message when the requested NSSAI is based on the default configured NSSAI.
[0658] The UE shall include the Request NSSAI in the RRC connection establishment and (applicable) connection establishment to N3IWF / TNGF and NAS registration procedure messages under the conditions described in clause 5.15.9. However, the UE shall not indicate any NSSAI in the RRC connection establishment or initial NAS message unless the UE has a configured NSSAI for the corresponding PLMN, an allowed NSSAI for the corresponding PLMN and access type, or a default configured NSSAI. If the UE has a HPLMN S-NSSAI for the established PDU session, the HPLMN S-NSSAI shall be provided in the mapping of the Request NSSAI in the NAS REGISTER REQUEST message, regardless of whether the UE has a corresponding VPLMN S-NSSAI. The (R)AN shall route NAS signaling between this UE and the AMF selected using the Request NSSAI obtained during RRC connection establishment or connection to N3IWF / TNGF, respectively. If the (R)AN cannot select an AMF based on the request NSSAI, it routes the NAS signaling to an AMF from the set of default AMFs. In the NAS signaling, if available, the UE provides a mapping of each S-NSSAI of the request NSSAI to the corresponding HPLMN S-NSSAI.
[0659] If the UE did not include the request NSSAI or GUAMI during the establishment of the connection to the (R)AN for this PLMN when the UE registers to the PLMN, the (R)AN shall route all NAS signaling from this UE to / from the default AMF to this UE. When the 5G-AN receives the request NSSAI and 5G-S-TMSI or GUAMI from the UE in the RRC connection establishment or the establishment of the connection to the N3IWF / TNGF, if the 5G-AN can reach the AMF corresponding to the 5G-S-TMSI or GUAMI, the 5G-AN shall forward the request to this AMF. Otherwise, the 5G-AN shall select a suitable AMF based on the request NSSAI provided by the UE and forward the request to the selected AMF. If the 5G-AN cannot select an AMF based on the request NSSAI, the request shall be sent to the default AMF.
[0660] When the AMF selected by the AN during the registration procedure receives a UE registration request, or after AMF selection by the MME (i.e., during handover from EPS to 5GS), the AMF receives the S-NSSAI from the SMF+PGW-C in 5GC.
[0661] -As part of the registration procedure described in clause 4.2.2.2.2 of TS 23.502 [3], or as part of a handover from EPS to 5GS using the N26 interface procedure described in clause 4.11.1.2.2 of TS 23.502 [3], the AMF may query the UDM to obtain UE subscription information, including the subscribed S-NSSAI.
[0662] -The AMF checks whether the S-NSSAI in the request NSSAI or the S-NSSAI received from the SMF+PGW-C is allowed based on the subscribed S-NSSAI (to identify the subscribed S-NSSAI, the AMF may use a mapping to the HPLMN S-NSSAI provided by the UE in the NAS message for each S-NSSAI in the request NSSAI).
[0663] -If the UE context in the AMF does not yet include an authorized NSSAI for the corresponding access type, the AMF queries the NSSF (see (B) below for further processing) unless the AMF is authorized (see (A) below for further processing) to determine whether the AMF can serve the UE based on the configuration in this AMF. The IP address or FQDN of the NSSF is configured locally in the AMF.
[0664] NOTE 2: Configuration in AMF depends on operator policy.
[0665] -If the UE context in the AMF already includes an authorized NSSAI for the corresponding access type, the AMF may be permitted to determine whether the AMF can provide service to the UE based on the configuration for this AMF (see (A) below for later processing).
[0666] -The AMF or NSSF may pre-subscribe to network data analysis related to slice load levels and / or observed service experience and / or variance analysis for a network slice from the NWDAF, optionally for an area of interest consisting of one or several TAIs. If the AMF subscribes to the analysis, the AMF may determine that the AMF cannot serve the UE based on the received analysis (see (A) below). If the AMF subscribes to notifications on changes in network slice or network slice instance availability information from the NSSF, which optionally indicates a list of supported TAIs, the AMF may determine that the AMF cannot serve the UE after a restriction notification is received (see (A) below). If the AMF does not subscribe to notifications on changes in availability information from the NSSF, the NSSF may take the analysis information into account when the AMF queries the NSSF (see (B) below).
[0667] NOTE 3: Configuration in AMF depends on operator policy.
[0668] (A) Depending on whether the above-mentioned configuration is satisfied, the AMF may be permitted to determine whether the AMF can provide service to the UE, and the following is performed:
[0669] For mobility from EPS to 5GS, the AMF first derives the serving PLMN value of the S-NSSAI based on the HPLMN S-NSSAI in the mapping of the requested NSSAI (in the CM-IDLE state) or the HPLMN S-NSSAI received from the SMF+PGW-C (in the CM-CONNECTED state). The AMF then considers the derived value as the requested NSSAI.
[0670] -For inter-PLMN mobility in 5GC, the new AMF derives the serving PLMN value of the S-NSSAI based on the HPLMN S-NSSAI in the mapping of the requested NSSAI. The AMF then considers the derived value as the requested NSSAI.
[0671] - The AMF checks whether it can serve all S-NSSAIs from the Requested NSSAI that are present in the Subscribed S-NSSAI (possibly using a configuration mapping S-NSSAI values between the HPLMN and the Serving PLMN) or whether it can serve all S-NSSAIs marked as default in the Subscribed S-NSSAI if the Requested NSSAI was not provided or any S-NSSAI in the Requested NSSAI is not allowed, i.e. does not match any of the subscribed S-NSSAIs or is not available in the tracking area of the current UE (see section 5.15.3).
[0672] --If the AMF subscribes to network data analysis related to slice load levels and / or observed service experience and / or variance analysis for a network slice from the NWDAF, or if the AMF receives network slice restrictions from the NSSF that apply to a list of TAIs supported by the AMF, the AMF may use that information to determine whether the AMF can serve the UE in the S-NSSAI in the request NSSAI.
[0673] If the AMF can serve the S-NSSAI in the request NSSAI, the AMF remains the serving AMF for the UE.Then, the allowed NSSAI consists of the list of S-NSSAIs in the request NSSAI that are allowed based on the subscribed S-NSSAI and / or the list of S-NSSAIs for serving PLMNs that are mapped to the HPLMN S-NSSAI provided in the mapping of the request NSSAI that are allowed based on the subscribed S-NSSAI, or all S-NSSAIs marked as default in the subscribed S-NSSAI if neither the requested NSSAI nor the mapping of the requested NSSAI is provided or none of the S-NSSAIs in the request NSSAI is allowed, taking into account the availability of network slice instances as described in clause 5.15.8 that can serve the S-NSSAI in the allowed NSSAI in the tracking area of the current UE in addition to any network slice instance restrictions for the S-NSSAI in the allowed NSSAI provided by the NSSF. If the AMF receives NSSRG information for subscribed S-NSSAIs as part of the UE subscription information, it shall include in the Allowed NSSAIs only S-NSSAIs for which all the S-NSSAIs share a common NSSRG (see clause 5.15.12). If at least one S-NSSAI in the Requested NSSAI is not available in the current UE tracking area, the AMF may determine the target NSSAI or step (B) is performed. The AMF also determines the mapping if the S-NSSAI included in the Allowed NSSAI needs to be mapped to the subscribed S-NSSAI value.If the Requested NSSAI is not provided, or the mapping of the S-NSSAI in the Requested NSSAI to the HPLMN S-NSSAI is not accurate, or the Requested NSSAI includes an S-NSSAI that is not valid in the serving PLMN, or the UE indicates that the Requested NSSAI is based on a default configured NSSAI, the AMF may also determine the association mapping of the configured NSSAI to the HPLMN S-NSSAI for the serving PLMN, if applicable, based on the subscribed S-NSSAI and the operator's configuration, so that these may be configured in the UE. Then, step (C) is performed.
[0674] --If not, the AMF queries the NSSF (see (B) below).
[0675] (B) If required as described above, the AMF needs to query the NSSF and the following occurs:
[0676] The AMF queries the NSSF for the requested NSSAI (if any, excluding the S-NSSAI according to the NSSAA that is in "pending" state and is not yet in the allowed NSSAIs), the default configured NSSAI indication, the mapping of the requested NSSAI to the HPLMN S-NSSAI, the subscribed S-NSSAI (with an indication if marked as the default S-NSSAI), the NSSRG information (if provided by the UDM see clause 5.15.12), any allowed NSSAIs the AMF may have for other access types (including their mapping to the HPLMN S-NSSAI), the PLMN ID of the SUPI, and the current tracking area of the UE.
[0677] Based on this information, local configuration, and other locally available information including RAN capabilities in the current tracking area for the UE, or load level information for the network slice instance provided by the NWDAF, the NSSF does the following:
[0678] --NSSF checks which S-NSSAI in the Request NSSAI is allowed based on the comparison of the subscribed S-NSSAI and the S-NSSAI in the mapping of the Request NSSAI to the HPLMN S-NSSAI. If the Request NSSAI was not provided or the S-NSSAI from the Request NSSAI is not allowed, i.e. not present in the subscribed S-NSSAI or not available, for example, in the current UE's tracking area, the NSSF considers the S-NSSAI marked as default in the subscribed S-NSSAI. If NSSRG information is provided, the NSSF selects only S-NSSAIs that share a common NSSRG (see clause 5.15.12).
[0679] --If the AMF does not subscribe to a network slice instance restriction service from the NSSF and the NSSF subscribes to network data analysis related to slice load levels and / or observed service experience and / or variance analysis for network slices from the NWDAF, the NSSF may use the analysis information for determining the (network slice instance and its) list of S-NSSAIs in the allowed NSSAI to serve the UE.
[0680] --NSSF selects a network slice instance to serve the UE. If multiple network slice instances in the UE's tracking area can serve a given S-NSSAI based on the operator's configuration, the NSSF may select one of the network slice instances to serve the UE, or the NSSF may delay the selection of the network slice instance until a NF / service within the network slice instance needs to be selected.
[0681] --The NSSF determines a target AMF set to be used to serve the UE, or determines a list of candidate AMFs based on the configuration, possibly after querying the NRF.
[0682] NOTE 4: If the target AMF returned from the NSSF is a list of candidate AMFs, the registration request message may simply be redirected via direct signaling between the initial AMF and the selected target AMF as described in clause 5.15.5.2.3.
[0683] The NSSF determines the allowed NSSAIs for the applicable access types consisting of the list of S-NSSAIs in the requested NSSAI that are allowed based on the subscribed S-NSSAI and / or the list of S-NSSAIs for serving PLMNs that are mapped to the HPLMN S-NSSAIs provided in the mapping of the requested NSSAI that are allowed based on the subscribed S-NSSAI, or all S-NSSAIs marked as default in the subscribed S-NSSAI if neither the requested NSSAI nor the mapping of the requested NSSAI is provided or none of the S-NSSAIs in the requested NSSAI are allowed, also taking into account the availability of network slice instances as described in clause 5.15.8 that can serve the S-NSSAIs in the allowed NSSAI in the tracking area of the current UE. If NSSRG information is applied, the NSSF selects only S-NSSAIs that share a common NSSRG (see clause 5.15.12).
[0684] --The NSSF also determines the mapping of each S-NSSAI of the authorized NSSAI to a subscribed S-NSSAI, if necessary.
[0685] --Based on operator configuration, the NSSF may determine the NRF to be used to select NFs / services within the selected network slice instance.
[0686] --Additional processing determines the mapping for the authorized NSSAI and subscribed S-NSSAI in roaming scenarios, as described in clause 5.15.6.
[0687] --If the requested NSSAI is not provided, or if the requested NSSAI includes an S-NSSAI that is not valid in the serving PLMN, or if the mapping of the S-NSSAI in the requested NSSAI to the HPLMN S-NSSAI is not accurate, or if a default configured NSSAI indication is not received from the AMF, the NSSF may also determine the configured NSSAI for the serving PLMN based on the subscribed S-NSSAI and operator configuration, and, if applicable, the association mapping of the configured NSSAI to the HPLMN S-NSSAI, which may be configured in the UE.
[0688] --If at least one S-NSSAI in the request NSSAI is not available in the current UE's tracking area, the NSSF may provide a target NSSAI to enable the NG-RAN to redirect the UE to a cell in a TA in another frequency band supporting a network slice not available in the current TA, as described in clause 5.3.4.3.3.
[0689] --NSSF returns to the current AMF the allowed NSSAIs for the applicable access type, the mapping of each S-NSSAI of the allowed NSSAI to the subscribed S-NSSAI if determined, and the target AMF set, or a list of candidate AMFs based on the configuration. The NSSF may return the NRF used to select the NF / service in the selected network slice instance, and the NRF used to determine the list of candidate AMFs from the AMF set. The NSSF may return the NSI ID associated with the network slice instance corresponding to the particular S-NSSAI. The NSSF may return the rejected S-NSSAI as described in clause 5.15.4.1. The NSSF may return the configured NSSAI for the serving PLMN, the association mapping of the configured NSSAI to the HPLMN S-NSSAI. The NSSF may return the target NSSAI as described in clause 5.3.4.3.3.
[0690] Depending on the available information, based on the configuration, the AMF may query an appropriate NRF (e.g., pre-configured locally or provided by the NSSF) for a target AMF set. The NRF returns a list of candidate AMFs.
[0691] --If AMF reassignment is required, the current AMF reroutes the registration request or transfers the UE context to the target serving AMF as described in section 5.15.5.2.3.
[0692] --Step (C) is executed.
[0693] (C) The Serving AMF shall determine a registration area such that all S-NSSAIs of the authorized NSSAIs for this registration area are available in all tracking areas of the registration area (taking into account other aspects as described in clause 5.3.2.3) and shall return to the UE the authorized NSSAIs and, if provided, a mapping of authorized NSSAIs to subscribed S-NSSAIs. The AMF may return a rejected S-NSSAI as described in clause 5.15.4.1.
[0694] Note 5: The S-NSSAI in the authorized NSSAI for non-3GPP access is uniformly available in the PLMN for the N3IWF case. For other types of non-3GPP access, the S-NSSAI in the authorized NSSAI for non-3GPP access may not be uniformly available across all PLMNs, e.g., different W-AGFs may support different TAIs supporting different network slices.
[0695] If the Requested NSSAI was not included, or if the mapping of the S-NSSAI in the Requested NSSAI to the HPLMN S-NSSAI is not accurate, or if the Requested NSSAI is not considered valid in the PLMN and therefore at least one S-NSSAI in the Requested NSSAI is rejected as not usable by the UE in the PLMN, or if the UE indicates that the Requested NSSAI is based on a default configured NSSAI, the AMF may update the UE slice configuration information for the PLMN as described in section 5.15.4.2.
[0696] If the Requested NSSAI does not contain an S-NSSAI mapped to an S-NSSAI of the HPLMN subject to network slice specific authentication and authorization, and the AMF determines that it cannot provide an S-NSSAI in the Authorized NSSAI for the UE in the current UE tracking area, and if it cannot add a default S-NSSAI as described in step (A), the AMF shall reject the UE registration and shall include a list of rejected S-NSSAIs in the rejection message, each of which is accompanied by an appropriate rejection cause value.
[0697] If the Requested NSSAI includes an S-NSSAI that is mapped to an S-NSSAI of an HPLMN that is subject to network slice specific authentication and authorization, the AMF shall include in the registration accept message the Authorized NSSAI that includes only the S-NSSAIs that are not subject to network slice specific authentication and authorization, and S-NSSAIs for which network slice specific authentication and authorization for at least one of the corresponding HPLMN S-NSSAIs based on the UE context in the AMF, if any, was previously successful regardless of the access type.
[0698] The AMF shall also provide a list of rejected S-NSSAIs, each of which is accompanied by an appropriate rejection cause value.
[0699] If the AMF has determined the target NSSAI or received the target NSSAI from the NSSF, the AMF shall provide the target NSSAI to the PCF to obtain the corresponding RFSP as described in clause 5.3.4.3.1, or if the PCF is not deployed, the AMF shall determine the corresponding RFSP based on the local configuration. The AMF then provides the target NSSAI and the corresponding RFSP to the NG-RAN as described in clause 5.3.4.3.3. The S-NSSAI that is mapped to the S-NSSAI of the HPLMN subject to ongoing network slice specific authentication and authorization shall be in "pending" state in the AMF and be included in the reserved NSSAI. The reserved NSSAI may include the mapping of the S-NSSAI for the serving PLMN to the HPLMN S-NSSAI, if applicable. The UE shall not include any of the S-NSSAIs from the reserved NSSAIs that the UE stores in the Requested NSSAI, regardless of the access type.
[0700] - if all S-NSSAIs in the requesting NSSAI are still subject to network slice specific authentication and authorization, or If a request-NSSAI was not provided or none of the S-NSSAIs in the request-NSSAI match any of the subscribe-S-NSSAIs, and all S-NSSAIs marked as default in the subscribe-S-NSSAI are subject to network slice-specific authentication and authorization, The AMF shall provide an "NSSAA to be performed" indicator to the UE in the registration accept message and shall not provide an authorized NSSAI. Upon receiving the registration accept message, the UE shall register in the PLMN but shall await completion of network slice specific authentication and authorization without attempting to use any services offered by the PLMN in any access, except for, e.g., emergency services (see TS 24.501
[47] ), until the UE receives an authorized NSSAI.
[0701] Then, the AMF shall initiate a network slice specific authentication and authorization procedure as described in clause 5.15.10 for each S-NSSAI that requires a network slice specific authentication and authorization procedure based on the network policy, except for S-NSSAIs for which network slice specific authentication and authorization has already been initiated in another access type for the same S-NSSAI. At the end of the network slice specific authentication and authorization step, the AMF shall provide the UE with new authorized NSSAIs, including S-NSSAIs subject to network slice specific authentication and authorization for which authentication and authorization are successful, by a UE configuration update procedure. The AMF may perform AMF selection once the NSSAA is completed for S-NSSAIs subject to S-NSSAIs in "pending" state. If an AMF change is required, this shall be triggered by the AMF using a UE configuration update procedure indicating that UE re-registration is required. S-NSSAIs that were not successfully authenticated and authorized are not included in the authorized NSSAIs, but are included in the list of rejected S-NSSAIs with a reject cause value indicating failure of network slice specific authentication and authorization.
[0702] If the AMF determines that upon completing the network slice specific (re-)authentication (re-)authorization procedure, it is unable to provide an S-NSSAI in the authorized NSSAI for a UE that is already successfully authorized by the PLMN, and if it was unable to add a default S-NSSAI as described in step (A), the AMF shall perform the network-initiated deregistration procedure as described in clause 4.2.2.3.3 of TS 23.502 [3] and shall include a list of rejected S-NSSAIs in the explicit deregistration request message, each of which is accompanied by an appropriate rejection cause value.
[0703] If the S-NSSAI is rejected with a rejection cause value indicating a network slice-specific authentication and authorization failure or revocation, the UE may attempt to request the S-NSSAI again based on a policy locally at the UE.
[0704] <Modifications and Replacements> Detailed embodiments have been described above. Still, those skilled in the art will appreciate that numerous modifications and alternatives may be made to the above embodiments while having the benefit of the disclosure embodied herein. Merely by way of example, numerous such alternatives and modifications are now described.
[0705] In the above description, the UE 3 and network devices are described for ease of understanding as having a number of separate modules (such as a communications control module). These modules may thus be provided for certain applications, for example where an existing system is modified to implement the present disclosure, and in other applications, for example in a system designed with the inventive features in mind from the beginning, but these modules may not be recognizable as separate entities, as they may be built into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a mixture of these.
[0706] Each controller may include any suitable form of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communications buses (e.g., control buses, data buses, and / or address buses), direct memory access (DMA) facilities, hardware or software implemented counters, pointers and / or timers, and / or the like.
[0707] In the above embodiment, a number of software modules have been described. Those skilled in the art will appreciate that the software modules may be provided in compiled or uncompiled form and may be provided to the UE 3 and the network device as a signal in a computer network or on a recording medium. Furthermore, the functions performed by some or all of the software may be performed using one or more dedicated hardware circuits. However, the use of software modules to update the functions of the UE 3 and the network device is preferred because the software modules facilitate the updating of the UE 3 and the network device.
[0708] In the above embodiment, 3GPP wireless communication (radio access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed line communication technology (e.g., BBF access, cable access, optical access, etc.) can also be used according to the above embodiment.
[0709] Items of user equipment may include communication devices such as, for example, mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (and even generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, 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 (mobile and / or generally fixed) communication device that may connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.
[0710] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
[0711] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and a system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.
[0712] It will be understood that each block of the block diagrams may be implemented by computer program instructions. The computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing apparatus generate means for implementing the function / act specified in the block or blocks of the flowcharts and / or block diagrams. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.
[0713] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC.
[0714] The previous description of the examples of the present disclosure is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples set forth herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[0715] Although the present disclosure has been shown and described in detail with reference to exemplary embodiments thereof, the present disclosure is not limited to such embodiments. It will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by this specification. For example, the above embodiments are not limited to 5GS, and the embodiments are also applicable to communication systems other than 5GS (e.g., 6G system, Beyond 5G system).
[0716] <Additional Notes> All or a part of the exemplary aspects of the above disclosure may be described as, but are not limited to, the following supplementary notes.
[0717] Addendum 1. A method for a communication device, the method comprising: receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; transmitting the S-NSSAI, the first information, and the second information; A method comprising:
[0718] Addendum 2. Receiving a first message, comprising: The first message includes the S-NSSAI and location information of a User Equipment (UE); and determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, sending a second message including an authorization NSSAI; the authorized NSSAI includes the S-NSSAI; and 2. The method of claim 1, further comprising:
[0719] Supplementary Note 3. The method of Supplementary Note 2, further comprising performing a process for removing the S-NSSAI from the permitted NSSAIs if the S-NSSAI is not valid.
[0720] Supplementary Note 4. A method for a User Equipment (UE), the method comprising: receiving a first message, the first message includes Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; and determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, sending a second message; the second message includes the S-NSSAI; and A method comprising:
[0721] Addendum 5. The method according to claim 1, further comprising receiving a third message after sending the second message; the third message includes an authorization NSSAI; The method of claim 4, wherein the authorized NSSAI includes the S-NSSAI.
[0722] Supplementary Note 6. The method of Supplementary Note 5, further comprising performing a process for removing the S-NSSAI from the permitted NSSAIs if the S-NSSAI is not valid.
[0723] Supplementary Note 7. The method of any one of Supplementary Notes 4 to 6, further comprising performing a Protocol Data Unit (PDU) Session Establishment procedure by using the S-NSSAI if the S-NSSAI is valid.
[0724] Addendum 8. A method for a communication device, the method comprising: receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, transmitting first system information, The first system information includes information indicating that the S-NSSAI is valid; and A method comprising:
[0725] Addition 9. The method according to claim 1, further comprising: if the S-NSSAI is not valid, sending second system information; The method of claim 8, wherein the second system information includes information indicating that the S-NSSAI is not valid.
[0726] Addendum 10. A communication device, comprising: means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; means for transmitting the S-NSSAI, the first information, and the second information; A communication device comprising:
[0727] Addendum 11. A means for receiving a first message, comprising: The first message includes the S-NSSAI and location information of a User Equipment (UE); means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for sending a second message including an authorization NSSAI, The authorized NSSAI includes the S-NSSAI; 11. The communication device of claim 10, further comprising:
[0728] Supplementary Note 12. The communications device of Supplementary Note 11, further comprising means for performing a process to remove the S-NSSAI from the permitted NSSAIs if the S-NSSAI is not valid.
[0729] Addition 13. A User Equipment (UE), comprising: A means for receiving a first message, the first message includes Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for sending a second message, the second message includes the S-NSSAI; A UE equipped with the above.
[0730] Addendum 14. The method according to claim 1, further comprising: receiving a third message after transmitting the second message; the third message includes an authorization NSSAI; The UE as described in Supplementary Note 13, wherein the permitted NSSAI includes the S-NSSAI.
[0731] Supplementary Note 15. The UE of Supplementary Note 14, further comprising means for performing a process to remove the S-NSSAI from the Allowed NSSAI if the S-NSSAI is not valid.
[0732] Supplementary Note 16. A UE as described in any one of Supplementary Notes 13 to 15, further comprising means for performing a Protocol Data Unit (PDU) Session Establishment procedure by using the S-NSSAI if the S-NSSAI is valid.
[0733] Addendum 17. A communication device, comprising: means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for transmitting first system information, The first system information includes information indicating that the S-NSSAI is valid; A communication device comprising:
[0734] Addition 18. The method according to claim 1, further comprising: means for transmitting second system information if the S-NSSAI is not valid; The communication device of claim 17, wherein the second system information includes information indicating that the S-NSSAI is not valid.
[0735] Addendum 19. A method of a first communication device, comprising: receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device; receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device; Transmitting to a communication terminal at least one of information indicating that registration in a network slice related to the S-NSSAI is permitted and information indicating that registration in the network slice is not permitted based on at least one of the information related to the validity time for the S-NSSAI and information related to the validity area for the S-NSSAI; A method comprising:
[0736] Addendum 20. A method for a communication terminal, comprising: Sending a request message for a network slice to a first communication device; receiving from the first communication device at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; A method comprising:
[0737] Addendum 21. A method of a first communication device, comprising: receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device; receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device; Transmitting at least one of information indicating that registration in a network slice associated with the S-NSSAI is permitted to a communication terminal based on at least one of the information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI; A method comprising:
[0738] Addendum 22. A method for a communication terminal, comprising: Sending a request message for a network slice to a first communication device; receiving information from the first communication device indicating that registration with the network is permitted, the information including at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; A method comprising:
[0739] Addendum 23. A method of a first communication device, comprising: receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; transmitting a first message related to at least one of the information related to a validity time for the network slice and the information related to a validity area for the network slice to a first base station; receiving a second message from the first base station confirming receipt by the first wireless station of the first message; A method comprising:
[0740] Supplementary Note 24. A method of a first communication device, comprising: receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; receiving a first message from a first base station indicating that the first base station manages a network slice over at least one of an effective area and an effective time; sending a second message to the first base station related to at least one of the validity time for the network slice and the validity area for the network slice; A method comprising:
[0741] 25. The method of claim 23 or 24, comprising transmitting at least one of information relating to the effective area and information of the effective time to a communication terminal.
[0742] 26. The method of claim 23 or 24, comprising transmitting information relating to said effective area and said effective time to a communications terminal.
[0743] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-mentioned embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.
[0744] This application claims priority to Indian Provisional Patent Application No. 202111060027, filed on December 22, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]
[0745] 1. Telecommunications Systems 3. UE 5 (R)AN Nodes 7 Core Network 20 Data Network 31 Transceiver Circuit 32 Antenna 33 Controller 34 User Interface 35 USIM 36 Memory 51 Transceiver Circuit 52 Antenna 53 Network Interface 54 Controller 55 Memory 60RU 61DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 AUSF 75 UDM 76 NWDAF 77 NF 361 Operating Systems 362 Communication Control Module 551 Operating Systems 552 Communication Control Module 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 Memory 611 Transceiver Circuit 612 Network Interface 613 Controller 614 Memory 621 Transceiver Circuit 622 Network Interface 623 Controller 624 Memory 701 Transceiver Circuit 702 Network Interface 703 Controller 704 Memory 751 Transceiver Circuit 752 Network Interface 753 Controller 754 Memory 771 Transceiver Circuit 772 Network Interface 773 Controller 774 Memory 3621 Transceiver Control Module 5521 Transceiver Control Module 6051 Operating System 6052 Communication Control Module 6141 Operating Systems 6142 Communication Control Module 6241 Operating Systems 6242 Communication Control Module 7041 Operating Systems 7042 Communication Control Module 7541 Operating Systems 7542 Communication Control Module 7741 Operating Systems 7742 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 75421 Transceiver Control Module 77421 Transceiver Control Module< / nf> < / udm> < / amf>
Claims
1. 1. A method for a communication device, the method comprising: receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; Transmitting the S-NSSAI, the first information, and the second information; A method comprising:
2. receiving a first message, the first message includes the S-NSSAI and User Equipment (UE) location information; determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, sending a second message including an authorization NSSAI; the authorization NSSAI includes the S-NSSAI; and The method of claim 1 further comprising:
3. 3. The method of claim 2, further comprising: if the S-NSSAI is not valid, performing a process to remove the S-NSSAI from the authorized NSSAIs.
4. 1. A method for a User Equipment (UE), the method comprising: receiving a first message, the first message includes Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; and determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, sending a second message; the second message includes the S-NSSAI; and A method comprising:
5. receiving a third message after sending the second message; the third message includes an authorization NSSAI; The method of claim 4 , wherein the authorization NSSAI includes the S-NSSAI.
6. 6. The method of claim 5, further comprising: if the S-NSSAI is not valid, performing a process to remove the S-NSSAI from the authorized NSSAIs.
7. 7. The method of claim 4, further comprising: if the S-NSSAI is valid, performing a Protocol Data Unit (PDU) Session Establishment procedure by using the S-NSSAI.
8. 1. A method for a communication device, the method comprising: receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; determining whether the S-NSSAI is valid based on the first information and the second information; and If the S-NSSAI is valid, transmitting first system information, the first system information includes information indicating that the S-NSSAI is valid; and A method comprising:
9. If the S-NSSAI is not valid, transmitting second system information; The method of claim 8 , wherein the second system information includes information indicating that the S-NSSAI is not valid.
10. 1. A communication device, comprising: means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; means for transmitting the S-NSSAI, the first information, and the second information; A communication device comprising:
11. A means for receiving a first message, comprising: The first message includes the S-NSSAI and location information of a User Equipment (UE); means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for sending a second message including an authorization NSSAI, The authorization NSSAI includes the S-NSSAI; The communication device of claim 10 further comprising:
12. The communications device of claim 11, further comprising: means for performing a process to remove the S-NSSAI from the permitted NSSAIs if the S-NSSAI is not valid.
13. A User Equipment (UE), A means for receiving a first message, comprising: the first message includes Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; and means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for sending a second message, the second message includes the S-NSSAI; A UE comprising:
14. means for receiving a third message after transmitting the second message; the third message includes an authorization NSSAI; The UE of claim 13, wherein the authorization NSSAI includes the S-NSSAI.
15. The UE of claim 14, further comprising: means for performing a process to remove the S-NSSAI from the allowed NSSAIs if the S-NSSAI is not valid.
16. The UE of any one of claims 13 to 15, further comprising: means for performing a Protocol Data Unit (PDU) Session Establishment procedure by using the S-NSSAI if the S-NSSAI is valid.
17. 1. A communication device, comprising: means for receiving Single Network Slice Selection Assistance Information (S-NSSAI), first information indicating where the S-NSSAI is valid, and second information indicating when the S-NSSAI is valid; means for determining whether the S-NSSAI is valid based on the first information and the second information; If the S-NSSAI is valid, a means for transmitting first system information, The first system information includes information indicating that the S-NSSAI is valid; A communication device comprising:
18. means for transmitting second system information if the S-NSSAI is not valid; The communications device of claim 17 , wherein the second system information includes information indicating that the S-NSSAI is not valid.
19. 1. A method for a first communication device, comprising: receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device; receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device; Transmitting at least one of information indicating that registration in a network slice associated with the S-NSSAI is permitted and information indicating that registration in the network slice is not permitted to a communication terminal based on at least one of the information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI; A method comprising:
20. A method for a communication terminal, comprising: sending a request message for a network slice to a first communication device; receiving from the first communication device at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; A method comprising:
21. 1. A method for a first communication device, comprising: receiving information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device; receiving at least one of information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI from the second communication device; Transmitting at least one of information indicating that registration in a network slice associated with the S-NSSAI is permitted to a communication terminal based on at least one of the information related to a validity time for the S-NSSAI and information related to a validity area for the S-NSSAI; A method comprising:
22. A method for a communication terminal, comprising: sending a request message for a network slice to a first communication device; receiving information from the first communication device indicating that registration with the network is permitted, the information including at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; A method comprising:
23. 1. A method for a first communication device, comprising: receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; transmitting a first message related to at least one of the information related to a validity time for the network slice and the information related to a validity area for the network slice to a first base station; receiving a second message from the first base station confirming receipt by the first wireless station of the first message; A method comprising:
24. 1. A method for a first communication device, comprising: receiving, from a second communication device, at least one of information related to a validity time for the network slice and information related to a validity area for the network slice; receiving a first message from a first base station indicating that the first base station manages a network slice over at least one of an effective area and an effective time; sending a second message to the first base station related to at least one of the validity time for the network slice and the validity area for the network slice; A method comprising:
25. 25. The method according to claim 23 or 24, comprising transmitting at least one of information relating to the effective area and information of the effective time to a communication terminal.
26. 25. A method according to claim 23 or claim 24, comprising transmitting information relating to the valid area and the valid time to a communications terminal.
Citation Information
Patent Citations
Improved selection of slice-supporting plmns while roaming away from home network
WO2021188351A1
