Access control method

Abstract

The present disclosure provides a method. The method comprises the steps in which: a UE transmits a registration request message to an AMF; and the UE receives a first message from the AMF, wherein the first message includes access control information, and the access control information includes information related to time and / or region.

Description

Access control methods

[0001] This specification relates to mobile communication.

[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] Access control of the terminal is performed through RAT control information for a specific PLMN.

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

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

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

[0009] Figure 4 is a structural diagram of a next-generation mobile communication network.

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

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

[0012] FIGS. 8 and 9 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0013] FIG. 10 illustrates a first example of a procedure according to the disclosure of the present specification.

[0014] FIG. 11 illustrates a second example of a procedure according to the disclosure of the present specification.

[0015] FIG. 12 shows a first example of information of a SoR transparent container according to the disclosure of the present specification.

[0016] FIG. 13 shows a second example of information of a SoR transparent container according to the disclosure of the present specification.

[0017] FIG. 14 shows an example of RAT control information according to the disclosure of the present specification.

[0018] FIG. 15 shows an example of the format of RAT control information according to the disclosure of the present specification.

[0019] FIG. 16 shows an example of RAT control information according to the disclosure of the present specification.

[0020] FIG. 17 shows an example of coding of RAT control information according to the disclosure of the present specification.

[0021] FIG. 18 illustrates the procedure of the UE for the disclosure of the present specification.

[0022] FIG. 19 illustrates the procedure of the AMF for the disclosure of the present specification.

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

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

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

[0026] 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."

[0027] 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."

[0028] 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."

[0029] 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."

[0030] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

[0058] As described above, the numerical values ​​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).

[0059] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

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

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

[0062] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {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. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

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

[0064] 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). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

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

[0066] 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 firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

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

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

[0069] 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). Additionally and / or alternatively, the memory (204) may be placed outside the processing chip (201).

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

[0071] 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 firmware and / or software code (205) that implements instruction code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

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

[0073] 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), one or more SDUs (service data units), 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) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart 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 description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0074] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. 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). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

[0075] 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 random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile 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.

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

[0077] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, one or more transceivers (106, 206) may include 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).

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

[0079] Although not illustrated in FIG. 2, the wireless device (100, 200) may include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

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

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

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

[0083] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0084] The UE (100) includes a processor (102), memory (104), transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0085] 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 DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), 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.

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

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

[0088] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0089] The display (143) outputs the result processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0090] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) 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.

[0091] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0092] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0093] 5GC (5G Core) may include various components, and FIG. 5 includes some of them, such as AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0094] The UE (100) is connected to the data network via the UPF (440) through the NG-RAN (Next Generation Radio Access Network) including the gNB (20).

[0095] The UE (100) can also receive data services through untrusted non-3GPP access, such as a WLAN (Wireless Local Area Network). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0096] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G systems. When the UE (100) is connected to non-3GPP access (e.g., WiFi referred to as IEEE 801.11), the UE (100) can be connected to the 5G system through the N3IWF (490). The N3IWF (490) performs control signing with the AMF (410) and connects to the UPF (440) via the N3 interface for data transmission.

[0097] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

[0098] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communication.

[0099] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains the data path between the gNB (20) and the SMF (420). Additionally, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform the function of handling PDUs. For mobility within the NG-RAN (Next Generation Radio Access Network defined in 3GPP Release-15 or later), packets can be routed through the UPF. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined prior to 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0100] The illustrated PCF (430) is a node that controls the operator's policy.

[0101] The illustrated AF (450) is a server for providing various services to the UE (100).

[0102] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home subscriber Server) of 4th generation mobile communication. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0103] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

[0104] For reference, the reference numerals for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0105] Fifth-generation mobile communication 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 environments, 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.

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

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

[0108] - AUSF (Authentication Server Function)

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

[0110] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0111] - USDF (Unstructured Data Storage Function)

[0112] - NEF (Network Exposure Function)

[0113] - I-NEF (Intermediate NEF)

[0114] - NRF (Network Repository Function)

[0115] - NSSF (Network Slice Selection Function)

[0116] - PCF (Policy Control Function)

[0117] - SMF (Session Management Function)

[0118] - UDM (Unified Data Management)

[0119] - UDR (Unified Data Repository)

[0120] - UPF (User Plane Function)

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

[0122] - AF (Application Function)

[0123] - UE (User Equipment)

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

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

[0126] - NWDAF (Network Data Analytics Function)

[0127] - CHF (CHarging Function)

[0128] In addition, the following network functions may be considered.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0152] - 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)

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

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

[0155] <Registration Procedure>

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

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

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

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

[0160] - Mobility registration update; or

[0161] - Periodic registration update; or

[0162] - Emergency registration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0214] <PDU 세션 수립 절차>

[0215] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0216] FIGS. 8 and 9 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0217] PDU session establishment may fall under the following:

[0218] - Procedure for establishing a PDU session initiated by the UE

[0219] - PDU session handover between 3GPP and non-3GPP initiated by the UE

[0220] - PDU session handover from EPS initiated by UE to 5GS.

[0221] - Procedure for establishing a PDU session triggered by the network

[0222] A PDU session may (a) be associated with a single access type at any given time, namely either a 3GPP access or a non-3GPP access, or (b) be associated with multiple access types simultaneously, namely one 3GPP access and one non-3GPP access. A PDU session associated with multiple access types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) enabled UE.

[0223] Figures 8 and 9 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0224] In the procedure shown in Figures 8 and 9, since the UE is already registered with the AMF, it is assumed that the AMF has already retrieved user subscription data from the UDM unless the UE is urgently registered.

[0225] First, the procedure of Fig. 8 will be explained.

[0226] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0227] The UE initiates the PDU session establishment procedure requested by the UE by transmitting a NAS message containing a PDU session establishment request message within an N1 SM container. The PDU session establishment request message includes a PDU session ID, a requested PDU session type, a requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), an SM PDU DN Request Container, and a UE Integrity Protection Maximum Data Rate.

