Communication based on radio access technology

Abstract

One aspect of the present disclosure provides a method. The method may comprise the steps in which: a UE transmits, on the basis of a first radio access technology, a first registration request message to a first network entity associated with mobility; the UE receives, from the first network entity, a first registration acceptance message; and the UE transmits, on the basis of a second radio access technology, a service request message to a second network entity associated with mobility.

Description

Communication based on wireless access technology

[0001] This specification relates to mobile communication.

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

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

[0004] NR targets a single technical framework that covers all deployment, usage, and requirements, including eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type-Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR must be forward compatible by nature.

[0005] According to conventional technology, a terminal can perform only one registration procedure at a time based on a single wireless access technology (e.g., 3GPP access). This results in a problem where it is impossible for the terminal to register simultaneously through multiple wireless access technologies.

[0006] According to conventional technology, a terminal can perform only one registration procedure at a time based on a single wireless access technology (e.g., 3GPP access). This results in a problem where it is impossible for the terminal to register simultaneously through multiple wireless access technologies.

[0007] In one embodiment, a method is provided. The method may include the steps of: a UE transmitting a first registration request message to a first network entity related to mobility, based on a first wireless access technology; the UE receiving a first registration acceptance message from the first network entity; and the UE transmitting a service request message to a second network entity related to mobility, based on a second wireless access technology.

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

[0009] In one embodiment, a method is provided. The method may include the steps of: a second network entity related to mobility receiving a service request message from a UE based on a second wireless access technology; the second network entity transmitting a first request message containing information related to requesting user plane activation of the session to a third network entity related to session management; the second network entity receiving a first response message from the third network entity containing a second request message for requesting session resources from a base station based on the second wireless access technology; and the second network entity transmitting the second request message to the base station.

[0010] In another aspect, a device for implementing the above method is provided.

[0011] For example, it can be effectively supported for a terminal to register simultaneously through multiple wireless access technologies. For example, the terminal and / or network can manage the registration of the terminal by wireless access technology type. Accordingly, it may be permitted for the terminal to register simultaneously based on multiple wireless access technology types. The terminal can effectively receive services through multiple wireless access technologies.

[0012] For example, network entities related to mobility, such as terminals and / or networks, can effectively store and manage the terminal's context based on the wireless access technology type.

[0013] For example, terminals and / or networks can effectively manage or / or store states related to mobility management by wireless access technology type.

[0014] For example, a terminal and / or network can effectively perform periodic registration updates for multiple wireless access technology types. For example, a terminal can effectively perform periodic registration updates for multiple wireless access technology types through a single wireless access type.

[0015] For example, the terminal and / or network can use NAS MM messages to effectively support handover between wireless access technologies for a session (e.g., PDU session). By performing handover based on NAS MM messages, signaling between the terminal and the network and / or signaling between network entities can be effectively performed.

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

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

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

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

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

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

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

[0023] FIGS. 9a and FIGS. 9b are examples of additional registration procedures according to one embodiment of the present disclosure.

[0024] FIGS. 10a and FIGS. 10b are examples of a deregistration procedure according to one embodiment of the present disclosure.

[0025] FIG. 11 is an example of performing periodic registration updates according to one embodiment of the present disclosure.

[0026] FIGS. 12a to 12c are examples of a procedure for handing over a PDU session according to one embodiment of the present disclosure.

[0027] FIG. 13 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0028] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

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

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

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

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

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

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

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

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

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

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

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

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

[0041] The three main requirement categories for 5G are (1) enhanced Mobile BroadBand (eMBB) category, (2) massive Machine Type Communication (mMTC) category, and (3) Ultra-Reliable and Low Latency Communications (URLLC) category.

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

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

[0044] Wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), eXtended Reality (XR) devices (100c), portable devices (100d), home appliances (100e), Internet-Of-Things (IoT) devices (100f), and Artificial Intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

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

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

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

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

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

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

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

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

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

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

[0055] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

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

[0057] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

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

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

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

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

[0062] 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 generally, the memory (204) may be placed outside the processing chip (201).

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

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

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

[0066] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an RRC (Radio Resource Control) layer, and an SDAP (Service Data Adaptation Protocol) layer). One or more processors (102, 202) may generate one or more PDUs (Protocol Data Units), one or more SDUs (Service Data Units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0067] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors. One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cache memory, computer read storage media, and / or combinations thereof.One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] - AUSF (Authentication Server Function)

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

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

[0089] - USDF (Unstructured Data Storage Function)

[0090] - NEF (Network Exposure Function)

[0091] - I-NEF (Intermediate NEF)

[0092] - NRF (Network Repository Function)

[0093] - NSSF (Network Slice Selection Function)

[0094] - PCF (Policy Control Function)

[0095] - SMF (Session Management Function)

[0096] - UDM (Unified Data Management)

[0097] - UDR (Unified Data Repository)

[0098] - UPF (User Plane Function)

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

[0100] - AF (Application Function)

[0101] - UE (User Equipment)

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

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

[0104] - NWDAF (Network Data Analytics Function)

[0105] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] - Mobility registration update; or

[0139] - Periodic registration update; or

[0140] - Emergency registration

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

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

[0143] First, the procedure of Fig. 5 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0174] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0202] First, the procedure of Fig. 7 will be explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0239] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0247] Now, the procedure of Fig. 8 following the procedure of Fig. 7 is explained.

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

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

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

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

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

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

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

[0255] After this step, the AMF delivers the relevant events that the SMF has subscribed to.

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

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

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

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

[0260] According to conventional technology, a terminal can perform only one registration procedure at a time based on a single wireless access technology (e.g., 3GPP access). This results in a problem where it is impossible for the terminal to register simultaneously through multiple wireless access technologies.

[0261] For example, according to the prior art, in a 5G network, when a terminal performs registration (e.g., a registration procedure), it can perform registration by access type. For example, a terminal can perform registration with a 3GPP access and registration with a non-3GPP access. In this case, the terminal can perform only one registration at a time in the 3GPP access. According to the prior art, it is impossible for a terminal to register simultaneously through multiple 3GPP accesses.

[0262] In addition, according to the prior art, a terminal could perform dual registration for each of two different types of networks (e.g., a 4G network and a 5G network). However, the prior art dual registration also has a problem in that it does not support the terminal registering by RAT type within a single network.

[0263] Conventional technology has the following problems. For example, a terminal can perform registration through a TN (Terrestrial Networks) base station using 6G radio. Subsequently, there is a problem that the terminal cannot perform registration through an NTN (Non-Terrestrial Networks) base station using 6G radio. If the terminal performs registration again through an NTN base station after being registered through a TN base station, the registration performed through the TN base station is lost.

[0264] In addition, in such cases, the MM NF (e.g., 6G AMF) to which the terminal is connected via NTN and the MM NF (e.g., 6G AMF) to which the terminal is connected via TN may be different. In this case, if the terminal performs a registration procedure after changing from an NT base station to an NTN base station or from an NTN base station to a TN base station, additional procedures such as exchanging UE Context between the two MM NFs (e.g., 6G AMF) may be required. However, according to the prior art, there is a problem in that such additional procedures are not supported at all. Consequently, according to the prior art, if the terminal performs a registration procedure through a base station based on a first Radio Access Technology (RAT) (e.g., TN) and then performs a registration procedure through a base station based on a second RAT (e.g., NTN), the terminal may not receive service while the registration procedure is being performed.

[0265] In one embodiment of the present disclosure, an example of a solution to solve the problems of the prior art is described. For example, in one embodiment of the present disclosure, an example of a method for managing terminal registration by RAT type is described.

[0266] The method proposed in this disclosure may be composed of a combination of one or more of the following examples of operations / configurations / steps.

[0267] In this specification, User Equipment (UE) and terminal may be used as terms with the same meaning.

[0268] In this specification, TN base station, TN RAT, and TN RAN may be used as terms with the same meaning.

[0269] In this specification, Low Earth Orbit (LEO) NTN base station, LEO NTN RAT, and LEO NTN RAN may be used as terms with the same meaning.

[0270] In this specification, Geostationary Earth Orbit (GEO) NTN base station, GEO NTN RAT, and GEO NTN RAN may be used as terms with the same meaning.

[0271] For reference, in this specification, MM NF (e.g., 6G AMF) may be an example of a network entity (or node) related to mobility management. For example, a network entity (or node) related to mobility management may be a network entity (or node) that supports operations for managing the mobility of a terminal. A 6G AMF may be an example of a network entity of a 6G and / or 6G and later mobile communication system capable of performing some or all of the operations performed by a 5G AMF, for example. In this disclosure, the designation of a 6G AMF is merely illustrative, and the description relating to MM NF (e.g., 6G AMF) may apply to a network entity related to mobility management of a 6G and / or 6G and later mobile communication system within the scope of this disclosure.

[0272] Hereinafter, the first to fourth examples of the present disclosure are described. In some embodiments, the first to fourth examples of the present disclosure may each be applied independently. In some embodiments, at least one of the first to fourth examples of the present disclosure may be combined.

[0273] 1. First example of the present disclosure

[0274] In the first example of the present disclosure, an example is described in which a terminal and / or network manages registration by RAT type.

[0275] According to one embodiment, a terminal and / or network can manage registration by RAT type of the terminal. To this end, the terminal and / or network can manage registration using RAT type information when performing a registration procedure.

[0276] For example, a terminal can manage a separate Mobility Management (MM) Non Access Stratum (NAS) Context (or MM Context) for each RAT type. A network can also manage a UE Context for each RAT type. For example, managing a UE Context for each RAT type may mean that the terminal and / or network store the terminal's security context separately for each RAT type. For example, the terminal and / or network can perform independent security procedures for each RAT type.

[0277] According to one embodiment, the terminal and / or network may manage each MM status (e.g., IDLE status, and / or CONNECTED status) and temporary ID (e.g., 6G Globally Unique Temporary UE Identity (GUTI)) for each RAT type. Additionally, the terminal and / or network may manage the context for a session for each RAT type. For reference, GUTI may be a Globally Unique Temporary Identity.

