SMS service according to user change

Abstract

One disclosure of the present specification provides a method. The method comprises the steps in which: an AMF receives a registration request message from a UE, wherein the registration request message includes an identifier of a specific user of the UE; and on the basis of the identifier, the AMF transmits an update request for an SMS service to an SMSF, wherein the SMSF is a network node for the SMS service for the UE and the specific user, and the update request includes information on the identifier.

Description

SMS service according to user change This specification relates to mobile communications. 3GPP(3rd generation partnership project) LTE(long-term evolution) is a technology to enable high-speed packet communication. Many methods have been proposed to achieve the LTE goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE requires cost reduction per bit, improved service availability, flexible use of frequency bands, simple structure, open interface, and appropriate power consumption of terminals as upper-level requirements. The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technology components necessary to successfully standardize NR in a timely manner that meets both urgent market needs and the longer-term requirements presented by the ITU-R (ITU radio communication sector) IMT (international mobile telecommunications)-2020 process. NR must also be able to use any spectrum band up to at least 100 GHz that will be available for wireless communications far into the future. NR targets a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced mobile broadband (eMBB), massive machine type-communications (mMTC), and ultra-reliable and low latency communications (URLLC). NR must be inherently forward-compatible. If the user of the terminal changes, the method of SMS service through the terminal becomes problematic. The terminal transmits an identifier for the new user to the network, and based on this, an SMS service for the new user is provided to the terminal. Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied. Figure 2 illustrates an example of a wireless device to which the implementation of this specification is applied. Figure 3 shows an example of a UE to which the implementation of this specification is applied. Figure 4 is a structural diagram of the next-generation mobile communications network. Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied. Figures 6 and 7 illustrate examples of registration procedures to which the implementation of this specification applies. Figures 8 and 9 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies. Figure 10 shows an example of a procedure according to the first embodiment of the present specification. Figure 11 shows an example of a procedure according to the second embodiment of the present specification. Figure 12 shows an example of a procedure according to the third embodiment of the present specification. Figure 13 shows an example of a procedure according to the fourth embodiment of the present specification. Figure 14 shows an example of a procedure according to the fifth embodiment of the present specification. Figure 15 shows an example of a procedure according to the sixth embodiment of the present specification. Figure 16 illustrates the AMF's procedure for disclosure of this specification. Figure 17 illustrates the SMSF's procedures for disclosure of this specification. The following techniques, devices, and systems can 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, systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via 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 over 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) that uses E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio). For convenience of explanation, the implementation of this specification is mainly described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, although the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of this specification that are not limited to a 3GPP-based wireless communication system may be applied to other mobile communication systems. 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. As used herein, “A or B” can mean “only A”, “only B”, or “both A and B”. In other words, as used herein, “A or B” can be interpreted as “A and / or B”. For example, as used herein, “A, B or C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. As used herein, a slash ( / ) or a comma can mean "and / or". For example, "A / B" can mean "A and / or B". Accordingly, "A / B" can mean "only A", "only B", or "both A and B". For example, "A, B, C" can mean "A, B, or C". As used herein, “at least one of A and B” can mean “only A”, “only B” or “both A and B”. Additionally, as used herein, the expressions “at least one of A or B” or “at least one of A and / or B” can be interpreted identically to “at least one of A and B”. Additionally, in this specification, "at least one of A, B and C" can mean "only A", "only B", "only C", or "any combination of A, B and C". Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" can mean "at least one of A, B and C". In addition, the parentheses used in this specification may mean "for example". Specifically, when it is 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". In addition, even when it is indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information". Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously. Although not limited thereto, the various descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this specification may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G). Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to identical or corresponding hardware blocks, software blocks and / or functional blocks unless otherwise indicated. Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied. The 5G usage scenarios shown in Fig. 1 are only examples, and the technical features of this specification can be applied to other 5G usage scenarios not shown in Fig. 1. There are three major requirement categories for 5G: (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low latency communications (URLLC) category. Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 describes a 5G network as an example of a network of the communication system (1), but the implementation of the present specification is not limited to a 5G system, and can be applied to future communication systems beyond the 5G system. The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices. The wireless devices (100a to 100f) represent devices that perform communications using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an IoT device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The 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), head-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches 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. 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 smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device. For example, a UAV may be an aircraft that does not carry a human on board and is guided by radio control signals. For example, a VR device may include a device for implementing an object or background of a virtual environment. For example, an AR device may include a device that implements an object or background of a virtual world by connecting it to an object or background of a real world. For example, an MR device may include a device that implements an object or background of a virtual world by merging it with an object or background of the real world. For example, a hologram device may include a device for implementing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using a light interference phenomenon that occurs when two laser lights called holograms meet. For example, a public safety device may include an image relay device or imaging device that can be worn on the user's body. For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors. 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 for the purpose of diagnosing, treating, alleviating, or correcting 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, an (in vitro) diagnostic device, a hearing aid, or a surgical device. For example, a security device may be a device installed to prevent possible hazards and maintain safety. For example, a security device may be a camera, closed circuit television (CCTV), recorder, or black box. For example, a fintech device may be a device that can provide financial services such as mobile payments. For example, a fintech device may include a payment device or a point-of-sale system. For example, a weather / environment device may include a device that monitors or predicts the weather / environment. Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via 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) can communicate with each other via the base station (200) / network (300), but can 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., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f). Wireless communications / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communications / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communications (150a), sidelink communications (150b) (or, device-to-device (D2D) communications), and inter-base station communications (150c) (e.g., relay, integrated access and backhaul (IAB)). Through the wireless communications / connections (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification. AI refers to a field that studies artificial intelligence or the methodologies for creating it, and machine learning refers to a field that defines various problems in the field of artificial intelligence and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves the performance of a task through constant experience with that task. A robot can refer to a machine that automatically processes or operates a given task by its own ability. In particular, a robot that has the function of recognizing the environment, making judgments on its own, and performing actions can be called an intelligent robot. Robots can be classified into industrial, medical, household, and military types depending on their purpose or field of use. A robot can perform various physical actions, such as moving robot joints, by having a drive unit including an actuator or motor. In addition, a mobile robot can have a drive unit including wheels, brakes, and propellers, and can drive on the ground or fly in the air through the drive unit. Autonomous driving refers to technology that drives itself, and autonomous vehicles refer to vehicles that drive without user intervention or with minimal user intervention. For example, autonomous driving can include technology that maintains the driving lane, technology that automatically adjusts speed such as adaptive cruise control, technology that automatically drives along a set path, and technology that automatically sets a path and drives when a destination is set. Vehicles include vehicles with only internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors, and can include not only cars but also trains, motorcycles, etc. Autonomous vehicles can be viewed as robots with autonomous driving functions. Extended reality is a general term for VR, AR, and MR. VR technology provides only CG images of objects or backgrounds in the real world, AR technology provides virtual CG images on top of images of real objects, and MR technology is a CG technology that mixes and combines virtual objects in the real world. MR technology is similar to AR technology in that it shows real and virtual objects together. However, there is a difference in that while AR technology uses virtual objects to complement real objects, MR technology uses virtual and real objects with equal characteristics. 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, 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. The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1, FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean "sub 6GHz range", and FR2 can mean "above 6GHz range" and can be called millimeter wave (mmW). Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 can include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 can 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 in FR1 can include an unlicensed band. The unlicensed band can be used for various purposes, for example, it can be used for communications for vehicles (e.g., autonomous driving). Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, the NB-IoT technology may be an example of a low power wide area network (LPWAN) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, the LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced MTC). For example, the LTE-M technology can be implemented by 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 above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, the ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names. Figure 2 illustrates an example of a wireless device to which the implementation of this specification is applied. In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the usage example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules. 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). 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 alternatively, the memory (104) may be located external to the processing chip (101). The processor (102) may control the memory (104) and / or the transceiver (106), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and store information obtained by processing the second information / signal in the memory (104). A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers. Here, the processor (102) and the 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 coupled to the processor (102) to transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (radio frequency) section. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip. 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). 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 located external to the processing chip (201). The processor (202) may control the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal, and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206), and store information obtained by processing the fourth information / signal in the memory (204). A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements a set of instructions, commands and / or instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers. Here, the processor (202) and the 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 coupled to the processor (202) to transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF section. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip. 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 physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The 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 the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphic processing unit (GPU), and a memory control processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be comprised of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections. One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can 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) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices. One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, 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 operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via 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) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202). Although not shown in FIG. 2, the wireless device (100, 200) may further 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., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections. In an implementation of the present disclosure, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In an implementation of the present disclosure, a base station can operate as a receiver in the UL and as a transmitter in the DL. For convenience of description, it is mainly assumed below 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 in the first wireless device (100) can be configured to perform UE operations according to an implementation of the present disclosure or to control a transceiver (106) to perform UE operations according to an implementation of the present disclosure. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to an implementation of the present disclosure or to control a transceiver (206) to perform base station operations according to an implementation of the present disclosure. In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB. Figure 3 shows an example of a UE to which the implementation of this specification is applied. Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2. The UE (100) includes a processor (102), memory (104), a 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). The processor (102) may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or 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, suggestions, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipset, logic circuitry 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 a processor (102) is the SNAPDRAGON made by Qualcomm®. TM Series Processor, EXYNOS made by Samsung® TM Series processors, A series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors. Memory (104) is operatively coupled with processor (102) and stores various information for operating processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by processor (102). Memory (104) may be implemented within processor (102) or external to processor (102), in which case it may be communicatively coupled with processor (102) via various methods known in the art. A transceiver (106) is operatively coupled to the processor (102) and transmits and / or receives wireless signals. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include baseband circuitry for processing radio frequency signals. The transceiver (106) controls one or more antennas (108) to transmit and / or receive wireless signals. 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). 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). 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 subscribers in mobile phone devices such as mobile phones and computers. Contact information can also be stored on many SIM cards. 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). Figure 4 is a structural diagram of the next-generation mobile communications network. 5GC (5G Core) may include various components, and in FIG. 5, some of them include 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). The UE (100) is connected to a data network via UPF (440) through a Next Generation Radio Access Network (NG-RAN) including a gNB (20). The UE (100) can also receive data services through untrusted non-3GPP access, for example, a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (490) can be deployed. The illustrated N3IWF (490) performs a function of managing interworking between non-3GPP access and a 5G system. When the UE (100) is connected to a non-3GPP access (e.g., WiFi referred to as IEEE 801.11), the UE (100) can be connected to a 5G system through the N3IWF (490). The N3IWF (490) performs control signaling with the AMF (410) and is connected to the UPF (440) through the N3 interface for data transmission. The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform a function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform a function of handling mobility in an idle state. 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 communications. 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 a data path between the gNB (20) and the SMF (420). In addition, when the UE (100) moves across an area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform a function of handling PDUs. For mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), the UPF can route packets. Additionally, UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined before 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). UPF (440) may correspond to a termination point of a data interface toward a data network. The illustrated PCF (430) is a node that controls the business operator's policy. The illustrated AF (450) is a server for providing various services to the UE (100). 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). The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session. For reference, the drawing symbols for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below. The 5th generation mobile communications support 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, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied. The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function). - AUSF (Authentication Server Function) -AMF (Access and Mobility Management Function) - DN (Data Network), for example operator services, Internet access or third-party services. - USDF (Unstructured Data Storage Function) - NEF (Network Exposure Function) - I-NEF (Intermediate NEF) - NRF (Network Repository Function) - NSSF (Network Slice Selection Function) - PCF (Policy Control Function) - SMF (Session Management Function) -UDM (Unified Data Management) -UDR (Unified Data Repository) - UPF (User Plane Function) - UCMF (UE radio Capability Management Function) - AF (Application Function) - UE (User Equipment) - (R)AN ((Radio) Access Network) - 5G-EIR (5G-Equipment Identity Register) - NWDAF (Network Data Analytics Function) - CHF (CHarging Function) Additionally, the following network features may be considered: - N3IWF (Non-3GPP InterWorking Function) - TNGF (Trusted Non-3GPP Gateway Function) - W-AGF (Wireline Access Gateway Function) Figure 5 shows the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other. In Figure 5, for clarity of the point-to-point diagram, UDSF, NEF and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF and NRF as needed. 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. The 5G system architecture includes the following benchmarks: - N1: Reference point between UE and AMF. - N2: Reference point between (R)AN and AMF. - N3: Reference point between (R)AN and UPF. - N4: Reference point between SMF and UPF. - N6: Reference point between UPF and data network. - N9: Reference point between two UPFs. The following benchmarks demonstrate the interactions that exist between NF services in NF. - N5: Reference point between PCF and AF. - N7: Reference point between SMF and PCF. - N8: Reference point between UDM and AMF. - N10: Reference point between UDM and SMF. - N11: Reference point between AMF and SMF. - N12: Reference point between AMF and AUSF. - N13: Reference point between UDM and AUSF. - N14: Reference point between two AMFs. - N15: Reference point between PCF and AMF for non-roaming scenarios, and between PCF and AMF of visited network for roaming scenarios. - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network) - N22: Reference point between AMF and NSSF. In some cases, two NFs may need to be interconnected to serve a UE. <Registration Procedure> Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12). Figures 6 and 7 illustrate examples of registration procedures to which the implementation of this specification applies. The UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration procedure using one of the following registration types: - Initial registration for 5GS; or - mobility registration update; or - periodic registration update; or - Emergency registration The general registration procedure of Figures 6 and 7 applies to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures. The generic registration procedure of Figures 6 and 7 may also be used when registering to a 3GPP connection when the UE is already registered to a non-3GPP connection, and vice versa. To register to a 3GPP connection when the UE is already registered to a non-3GPP connection scenario, an AMF change may be required. First, the procedure of Fig. 6 is described. (1) Step 1: The UE transmits a Registration Request message to (R)AN. The Registration Request message corresponds to an AN message. The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, a 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or a globally unique AMF ID (GUAMI), a selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)) and a requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter. A 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 RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and initiates the registration procedure because the UE is moving, or the UE wants to update capabilities or protocol parameters, or the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and initiates the registration procedure due to expiration of a periodic registration update timer), or an emergency registration (i.e., the UE is in a restricted service state). When a UE performs initial registration, the UE indicates its UE ID in the registration request message as follows, listed in decreasing priority order: i) If the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), 5G-GUTI mapped from the EPS GUTI; ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register; iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register; iv) Native 5G-GUTI allocated by another PLMN (if available); v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message. If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI in decreasing priority order from items (ii)-(iv) in the list above. When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters. For emergency registration, if the UE does not have a valid 5G-GUTI, SUCI is included, if the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, PEI (permanent equipment identifier) is included. In other cases, 5G-GUTI is included, which indicates the last serving AMF. The registration request message may also include security parameters, PDU session status, etc. The 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 an established PDU session in the current PLMN in the UE. (2) Step 2: (R)AN selects AMF. If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not represent a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available. When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the UE's N2 connection. If (R)AN cannot select an appropriate AMF, (R)AN performs AMF selection by forwarding a registration request message to an AMF configured in (R)AN. (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message. The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1. The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause. If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted. (4) Step 4: If the 5G-GUTI of the UE is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message, to request the SUPI and UE context of the UE. (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context. (6) Step 6: If SUCI is not provided by the UE or is not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE. (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN). (8) Step 8: The new AMF may decide to initiate UE authentication by calling the AUSF. In this case, the new AMF selects the AUSF based on SUPI or SUCI. (9) Step 9: Authentication / security can be established by the UE, new AMF, AUSF and / or UDM. (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received. (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 ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated. (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation. Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described. (13) Step 13: If step 14 below is performed, the new AMF can select UDM based on SUPI, and UDM can select UDR instance. (14) Step 14: New AMFs can be registered with UDM. (15) Step 15: New AMF can select PCF. (16) Step 16: The new AMF can optionally perform AM policy association establishment / modification. (17) Step 17: The new AMF can send update / release SM context messages (e.g. Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to SMF. (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to N3IWF / TNGF / W-AGF. (19) Step 19: N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF. (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM. (21) Step 21: The new AMF sends a Registration Accept message to the UE. The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI allocated for the existing registration for the new registration. If the new AMF allocates a new Registration Area, it sends the Registration Accept message to the UE with the Registration Accept message. If the Registration Accept message does not include a Registration Area, the UE considers the previous Registration Area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions 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 is connected to two AMFs belonging to different PLMNs via 3GPP and non-3GPP connections, the UE locally removes internal resources associated with PDU sessions of the current PLMN that are not marked as established in the received PDU Session State. If PDU Session State information is present in the Registration Accept message, the new AMF indicates the PDU Session State to the UE. The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs having a tracking area included in the registration area. Mapping Of Allowed NSSAI maps HPLMN S-NSSAI to each S-NSSAI of Allowed NSSAI. Mapping Of Configured NSSAI maps HPLMN S-NSSAI to each S-NSSAI of Configured NSSAI for serving PLMN. Additionally, optionally, the new AMF performs UE policy association establishment. (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF. The UE may send a registration complete message to the new AMF to check if a new 5G-GUTI has been allocated. (23) Step 23: For registration over 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. For registration over non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. (24) Step 24: AMF can perform information updates on UDM. (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure. <PDU 세션 수립 절차> Describes the PDU session establishment procedure. See section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12). Figures 8 and 9 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies. Establishing a PDU session can involve: - UE initiated PDU session establishment procedure - PDU session handover between 3GPP and non-3GPP initiated by UE - PDU session handover from UE-initiated EPS to 5GS. - Network triggered PDU session establishment procedure A PDU session may be associated with (a) a single connection type at a given time, i.e., either a 3GPP connection or a non-3GPP connection, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) capable UE. Figures 8 and 9 specify the procedure for establishing a PDU session associated with a single connection type at a given time. In the procedures shown in Figures 8 and 9, it is assumed that the AMF has already retrieved the user subscription data from the UDM, unless the UE is emergency registered, since the UE is already registered with the AMF. First, the procedure of Fig. 8 is explained. (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID. The UE initiates the PDU session establishment procedure requested by the UE by transmitting an 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. If the PDU Session Establishment is a request to establish a new PDU Session, the Request Type is "Initial Request". If the Request refers to an existing PDU Session switching between a 3GPP connection and a non-3GPP connection, or a PDU Session handover from an existing packet data network (PDN) connection in the EPC, the Request Type is "Existing PDU Session". If the PDU Session Establishment is a request to establish a PDU Session for emergency services, the Request Type is "Emergency Request". If the Request refers to an existing PDU Session for emergency services switching between a 3GPP connection and a non-3GPP connection, or a PDU Session handover from an existing PDN connection for emergency services in the EPC, the Request Type is "Existing Emergency PDU Session". The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If the Mapping Of Allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI. (2) Step 2: AMF selects an SMF. If the request type indicates "initial request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID. If the request type is "Initial Request" and the message also contains a previous PDU session ID representing an existing PDU session, AMF selects an SMF and stores the association for the new PDU session ID, S-NSAI(s), and the selected SMF ID. If the request type indicates "Existing PDU Session", AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session. If the request type indicates "Existing PDU Session" referring to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAIs of the target connection type, the PDU session establishment procedure may be performed in the following cases: - When the SMF ID and AMF corresponding to the PDU session ID belong to the same PLMN; - If the SMF ID corresponding to the PDU session ID belongs to HPLMN; Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause. AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session". (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF calls the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF calls the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request). The AMF forwards the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also forwards the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI. The AMF ID is the GUAMI of the UE, which uniquely identifies the AMF serving the UE. The AMF passes the PDU Session ID along with the N1 SM container containing the PDU Session Establishment Request message received from the UE. The generic public subscription identifier (GPSI) is included if available to the AMF. If a UE in restricted service state is registered for emergency services without providing SUPI, the AMF provides PEI instead of SUPI. If a UE in restricted service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered not authenticated. AMF can include PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies H-PCF (home PCF) in non-roaming case and V-PCF (visited PCF) in LBO roaming case. (4) Step 4: If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, and HPLMN is not available, the SMF can retrieve the session management subscription data from the UDM and be notified when the subscription data is modified. (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 according to the request received in Step 3. 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. If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request via NAS SM signaling including the relevant SM rejection cause by responding to the AMF with Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below and the PDU session establishment procedure is aborted. (6) Step 6: Optional secondary authentication / authorization may be performed. (7a) Step 7a: When dynamic policy and charging control (PCC) is used for a PDU session, the SMF can perform PCF selection. (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a SM policy association with the PCF and obtain the default PCC rules for the PDU session. (8) Step 8: SMF selects one or more UPFs. (9) Step 9: The SMF may perform the SM policy association modification procedure initiated by the SMF to provide information about the satisfied policy control request trigger conditions. (10) Step 10: If the request type indicates an “Initial Request”, the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF. In step 10a, SMF can send N4 session establishment / modification request to UPF and provide packet detection, enforcement and reporting rules to be installed in UPF for PDU session. In step 10b, UPF can confirm by sending N4 session establishment / modification response. (11) Step 11: SMF sends an N1N2 Message Transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF. The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF is to forward to the (R)AN: - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session; - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles; - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE; - S-NSSAI with value for the serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming); - User plane security enforcement information determined by SMF; - UE integrity protection maximum data rate received in the PDU Session Establishment Request message: if integrity protection is indicated as “Preferred” or “Required” in the user plane security enforcement information. - RSN(redundancy sequence number) parameter The N1N2 Message Transfer message may contain an N1 SM container. The N1 SM container contains a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message contains an S-NSSAI from the allowed NSSAIs. For LBO roaming scenarios, the PDU Session Establishment Accept message contains an S-NSSAI from the allowed NSSAIs for the VPLMN and also contains the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAIs received by the SMF in step 3. Multiple QoS rules, QoS flow levels, and QoS parameters, if required, for QoS flows associated with QoS rules and QoS profiles can be included in the PDU session establishment accept message and N2 SM information within the N1 SM container. If the PDU session establishment fails between steps 5 and 11, the N1N2 message transfer message contains an N1 SM container containing a PDU session establishment rejection message, and does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted. (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message. (13) Step 13: (R)AN may perform AN specific signaling exchange with the UE related to the information received from the SMF. For example, in case of NG-RAN, the UE may perform RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12. (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN specific signaling exchange with the UE includes (R)AN resource addition related to the received N2 command. If N2 SM information is not included in step 11, steps 14-16b and step 17 below are omitted. Now, the procedure of Fig. 9 following the procedure of Fig. 8 is described. (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc. (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. (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and corresponding forwarding rules to UPF. (16b) Step S16b: UPF provides an N4 session modification response to SMF. After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE. (16c) Step 16c: If the SMF is not already registered for this PDU session, the SMF may register with the UDM for the given PDU session. (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF. After this step, AMF forwards the relevant events to which SMF has subscribed. (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g. IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted. (19) Step 19: For PDU session type IPv6 or IPv4v6, SMF may generate and send an IPv6 Router Advertisement to the UE. (20) Step 20: SMF can perform SM policy association modification initiated by SMF. (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe from modifications to the session management subscription data if the SMF no longer processes the UE's PDU session. The proposed method may consist of a combination of one or more of the operations / configurations / steps described herein. In this specification, UE (User Equipment) and terminal are used interchangeably. The operations / compositions / steps / methods described in this specification may be performed or used in combination or complementary manner. Multiple users can use one terminal. For example, user 1 can use a specific terminal. After that, user 2 can use the specific terminal. For example, a subscriber of a terminal and other users may use one terminal. The subscriber of a terminal and the user using the terminal may be different. Methods for supporting service provision, QoS provision, and authentication information exposure may vary depending on the user using the terminal. Methods for this may be proposed in this specification. The method proposed in this specification may be composed of a combination of one or more of the operations / configurations / steps described below. Any action or description of a UE in this specification may be interpreted as an action or description of a subscriber. Any action or description regarding a User Identifier in this specification may be interpreted as an action or description regarding a User. In this specification, a subscriber may also be interpreted as one of the users. In this case, the subscriber may be referred to as a default user, an owner of UE, a user without a specific user identifier, a user without a user identifier, a subscribing user, a UE holder, a primary user, a user without a user profile, etc. The methods proposed in this specification can be performed or used in combination or complementary manner. For SMS, you can refer to TS 23.501 v18.4.0, TS 23.502 v18.4.0, TS 23.040 v17.3.0, TS 23.540 v18.2.0, etc. Conventional NAS messages and service operations may be extended and used for the scheme proposed in this specification. Alternatively, new NAS messages and service operations may be defined and used. The UDM of the terminal (UDM of UE) of this specification may be a UDM for the terminal (or subscriber, user 1). The UDM of User Identifier (UDM) of the user identification of this specification may be a UDM for a new user (User 2) of the terminal. I. The network determines the identification information of the subscriber / user registered by the terminal. A subscriber of a terminal may use the terminal. Or, a user other than the subscriber may use the terminal. When a subscriber uses a specific terminal, an MT (Mobile Terminating) SMS message tailored to the subscriber is transmitted to the specific terminal. When another user uses the specific terminal, an MT SMS message tailored to the other user is transmitted to the specific terminal. For example, if a non-subscriber user #1 is using the terminal, an SMS message addressed to user #1 should be sent to the terminal. At this time, an SMS message addressed to a subscriber (or a user other than user #1) (e.g., a user who can use or is permitted to use the terminal) should not be sent to the terminal. To provide SMS to a terminal, the network can determine who is the current user using the terminal. Alternatively, the network can determine whether the terminal is being used by a specific user or without a user (or user information). UDM can store / manage user profiles for users who can use (or are permitted to use) terminals. User profiles can be stored / managed by UDM. Alternatively, the user profile may be stored / managed by a NF other than UDM (e.g., UDR, AF, etc.) or a newly defined NF. In this case, the UDM in this specification may be interpreted as the NF (or the newly defined NF) that stores / manages the user. The UDM of the User Identifier may be a UDM that stores / manages a user profile for a user (or identified / managed by a user identifier) using a terminal. In addition, the UDM of the User Identifier may be interpreted as the UDM of the user. User profiles for users may be stored / managed as part of the subscriber information of the terminal or may be stored / managed as separate information. When a user profile for a user is stored / managed as part of the subscriber information of a terminal, the user profile may be in the form of information about the user(s) who can use (or are permitted to use) the terminal. When a user profile for a user is stored / managed as separate information, the user profile may be in the form of information about terminals (UE(s)) that the user can use (or is permitted to use). The UDM of the terminal (UDM of UE) and the UDM of the user identifier (UDM of User Identifier) may be the same or different. The UDM of the terminal (UDM of UE) and the UDM of the user identifier (UDM of User Identifier) may belong to the same operator network or to different operator networks. In this specification, a UDM of a terminal (UDM of UE) and / or a UDM of a user identifier (UDM of User Identifier) may also be referred to as UDM. A user profile may contain SMS-related subscription information for the user (or SMS-related information or SMS-related user profile or SMS-related user profile information). SMS-related subscription information may take the form of one of the following: - SMS-related subscription information may be information that follows the SMS-related subscriber information of the terminal that the user can use (or is permitted to use). For example, the SMS-related subscription information may include indication information that follows (applies) the SMS-related subscriber information of the terminal. For example, the SMS-related subscription information may indicate that it follows the SMS-related information of the terminal in a way that does not include (store) the SMS-related subscription information. - SMS-related subscription information may include the same information as the SMS-related subscriber information of the terminal that the user can use (or is permitted to use). - SMS-related subscription information may include separate SMS-related subscription information for the user. In this case, the SMS-related subscription information may be terminal-specific SMS-related subscription information or may be common SMS-related subscription information for all terminals. Here, the SMS related subscription information may be information transmitted from the UDM to the SMSF. For example, SMS-related subscription information for a user may include some or all of the information in Tables 3 and 4. For example, to provide SMS to a user, the SMS-related subscription information may additionally include required information. For example, the information in Tables 3 and 4 may be transformed / expanded to serve as SMS-related subscription information for users. For example, SMS-related subscription information may include information indicating that SMS delivery is not permitted when a user uses a particular terminal. For example, SMS-related subscription information may include information indicating that SMS delivery is not permitted for any UE used by the user. For example, SMS related subscription information may include information about UEs that are / are not allowed to provide SMS to the user (e.g. list of SUPI / GPSI of UE). SMS Management Subscription data (data needed bySMS parametersIndicates SMS parameters subscribed for SMS service such as SMS teleservice, SMS barring listSMSF for SMSF Registration)Trace RequirementsTrace requirements about a UE (eg trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421