[0228] If the PDU session establishment is a request to establish a new PDU session, the request type indicates "Initial Request". If the request refers to an existing PDU session transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN (packet data network) connection in the EPC, the request type indicates "Existing PDU Session". If the PDU session establishment is a request to establish a PDU session for an emergency service, the request type indicates "Emergency Request". If the request refers to an existing PDU session for an emergency service transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for an emergency service in the EPC, the request type indicates "Existing Emergency PDU Session".

[0229] The UE includes an S-NSSAI from the allowed NSSAI of the current connection type. If a Mapping of Allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the visited VPLMN from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI.

[0230] (2) Step 2: The AMF selects an SMF. If the request type indicates an "initial request" or if the request is due to a handover from a non-3GPP connection provided by an EPS or another AMF, the AMF stores the connection type of the PDU session, as well as the association of the S-NSSAI(s), the DNN (data network name), the PDU session ID, and the SMF ID.

[0231] If the request type is "Initial Request" and the message also includes a previous PDU session ID representing an existing PDU session, the AMF selects an SMF and saves the new PDU session ID, S-NSAI(s), and the association of the selected SMF ID.

[0232] If the request type indicates an "existing PDU session," the AMF selects an SMF based on the SMF-ID received from the UDM. The AMF updates the connection type stored for the PDU session.

[0233] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

[0234] - If the SMF ID corresponding to the PDU session ID and the AMF belong to the same PLMN;

[0235] - If the SMF ID corresponding to the PDU session ID belongs to the HPLMN;

[0236] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0237] AMF rejects requests from urgently registered UEs where the request type does not indicate "Urgent Request" or "Existing Urgent PDU Session".

[0238] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0239] The AMF transmits the S-NSSAI of the serving PLMN from the allowed NSSAI to the SMF. For a local breakout (LBO) roaming scenario, the AMF also transmits the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI to the SMF.

[0240] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

[0241] If a UE in a restricted service state is registered for emergency services without providing a SUPI, the AMF provides a PEI instead of a SUPI. If a UE in a restricted service state is registered for emergency services while providing a SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI from a UE or if the AMF indicates that the SUPI is not authenticated, the UE is determined to be unauthenticated.

[0242] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the H-PCF (home PCF) in the non-roaming case and the V-PCF (visited PCF) in the LBO roaming case.

[0243] (4) Step 4: If session management subscription data for S-NSSAI of the corresponding SUPI, DNN, HPLMN is unavailable, the SMF can retrieve the session management subscription data from the UDM and be notified when this subscription data is modified.

[0244] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF in accordance with the request received in Step 3.

[0245] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0246] If the SMF decides not to accept the establishment of a PDU session, the SMF rejects the UE request via a NAS SM signal containing the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and that the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.

[0247] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0248] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0249] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

[0250] (8) Step 8: SMF selects one or more UPFs.

[0251] (9) Step 9: SMF can provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by SMF.

[0252] (10) Step 10: If the request type indicates an “initial request,” the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

[0253] In step 10a, SMF can send an N4 session establishment / modification request to UPF and provide packet detection, enforcement, and reporting rules installed in UPF for the PDU session. In step 10b, UPF can confirm by sending an N4 session establishment / modification response.

[0254] (11) Step 11: SMF sends an N1N2 message transfer message (e.g., Namf_Communication_N1N2 Message Transfer) to AMF.

[0255] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

[0256] - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session;

[0257] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0258] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

[0259] - S-NSSAI with a value for the serving PLMN (i.e., HPLMN S-NSSAI, or VPLMN S-NSSAI in the case of LBO roaming);

[0260] - User plane security enforcement information determined by SMF;

[0261] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0262] - RSN (redundancy sequence number) parameter

[0263] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0264] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

[0265] If PDU session establishment fails between steps 5 and 11, the N1N2 message delivery message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. (R)AN sends a NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0266] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0267] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0268] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

[0269] If N2 SM information is not included in step 11, steps 14–16b and step 17 below are omitted.

[0270] Now, the procedure of Fig. 9 following the procedure of Fig. 8 is explained.

[0271] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

[0272] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

[0273] (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and the corresponding forwarding rule to UPF.

[0274] (16b) Step S16b: UPF provides the N4 session modification response to SMF.

[0275] After this step, UPF can deliver the DL packet that may have been buffered for this PDU session to the UE.

[0276] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF can register with the UDM for the given PDU session.

[0277] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0278] After this step, AMF delivers the relevant events subscribed to by SMF.

[0279] (18) Step 18: At any time after Step 5, if the establishment of the PDU session fails during the procedure, the SMF may notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF may also release the created N4 session, the assigned PDU session address (e.g., IP address), and, if possible, release the association with the PCF. In this case, Step 19 below is omitted.

[0280] (19) Step 19: For PDU session type IPv6 or IPv4v6, the SMF can generate an IPv6 Router Advertisement and send it to the UE.

[0281] (20) Step 20: SMF can perform SM policy association modifications initiated by SMF.

[0282] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0283] <RAT (Radio Access Technology) 제한 (restriction)>

[0284] The implementation of RAT utilization restrictions is currently being discussed.

[0285] To restrict RATs, it is necessary to discuss the precise definition and scope of RATs for control purposes. Additionally, discussions are needed regarding which layers (e.g., NAS, AS (RRC), upper layers than NAS) require support for RAT restriction operations.

[0286] RAT restrictions defined in the current standard are possible through handover or redirection procedures only when the terminal is in the CM-CONNECTED state. In this case, information regarding RAT restrictions applied by the network is not provided to the terminal.

[0287] In situations restricted by RAT restrictions, subscription-based terminals are not allowed access to the corresponding PLMN. In the case of 3GPP access and CM-CONNECTED status, during the handover (or redirection) procedure, the radio access network may determine the target RAT and target PLMN by taking into account the RAT restrictions.

[0288] UDM can provide AMF with information on subscribers' NR or E-UTRA access restrictions.

