Handling rejected NSSAIs due to NSSAA failure

Abstract

A method and apparatus are provided for processing network slice selection assistance information (NSSAI) that has been rejected due to a network slice-specific authentication and authorization (NSSAA) failure. User equipment (UE) receives a UE configuration update command message from an access and mobility management function (AMF). Based on the failure of the NSSAA for a single NSSAI (S-NSSAI), the UE configuration update command message includes time information associated with a timer. The UE adds the S-NSSAI to the rejected NSSAI, starts the timer based on the time information, and deletes the S-NSSAI included in the rejected NSSAI after the timer expires.

Description

Technology Field

[0001] This specification relates to the processing of rejected NSSAI (network slice selection assistance information) due to a network slice-specific authentication and authorization (NSSAA) failure. Background Technology

[0002] 3GPP (3rd generation partnership project) LTE (long-term evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced mobile broadband), mMTC (massive machine type communications), and URLLC (ultra-reliable and low latency communications). NR must inherently be forward compatible.

[0005] A network slice refers to a logical network that provides specific network capabilities and characteristics. More specifically, a network slice is a network structure that enables the multiplexing of virtualized, independent logical networks within the same physical network infrastructure. Each network slice is a separate end-to-end network tailored to meet the diverse requirements requested by a specific application. Network slices enable the provision of various services to diverse terminals with different attributes. The problem to be solved

[0006] Network slice-specific authentication and authorization (NSSAA) procedures may be performed for a specific network slice. Data cannot be transmitted through a network slice where the NSSAA procedure has failed until specific conditions are satisfied. However, there may exist types of devices that are inherently difficult to satisfy the aforementioned specific conditions. Furthermore, even though there is a high probability that the NSSAA procedure will succeed after a certain period if the failure is temporary, the NSSAA procedure may only be performed after the aforementioned specific conditions are satisfied. means of solving the problem

[0007] In one embodiment, a method is provided to be performed by user equipment (UE) operating in a wireless communication system. The UE receives a UE configuration update command message from an access and mobility management function (AMF). Based on the failure of network slice-specific authentication and authorization (NSSAA) for single network slice selection assistance information (S-NSSAI), the UE configuration update command message includes time information associated with a timer. The UE adds the S-NSSAI to the rejected NSSAI, starts the timer based on the time information, and deletes the S-NSSAI included in the rejected NSSAI after the timer expires.

[0008] In another aspect, a device for implementing the above method is provided. Effects of the invention

[0009] This specification may have various effects.

[0010] For example, for a UE where error recovery through UE self-initialization is difficult because the device characteristics make it difficult to turn off the power or remove the USIM, error recovery may be possible for an S-NSSAI that was rejected due to a temporary NSSAA failure.

[0011] For example, even if the NSSAA fails once, the rejected S-NSSAI can be used again after a certain period of time, so data transmission may be possible using the S-NSSAI that failed the NSSAA once, without moving to a new PLMN.

[0012] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification. Brief explanation of the drawing

[0013] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied. FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies. FIG. 3 shows an example of a wireless device to which the implementation of the present specification applies. FIG. 4 shows an example of a UE to which the implementation of the present specification applies. FIG. 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied. FIGS. 6 and FIGS. 7 illustrate examples of registration procedures to which the implementation of the present specification applies. FIGS. 8 and FIGS. 9 illustrate examples of NSSAA procedures to which the implementation of the present specification applies. FIG. 10 illustrates an example of a network slice-specific re-authentication and re-authorization procedure disclosed by AAA-S to which the implementation of the present specification applies. FIG. 11 shows an example of a network slice permission revocation procedure disclosed by AAA-S to which the implementation of the present specification applies. FIG. 12 illustrates an example of a method performed by a UE to which the implementation of the present specification applies. FIG. 13 shows another example of a method performed by a UE to which the implementation of the present specification applies. FIG. 14 illustrates an example of a method for providing backoff time information to which the third implementation of the present specification is applied. FIG. 15 illustrates an example of a UE setting update procedure to which the third implementation of the present specification is applied. Specific details for implementing the invention

[0014] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0015] For convenience of explanation, the implementation of this specification is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to 3GPP-based wireless communication systems may be applied to other mobile communication systems.

[0016] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0017] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0018] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0019] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0020] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0021] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0022] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0023] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0024] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0025] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0026] The 5G usage scenario shown in FIG. 1 is merely an example, and the technical features of this specification may be applied to other 5G usage scenarios not shown in FIG. 1.

[0027] The three main requirements categories for 5G are (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low latency communications (URLLC) category.

[0028] Referring to FIG. 1, the communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

[0029] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0030] Wireless devices (100a to 100f) represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs) and head-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0031] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (personal digital assistant), a PMP (portable multimedia player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0032] For example, a UAV can be an aircraft that is not on board and is navigated by radio control signals.

[0033] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in a real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in a real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and playing back stereoscopic information using the phenomenon of light interference that occurs when two laser lights called holograms meet.

[0034] For example, a public safety device may include an image relay device or an image device that can be worn on a user's body.

[0035] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or operation. For instance, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0036] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, a (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0037] For example, a security device may be a device installed to prevent potential risks and maintain safety. For example, a security device may be a camera, closed-circuit TV (CCTV), a recorder, or a black box.

[0038] For example, a fintech device may be a device capable of providing financial services such as mobile payments. For example, a fintech device may include a payment device or a POS system.

[0039] For example, a weather / environment device may include a device for monitoring or predicting the weather / environment.

[0040] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0041] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D (device-to-device) communication), and communication between base stations (150c) (e.g., relay, IAB (integrated access and backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) may transmit / receive signals through various physical channels. To this end, based on various proposals in this specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0042] AI refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems within the realm of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0043] A robot can refer to a machine that automatically processes or operates given tasks based on its own capabilities. In particular, a robot equipped with the ability to perceive its environment, make independent judgments, and perform actions can be called an intelligent robot. Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units, enabling them to drive on the ground or fly in the air.

[0044] Autonomous driving refers to technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user intervention or with minimal user intervention. For example, autonomous driving can include technologies such as maintaining the driving lane, automatically adjusting speed like adaptive cruise control, driving automatically along a predetermined route, and automatically setting a route and driving once a destination is set. The term "vehicle" encompasses vehicles equipped solely with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped solely with electric motors; it can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be viewed as a robot equipped with autonomous driving capabilities.

[0045] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

[0046] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0047] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change. For example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as millimeter wave (mmW).

[0048] Frequency range definition Frequency range Subcarrier spacing FR1 450MHz - 6000MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

[0049] As described above, the numerical value of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0050] Frequency range definition Frequency range Subcarrier spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

[0051] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0052] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0053] Referring to FIG. 2, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals to / from an external device via various RATs (e.g., LTE and NR).

[0054] In FIG. 2, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of the {wireless devices (100a~100f) and base station (200)}, {wireless devices (100a~100f) and wireless devices (100a~100f)} and / or {base station (200) and base station (200)} of FIG. 1.

[0055] The first wireless device (100) may include at least one transceiver such as a transceiver (106), at least one processing chip such as a processing chip (101), and / or one or more antennas (108).

[0056] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). FIG. 2 is shown as an example in which the memory (104) is included in the processing chip (101). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

[0057] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0058] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store software code (105) that implements instructions to perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, software code (105) may implement instructions to perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, software code (105) may control the processor (102) to perform one or more protocols. For example, software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0059] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). Each transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (radio frequency) unit. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0060] The second wireless device (200) may include at least one transceiver such as a transceiver (206), at least one processing chip such as a processing chip (201), and / or one or more antennas (208).

[0061] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). FIG. 2 is shown as an example in which the memory (204) is included in the processing chip (201). Additionally and / or alternatively, the memory (204) may be placed outside the processing chip (201).

[0062] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0063] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store software code (205) that implements instructions to perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, software code (205) may implement instructions to perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, software code (205) may control the processor (202) to perform one or more protocols. For example, software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0064] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and transmit and / or receive a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0065] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (media access control) layer, a RLC (radio link control) layer, a PDCP (packet data convergence protocol) layer, a RRC (radio resource control) layer, and an SDAP (service data adaptation protocol) layer). One or more processors (102, 202) may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification.

[0066] One or more processors (102, 202) may be referred to as controllers, microcontrollers, microprocessors, and / or microcomputers. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in one or more processors (102, 202). Descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein may be implemented using firmware and / or software, and the firmware and / or software may be implemented to include modules, procedures, and functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0067] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may consist of read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0068] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0069] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0070] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0071] In an implementation of this specification, the UE may operate as a transmitting device in the uplink (UL; uplink) and as a receiving device in the downlink (DL; downlink). In an implementation of this specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of this specification or to control a transceiver (106) to perform UE operations according to an implementation of this specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of this specification or to control a transceiver (206) to perform base station operations according to an implementation of this specification.

[0072] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0073] FIG. 3 shows an example of a wireless device to which the implementation of the present specification applies.

[0074] Wireless devices can be implemented in various forms depending on the use example / service (see FIG. 1).

[0075] Referring to FIG. 3, the wireless device (100, 200) may correspond to the wireless device (100, 200) of FIG. 2 and may be composed of various components, devices / parts and / or modules. For example, each wireless device (100, 200) may include a communication device (110), a control device (120), a memory device (130), and additional components (140). The communication device (110) may include a communication circuit (112) and a transceiver (114). For example, the communication circuit (112) may include one or more processors (102, 202) of FIG. 2 and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver (114) may include one or more transceivers (106, 206) of FIG. 2 and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication device (110), the memory device (130), and the additional component (140) and controls the overall operation of each wireless device (100, 200). For example, the control unit (120) may control the electrical / mechanical operation of each wireless device (100, 200) based on a program / code / command / information stored in the memory device (130). The control device (120) can transmit information stored in the memory device (130) to an external (e.g., other communication device) via the communication device (110) through a wireless / wired interface, or store information received from an external (e.g., other communication device) via the communication device (110) through a wireless / wired interface in the memory device (130).

[0076] The additional component (140) can be configured in various ways depending on the type of wireless device (100, 200). For example, the additional component (140) may include at least one of a power device / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The wireless device (100, 200) may be implemented in the form of, but is not limited to, a robot (100a in FIG. 1), a vehicle (100b-1 and 100b-2 in FIG. 1), an XR device (100c in FIG. 1), a portable device (100d in FIG. 1), a home appliance (100e in FIG. 1), an IoT device (100f in FIG. 1), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (400 in FIG. 1), a base station (200 in FIG. 1), or a network node. The wireless device (100, 200) may be used in a mobile or fixed location depending on the use example / service.