[0278] In some implementations, when a terminal performs registration with a network (e.g., registration procedure), the MM NF (e.g., 6G AMF) may perform the following actions. For example, the MM NF (e.g., 6G AMF) may inform the terminal of RAT type information for which additional registration is permitted. For example, the terminal may register with the MM NF (e.g., 6G AMF) through a TN base station. In this case, the MM NF (e.g., 6G AMF) may transmit information related to additional registration to the terminal. The information related to additional registration may be, for example, information that additional registration is possible through a RAT type (e.g., NTN) different from the RAT type (e.g., TN) associated with the registration performed by the terminal. For example, the information related to additional registration may include information that additional registration is possible through an NTN base station.

[0279] In some implementations, based on capability information provided by the terminal, request information that the terminal wants to register based on additional RAT types, subscriber information of the terminal, local policy set in the MM NF, information provided by the Policy Management (PM) NF (e.g., 6G PCF), etc., the MM NF (6G AMF) may decide to transmit information related to additional registration and / or information related to additional registration to the terminal.

[0280] For example, if the terminal has registered with an MM NF (e.g., 6G AMF), the MM NF (e.g., 6G AMF) may transmit information to the terminal, such as information on RAT types that allow for additional registration (e.g., 6G NTN Radio (GEO), 6G NTN Radio (LEO), 6G Radio (TN), etc.). In some implementations, information such as information on RAT types that allow for additional registration (e.g., 6G NTN Radio (GEO), 6G NTN Radio (LEO), 6G Radio (TN), etc.) may be included in information related to additional registration or may be information related to additional registration. Based on the information on RAT types that allow for additional registration, the terminal may know that simultaneous registration is supported through the RAT types included in the information on RAT types that allow for additional registration. The terminal may also perform an additional registration procedure through at least one of the RAT types included in the information on RAT types that allow for additional registration.

[0281] Hereinafter, with reference to FIGS. 9a and 9b, an example of a case in which a terminal registers through a TN base station and then registers through an NTN base station is described.

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

[0283] FIGS. 9a and FIGS. 9b are examples of additional registration procedures according to one embodiment of the present disclosure.

[0284] FIGS. 9a and 9b are examples of a method in which a terminal performs additional registration based on additional RAT type information provided by a network.

[0285] For reference, in the examples of FIGS. 9a and 9b, MM NF (TN) may be an MM NF related to TN. MM NF (NTN) may be an MM NF related to NTN. In the examples of FIGS. 9a and 9b, MM NF (TN) and MM NF (NTN) are depicted as separate objects, but this is merely an example. MM NF (TN) and MM NF (NTN) may be different network entities or the same network entity. For example, if MM NF (TN) and MM NF (NTN) are the same network entity, this network entity may store and / or manage UE contexts per RAT.

[0286] 1. The terminal can send a registration request message.

[0287] For example, the terminal can send a Registration Request message to register with the network through the TN base station.

[0288] In some implementations, the registration request message may include at least one of capability information indicating that the terminal supports simultaneous registration through another RAT, information indicating a desire for simultaneous registration, or information on the supported RAT type. The simultaneous registration may be interpreted as registering for 3GPP access through multiple (i.e., multiple) RATs, and this may be applied throughout this specification.

[0289] For reference, in this disclosure, simultaneous registration may also be expressed by other terms, such as additional registration. For example, the simultaneous registration described in this disclosure may mean that a terminal registers based on a plurality of RATs. The scope of this disclosure is not limited to the term simultaneous registration. For example, the description of simultaneous registration in this disclosure may be equally applied to any term related to a terminal registering based on a plurality of RATs.

[0290] 2. The MM NF (e.g., 6G AMF) can perform authentication on the terminal and obtain the terminal's subscriber information. Subsequently, the MM NF (e.g., 6G AMF) may decide to allow registration of the terminal. In some implementations, the MM NF (e.g., 6G AMF) may perform authentication on the terminal with the network entity involved in the authentication. After successful authentication, the MM NF (e.g., 6G AMF) can obtain the terminal's subscriber information from the SDM NF.

[0291] In this case, at step 2a, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM (Subscriber Data Management) NF (e.g., 6G UDM). For example, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM NF (e.g., 6G UDM) to register that the MM NF (e.g., 6G AMF) is the terminal's serving MM NF. For example, the MM NF (e.g., 6G AMF) can send a message related to Nsdm_Registration to the SDM NF (e.g., 6G UDM). In some implementations, the message related to Nsdm_Registration sent by the MM NF (e.g., 6G AMF) may include the terminal's current RAT type information. In some implementations, the message related to Nsdm_Registration transmitted by the MM NF (e.g., 6G AMF) may further include at least one of information indicating that the terminal supports simultaneous registration or information indicating that the terminal wants simultaneous registration.

[0292] In step 2a, the SDM NF (e.g., 6G UDM) may send a response containing information allowing simultaneous registration of terminals (e.g., a message related to Nsdm_Registration) to the MM NF (e.g., 6G AMF).

[0293] Also, in step 2b, the MM NF (e.g., 6G AMF) may retrieve the terminal's subscriber information and perform a subscription to receive notifications about changes to the terminal's subscriber information.

[0294] 3. MM NF (e.g., 6G AMF) can send a registration acceptance message to the terminal.

[0295] For example, MM NF (e.g., 6G AMF) can send a Registration Accept message to notify the terminal that registration has been accepted.

[0296] In some implementations, the MM NF (e.g., 6G AMF) may provide the terminal with information on the RAT types for which additional registration is allowed and / or information indicating that additional registration is allowed. For example, the MM NF (e.g., 6G AMF) may indicate to the terminal that additional registration is allowed through the RAT types for which additional registration is allowed (e.g., NTN (GEO) and / or TN).

[0297] For example, the MM NF (e.g., 6G AMF) may transmit to the terminal, along with the registration acceptance message, additional information on the RAT type for which registration is allowed and / or information indicating that additional registration is allowed. The registration acceptance message may also include additional information on the RAT type for which registration is allowed and / or information indicating that additional registration is allowed.

[0298] In some implementations, the MM NF (e.g., 6G AMF) may assign a temporary ID (e.g., 6G GUTI) to the terminal. For example, the MM NF (e.g., 6G AMF) may send the temporary ID (e.g., 6G GUTI) to the terminal along with a registration acceptance message. The registration acceptance message may also include the temporary ID (e.g., 6G GUTI).

[0299] In some implementations, MM NF (e.g., 6G AMF) can store and manage current RAT type information within the terminal's context.

[0300] In some implementations, the MM NF (e.g., 6G AMF) may provide the terminal with Registration Area information (e.g., TAI list) to manage the terminal's mobility. For example, the MM NF (e.g., 6G AMF) may transmit the Registration Area information (e.g., TAI list) to the terminal along with a registration acceptance message. The registration acceptance message may also include the Registration Area information (e.g., TAI list).

[0301] 4. The terminal can transmit a registration request message to an MM NF associated with the NTN via the NTN cell.

[0302] For example, based on the information received in step 3, the terminal may locate an NTN (GEO) cell and perform registration (e.g., transmit a registration request message). While performing the registration, the terminal may include additional information related to the registration (e.g., information indicating that it is an additional registration) in the Registration Request message. Additionally, the registration request message transmitted by the terminal may include at least one of capability information indicating that simultaneous registration is supported through another RAT, information indicating that simultaneous registration is desired, and / or information on the supported RAT type. In some implementations, the terminal may or may not include the temporary ID (e.g., 6G GUTI) received in step 3 in the registration request message.

[0303] 5. The MM NF (e.g., 6G AMF) can perform authentication on the terminal and obtain the terminal's subscriber information. Subsequently, the MM NF (e.g., 6G AMF) may decide to allow registration of the terminal. In some implementations, the MM NF (e.g., 6G AMF) may perform authentication on the terminal with the network entity involved in the authentication. After successful authentication, the MM NF (e.g., 6G AMF) can obtain the terminal's subscriber information from the SDM NF.

[0304] In this case, at step 5a, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM (Subscriber Data Management) NF (e.g., 6G UDM). For example, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM NF (e.g., 6G UDM) to register that the MM NF (e.g., 6G AMF) is the terminal's serving MM NF. For example, the MM NF (e.g., 6G AMF) can send a message related to Nsdm_Registration to the SDM NF (e.g., 6G UDM). In some implementations, the message related to Nsdm_Registration sent by the MM NF (e.g., 6G AMF) may include information on the terminal's current RAT type. In some implementations, the message related to Nsdm_Registration transmitted by the MM NF (e.g., 6G AMF) may further include at least one of information indicating that the terminal supports simultaneous registration or information indicating that the terminal wants simultaneous registration.

[0305] In step 5a, the SDM NF (e.g., 6G UDM) may send a response containing information allowing simultaneous registration of terminals (e.g., a message related to Nsdm_Registration) to the MM NF (e.g., 6G AMF).

[0306] Also, in step 5b, the MM NF (e.g., 6G AMF) may retrieve the terminal's subscriber information and perform a subscription to receive notifications about changes to the terminal's subscriber information.

[0307] 6. MM NF (e.g., 6G AMF) can send a registration acceptance message to the terminal.

[0308] For example, MM NF (e.g., 6G AMF) can send a Registration Accept message to notify the terminal that registration has been accepted.

[0309] In some implementations, the MM NF (e.g., 6G AMF) may provide the terminal with information on the RAT type for which additional registration is allowed and / or information indicating that additional registration is allowed. For example, the MM NF (e.g., 6G AMF) may inform the terminal that additional registration is allowed through the RAT type for which additional registration is allowed (e.g., NTN (GEO) and / or TN). For example, a registration acceptance message may include information on the RAT type for which additional registration is allowed and / or information indicating that additional registration is allowed.

[0310] For example, the MM NF (e.g., 6G AMF) may transmit to the terminal, along with the registration acceptance message, additional information on the RAT type for which registration is allowed and / or information indicating that additional registration is allowed. The registration acceptance message may also include additional information on the RAT type for which registration is allowed and / or information indicating that additional registration is allowed.

[0311] In some implementations, the MM NF (e.g., 6G AMF) may assign a temporary ID (e.g., 6G GUTI) to the terminal. For example, the MM NF (e.g., 6G AMF) may send the temporary ID (e.g., 6G GUTI) to the terminal along with a registration acceptance message. The registration acceptance message may also include the temporary ID (e.g., 6G GUTI).

[0312] In some implementations, MM NF (e.g., 6G AMF) can store and manage current RAT type information within the terminal's context.