[0039] .This information is only sent to a SMSF in HPLMN.Routing IndicatorRouting Indicator assigned to the SUPI.SMS Subscription dataSMS SubscriptionIndicates subscription to any SMS delivery service over NAS irrespective of access type.(data needed in AMF) The GPSI information in Table 4 can be used for SMS transmission. Therefore, the GPSI information can correspond to SMS-related subscriber information, SMS-related subscription information for users. Access and Mobility Subscription data (data needed for UEGPSI ListList of the GPSI (Generic Public Subscription Identifier) used both inside and outside of the 3GPP system to address a 3GPP subscription (see NOTE 9).Registration and Mobility Management) A Generic Public Subscription Identifier (GPSI) may be required to process 3GPP subscriptions in other data networks outside the 3GPP system. The 3GPP system may store the association between a GPSI and its SUPI in the subscription data. GPSI may be a public identifier used both inside and outside the 3GPP system. GPSI can be an MSISDN or an external identifier. If the subscription data contains an MSISDN, the same MSISDN value can be supported in both 5GS and EPS. There may not be a one-to-one relationship between GPSI and SUPI. Information such as SUPI and PEI can be used as terminal identification information. User identification information (or user identifier) may include GPSI, identification information in the form of URI, and newly defined identification information. 1. First embodiment - When the SMSF (Short Message Service Function) for providing SMS to the terminal and the SMSF for providing SMS to the user identifier are the same The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 10 shows an example of a procedure according to the first embodiment of the present specification. 1) step 1 The procedure defined in Section 4.13.3.1 (Registration procedures for SMS over NAS) of TS 23.502 v18.4.0 may be performed. Alternatively, the operations of FIGS. 6 and 7 may be performed. The UE may transmit its ID to the network during the registration procedure. For example, the UE may perform registration without a user identifier. When an MT SMS occurs for a terminal (or subscriber) (or user 1), the MT SMS can be transmitted to the terminal via SMSF. 2) step 2 The terminal can detect (determine) that a user (User 2) wants to use the terminal. When a user (User 2) wants to use a terminal, the terminal can notify the network that the user (User 2) wants to use the terminal. For example, when a user (User 2) wants to use a terminal, the terminal can use a registration procedure to notify the network that the user (User 2) wants to use the terminal. For example, through another existing procedure / NAS message (or a newly defined procedure / NAS message), the terminal can notify the network that a user (User 2) wishes to use the terminal. The terminal may provide information about the user (e.g., user identifier information) to the network. For example, a terminal may transmit a registration request message to the AMF that includes information about the user (e.g., user identifier information). The registration request message may include information about the ID of the UE and an identifier for the new user (user 2). In addition, the registration request message may additionally include an indication that the new user (user 2) uses the UE. For example, the terminal may provide information about the user (e.g., user identifier information) to the network using a registration procedure. Or, the terminal may inform the network about the user (e.g., user identifier information) through another existing procedure / NAS message (or a newly defined procedure / NAS message). Additionally, depending on the terminal's settings, the terminal may transmit the following information to the network: - Whether to receive / use both SMS for the terminal and SMS for the user - Whether to receive / use SMS only for users or SMS only for terminals, etc. Alternatively, this information may be stored in the AMF local configuration, subscriber information of the UE and / or user profile. Instead of AMF receiving identification information of a user (User 2) attempting to use a terminal from a terminal, AMF may also receive identification information of a user (User 2) attempting to use a terminal from another NF. If registration has already been performed with a user identifier in step 1, the UDM involved in the registration may be a UDM of the user identifier (UDM of UE) instead of a UDM of the terminal (UDM of UE). Alternatively, the UDM involved in the registration may be a UDM of the terminal (UDM of UE) and a UDM of the user identifier (UDM of User Identifier). This may be because AMF needs subscriber information of the terminal throughout the registration process as it interacts with the UDM of the terminal (UDM of UE). 3) step 3 AMF can obtain a user profile for a user (user 2) currently using a terminal from the UDM of the user identifier. Although not shown in Fig. 10, an authentication operation for the user may be performed before step 3. Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). AMF can send information about the user identifier for the user (User 2) to UDM (UDM of User Identifier). Based on this, UDM (UDM of User Identifier) can send the user profile for the user (User 2) to AMF. 4) step 4 AMF can notify SMSF that said user (User 2) wishes to use the terminal. AMF can send SMSF information about the user identifier for said user. AMF may send SMSF a request to update SMS services for a terminal. For this purpose, a new service operation, such as the Nsmsf_SMService_Update service operation, may be defined and used. Alternatively, an existing service operation (e.g., Nsmsf_SMService_Activate) may be extended and used. Alternatively, after performing Nsmsf_SMService_Deactivate for the terminal, Nsmsf_SMService_Activate may be performed for the user. AMF assumes that the same SMSF has been selected for the user as the SMSF for the terminal. AMF may transmit information about the above user (e.g., user identifier information) to SMSF. Additionally, AMF may transmit information about whether both the terminal and the user require SMS reception / use (and / or whether only the user requires SMS reception / use) to SMSF. SMSF can recognize that the above terminal is used by the above user and store information about this. If SMS reception / use for a terminal / user is not necessary at all (e.g., NAS-based SMS transmission service is not allowed based on subscriber information or user profile), AMF can use Nsmsf_SMService_Deactivate to the terminal's SMSF to suspend SMS reception / use for the UE. 5) step 5 SMSF can perform Nudm_UECM_Deregistration operation to delete SMSF address for UE to UDM (UDM of UE). Based on this, UDM (UDM of UE) of UE can delete SMSF address for subscriber (user 1). The SMSF can send a Nudm_UECM_Deregistration message to the UDM (UDM of UE) of the terminal to delete the SMSF address for the terminal. Based on this, the UDM (UDM of UE) of the terminal can delete the SMSF address serving the subscriber (User 1). Then, the SMS transmission service for the subscriber (User 1) can be stopped / deactivated. This action may be performed if it is determined that SMS reception / use is not permitted for the terminal (or subscriber). 6) step 6 SMSF can perform Nudm_UECM_Registration operation to store SMSF address for said user (User 2) in UDM of User Identifier (UDM of User Identifier). Based on this, UDM of User Identifier (UDM for User 2) can store SMSF address for user (User 2). The SMSF can send a Nudm_UECM_Registration message to the UDM of the User Identifier (UDM of User Identifier) to store an SMSF address for the user (User 2). Based on this, the UDM of the User Identifier (UDM for User 2) can store an SMSF address serving the user (User 2). Then, the SMS transmission service for the user (User 2) can be initiated / activated. SMSF can send information about the user identifier for a user (User 2) to the UDM of User Identifier (UDM) via the above Nudm_UECM_Registration operation. This action may be performed if it is determined that SMS reception / use is required for the user (User 2). In such cases, subsequent steps can be performed if SMS reception / use is required for the user. The UDM of the terminal (UDM of UE) and the UDM of the user identifier (UDM of User Identifier) may be the same. Alternatively, the user profile information may be stored / managed as part of the subscriber information. If the UDM (UDM of UE) of the terminal and the UDM (UDM of User Identifier) of the user identifier are the same, or if the user profile information is stored / managed as part of the subscriber information, the SMSF can use the Nudm_UECM_Update service operation instead of performing steps 5 and 6 respectively to inform the UDM that it is acting as an SMSF for the user (User 2) and not the terminal. Step 6 may be performed before step 5, or steps 5 and 6 may be performed in parallel. 7) step 7 SMSF can obtain SMS related subscription information for a user (User 2) from the UDM of User Identifier. The SMSF can send information about the user identifier for the user (User 2) to the UDM of User Identifier (UDM of User Identifier). Based on this, the UDM of User Identifier (UDM of User Identifier) can send SMS-related subscription information to the SMSF. If SMS-related subscription information for a user (User 2) is stored / managed in the terminal's UDM (UDM of UE) as part of the terminal's subscriber information, the AMF may obtain the SMS-related subscription information for the user (User 2) and provide it to the SMSF. 8. step 8 The SMSF may send a response to step 4 to the AMF. The above response may include information that SMS service for the user is permitted to be provided to the terminal. 9. step 9 AMF can send a response message to the registration request to the terminal. If SMS service is allowed for the user (User 2), the response message may include an "SMS allowed" indication. When an MT SMS occurs for a user (User 2), the MT SMS can be transmitted to the user (User 2) using the terminal through SMSF. SMSF can provide SMS service for the user (User 2) to the terminal based on the SMS-related subscription information received in step 7. Based on the terminal being used by the above user (User 2), SMSF can send an MT SMS to the terminal. If SMS service for the user (User 2) is not allowed, then in step 8, SMSF may send a response to AMF including information that SMS service for said user (User 2) is not allowed to be provided to the terminal. Then, in step 9, AMF may send a response message including an "SMS not allowed" indication to the terminal. Thereafter, when a user who wishes to use the terminal changes, steps 2 to 9 may be performed. At this time, in the contents described above in steps 2 to 9, the UDM (UDM of UE) of the terminal may be replaced with the UDM (UDM of old User Identifier) of the old user identifier, and the UDM (UDM of User Identifier) of the user identifier may be replaced with the UDM (UDM of new User Identifier) of the new user identifier. Alternatively, if the subscriber (user 1) uses the terminal instead of the user (user 2) thereafter, steps 2 to 9 may be performed. At this time, in the contents described above in steps 2 to 9, the UDM (UDM of UE) of the terminal may be replaced with the UDM (UDM of User Identifier) of the user identifier, and the UDM (UDM of User Identifier) of the user identifier may be replaced with the UDM (UDM of UE) of the terminal. 2. Second embodiment - When the SMSF for providing SMS to the terminal and the SMSF for providing SMS to the user identifier are different The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 11 shows an example of a procedure according to the second embodiment of the present specification. 1) step 1 The procedure defined in Section 4.13.3.1 (Registration procedures for SMS over NAS) of TS 23.502 v18.4.0 may be performed. Alternatively, the operations of FIGS. 6 and 7 may be performed. The UE may transmit its ID to the network during the registration procedure. For example, the UE may perform registration without a user identifier. SMSF#1 can be selected as the SMSF serving the terminal (subscriber, user 1). SMSF#2 may be selected as the SMSF serving the user identifier for the user (User 2). When an MT SMS occurs for a terminal (or subscriber) (or user 1), the MT SMS can be transmitted to the terminal via SMSF. 2) step 2 The terminal can detect (determine) that a user (User 2) wants to use the terminal. When a user (User 2) wants to use a terminal, the terminal can notify the network that the user (User 2) wants to use the terminal. For example, when a user (User 2) wants to use a terminal, the terminal can use a registration procedure to notify the network that the user (User 2) wants to use the terminal. For example, through another existing procedure / NAS message (or a newly defined procedure / NAS message), the terminal can notify the network that a user (User 2) wishes to use the terminal. The terminal may provide information about the user (e.g., user identifier information) to the network. For example, a terminal may transmit a registration request message to the AMF that includes information about the user (e.g., user identifier information). The registration request message may include information about the ID of the UE and an identifier for the new user (user 2). In addition, the registration request message may additionally include an indication that the new user (user 2) uses the UE. For example, the terminal may provide information about the user (e.g., user identifier information) to the network using a registration procedure. Or, the terminal may inform the network about the user (e.g., user identifier information) through another existing procedure / NAS message (or a newly defined procedure / NAS message). Additionally, depending on the terminal's settings, the terminal may transmit the following information to the network: - Whether to receive / use both SMS for the terminal and SMS for the user - Whether to receive / use SMS only for users or SMS only for terminals, etc. Alternatively, this information may be stored in the AMF local configuration, subscriber information of the UE and / or user profile. Instead of AMF receiving identification information of a user (User 2) attempting to use a terminal from a terminal, AMF may also receive identification information of a user (User 2) attempting to use a terminal from another NF. If registration has already been performed with a user identifier in step 1, the UDM involved in the registration may be a UDM of the user identifier (UDM of UE) instead of a UDM of the terminal (UDM of UE). Alternatively, the UDM involved in the registration may be a UDM of the terminal (UDM of UE) and a UDM of the user identifier (UDM of User Identifier). This may be because AMF needs subscriber information of the terminal throughout the registration process as it interacts with the UDM of the terminal (UDM of UE). 3) step 3 AMF can obtain a user profile for a user (user 2) currently using a terminal from the UDM of the user identifier. Although not shown in Fig. 10, an authentication operation for the user may be performed before step 3. Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). AMF can send information about the user identifier for the user (User 2) to UDM (UDM of User Identifier). Based on this, UDM (UDM of User Identifier) can send the user profile for the user (User 2) to AMF. 4) step 4 AMF can send Nsmsf_SMService_Deactivate Request message to SMSF#1 to deactivate SMS for the terminal. For example, if it is determined that SMS reception / use for a terminal is not permitted, SMF can send a Nsmsf_SMService_Deactivate Request message to deactivate SMS for the terminal. For a new user of the terminal (User 2), AMF can select a different SMSF (SMSF#2) than the SMSF (SMSF#1) for the terminal (User 1). AMF may select a different SMSF (SMSF#2) because the user (User 2) has SMSF information (e.g. information about SMSF#2) in his SMS-related subscription information. AMF may choose a different SMSF (SMSF#2) because SMSF#1 does not support registrations with users other than the registrant (e.g., User2). 5) step 5 SMSF#1 can perform the Nudm_UECM_Deregistration operation to delete the SMSF address for the terminal to the UDM (UDM of UE). Based on this, the UDM (UDM of UE) of the terminal can delete the SMSF address for the subscriber (user 1). SMSF#1 can send a Nudm_UECM_Deregistration message to the UDM (UDM of UE) of the terminal to delete the SMSF address for the terminal. Based on this, the UDM (UDM of UE) of the terminal can delete the SMSF address serving the subscriber (User 1). Then, the SMS transmission service for the subscriber (User 1) can be stopped / deactivated. 6) step 6 SMSF#1 can send a response to the Nsmsf_SMService_Deactivate Request message to AMF. 7) step 7 AMF can notify SMSF#2 that the user (User 2) wishes to use the terminal via Nsmsf_SMService_Activate Request message. The Nsmsf_SMService_Activate Request message can include a user identifier for the user (User 2). If it is determined that SMS reception / use is required for the user (User 2), AMF can notify SMSF#2 that the user (User 2) wishes to use the terminal via the Nsmsf_SMService_Activate Request message. In this case, the following steps can be performed if SMS reception is required for the user. AMF may provide information about a user (User 2) (e.g. information about the user identifier) to SMSF#2. SMSF#2 can recognize that the above terminal is used by the above user (User 2) and store information about this. Step 7 may be performed before step 4, or steps 4 and 7 may be performed in parallel. 8) step 8 SMSF#2 can perform Nudm_UECM_Registration operation to store SMSF address for said user (User 2) in UDM of User Identifier (UDM of User Identifier). Based on this, UDM of User Identifier (UDM for User 2) can store SMSF address for user (User 2). SMSF#2 can send a Nudm_UECM_Registration message to the UDM of User Identifier (UDM of User Identifier) to store an SMSF address for the user (User 2). Based on this, the UDM of User Identifier (UDM for User 2) can store an SMSF address serving the user (User 2). Then, the SMS transmission service for the user (User 2) can be initiated / activated. SMSF can send information about the user identifier for a user (User 2) to the UDM of User Identifier (UDM) via the above Nudm_UECM_Registration operation. 9) step 9 SMSF#2 can obtain SMS-related subscription information for a user (User 2) from the UDM of User Identifier. SMSF#2 can transmit information about the user identifier for the user (User 2) to the UDM of User Identifier (UDM of User Identifier). Based on this, the UDM of User Identifier can transmit SMS-related subscription information to SMSF#2. If SMS-related subscription information for a user (User 2) is stored / managed in the terminal's UDM (UDM of UE) as part of the terminal's subscriber information, AMF may obtain SMS-related subscription information for the user (User 2) and provide it to SMSF#2. 10) step 10 SMSF#2 can send a response to the Nsmsf_SMService_Activate Request message to AMF. 11) step 11 AMF can send a response message to the registration request to the terminal. If SMS service is allowed for the user (User 2), the response message may include an "SMS allowed" indication. When an MT SMS occurs for a user (User 2), the MT SMS can be sent to the user (User 2) using the terminal via SMSF#2. Based on the terminal being used by the above user (User 2), SMSF#2 can send an MT SMS to the terminal. SMSF#2 can provide SMS service to the terminal for the user (User 2) based on the SMS-related subscription information received in step 9. If SMS service for the user (User 2) is not allowed, then in step 10, SMSF#2 may send a response to AMF including information that SMS service for said user (User 2) is not allowed to be provided to the terminal. Then, in step 11, AMF may send a response message including an "SMS not allowed" indication to the terminal. Thereafter, when a user who wishes to use the terminal changes, steps 2 to 9 may be performed. At this time, in the contents described above in steps 2 to 9, the UDM (UDM of UE) of the terminal may be replaced with the UDM (UDM of old User Identifier) of the old user identifier, and the UDM (UDM of User Identifier) of the user identifier may be replaced with the UDM (UDM of new User Identifier) of the new user identifier. Alternatively, if the subscriber (user 1) uses the terminal instead of the user (user 2) thereafter, steps 2 to 9 may be performed. At this time, in the contents described above in steps 2 to 9, the UDM (UDM of UE) of the terminal may be replaced with the UDM (UDM of User Identifier) of the user identifier, and the UDM (UDM of User Identifier) of the user identifier may be replaced with the UDM (UDM of UE) of the terminal. II. SMS support via NAS for active user identifiers When a user accesses a service via 5GS using a user identifier, the question arises as to how to identify the user of the terminal's 3GPP subscription. The following may be relevant to this issue: - Whether and how 5GC supports identifying the user identifier associated with the UE's traffic; - Requirements related to user identifiers (e.g. uniqueness range and allocation method); - Information stored as part of a user ID profile (e.g., user identifier, associated security credentials, associated devices, user-specific QoS settings). This includes how the user ID profile is created / obtained, stored, and updated. - Whether and how user identifiers are associated with and disconnected from 3GPP subscriptions (i.e. connected) in an operator-controlled manner; - Per-user policies. For example, 5GS considers QoS settings for service differentiation. This specification may provide solutions to this problem. It can be assumed that the user identifier attempting to use an authorized terminal has been authenticated and authorized. To support SMS over NAS for active user identifiers, this specification may propose: - User identity profile (user profile) may include SUPI, GPSI and SMS management subscriber data (e.g. SMS teleservice, SMS blocking list) for a specific user identifier. The SUPI may be information for identifying a 3GPP subscription of a user using the user identifier. An identifier in the form of SUPI may be used as this identification information, or other identification information / identifier may be used. - The User Identity Profile (User Profile) may be stored in a UDM that stores subscription data for the associated 3GPP subscription. Alternatively, the User Identity Profile (User Profile) may be stored in a UDM that stores subscriber information / data for the associated SUPI and / or GPSI. - SMS subscription data representing all SMS transmission service subscriptions via NAS may be independent of the active user identifier. For example, AMF may check SMS subscription data stored in the terminal's subscription to determine whether the SMS service is permitted for the terminal. - If there is an active user identifier for the terminal (for example, if the terminal is used by a user other than the subscriber of the terminal), an SMS service bound to (corresponding to) the active user identifier can be supported for the terminal. 1. Third embodiment The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 12 shows an example of a procedure according to the third embodiment of the present specification. 1) step 1 The procedure defined in Section 4.13.3.1 (Registration procedures for SMS over NAS) of TS 23.502 v18.4.0 may be performed. Alternatively, the operations of FIGS. 6 and 7 may be performed. During the registration procedure, the terminal may include an indication that it supports SMS in the registration request message and transmit it to the network. Based on this indication, SMS via NAS transport may be activated. The UE may transmit its ID to the network during the registration procedure. For example, the UE may perform registration without a user identifier. AMF can activate SMS for subscribers (SUPI) of selected SMSFs. 2) step 2 MT SMS can be sent as SMS-GMSC. The MT SMS can be for subscribers registered in the terminal in step 1. 3) step 3 SMS-GMSC can interact with NRF to discover and select a UDM, then invoke Nudm_UECM_SendRoutingInfoForSM(subscriber's GPSI) to get routing information of nodes available for MT SMS delivery in the UDM. 4) step 4 SMS-GMSC can forward SMS messages to the SMSF provided by UDM. 5) step 5 SMS messages can be sent to the terminal as specified in section 4.13.3.6 or 4.13.3.7 of TS 23.502 v18.4.0. 6) step 6 A user corresponding to the user identifier (User_ID#1) may wish to use the above terminal. In this case, the terminal can send a registration request including User_ID#1 to AMF. The registration request may include information about the ID of the UE and the User_ID#1. Additionally, the registration request may include an indication that the new user uses the UE. Authentication and authorization can be performed for User_ID#1. 7) step 7 AMF may inform SMSF that SMS activation needs to be updated from subscriber to user with User_ID#1. AMF may send information about user identifier (e.g. User_ID#1 or equivalent) to SMSF. Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). AMF may provide SMSF with User_ID#1 and SUPI of User_ID#1. The user with User_ID#1 can be identified by SUPI and / or GPSI. Instead of using the Nsmsf_SMService_Update service action that needs to be redefined, the Nsmsf_SMService_Deactivate service action and the Nsmsf_SMService_Activate service action can be used to trigger steps 8 and 9 respectively. Based on a registration request from a user wishing to use the terminal (or a NAS message containing the user identifier of this user), such as step 6, AMF may perform step 7 or perform step 7 during the registration process. Alternatively, based on other messages (messages / information from the terminal or messages / information from other NFs) or procedures, the AMF may recognize a user attempting to use the terminal and perform step 7. The AMF may also disclose to the SMSF, either explicitly or implicitly, at least one of the following pieces of information: - That there is a user who wants to use the terminal or that there is an activated user. - Information indicating that the subscriber of the terminal is not using the terminal. The SMSF may also perform step 8 by obtaining the information described above from an NF other than the AMF. 8) step 8 SMSF can request to remove SMSF address for subscription by sending Nudm_UECM_Deregistration message to UDM. Based on this, UDM can delete SMSF address for subscriber (User 1). SMSF can send Nudm_UECM_Deregistration message to UDM to delete SMSF address for terminal. Based on this, UDM can delete SMSF address serving subscriber (User 1). Then, SMS transmission service for said subscriber (User 1) can be stopped / deactivated. 9) step 9 SMSF can request UDM (the UDM storing the user profile for User_ID#1) to add SMSF address for SUPI of User_ID#1 by sending Nudm_UECM_Registration message. SMSF can send Nudm_UECM_Registration message to UDM (UDM storing user profile for User_ID#1) to store SMSF address for said user (User 2). Based on this, UDM (UDM storing user profile for User_ID#1) can store SMSF address serving user (User 2). Then, SMS transmission service for said user (User 2) can be initiated / activated. The UDM for the subscriber (UDM of the terminal) and the UDM for the SUPI of User_ID#1 may be different or the same. 10) step 10 SMSF can obtain SMS management subscription data (e.g. SMS teleservice, SMS blocking list) for User_ID#1 stored in User ID profile (User Profile) from UDM (UDM storing User Profile for User_ID#1). 11) step 11 The SMSF may send a response to step 7 to the AMF. The above response may include information that SMS service for the user is permitted to be provided to the terminal. 12) step 12 AMF can send a registration approval message to the terminal for the registration request. If SMS service is allowed for the user (User 2), the response message may include an "SMS allowed" indication. If SMS service for the user (User 2) is not allowed, then in step 11, SMSF may send a response to AMF including information that SMS service for said user (User 2) is not allowed to be provided to said terminal. Then, in step 12, AMF may send a response message including an "SMS not allowed" indication to the terminal. 13) step 13 MT SMS can be sent as SMS-GMSC. Said MT SMS can be for a user registered in the terminal in step 6 to step 12 (a new user of said terminal). 14) step 14 SMS-GMSC can interact with NRF to discover and select a UDM, then invoke Nudm_UECM_SendRoutingInfoForSM (GPI of user with User_ID#1) to get routing information of nodes available for MT SMS forwarding in the UDM. 15) step 15 SMS-GMSC can forward SMS messages to the SMSF provided by UDM. 16) step 16 SMS messages can be sent to the terminal (new user of the terminal) as specified in section 4.13.3.6 or 4.13.3.7 of TS 23.502 v18.4.0. AMF can support performing SMS activation for a user (the user using the terminal) corresponding to a user identifier. SMSF can support registration in UDM for users (users using terminals) corresponding to user identifiers. SMSF can support obtaining SMS management subscription data for a user (a user using a terminal) corresponding to a user identifier. UDM can support storing user profiles. UDM may support providing SMS management subscription data to the SMSF for user identifiers using the terminal. 2. Fourth Example The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 13 shows an example of a procedure according to the fourth embodiment of the present specification. 1) step 1 The procedure defined in Section 4.13.3.1 (Registration procedures for SMS over NAS) of TS 23.502 v18.4.0 may be performed. Alternatively, the operations of FIGS. 6 and 7 may be performed. During the registration procedure, the terminal may include an indication that it supports SMS in the registration request message and transmit it to the network. Based on this indication, SMS via NAS transport may be activated. The UE may transmit its ID to the network during the registration procedure. For example, the UE may perform registration without a user identifier. AMF can activate SMS for subscribers (SUPI) of selected SMSFs. 2) step 2 MT SMS can be sent as SMS-GMSC. The MT SMS can be for subscribers registered in the terminal in step 1. 3) step 3 SMS-GMSC can interact with NRF to discover and select a UDM, then invoke Nudm_UECM_SendRoutingInfoForSM(subscriber's GPSI) to get routing information of nodes available for MT SMS delivery in the UDM. 4) step 4 SMS-GMSC can forward SMS messages to the SMSF provided by UDM. 5) step 5 SMS messages can be sent to the terminal as specified in section 4.13.3.6 or 4.13.3.7 of TS 23.502 v18.4.0. 6) step 6 A user corresponding to the user identifier (User_ID#1) may wish to use the above terminal. In this case, the terminal can send a registration request including User_ID#1 to AMF. The registration request may include information about the ID of the UE and the User_ID#1. Additionally, the registration request may include an indication that the new user uses the UE. Authentication and authorization can be performed for User_ID#1. 7) step 7 AMF may inform SMSF that SMS activation needs to be updated from subscriber to User_ID#1. AMF may send information about user identifier (e.g. User_ID#1 or equivalent) to SMSF. Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). Instead of using the Nsmsf_SMService_Update service action that needs to be redefined, the Nsmsf_SMService_Deactivate service action and the Nsmsf_SMService_Activate service action can be used to trigger steps 8 and 9 respectively. Based on a registration request from a user wishing to use the terminal (or a NAS message containing the user identifier of this user), such as step 6, AMF may perform step 7 or perform step 7 during the registration process. Alternatively, based on other messages (messages / information from the terminal or messages / information from other NFs) or procedures, the AMF may recognize a user attempting to use the terminal and perform step 7. The AMF may also disclose to the SMSF, either explicitly or implicitly, at least one of the following pieces of information: - That there is a user who wants to use the terminal or that there is an activated user. - Information indicating that the subscriber of the terminal is not using the terminal. The SMSF may also perform step 8 by obtaining the information described above from an NF other than the AMF. 8) step 8 An SMSF can request that an SMSF address be removed for subscription by sending a Nudm_UECM_Deregistration message to the UDM. SMSF can send Nudm_UECM_Deregistration message to UDM to delete SMSF address for terminal. Based on this, UDM can delete SMSF address serving subscriber. Then, SMS transmission service for said subscriber (User 1) can be stopped / deactivated. The Nudm_UECM_Deregistration message may contain access type information (e.g., 3GPP access) and subscriber SUPI information. 9) step 9 SMSF can request UDM (the UDM storing the user profile for User_ID#1) to add SMSF address for User_ID#1 by sending Nudm_UECM_Registration message. SMSF can send Nudm_UECM_Registration message to UDM (UDM storing user profile for User_ID#1) to store SMSF address for said user (User 2). Based on this, UDM (UDM storing user profile for User_ID#1) can store SMSF address serving user (User 2). Then, SMS transmission service for said user (User 2) can be initiated / activated. The Nudm_UECM_Registration message may contain access type information (e.g., 3GPP access) and SUPI information of User_ID#1. The UDM for the subscriber (UDM of the terminal) and the UDM for the SUPI of User_ID#1 may be different or the same. A UDM storing a user ID profile (user profile) can register and update a user identifier serving NRF. An SMSF can find a UDM storing a user ID profile (user profile) of a user identifier based on a user identifier. 10) step 10 SMSF can obtain SMS management subscription data (e.g. SMS teleservice, SMS blocking list) for User_ID#1 stored in User ID profile (User Profile) from UDM (UDM storing User Profile for User_ID#1). Obtaining SMS management subscription data (e.g., SMS teleservice, SMS blocking list) for User_ID#1 stored in the above user ID profile (user profile) can be interpreted as obtaining SMS management subscription data that is applied when a new user uses a terminal using User_ID#1. Obtaining SMS management subscription data (e.g., SMS teleservice, SMS blocking list) for User_ID#1 stored in the above User ID profile (User Profile) may also be interpreted as obtaining a User Profile (User Identity Profile) or a User Profile including SMS-related information for the SUPI of User_ID#1. In this case, the subscription data type you want to obtain may be a User Identity Profile or a User Identity Profile including SMS-related information. 11) step 11 The SMSF may send a response to step 7 to the AMF. The above response may include information that SMS service for the user is permitted to be provided to the terminal. 12) step 12 AMF can send a registration approval message to the terminal for the registration request. If SMS service is allowed for the user (User 2), the response message may include an "SMS allowed" indication. If SMS service for the user (User 2) is not allowed, then in step 11, SMSF may send a response to AMF including information that SMS service for said user (User 2) is not allowed to be provided to said terminal. Then, in step 12, AMF may send a response message including an "SMS not allowed" indication to the terminal. 13) step 13 MT SMS can be sent as SMS-GMSC. Said MT SMS can be for a user registered in the terminal in step 6 to step 12 (a new user of said terminal). 14) step 14 SMS-GMSC can interact with NRF to discover and select a UDM, then invoke Nudm_UECM_SendRoutingInfoForSM (GPI of user with User_ID#1) to get routing information of nodes available for MT SMS forwarding in the UDM. 15) step 15 SMS-GMSC can forward SMS messages to the SMSF provided by UDM. 16) step 16 SMS messages can be sent to the terminal (new user of the terminal) as specified in section 4.13.3.6 or 4.13.3.7 of TS 23.502 v18.4.0. AMF may support performing SMS activation for user identifiers using terminals. SMSF can support registering user identifiers using terminals into UDM. SMSF may support obtaining SMS management subscription data for user identifiers using terminals. UDM can support storing user profiles. UDM may support providing SMS management subscription data to the SMSF for user identifiers using the terminal. Unlike in Figure 12, step 8 may not be performed. Or, the procedure / action that triggers step 8 may not be performed. Or, even if step 8 is performed, the UDM may not accept or reject it. SMSF may also provide information about the reason / cause for deregistration when sending the message in step 8 above (e.g., UE is used by a user other than the subscriber, etc.). When a non-subscriber user (a user using a user identifier) uses a terminal, the SMSF (or AMF, UDM) may decide not to perform the action of deleting the SMSF from the UDM for the subscriber based on one or more of the following pieces of information: - Information requested or provided by the UE / user. For example, even if a user other than the subscriber uses the terminal, the UE may provide information requesting / instructing not to deregister the subscriber's SMSF or to keep it activated. - Based on subscriber information of the UE. For example, the subscriber information contains information requesting / instructing not to deregister the subscriber's SMSF or to keep it activated even if a user other than the subscriber uses the terminal. - User profile information of a user who wishes to use a terminal. For example, even if the user uses a terminal that is permitted to be used, the User Identity Profile includes information requesting / instructing not to deregister the SMSF of the subscriber of the terminal or to keep it activated. - Local configuration / policy and / or operator policy set in one or more of the 5GC NFs among AMF, SMSF and UDM. For example, information requesting / instructing that the subscriber's SMSF not be deregistered or kept activated even if a user other than the subscriber uses the terminal is set in the 5GC NF. - Information provided while performing authentication / authorization for a user who wishes to use a terminal. For example, when performing authentication / authorization to determine whether the user can use the terminal, the SMSF (or AMF) receives information requesting / instructing not to deregister the subscriber's SMSF or to keep it activated. - Other information When a non-subscriber user (e.g., a user using a user identifier) uses a terminal, if the SMSF for the subscriber is not deleted from the UDM, when an MT SMS for the subscriber is generated, the MT SMS can be delivered to the terminal via the SMSF. Also, in this case, if the subscriber who owns the terminal is using another UE by using the user identifier, the SMS service can be activated through the other terminal. Based on this, a serving SMSF can exist. In this case, when an MT SMS occurs for the subscriber, there can be two SMSFs serving the same access type (e.g., 3GPP access). Then, SMS-GMSC can simultaneously deliver the MT SMS to the two SMSFs mentioned above. In addition, three or more serving SMSFs may be created when a subscriber owns a terminal and uses multiple other terminals using the user identifier. In this case, when an MT SMS for the subscriber occurs, SMS-GMSC may cause the MT SMS to be delivered simultaneously to three or more SMSFs described above. III. SMS support via NAS considering users An MT SMS of an activated user may not be delivered to a terminal having an IMSI associated with the GPSI that is the target of SMS redirection (i.e., the GPSI of the activated user), because the MT SMS is delivered to the terminal used by the activated user. It may be suggested not to provide SMS to other users who are not subscribers of the terminal while other users are using the terminal. When a user logs into the terminal, the subscriber's SMSF address may be deleted from the UDM so that SMS is no longer provided to the subscriber of the terminal. User identifiers attempting to use an authorized terminal can be authenticated and authorized. When a user other than the subscriber of the terminal is activated, the following two options may be proposed: - Option #1: SMS can be delivered to the active user (the other user mentioned above) instead of the subscriber of the terminal. - Option #2: SMS may not be available to all active users or subscribers on the terminal. (1) Option #1: SMS support via NAS for active user identifiers For Option #1, the MT SMS for an activated user may not be delivered to the terminal having the IMSI associated with the GPSI that is the target of the SMS redirection (i.e., the GPSI of the activated user). The MT SMS may be delivered to the terminal used by the activated user. This option may suggest the following to support SMS via NAS for active user identifiers: - The User ID Profile (User Profile) may contain GPSI and SMS management subscription data (e.g. SMS teleservice, SMS block list) for a particular user identifier. The GPSI used for SMS services may be in MSISDN format. - User ID profiles (user profiles) can be stored in the UDM, which stores subscription data for connected 3GPP subscriptions. - Since SMS subscription data representing subscriptions to all SMS delivery services via NAS is independent of the active user identifier, AMF can check whether SMS services are permitted for the terminal by checking the SMS subscription data stored in the terminal's subscription. - If there is an active user identifier for the terminal, an SMS service bound to the active user identifier can be supported for the terminal. (2) Option #2: Do not provide SMS to active users SMS may not be delivered to active users. The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 14 shows an example of a procedure according to the fifth embodiment of the present specification. 1-6) Steps 1 to 6 can be applied to the contents of steps 1 to 6 of Fig. 12. 7) step 7 The AMF may send an SM Service Update Request to the SMSF to notify that the SMS activation needs to be updated from the subscriber to the user with User_ID#1. The AMF may provide the SMSF with User_ID#1 and the GPSI of User_ID#1. The AMF may send the SMSF information about the user identifier (e.g., User_ID#1 or its equivalent). Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). The above SM service update request may include User_ID#1 and / or GPSI of User_ID#1. Instead of using the Nsmsf_SMService_Update service action, which must be redefined, steps 8 and 9 can be triggered using the Nsmsf_SMService_Deactivate and Nsmsf_SMService_Activate service actions, respectively. 8) step 8 An SMSF can request that an SMSF address be removed for subscription by sending a Nudm_UECM_Deregistration message to the UDM. SMSF can send Nudm_UECM_Deregistration message to UDM to delete SMSF address for terminal. Based on this, UDM can delete SMSF address serving subscriber (User 1). Then, SMS transmission service for said subscriber (User 1) can be stopped / deactivated. 9) step 9 SMSF can request addition of SMSF address for GPSI of User_ID#1 by sending Nudm_UECM_Registration message to UDM. 10) step 10 UDM can send Nnrf_NFManagement_NFUpdate to NRF to notify that UDM supports GPSI for user identifier User_ID#1. 11) step 11 SMSF can obtain SMS management subscription data (e.g. SMS teleservice, SMS blocking list) for User_ID#1 stored in User ID profile (User Profile). SMSF can send a request to UDM. Based on this, UDM can send SMS management subscription data (e.g. SMS teleservice, SMS blocking list) for User_ID#1 stored in User ID profile (User Profile) to SMSF. 12) step 12 The SMSF may send a response to step 7 to the AMF. 13) step 13 AMF can send a registration acceptance to the terminal. 14) step 14 MT SMS can be sent as SMS-GMSC. The above MT SMS may be for the user registered in the terminal in step 6-step 13 (the user corresponding to User_ID#1). 15) step 15 SMS-GMSC can invoke Nnrf_NFDiscovery with NRF to retrieve and select UDM for GPSI of user with User_ID#1. 16) step 16 SMS-GMSC can retrieve routing information of nodes available for MT SMS forwarding from UDM by invoking Nudm_UECM_SendRoutingInfoForSM(GPI of user using User_ID#1). 17) step 17 Based on the information received from UDM, SMS-GMSC can forward MT SMS messages to SMSF. 18) step 18 SMS messages can be sent to terminals as specified in 4.13.3.6 or 4.13.3.7 of TS 23.502 v18.4.0. After step 18 is performed, if the activated user identifier of the terminal is changed, steps 6 through 13 can be performed with the following differences: - In step 6, the terminal may include a new user identifier User_ID#2. - In step 7, AMF can include a new user identifier User_ID#2. - In step 8, SMSF can request UDM to delete SMSF address for user identifier User_ID#1. - In step 9, SMSF can request to add SMSF address for GPSI of User_ID#2 to UDM. - In step 10, UDM can trigger Nnrf_NFManagement_NFUpdate to notify that UDM supports GPSI of user identifier User_ID#2 and does not support GPSI of user identifier User_ID#1. - In step 11, SMSF can obtain SMS management subscription data (e.g. SMS teleservice, SMS blocking list) for User_ID#2 stored in User ID profile (User Profile). The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 15 shows an example of a procedure according to the sixth embodiment of the present specification. SMS for active users may not be provided to the terminal. 1-6) Steps 1 to 6 can be applied to the contents of steps 1 to 6 of Fig. 14. In Step 6, the terminal may also send a registration request message including information that SMS over NAS is not supported (SMS over NAS not supported). In step 1, the terminal can perform the registration procedure by including information that SMS over NAS is supported (SMS over NAS supported) in the registration request message. After this, based on the fact that a user other than the subscriber of the terminal is using the terminal, the terminal can provide information to the network that SMS over NAS is not supported. After this, when the subscriber of the terminal attempts to use the terminal again, the terminal can perform a registration procedure by including information that SMS over NAS is supported (SMS over NAS supported) in the registration request message. 7) step 7 AMF can release the UE context for SMS from SMSF via Nsmsf_SMService_Deactivate service operation. For example, SMS service authorization for a UE subscriber can be removed from SMSF. Based on the user identifier included in the registration request message, AMF can recognize that the user of said UE has changed to a new / specific user (User 2). Based on the user's registration request (or the NAS message containing the user's user identifier), AMF may perform step 7 or may perform step 7 during the registration procedure based on said registration request. Alternatively, based on other messages (either messages / information from the UE or messages / information from other NFs) or procedures, the AMF may recognize a user attempting to use the terminal and perform step 7. Instead of AMF sending Nsmsf_SMService_Deactivate Request to SMSF, AMF can also use other service operation (conventional or newly defined service operation) to explicitly or implicitly inform SMSF that there is a user trying to use terminal (or that there is an activated user) (or that the subscriber of terminal does not use terminal). SMSF can also receive this information from another NF other than AMF and perform step 8. 8) step 8 An SMSF may request that UDM delete the SMSF address for a subscriber. 9) step 9 The SMSF may send a response to step 7 to the AMF. 10) step 10 AMF may send registration approval to the terminal. If there is an activated user for the terminal (i.e., a user other than the subscriber of the terminal is using the terminal), SMS for the UE subscriber or the activated user may not be provided on the terminal. Steps 7-9 may be performed in parallel with step 10, or may be performed after step 10. When a subscriber performs IMS registration using a terminal, the terminal may include the "+g.3gpp.smsip" parameter in the Contact header of the SIP REGISTER message to receive SMS based on IMS. When a non-subscriber user performs IMS registration using a terminal (e.g., for voice call service, etc.), the terminal may not include the "+g.3gpp.smsip" parameter in the Contact header of the SIP REGISTER message. This may prevent SMS for the user from being transmitted to the terminal while the user is using it. If the S-CSCF had previously performed registration with the IP-SM-GW as a subscriber of the terminal performed IMS registration using the terminal, the S-CSCF may also perform deregistration with the IP-SM-GW as a result of IMS registration of a user other than the subscriber. Alternatively, if a user other than the subscriber of the terminal uses the terminal, the terminal may include the "+g.3gpp.smsip" parameter in the Contact header of the SIP REGISTER message. In this case, if the S-CSCF has performed registration with the IP-SM-GW, the S-CSCF may recognize that the user is using the terminal and perform deregistration for the subscriber previously. AMF may support activating SMS for users of user identifiers using terminals. SMSF can support registration with UDM for user identifiers using terminals. SMSF can support the acquisition of SMS management subscription data for user identifiers using terminals. UDM can support storage of user profiles. UDM may support providing SMS management subscription data to the SMSF for user identifiers using the terminal. UDM can support updating the user's GPSI with NRF. If a user other than the subscriber is activated for the terminal, AMF may support deactivating SMS of the previously activated terminal subscriber. The network can identify the subscriber or user using the terminal and deliver SMS messages correctly to that subscriber or user. The following actions can be performed: - AMF can provide SMSF with information about the user attempting to use the terminal (e.g. user identifier). - The above SMSF can provide information about a user who wants to use the terminal to the UDM. Accordingly, the UDM can store the serving SMSF information of the user. - If the UDM that stores / manages subscriber information for a terminal and the UDM that stores / manages user profile information for a user who can use the terminal are different, the SMSF can notify the UDM that stores / manages subscriber information for the terminal that it no longer serves the terminal. The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 16 illustrates the AMF's procedure for disclosure of this specification. 1. AMF (Access and Mobility Management Function) can receive a registration request message from UE (User Equipment). The above registration request message may include an identifier of a specific user of the UE. 2. Based on the above identifier, the AMF can send an update request for the SMS service to the SMSF (Short Message Service Function). The above SMSF may be a network node for SMS service for the UE and the specific user. The above update request may include information about the identifier. The above update request may include information requesting discontinuation of SMS service for the UE. The above AMF can transmit information about the above identifier to the UDM (Unified Data Management) for the above identifier. The above AMF can receive a user profile for the specific user from the UDM for the above identifier. The above AMF may receive a response to the above update request from the above SMSF. The above response may include information that an SMS service for the specific user is provided to the UE. The above registration request message may include an identifier of the UE. The above registration request message may include information that the specific user uses the UE. The drawings below are created to illustrate specific examples of the present specification. The names of specific devices or names of specific signals / messages / fields depicted 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 drawings below. Figure 17 illustrates the SMSF's procedures for disclosure of this specification. 1. SMSF (Short Message Service Function) can receive an update request for SMS service for UE (User Equipment) from AMF (Access and Mobility Management Function). The above SMSF may be a network node for SMS service for the UE and the specific user. The above update request may include information about an identifier of a specific user of the UE. 2. Based on the information about the identifier, the SMSF may send a first request message to the UDM (Unified Data Management) for the UE requesting deletion of the SMSF address for the UE. 3. Based on the information about said identifier, said SMSF may send a second request message to the UDM for said identifier requesting storage of an SMSF address for said specific user. The second request message may include information about the identifier. 4. Based on the second request message, the SMSF can receive SMS related information for the specific user from the UDM for the identifier. The above update request may include information requesting discontinuation of SMS service for the UE. The above SMSF may send a response to the above update request to the above AMF. The above response may include information that an SMS service for the specific user is provided to the UE. The SMS related information for said particular user may include an indication that the SMS related information for said UE applies. The SMS related information for the specific user may include a list of UEs for which SMS service is not provided for the specific user. The SMS related information for the specific user may include information that SMS service is not provided to the specific user. Below, a device for performing communication according to some embodiments of the present specification is described. For example, a device may include a processor, a transceiver, and memory. For example, a processor may be configured to be operatively coupled with a memory and a processor. The operations performed by the above processor include: the AMF receiving a registration request message from the UE; the registration request message including an identifier of a specific user of the UE; and, based on the identifier, the AMF transmitting an update request for an SMS service to the SMSF, wherein the SMSF is a network node for an SMS service for the UE and the specific user, and the update request may include information about the identifier. Below, a processor of a device for providing communication according to some embodiments of the present specification is described. The operations performed by the above processor include: the AMF receiving a registration request message from the UE; the registration request message including an identifier of a specific user of the UE; and, based on the identifier, the AMF transmitting an update request for an SMS service to the SMSF, wherein the SMSF is a network node for an SMS service for the UE and the specific user, and the update request may include information about the identifier. Below, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described. According to some embodiments of the present disclosure, the technical features of the present disclosure may be implemented directly in hardware, software executed by a processor, or a combination of the two. 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, the 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. Some examples of storage media are coupled to the processor such that the processor can read information from the storage media. Alternatively, the storage media may be integral to the processor. The processor and the storage media may reside in an ASIC. In other examples, the processor and the storage media may reside as separate components. Computer-readable media may include tangible and nonvolatile computer-readable storage media. For example, nonvolatile computer-readable media can include random access memory (RAM), such as synchronization dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media can also include combinations of the above. Additionally, the methods described herein can be realized at least in part by a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer. According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more instructions stored thereon can be executed by a processor of a base station. The one or more stored commands include: a step in which the AMF receives a registration request message from the UE; the registration request message includes an identifier of a specific user of the UE; and, based on the identifier, the AMF transmits an update request for an SMS service to the SMSF, wherein the SMSF is a network node for an SMS service for the UE and the specific user, and the update request may include information about the identifier. Below, a nonvolatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described. This specification may have various effects. For example, through the procedure disclosed in this specification, a new user of the terminal can be provided with SMS service. The effects that can be obtained through specific examples of this specification are not limited to the effects listed above. For example, there may be various technical effects that a person having 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 in this specification, and may include various effects that can be understood or derived from the technical features of this specification. The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims of this specification and the technical features of the device claims of this specification may be combined and implemented as a method. Other implementations are within the scope of the claims as follows.