[0077] In FIG. 3, the entirety of the various components, devices / parts and / or modules of the wireless device (100, 200) may be connected to each other via a wired interface, or at least some of them may be connected wirelessly via a communication device (110). For example, in each wireless device (100, 200), the control device (120) and the communication device (110) may be connected via a wire, and the control device (120) and the first device (e.g., 130 and 140) may be connected wirelessly via the communication device (110). Each component, device / part and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control device (120) may be composed of one or more sets of processors. As an example, the control device (120) may be composed of a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory device (130) may be composed of RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0078] FIG. 4 shows an example of a UE to which the implementation of the present specification applies.

[0079] Referring to FIG. 4, the UE (100) may correspond to the first wireless device (100) of FIG. 2 and / or the wireless device (100 or 200) of FIG. 3.

[0080] The UE (100) includes a processor (102), memory (104), transceiver (106), one or more antennas (108), a power management module (110), a battery (112), a display (114), a keypad (116), a SIM (subscriber identification module) card (118), a speaker (120), and a microphone (122).

[0081] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processor, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0082] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

[0083] A transceiver (106) is coupled to operate with a processor (102) and transmits and / or receives a wireless signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a wireless frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a wireless signal.

[0084] The power management module (110) manages the power of the processor (102) and / or the transceiver (106). The battery (112) supplies power to the power management module (110).

[0085] The display (114) outputs the result processed by the processor (102). The keypad (116) receives input to be used by the processor (102). The keypad (116) can be displayed on the display (114).

[0086] A SIM card (118) is an integrated circuit for securely storing an IMSI (international mobile subscriber identity) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

[0087] The speaker (120) outputs sound-related results processed by the processor (102). The microphone (122) receives sound-related input to be used by the processor (102).

[0088] FIG. 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.

[0089] The 5G system (5GS) structure consists of the following network functions (NF).

[0090] - AUSF (Authentication Server Function)

[0091] -AMF (Access and Mobility Management Function)

[0092] - DN (Data Network), for example, operator services, internet access, or third-party services

[0093] - USDF (Unstructured Data Storage Function)

[0094] - NEF (Network Exposure Function)

[0095] - I-NEF (Intermediate NEF)

[0096] - NRF (Network Repository Function)

[0097] - NSSF (Network Slice Selection Function)

[0098] - PCF (Policy Control Function)

[0099] - SMF (Session Management Function)

[0100] - UDM (Unified Data Management)

[0101] - UDR (Unified Data Repository)

[0102] - UPF (User Plane Function)

[0103] - UCMF (UE radio Capability Management Function)

[0104] - AF (Application Function)

[0105] - UE (User Equipment)

[0106] - (R)AN ((Radio) Access Network)

[0107] - 5G-EIR (5G-Equipment Identity Register)

[0108] - NWDAF (Network Data Analytics Function)

[0109] - CHF (CHarging Function)

[0110] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0111] - N3IWF (Non-3GPP InterWorking Function)

[0112] - TNGF (Trusted Non-3GPP Gateway Function)

[0113] - W-AGF (Wireline Access Gateway Function)

[0114] Figure 5 shows the 5G system structure in a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0115] In Fig. 5, for clarity of the point-to-point diagram, UDSF, NEF, and NRF are not described. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0116] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in FIG. 5. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in FIG. 5.

[0117] The 5G system structure includes the following reference points.

[0118] - N1: Reference point between UE and AMF.

[0119] - N2: Reference point between (R)AN and AMF.

[0120] - N3: Reference point between (R)AN and UPF.

[0121] - N4: Reference point between SMF and UPF.

[0122] - N6: Reference point between the UPF and the data network.

[0123] - N9: Reference point between two UPFs.

[0124] The following reference points show the interactions that exist between the NF services of NF.

[0125] - N5: Reference point between PCF and AF.

[0126] - N7: Reference point between SMF and PCF.

[0127] - N8: Reference point between UDM and AMF.

[0128] - N10: Reference point between UDM and SMF.

[0129] - N11: Reference point between AMF and SMF.

[0130] - N12: Reference point between AMF and AUSF.

[0131] - N13: Reference point between UDM and AUSF.

[0132] - N14: Reference point between two AMFs.

[0133] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF of the visited network for roaming scenarios.

[0134] - N16: Reference point between two SMFs (in the case of roaming, between the SMF of the visited network and the SMF of the home network)

[0135] - N22: Reference point between AMF and NSSF.

[0136] In some cases, two NFs may need to be connected to each other to service the UE.

[0137] The registration procedure is described. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0138] FIGS. 6 and FIGS. 7 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0139] The UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types.

[0140] - Initial registration for the 5GS; or

[0141] - Mobility registration update; or

[0142] - Periodic registration update; or

[0143] - Emergency registration

[0144] The general registration procedure of Figures 6 and 7 applies to all registration procedures described above, but the periodic registration update does not need to include all parameters used in other registration procedures.

[0145] The general registration procedure of Figures 6 and 7 is used when a UE is registered to a 3GPP connection when it is already registered to a non-3GPP connection, and vice versa. To register a UE to a 3GPP connection when it is already registered to a non-3GPP connection scenario, an AMF change may be required.

[0146] First, the procedure of Fig. 6 is explained.

[0147] (1) Step 1: The UE sends a Registration Request message to the (R)AN. The Registration Request message corresponds to the AN message.

[0148] A registration request message may include AN parameters. For NG-RAN, AN parameters include, for example, 5G-S-TMSI (5G SAE temporary mobile subscriber identity) or GUAMI (globally unique AMF ID), a selected PLMN (public land mobile network) ID (or PLMN ID and NID (network identifier)), and requested NSSAI (Requested network slice selection assistance information). AN parameters also include an establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0149] The registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change to the set of network slices allowed for the UE to use), or a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an urgent registration (i.e., the UE is in the restricted service state).

[0150] When a UE performs initial registration, the UE specifies the UE ID in the registration request message as follows, listed in order of lowest priority.

[0151] i) If the UE has a valid EPS (evolved packet system) GUTI (globally unique temporary identifier), the 5G-GUTI mapped from the EPS GUTI;

[0152] ii) Native 5G-GUTI assigned by the PLMN for which the UE is attempting to register (if available);

[0153] iii) Native 5G-GUTI assigned by a PLMN equivalent to the PLMN for which the UE is attempting to register;

[0154] iv) Native 5G-GUTI assigned by other PLMNs (if available);

[0155] v) Otherwise, the UE includes SUCI (subscriber concealed identifier) ​​in the registration request message.

[0156] If the UE performing the initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also marks the native 5G-GUTI as an additional GUTI. If one or more native 5G-GUTIs are available, the UE selects the 5G-GUTIs from items (ii)-(iv) in the list above in decreasing order of priority.

[0157] When the UE performs initial registration with native 5G-GUTI, the UE displays relevant GUAMI information in AN parameters. When the UE performs initial registration with SUCI, the UE does not display GUAMI information in AN parameters.

[0158] In the case of emergency registration, SUCI is included if the UE does not have a valid 5G-GUTI, and PEI is included if the UE does not have a SUPI (subscriber permanent identifier) ​​and does not have a valid 5G-GUTI. In other cases, a 5G-GUTI is included, which indicates the last serving AMF.

[0159] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the established PDU session of the current PLMN in the UE.

[0160] (2) Step 2: (R)AN selects AMF.

[0161] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not represent a valid AMF, (R)AN selects an AMF based on (R)AT and the requested NSSAI, if available.

[0162] If the UE is in the CM-CONNECTED state, (R)AN can forward a registration request message to the AMF based on the UE's N2 connection.

[0163] If (R)AN cannot select a suitable AMF, (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in (R)AN.

[0164] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0165] The registration request message may include all information and / or part of the information contained in the registration request message received from the UE described in Step 1.

[0166] The registration request message may include N2 parameters. When NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell ID associated with the cell where the UE is camping, and a UE context request indicating that a UE context including security information in NG-RAN must be established. When NG-RAN is used, the N2 parameters also include the cause for establishment.

[0167] If the registration type directed by the UE is a periodic registration update, steps 4-19 described below may be omitted.

[0168] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may call the Namf_Communication_UEContextTransfer service operation on the previous AMF, including the full registration request NAS (non-access stratum) message to request the UE's SUPI and UE context.

[0169] (5) Step 5: The previous AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call, including the UE's SUPI and UE context.

[0170] (6) Step 6: If SUCI is not provided by the UE or is not retrieved from the previous AMF, the new AMF may initiate the identity request procedure by sending an identity request message to the UE to request SUCI.

[0171] (7) Step 7: The UE may respond with an Identity Response message containing SUCI. The UE derives SUCI using the provided public key of the home PLMN (HPLMN).

[0172] (8) Step 8: The new AMF may decide to call AUSF to initiate UE authentication. In this case, the new AMF selects AUSF based on SUPI or SUCI.

[0173] (9) Step 9: Authentication / security may be established by UE, new AMF, AUSF and / or UDM.

[0174] (10) Step 10: If the AMF is changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the previous AMF that UE registration to the new AMF is complete. If the authentication / security procedure fails, registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to the previous AMF with a reject indication reason code. The previous AMF may continue as if no UE context passing service operation was received.

[0175] (11) Step 11: If the PEI is not provided by the UE or has not been retrieved from the previous AMF, the new AMF may initiate an Identity Request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted in encryption, except in cases where the UE cannot perform emergency registration and be authenticated.

[0176] (12) Step 12: Optionally, the new AMF can call the N5g-eir_EquipmentIdentityCheck_Get service operation to start ME ID checking.

[0177] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is explained.

[0178] (13) Step 13: If you perform Step 14 below, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0179] (14) Step 14: New AMFs can be registered with UDM.

[0180] (15) Step 15: The new AMF can select PCF.

[0181] (16) Step 16: The new AMF may optionally establish / modify AM policy associations.

[0182] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0183] (18) Step 18: If the new AMF and the previous AMF are in the same PLMN, the new AMF can send a request to modify the UE context to N3IWF / TNGF / W-AGF.

[0184] (19) Step 19: N3IWF / TNGF / W-AGF can send a UE context modification response to the new AMF.

[0185] (20) Step 20: After the new AMF receives a response message from N3IWF / TNGF / W-AGF in Step 19, the new AMF can register with UDM.