[0313] In some implementations, the MM NF (e.g., 6G AMF) may provide the terminal with Registration Area information (e.g., TAI list) to manage the terminal's mobility. For example, the MM NF (e.g., 6G AMF) may transmit the Registration Area information (e.g., TAI list) to the terminal along with a registration acceptance message. The registration acceptance message may also include the Registration Area information (e.g., TAI list).

[0314] 7. The SDM NF (e.g., 6G UDM) can send a notification message (e.g., Nsdm_SDM_Notification message) to the MM NF (TN).

[0315] For example, an SDM NF (e.g., 6G UDM) may recognize in step 5a that the terminal is connected via an additional RAT. Based on the subscriber information change notification subscription requested by the MM NF (e.g., 6G AMF) in step 2b, the SDM NF (e.g., 6G UDM) may transmit information of the MM NF (NTN) that the terminal connected to via the NTN to the MM NF (TN). For example, a notification message (e.g., Nsdm_SDM_Notification message) may include information of the MM NF (NTN) that the terminal connected to via the NTN.

[0316] 8. The terminal may also send a registration request message to a new MM NF(TN).

[0317] For example, the terminal may move and exit the Registration Area received in step 3 via the TN base station. In this case, the terminal may transmit the Registration Request to a new MM NF (TN) via the RAN (TN). In this case, the terminal may include information related to the mobility registration update (e.g., information indicating that it is a mobility registration update) in the registration request message. Additionally, the terminal may include at least one of capability information indicating support for simultaneous registration through another RAT, information indicating a desire for simultaneous registration, and / or information on the supported RAT type in the registration request message. Additionally, the terminal may transmit the temporary ID (e.g., 6G GUTI) information from step 3 along with the registration request message.

[0318] When a terminal transmits a registration request message, the TN base station (e.g., RAN(TN) in FIG. 9b) can select a new MM NF (e.g., 6G AMF) and transmit the terminal's registration request message to the new MM NF (e.g., 6G AMF).

[0319] 9. A new MM NF (e.g., 6G AMF) can send a request message (e.g., Nmmnf_Communication_UEContext Request) to an older MM NF (e.g., 6G AMF). An older MM NF (e.g., 6G AMF) can send a response message (e.g., Nmmnf_Communication_UEContext Response) to the new MM NF (e.g., 6G AMF).

[0320] For example, a new MM NF (e.g., 6G AMF) that receives a registration request message from a terminal can request the terminal's context from the previous MM NF (e.g., 6G AMF) based on the temporary ID (e.g., 6G GUTI) transmitted by the terminal. In this process, the new MM NF (e.g., 6G AMF) can include the terminal's RAT type information (e.g., TN 6G Radio) in the request message (e.g., Nmmnf_Communication_UEContext Request) and transmit the request message to the previous MM NF (e.g., 6G AMF).

[0321] For example, the previous MM NF (e.g., 6G AMF) that received the request message may transmit the terminal's context information related to the terminal's RAT type information (e.g., information corresponding to the terminal's context that matches the requested RAT type) to the New MM NF (e.g., 6G AMF). For example, the previous MM NF (e.g., 6G AMF) may transmit a response message (e.g., Nmmnf_Communication_UEContext Response) containing the terminal's context information related to the terminal's RAT type information (e.g., information corresponding to the terminal's context that matches the requested RAT type) to the new MM NF (e.g., 6G AMF).

[0322] 10. The MM NF (e.g., 6G AMF) can perform authentication on the terminal and obtain the terminal's subscriber information. Subsequently, the MM NF (e.g., 6G AMF) may decide to allow registration of the terminal. In some implementations, the MM NF (e.g., 6G AMF) may perform authentication on the terminal with the network entity involved in the authentication. After successful authentication, the MM NF (e.g., 6G AMF) can obtain the terminal's subscriber information from the SDM NF.

[0323] In this case, at step 10a, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM (Subscriber Data Management) NF (e.g., 6G UDM). For example, the MM NF (e.g., 6G AMF) can perform Nsdm_Registration with the SDM NF (e.g., 6G UDM) to register that the MM NF (e.g., 6G AMF) is the terminal's serving MM NF. For example, the MM NF (e.g., 6G AMF) can send a message related to Nsdm_Registration to the SDM NF (e.g., 6G UDM). In some implementations, the message related to Nsdm_Registration sent by the MM NF (e.g., 6G AMF) may include the terminal's current RAT type information. In some implementations, the message related to Nsdm_Registration transmitted by the MM NF (e.g., 6G AMF) may further include at least one of information indicating that the terminal supports simultaneous registration or information indicating that the terminal wants simultaneous registration.

[0324] In step 10a, the SDM NF (e.g., 6G UDM) may send a response containing information allowing simultaneous registration of terminals (e.g., a message related to Nsdm_Registration) to the MM NF (e.g., 6G AMF).

[0325] Also, in step 10b, if necessary, the MM NF (e.g., 6G AMF) may retrieve the terminal's subscriber information and perform a subscription to receive notifications about changes to the terminal's subscriber information.

[0326] 11. SDM NF (e.g., 6G UDM) can perform deregistration notification (e.g., Nsdm_DeregistrationNotification) for old MM NF (e.g., 6G AMF).

[0327] For example, based on the RAT type information provided by the MM NF (e.g., 6G AMF) in step 9, the SDM NF (e.g., 6G UDM) can perform Nsdm_DeregistrationNotification on the old MM NF (e.g., 6G AMF) that manages the same RAT type as the new MM NF (TN). In this process, the MM NF (NTN) that manages a different RAT type is not affected.

[0328] 12. The MM NF (e.g., 6G AMF) can transmit a registration acceptance message to the terminal. Step 12 can be performed in the same manner as Step 3.

[0329] 13. An SDM NF (e.g., 6G UDM) can send a notification message (e.g., Nsdm_SDM_Notification) to an MM NF (NTN).

[0330] For example, the SDM NF (e.g., 6G UDM) may recognize that an MM NF managing the same RAT type has changed based on the RAT type information provided by the MM NF (e.g., 6G AMF) in step 10. The SDM NF (e.g., 6G UDM) may update the subscriber information of the terminal. Accordingly, based on the subscriber information change notification subscription requested by the MM NF (NTN) in step 5b, the terminal may notify the MM NF (NTN) that the information of the MM NF (e.g., 6G AMF) accessed through the TN has changed. For example, a notification message (e.g., Nsdm_SDM_Notification) may include information that the information of the MM NF (e.g., 6G AMF) accessed through the MM NF (NTN) TN has changed and / or information of the changed MM NF (TN).

[0331] 2. Second example of the present disclosure

[0332] A second example of the present disclosure describes an example of a method in which a terminal and / or network performs deregistration using RAT type information.

[0333] According to one embodiment, the terminal and / or network can perform deregistration for a specific RAT type while transmitting a deregistration request.

[0334] For example, while a terminal has registered through a TN base station and an NTN base station, the terminal may want to perform deregistration to the NTN base station. In this case, the terminal may perform deregistration to the NTN base station through the TN base station. For example, a deregistration request message transmitted by the terminal to the TN base station may include information related to a deregistration request for an NTN RAT type. The TN base station may transmit the deregistration request message to the MM NF (TN) connected via the TN base station.

[0335] In this case, the MM NF (TN) that receives the Deregistration request message may transmit information related to the deregistration of the NTN base station (e.g., information indicating that the deregistration is for the terminal's NTN base station (e.g., RAT type = 6G NTN Radio (GEO))) to the SDM NF (e.g., UDM). The SDM NF (e.g., 6G UDM) that receives the information related to the deregistration of the NTN base station may perform Nsdm_Deregistration to the MM NF (NTN) managing the RAT. The MM NF (NTN) that receives Nsdm_Deregistration (e.g., MM NF connected via the NTN base station (e.g., 6G AMF)) may perform deregistration for the terminal. In this case, the MM NF (NTN) may perform deregistration without direct signaling with the terminal.

[0336] In some implementations, a terminal may be registered through 3GPP access and non-3GPP access. For example, a terminal may be registered through multiple 3GPP accesses. In this case, when unregistration related to a 3GPP access is performed for the terminal, unregistration may be performed for all 3GPP accesses at once. In this case, the terminal (e.g., when the terminal performs / initiates the unregistration procedure) or the network (e.g., when the network performs / initiates the unregistration procedure) may include the RAT types of all registered 3GPP accesses in the unregistration request message. Alternatively, the terminal (e.g., when the terminal performs / initiates the unregistration procedure) or the network (e.g., when the network performs / initiates the unregistration procedure) may include "3GPP access" in the unregistration request message or express "3GPP access" so that unregistration may be performed for all RAT types of the 3GPP access to which the terminal was registered at once.

[0337] Referring to FIGS. 10a and 10b, an example is described in which deregistration is performed after a terminal is registered through a plurality of RAT types.

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

[0339] FIGS. 10a and FIGS. 10b are examples of a deregistration procedure according to one embodiment of the present disclosure.

[0340] FIGS. 10a and FIGS. 10b are examples of deregistration procedures performed when a terminal and / or network indicates (or transmits) a RAT type to perform deregistration for a specific RAT type.

[0341] 1. The terminal can transmit a registration request message to the MM NF (TN) via the RAN (TN).

[0342] For example, a terminal can perform registration through a TN base station (e.g., RAN(TN)). In this process, the terminal may transmit a registration request message including at least one of capability information indicating that it supports simultaneous registration through another RAT, information indicating that it wants simultaneous registration, and / or information on the type of RAT that supports it.

[0343] A TN base station (e.g., RAN(TN)) can select an MM NF (e.g., 6G AMF). The TN base station (e.g., RAN(TN)) can send a registration request message to the MM NF (e.g., 6G AMF).

[0344] 2. An MM NF (e.g., 6G AMF) can perform registration for an SDM NF. For example, an MM NF (e.g., 6G AMF) can send a message related to registration (e.g., a message related to Nsdm_Registration) to an SDM NF. An SDM NF can also send a message related to registration (e.g., a message related to Nsdm_Registration) to an MM NF (e.g., 6G AMF).

[0345] For example, in step 2a, the MM NF (e.g., 6G AMF) selected through the TN base station can perform registration for the SDM NF. In this process, the MM NF (e.g., 6G AMF) can transmit information to the SDM NF that the RAT type is TN.

[0346] For example, in step 2b, an MM NF (e.g., 6G AMF) may obtain subscriber information about a terminal from an SDM NF and / or enter into a subscription to receive notifications of changes to the terminal's subscriber information. In some implementations, during this process, the MM NF (e.g., 6G AMF) may also enter into a subscription to request information about the terminal's serving MM NF (e.g., 6G AMF) from an SDM NF (e.g., UDM). For example, in this case, for a terminal registered through one or more RATs, if any of the serving MM NFs (e.g., 6G AMF) associated with one or more RATs is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0347] In some implementations, an MM NF (e.g., 6G AMF) may request information about a serving MM NF (e.g., 6G AMF) that uses a specific RAT. For example, in this case, for a terminal registered through one or more RATs, if the serving MM NF (e.g., 6G AMF) associated with a specific RAT is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0348] 3. MM NF (e.g., 6G AMF) can send a registration acceptance message to the terminal.