Claims

1. As a method, A step in which AMF (Access and Mobility Management Function) receives a registration request message from UE (User Equipment); The above registration request message includes an identifier of a specific user of the UE, Based on the above identifier, the AMF comprises a step of sending an update request for SMS service to the SMSF (Short Message Service Function), The above SMSF is a network node for SMS service for the above UE and the above specific user, A method wherein said update request includes information about said identifier.

2. In paragraph 1, A method wherein the above update request includes information requesting discontinuation of SMS service for the UE.

3. In paragraph 1 or 2, A step in which the AMF transmits information about the identifier to a UDM (Unified Data Management) for the identifier; A method further comprising the step of the AMF receiving a user profile for the specific user from the UDM for the identifier.

4. In any one of the clauses 1 to 3, The AMF further comprises a step of receiving a response to the update request from the SMSF, A method wherein the above response includes information that an SMS service for the specific user is provided to the UE.

5. In any one of paragraphs 1 to 4, A method wherein the above registration request message includes an identifier of the UE.

6. In any one of paragraphs 1 to 5, A method wherein the above registration request message includes information that the specific user uses the UE.

7. As a method, A step in which the SMSF (Short Message Service Function) receives an update request for SMS service for UE (User Equipment) from the AMF (Access and Mobility Management Function); The above SMSF is a network node for SMS service for the above UE and the above specific user, The above update request includes information about the identifier of a specific user of the UE, Based on the information about the identifier, the SMSF sends a first request message to the UDM (Unified Data Management) for the UE requesting deletion of the SMSF address for the UE; Based on the information about said identifier, the SMSF sends a second request message to the UDM for said identifier, requesting storage of an SMSF address for said specific user; The second request message contains information about the identifier, A method comprising the step of the SMSF receiving SMS related information for the specific user from the UDM for the identifier based on the second request message.