[0289] The UDM may provide the AMF with information regarding restrictions on a subscriber's NR or E-UTRA access. For example, these restrictions may have been determined by the operator based on subscription scenarios and roaming scenarios:

[0290] - In the case of NR, NR is not allowed as a default RAT, but the NR categories listed below may still be allowed.

[0291] - In the case of NR, NR may not be allowed as a secondary RAT.

[0292] - In the case of NR, NR in unlicensed bands may not be allowed as the default RAT.

[0293] - In the case of NR, NR in the unlicensed band may not be allowed as a secondary RAT.

[0294] - In the case of NR, NR(LEO) satellite access may not be allowed as the default RAT.

[0295] - In the case of NR, NR(MEO) satellite access may not be allowed as the default RAT.

[0296] - In the case of NR, NR(GEO) satellite access may not be allowed as the default RAT.

[0297] - In the case of NR, NR(OTHERSAT) satellite access may not be allowed as the default RAT.

[0298] - In the case of NR, NR RedCap may not be allowed as the default RAT.

[0299] - In the case of NR, NR eRedCap may not be allowed as the default RAT.

[0300] - In the case of E-UTRA, E-UTRA may not be allowed as a basic RAT.

[0301] - In the case of E-UTRA, E-UTRA may not be allowed as a secondary RAT.

[0302] - In the case of E-UTRA, E-UTRA in the unlicensed band may not be permitted as a secondary RAT.

[0303] - In the case of E-UTRA, NB-IoT may not be allowed as the default RAT.

[0304] - In the case of E-UTRA, LTE-M may not be allowed as the default RAT.

[0305] - In the case of E-UTRA, WB-E-UTRAN (LEO) satellite access may not be allowed as primary access.

[0306] - In the case of E-UTRA, WB-E-UTRAN (MEO) satellite access may not be allowed as primary access.

[0307] - In the case of E-UTRA, WB-E-UTRAN (GEO) satellite access may not be allowed as primary access.

[0308] - In the case of E-UTRA, WB-E-UTRAN(OTHERSAT) satellite access may not be allowed as primary access.

[0309] - In the case of E-UTRA, NB-IoT (LEO) satellite access may not be allowed as primary access.

[0310] - In the case of E-UTRA, NB-IoT (MEO) satellite access may not be allowed as primary access.

[0311] - In the case of E-UTRA, NB-IoT (GEO) satellite access may not be allowed as primary access.

[0312] - In the case of E-UTRA, NB-IoT (OTHERSAT) satellite access may not be allowed as primary access.

[0313] - In the case of E-UTRA, LTE-M (LEO) satellite access may not be allowed as primary access.

[0314] - In the case of E-UTRA, LTE-M (MEO) satellite access may not be allowed as primary access.

[0315] - In the case of E-UTRA, LTE-M(GEO) satellite access may not be allowed as primary access.

[0316] - In the case of E-UTRA, LTE-M (OTHERSAT) satellite access may not be allowed as the primary access.

[0317] To apply all default RAT restrictions, RATs may be deployed across different Trace Zone Codes (TAs). Subscribers may be denied access to the network in a TA using a specific RAT.

[0318] If all secondary RAT restrictions apply, the subscriber may not be permitted to use the RAT as a secondary RAT.

[0319] RAT types (e.g., NR, NB-IOT, Untrusted Non-3GPP, Trusted Non-3GPP, Trusted IEEE 802.11 Non-3GPP access, Wireline, Wireline-Cable, Wireline-BBF, etc.) identify the transmission technology used in the access network for both 3GPP access and non-3GPP access.

[0320] LTE-M is a 3GPP RAT type identifier used only in the core network, a subtype of the E-UTRA RAT type, and is defined to identify E-UTRA in the core network when used by a UE representing category M.

[0321] NR RedCap is a 3GPP RAT type identifier used only in the core network, a subtype of the NR RAT type, and is defined to identify NR in the core network when used by a UE representing NR RedCap.

[0322] NR eRedCap is a 3GPP RAT type identifier used only in the core network, a subtype of the NR RAT type, and is defined to identify NR in the core network when a UE uses NR eRedCap.

[0323] The default RAT is the RAT of the master RAN node when using duplex linkage. Otherwise, it is the RAT of the RAN node.

[0324] The secondary RAT is the RAT of the secondary RAN node.

[0325] The network can determine whether to permit / authenticate connectivity requests to the core network and RAN nodes based on the terminal's subscription information.

[0326] Authorization for services (e.g., Operator Determined Barring, Roaming restrictions, Access Type and RAT Type currently in use) that the user is allowed to access based on the subscriber's 5GC connection authorization and subscription is evaluated after the user is successfully identified and authorized. This authorization is performed during the UE registration process.

[0327] To ensure that the UE initiates the mobility registration process when moving to or from NB-IoT to a RAT, the Tracking Area (TA) must not simultaneously contain NB-IoT cells and other RAT cells (e.g., WB-E-UTRA, NR), and the AMF must not assign a TAI list that simultaneously contains NB-IoT TAs and other RAT TAs.

[0328] For TAs that support one or more RATs, the current network may not differentiate the TAI list based on the RAT, thereby avoiding signaling overhead for Mobility Registration Updates. However, NB-IoT RATs may be an exception.

[0329] To prevent additional signal load caused by Mobility Registration Updates that occur whenever a RAT is changed, a per-RAT TAI list may not be generated for UEs that support two or more RATs.

[0330] For 3GPP access, based on the global RAN node ID connected to the N2 interface and the TA specified in NG-RAN, the AMF can determine the type of RAT the UE is camping on.

[0331] AMF can also determine more accurate RAT type information based on additional information received from NG-RAN:

[0332] - AMF can determine the RAT type as LTE-M.

[0333] - AMF can determine the RAT type using the unlicensed band as NR.

[0334] - AMF can determine the RAT type as one of the satellite access RAT types.

[0335] - AMF can determine the RAT type as NR RedCap.