[0186] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0187] The new AMF sends a registration acceptance message to the UE indicating that the registration request has been accepted. If the new AMF assigns a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-REGISTERED state via another connection on the same PLMN, the UE uses the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration as well. If the new AMF assigns a new registration area, it transmits the registration area to the UE via the registration acceptance message. If the registration acceptance message does not contain a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included when mobility restrictions apply to the UE and the registration type is not an urgent registration. The new AMF indicates the PDU session established for the UE in the PDU session state. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU session state. When a UE connects to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with the PDU session of the current PLMN that are not indicated as established in the received PDU session state. If PDU session state information is present in the registration acceptance message, the new AMF instructs the UE on the PDU session state.

[0188] The Allowed NSSAI provided in the registration acceptance message is valid in the registration area and applies to all PLMNs having a tracking area included in the registration area. The Mapping of Allowed NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Allowed NSSAI. The Mapping of Configured NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0189] Additionally, the new AMF optionally performs UE policy association establishment.

[0190] (22) Step 22: If the UE succeeds in updating itself, it can send a Registration Complete message to the new AMF.

[0191] The UE can send a registration completion message to the new AMF to check if a new 5G-GUTI has been assigned.

[0192] (23) Step 23: In the case of registration via a 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In the case of registration via a non-3GPP connection, if the UE is in a CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0193] (24) Step 24: AMF can perform information updates on UDM.

[0194] (25) Step 25: The UE can execute network slice-specific authentication and authorization (NSSAA) procedures.

[0195] Network slicing is described. You may refer to Section 4.6 of 3GPP TS 24.501 V16.4.1.

[0196] 5GS supports network slicing. Within a PLMN or SNPN (stand-alone non-public network), a network slice is identified by an S-NSSAI consisting of an SST (slice / service type) and an SD (slice differentiator). Including an SD in an S-NSSAI is optional. A set of one or more S-NSSAIs is called an NSSAI. The following NSSAIs may be defined.

[0197] a) Configured NSSAI (configured NSSAI);

[0198] b) Requested NSSAI;

[0199] c) Allowed NSSAI;

[0200] d) subscribed NSSAI; and

[0201] e) Pending NSSAI

[0202] In addition, the following NSSAIs can be defined.

[0203] a) Rejected NSSAI for the current PLMN or SNPN;

[0204] b) Rejected NSSAI for the current registration area; and

[0205] c) Rejected NSSAI for the failed or revoked NSSAA

[0206] In the case of PLMN, the serving PLMN can set an NSSAI configured for the UE on a per-PLMN basis. Additionally, the HPLMN can set a single default NSSAI configured for the UE and may consider that default NSSAI configured as valid within a PLMN where the UE does not have a configured NSSAI or an allowed NSSAI. In the case of SNPN, the SNPN can set an SNPN configured for the UE that is applicable to the SNPN.

[0207] Rejected NSSAIs and allowed NSSAIs for a current registration area are managed independently by connection type (i.e., 3GPP connection or non-3GPP connection) and apply to the registration area. If a registration area contains tracking area IDs (TAIs) belonging to different PLMNs, the rejected NSSAIs and allowed NSSAIs for the current registration area may apply to PLMNs within this registration area.

[0208] An allowed NSSAI associated with a registration area containing a TAI belonging to a different PLMN that is an EPLMN (equivalent PLMN) can be used to form a requested NSSAI for any EPLMN when the UE moves out of the registration area where the allowed NSSAI was received.

[0209] When an NSSAA procedure is to be initiated for one or more S-NSSAIs within a requested NSSAI, said S-NSSAIs may be included in a pending NSSAI. When an NSSAA procedure is completed for an S-NSSAI within a pending NSSAI, said S-NSSAIs are moved to an accepted NSSAI or a rejected NSSAI depending on the outcome of the NSSAA procedure, and the UE is notified. Pending NSSAIs are managed regardless of the connection type. That is, even if a pending NSSAI is transferred to only one of the 3GPP connections and non-3GPP connections, it may apply to both.

[0210] A rejected NSSAI for a current PLMN or SNPN is applicable to all registered PLMNs or SNPNs. The AMF transmits a rejected NSSAI for a current PLMN when the registration area consists only of TAIs belonging to registered PLMNs. When a UE receives a rejected NSSAI for a current PLMN and the registration area contains TAIs belonging to different PLMNs, the UE treats the received rejected NSSAI for the current PLMN as applicable to all registered PLMNs.

[0211] A rejected NSSAI for a failed or withdrawn NSSAA includes one or more S-NSSAIs for which the NSSAA failed or withdrawn, and is applicable to all registered PLMNs or SNPNs.

[0212] NSSAI storage is described. You may refer to Section 4.6.2.2 of 3GPP TS 24.501 V16.4.1.

[0213] Generally, the configured NSSAI is the UE's subscriber NSSAI when the UE connects to the HPLMN, and it remains the same unless the UE's subscriber information changes. However, due to changes in subscriber information, an existing S-NSSAI may be created as the configured NSSAI, or a specific S-NSSAI may be removed. Subsequently, the AMF can notify the UE of the updated S-NSSAI to the currently connected network.

[0214] Additionally, the UE can store the configured NSSAI for networks it has visited in non-volatile memory. Therefore, when the UE selects a new VPLMN, the configured NSSAI information for previously visited networks may exist. Consequently, when performing a PLMN selection, the UE can possess the configured NSSAI information of the selected PLMN.

[0215] In addition, if a service level agreement (SLA) exists between the HPLMN and VPLMN that the UE can connect to, the UE can know which HPLMN's S-NSSAI the VPLMN has.

[0216] Where possible, configured NSSAIs are stored in the UE's non-volatile memory. Allowed NSSAIs are stored in the UE's non-volatile memory.

[0217] Each configured NSSAI stored in the UE is a set consisting of up to 16 S-NSSAIs. Each allowed NSSAI stored in the UE is a set consisting of up to 8 S-NSSAIs and is associated with a PLMN ID or SNPN ID and a connection type. Each configured NSSAI, excluding denied NSSAIs and default NSSAIs, is associated with a PLMN ID or SNPN ID. S-NSSAIs within a denied NSSAI for the current registration zone are additionally associated with the registration zone where the denied S-NSSAI is unavailable. S-NSSAIs within a denied NSSAI for the current PLMN or SNPN are considered denied for the current PLMN or SNPN regardless of the connection type. S-NSSAIs within a denied NSSAI for NSSAI and NSSAA failure or withdrawal are considered denied for the current PLMN regardless of the connection type. There are no duplicate PLMN IDs or SNPN IDs in each of the lists of established NSSAIs, allowed NSSAIs, rejected NSSAIs for current PLMNs or SNPNs, and rejected NSSAIs for current enrollment areas.

[0218] The UE stores the NSSAI as follows.

[0219] a) The configured NSSAI is stored until a newly configured NSSAI is received for a given PLMN or SNPN. The network may also provide the UE with an S-NSSAI mapped to the newly configured NSSAI to be stored in the UE. When the UE receives a newly configured NSSAI for a PLMN or SNPN, the UE must perform the following:

[0220] 1) Replace the configured NSSAI stored for this PLMN or SNPN with the newly configured NSSAI for this PLMN or SNPN;

[0221] 2) Delete the S-NSSAI stored for the configured NSSAI, and, if possible, save the S-NSSAI mapped for the newly configured NSSAI;

[0222] 3) Delete the allowed NSSAI stored for this PLMN or SNPN, and, where possible, if the UE receives a newly configured NSSAI for this PLMN or SNPN and a configuration update indication IE with the Registration requested bit set to "Registration requested" via the same Configuration Update Command message, but the message does not contain any new allowed NSSAI for this PLMN or SNPN, delete the mapped S-NSSAI stored for the allowed NSSAI;

[0223] 4) Delete the stored rejected NSSAI for the current PLMN or SNPN, the rejected NSSAI for the current registry area, and the rejected NSSAI for NSSAI and NSSAA failure or withdrawal.

[0224] When a UE receives an S-NSSAI associated with a PLMN ID from the network during the PDN connection establishment process in the EPS, the UE can save the received S-NSSAI as the NSSAI set for the PLMN identified by the PLMN ID associated with the S-NSSAI (if it is not already saved in the NSSAI set).

[0225] When a UE registers with a different PLMN, if possible, the UE can continue to store the configured NSSAI received for the PLMN and the associated mapped S-NSSAI.

[0226] b) An allowed NSSAI is stored until a new allowed NSSAI is received for a given PLMN or SNPN. The network may also provide the UE with an S-NSSAI mapped to the new allowed NSSAI to be stored in the UE. When a new allowed NSSAI is received for a PLMN or SNPN, the UE performs the following:

[0227] 1) Replace the allowed NSSAI stored for this PLMN or SNPN with the newly allowed NSSAI for this PLMN or SNPN;

[0228] 2) Delete the stored mapped S-NSSAI for the allowed NSSAI, and if possible, store the newly mapped S-NSSAI for the allowed NSSAI;

[0229] 3) Remove S-NSSAIs (if any) included in newly allowed NSSAIs for current PLMN or SNPN from the stored rejected NSSAIs;

[0230] 4) Remove one or more S-NSSAIs (if any) included in the newly allowed NSSAIs for the current PLMN or SNPN from the stored pending NSSAIs.

[0231] When the UE receives a configuration update command message in which the registration request bit of the configuration update instruction IE is set to "registration request" and does not contain other parameters, the UE deletes the allowed NSSAI stored for this PLMN or SNPN and, if possible, deletes the mapped S-NSSAI stored for the allowed NSSAI.

[0232] c) When the UE receives an S-NSSAI included in a rejected NSSAI in a registration acceptance message, registration rejection message, deregistration request message, or configuration update command message, the UE performs the following:

[0233] 1) Store the S-NSSAI in the rejected NSSAI based on the associated rejection cause;

[0234] 2) Remove the following S-NSSAIs (if any) from the allowed NSSAIs currently stored for PLMN or SNPN:

[0235] i) Rejected NSSAI for the current PLMN or SNPN for each and every connection type;

[0236] ii) Denied NSSAI for the current registry zone associated with the same access type; and

[0237] iii) Rejected NSSAI for NSSAA failure or withdrawal for each and every connection type;

[0238] 3) Remove one or more S-NSSAIs (if any) containing the following from the pending NSSAIs currently stored for PLMN or SNPN:

[0239] i) Rejected NSSAI for the current PLMN or SNPN for each and every connection type;

[0240] ii) Denied NSSAI for the current registry zone associated with the same access type; and

[0241] iii) Rejected NSSAI for NSSAA failure or withdrawal for each and every connection type;

[0242] UE,