[0349] For example, the MM NF (e.g., 6G AMF) may provide information to the terminal indicating that additional RAT registration is allowed. For example, the MM NF (e.g., 6G AMF) may transmit information indicating that additional RAT registration is allowed along with a registration acceptance message. The registration acceptance message may include information indicating that additional RAT registration is allowed.

[0350] 4. The terminal can transmit a registration request message to MM NF (LEO NTN) via RAN (LEO NTN).

[0351] For example, a terminal can perform registration through an NTN (LEO) base station (e.g., RAN (LEO NTN)). In this process, the terminal may transmit a registration request message including at least one of capability information indicating that it supports simultaneous registration through another RAT, information indicating that it wants simultaneous registration, and / or information on the type of RAT that supports it.

[0352] An NTN (LEO) base station (e.g., RAN (LEO NTN)) can select an MM NF (LEO NTN). An NTN (LEO) base station (e.g., RAN (LEO NTN)) can send a registration request message to the MM NF (LEO NTN).

[0353] 5. An MM NF (LEO NTN) can perform registration for an SDM NF. For example, an MM NF (LEO NTN) can send a message related to registration (e.g., a message related to Nsdm_Registration) to an SDM NF. An SDM NF can also send a message related to registration (e.g., a message related to Nsdm_Registration) to an MM NF (LEO NTN).

[0354] For example, in step 5a, the MM NF (LEO NTN) selected through the NTN (LEO) base station can perform registration for the SDM NF. In this process, the MM NF (LEO NTN) can transmit information that the RAT type is NTN (LEO) to the SDM NF.

[0355] For example, in step 5b, the MM NF (LEO NTN) may obtain subscriber information about the terminal from the SDM NF and / or perform a subscription to receive notifications of changes to the terminal's subscriber information. In some implementations, during this process, the MM NF (LEO NTN) may also perform a subscription to request information about the terminal's serving MM NF (e.g., 6G AMF) from the SDM NF (e.g., UDM). For example, in this case, for a terminal registered through one or more RATs, if any of the serving MM NFs (e.g., 6G AMF) associated with one or more RATs is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0356] In some implementations, an MM NF (e.g., 6G AMF) may request information about a serving MM NF (e.g., 6G AMF) that uses a specific RAT. For example, in this case, for a terminal registered through one or more RATs, if the serving MM NF (e.g., 6G AMF) associated with a specific RAT is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0357] Through this, the MM NF (LEO NTN) can receive subscriber information of the terminal from the SDM NF (e.g., UDM), including information (e.g., FQDN, address, etc.) about the MM NF (e.g., 6g AMF) that the terminal connected to through the TN.

[0358] 6. The MM NF (e.g., 6G AMF) can transmit a registration acceptance message to the terminal. Step 6 can be performed in the same manner as Step 3.

[0359] 7. The SDM NF (e.g., 6G UDM) can send a notification message (e.g., Nsdm_SDM_Notification message) to the MM NF (TN).

[0360] For example, an SDM NF (e.g., 6G UDM) may recognize in step 5a that the terminal is connected via an additional RAT. Based on the subscription for the subscriber information change notification requested by the MM NF (TN) in step 2b, the SDM NF (e.g., 6G UDM) may transmit information of the MM NF (LEO NTN) that the terminal connected to via the LEO NTN to the MM NF (TN). For example, a notification message (e.g., Nsdm_SDM_Notification message) may include information of the MM NF (LEO NTN) that the terminal connected to via the LEO NTN.

[0361] 8. The terminal can transmit a registration request message to MM NF (GEO NTN) via RAN (GEO NTN).

[0362] For example, a terminal can perform registration through an NTN (GEO) base station (e.g., RAN(GEO NTN)). In this process, the terminal may transmit a registration request message including at least one of capability information indicating that it supports simultaneous registration through another RAT, information indicating that it wants simultaneous registration, and / or information on the type of RAT that supports it.

[0363] An NTN (GEO) base station (e.g., RAN(GEO NTN)) can select an MM NF (GEO NTN). An NTN (GEO) base station (e.g., RAN(GEO NTN)) can send a registration request message to the MM NF (GEO NTN).

[0364] 9. An MM NF (GEO NTN) can perform registration for an SDM NF. For example, an MM NF (GEO NTN) can send a message related to registration (e.g., a message related to Nsdm_Registration) to an SDM NF. An SDM NF can also send a message related to registration (e.g., a message related to Nsdm_Registration) to an MM NF (GEO NTN).

[0365] For example, in step 9a, the MM NF (GEO NTN) selected through the NTN (GEO) base station can perform registration for the SDM NF. In this process, the MM NF (GEO NTN) can transmit information that the RAT type is NTN (GEO) to the SDM NF.

[0366] For example, in step 9b, the MM NF (GEO NTN) may obtain subscriber information about the terminal from the SDM NF and / or perform a subscription to receive notifications of changes to the terminal's subscriber information. In some implementations, during this process, the MM NF (GEO NTN) may also perform a subscription to request information about the terminal's serving MM NF (e.g., 6G AMF) from the SDM NF (e.g., UDM). For example, in this case, for a terminal registered through one or more RATs, if any of the serving MM NFs (e.g., 6G AMF) associated with one or more RATs is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0367] In some implementations, an MM NF (e.g., 6G AMF) may request information about a serving MM NF (e.g., 6G AMF) that uses a specific RAT. For example, in this case, for a terminal registered through one or more RATs, if the serving MM NF (e.g., 6G AMF) associated with a specific RAT is changed, the MM NF (e.g., 6G AMF) may receive a notification.

[0368] Through this, the MM NF (GEO NTN) can receive subscriber information of the terminal from the SDM NF (e.g., UDM), including information (e.g., FQDN, address, etc.) about the MM NF (e.g., 6g AMF) that the terminal connected to through the TN.

[0369] 10. The MM NF (e.g., 6G AMF) can transmit a registration acceptance message to the terminal. Step 10 can be performed in the same manner as Step 3.

[0370] 11. An SDM NF (e.g., 6G UDM) can send a notification message (e.g., Nsdm_SDM_Notification message) to an MM NF (TN) and / or an MM NF (LEO NTN).

[0371] For example, an SDM NF (e.g., 6G UDM) may recognize in step 9a that the terminal is connected via an additional RAT. Based on the subscription for a subscriber information change notification requested by the MM NF (TN) in step 2b and / or the subscription for a subscriber information change notification requested by the MM NF (LEO NTN) in step 5b, the SDM NF (e.g., 6G UDM) may transmit information of the MM NF (GEO NTN) that the terminal connected to via the GEO NTN to the MM NF (TN) and / or the MM NF (LEO NTN). For example, a notification message (e.g., Nsdm_SDM_Notification message) may include information of the MM NF (GEO NTN) that the terminal connected to via the GEO NTN.

[0372] 12. A terminal may want to perform deregistration for NTN (LEO) when it moves out of NTN (LEO) coverage. In this case, the terminal may decide to send a deregistration request message through a TN base station. The terminal may transmit a deregistration request message to a TN base station. For example, the terminal may transmit a deregistration request message to MM NF (TN) via a TN base station. The terminal may include RAT type information related to deregistration (e.g., information that RAT type = deregistration for NTN (LEO)) in the deregistration request message.

[0373] 13. An MM NF (e.g., 6G AMF) can perform Nsdm_Deregistration to an SDM NF (e.g., 6G UDM). An MM NF (TN) can send a deregistration message (e.g., Nsdm_Deregistration) containing information about the RAT type = NTN (LEO) requested by the terminal to the SDM NF (e.g., 6G UDM).

[0374] 14. MM NF (e.g., 6G AMF) can transmit a Deregistration accept message to the terminal. For example, the Deregistration accept message may include information related to the fact that deregistration for RAT type = NTN (LEO) has been performed.

[0375] 15. An SDM NF (e.g., 6G UDM) can send messages related to deregistration notifications (e.g., messages related to Nsdm_DeregistrationNotification) to an MM NF (LEO NTN).

[0376] For example, an SDM NF (e.g., 6G UDM) may send an Nsdm_DeregistrationNotification to an MM NF (LEO NTN) based on the information regarding the serving AMF for the RAT type = NTN (LEO) in step 13. Upon receiving this, the MM NF (LEO NTN) may delete the UE Context for the terminal and perform the deregistration process. During this process, signaling to the terminal may not be performed. In some implementations, step 15 may be performed before step 14 or simultaneously.

[0377] 16. The SDM NF can send notification messages (e.g., messages related to Nsdm_SDM_Notification) to the MM NF (TN) and / or the MM NF (GEO NTN).

[0378] For example, based on the subscription related to the notification of subscriber information change in step 2b and / or step 9b, the SDM NF may notify the MM NF (TN) and / or MM NF (GEO NTN) that the terminal has been deregistered from the LEO NTN. For example, the NF may transmit information related to the fact that the terminal has been deregistered from the LEO NTN to the MM NF (TN) and / or MM NF (GEO NTN). For example, the SDM NF may notify the MM NF (TN) and / or MM NF (GEO NTN) that the information of the terminal's LEO NTN's serving MM NF (e.g., 6G AMF) has been deleted.

[0379] 3. Third example of the present disclosure

[0380] The third example of the present disclosure describes an example in which a terminal performs periodic registration for multiple RAT types simultaneously, rather than performing periodic registration for each RAT type.