[0336] For non-3GPP access, the AMF can determine the type of RAT the UE is camping based on the 5G-AN node connected to the N2 interface as follows:

[0337] - If the 5G-AN node has a global N3IWF node ID, the RAT type is untrusted non-3GPP.

[0338] - If the 5G-AN node has a global TNGF node ID or a global TWIF node ID, the RAT type is trusted non-3GPP.

[0339] - If a 5G-AN node has a global W-AGF node ID corresponding to a W-AGF that supports a Wireline BBF Access Network, the RAT type is Wireline-BBF. If a 5G-AN node has a global W-AGF node ID corresponding to a W-AGF that supports a Wireline Cable Access Network, the RAT type is Wireline-Cable. If the two types cannot be distinguished, the RAT type is Wireline.

[0340] Conventionally, when a UE that supports access to a specific RAT is not allowed access based on subscription information, the network can reject the UE's access attempt. In this case, signaling overhead occurs, and service continuity issues may arise.

[0341] - Cause #12 (TA not allowed): In a TA where the HPLMN or SNPN determines that operation is not allowed based on the UE's subscription, if the UE requests a service or the network initiates a deregistration request, this 5GMM cause may be transmitted to the UE.

[0342] - Cause #15 (No suitable cell for TA): If, in a TA where operation is not permitted based on subscription, the UE requests service or the network initiates a deregistration request, but another permitted TA must be found in the same PLMN or equivalent PLMN or the same SNPN or equivalent SNPN, this 5GMM cause may be transmitted to the UE.

[0343] Cause #12 may not trigger the UE to search for a different allowed TA in the same PLMN or SNPN. Cause #15 may be different.

[0344] - Cause #27 (N1 mode not allowed): If a UE requests service or a network initiates a deregistration request on a PLMN or SNPN where the UE cannot operate in N1 mode according to subscription or operator policy, this 5GMM cause may be transmitted to the UE.

[0345] - Cause #14 (EPS service not allowed in this PLMN): In a PLMN that does not provide EPS service roaming to the UE, if the UE requests the service or the network initiates a disconnection request, this 5GMM cause may be transmitted to the UE.

[0346] Since only one list of PLMNs for which packet service is forbidden is maintained in the UE, "forbidden PLMNs for GPRS service" is the maintained list, and the PLMNs for which EPS service is forbidden may be the same as this list.

[0347] - Cause #25 (Unauthorized access to this CSG): In a CSG cell with a CSG ID (where the UE has no subscription to operate in this CSG cell or the subscription has expired and must find another cell in the same PLMN or an equivalent PLMN), this EMM cause may be sent to the UE when the UE requests access or the network initiates a disconnection request.

[0348] Therefore, when attempting to register with the network, a method is needed to prevent the UE from attempting access from RATs that are not permitted to it. For example, discussions regarding the following may be necessary:

[0349] - How to deliver RAT control information to the terminal

[0350] - How the terminal receiving this RAT control information will operate, whether to support it solely through NAS layer operations, or to transmit the information to the AS layer so that the AS layer also uses RAT permission information when selecting a cell.

[0351] - If the RAT information allowed to the UE changes due to subsequent changes in subscription information, etc., how can the UE re-enable and use the RAT?

[0352] When receiving RAT control information proposed by the terminal, the terminal operation management method may be composed of a combination of one or more operations / configurations / steps described in this specification.

[0353] In this specification, RAT control information may have the same meaning as RAT restriction information.

[0354] In this specification, RAT control, RAT utilization, access technology utilization, access technology utilization control, access technology, RAT type, and access control may have the same meaning.

[0355] For example, RAT control information, RAT utilization information, access technology utilization information, access technology utilization control information, access technology information, RAT type information, and access control information may have the same meaning.

[0356] In this specification, RAT control information may be used for cell selection / cell reselection / PLMN selection of the terminal.

[0357] In this specification, the terminal may not be allowed to access a RAT restricted to a PLMN to which RAT control information is applied (a restricted RAT included in the RAT control information).

[0358] In this specification, RAT control information may be applied restrictively to a specific area (e.g., PLMN, tracking area, registration area, service area, cell, geographical area, etc.) or restricted to a specific time.

[0359] The RAT control information in this specification may refer to RAT restriction information that an operator has restricted the use of in a specific PLMN. For example, when connecting to PLMN-A, a UE may be allowed to connect via E-UTRAN but restricted from connecting via an NR satellite network.

[0360] The RAT control information of this specification may include not only RATs currently distinguished at the AS layer, but also all terms distinguished in relation to radio access, such as RAT types and access types used at the NAS layer or core network.

[0361] For example, RAT control information may be a PLMN identifier and a list of RATs allowed (or restricted) for use in that PLMN.

[0362] For example, RAT control information can be interpreted as control information for RAT utilization.

[0363] RAT control information may apply restrictions on specific areas (e.g., PLMN, TA (tracking area), registration area, service area, cell, geographical area, etc.) and / or restrictions on specific times. RAT control information may include restriction information on specific areas and / or restriction information on specific times.

[0364] For example, the RAT control information in this specification may refer to allowed RAT information that the operator has permitted for use in a specific PLMN.

[0365] Radio Access Technology (RAT) in this specification is not limited to RAT associated with Radio access capability mentioned in TS 38.304 v18.3.0 or TS 36.304 v18.2.0, and may also include RAT types distinguished by RAT type value specified in TS 29.274 v18.7.0.

[0366] This specification describes the proposed content. For operations and procedures related to NAS signal reception, AS signal reception, cell (re)selection, and PLMN selection, including basic SoR information reception, we will refer to TS 24.501 v18.8.0, TS 38.304 v18.3.0, and TS 23.122 v18.8.0.

[0367] I. Receiving RAT control information restricted (or permitted) for specific PLMN / region / time

[0368] RAT control information may be information about content that is restricted (or allowed) for use in a specific PLMN.

[0369] RAT control information can be pre-configured on the terminal.