8. In paragraph 7, A method wherein the above update request includes information requesting discontinuation of SMS service for the UE.

9. In paragraph 7 or 8, further comprising the step of the SMSF sending a response to the update request to the AMF; A method wherein the above response includes information that an SMS service for the specific user is provided to the UE.

10. In any one of paragraphs 7 to 9, A method wherein the SMS related information for said specific user includes an indication that the SMS related information for said UE applies.

11. In any one of the clauses 7 to 9, A method wherein the SMS related information for the specific user includes a list of UEs for which SMS service is not provided for the specific user.

12. In any one of paragraphs 7 to 9, A method wherein the SMS related information for the specific user includes information that SMS service is not provided to the specific user.

13. As an AMF (Access and Mobility Management Function) that performs communication, At least one transmitter and receiver; comprising at least one processor, The operation performed by said at least one processor is an AMF method according to any one of claims 1 to 6.

14. As a SMSF (Short Message Service Function) that performs communication, At least one transmitter and receiver; comprising at least one processor, An SMSF wherein the operation performed by said at least one processor is a method according to any one of claims 7 to 12.

15. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to said at least one processor, A device wherein an operation performed based on the above command being executed by the at least one processor is a method according to any one of claims 1 to 6.

16. A non-volatile computer-readable storage medium that records commands, A nonvolatile computer-readable storage medium which, when executed by one or more processors, causes the one or more processors to perform a method according to any one of claims 1 to 6.

Images