[0243] 1) Deregister from the current PLMN using explicit signaling or enter the 5GMM-DEREGISTERED state for the current PLMN; or

[0244] 2) Upon successful registration with the new PLMN; or

[0245] 3) If you enter the 5GMM-DEREGISTERED state after failing to register a new PLMN;

[0246] If the UE is not registered with the current PLMN through another connection, the rejected NSSAI for the current PLMN is deleted.

[0247] UE,

[0248] 1) Unregister via connection type;

[0249] 2) Successfully register in the new registration area through the connection type; or

[0250] 3) If you enter the 5GMM-REGISTERED or 5GMM-DEREGISTERED status after failing to register in the new registration area via the connection type;

[0251] Rejected NSSAIs for the current registration area corresponding to the connection type are deleted.

[0252] d) When the UE receives one or more S-NSSAIs included in the pending NSSAI in the registration acceptance message, the UE stores one or more S-NSSAIs for the pending NSSAI.

[0253] UE,

[0254] 1) When deregistering from the current PLMN using explicit signaling or entering the 5GMM-DEREGISTERED state for the current PLMN;

[0255] 2) Upon successful registration with the new PLMN;

[0256] 3) If you enter the 5GMM-DEREGISTERED state after failing to register a new PLMN;

[0257] 4) When the attach or tracking area update procedure is successfully completed in S1 mode; or

[0258] 5) Initiate the attachment or tracking area update procedure in S1 mode, and when an attachment rejection message or a tracking area update rejection message is received;

[0259] If the UE is not registered with the current PLMN through another connection, the pending NSSAI for the current PLMN is deleted.

[0260] e) In the case of a PLMN, if the UE receives a network slicing instruction IE in a registration acceptance message or a configuration update command message where the network slicing subscription change indication is set to "Network slicing subscription changed," the UE deletes the network slicing information for each PLMN (excluding the current PLMN) that stores network slicing information. The UE does not delete the default NSSAI. Additionally, the UE updates the network slicing information for the current PLMN as described in a), b), c), and e) above (if received).

[0261] Describes initial registrations that the network does not accept. Refer to Section 5.5.1.2.5 of 3GPP TS 24.501 V16.4.1.

[0262] When the network is unable to use the network slice requested by the UE, it notifies the UE that the specific network slice is unavailable via a rejected NSSAI. If the network notifies the UE that a specific slice is unavailable, the UE performs the registration process again in the current cell if other network slices are available, and selects a different PLMN if all network slices are unavailable.

[0263] More specifically, if the network cannot accept the initial registration, the AMF sends a Registration reject message to the UE containing an appropriate 5GMM cause value.

[0264] When an initial registration request is rejected for the following reason, the network sets the 5GMM cause value to #62 "No network slices available" and may include the rejected NSSAI.

[0265] a) if all S-NSSAIs within the requested NSSAI are rejected for the current PLMN, for the current registry area, or are rejected due to a failed or withdrawn NSSAA, or if the UE has not requested any S-NSSAIs; and

[0266] b-1) If the UE sets the NSSAA bit of the 5GMM capability IE (information element) to "Network slice-specific authentication and authorization supported" and there is no subscribed S-NSSAI marked as default; or

[0267] b-2) If the UE sets the NSSAA bit of the 5GMM capability IE to "Network slice-specific authentication and authorization not supported," and i) there are no subscribed S-NSSAIs marked as default, or ii) all subscribed S-NSSAIs marked as default are targets of the NSSAA

[0268] The UE then performs the following actions based on the 5GMM cause value set to #62.

[0269] The UE stops the initial registration process, sets the 5GS update status to "5U2 NOT UPDATED", and enters the "5GMM-DEREGISTERED.NORMAL-SERVICE" or "5GMM-DEREGISTERED.PLMN-SEARCH" status. Additionally, the UE resets the registration attempt counter.

[0270] A UE that receives a rejected NSSAI in a registration rejection message performs the following actions depending on the reason for rejection of the rejected S-NSSAI.

[0271] - "S-NSSAI not available in the current PLMN or SNPN": The UE stores the rejected S-NSSAI in the rejected NSSAI for the current PLMN or SNPN and does not attempt to use the said rejected S-NSSAI in the current PLMN or SNPN until the UE is turned off, the universal integrated circuit card (UICC) containing the universal subscriber identification module (USIM) is removed, an entry in the "list of subscriber data" containing the SNPN ID of the current SNPN is updated, or the rejected S-NSSAI is removed or deleted.

[0272] - "S-NSSAI not available in the current registration area": ​​The UE stores the rejected S-NSSAI in the rejected NSSAI for the current registration area and does not attempt to use the rejected S-NSSAI in the current registration area until the UE is turned off, the UE leaves the current registration area, the UICC containing the USIM is removed, an entry in the "list of subscriber data" containing the SNPN ID of the current SNPN is updated, or the rejected S-NSSAI is removed or deleted.

[0273] - "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization": The UE stores the revoked S-NSSAI in the revoked NSSAI for the failed or revoked NSSAA, and does not attempt to use the revoked S-NSSAI on the current PLMN through any connection until the UE is turned off, the UICC containing the USIM is removed, the entry in the "list of subscriber data" containing the SNPN ID of the current SNPN is updated, or the revoked S-NSSAI is removed or deleted.

[0274] If the UE has an allowed NSSAI or a set NSSAI containing an S-NSSAI that is not included in any of the rejected NSSAIs for the current PLMN or SNPN, the rejected NSSAIs for the current enrollment area, or the rejected NSSAIs for NSSAA failure or withdrawal, the UE may remain in the current serving cell and apply the normal cell selection procedure. Additionally, the UE may initiate initial enrollment with a requested NSSAI containing any S-NSSAI from the allowed NSSAI or the set NSSAI that is not included in the rejected NSSAIs for the current PLMN or SNPN or the rejected NSSAIs for the current enrollment area. Otherwise, the UE may perform PLMN selection or SNPN selection.

[0275] NSSAA is described. You may refer to Section 4.2.9 of 3GPP TS 23.502 V16.4.0.

[0276] The NSSAA procedure is triggered for S-NSSAIs requiring network slice-specific authentication and authorization using the Extensible Authentication Protocol (EAP) framework via an AAA-S (AAA server) that can be hosted by the H-PLMN operator or a third party with a business relationship with the H-PLMN. If the AAA-S belongs to a third party, it may include the HPLMN's AAA-P (AAA proxy).

[0277] This procedure is triggered by the AMF during the registration process when network slice-specific authentication and authorization are required for some network slices, when the AMF determines that network slice-specific authentication and authorization are required for the S-NSSAI of a currently allowed NSSAI (e.g., change of subscription), or when the AAA-S that authenticated the network slice triggers re-authentication (e.g., step 25 of Fig. 7).

[0278] The AMF acts as the EAP authenticator and communicates with the AAA-S via the AUSF. The AUSF executes all AAA protocols that interact with the AAA protocols supported by the AAA-S.

[0279] FIGS. 8 and FIGS. 9 illustrate examples of NSSAA procedures to which the implementation of the present specification applies.

[0280] The AMF determines whether to execute the NSSAA procedure; if the AMF decides to execute the NSSAA procedure, it sends an EAP ID request to the UE. Upon receiving the EAP ID response from the UE, the AMF forwards it to the AAA-S via the NSSAAF (NSSAFF function). After exchanging multiple EAP requests and responses, the success or failure of the EAP is communicated. At this point, the AMF stores the EAP result for the corresponding S-NSSAI and sends the allowed or rejected NSSAI to the UE through the UE configuration update procedure.

[0281] First, the procedure of Fig. 8 is explained.

[0282] 1. For an S-NSSAI that requires an NSSAA due to a change in subscription information or a trigger by AAA-S, the AMF may trigger the start of the NSSAA procedure.

[0283] If an NSSAA procedure is triggered as a result of the registration procedure, the AMF may determine, based on the UE context within the AMF, that the UE has already been authenticated through the registration procedure via the first connection for some or all of the S-NSSAIs subject to the NSSAA. Depending on the result of the NSSAA from the previous registration procedure (e.g., success / failure), the AMF may skip the NSSAA for these S-NSSAAIs during the registration procedure via the second connection based on network policies.

[0284] If the NSSAA procedure corresponds to a UE re-authentication and re-licensing procedure triggered by AAA-S for one or more S-NSSAIs, or a re-authentication and re-licensing procedure triggered by the AMF based on operator policy or subscription changes, and the S-NSSAIs requiring NSSAA are included in the NSSAIs allowed for each connection type, the AMF selects the connection type to use for performing the NSSAA procedure based on the network policy.

[0285] 2. The AMF may send an EAP ID request for the S-NSSAI in a NAS MM forwarding message containing the S-NSSAI. This is the S-NSSAI of the H-PLMN, not the locally mapped S-NSSAI value.

[0286] 3. The UE provides the EAP ID response for the S-NSSAI along with the S-NSSAI to the AMF as a NAS MM forwarding message.

[0287] 4. AMF sends the EAP ID response to AUSF as Nausf_NSSAA_Authenticate Request (EAP ID response, AAA-S address, GPSI (generic public subscription identifier), S-NSSAI).

[0288] 5. If AAA-P exists (e.g., AAA-S belongs to a third party and the operator has deployed a proxy to the third party), AUSF forwards the EAP ID response message to AAA-P. Otherwise, AUSF forwards the message directly to AAA-S. AUSF uses an AAA protocol message of the same protocol supported by AAA-S toward AAA-P or AAA-S.

[0289] 6. AAA-P forwards the EAP ID message along with S-NSSAI and GPSI to AAA-S, which can be identified by the AAA-S address. AAA-S stores the GPSI to establish a connection with the EAP ID within the EAP ID response message, and AAA-S can later use this to revoke authentication and authorization or trigger re-authentication.

[0290] 7-14. EAP messages are exchanged with the UE. This step can be repeated one or more times.

[0291] Now, the procedure of Fig. 9, which follows the procedure of Fig. 8, is explained.

[0292] 15. EAP authentication is completed. AAA-S stores the authorized S-NSSAI and can determine the criteria for re-authentication and re-authorization based on local policies. EAP success / failure messages are forwarded to AAA-P along with GPSI and S-NSSAI (or directly to AUSF if AAA-P does not exist).

[0293] 16. When using AAA-P, AAA-P sends AAA protocol messages to AUSF including EAP success / failure, S-NSSAI, and GPSI.

[0294] 17. AUSF sends a Nausf_NSSAA_Authenticate Response to AMF containing EAP success / failure, S-NSSAI, and GPSI.