[0370] RAT control information can be transmitted to the terminal via RRC signaling, NAS signaling, or UICC (Universal Integrated Circuit Card).

[0371] RAT control information may be transmitted to the terminal along with a specific timer value. In this case, the terminal may perform an operation using the corresponding RAT control before the timer expires (or until the timer is stopped by a specific event).

[0372] For example, the terminal can perform an operation based on the RAT control information until the timer received along with the RAT control information expires (when the timer starts and the time corresponding to the received timer value expires). For example, when the timer received along with the RAT control information expires, the RAT control information may no longer be valid.

[0373] RAT control information can be transmitted to the terminal without a specific timer value. The terminal can apply the RAT control information by applying a preset value. Alternatively, the terminal can disable the RAT control information by applying a preset value.

[0374] RAT control information can be transmitted to the terminal along with specific area information.

[0375] Specific area information may be area information to which RAT control is applied. For example, specific area information may be information such as PLMN, TA, registration area, service area, cell, geographical area, etc.

[0376] RAT control information may be transmitted to a terminal without specific region information. In this case, the terminal may apply the RAT control information to a registered PLMN or a serving PLMN.

[0377] 1. The terminal receives RAT control information for a specific PLMN via a registration approval, registration rejection, deregistration request, or configuration update message.

[0378] RAT control information can be transmitted to the terminal in the form of conveying Restricted RAT or Allowed RAT for a specific region / time.

[0379] For example, the terminal can receive RAT control information through NAS signaling, such as a registration approval message, a registration rejection message, a deregistration request message, or a configuration update message.

[0380] RAT control information can be composed of RAT information for PLMN as shown in Fig. 14.

[0381] RAT control information can be transmitted in a bitmap format as shown in Fig. 15.

[0382] The following drawings are made 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.

[0383] FIG. 10 illustrates a first example of a procedure according to the disclosure of the present specification.

[0384] The terminal can receive RAT control information through a registration approval message or a configuration update command.

[0385] The registration approval message may include access control-related information elements (IEs) (e.g., RAT control IE, access technology utilization control). The type of the RAT control IE may be Restricted RAT (or Allowed RAT). The format of the RAT control IE may be a TLV (Type / Length / Value).

[0386] The terminal can receive RAT control information in both the registration approval and configuration update commands. In this case, the RAT control information included in the message transmitted later in time (e.g., configuration update command) can replace the RAT control information included in the message transmitted earlier (e.g., registration approval).

[0387] Here, the registration approval and setting update commands are merely examples, and each message can be one of a registration approval message, a registration rejection message, a deregistration request message, and a setting update message.

[0388] 2. Through the SoR transparent container, the terminal receives RAT control information for a specific PLMN.

[0389] The following drawings are made 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.

[0390] FIG. 11 illustrates a second example of a procedure according to the disclosure of the present specification.

[0391] Based on the terminal's registration request, the UDM can transmit PLMN-specific RAT control information (or access control information) to the SOR-AF.

[0392] UDM can send SoR request messages to SOR-AF.

[0393] SOR-AF can send SoR response messages to UDM.

[0394] The SoR response message may include RAT control information (PLMN / RAT restriction information list) (or access control information).

[0395] Based on the SoR response message, the UDM can send SoR information and RAT control information (PLMN / RAT restriction information list) (or access control information) to the AMF.

[0396] The PLMN / RAT restriction information list may include a list of PLMNs and / or a list of RAT information restricted (or allowed) in each PLMN.

[0397] Based on this, the AMF may transmit a registration approval message to the terminal containing the relevant RAT control information (PLMN / RAT restriction information list) (or access control information). The RAT control information (PLMN / RAT restriction information list) (or access control information) may be delivered to the terminal through the SoR transparent container of the registration approval message.

[0398] Based on this, the terminal can delete already stored RAT control information (PLMN / RAT restriction information list) (or access control information).

[0399] FIG. 12 shows a first example of information of a SoR transparent container according to the disclosure of the present specification.

[0400] FIG. 13 shows a second example of information of a SoR transparent container according to the disclosure of the present specification.

[0401] The terminal can receive the information of Fig. 12.

[0402] If the terminal supports SOR-CMCI, SOR-SNPN-SI, or SOR-SNPN-SI-LS, the terminal can receive the information of FIG. 12 and the information of FIG. 13.

[0403] The information in Fig. 13 may be information about SOR-CMCI, SOR-SNPN-SI, or SOR-SNPN-SI-LS.

[0404] The SoR transparent container may include RAT control information (PLMN ID list and RAT control list). Here, the RAT control list may be content corresponding to a specific PLMN ID.

[0405] FIG. 14 shows an example of RAT control information according to the disclosure of the present specification.

[0406] RAT control information (PLMN ID list and RAT control list) may include the following information:

[0407] - ID of the 1st PLMN

[0408] - Restricted (or permitted) RAT information applicable to the 1st PLMN

[0409] - ID of the nth PLMN

[0410] - Restricted (or permitted) RAT information applicable to the nth PLMN

[0411] RAT control information may be RAT information for a specific PLMN. The RAT information may be Restricted RAT or Allowed RAT information.

[0412] RAT control information may include information on multiple PLMNs (e.g., ID and RAT control information).

[0413] FIG. 15 shows an example of the format of RAT control information according to the disclosure of the present specification.

[0414] RAT control information (e.g., RAT control list for each of one or more PLMNs in the PLMN ID list) may be in the format of a bitmap.

[0415] RAT information may include, but is not limited to, radio access technologies such as NR, E-UTRA, UTRA, and GSM.

[0416] For example, RAT information may include RAT types defined in TS 29.274 v18.7.0 Table 8.17-1. RAT information is not limited to 1 byte as shown in FIG. 15 and may be represented as 2 bytes or more.

[0417] FIG. 16 shows an example of RAT control information according to the disclosure of the present specification.

[0418] The RAT control information transmitted to the terminal may optionally include region and / or time information to which RAT control applies.