[0381] In one embodiment, the terminal can register with the network through multiple RATs. In this case, the terminal must perform a periodic registration update for each RAT.

[0382] However, if a terminal is communicating through one RAT (e.g., the first RAT), and the terminal performs a periodic registration update to another RAT (e.g., the second RAT), the following problem may occur.

[0383] For example, in such a case, if the terminal performs a periodic registration update with a different RAT (e.g., a second RAT) due to the terminal's radio capability, it may affect the quality of the service the terminal is using by utilizing a specific RAT.

[0384] For example, the terminal may be in an idle state for each RAT. In this case, if the terminal performs a periodic registration update for each RAT, the terminal frequently enters connected mode, which increases the problem of increased battery consumption.

[0385] To solve these problems, according to one embodiment, a terminal can perform a periodic registration update of another RAT through one RAT. For example, the terminal can perform a periodic registration update to an AMF registered through NTN via TN. To do this, while performing the periodic registration update through TN, the terminal can include temporary ID information (e.g., 6G GUTI) assigned by serving MM NFs (e.g., 6G AMFs) that require a periodic registration update in the registration request message.

[0386] For example, a terminal may have registered through two or more RATs. In this case, temporary ID information (e.g., 6G GUTI) may include all information assigned by each RAT through which the terminal has registered. Additionally, the terminal may send one or more Registration request messages mapped to each temporary ID information (e.g., 6G GUTI) to the MM NF (e.g., 6G AMF). In this case, each Registration request message may be integrity and / or confidentiality protected using the security context used by each RAT.

[0387] An MM NF (e.g., 6G AMF) that receives a registration request message can find the serving MM NF (e.g., 6G AMF) in each RAT based on each temporary ID information (e.g., 6G GUTI). An MM NF (e.g., 6G AMF) that receives a registration request message can forward the Registration request message sent by the terminal to the serving MM NF (e.g., 6G AMF) in each RAT.

[0388] The serving MM NF of each RAT that receives the registration request message can check security and perform periodic registration updates for the terminal. The serving MM NF of each RAT can send a Registration accept message to be sent to the terminal to the MM NF (e.g., 6G AMF) that received the terminal's Registration request. The MM NF (e.g., 6G AMF) can receive all responses from the serving MM NF (e.g., 6G AMF) in each RAT. Then, the MM NF (e.g., 6G AMF) can send the Registration accept message, the temporary ID information (e.g., 6G GUTI) from each RAT that the terminal sent, and the Registration accept message mapped to the temporary ID information (e.g., 6G GUTI) in each RAT together to the terminal. Through this, periodic registration updates in all RATs can be performed at once.

[0389] In some implementations, while a terminal performs a periodic registration update through a single RAT type, it may perform the following actions. For example, the terminal may perform other registration updates (e.g., Mobility Registration Update) in addition to the Periodic Registration Update. For example, the terminal may perform a mobility registration update without performing a periodic registration update for a different RAT type. For example, while the terminal transmits the Periodic Registration Update to the TN, it may also want to perform a Mobility Registration Update because the terminal has moved out of the NTN's Registration Area. In this case, the terminal may transmit the Mobility Registration Update to the NTN while transmitting the Periodic Registration Update to the TN.

[0390] In some implementations, the terminal may perform periodic registration updates for different RAT types through different messages. For example, a new message may be used instead of a Periodic Registration Update message. The terminal may transmit a Periodic Registration Update / Mobility Registration Update for a different RAT by sending a new message.

[0391] Referring to FIG. 11, an example of a method in which a terminal performs periodic registration updates for a plurality of RATs is described.

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

[0393] FIG. 11 is an example of performing periodic registration updates according to one embodiment of the present disclosure.

[0394] 1. A terminal can register with a network through a TN base station. During this process, an MM NF (e.g., 6G AMF) connected through the TN base station assigns a temporary ID (e.g., 5G-GUTI) to the terminal. For the actions performed in the registration procedure, FIGS. 9a and 9b, and / or FIGS. 10a and 10b may be referenced.

[0395] 2. A terminal can register with the network through an LEO NTN base station. During this process, an MM NF (LEO NTN) connected through the LEO NTN base station can assign a temporary ID (e.g., 5G-GUTI) to the terminal. Additionally, the MM NF (LEO NTN) can assign a periodic registration timer value to the terminal to perform periodic registration.

[0396] In some implementations, at step 2, the terminal may transmit a Registration request message containing the periodic registration timer value desired by the terminal to the MM NF (LEO NTN) via the LEO NTN base station. For example, in this case, the terminal may request the periodic registration timer value desired by the terminal from the MM NF (LEO NTN) by transmitting the periodic registration timer value desired by the terminal. By transmitting the periodic registration timer value desired by the terminal, the terminal may ensure that the periodic registration timer value assigned by the MM NF (LEO NTN) matches the periodic registration timer values ​​associated with other RATs. Subsequently, the terminal may enter an IDLE state at the LEO NTN.

[0397] In some implementations, regardless of whether the terminal requests the same periodic registration timer, the terminal may perform the following actions. For example, the periodic registration timer of a specific RAT may expire based on the smallest value among multiple periodic registration timer values ​​assigned by each RAT's MM NF (e.g., 6G AMF). In this case, the terminal may perform periodic registration with other RATs simultaneously, in addition to the specific RAT. For example, even if the periodic registration timers assigned by each RAT's MM NF (e.g., 6G AMF) are the same, the time for performing periodic registration updates and the time for becoming idle may differ for each RAT. In this case, the terminal may perform periodic registration with other RATs simultaneously at the time when the periodic registration timers expire first.

[0398] 3. A terminal can register with the network through a GEO NTN base station. During this process, the MM NF (GEO NTN) connected through the GEO NTN base station may assign a temporary ID (e.g., 5G-GUTI) to the terminal. Additionally, the MM NF (GEO NTN) may assign a periodic registration timer value to perform periodic registration. For example, in this case, the terminal may request the desired periodic registration timer value from the MM NF (GEO NTN) by transmitting the desired periodic registration timer value. By transmitting the desired periodic registration timer value, the terminal can ensure that the periodic registration timer value assigned by the MM NF (GEO NTN) matches the periodic registration timer values ​​associated with other RATs. Subsequently, the terminal may enter an IDLE state in the GEO NTN.

[0399] For reference, after the terminal enters the IDLE state, it starts a timer based on the periodic registration timer value. After the periodic registration timer value expires, the terminal can perform the periodic registration procedure.

[0400] In some implementations, the terminal may perform the following actions regardless of whether the terminal requests the same periodic registration timer. For example, the periodic registration timer of a specific RAT may expire based on the smallest value among multiple periodic registration timer values ​​assigned by each RAT's MM NF (e.g., 6G AMF). In this case, the terminal may perform periodic registration with other RATs simultaneously, in addition to the specific RAT. For example, even if the periodic registration timers assigned by each RAT's MM NF (e.g., 6G AMF) are the same, the time for performing periodic registration updates and the time for becoming idle may differ for each RAT. In this case, the terminal may perform periodic registration with other RATs simultaneously at the time when the periodic registration timers expire first.

[0401] 4. The terminal can send a NAS MM request message.

[0402] For example, the terminal may perform a periodic registration procedure. For example, in steps 1 through 3, the periodic registration timer value received by the terminal via TN, the periodic registration timer value received by the terminal via LEO NTN, and the periodic registration timer value received by the terminal via GEO NTN may be the same. In this case, at least one of the timer based on the periodic registration timer value received by the terminal via TN, the timer based on the periodic registration timer value received by the terminal via LEO NTN, and / or the timer based on the periodic registration timer value received by the terminal via GEO NTN may expire. In this case, the terminal may perform periodic registration.

[0403] As another example, for example, in steps 1 through 3, the periodic registration timer value received by the terminal via TN, the periodic registration timer value received by the terminal via LEO NTN, and the periodic registration timer value received by the terminal via GEO NTN may not be the same. In this case, when the timer based on the smallest value among the periodic registration timer value received via TN, the periodic registration timer value received by the terminal via LEO NTN, and the periodic registration timer value received by the terminal via GEO NTN expires, the terminal can perform periodic registration.

[0404] For example, if the periodic registration timer received via the terminal's LEO NTN and the periodic registration timer received via the GEO NTN have expired (or based on the said timers), the terminal must perform periodic registration.

[0405] In some implementations, when a terminal performs periodic registration, the following description may apply. Instead of performing periodic registration through each RAT, the terminal may perform periodic registration updates through a single RAT.

[0406] For example, in such a case, as shown in FIG. 11, an example is assumed in which a periodic registration update is performed through a TN base station. The terminal can transmit a NAS MM Request message to the TN base station. For example, the NAS MM Request message may be a Registration Request message or may contain a Registration Request message. At this time, since the periodic registration timer received through the terminal's LEO NTN and the periodic registration timer received through the GEO NTN have expired, the terminal can perform the following action. The terminal can transmit the NAS MM Request message by including both the registration request message to be transmitted through the LEO NTN and the registration request message to be transmitted through the GEO NTN in the NAS MM Request message. At this time, the terminal can transmit each Registration Request message in the format of a NAS message container. Since the MM NF (TN) connected through the TN base station does not directly process the NAS message container, the MM NF (TN) does not directly process the Registration Request that needs to be transmitted through another RAT. In addition, each Registration Request may be security protected using the security context of each RAT.

[0407] For example, the terminal can send a Registration Request message in the following format:

[0408] NAS MM Request (Registration type, 6G-GUTI#1, [6G-GUTI#2, NAS message container#2], [6G-GUTI#3, NAS message container#3])

[0409] For example, 6G-GUTI#1 may be a temporary ID assigned by an MM NF (NF) connected through a TN base station. 6G-GUTI#2 may be a temporary ID assigned by an MM NF (LEO NTN) connected through an LEO NTN base station. 6G-GUTI#3 may be a temporary ID assigned by an MM NF (GEO NTN) connected through a GEO NTN base station. NAS message container #2 may contain a Registration Request message to be forwarded to the MM NF (LEO NTN) that assigned 6G-GUTI#2. NAS message container #3 may contain a Registration Request message to be forwarded to the MM NF (GEO NTN) that assigned 6G-GUTI#3.

[0410] The terminal may send a Registration Request message for each RAT type instead of a temporary ID (e.g., 6G GUTI). For example, the terminal may include “RAT Type = LEO NTN” information instead of 6G-GUTI#2 and “RAT Type=GEO NTN” information instead of 6G-GUTI#3. In this case, the MM NF (e.g., 6G AMF) may find the MM NF (e.g., 6G AMF) for each RAT through the MM NF (e.g., 6G AMF) for other RATs received from the SDM NF (e.g., 6G UDM) during the registration process, and deliver the Registration Request message to the MM NF (e.g., 6G AMF) for each RAT.

[0411] 5. An MM NF (TN) connected through a TN base station can locate an MM NF (e.g., 6G AMF) connected through a RAT using temporary ID information (e.g., 6G GUTI) provided by the terminal. In step 5a, and / or step 5c, the MM NF (TN) can send a Registration Request message contained in a NAS message container to an MM NF (e.g., 6G AMF) connected through a RAT. An MM NF (e.g., MM NF (LEO NTN), MM NF (GEO NTN)) that receives a registration request message can check the security of the Registration Request. The MM NF (LEO NTN) and MM NF (GEO NTN) can each generate a Registration Accept message to be sent to the terminal. In step 5b, and / or step 5d, MM NF (LEO NTN) and MM NF (GEO NTN) can transmit a Registration Accept message to the connected MM NF (TN) via TN.

[0412] In some implementations, during this process, MM NFs connected through other RATs (e.g., MM NF (LEO NTN), and / or MM NF (GEO NTN)) may assign a new temporary ID (e.g., 6G GUTI). For example, an MM NF (LEO NTN) that assigned 6G-GUTI#2 may assign 6G-GUTI#2' as a new temporary ID (e.g., 6G-GUTI).

[0413] 6. MM NF (TN) can send a NAS MM acceptance message to the terminal.

[0414] For example, an MM NF (TN) connected via a TN may receive responses from all of one or more MM NFs (e.g., 6G AMF) that manage each of one or more temporary IDs (e.g., 6G GUTI) provided by the terminal. In this case, the MM NF (TN) may send a NAS MM Accept message to the terminal that includes the Registration Accept message received from one or more MM NFs (e.g., 6G AMF). For example, the MM NF (TN) may include the Registration Accept message received from one or more MM NFs (e.g., 6G AMF) in the NAS MM Accept message in a container format.

[0415] The NAS MM Accept message of step 6 may be a Registration Accept message. The MM NF (TN) may transmit each NAS message container to the terminal in a format mapped to a temporary ID (e.g., 6G GUTI), as in step 4. In this case, based on the NAS message container and the temporary ID (e.g., 6G GUTI), the terminal can determine which RAT's MM NF (e.g., 6G AMF) the NAS message contained in the NAS message container is from.

[0416] For example, MM NF (TN) can send a Registration Accept message in the following format:

[0417] NAS MM Accept (6G-GUTI#1', [6G-GUTI#2', NAS message container#2], [6G-GUTI#3', NAS message container#3])

[0418] 7. In some implementations, the terminal can send a NAS MM complete message to the MM NF (TN).

[0419] For example, at step 6, the terminal can identify a NAS MM Accept message (e.g., a registration acceptance message) contained in a NAS message container included in a NAS MM Accept message received from an MM NF (NF) (e.g., a NAS MM Accept message received from an MM NF connected through another RAT (e.g., MM NF (LEO NTN), and / or MM NF (GEO NTN)).

[0420] In some implementations, the NAS MM acceptance message of step 6 may include a newly assigned temporary ID (e.g., 6G GUTI). In this case, the terminal may send a Registration Complete message to confirm the temporary ID (e.g., 6G GUTI). Similar to step 4, the Registration Complete message may be included within the NAS MM Complete message in the form of a NAS message container. For example, the NAS MM Complete message may include a NAS message container and information on temporary IDs (e.g., 6G GUTI) mapped to each NAS message container. For example, the NAS MM Complete message may be a Registration Complete message.

[0421] 8. An MM NF (TN) connected through a TN base station may locate one or more MM NFs (e.g., 6G AMF) connected through other RATs based on temporary ID (e.g., 6G GUTI) information provided by the terminal. In step 8a, and / or step 8c, the MM NF (TN) may send a Registration Complete message contained in each NAS message container to one or more MM NFs (e.g., 6G AMF). In step 8b, and / or step 8d, one or more MM NFs (e.g., 6G AMF) may also send a response message (e.g., Nmmnf_Communication_RegistrationStatusUpdate response message) to the MM NF (TN).

[0422] 4. Fourth example of the present disclosure

[0423] In the fourth example of the present disclosure, an example of session handover between RAT types via NAS MM messages is described.

[0424] In one embodiment, an example of a method for a terminal to move a PDU session created (or established) through a specific RAT to another RAT is described.

[0425] According to the prior art, in order for a terminal to hand over a PDU session between 3GPP access and non-3GPP access, the terminal performs a PDU session establishment procedure. For example, the terminal can perform a PDU session establishment procedure to hand over the PDU session to a different access type.

[0426] Although a method using the PDU session establishment procedure, as in conventional technology, could be considered for a terminal to hand over a PDU session to another RAT, there is a problem that the terminal transmitting and receiving NAS SM messages is inefficient. For example, when the PDU session establishment procedure is performed, there is a problem that more signaling occurs between the terminal and the network, and / or between different network entities.

[0427] To address these issues, in one embodiment, an example of a method for handing over PDU sessions between RAT types using terminal and / or NAS MM messages is described. For reference, the examples described in the fourth example of this disclosure may also be used to hand over PDU sessions between 3GPP access and non-3GPP access.

[0428] In one embodiment, after establishing a PDU session, the terminal may want to hand over the PDU session from the RAT where the PDU session was created to another RAT. In this case, the terminal may request user plane activation for the PDU session to be handed over by sending a NAS MM message to an MM NF (e.g., 6G AMF). Upon receiving this, the MM NF (e.g., 6G AMF) may perform user plane activation through the RAT sent by the terminal and update the RAT type information for the PDU session. If the user plane activation is successfully performed, the MM NF (e.g., 6G AMF) may update the RAT type information for the PDU session.

[0429] Referring to the examples in FIGS. 12a and 12b, an example of handing over a PDU session established by a terminal through a TN base station to an NTN base station is described.

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

[0431] FIGS. 12a to 12c are examples of a procedure for handing over a PDU session according to one embodiment of the present disclosure.

[0432] FIGS. 12a to 12c are examples of inter-RAT PDU session handover using NAS MM messages.

[0433] 1~7. Steps 1 to 7 of FIG. 9 can be performed in the same manner.

[0434] 8. The terminal can send a PDU session establishment request message to the MM NF (TN) via the RAT (TN).

[0435] For example, a terminal may send a PDU Session Establishment Request message to create a PDU session through a TN RAT. At this time, information such as the PDU Session ID, DNN, and S-NSSAI of the PDU session that the terminal wishes to create may be transmitted together. Upon receiving this, an MM NF (e.g., 6G AMF) may store information related to the terminal's PDU session (e.g., PDU Session ID, DNN, S-NSSAI, SM NF (e.g., 6G SMF) information, etc.) and store the RAT type as TN.

[0436] 9. The TN MM NF (e.g., 6G AMF) can send a request message related to the Session Management (SM) context (e.g., Nsm_PDU Session_CreateSMContext Request) to the SM NF.

[0437] For example, the TN MM NF (e.g., 6G AMF) can transmit a PDU Session Establishment Request message sent by the terminal to the SM NF (e.g., 6G SMF). In this process, the terminal's location information, RAT type information, etc. are transmitted together to the SM NF (e.g., 6G SMF).

[0438] 10. SM NF (e.g., 6G SMF) can obtain subscriber information related to the terminal's session from SDM NF (e.g., 6G UDM). Additionally, SM NF (e.g., 6G SMF) can also perform a subscription to SDM NF (e.g., 6G UDM) to receive notifications regarding changes in the terminal's subscriber information.

[0439] 11. The SM NF (e.g., 6G SMF) can send a request message related to the SM context (e.g., Nsm_PDU Session_CreateSMContext Response) to the TN MM NF (e.g., 6G AMF).

[0440] For example, the SM NF (e.g., 6G SMF) can send a response message for step 9 to the MM NF (e.g., 6G AMF).

[0441] In some implementations, a PM NF (e.g., 6G PCF) may exist. In this case, an SM NF (e.g., 6G SMF) may establish an association with the PM NF (e.g., 6G PCF) and obtain a Policy and Charging Control (PCC) rule for the session from the PM NF (e.g., 6G PCF). During this process, the SM NF (e.g., 6G SMF) may transmit RAT type information, etc., to the PM NF (e.g., 6G PCF), and the PM NF (e.g., 6G PCF) may generate a PCC rule based on the RAT type.

[0442] 12. The SM NF (e.g., 6G SMF) may perform Nup_Session_Establishment to the UP NF (e.g., 6G UPF) to create user plane resources for the PDU session. In this process, the UP NF (e.g., 6G UPF) may transmit information such as the IP address to be assigned to the terminal and / or uplink tunnel information to the SM NF (e.g., 6G SMF).

[0443] 13. SM NF (e.g., 6G SMF) can send Nmm_Communication_N1N2MessageTransfer to MM NF (e.g., 6G AMF).

[0444] For example, an SM NF (e.g., 6G SMF) may transmit an Nmm_Communication_N1N2MessageTransfer message to an MM NF (e.g., 6G AMF) to transmit a PDU Session Establishment Accept message that allows the terminal to create a PDU session and a message to request a PDU Session Resource from a base station. For example, the Nmm_Communication_N1N2MessageTransfer message may include a PDU Session Establishment Accept message and a message to request a PDU Session Resource from a base station.

[0445] 14. The MM NF (e.g., 6G AMF) can send an N2 PDU session request message (including NAS information) to the RAN (TN).

[0446] For example, an MM NF (e.g., 6G AMF) can transmit information transmitted by an SM NF (e.g., 6G SMF) to a base station (e.g., a PDU Session Establishment Accept message and / or a message to request a PDU Session Resource from the base station). For example, NAS information may include a PDU Session Establishment Accept message.

[0447] 15. The base station can create resources for a PDU session requested by an SM NF (e.g., 6G SMF). The base station can allocate radio resources to the terminal via AN specific signaling (e.g., RRC message). In addition, during this process, the base station can send a PDU Session Establishment Accept message to the terminal.

[0448] 16. The base station can transmit the N2 PDU session response to the MM NF (TN).

[0449] For example, while transmitting a response to step 14, the base station may transmit downlink tunnel information and / or successfully allocated resource information (e.g., QoS flow information) to the MM NF (e.g., 6G AMF) to be sent to the SM NF (e.g., 6G SMF). For example, the N2 PDU session response may include downlink tunnel information and / or successfully allocated resource information (e.g., QoS flow information) to be sent to the SM NF (e.g., 6G SMF).

[0450] 17. An MM NF (e.g., 6G AMF) can send a request message related to the SM context (e.g., Nsm_PDUSession_UpdateSMContext Request) to an SM NF (e.g., 6G SMF).

[0451] For example, an MM NF (e.g., 6G AMF) may send an Nsm_PDUSession_UpdateSMContext Request to transmit information transmitted by the base station to an SM NF (e.g., 6G SMF). For example, a message related to the SM context (e.g., Nsm_PDUSession_UpdateSMContext Request) may include downlink tunnel information and / or information on successfully allocated resources (e.g., QoS flow information).

[0452] 18. SM NF (e.g., 6G SMF) can perform Nup_Session_Modification on UP NF to update down tunnel information transmitted by the base station.

[0453] 19. An SM NF (e.g., 6G SMF) may send a response message related to the SM context (e.g., Nsm_PDUSession_UpdateSMContext Response) to an MM NF (TN). For example, an SM NF (e.g., 6G SMF) may send a response message for step 17 (e.g., Nsm_PDUSession_UpdateSMContext Response) to an MM NF (TN).

[0454] 20. An SM NF (e.g., 6G SMF) can perform Nsdm_UECM_Registration to an SDM NF (e.g., 6G UDM) to store information about a PDU session (e.g., SM NF (e.g., 6G SMF) information, RAT type information, DNN, S-NSSAI information, etc.) in the terminal's subscriber information.

[0455] 21. Based on a subscription for subscriber information change notifications according to Step 2b and / or Step 5b, an SDM NF (e.g., 6G UDM) may transmit information updated in Step 20 (e.g., information about the PDU session of Step 20) to a TN MM NF (e.g., 6G AMF) (Step 21b) and / or an NTN MM NF (e.g., 6G AMF) (Step 21a).

[0456] 22. The terminal can send a service request message to the MM NF (NTN).

[0457] For example, a terminal may attempt to hand over a PDU session established through a TN RAT to an NTN RAT. For example, the terminal may attempt a handover for various reasons, such as the terminal moving out of TN coverage or the signal from the NTN RAT improving. To this end, the terminal may transmit a Service Request message through the RAT (e.g., the NTN RAT of FIG. 12a to 12c) over which the terminal wishes to hand over the PDU session. The Service Request message may include information regarding the PDU session over which the terminal wishes to hand over to the NTN RAT (e.g., PDU Session ID). This information may not be information indicating that the terminal wishes to hand over, but rather information indicating that it is requesting user plane activation. For example, the Service Request message may include information indicating a request for user plane activation and information regarding the PDU session (e.g., PDU Session ID).

[0458] 23. An NTN MM NF (e.g., 6G AMF) can send a request message related to the SM context (e.g., Nsm_PDUSession_CreateSMContext Request) to an SM NF.

[0459] For example, the NTN MM NF (e.g., 6G AMF) may send an Nsm_PDUSession_CreateSMContext Request containing information requesting user plane activation to the SMF managing the PDU session over which the terminal wants to hand over, based on the information about the PDU session received in step 21a.

[0460] 24. Based on Nup_Session_Modification, SM NF (e.g., 6G SMF) can obtain uplink tunnel information to use from UP NF (e.g., 6G UPF) via NTN RAT.

[0461] For example, an SM NF (e.g., 6G SMF) that receives a request message related to the SM context (e.g., Nsm_PDUSession_CreateSMContext Request) can perform Nup_Session_Modification with a UP NF (e.g., 6G UPF). Through this, the SM NF (e.g., 6G SMF) can obtain uplink tunnel information to use from the NF (e.g., 6G UPF) via NTN RAT. For example, the SM NF (e.g., 6G SMF) can send a message related to Nup_Session_Modification to the UP NF (e.g., 6G UPF). The UP NF (e.g., 6G UPF) can send a message related to Nup_Session_Modification containing uplink tunnel information to use to the SM NF (e.g., 6G SMF) via NTN RAT.

[0462] In some implementations, step 24 may be omitted. For example, the uplink tunnel information used through the SM NF (e.g., 6G SMF) TN RAT (e.g., the uplink tunnel information from step 12) may be used as is.

[0463] 25. The SM NF (e.g., 6G SMF) can send a response message related to the SM context (e.g., Nsm_PDUSession_CreateSMContext Response) to the MM NF (NTN).

[0464] For example, to transmit uplink tunnel information and base station resources to the base station, the SM NF (e.g., 6G SMF) transmits an Nsm_PDUSession_CreateSMContext Response to the MM NF (NTN) containing a message (e.g., N2 PDU Session Resource Setup Request) to request a PDU Session Resource from the base station.

[0465] 26. MM NF (e.g., 6G AMF) can transmit a message (e.g., N2 PDU Session Resource Setup Request) transmitted by SM NF (e.g., 6G SMF) to the base station.

[0466] 27. The base station can perform operations related to AN-specific resource setup with the terminal.

[0467] For example, a base station can create a resource for a PDU session requested by an SM NF (e.g., 6G SMF) and allocate a wireless resource to a terminal through AN specific signaling (e.g., RRC message).

[0468] 28. The base station can send an N2 PDU session response message to the MM NF (NTN).

[0469] For example, while transmitting a response to step 26 (e.g., N2 PDU session response message), the base station may transmit downlink tunnel information to be sent to the SM NF (e.g., 6G SMF) and information on successfully allocated resources (e.g., QoS flow information) to the MM NF (e.g., 6G AMF).

[0470] 29. An MM NF (e.g., 6G AMF) can send an Nsm_PDUSession_UpdateSMContext Request to an SM NF (e.g., 6G SMF) to transmit information transmitted by the base station to the SM NF.

[0471] 29a. SM NF (e.g., 6G SMF) can perform Nup_Session_Modification to update down tunnel information transmitted by the base station.

[0472] 30. SM NF (e.g., 6G SMF) can send an Nsm_PDU_Session_UpdateSMContext Response in response to step 29.

[0473] 31. An SM NF (e.g., 6G SMF) can perform Nsdm_UECM_Registration on an SDM NF (e.g., 6G UDM) to store information about a PDU session (e.g., SM NF (e.g., 6G SMF) information, RAT type information, DNN, S-NSSAI information, etc.) in the terminal's subscriber information. Through this, the RAT type information of the PDU Session can be changed from TN to NTN.

[0474] 32. MM NF (e.g., 6G AMF) can send a service acceptance message to the terminal.

[0475] For example, the MM NF (e.g., 6G AMF) may send a Service Accept message to the terminal in response to step 22. The Service Accept message may contain information about the PDU session where a handover was successfully performed (or user plane activation was successfully performed). For example, the Service Accept message may include information related to the successful handover (or successful user plane activation) and information about the PDU session (e.g., PDU session ID).

[0476] 33. An SDM NF (e.g., 6G UDM) can send a notification message (e.g., Nsdm_SDM_Notification) to an MM NF (NTN) and / or an MM NF (TN).

[0477] For example, based on the subscription for subscriber information change notifications of Step 2b and / or Step 5b, the SDM NF (e.g., 6G UDM) may transmit the updated information (e.g., information related to the change of RAT type from TN to NTN) through Step 31 to the TN MM NF (e.g., 6G AMF) and / or NTN MM NF (e.g., 6G AMF).

[0478] 34. Based on step 33, the TN MM NF (e.g., 6G AMF) may recognize that the RAT type for the PDU session has changed. If user plane resources for the PDU session remain, the TN MM NF (e.g., 6G AMF) may request the base station to release the user plane resources for the PDU session. For example, in step 34a, the TN MM NF (e.g., 6G AMF) may send a PDU session release request message to the base station. In some implementations, as in step 34a, the MM NF (e.g., 6G AMF) may directly send a PDU session release request message to the base station. In this case, the base station may send an N2 PDU session release response to the MM NF (e.g., 6G AMF).

[0479] As another example, the MM NF (e.g., 6G AMF) may request the SM NF (6G SMF) to release the PDU session through Nsm_PDUSession_UpdateSMContext. As yet another example, after step 30, the SM FN (e.g., 6G SMF) may notify the previous TN MM FN (e.g., 6G AMF) to release the session's resources by performing an action related to Nsm_PDUSession_SMContextStatusNotify (e.g., sending a notification message related to the SM context).

[0480] For reference, in Examples 1 through 4 of the present disclosure, examples in which different RAT types are served by different MM NFs (e.g., 6G AMF) have been illustrated and described, but this is merely an example and the scope of the present disclosure is not limited thereto. For example, Examples 1 through 4 of the present disclosure may also be applied to scenarios in which different RAT types are served by the same MM NF (e.g., 6G AMF).

[0481] In some implementations, based on the RAT type in which the terminal performs the registration procedure, an MM NF (e.g., 6G AMF) can store and manage the terminal's context.

[0482] In some implementations, the terminal and / or MM NF (e.g., 6G AMF) can manage and store MM status by RAT type.

[0483] In some implementations, a terminal can perform periodic registration updates of another RAT through one RAT.

[0484] In some implementations, the terminal can perform an inter-RAT handover for a PDU session based on a NAS MM message.

[0485] In some implementations, at least one of the operations described in Examples 1 through 4 of the present disclosure may be performed.

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

[0487] FIG. 13 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0488] For reference, the procedure illustrated in FIG. 13 is merely an example, and the scope of disclosure of this specification is not limited by the example of FIG. 13.

[0489] For example, regarding the example of FIG. 13, the operations described in the examples of FIG. 1 to 12c may also be applied. For example, even if the operations, contents, etc. are not directly described in the example of FIG. 13, the operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0490] For example, in the example of FIG. 13, the first network entity may be a network entity related to mobility. For example, the first network entity may be an MM NF of various examples of the present disclosure. For example, the first network entity may be a network entity related to the first wireless access technology. For example, the first network entity may be a network entity related to a base station related to the first wireless access technology.

[0491] For example, in the example of FIG. 13, the second network entity may be a network entity related to mobility. For example, the second network entity may be an MM NF of various examples of the present disclosure. For example, the second network entity may be a network entity related to the second wireless access technology. For example, the second network entity may be a network entity related to a base station related to the second wireless access technology.

[0492] In the example of FIG. 13, the first network entity and the second network entity are depicted as separate objects, but this is merely an example and the scope of the disclosure is not limited thereto. For example, the first network entity and the second network entity may be the same. In this case, the first network entity (or the second network entity) may be a network entity related to both the first wireless access technology and the second wireless access technology.

[0493] In step (S1301), the UE can send a registration request message to the first network entity.

[0494] For example, a UE may transmit a first registration request message to a first network entity related to mobility, based on a first wireless access technology. For example, the UE may transmit the first registration request message to a base station related to the first wireless access technology, and this base station may deliver the first registration request message to the first network entity.

[0495] In some implementations, the registration request message may include at least one of information related to simultaneous registration based on multiple wireless access technologies, or information related to the type of wireless access technology supported by the terminal.

[0496] In step (S1302), the first network entity can send a registration acceptance message to the UE.

[0497] In some implementations, the first registration acceptance message may include at least one of information related to allowing simultaneous registration based on multiple wireless access technologies or information related to the types of wireless access technologies that the UE can simultaneously register.

[0498] In some implementations, the UE may transmit a session establishment request message to a third network entity involved in session management based on the first wireless access technology. For example, the UE may transmit a session establishment request message to a base station involved in the first wireless access technology. The base station may transmit a session establishment request message to the first network entity. The first network entity may transmit a session establishment request message to the third network entity.

[0499] For example, a session establishment request message may include information related to the session. The UE may receive a session establishment acceptance message from the third network entity based on the first wireless access technology.

[0500] In step (S1303), the UE can send a service request message to a second network entity.

[0501] For example, the service request message may include at least one of information regarding a session related to a handover from the first wireless access technology to the second wireless access technology, or information related to the user plane of the session being activated.

[0502] For example, the UE may transmit a service request message to a second network entity related to mobility, based on a second wireless access technology. For example, the UE may transmit the service request message to a base station related to the second wireless access technology. This base station may deliver the service request message to the second network entity.

[0503] In some implementations, the UE may receive a service acceptance message from the second network entity. For example, the service acceptance message may include information related to the session where the handover was successfully performed.

[0504] In some implementations, after the service request message is transmitted, the UE may further include the step of receiving a message related to resource setup from a base station related to the second wireless access technology.

[0505] In some implementations, the UE may recognize that the handover has been successfully performed based on a message related to the resource setup. For example, the UE may know that the handover has been successfully performed when it receives a message related to the resource setup.

[0506] In some implementations, the UE may send a second registration request message related to periodic registration to the second network entity. For example, the second registration request message may further include a first message container comprising a first temporary Identity (ID) related to the second network entity, a second temporary ID related to the first network entity, and a third registration request message related to the first network entity.

[0507] In some implementations, the UE may receive a second registration acceptance message from the second network entity. For example, the second registration acceptance message may further include a second message container comprising a third temporary ID associated with the second network entity, a fourth temporary ID associated with the first network entity, and a third registration acceptance message associated with the first network entity. For example, the third temporary ID and the first temporary ID may be the same. As another example, the second network entity may assign a new third temporary ID.

[0508] For example, a second network entity may transmit a first request message containing information related to requesting user plane activation of said session to a third network entity involved in session management.

[0509] For example, a second network entity may receive a first response message from the third network entity, which includes a second request message for requesting session resources from a base station based on the second wireless access technology.

[0510] For example, a second network entity can transmit the second request message to a base station based on the second wireless access technology.

[0511] In some implementations, the second network entity may receive a second response message from a base station based on the second wireless access technology in response to the second request message. For example, the second response message may include information related to a downlink tunnel and information related to allocated resources.

[0512] In some implementations, the second network entity may transmit a third request message to the third network entity, the message including information related to the downlink tunnel and information related to the allocated resource.

[0513] This specification may have various effects.

[0514] For example, it can be effectively supported for a terminal to register simultaneously through multiple wireless access technologies. For example, the terminal and / or network can manage the registration of the terminal by wireless access technology type. Accordingly, it may be permitted for the terminal to register simultaneously based on multiple wireless access technology types. The terminal can effectively receive services through multiple wireless access technologies.

[0515] For example, network entities related to mobility, such as terminals and / or networks, can effectively store and manage the terminal's context based on the wireless access technology type.

[0516] For example, terminals and / or networks can effectively manage or / or store states related to mobility management by wireless access technology type.

[0517] For example, a terminal and / or network can effectively perform periodic registration updates for multiple wireless access technology types. For example, a terminal can effectively perform periodic registration updates for multiple wireless access technology types through a single wireless access type.

[0518] For example, according to one embodiment, sessions (e.g., PDU sessions) can be effectively managed and / or controlled among a plurality of wireless access technologies.

[0519] For example, the terminal and / or network can use NAS MM messages to effectively support handover between wireless access technologies for a session (e.g., PDU session). By performing handover based on NAS MM messages, signaling between the terminal and the network and / or signaling between network entities can be effectively performed.

[0520] For example, a terminal and / or network may manage the registration of the terminal by RAT type. Accordingly, a terminal may be allowed to register with multiple RAT types simultaneously. The terminal may receive services through multiple RATs simultaneously.

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

[0522] For reference, the operation of the terminal (e.g., UE, etc.) described in this specification may be implemented by the device of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206) and execute the instruction / program stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0523] Additionally, instructions for performing the operation of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of the terminal described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0524] For reference, the operation of a network node (e.g., MM NF, MM NF (TN), MM NF (NTN), MM NF (LEO NTN), MM NF (GEO NTN), SDM NF, SM NF, UP NF, AMF, SMF, UPF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, RAN (TN), RAN (NTN), RAN (GEO NTN), RAN (LEO NTN), etc.) described in this specification may be implemented by the device of FIGS. 1 to 3, which will be described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206) and execute the instruction / program stored in one or more memories (104 or 204) to perform the operation of the network node or base station described in the disclosure of this specification.