[0295] 18. The AMF transmits the NAS MM delivery message (EAP success / failure) to the UE. The AMF stores the EAP results for each S-NSSAI where the NSSAA procedure of steps 1-17 was performed.

[0296] 19a. [Conditional] If it is necessary to pass a new allowed NSSAI (i.e., a new S-NSSAI in which the NSSAA procedure succeeded in the requested NSSAI and / or an S-NSSAI in which the NSSAA procedure failed in the existing allowed NSSAI for the UE) and / or a new rejected S-NSSAI (i.e., an S-NSSAI in which the NSSAA procedure failed in the existing allowed NSSAI for the UE, or a new requested S-NSSAI in which the NSSAA procedure failed) to the UE, or if AMF reassignment is required, the AMF initiates a UE configuration update procedure for each connection type.

[0297] 19b. [Conditional] If the NSSAA procedure fails for all S-NSSAIs (if any) in the existing allowed NSSAIs for a UE and all S-NSSAIs (if any) in the requested NSSAIs, the AMF performs the unregistration procedure initiated by the network, or rejects the UE's registration request (if this procedure is triggered). The AMF includes a list of rejected S-NSSAIs with appropriate rejection cause values ​​in the explicit unregistration request message or registration rejection message. If network slice-specific re-authentication and re-authorization fail and there are PDU sessions associated with the S-NSSAIs for which the NSSAA procedure failed, the AMF initiates the PDU session release procedure with appropriate cause values ​​to release the PDU sessions.

[0298] FIG. 10 illustrates an example of a network slice-specific re-authentication and re-authorization procedure disclosed by AAA-S to which the implementation of the present specification applies.

[0299] AAA-S triggers the re-authentication and re-authorization of NSSAA. Re-authentication and re-authorization are performed on network slices that have already been authenticated and authorized. When AAA-S notifies of a re-authentication event, GPSI, and S-NSSAI, AMF performs NSSAA re-authentication and re-authorization.

[0300] 1. AAA-S requests reauthentication and re-authorization for the network slice specified by S-NSSAI in the AAA protocol reauthentication request message for the UE identified by GPSI in the AAA protocol reauthentication request message. This message is sent to AAA-P if AAA-P is used (e.g., AAA-S is owned by a third party), otherwise it is sent directly to AUSF.

[0301] 2. If AAA-P exists, forward the request to AUSF.

[0302] 3a-3b. AUSF obtains the AMF ID from the UDM using Nudm_UECM_Get along with the GPSI in the received AAA message.

[0303] 4. AUSF uses Nausf_NSSAA_Notify with the GPSI and S-NSSAI in the received AAA message to notify AMF of a re-authentication event to re-authenticate / re-authorize the S-NSSAI for the UE.

[0304] 5. The AMF triggers the NSSAA procedure defined in Figures 8 and 9.

[0305] FIG. 11 shows an example of a network slice permission revocation procedure disclosed by AAA-S to which the implementation of the present specification applies.

[0306] AAA-S may revoke and / or cancel the certification and authorization for S-NSSAI for which the certification and authorization procedures have already been performed, whenever it desires.

[0307] 1. AAA-S requests the revocation of authorization for the network slice specified by S-NSSAI within the AAA protocol revocation authorization request message for the UE identified by GPSI within the AAA protocol revocation authorization request message. This message is sent to AAA-P when AAA-P is used (e.g., AAA-S is owned by a third party).

[0308] 2. If AAA-P exists, forward the request to AUSF.

[0309] 3a-3b. AUSF obtains the AMF ID from the UDM using Nudm_UECM_Get along with the GPSI in the received AAA message.

[0310] 4. AUSF uses Nausf_NSSAA_Notify with GPSI and S-NSSAI in the received AAA message to notify AMF of the withdrawal permission event to revoke S-NSSAI permission for the UE.

[0311] 5. The AMF updates the UE configuration to revoke the corresponding S-NSSAI from the currently allowed NSSAI for all connection types where the NSSAA has been successfully executed on the S-NSSAI. The UE configuration update may include a registration request if the AMF needs to be reassigned. The AMF provides the UE with a new allowed NSSAI by removing the revoked S-NSSAI. The AMF provides the UE with a new denied NSSAI, including the revoked S-NSSAI. If, after revocation, no S-NSSAI remains in the allowed NSSAI for the connection and there is a default NSSAI that does not require network slice-specific permissions or requires network slice-specific permissions that have not previously failed on this connection, the AMF may provide the UE with a new allowed NSSAI, including the default NSSAI. If, after withdrawal, no S-NSSAI remains in the NSSAI allowed for the connection, and the primary NSSAI cannot be provided in the NSSAI allowed to the UE, or if a previous network slice-specific permission for the primary NSSAI on this connection has failed, the AMF performs the unregistration procedure initiated by the network for the connection. The UE includes a list of the denied S-NSSAIs with appropriate refusal cause values ​​in an explicit unregistration request message. If there are established PDU sessions associated with the withdrawn S-NSSAI, the AMF initiates the PDU session unregistration procedure with appropriate cause values ​​to unregister the PDU sessions.

[0312] As described in detail in FIGS. 8 through 11, the NSSAA procedure is a procedure in which a UE performs additional authentication and authorization for a specific network slice after successfully completing the initial authentication and authorization procedure with the network. When the UE performs a registration request, it informs the network (e.g., AMF) that the UE is a UE that supports the NSSAA function. The network (e.g., AMF) determines whether to perform the NSSAA procedure for the S-NSSAI for which the UE requested registration and performs the NSSAA procedure accordingly. If the NSSAA procedure fails, the network informs the UE of the failure of the NSSAA procedure and also informs the UE of the rejected NSSAI for the corresponding S-NSSAI via a UE configuration update command message. The S-NSSAI received through the rejected NSSAI remains stored in the UE's memory as a rejected NSSAI until the UE is powered off or the USIM is removed. Additionally, the use of the corresponding S-NSSAI is prohibited to prevent the PLMN that informed the UE of the rejected NSSAI from transmitting data using that S-NSSAI.

[0313] Meanwhile, AAA-S can trigger the NSSAA procedure for recertification and re-authorization for S-NSSAIs that have already successfully been certified and authorized. However, for S-NSSAIs that have been rejected due to the failure of the NSSAA procedure, the AMF cannot request certification through the NSSAA procedure.

[0314] Consequently, regarding S-NSSAIs included in NSSAIs that were rejected due to NSSAA procedure failures caused by reasons such as network errors or timeouts, the network does not perform the NSSAA procedure because the UE does not request it. Furthermore, since the network can only perform re-authentication on network slices for which authentication and authorization have already been completed, network slices rejected due to NSSAA failure cannot be the subject of re-authentication requests. Therefore, data transmission using network slices for which the NSSAA procedure failed is prohibited to this PLMN until the UE is powered off or the USIM is removed.

[0315] Meanwhile, in 5G systems, various types of devices, such as telematics devices running in vehicles, can serve as UEs in addition to traditional smartphones. For example, due to their nature, telematics devices running in vehicles may utilize semiconductor devices such as eSIM (embedded SIM) or eUICC (embedded universal integrated circuit card) rather than traditional removable MFF2-type USIM cards. Since these eSIMs or eUICCs are semiconductor devices, they cannot be removed. Furthermore, telematics devices are communication modules provided by the vehicle; as their typical use involves operating vehicle applications for theft prevention or rollover prevention while the vehicle is parked, the standard power input for telematics devices is the vehicle's own battery and / or an additional auxiliary battery. Therefore, it is difficult to turn off the power to the telematics device unless the vehicle is completely discharged. Moreover, even if the vehicle is completely discharged, power to the telematics device can be supplied through the additional auxiliary battery, making it even more difficult to turn off the power.

[0316] In summary, UEs—such as telematics devices where it is difficult to turn off the power or remove the USIM—can operate in 5G systems. For such UEs, there is a possibility that data transmission via an S-NSSAI that has experienced an NSSAA failure may be permanently impossible within the corresponding PLMN. In other words, even though the NSSAA procedure is highly likely to succeed after a certain period following an NSSAA failure caused by temporary network errors or the passage of time, once an NSSAA failure occurs for a specific S-NSSAI, data transmission using that S-NSSAI is prohibited until the UE is turned off or the USIM is removed; since it is difficult for the UE to turn off the power or remove the USIM, that S-NSSAI cannot be used. Consequently, an error handling method that allows the NSSAA procedure to be performed again only after the power is turned off or the USIM is removed for UEs that are difficult to turn off or remove the USIM, in the event of the same error as with a standard UE, can be quite dangerous.

[0317] Furthermore, the purpose of the NSSAA procedure is to grant network slice-specific authorization. AAA-S can perform authorization granting for each vehicle network slice, and such authorization granting may be based on network policies or network configuration options. For example, authorization for a network slice for GM V2X communication may be performed once a week. Alternatively, for example, authorization for a network slice for GM V2X communication may be performed whenever the application related to the GM V2X communication network slice on the corresponding UE is executed. In such cases, if the NSSAA for that network slice fails once, that network slice cannot be used until the next week arrives or until the application is executed again.

[0318] Therefore, in cases where the NSSAA procedure fails for a UE that cannot be recovered from errors via UE self-initialization because it is difficult to turn off the power or remove the USIM, and / or where the NSSAA procedure fails due to a network error, a method to re-perform the NSSAA procedure on the network slice where the procedure failed may be required.

[0319] According to an implementation of the present specification, if the UE requesting registration is a device that is difficult to enter a power cycle, such as a telematics device using an eSIM, etc., even if the NSSAA procedure fails for a specific S-NSSAI and the UE receives a rejected NSSAI containing said specific S-NSSAI from the AMF, the UE can subsequently transmit data in the same PLMN using said specific S-NSSAI.

[0320] According to an implementation of this specification, if a UE capable of performing an NSSAA re-authentication procedure informs the network of its capability to perform the NSSAA re-authentication procedure, the network (e.g., AMF) may transmit a rejected NSSAI with time information to the UE in the event of an NSSAA failure, depending on the UE's capability to perform the NSSAA re-authentication procedure and the cause of the NSSAA failure. Through this, the UE that receives the rejected NSSAI with time information may subsequently transmit data within the same PLMN via an S-NSSAI included in the rejected NSSAI that requests data transmission.

[0321] According to an implementation of this specification, when a UE requests network registration / connection, it may inform the network that the request is made by a UE having a characteristic that makes it difficult to enter a power cycle. Additionally, it may inform the network that the UE is capable of performing the NSSAA re-authentication procedure.