[0419] 3. Store RAT control information for specific regions / times

[0420] (1) Store on SIM

[0421] The UE can manage RAT control information for specific regions / times in the form of preconfigured information stored in the SIM.

[0422] RAT control information for a specific region / time can be pre-set and stored in the terminal's SIM.

[0423] For basic operation, refer to TS 31.102 v18.6.2 and TS 31.111 v18.1.0.

[0424] RAT control information may include PLMN ID and RAT information (e.g., NR, E-UTRAN, satellite E-UTRAN, etc.).

[0425] RAT control information may include RAT control information for each PLMN / SNPN value to which PLMN selection or cell selection can be applied.

[0426] FIG. 17 shows an example of coding of RAT control information according to the disclosure of the present specification.

[0427] (2) Store in storage space other than SIM

[0428] The terminal can receive RAT control information for a specific region / time from the network. Based on this, the terminal can store the RAT control information in non-volatile memory (NVM) or volatile memory.

[0429] RAT control information stored in the NVM can be deleted from the terminal in the following cases:

[0430] - When the terminal receives RAT control information for the relevant area from the network, it may delete any already stored RAT control information and store the received RAT control information.

[0431] - The terminal may receive RAT control information from the network. If there is no information in the RAT control information IE (e.g., if the length of the RAT control information content for the RAT control information IE is set to “0”), the terminal may delete any already stored RAT control information. For example, the terminal may subsequently not perform operations based on the RAT control information. For example, the terminal may perform cell selection / cell reselection / PLMN selection without using the RAT control information.

[0432] - When the terminal is powered off (or switched off / on), the terminal can delete RAT control information (e.g., previously received RAT control information, RAT control information previously configured on the terminal). For example, a rebooted terminal can perform cell selection / cell reselection / PLMN selection without using RAT control information.

[0433] - If RAT control information is applied only at specific times, when the terminal is powered off (or switched off / on), the terminal can calculate the remaining time for which the RAT control information is applied, and the rebooted terminal can apply the RAT control information during that time. (For example, the method of applying remaining time can be utilized when managing a back-off timer.)

[0434] II. Operation of the terminal after receiving RAT control information restricted (or allowed) for a specific PLMN

[0435] 1. NAS Tier

[0436] The UE's NAS layer can store RAT control information after receiving it.

[0437] The UE's NAS layer can update the already stored RAT control information when it receives new RAT control information.

[0438] The UE can delete RAT control information received via NAS signaling when switching off.

[0439] Based on available PLMN lists and signal quality information received from the AS layer, the UE's NAS layer can utilize RAT control information when performing PLMN selection (or cell (re)selection).

[0440] The NAS layer can transmit RAT control information to the AS layer. Based on this, the NAS layer may not receive cell quality information regarding restricted RATs of a specific PLMN.

[0441] After the NAS layer receives available PLMN lists, signal quality, etc. from the AS layer as in the past (according to Rel-18 operation), the NAS layer can transmit assistance information for performing cell selection to the AS layer based on the RAT control information it possesses.

[0442] For example, the NAS layer can transmit to the AS layer information about the selected PLMN and restricted RATs (or allowed RATs) for that PLMN (or region where RAT control applies).

[0443] As another example, just as conventionally, the NAS layer can transmit information about areas subject to RAT control to the AS layer as a forbidden TA. Alternatively, the NAS layer can transmit information about areas subject to RAT control to the AS layer by designating them as a forbidden area. Upon receiving this, the AS layer can perform idle mobility (e.g., cell selection / reselection) excluding TAs or areas processed as 'forbidden'.

[0444] As another example, the NAS layer can disable the capability related to terminal operations that are restricted from use due to RAT control. If necessary, the NAS layer can notify the AS layer of this fact.

[0445] The above capabilities may include NR / E-UTRAN satellite capability, N1 / S1 mode disable / enable, AS layer deactivation, UE network capability, UE radio access capability, etc.

[0446] The UE NAS layer can transmit RAT control information or assistance information for RAT control received from the network to the AS layer.

[0447] The NAS can control the RAT(s) in which the cell (re)selection should be performed, for instance by indicating RAT(s) associated with the selected PLMN, and by maintaining a list of restricted registration area(s) and a list of equivalent PLMNs.

[0448] 2. AS Layer

[0449] Conventionally, the UE AS layer can receive information on a specific PLMN (aka selected PLMN) and RAT(s) associated with that PLMN from the NAS, and perform cell (re)selection based on this. Additionally, the UE AS layer can receive information on forbidden TAs and perform cell (re)selection based on this.

[0450] If the terminal does not find a suitable cell among all RATs, it may transition to the 'Any Cell Selection' state or the 'limited' state.

[0451] The sequence in which a terminal scans the allowed (or restricted) RATs for the corresponding PLMN to find a suitable cell may be as follows:

[0452] - 1) The terminal can find a suitable cell by first scanning the PLMN received from the NAS layer, the allowed RAT(s) for a specific region, or the RAT that excludes the restricted RAT (allowed RAT).

[0453] - 2) If a suitable cell is not found in the allowed RAT(s), the terminal can find a suitable cell in the RAT associated with the PLMN (associated RAT(s)) based on the RAT control information.

[0454] - 3) If a suitable cell is not found among the RAT(s) allowed in the corresponding PLMN based on RAT control information, the terminal may find a suitable cell among all RAT(s) detected for the corresponding PLMN. In this case, if the terminal finds and camps a suitable cell in a RAT that is not an allowed RAT(s), the terminal may transition to an 'Any cell state' or behave as if it is in an 'Any cell state'. For example, the terminal may only use emergency services instead of normal services.

[0455] The terminal may use at least one of the following for cell (re)selection or other layer operations (e.g., measurement):

[0456] - RAT control information transmitted from the NAS layer or upper layers

[0457] - RAT control information received from the base station

[0458] The AS layer can perform an SIB acquisition operation based on RAT control information received from the NAS layer. For example, if the terminal can distinguish RATs based on frequency, the terminal may not perform an SIB acquisition operation for unauthorized frequencies based on the RAT control information (e.g., does not read MIB / SIB1).