[0525] Additionally, instructions for performing the operation of a network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transient) computer-readable storage medium. The storage medium may be contained in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of a network node or base station described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0526] Although preferred embodiments have been described by way of example above, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0527] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

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

Claims

1. In the method performed by the User Equipment (UE), The step of the above UE transmitting a first registration request message to a first network entity related to mobility, based on a first wireless access technology; The step of the UE receiving a first registration acceptance message from the first network entity; and The above UE includes the step of transmitting a service request message to a second network entity related to mobility, based on a second wireless access technology, and A method in which the above service request message includes information about a session related to a handover from the first wireless access technology to the second wireless access technology.

2. In Paragraph 1, A method wherein the first registration request message comprises at least one of information related to requesting simultaneous registration based on a plurality of wireless access technologies, or information related to the type of wireless access technology supported by the terminal.

3. In Paragraph 1 or 2, A method wherein the first registration acceptance message comprises at least one of information related to allowing simultaneous registration based on a plurality of wireless access technologies, or information related to the type of wireless access technology that the UE can simultaneously register.

4. In any one of paragraphs 1 through 3, The step of the above UE transmitting a session establishment request message to a third network entity involved in session management, based on the first wireless access technology, The above session establishment request message includes information about the above session; and A method further comprising the step of the UE receiving a session establishment acceptance message from the third network entity based on the first wireless access technology.