[0322] According to the implementation of this specification, a network (e.g., AMF) subsequently recognizes UEs that are difficult to enter a power cycle and those that are not. If it is determined that recovery is difficult by turning the power off and on in the UE in the event of an NSSAA procedure failure (i.e., for a UE that is difficult to enter a power cycle), the network may request the NSSAA re-authentication procedure for such UEs. In this case, the network may transmit the rejected NSSAI and time information together to UEs that are difficult to enter a power cycle, and transmit only the rejected NSSAI to UEs that are not. That is, different methods for handling rejected NSSAIs based on UE characteristics may be proposed for the network.

[0323] According to the implementation of the present specification, when a network transmits time information and an NSSAI rejected by a UE that has difficulty entering a power cycle, the network can configure the UE to transmit data even after a specific time.

[0324] According to an implementation of the present specification, a method of operation of a UE and a method of requesting network registration / connection by the UE may be proposed so that a UE that receives an NSSAI rejected due to an NSSAA failure attempts to transmit data to the corresponding network slice. A UE that receives the rejected NSSAI and time information may remove the S-NSSAI where the NSSAA failed from the rejected NSSAI after the time has elapsed.

[0325] The following drawings are prepared to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0326] FIG. 12 illustrates an example of a method performed by a UE to which the implementation of the present specification applies.

[0327] In step S1200, the method includes the step of transmitting a registration request message to an AMF. The registration request message includes a requested NSSAI. The requested NSSAI includes an S-NSSAI corresponding to the network slice for which the UE requests registration.

[0328] In some implementations, information indicating that the UE is a specific type of device may be transmitted to the AMF. The specific type of device may include at least one of a device capable of performing an NSSAA re-certification procedure and / or a device that is difficult to enter a power cycle.

[0329] In step S1210, the method includes the step of receiving a UE configuration update command message from the AMF. The UE configuration update command message includes a rejected NSSAI containing the S-NSSAI. Based on the failure of the NSSAA for the S-NSSAI, the UE configuration update command message includes time information associated with a timer.

[0330] In some implementations, the failure of the NSSAA for the first S-NSSAI may be due to a network issue. Such failure may correspond to a hypertext transfer protocol (HTTP) status code transmitted from the NSSAAF as "504 gateway timeout" and / or "5xx".

[0331] In some implementations, the time information may be transmitted from the AAA-S through the NSSAAF to the AMF for periodic NSSAA execution. Alternatively, in some implementations, the time information may be stored in the AMF or UDM as a network slice characteristic available for NSSAA failure for the S-NSSAI.

[0332] In step S1220, the method includes the step of adding the S-NSSAI to the rejected NSSAI.

[0333] In step S1230, the method includes the step of starting the timer based on the time information.

[0334] In step S1240, the method includes the step of deleting the S-NSSAI included in the rejected NSSAI after the timer expires.

[0335] In some implementations, after the timer expires, a second registration request message containing a requested NSSAI including the S-NSSAI may be transmitted to the AMF. Based on the success of the NSSAA for the first S-NSSAI, an allowed NSSAI including the first S-NSSAI may be received from the AMF.

[0336] In some implementations, the UE can communicate with at least one of a mobile device, a network, and / or an autonomous vehicle other than the UE.

[0337] Additionally, the method described in the view of the UE in FIG. 12 may be performed by the first wireless device (100) shown in FIG. 2, the wireless device (100) shown in FIG. 3, and / or the UE (100) shown in FIG. 4.

[0338] More specifically, the UE includes one or more transceivers, one or more processors, and one or more memories that can be connected to operate with said one or more processors. said one or more memories store instructions that cause the following operations to be performed by said one or more processors.

[0339] The above UE transmits a registration request message to the AMF. The registration request message includes a requested NSSAI. The requested NSSAI includes an S-NSSAI corresponding to the network slice for which the UE is requesting registration.

[0340] In some implementations, information indicating that the UE is a specific type of device may be transmitted to the AMF. The specific type of device may include at least one of a device capable of performing an NSSAA re-certification procedure and / or a device that is difficult to enter a power cycle.

[0341] The UE receives a UE configuration update command message from the AMF. The UE configuration update command message includes a rejected NSSAI containing the S-NSSAI. Based on the failure of the NSSAA for the S-NSSAI, the UE configuration update command message includes time information associated with a timer.

[0342] In some implementations, the failure of the NSSAA for the first S-NSSAI may be due to a network issue. Such failure may correspond to an HTTP status code "504 gateway timeout" and / or "5xx" transmitted from the NSSAAF.

[0343] In some implementations, the time information may be transmitted from the AAA-S through the NSSAAF to the AMF for periodic NSSAA execution. Alternatively, in some implementations, the time information may be stored in the AMF or UDM as a network slice characteristic available for NSSAA failure for the S-NSSAI.

[0344] The above UE adds the above S-NSSAI to the rejected NSSAI.

[0345] The above UE starts the timer based on the above time information.

[0346] The above UE deletes the S-NSSAI included in the rejected NSSAI after the timer expires.

[0347] In some implementations, after the timer expires, a second registration request message containing a requested NSSAI including the S-NSSAI may be transmitted to the AMF. Based on the success of the NSSAA for the first S-NSSAI, an allowed NSSAI including the first S-NSSAI may be received from the AMF.

[0348] Additionally, the method described in the view of the UE in FIG. 12 may be performed by the control of the processor (102) included in the first wireless device (100) shown in FIG. 2, the control of the communication device (110) and / or control device (120) included in the wireless device (100) shown in FIG. 3, and / or the control of the processor (102) included in the UE (100) shown in FIG. 4.

[0349] More specifically, a processing unit operating in a wireless communication system comprises one or more processors and one or more memories that can be connected to operate with said one or more processors. The one or more processors are configured to perform operations including: generating a registration request message, said registration request message comprising a requested NSSAI, said requested NSSAI comprising an S-NSSAI corresponding to a network slice for which the UE requests registration; obtaining a UE configuration update command message, said UE configuration update command message comprising a rejected NSSAI comprising the S-NSSAI, and based on the failure of the NSSAI for said S-NSSAI, said UE configuration update command message comprising time information associated with a timer; adding said S-NSSAI to the rejected NSSAI; starting said timer based on said time information; and, after the timer expires, deleting said S-NSSAI included in said rejected NSSAI.

[0350] Additionally, the method described in Fig. 12 from the perspective of the UE can be performed by software code (105) stored in the memory (104) included in the first wireless device (100) shown in Fig. 2.

[0351] The technical features of this specification may be implemented directly in hardware, in software executed by a processor, or in a combination of both. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or a combination thereof. For example, software may be in RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0352] Some examples of storage media may be coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may exist in an ASIC. In other examples, the processor and storage media may exist as separate components.

[0353] Computer-readable media may include non-transitory computer-readable storage media of a type.

[0354] For example, non-transient computer-readable media may include RAM such as SDRAM (synchronous dynamic RAM), ROM, non-volatile NVRAM (non-volatile RAM), EEPROM, flash memory, magnetic or optical data storage media, or other media that can be used to store instructions or data structures. Non-transient computer-readable media may include combinations of the above.

[0355] Additionally, the method described herein may be realized by a computer-readable communication medium that carries or communicates code in the form of at least partially instructions or data structures and can be accessed, read, and / or executed by a computer.

[0356] According to some implementations of this specification, a non-transient computer-readable medium (CRM) stores multiple commands.

[0357] More specifically, the CRM stores instructions for an operation to be performed by one or more processors. The operation comprises the steps of: generating a registration request message, wherein the registration request message includes a requested NSSAI, and the requested NSSAI includes an S-NSSAI corresponding to the network slice for which the UE requests registration; obtaining a UE configuration update command message, wherein the UE configuration update command message includes a rejected NSSAI containing the S-NSSAI, and based on the failure of the NSSAI for the S-NSSAI, the UE configuration update command message includes time information associated with a timer; adding the S-NSSAI to the rejected NSSAI; starting the timer based on the time information; and, after the timer expires, deleting the S-NSSAI included in the rejected NSSAI.

[0358] FIG. 13 shows another example of a method performed by a UE to which the implementation of the present specification applies.

[0359] In step S1300, the UE sends a registration request message to the AMF. The registration request message includes a requested NSSAI containing a specific S-NSSAI. Additionally, if the UE is a type of device where it is difficult to power off or remove the USIM, the UE informs the network that it is a UE capable of performing the NSSAA re-authentication procedure, which is a new capability of the UE, in order to request the NSSAA re-authentication procedure from the network.

[0360] In step S1302, the NSSAA procedure fails for the specific S-NSSAI mentioned above.

[0361] In step S1304, NSSAAF sends an HTTP status code to AMF as the cause of the NSSAA failure.

[0362] In step S1306, the AMF determines whether the UE is capable of performing the NSSAA re-authentication procedure and / or whether the HTTP status code corresponding to the cause of the NSSAA failure is "504 gateway timeout" or "5xx". If the HTTP status code is "504 gateway timeout" or "5xx", the AMF determines that the NSSAA failure was caused by a temporary network issue rather than an actual authentication failure.

[0363] In step S1308, if the UE is a UE that is unable to perform the NSSAA re-authentication procedure and / or the HTTP status code corresponding to the cause of the NSSAA failure is 4xx (e.g., "403 forbidden", "404 not found"), the AMF may send a UE configuration update command message containing only the NSSAI rejected to the UE.

[0364] In step S1308, if the UE is capable of performing the NSSAA re-authentication procedure and the HTTP status code is "504 gateway timeout" or "5xx", the AMF may send a UE configuration update command message to the UE containing the rejected NSSAI and time information.

[0365] If the UE receives a UE configuration update command message containing a rejected NSSAI and time information, in step S1312 the UE starts a timer according to the time information, and in step S1314 the UE includes / stores the S-NSSAI received through the rejected NSSAI in the rejected NSSAI.

[0366] When the timer expires in step S1316, the UE removes the corresponding S-NSSAI from the rejected NSSAI.

[0367] Subsequently, when requesting network registration / connection to perform data transmission through the corresponding S-NSSAI, in step S1320, the UE includes the corresponding S-NSSAI in the requested NSSAI. In step S1322, the UE transmits a registration request message containing the requested NSSAI to the AMF.

[0368] In step S1324, the AMF triggers the execution of the NSSAA procedure again. Accordingly, in step S1326, the NSSAA procedure succeeds.

[0369] In step S1328, the AMF informs the UE that the corresponding S-NSSAI is an allowed NSSAI. Subsequently, since the S-NSSAI corresponding to the allowed NSSAI has successfully requested registration, data transmission can be performed through the corresponding S-NSSAI in the network where the previous NSSAA failure occurred.