[0459] The AS layer can select a cell (selected cell) based on RAT control information received from the NAS layer when performing inter-RAT cell reselection.

[0460] The AS layer can receive additional cell reselection priorities for inter-RAT cell reselection from the RAN node via dedicated RRC signaling (e.g., RRC release). In this case, the RAN node may also provide timer values ​​applied to the additional cell reselection priorities.

[0461] III. Re-enabling RAT

[0462] The terminal can restrict usage for certain RATs by applying received RAT control information.

[0463] Afterwards, if a specific event occurs, the terminal can delete the RAT information (e.g., RAT control information) for which usage was restricted.

[0464] This deletion of RAT information may be the deletion of the entire RAT control information depending on the event.

[0465] This deletion of RAT information may be the deletion of parts of the RAT control information depending on the event.

[0466] The terminal can disable RAT control information-based operations when a specific event occurs. Additionally, the terminal can re-enable the operations for the RAT that was previously suggested for use.

[0467] For example, if cell (re)selection, measurement, etc. to a specific RAT was restricted by RAT control information, the terminal can allow cell (re)selection, measurement, etc. to the specific RAT again.

[0468] The specific event mentioned above will be described below.

[0469] i) Update UE's subscription information

[0470] The UE can receive update indications regarding the modification of RAT control information from the network (e.g., AMF).

[0471] For example, the above indication may be updated RAT control information.

[0472] For example, the above indication may be an indication to delete previously received RAT control information. For example, when the terminal receives the above indication, it may delete all stored RAT control information.

[0473] ii) If access was made to a RAT that was restricted by network control

[0474] If a UE moves to a restricted RAT through network control (e.g., handover, redirection) in connected mode, the UE can remove the restriction on that RAT.

[0475] A network operator can apply whether to allow the use of a specific RAT regardless of the terminal's state (idle or connected). This enables flexible and efficient RAT management.

[0476] The terminal can receive RAT control information from the first network. The RAT control information may include information about a RAT that is restricted from use in the second network.

[0477] The above RAT control information may be transmitted in the form of NAS signaling (e.g., Registration Accept, Registration Reject, Deregistration Request, UE Configuration Update Command, or SoR message).

[0478] Based on the above RAT control information, the NAS layer of the terminal can disable terminal capabilities (e.g., N1 mode disable, NR satellite capability disable, AS layer deactivation).

[0479] Based on the above RAT control information, the NAS layer of the terminal can determine / define the area to which the RAT control information applies as a service-unavailable area (e.g., forbidden TA, restricted area).

[0480] In this case, the terminal's NAS layer can transmit RAT control information (or RAT control-related assistance information) to the AS layer. Then, the AS layer can utilize the RAT control information (or RAT control-related assistance information) when executing mobility procedures (e.g., cell (re)selection, handover).

[0481] The above RAT control information can be transmitted via AS signaling (e.g., RRC release, RRC reconfiguration, SystemInformation). For example, the above AS signaling may be RRC signaling.

[0482] If a terminal receives RAT control information via both NAS signaling and AS signaling, the information from AS signaling may take precedence over the information from NAS signaling. Based on this, the AS layer can perform mobility operations based on the relevant information (information from NAS signaling).

[0483] The terminal can receive RAT control information from the first network. The RAT control information may include information regarding RATs restricted from use in the second network. When selecting the second network, the terminal can select a cell where a specific RAT (e.g., a RAT available for network access) is allowed based on the RAT control information.

[0484] If the terminal cannot select a suitable cell of the allowed RAT, and only the RAT restricted by the RAT control information satisfies the suitable cell signaling criteria, the terminal can select a cell of the restricted RAT and transition to 'any cell state'.

[0485] The following drawings are made 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.

[0486] FIG. 18 illustrates the procedure of the UE for the disclosure of the present specification.

[0487] 1. A UE (User Equipment) can send a registration request message to an AMF (Access and Mobility management Function).

[0488] 2. The above UE can receive a first message from the above AMF.

[0489] The first message above may include access control information.

[0490] The above access control information may include an identifier of the PLMN (Public Land Mobile Network) and information regarding access restricted in the PLMN.

[0491] The above access control information may include information related to time and / or region.

[0492] The above UE may not be allowed to access the above PLMN through the above restricted RAT.

[0493] The above access control information may include information on multiple PLMNs.

[0494] Based on the above access control information, the UE can perform cell selection, cell re-selection, or PLMN selection.

[0495] The first message above may include timer information for the access control information.

[0496] Based on the above timer information, the UE can start the timer.

[0497] Until the above timer expires, the UE can perform cell selection, cell re-selection, or PLMN selection based on the access control information.

[0498] The first message above may be a registration approval message, a registration rejection message, a deregistration request message, a configuration update command, or a SoR (Steer of Roaming) message.

[0499] The above UE can perform a reboot.

[0500] Based on the above reboot, it can be determined whether the UE can continue to apply the access control information.

[0501] Based on the determination that the above UE cannot continue to apply the access control information, the above UE may perform cell selection, cell reselection, or PLMN selection regardless of the access control information.

[0502] Based on the determination that the above UE can continue to apply the access control information, the above UE may perform cell selection, cell re-selection, or PLMN selection based on the access control information.

[0503] Based on the above access control information, the UE can disable the capability of the UE.

[0504] The above UE can store the access control information.

[0505] The above UE can receive access indication from the network.

[0506] The above access indication may be an indication to delete the above access control information.

[0507] Based on the above access indication, the UE can delete the access control information.

[0508] The above access control information may be access technology utilization control information.

[0509] The following drawings are made 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.

[0510] FIG. 19 illustrates the procedure of the AMF for the disclosure of the present specification.

[0511] 1. The AMF can receive a registration request message from the UE.

[0512] 2. The above AMF can obtain access control information from UDM (Unified Data Management).