5. In any one of paragraphs 1 through 4, The above UE further includes the step of receiving a service acceptance message from the second network entity, and A method in which the above service acceptance message includes information about the session in which the above handover was successfully performed.

6. In any one of paragraphs 1 through 5, A method comprising the step of the UE receiving a message related to resource setup from a base station related to the second wireless access technology after the service request message is transmitted.

7. In Paragraph 6, A method in which the UE recognizes that the handover has been successfully performed based on a message related to the resource setup.

8. In any one of paragraphs 1 through 7, The above UE further includes the step of transmitting a second registration request message related to periodic registration to the second network entity, and A method comprising a first message container including a first temporary Identity (ID) associated with the second network entity, a second temporary ID associated with the first network entity, and a third registration request message associated with the first network entity.

9. In any one of paragraphs 1 through 8, The above UE further includes the step of receiving a second registration acceptance message from the second network entity, and A method comprising a second message container including a third temporary ID associated with the second network entity, a fourth temporary ID associated with the first network entity, and a third registration acceptance message associated with the first network entity.

10. In the device, At least one transmitter / receiver; At least one processor; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is: a device adapted to perform a method according to any one of claims 1 to 9.

11. At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and An operation performed based on the execution of the above instruction by the at least one processor is: an apparatus comprising a method according to any one of claims 1 to 9.

12. As a non-transitory computer-readable medium (CRM) recording instructions, The above instructions, when executed by one or more processors, cause the one or more processors to: perform a method according to any one of claims 1 through 9, CRM.

13. A second network entity related to mobility receiving a service request message from User Equipment (UE) based on a second wireless access technology, The above service request message includes information about a session related to a handover from the first wireless access technology to the second wireless access technology; The step of the second network entity transmitting a first request message containing information related to requesting user plane activation of the session to a third network entity related to session management; The step of the second network entity receiving a first response message from the third network entity, the first response message including a second request message for requesting a session resource from a base station based on the second wireless access technology; and A method comprising the step of the second network entity transmitting the second request message to the base station.

14. In Paragraph 13, The step of the second network entity receiving a second response message from the base station in response to the second request message, A method in which the second response message above includes information related to a downlink tunnel and information related to allocated resources.

15. In Paragraph 14, A method further comprising the step of the second network entity transmitting to the third network entity a third request message containing information related to the downlink tunnel and information related to the allocated resource.

16. In any one of paragraphs 13 through 15, The method further includes the step of the second network entity transmitting a service acceptance message to the UE, A method in which the above service acceptance message includes information about the session in which the above handover was successfully performed.

17. In a device, the device is: One or more transmitters / receivers; One or more processors; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is: a device adapted to perform the method according to any one of claims 13 to 16.

Images