[0370] 1. First implementation

[0371] According to the first embodiment of the present specification, when a UE that has difficulty entering a power cycle requests network registration / connection, it may be informed that it has difficulty entering a power cycle. General IoT devices, such as unmanned meters, unmanned vending machines, and intelligent transportation services, have the characteristic of being able to autonomously share information with each other without human intervention, making it difficult to turn off the power or remove the USIM. Therefore, a UE having such IoT capabilities can be considered to have the characteristics of a UE that has difficulty entering a power cycle, and the IoT UE capability can be replaced with the features of the UE proposed in the present specification.

[0372] According to the first embodiment of this specification, the UE capability that the UE has difficulty entering a power cycle may correspond to cases where the UE has eMTC capability, the UE has NB-IoT capability, or the UE has Category 0 capability. Alternatively, the UE may have difficulty entering a power cycle when the UE has 5G CP (control plane) CIoT (cellular internet-of-things) or 5G UP (user plane) CIoT capability. The UE's AS layer informs the UE's NAS layer of the relevant radio capability that has difficulty entering a power cycle, and the UE's NAS layer may inform the AMF of the relevant capability. Alternatively, the gNB or eNB may inform the AMF of the relevant radio capability that has difficulty entering a power cycle, as informed by the UE's AS layer.

[0373] According to the first embodiment of this specification, a UE can indicate that it is a UE that is difficult to enter a power cycle by using a 5GMM capability information element (IE). For example, an indicator indicating that a UE is a UE that is difficult to enter a power cycle may be indicated by a new bit within the 5GMM capability IE included in a registration request message. Based on said indicator, the network may determine that the UE is difficult to enter a power cycle.

[0374] According to the first embodiment of the present specification, since a UE having the characteristic of being difficult to enter a power cycle is a UE capable of performing an NSSAA re-authentication procedure to the network when an NSSAA failure occurs, the UE can directly inform the network that it is a UE capable of performing an NSSAA re-authentication procedure, rather than through 5GMM capability or radio capability. To this end, the UE having the characteristic of being a UE capable of performing an NSSAA re-authentication procedure can inform the network when transmitting a registration request message by adding the capability of being a UE capable of performing an NSSAA re-authentication procedure to its UE capability.

[0375] 2. Second implementation

[0376] According to the second implementation of the present specification, for a UE capable of NSSAA re-authentication (i.e., a UE that has difficulty entering a power cycle) or a general UE, a method for configuring a UE and a method for utilizing relevant information between networks when transmitting a rejected NSSAI due to NSSAA failure may be proposed.

[0377] According to a second implementation of the present specification, a first network node (e.g., AMF) receives an HTTP status code corresponding to an application error and the cause of the NSSAA failure from a second network node (e.g., NSSAAF) upon NSSAA failure, and can determine whether there is a possibility of success if the NSSAA procedure is performed again even if an NSSAA failure occurs, based on the HTTP status code. More specifically, if the UE requesting registration is a UE capable of NSSAA re-authentication and the HTTP status code received from NSSAAF is 504 or 5xx, the AMF can determine that the NSSAA failure occurred due to a network problem.

[0378] Table 3 shows examples of application errors corresponding to the HTTP status code "504 gateway timeout". The application errors disclosed in Table 3 are merely examples, and the application errors corresponding to the HTTP status code "504 gateway timeout" may include application errors not disclosed in Table 3.

[0379] Application error HTTP status code explanation UPSTREAM_SERVER_ERROR 504 Gateway Timeout Error occurred in reaching the remote peer (i.e., AAA-S). NETWORK_FAILURE 504 Gateway Timeout The request was denied due to a network issue. TIMED_OUT_REQUEST 504 Gateway Timeout Failure to receive a response from the remote peer (i.e., AAA-S) after a period of time.

[0380] According to the second implementation of this specification, if the AMF determines that an NSSAA failure occurred due to a network problem (i.e., the HTTP status code received from the NSSAAF is 504 or 5xx), the AMF may determine that the NSSAA failure is not an actual authentication failure but a temporary NSSAA failure caused by a network problem. Additionally, the AMF may consider that there is a possibility that the NSSAA procedure will succeed if the NSSAA procedure is performed again.

[0381] According to a second implementation of the present specification, if a UE is a UE capable of NSSAA re-authentication and there is a possibility of success if the NSSAA procedure is performed again even if an NSSAA failure occurs (i.e., if the NSSAA failure is temporary due to a network issue), the AMF may inform the UE to perform the NSSAA procedure again for the relevant network slice. Specifically, if the UE is a UE capable of NSSAA re-authentication and the HTTP status code received from the NSSAAF is 504 or 5xx, the AMF may provide the UE with time information indicating when the network slice corresponding to the rejected NSSAI can request network registration again, along with the rejected NSSAI. That is, the time information may implicitly indicate to the UE that the NSSAA procedure can be performed again for the relevant network slice.

[0382] According to the second implementation of this specification, if the UE is a UE that is not capable of the NSSAA re-authentication procedure, the AMF may provide the UE with only the rejected NSSAI without time information indicating when the network slice corresponding to the rejected NSSAI can request network registration again upon NSSAA failure.

[0383] According to the second implementation of this specification, if the HTTP status code received from NSSAAF is not 504 or 5xx (e.g., "403 forbidden" or "404 not found"), the AMF may determine that performing the NSSAA procedure again would result in the same failure as before. Therefore, if the HTTP status code received from NSSAAF is not 504 or 5xx, the AMF may provide the UE with only the rejected NSSAI without time information indicating when the network slice corresponding to the rejected NSSAI can request network registration again upon NSSAA failure.

[0384] 3. Third implementation

[0385] According to a third implementation of the present specification, when a network determines that an NSSAA failure has occurred due to a network problem, a method may be proposed to provide backoff time information indicating when the rejected NSSAI and the network slice corresponding to the rejected NSSAI can request network registration again.

[0386] FIG. 14 illustrates an example of a method for providing backoff time information to which the third implementation of the present specification is applied.

[0387] Referring to FIG. 14, the basic structure of the network slice-specific re-authentication and re-authorization procedure initiated by AAA-S described in FIG. 10 is the same, but backoff time information is transmitted from AAA-S to AMF using the AAA protocol re-authentication request message, Nudm_UECM get, and Nausf_NSSAA_Notify.

[0388] According to a third implementation of this specification, when AAA-S periodically performs an NSSAA procedure, AAA-S may provide NSSAAF with backoff time information for periodically performing the NSSAA. NSSAAF may determine which AMF to use to perform re-authentication, and then transmit the backoff time information to the said AMF so that the UE can perform the NSSAA procedure using the said AMF.

[0389] According to the third implementation of the present specification, for a specific slice, an AMF or UDM may store a time value as a slice attribute after a specific time when network registration / connection is possible when an NSSAA failure occurs, and may use the said time value as the backoff time information.

[0390] According to the third implementation of the present specification, the value of the backoff time information may be 0, infinite, or a specific time value.

[0391] According to the third implementation of the present specification, subsequent NSSAA procedures may follow the procedures of FIGS. 8 and FIG. 9 described above.

[0392] FIG. 15 illustrates an example of a UE setting update procedure to which the third implementation of the present specification is applied.

[0393] 0. The AMF determines the need to update the UE's configuration or re-register it. For example, if an EAP failure occurs as a result of an NSSAA procedure, the AMF may determine to update the UE configuration for the S-NSSAI where the EAP failure occurred. For example, if an EAP success occurs as a result of an NSSAA procedure, the AMF may determine to update the UE configuration for the S-NSSAI where the EAP success occurred.

[0394] 1. The AMF sends a UE configuration update command message to the UE. Since the S-NSSAI of the network slice specific authentication result message is the HPLMN S-NSSAI, the AMF can change it to the serving S-NSSAI when sending the configuration update command message to the UE.

[0395] The UE configuration update command message includes not only the S-NSSAI but also backoff time information that allows the S-NSSAI to perform network registration / connection after a certain period of time without performing network registration / connection for a certain period of time. The backoff time information may be a value received from another network entity (e.g., received from AAA-S as described above in FIG. 14), or a value set by the AMF itself. The backoff time information may be a value determined by the network configuration or a value determined by the UE's specific slice policy.

[0396] Table 4 shows an example of a UE setting update command message containing backoff time information according to the third implementation of the present specification.

[0397] IEI Information Element Type / Reference Presence Format Length Extended protocol discriminator Extended protocol discriminator9.2 M V 1 Security header type Security header type9.3 M V 1 / 2 Spare half octet Spare half octet 9.5 M V 1 / 2 Configuration update command message identity Message type9.7 M V 1 D- Configuration update indication Configuration update indication9.11.3.18 O TV 1 77 5G-GUTI 5GS mobile identity9.11.3.4 O TLV-E 14 54 TAI list 5GS tracking area identity list9.11.3.9 O TLV 9-114 15 Allowed NSSAI NSSAI9.11.3.37 O TLV 4-74 27 Service area list Service area list9.11.3.49 O TLV 6-114 43 Full name for network Network name9.11.3.35 O TLV 3-n 45 Short name for network Network name9.11.3.35 O TLV 3-n 46 Local time zone Time zone9.11.3.52 O TV 2 47 Universal time and local time zone Time zone and time9.11.3.53 O TV 8 49 Network daylight saving time Daylight saving time9.11.3.19 O TLV 3 79 LADN information LADN information9.11.3.30 O TLV-E 3-1715 B- MICO indication MICO indication9.11.3.31 O TV 1 9- Network slicing indication Network slicing indication9.11.3.36 O TV 1 31 Configured NSSAI NSSAI9.11.3.37 O TLV 4-146 11 Rejected NSSAI Rejected NSSAI9.11.3.46 O TLV 4-42 76 Operator-defined access category definitions Operator-defined access category definitions9.11.3.38 O TLV-E 3-n F- SMS indication SMS indication9.11.3.50A O TV 1 6C T3447 value GPRS timer 39.11.2.5 O TLV 3 75 CAG information list CAG information list9.11.3.18A O TLV-E 3-n 67 UE radio capability ID UE radio capability ID9.11.3.68 O TLV 3-n 68 UE radio capability ID deletion indication UE radio capability ID deletion indication9.11.3.69 O TV 1 44 5GS registration result 5GS registration result9.11.3.6 O TLV 3 1B Truncated 5G-S-TMSI configuration Truncated 5G-S-TMSI configuration9.11.3.70 O TLV 3 XX Txxx value GPRS timer 29.11.2.4 O TLV 3