[0513] 3. The above AMF may transmit the access control information to the above UE.

[0514] The above access control information may include an identifier of the PLMN (Public Land Mobile Network) and information regarding access restricted in the PLMN.

[0515] The above access control information may include information related to time and / or region.

[0516] The above UE may not be allowed to access the above PLMN through the above restricted RAT.

[0517] The above access control information may include information on multiple PLMNs.

[0518] The first message above may include timer information for the access control information.

[0519] The above timer information may include information regarding the time when the access control information is valid.

[0520] The first message above may be a registration approval message, a registration rejection message, a deregistration request message, a configuration update command, or a SoR message.

[0521] The above AMF can transmit an access indication to the above UE.

[0522] The above access indication may be an indication to delete the above access control information.

[0523] The above access control information may be access technology utilization control information.

[0524] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0525] For example, the device may include a processor, a transceiver, and memory.

[0526] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0527] The operation performed by the processor comprises: a step in which the UE transmits a registration request message to the AMF; and a step in which the UE receives a first message from the AMF, wherein the first message includes access control information, and the access control information may include information related to time and / or region.

[0528] Hereinafter, a processor of a device for providing communication according to some embodiments of the present specification will be described.

[0529] The operation performed by the processor comprises: a step in which the UE transmits a registration request message to the AMF; and a step in which the UE receives a first message from the AMF, wherein the first message includes access control information, and the access control information may include information related to time and / or region.

[0530] Hereinafter, a non-volatile computer-readable medium storing one or more instructions for providing mobile communication according to some embodiments of the present specification will be described.

[0531] According to some embodiments of the present disclosure, the technical features of the present disclosure may be directly implemented in hardware, software executed by a processor, or a combination of both. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0532] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

[0533] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0534] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

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

[0536] According to some embodiments of the present disclosure, a non-transient computer-readable medium stores one or more instructions thereon. The stored one or more instructions can be executed by a processor of a base station.

[0537] One or more stored commands include the step of a UE transmitting a registration request message to an AMF; and the step of the UE receiving a first message from the AMF, wherein the first message includes access control information, and the access control information may include information related to time and / or region.

[0538] Hereinafter, a non-volatile computer-readable medium storing one or more instructions for providing mobile communication according to some embodiments of the present specification will be described.

[0539] This specification may have various effects.

[0540] For example, RAT control can be applied in a specific region / time through the procedure disclosed in this specification.

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

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

1. As a method, A step in which the UE (User Equipment) sends a registration request message to the AMF (Access and Mobility management Function); and The above UE includes the step of receiving a first message from the above AMF, and The first message above includes access control information, and A method in which the above access control information includes an identifier of a PLMN (Public Land Mobile Network) and information regarding access restricted in said PLMN.

2. In Paragraph 1, The above access control information is a method that includes information related to time and / or region.

3. In Paragraph 2, A method in which the above UE is not allowed to access the above PLMN through the above restricted RAT.

4. In any one of paragraphs 1 through 3, The above access control information is a method that includes information on a plurality of PLMNs.

5. In any one of paragraphs 1 through 4, A method further comprising the step of the UE performing cell selection, cell re-selection, or PLMN selection based on the above access control information.

6. In any one of paragraphs 1 through 5, The first message above includes timer information for the access control information, and Based on the above timer information, the step of the UE starting a timer; and A method further comprising the step of the UE performing cell selection, cell re-selection, or PLMN selection based on the access control information before the above timer expires.

7. In any one of paragraphs 1 through 6, The above first message is a method in which it is a registration approval message, a registration rejection message, a deregistration request message, a configuration update command, or a SoR (Steer of Roaming) message.

8. In any one of paragraphs 1 through 7, Step of the above UE performing a reboot; A step of determining whether the UE can continue to apply the access control information based on the above reboot; Based on the determination that the above UE cannot continue to apply the access control information, the step of the UE performing cell selection, cell reselection, or PLMN selection regardless of the access control information; and A method further comprising the step of the UE performing cell selection, cell re-selection, or PLMN selection based on the access control information, based on the determination that the UE can continue to apply the access control information.

9. In any one of paragraphs 1 through 8, A method further comprising the step of disabling the capability of the UE based on the access control information above.

10. In any one of paragraphs 1 through 9, The step of the above UE storing the access control information; The step of the above UE receiving an access indication from the network; The above access indication is an indication to delete the above access control information, and A method comprising the step of the UE deleting the access control information based on the above access indication.

11. In any one of paragraphs 1 through 10, The above access control information is access technology utilization control information.

12. As a method, Step of AMF receiving a registration request message from UE; The step of the above AMF obtaining access control information from UDM (Unified Data Management); and The above AMF includes the step of transmitting the access control information to the UE, A method in which the above access control information includes an identifier of a PLMN (Public Land Mobile Network) and information regarding access restricted in said PLMN.

13. In Paragraph 12, The above access control information is a method that includes information related to time and / or region.

14. In Paragraph 12, A method in which the above UE is not allowed to access the above PLMN through the above restricted RAT.

15. In any one of paragraphs 12 through 14, The above access control information is a method that includes information on a plurality of PLMNs.

16. In any one of paragraphs 12 through 15, The first message above includes timer information for the access control information, and The above timer information includes information about the time when the access control information is valid.

17. In any one of paragraphs 12 through 16, The above first message is a method in which it is a registration approval message, a registration rejection message, a deregistration request message, a configuration update command, or a SoR message.

18. In any one of paragraphs 12 through 17, The above AMF further includes the step of transmitting an access indication to the UE, The above access indication is a method in which the above access indication is an indication to delete the above access control information.

19. In any one of paragraphs 12 through 18, The above access control information is access technology utilization control information.

20. As a UE (User Equipment) performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is a specific UE that is a method according to any one of claims 1 to 11.

21. As an AMF performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is an AMF, which is a method according to any one of claims 12 to 19.

22. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and A device in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 11.

23. A non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium in which the above instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 11.

Images