[0398] Referring to Table 4, the UE configuration update command message includes a "Txxx value" IE. This can correspond to the backoff time information mentioned above. That is, the "Txxx value" IE can indicate backoff time information that indicates when a network slice corresponding to a rejected NSSAI can request network registration again when an NSSAA failure occurs for a UE that has difficulty entering a power cycle. The "Txxx value" IE may be included in the UE configuration update command message only when the UE configuration update command message includes a rejected NSSAI where the cause value is "S-NSSAI unavailable due to failed or withdrawn NSSAA".

[0399] 4. Fourth implementation

[0400] According to the fourth implementation of the present specification, a method of operation of a UE and a method of requesting network registration / connection of a UE may be proposed for a UE that receives an NSSAI rejected due to an NSSAA failure to attempt data transmission through a network slice corresponding to the rejected NSSAI.

[0401] According to the fourth implementation of the present specification, if a UE receives backoff time information (e.g., "Txxx value" IE as described in Table 4) along with a rejected NSSAI due to an NSSAA failure, the UE may start a timer according to the backoff time information. If the UE receives a rejected NSSAI for a failed or withdrawn NSSAA with a cause value of "S-NSSAI is unavailable due to failed or withdrawn NSSAA" via a UE configuration update command message, the UE may start a timer by applying the backoff time information in the registered PLMN.

[0402] According to the fourth implementation of this specification, the UE may store the S-NSSAI included in the rejected NSSAI in the rejected NSSAI while the timer is operating, and delete the S-NSSAI from the rejected NSSAI when the timer expires. The rejected NSSAI may be stored in the UE's ME (mobile equipment). While the S-NSSAI is stored in the rejected NSSAI, data associated with the S-NSSAI existing within the rejected NSSAI cannot be transmitted to the corresponding PLMN. Therefore, while the timer is operating, data transmission through the network slice corresponding to the rejected NSSAI is impossible, and subsequently, after the timer expires, data transmission may become possible by deleting the S-NSSAI from the rejected NSSAI.

[0403] According to the fourth implementation of this specification, the timer may be applied to all S-NSSAIs included in the rejected NSSAI for the failed or withdrawn NSSAA within the UE configuration update command message. For example, if the rejected NSSAI within the UE configuration update command message includes S-NSSAI #1 and S-NSSAI #2, the timer may be applied to S-NSSAI #1 and S-NSSAI #2.

[0404] According to the fourth implementation of this specification, when a UE receives a new allowed NSSAI or a new configured NSSAI from a network, if there exists an S-NSSAI within the allowed NSSAI or configured NSSAI that is identical to the S-NSSAI stored in the rejected NSSAI for the failed or withdrawn NSSAA in a previously received UE configuration update command message, the UE may stop the timer associated with that S-NSSAI.

[0405] According to the fourth implementation of the present specification, when the timer expires, the UE removes the S-NSSAI from the rejected NSSAIs, so that when a network registration / connection is subsequently requested, the S-NSSAI may be included in the requested NSSAIs. If the S-NSSAI exists in the requested NSSAIs, the network determines that the UE is requesting a network registration / connection to use a network slice corresponding to the S-NSSAI, and may allocate a network slice to the S-NSSAI.

[0406] More specifically, when the timer expires, if the UE receives via a UE configuration update command message an S-NSSAI contained in a rejected NSSAI for a failed or withdrawn NSSAA whose cause value is "S-NSSAI is unavailable due to a failed or withdrawn NSSAA," and the UE has stored said S-NSSAI in the rejected NSSAI, the UE may delete said S-NSSAI contained in the rejected NSSAI for the failed or withdrawn NSSAA from the rejected NSSAI stored for PLMNs registered for all connection types.

[0407] 5. Fifth implementation

[0408] According to the fifth implementation of the present specification, the operation of the UE after the timer expires may be proposed.

[0409] According to the fifth implementation of this specification, after the timer expires, the UE may remove the S-NSSAI included in the rejected NSSAI from the rejected NSSAI and, when performing a network connection request for a new network slice, include the S-NSSAI in the requested NSSAI and transmit a registration request message to the network. Upon receiving the registration request message, the network may determine whether to perform NSSAA again on the S-NSSAI present in the requested NSSAI. If it is determined to perform NSSAA again, the NSSAA procedure may be performed again, and subsequently, the network may notify the UE of the S-NSSAI in the form of an allowed NSSAI or a rejected NSSAI through a UE configuration update command message. If the S-NSSAI is delivered to the UE via the allowed NSSAI, the UE may transmit data by establishing a PDN session by transmitting a PDU session repair request message to the network when data transmission is required in the future.

[0410] The various implementations of the present specification described above may operate individually, or one or more may be combined to operate in combination.

[0411] This specification may have various effects.

[0412] For example, for a UE where error recovery through UE self-initialization is difficult because the device characteristics make it difficult to turn off the power or remove the USIM, error recovery may be possible for an S-NSSAI that was rejected due to a temporary NSSAA failure.

[0413] For example, even if the NSSAA fails once, the rejected S-NSSAI can be used again after a certain period of time, so data transmission may be possible using the S-NSSAI that failed the NSSAA once, without moving to a new PLMN.

[0414] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0415] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

Claim 1 A method performed by a User Equipment (UE), wherein the method comprises: transmitting a registration request message to an Access Mobility Management Node containing first requested network slice selection assistance information; wherein the first requested network slice selection assistance information includes single network slice selection assistance information corresponding to a network slice that the UE intends to register; and receiving a configuration update command message containing first rejected network slice selection assistance information, wherein the first rejected network slice selection assistance information includes the single network slice selection assistance information based on a failure of network slice-specific authentication and authorization for the single network slice selection assistance information, and wherein the configuration update command message includes i) a failure of network slice-specific authentication and authorization for the single network slice selection assistance information, and ii) time information related to a timer based on the fact that the UE is a specific type of device, and wherein the specific type of device is capable of performing network slice-specific re-authentication based on the fact that the UE cannot be powered off. A device; a step of storing the single network slice selection help information in the second rejected network slice selection help information; a step of starting the timer based on the time information; and a step of deleting the single network slice selection help information stored in the second rejected network slice selection help information after the expiration of the timer. Claim 2 A method according to claim 1, characterized in that information related to the specific type of device is included in the registration request message. Claim 3 delete Claim 4 A method according to claim 1, characterized in that the failure of the network slice-specific authentication and authorization for the single network slice selection assistance information is a failure caused by a network problem. Claim 5 A method according to claim 4, wherein a failure due to a problem in the network is characterized in that an HTTP (hypertext transfer protocol) status code transmitted from a network slice-specific authentication and authorization node corresponds to "504 gateway timeout" and / or "5xx". Claim 6 A method according to claim 1, characterized in that, after the expiration of the timer, a second registration request message including second requested network slice selection help information including the single network slice selection help information is transmitted to the connection mobility management node. Claim 7 A method according to claim 6, characterized in that allowed network slice selection assistance information including the single network slice selection assistance information is received from the connection mobility management node based on the success of the network slice specific authentication and authorization for the single network slice selection assistance information. Claim 8 A method according to claim 1, characterized in that the time information is transmitted from the AAA-S (authentication, authorization and accounting server) to the access mobility management node via a network slice-specific authentication and authorization node. Claim 9 A method according to claim 1, characterized in that the time information is stored in the connection mobility management node or unified data management (UDM) as a network slice characteristic available for failure of network slice-specific authentication and authorization for the single network slice selection help information. Claim 10 A method according to claim 1, characterized in that the UE communicates with at least one of a mobile device, a network, or an autonomous vehicle other than the UE. Claim 11 The UE (User Equipment) is: one or more transceivers; one or more processors; and includes one or more memories capable of storing instructions and being connected to operate with said one or more processors, and the operation performed based on said instructions being executed by said one or more processors is: transmitting a registration request message containing first requested network slice selection assistance information to an access mobility management node, said first requested network slice selection assistance information including single network slice selection assistance information corresponding to a network slice that said UE intends to register; and receiving a configuration update command message containing first rejected network slice selection assistance information, said first rejected network slice selection assistance information including said single network slice selection assistance information based on a failure of network slice-specific authentication and authorization for said single network slice selection assistance information, and said configuration update command message including i) a failure of said network slice-specific authentication and authorization for said single network slice selection assistance information, and ii) a timer and based on said UE being a specific type of device It includes related time information, and is a device capable of performing network slice-specific re-authentication based on the fact that the specific type of device cannot turn off the power of the UE;A UE comprising: a step of storing the single network slice selection help information in the second rejected network slice selection help information; a step of starting the timer based on the time information; and a step of deleting the single network slice selection help information stored in the second rejected network slice selection help information after the expiration of the timer. Claim 12 A UE according to claim 11, characterized in that information related to the specific type of device is included in the registration request message. Claim 13 In claim 11, the failure of the network slice-specific authentication and authorization for the single network slice selection assistance information is a failure due to a network problem, and the failure due to the network problem is characterized by the fact that the HTTP (hypertext transfer protocol) status code transmitted from the network slice-specific authentication and authorization node corresponds to "504 gateway timeout" and / or "5xx". Claim 14 A UE according to claim 11, wherein, after the expiration of the timer, a second registration request message including second requested network slice selection assistance information including the single network slice selection assistance information is transmitted to the access mobility management node, and allowed network slice selection assistance information including the single network slice selection assistance information is received from the access mobility management node based on the success of network slice specific authentication and authorization for the single network slice selection assistance information. Claim 15 A processing unit configured to control a UE (User Equipment) comprises: one or more processors; and includes one or more memories that can be connected to operate with the one or more processors, wherein the one or more processors generate a registration request message including first requested network slice selection assistance information, wherein the first requested network slice selection assistance information includes single network slice selection assistance information corresponding to a network slice that the UE intends to register; and obtain a configuration update command message including first rejected network slice selection assistance information, wherein the first rejected network slice selection assistance information includes the single network slice selection assistance information based on the failure of network slice specific authentication and authorization for the single network slice selection assistance information, and the configuration update command message includes i) the failure of the network slice specific authentication and authorization for the single network slice selection assistance information, and ii) time information related to a timer based on the fact that the UE is a specific type of device, and performs network slice specific re-authentication based on the fact that the specific type of device cannot turn off the power of the UE. A device capable of doing so; a step of storing the single network slice selection help information in the second rejected network slice selection help information; a step of starting the timer based on the time information;A processing device configured to perform an operation including the step of deleting the single network slice selection help information stored in the second rejected network slice selection help information after the expiration of the timer.; Claim 16 delete

Images