Method for supporting hybrid access mode in 5g femto

Abstract

Provided are a method and a device related to hybrid access mode support in a 5G femto. An access mobility management node performs a step of receiving access mode information of a cell, which user equipment (UE) accesses, from a base station. The access mobility management node performs a step of determining type information of the UE on the basis of the access mode information of the cell, closed access group (CAG) information of the UE, and support capability of the UE. The access mobility management node performs a step of determining whether to perform CAG access control on the basis of at least one of the type information of the UE or the CAG information of the UE. The access mobility management node performs a step of transmitting the access mode information of the cell and the type information of the UE to a session management node. The access mobility management node performs a step of acquiring, from the session management node, information related to a quality of service (QoS) configured on the basis of the type information of the UE and the access mode information of the cell.

Description

How to support HYBRID ACCESS mode in 5G femtoseconds

[0001] This specification relates to the support of hybrid access mode in 5G femto.

[0002] 3GPP (3rd Generation Partnership Project) New Radio (NR) targets a single technical framework that addresses all deployment, use, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mmTC), and Ultra-Reliable and Low Latency Communications (URLLC). Additionally, NR must be able to utilize any spectrum band up to at least 100 GHz that can be used for wireless communication in the distant future. NR must be inherently forward compatible.

[0003] 6G is the successor to 5G cellular technology. 6G networks can utilize higher frequencies than 5G networks and will provide significantly higher capacity and much lower latency. The 6G technology market is expected to drive massive improvements in imaging, presence technology, and location awareness. Working in conjunction with Artificial Intelligence (AI), 6G computing infrastructure will be able to identify the best places for computing to occur. This includes decisions regarding data storage, processing, and sharing.

[0004] In one embodiment, a method related to supporting a hybrid access mode in a 5G femto is provided. The method includes the step of receiving access mode information of a cell to which a User Equipment (UE) connects from a base station by an access mobility management node. The method includes the step of determining type information of a UE based on the access mode information of the cell, the Closed Access Group (CAG) information of the UE, and the capability of the UE by the access mobility management node.

[0005] This method includes a step of determining whether to perform CAG connection control based on at least one of UE type information and UE's CAG information by an access mobility management node. This method includes a step of transmitting cell access mode information and UE type information by an access mobility management node to a session management node. This method includes a step of obtaining information related to Quality of Service (QoS) set based on the UE type information and cell access mode information from the session management node by an access mobility management node.

[0006] In another aspect, an apparatus for implementing the above method is provided.

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

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

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

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

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

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

[0013] FIG. 9 shows an example of the overall architecture of NG-RAN to which the implementation of the present specification is applied.

[0014] FIG. 10 shows an example of the logical structure of Femto to which the implementation of the present specification applies.

[0015] FIG. 11 illustrates an example of a method to which the implementation of the present specification is applied.

[0016] FIG. 12 illustrates an example of another method to which the implementation of the present specification is applied.

[0017] FIGS. 13a and FIGS. 13b illustrate examples of registration procedures for determining the type of a UE and controlling the connection to which the implementation of the present specification applies.

[0018] FIG. 14 shows an example of instructions for a hybrid access mode during a PDU session setup procedure to which the implementation of the present specification applies.

[0019] FIG. 15 illustrates an example of an NG-based handover procedure based on instructions for a hybrid access mode to which the implementation of the present specification applies.

[0020] FIG. 16 shows an example in which an indicator for a hybrid access mode is applied during an NG-based handover procedure to which the implementation of the present specification is applied.

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

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

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

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

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

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

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

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

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

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

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

[0032] The present specification will describe embodiments based on the structure, procedures, messages, etc. of a 5G mobile communication system. However, this is merely an example, and the embodiments of the present specification are not limited thereto. For example, the embodiments of the present specification can be extended to an evolved form of a 6G mobile communication system. For example, the 5G-based messages described in the embodiments of the present specification may be defined as other existing messages, new messages, or parameters.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be placed outside the processing chip (201).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0080] - AUSF (Authentication Server Function)

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

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

[0083] - USDF (Unstructured Data Storage Function)

[0084] - NEF (Network Exposure Function)

[0085] - I-NEF (Intermediate NEF)

[0086] - NRF (Network Repository Function)

[0087] - NSSF (Network Slice Selection Function)

[0088] - PCF (Policy Control Function)

[0089] - SMF (Session Management Function)

[0090] - UDM (Unified Data Management)

[0091] - UDR (Unified Data Repository)

[0092] - UPF (User Plane Function)

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

[0094] - AF (Application Function)

[0095] - UE (User Equipment)

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

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

[0098] - NWDAF (Network Data Analytics Function)

[0099] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0131] - Mobility registration update; or

[0132] - Periodic registration update; or

[0133] - Emergency registration

[0134] The general registration procedure of Figures 5 and 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.

[0135] The general registration procedure of Figures 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.

[0136] First, the procedure of Fig. 5 will be explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0194] 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 is already registered with the AMF.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0232] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0240] The procedure of Fig. 8 following the procedure of Fig. 7 is described.

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

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

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

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

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

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

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

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

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

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

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

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

[0253] FIG. 9 shows an example of the overall architecture of NG-RAN to which the implementation of the present specification is applied.

[0254] Referring to FIG. 9, the NG (Next Generation)-RAN (Radio Access Network) consists of a set of gNBs connected to the 5GC via the NG interface. Alternatively, the NG-RAN may consist of a set of ng-eNBs, and the ng-eNB may consist of an ng-eNB-CU and one or more ng-eNB-DUs. The ng-eNB-CU and ng-eNB-DU are connected via the W1 interface. The general principles for the overall architecture of the NG-RAN described below also apply to the ng-eNBs and the W1 interface unless otherwise explicitly specified.

[0255] gNBs can be interconnected through the Xn interface.

[0256] A gNB may consist of a gNB-CU (Central Unit) and one or more gNB-DU (Distributed Units). The gNB-CU and gNB-DU are connected via the F1 interface. For convenience of explanation, the gNB-CU may be simply denoted as CU and the gNB-DU as DU.

[0257] A gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB or the RRC and PDCP protocols of an en-gNB, controlling the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU.

[0258] A gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by a gNB-CU. A single gNB-DU supports one or more cells. A single cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU.

[0259] A single gNB-DU can be connected to only one gNB-CU. Alternatively, for resilience, a gNB-DU can be connected to multiple gNB-CUs through appropriate implementation.

[0260] NG, Xn, and F1 are logical interfaces.

[0261] In the case of NG-RAN, the NG and Xn-C interfaces for a gNB composed of a gNB-CU and a gNB-DU terminate at the gNB-CU. In the case of EN (E-UTRAN-NR)-DC (Dual Connectivity), the S1-U and X2-C interfaces for a gNB composed of a gNB-CU and a gNB-DU terminate at the gNB-CU. The gNB-CU and the associated gNB-DU are identified as gNBs only to other gNBs and 5GCs.

[0262] FIG. 10 shows an example of the logical structure of Femto to which the implementation of the present specification applies.

[0263] The SeGW and NR Femto Management System may be outside the RAN range.

[0264] NR Femto nodes can be directly connected to 5GC. In an NG-RAN architecture, an NR Femto gateway (NR Femto GW) may be deployed to concentrate the NG-C interface between NR Femto nodes and 5GC. Depending on the implementation, NG-U transmission between NR Femto nodes and 5GC may be optionally concentrated at the NR Femto GW.

[0265] For an NR Femto node, the NG-C interface can be defined as the following interface.

[0266] Interface between the NR Femto GW and the Core Network;

[0267] Interface between the NR Femto node and the NR Femto GW;

[0268] Interface between the NR Femto node and the core network.

[0269] The NR Femto GW can be seen as a gNB for the AMF. The NR Femto GW can be seen as an AMF for the NR Femto node. The NG interface between the NR Femto node and 5GC can be the same regardless of whether the NR Femto node is connected to 5GC through the NR Femto GW.

[0270] The functions supported by the NR Femto node may be the same as the functions supported by the gNB (for example, there may be some exceptions such as the NAS Node Selection Function when the NR Femto node is connected through the NR Femto GW), and the procedures performed between the NR Femto node and 5GC may also be the same as the procedures performed between the gNB and 5GC.

[0271] Xn-connectivity may be supported between NR Femto nodes and between an NR Femto node and a gNB, regardless of whether any of the related NR Femto nodes are connected to an NR Femto GW. A single NR Femto node services one or more cells.

[0272] PNI-NPN is a network deployed for private use, relying on network functions provided by PLMN.

[0273] In PNI-NPN, a Closed Access Group (CAG) (or, Closed Access Group) can identify a group of subscribers allowed access to one or more CAG cells associated with the CAG.

[0274] In this case, a CAG cell may refer to a PLMN cell that broadcasts at least one Closed Access Group (CAG) identifier.

[0275] The CAG can be identified by the CAG identifier broadcast to SIB1.

[0276] UEs that support the CAG function can be configured as follows per PLMN.

[0277] An Allowed CAG list containing CAG identifiers that the UE is allowed to connect to; and a CAG-only indication indicating whether the UE is allowed to connect to the 5GS only through the CAG cell.

[0278] Dual Connectivity is supported and can include both PNI-NPN cells and PLMN cells depending on mobility restrictions within the UE context.

[0279] Cell selection / reselection for CAG cells may be based on the UE autonomous search function, which allows the UE to independently determine when and where to search, but cannot violate this if dedicated cell reselection priority information is stored.

[0280] The range of PCI values ​​reserved for CAG cell usage by the network can be broadcast.

[0281] A CAG Member Cell for a UE may refer to a cell that broadcasts the identifier of a selected PLMN, a registered PLMN, or an equivalent PLMN, and broadcasts a CAG identifier belonging to the UE's allowed CAG list for that PLMN.

[0282] In addition, a Non-CAG cell may refer to a PLMN cell that does not broadcast any closed access group identifier.

[0283] The UE checks the suitability of a CAG cell based on the list of accepted CAGs provided by the upper layer, and a CAG-only cell may be suitable only for the corresponding subscriber, but may be acceptable to other UEs.

[0284] A CAG-only cell may refer to a CAG cell where normal services are provided only to CAG UEs.

[0285] UEs that do not support the CAG function (e.g., Rel-15 UEs) consider a CAG-only cell to be an acceptable cell if the cell is not barred to the Rel-15 UE, a PLMN ID without a CAG list is broadcast, and that PLMN is barred (e.g., if all registration attempts are rejected and the PLMN ID becomes barred).

[0286] If the UE is set to a CAG-only indication, only CAG member cells can be suitable cells.

[0287] However, if the UE is set to a CAG-only indicator for one of the PLMNs broadcasting by the cell, a non-suitable cell may also be allowed.

[0288] In addition, manual selection of CAG cells is supported, in which case HRNN(s) may be optionally provided.

[0289] Cells serviced by NR Femto nodes may be deployed as part of PNI-NPN to restrict UE access based on their subscriptions.

[0290] The NR Femto node can use the aforementioned CAG mechanism for PNI-NPN as follows:

[0291] The NR Femto node can activate PLMN cells that legacy UEs can connect to without CAG connection control;

[0292] The NR Femto physical node can activate a physical cell shared by both PLMN and PNI-NPN as specified in Section 4.6 by broadcasting both plmn-IdentityInfoList and npn-IdentityInfoList-r16 on SIB1 without cellReservedForOtherUse;

[0293] An NR Femto node can enable an NPN-only cell by broadcasting cellReservedForOtherUseIE with the value "true", and then only UEs with an allowed CAG list containing the CAG-ID broadcast by the cell can connect to this cell.

[0294] Looking at this, it can be seen that a cell operating in hybrid access mode (i.e., a hybrid cell) is a cell shared by PLMN and CAG. A hybrid cell fundamentally supports CAG UEs (UEs that support CAG) while additionally supporting normal UEs (UEs that do not support CAG); therefore, access control and QoS for CAG UEs and normal UEs can be configured differently depending on operator policy or base station and network settings.

[0295] During the UE registration process, the 5G Femto (NG-RAN) cannot determine whether the UE has selected a PLMN cell or a CAG cell; therefore, it includes the list of CAGs supported by the current cell (i.e., the Cell CAG list) within the INITIAL UE MESSAGE. Consequently, since the AMF does not know whether the UE accessed the system via a hybrid cell, it compares the CAG information within the UE's subscription details with the Cell CAG list sent by the 5G Femto to decide whether to accept the UE's registration request. In other words, even though a UE that does not support CAG accessed the system by perceiving the hybrid cell as a PLMN cell, the AMF (considering the Cell CAG list sent by the 5G Femto because it does not know the UE accessed via a hybrid cell) may judge that the UE accessed the system via a CAG cell and perform CAG access control to reject the UE's registration request. Therefore, during the registration process, the AMF may need to be aware that the UE is accessing the AMF via a hybrid cell.

[0296] Furthermore, when a UE is accessing a hybrid cell, the UE could be a normal UE accessing via a PLMN cell or a CAG UE accessing via a CAG cell. If the network wishes to apply different QoS to normal UEs and CAG UEs, it may be necessary to determine whether the UE is a normal UE or a CAG UE. For example, an SMF may provide better QoS to a CAG UE than to a normal UE in a hybrid cell situation. Therefore, from the SMF's perspective, it may be necessary to determine whether the current UE is accessing via a hybrid cell, and if so, whether it is a normal UE or a CAG UE.

[0297] During the process of a UE moving to a target NG-RAN via NG-based Handover, AMF#2, which is associated with the target cell, cannot determine which of the three access modes the target cell is operating in. Therefore, even though the target cell is operating in hybrid access mode and the UE does not support CAG, AMF#2 can transmit Mobility Restriction List information, including NPN Mobility Information, to the target NG-RAN. In this case, NG-RAN#2 performs CAG access control on the UE based on the NPN Mobility Information, and rejects the handover request for the UE even though the UE is operating as a normal UE in the hybrid cell.

[0298] Accordingly, when a terminal receives service through 5G Femto, a method is needed to apply different policies depending on whether the terminal operates as a normal UE or a CAG UE. For example, a method may be needed to enable AMF and SMF to recognize the hybrid access mode.

[0299] In the present invention, when a UE accesses a hybrid cell, a method is presented in which a 5G Femto transmits information related to the hybrid access mode to an AMF so that the AMF can appropriately perform access control according to the UE's CAG capability. Additionally, in the above situation, a method is presented in which an AMF provides information such as the UE type and hybrid access mode to an SMF so that the SMF can provide different QoS depending on the UE type. Finally, a method is presented in which an AMF provides the UE's CAG capability to a Target NG-RAN so that the Target NG-RAN can perform access control by considering both the UE's CAG capability and the hybrid access mode during the handover process.

[0300] In this specification, the terms UE (User Equipment) and terminal are used interchangeably.

[0301] This specification focuses on the proposed content. For 5G Femto-related operations and procedures, reference will primarily be made to TS 23.501, TS 23.502, TS 38.331, TS 38.300, TS 38.413, TS 38.401, TS 38.423, etc.

[0302] The proposed method for supporting a hybrid access mode in 5G Femto may consist of a combination of one or more of the following operations / configurations / steps.

[0303] In some of the NG messages between the AMF and NG-RAN (5G Femto) described below, new NG messages may be defined and used. In addition, in some of the RRC messages between the NG-RAN and the terminal described below, new RRC messages may be defined and used.

[0304] In the procedures below, some steps may be performed simultaneously / in parallel, or in a reversed order.

[0305] The names of the indication or parameter information proposed below are examples and may be replaced with other names for the proposed procedure / purpose / method.

[0306] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings. Hereinafter, a wireless device may be referred to as a User Equipment (UE).

[0307] FIG. 11 illustrates an example of a method to which the implementation of the present specification is applied.

[0308] In particular, FIG. 11 shows an example of a method performed by an access mobility management node in a wireless communication system. For example, the access mobility management node may be an AMF. For example, the access mobility management node may be a network node responsible for access and mobility management in 6G.

[0309] In step S1101, the access mobility management node may perform the step of receiving access mode information of the cell to which the UE (User Equipment) connects from the base station.

[0310] For example, the access mode of the cell may include at least one of an open access mode, a hybrid access mode, or a closed access mode.

[0311] For example, in the case of a cell operating in hybrid access mode (i.e., a hybrid cell), it can be a cell shared by PLMN (Public Land Mobile Network) and CAG (Closed Access Group).

[0312] A hybrid cell is a cell that supports CAG UEs (or CAG-type UEs) (UEs that support CAG functionality) and additionally supports normal UEs (or normal-type UEs) (UEs that do not support CAG functionality). Depending on operator policies or base station and network settings, hybrid cells can configure access control and QoS differently for CAG UEs and normal UEs.

[0313] For example, the above base station can be a femto base station.

[0314] In step S1102, the access mobility management node can determine the type information of the UE based on the cell's access mode information and the UE's CAG (Closed Access Group) information.

[0315] For example, the type information of the above UE may include at least one of a normal type that does not use the CAG function or a CAG type that uses the CAG function.

[0316] For example, when a UE accesses a hybrid cell (a cell operating in hybrid access mode), the UE may be a normal UE (or a normal type UE) accessing through a PLMN cell, or a CAG UE (or a CAG type UE) accessing through a CAG cell.

[0317] For example, based on the fact that the UE supports the CAG function and the access mode of the cell is a hybrid access mode, the type information of the UE can be determined as the CAG type.

[0318] For example, based on the fact that the UE does not support the CAG function and the access mode of the cell is a hybrid access mode, the type information of the UE can be determined to be the normal type.

[0319] In step S1103, the access mobility management node can determine whether to perform CAG access control based on at least one of UE type information and UE's CAG information.

[0320] For example, it may be determined that the CAG connection control is not performed based on the fact that the type information of the above UE is a normal type and the above CAG information does not include a CAG-only indicator.

[0321] For example, it may be determined that the CAG connection control is performed based on the fact that the type information of the above UE is a normal type and the above CAG information includes a CAG-only indicator.

[0322] For example, it may be determined that the above CAG connection control is performed based on the fact that the UE type information is a CAG type.

[0323] For example, based on the fact that the type information of the UE is the normal type and the CAG information includes a CAG-only indicator, the registration request of the UE may be rejected according to the CAG connection control.

[0324] For example, if the type information of the above UE is the above normal type and the CAG information of the UE's subscription is included, CAG connection control may not be performed.

[0325] In step S1104, the access movement management node can transmit the cell's access mode information and the UE's type information to the session management node.

[0326] For example, based on the fact that the cell to which the UE connects is a hybrid cell, the type information of the UE may be stored in the context of the UE within the access mobility management node or transmitted to another access mobility management node upon handover.

[0327] In step S1105, the access mobility management node can obtain information related to the Quality of Service (QoS) set based on the UE type information and the cell access mode information from the session management node.

[0328] For example, the information related to the above QoS may include QoS parameters that are set differently based on the type information of the above UE.

[0329] For example, if the type of the above UE is a normal type, a low QoS can be applied.

[0330] For example, if the type of the above UE is a CAG type, a high QoS can be applied.

[0331] For example, a message including a response message to a registration request of the UE is transmitted to the base station, wherein the message does not include a list of allowed CAGs based on the UE's type information being the normal type, and the message may include a list of allowed CAGs based on the UE's type information being the CAG type.

[0332] FIG. 12 illustrates an example of another method to which the implementation of the present specification is applied.

[0333] In particular, FIG. 12 shows an example of a method performed by a session management node in a wireless communication system. For example, the session management node may be an SMF. For example, the session management node may be a network node responsible for session management in 6G.

[0334] In step S1201, the session management node may perform the step of receiving access mode information of the cell to which the UE (User Equipment) connects and type information of the UE from the access mobility management node.

[0335] For example, the access mode of the cell may include at least one of an open access mode, a hybrid access mode, or a closed access mode.

[0336] For example, in the case of a cell operating in hybrid access mode (i.e., a hybrid cell), it can be a cell shared by PLMN (Public Land Mobile Network) and CAG (Closed Access Group).

[0337] A hybrid cell is a cell that supports CAG UEs (or CAG-type UEs) (UEs that support CAG functionality) and additionally supports normal UEs (or normal-type UEs) (UEs that do not support CAG functionality). Depending on operator policies or base station and network settings, hybrid cells can configure access control and QoS differently for CAG UEs and normal UEs.

[0338] For example, the type information of the above UE may include at least one of a normal type that does not use the CAG function or a CAG type that uses the CAG function.

[0339] For example, when a UE accesses a hybrid cell (a cell operating in hybrid access mode), the UE may be a normal UE (or a normal type UE) accessing through a PLMN cell, or a CAG UE (or a CAG type UE) accessing through a CAG cell.

[0340] For example, based on the fact that the UE supports the CAG function and the access mode of the cell is a hybrid access mode, the type information of the UE can be determined as the CAG type.

[0341] For example, based on the fact that the UE does not support the CAG function and the access mode of the cell is a hybrid access mode, the type information of the UE can be determined to be the normal type.

[0342] In step S1202, the session management node may perform the step of transmitting information related to the Quality of Service (QoS) set based on the UE's type information and the cell's access mode information to the access mobility management node.

[0343] For example, the information related to the above QoS may include QoS parameters that are set differently based on the type information of the above UE.

[0344] For example, if the type of the above UE is a normal type, a low QoS can be applied.

[0345] For example, if the type of the above UE is a CAG type, a high QoS can be applied.

[0346] FIGS. 13a and FIGS. 13b illustrate examples of registration procedures for determining the type of a UE and controlling the connection to which the implementation of the present specification applies.

[0347] Although this specification assumes a situation where 5G Femto #1 is divided into a CU and a DU, it may also be applied to situations where 5G Femto #1 is not separated into a CU and a DU. Additionally, NG-RAN #2 may be a base station supporting 5G Femto (i.e., a 5G Femto node) or a general base station (i.e., an NG-RAN). This may be applied throughout this specification.

[0348] First, Figure 13a will be explained.

[0349] 1. The DU of 5G Femto#1 can send an F1 setup request message to set up an F1 interface with the CU (S1301).

[0350] At this stage, the DU of 5G Femto #1 can explicitly inform the CU of 5G Femto #1 that a specific cell is operating in hybrid access mode for 5G Femto. That is, the DU of 5G Femto #1 can include the new indication in the F1 SETUP REQUEST message. Alternatively, the DU of 5G Femto #1 can implicitly inform that the cell is operating in hybrid access mode by providing a SIB1 that includes hybrid access mode (i.e., setting cellReservedForOtherUseIE to false in the CAG cell). For example, an NR Femto node can enable a cell shared by the PLMN and CAG by broadcasting both plmn-IdentityInfoList and npn-IdentityInfoList-r16 in the SIB1 but not setting cellReservedForOtherUse. In this case, the cell can be accessed by UEs that possess an allowed CAG list containing the CAG-ID broadcast from the cell. For legacy UEs that do not support CAG, the cell may be recognized as a standard PLMN cell.

[0351] 2. The CU of 5G Femto#1 can trigger an NG setup procedure to set up an NG interface with the AMF (S1302).

[0352] If hybrid cell support is provided on a TAI (Tracking Area Identity) basis (i.e., multiple cells corresponding to a specific TAI are all operating in hybrid access mode), the CU may notify the AMF that all cells belonging to the TAI support hybrid access mode. In this case, the AMF may determine whether the cell connected to the UE is operating in hybrid access mode based on the basic User Location TAI information included in the Initial UE Message of S1310 described below.

[0353] For example, if core network capability (e.g., when the AMF needs to be enhanced or the SMF needs to be enhanced) is required to support a cell operating in hybrid access mode, the AMF can transmit core network capability information to the NG-RAN during the NG-Setup process. Subsequently, the CU can transmit information to the DU regarding whether hybrid cell support is possible via F1 signaling. Through this, the DU can confirm that it is capable of operating as a hybrid cell and decide to operate as a hybrid cell.

[0354] 3. The CU of 5G Femto#1 may respond to the DU of 5G Femto#1 with an F1 SETUP RESPONSE message including a list of cells to be activated, etc. (S1303).

[0355] 4a. The CU of 5G Femto#1 can set up an Xn interface with NG-RAN#2 by sending an Xn SETUP REQUEST message to NG-RAN#2 (S1304).

[0356] At this stage, the CU of 5G Femto#1 can transmit a list of cells capable of operating in hybrid access mode in 5G Femto#1 to NG-RAN#2.

[0357] 4b. NG-RAN#2 can respond to 5G Femto#1 with an Xn SETUP RESPONSE message (S1305).

[0358] If NG-RAN#2 that receives the Xn SETUP REQUEST message is a 5G Femto node, it can also inform 5G Femto#1 of the list of cells that can operate in hybrid access mode from NG-RAN#2 (i.e., 5G Femto#2) in the Xn SETUP RESPONSE message.

[0359] 5. For a cell operating in hybrid access mode, the DU of 5G Femto#1 can broadcast by including a list of CAG IDs that the cell can support and cellReservedForOtherUseIE set to false in SIB1 (S1306).

[0360] Based on the SIB1 received in step S1306, the UE can determine that the current cell is operating in hybrid mode, and based on this, can determine whether the UE can access the cell.

[0361] 6a. If the UE determines that it can access the cell, it may send an RRCSetupRequest message to the DU of 5G Femto#1 (S1307).

[0362] 6b. The DU of 5G Femto#1 may include the RRCSetupRequest message received from the UE and the cell ID information currently accessed by the UE in the INITIAL UL RRC MESSAGE TRANSFER message and transmit it to the CU.

[0363] The CU of 5G Femto#1 can determine that the current UE is accessing 5G Femto#1 through a cell operating in hybrid access mode by combining the information included in the F1 SETUP REQUEST message received in step S1301 and the cell ID received in step S1307. Alternatively, even if the DU of 5G Femto#1 does not notify the CU of the list of cells capable of operating in hybrid access mode in step S1301, the DU may explicitly notify the CU in step S1307 that the UE is accessing the DU through a cell operating in hybrid access mode using the INITIAL UL RRC MESSAE TRANSFER message.

[0364] 7a / 7b. If the CU of 5G Femto#1 decides to establish an RRC connection with the UE, it may send an RRCSetup message to the UE through the DU (S1308).

[0365] 8a / 8b. The UE can respond to the CU of 5G Femto #1 using the RRCSetupComplete message (S1309). At this stage, the UE can include a Registration Request message for network registration in the RRCSetupComplete message and transmit it.

[0366] Now, Fig. 13b will be described. The operation of Fig. 13b can be performed following the operation of Fig. 13a.

[0367] 9. The CU of 5G Femto#1 can include the Registration Request message received in step S1309 in the INITIAL UE MESSAGE message and transmit it to the AMF (S1310). At this step, the UE can also inform the AMF that it is currently accessing 5G Femto#1 through a cell operating in hybrid access mode.

[0368] For example, the AMF can determine whether the UE's serving cell is a PLMN cell or a CAG cell from the UE's perspective by considering information regarding whether the UE supports CAG among the UE's 5GMM Core Network capabilities and the access mode of the cell the UE is currently accessing (i.e., one of open access mode, hybrid access mode, or closed access mode).

[0369] For example, if a UE that does not support CAG accesses a cell operating in hybrid access mode, the AMF may determine that the UE is a normal type accessing through a PLMN cell. Therefore, even if CAG information is included in the UE's subscription information, the AMF may not perform CAG access control for the UE.

[0370] For example, CAG access control can be performed only when the CAG information contains a CAG-only indication (i.e., an indication of whether the UE is allowed to access the 5GS only through the CAG cell). (i.e., the AMF can perform a Registration Reject for the UE's Registration Request).

[0371] For example, if the CAG information does not include a CAG-only indication, CAG access control for the UE may not be performed.

[0372] For example, if a UE supporting CAG accesses a cell operating in hybrid access mode, the AMF can determine that the UE is a CAG-type UE connecting through the CAG cell. Therefore, CAG access control for the UE must be performed based on the UE's subscription information.

[0373] The AMF determines whether the UE operates as a normal type or a CAG type in the hybrid access cell, and can store the determined UE type information in the UE context. If an AMF change occurs, the UE type information can be transferred to another AMF.

[0374] 10. The AMF may send an Nsmf_PDUSession_UpdateSMContext Request message to the SMFs associated with each PDU Session associated with the above-mentioned UE (S1311). Additionally, based on the above-mentioned S1310, the AMF may inform the SMF whether the UE is currently accessing a cell operating in hybrid access mode and whether the UE is a normal type UE or a CAG type UE. Alternatively, the AMF may inform the SMF of the UE type only if the UE is a normal type UE. Upon receiving this, the SMF may transmit the relevant information to the PCF. This may be done based on the PCRT (Policy Control Request Triggers) set by the PCF. The PCF may update the PCC rule to control QoS based on the fact that the UE is operating as a normal type UE in the hybrid cell. Additionally, the SMF may set the QoS based on this. For example, the QoS of a normal type UE may be a lower level of QoS compared to the QoS provided for a CAG type UE.

[0375] 11. Each SMF that receives the Nsmf_PDUSession_UpdateSMContext Request message from the AMF can set the QoS differently depending on whether the UE is a normal type UE or a CAG type UE.

[0376] For example, SMF can provide better QoS to CAG-type UEs than to normal-type UEs among multiple UEs accessed through a cell operating in hybrid access mode.

[0377] Based on this, SMF can transmit N2 SM information to be delivered to 5G Femto#1 to AMF via the Nsmf_PDUSession_UpdateSMContext Response message (S1312).

[0378] 12. The AMF can transmit the N2 SM information received from the SMF and the Registration Accept message to be delivered to the UE to 5G Femto#1 via an Initial Context Setup Request message (S1313).

[0379] For example, if the AMF determines the UE to be a normal type UE in step S1310, the AMF may not include the NPN Mobility Information IE (i.e., Allowed CAG list) in the Mobility Restriction List IE transmitted to 5G Femto#1.

[0380] For example, if the AMF determines the UE to be a CAG type UE in step S1310, the AMF may include NPN Mobility InformationIE in the Mobility Restriction ListIE transmitted to 5G Femto#1.

[0381] 5G Femto #1 can implicitly determine whether the UE is a normal type UE or a CAG type UE by whether NPN Mobility Information is included in the Mobility Restriction List.

[0382] For example, it is also possible for the AMF to explicitly inform 5G Femto#1 by including an indication that the above UE is a normal type UE or a CAG type UE.

[0383] 13. Based on the information received in step S1313, the CU of 5G Femto#1 may trigger the UE Context Setup procedure toward the DU and also send a Registration Accept message to be delivered to the UE (S1314).

[0384] 14. The remaining steps of the registration procedure disclosed in FIGS. 5 and FIGS. 6 can be executed (S1315).

[0385] FIG. 14 shows an example of instructions for a hybrid access mode during a PDU session setup procedure to which the implementation of the present specification applies.

[0386] 1. The UE can transmit an RRC message including a PDU Session Establishment Request message to the base station (5G Femto #1) to create a new PDU session (S1401).

[0387] 2. The DU of 5G Femto#1 can transmit the RRC message received from the UE to the CU via the UL RRC MESSAGE message (S1402).

[0388] 3. The CU of 5G Femto#1 can send a PDU Session Establishment Request message received from the UE to the AMF via an UPLINK NAS TRANSPORT message (S1403).

[0389] If the UE is accessing through a cell operating in hybrid access mode, this information can be included in an UPLINK NAS TRANSPORT message and transmitted to the AMF. Additionally, as in step S1313 of FIG. 13, if 5G Femto #1 already knows whether the UE is a normal type UE or a CAG type UE, information about the UE type can also be transmitted to the AMF.

[0390] If hybrid cell support is provided on a TAI (Tracking Area Identity) basis (i.e., multiple cells corresponding to a specific TAI all operate in hybrid access mode), and the CU of 5G Femto #1 has already informed the AMF during the NG setup process that all cells corresponding to the TAI support hybrid access mode, the AMF can determine whether the cell connected to the UE is operating in hybrid access mode based on the basic User Location TAI information included in the UPLINK NAS TRANSPORT message of S1403.

[0391] 4. To set up (or establish) a PDU Session associated with the above UE, the AMF may trigger the Nsmf_PDUSession_CreateSMContext procedure to the SMFs associated with each PDU Session (S1404).

[0392] At this stage, the AMF can inform the SMF that the UE is accessing through a cell operating in hybrid access mode and whether the current UE is a normal type UE or a CAG type UE. The AMF can receive this information from 5G Femto#1 through step S1403. Alternatively, it may store information obtained during the UE registration process as described in FIG. 11 above.

[0393] Based on information received from the AMF, each SMF can set the QoS differently depending on whether the UE is a normal type UE or a CAG type UE.

[0394] For example, SMF can provide better QoS to CAG-type UEs than to normal-type UEs among multiple UEs accessed through a cell operating in hybrid access mode.

[0395] 5. Based on the QoS determined in step S1404, the SMF can generate N2 SM information to be transmitted to 5G Femto#1 and transmit it to the AMF through the Namf_Communication_N1N2Message Transfer procedure (S1405).

[0396] 6. The AMF transmits the N2 SM information received from the SMF and the PDU Session Establishment Accept message to be delivered to the UE to 5G Femto#1 via the PDU SESSION RESOURCE SETUP REQUEST message (S1406).

[0397] 7a / 7b. Based on the information received in step S1406, the CU of 5G Femto#1 sends a UE CONTEXT MODIFICATION REQUEST message to the DU. Additionally, the CU may send a PDU Session Establishment Accept message to the UE through the DU (S1407).

[0398] 8. The DU of 5G Femto#1 can update the context for the UE based on the information received in step S1407 and then respond to the CU via a UE CONTEXT MODIFICATION RESPONSE message (S1408).

[0399] 9. The remaining steps of the PDU Session Establishment procedure disclosed in FIGS. 7 and FIGS. 8 can be executed (S1409).

[0400] FIG. 15 illustrates an example of an NG-based handover procedure based on instructions for a hybrid access mode to which the implementation of the present specification applies.

[0401] Although the following description is based on the premise that NG-RAN#1 and NG-RAN#2 are connected to AMF#1 and AMF#2, respectively, it may also be applied to situations where NG-RAN#1 and NG-RAN#2 are connected to the same AMF. This may be applied throughout the entire specification.

[0402] NG-RAN#1 can decide to hand over the UE to the target cell of NG-RAN#2 based on the UE's measurement reports.

[0403] 1. NG-RAN#1 can send a HANDOVER REQUIRED message to AMF#1 (S1501).

[0404] 2. AMF#1 can notify AMF#2 that the UE requires a handover to NG-RAN#2 via the Namf_Communication_CreateUEContext Request message. Additionally, AMF#1 can transmit the UE context stored within AMF#1 to AMF#2 (S1502).

[0405] If AMF#1 has already determined whether the UE operates as a normal type UE or a CAG type UE in a hybrid access cell, it can directly transmit the UE type information to AMF#2.

[0406] 3. AMF#2 can notify each SMF managing the PDU Session for the UE through the Nsmf_PDUSession_UpdateSMContext procedure that the PDU session is being handed over to NG-RAN#2. Additionally, each SMF can decide whether to accept this (S1503).

[0407] 4. AMF#2 can send a handover request message to NG-RAN#2 (S1504).

[0408] For example, AMF#2 can transmit to NG-RAN#2 whether the UE supports CAG based on information received from AMF#1 (e.g., the UE's 5GMM Core Network capability).

[0409] For example, AMF#2 can configure the NPN Mobility InformationIE within the Mobility Restriction ListIE based on the subscription information of the above UE and transmit it together to NG-RAN#2. Therefore, even if the above UE is a UE that does not support CAG, if CAG information exists within the UE's subscription information, AMF#2 can transmit the NPN Mobility InformationIE to NG-RAN#2.

[0410] 5. NG-RAN#2 can send a Handover request acknowledge message to AMF#2 (S1505).

[0411] NG-RAN#2 can decide whether to accept a handover request to the target cell selected by NG-RAN#1.

[0412] At this stage, the access mode of the cell can be received from the target base station through a handover request acknowledge message.

[0413] For example, if NG-RAN#2 is a 5G Femto node, NG-RAN#2 can decide whether to accept a Handover by considering the access mode of the target cell selected by NG-RAN#1 (i.e., open access mode, hybrid access mode, or closed access mode), UE CAG capability, and NPN Mobility Information in the Mobility Restriction List.

[0414] For example, if a UE that does not support CAG is handed over to a target cell operating in hybrid access mode (Case A), NG-RAN#2 may accept the handover for said UE regardless of the NPN Mobility InformationIE in the Mobility Restriction ListIE. Alternatively, in the situation of Case A, if the NPN Mobility InformationIE contains a PNI-NPN RestrictedIE set to "restricted", the handover request may be rejected.

[0415] If NG-RAN#2 accepts the Handover for the above UE, it may respond to AMF#2 via a HANDOVER REQUEST ACKNOWLEDGE message. The HANDOVER REQUEST ACKNOWLEDGE message may include an indication indicating whether the target cell is currently operating in hybrid access mode.

[0416] 6. AMF#2 can determine whether the UE's target cell is a PLMN cell or a CAG cell from the current UE's perspective by considering information on whether the UE supports CAG and information on the target cell's access mode (i.e., open access mode, hybrid access mode, or closed access mode). That is, if a UE that does not support CAG accesses a cell operating in hybrid access mode, AMF#2 can determine that the UE is a normal type UE accessing through a PLMN cell. However, if a UE that supports CAG accesses a cell operating in hybrid access mode, AMF#2 can determine that the UE is a CAG type UE accessing through a CAG cell.

[0417] AMF#2 can transmit the DL TEID to NG-RAN#2 by sending an Nsmf_PDUSession_UpdateSMContext Request message to the SMFs associated with each PDU Session. Additionally, it can also transmit to the SMF whether the UE is accessing through a cell operating in hybrid access mode and whether the current UE is a normal UE or a CAG UE (S1506).

[0418] Upon receiving this, the SMF can transmit relevant information to the PCF. This may be done based on the PCRTs (Policy Control Request Triggers) configured by the PCF. The PCF can update PCC rules to control QoS based on whether the UE is operating as a normal type UE in a hybrid cell. Additionally, the SMF can set the QoS based on this. For example, the QoS for a normal type UE may be at a lower level compared to the QoS provided for a CAG type UE.

[0419] 7. After updating the DL TEID associated with each PDU Session, the SMF can send it to AMF#2 via the Nsmf_PDUSession_UpdateSMContext Response message (S1507).

[0420] 8. AMF#2 transmits the result of the handover request for the UE to AMF#1 via the Namf_Communication_CreateUEContext Response message (S1508).

[0421] 9. AMF#1 sends a handover command message to NG-RAN#1 (S1509).

[0422] 10. In accordance with Clause 4.9.1.3.3 in TS 23.502, the remaining process during the NG-based handover (Execution phase) procedure may be executed (S1510).

[0423] 11. The SMF may request a QoS change based on the type information of the above UE and perform the PDU Session Modification procedure defined in Section 4.3.3.2 of TS 23.502 (S1511).

[0424] Based on the information received in step S1506, the SMF can set the QoS differently depending on whether the UE is accessing through a cell operating in hybrid access mode and whether the UE is a normal type UE or a CAG type UE.

[0425] For example, the SMF can provide better QoS to a CAG-type UE than to a normal-type UE among several UEs accessed through a cell operating in hybrid access mode. Therefore, the SMF can trigger a PDU Session Modification procedure toward NG-RAN#2 to set the QoS differently depending on whether the UE is a normal-type UE or a CAG-type UE.

[0426] Alternatively, instead of AMF#2 transmitting the UE's type information and hybrid access mode information to SMF in step S1506, the PDU Session Modification procedure may be triggered by AMF#2 transmitting the UE's type information and hybrid access mode information to SMF after the NG-based handover procedure is completed and requesting a QoS change based on the UE's type information.

[0427] FIG. 16 shows an example in which an indicator for a hybrid access mode is applied during an NG-based handover procedure to which the implementation of the present specification is applied.

[0428] Meanwhile, for the sake of convenience of explanation, the source access mobility management node will be referred to as AMF #1 and the target access mobility management node as AMF #2.

[0429] NG-RAN#1 can decide to hand over the UE to the target cell of NG-RAN#2 based on the UE's measurement reports.

[0430] 1. NG-RAN#1 can send a HANDOVER REQUIRED message to AMF#1 (S1601).

[0431] If it is known that the target cell can operate in a hybrid access mode through the Xn interface, as in steps S1504 to S1505 of FIG. 15 described above, NG-RAN#1 can transmit the information to AMF#1 through a HANDOVER REQUIRED message.

[0432] 2. AMF#1 can notify AMF#2 via the Namf_Communication_CreateUEContext Request message that the UE needs a handover to NG-RAN#2 and transmit the UE context stored in AMF#1 to AMF#2 (S1602).

[0433] If, in step S1601, access mode information for the target cell is received, the access mode information can be transmitted to AMF#2.

[0434] For example, the access mode information of the cell can be received from the source access mobility management node of the handover.

[0435] AMF#2 can determine whether the UE will operate as a normal type UE or a CAG type UE in a target cell in hybrid access mode by considering the information received from AMF#1 regarding whether the UE supports CAG and the access mode information of the target cell (i.e., one of open access mode, hybrid access mode, or closed access mode).

[0436] For example, if a UE that does not support CAG is handed over to a target cell operating in hybrid access mode (Case A), AMF#2 may determine that the UE is a normal type UE. Additionally, it may continue to execute the remaining procedures of an NG-based handover. However, AMF#2 may reject the handover request for the UE if the CAG information in the UE’s subscription contains a CAG-only indication (i.e., an indication of whether the UE is allowed to access 5GS only through a CAG cell).

[0437] For example, if a UE supporting CAG is handed over to a target cell operating in hybrid access mode, AMF#2 can determine that the UE is a CAG-type UE accessing through the CAG cell. Additionally, in step S1604, NG-RAN#2 can transmit to NG-RAN#2 the NPN Mobility InformationIE required for access control of the UE, including it in the Mobility Restriction ListIE.

[0438] 3. AMF#2 may notify each SMF managing the PDU Session for the UE through the Nsmf_PDUSession_UpdateSMContext procedure that the PDU session will be handed over to NG-RAN#2. Additionally, each SMF may decide whether to accept this (S1603).

[0439] For example, AMF#2 can inform the SMF whether the UE is accessing a cell operating in hybrid access mode and whether the current UE is a normal type UE or a CAG type UE. Upon receiving this, the SMF can transmit the relevant information to the PCF. This may be done based on the PCRTs (Policy Control Request Triggers) configured by the PCF. The PCF can update PCC rules to control QoS based on the fact that the terminal is operating as a normal type UE in the hybrid cell. Additionally, the SMF can set the QoS based on this. For example, the QoS for a normal type UE may be at a lower level compared to the QoS provided for a CAG type UE.

[0440] Based on this, the SMF will hand over the above UE to a target cell operating in hybrid access mode, and can set the QoS differently depending on whether the UE is a normal type UE or a CAG type UE.

[0441] For example, SMF can provide better QoS to CAG-type UEs than to normal-type UEs among multiple UEs accessed through a cell operating in hybrid access mode.

[0442] SMF can transmit N2 SM information with different QoS settings depending on whether the above UE is a normal type UE or a CAG type UE to AMF#2 through the Nsmf_PDUSession_UpdateSMContext procedure.

[0443] 4. AMF#2 can send a handover request message to NG-RAN#2. AMF#2 can also send N2 SM information received from SMF to NG-RAN#2 (S1604).

[0444] In addition, as in step S1513 of FIG. 15 described above, depending on whether the UE is a normal type UE or a CAG type UE, a Mobility Restriction ListIE can be configured and transmitted to NG-RAN#2.

[0445] 5. NG-RAN#2 can decide whether to accept a handover request to the target cell selected by NG-RAN#1 (S1605).

[0446] For example, NG-RAN#2 can implicitly determine whether the UE is a normal type UE or a CAG type UE based on the Mobility Restriction ListIE received in Step 4.

[0447] For example, AMF#2 may explicitly inform NG-RAN#2 whether the UE is a normal type UE or a CAG type UE by including an indication in step S1604.

[0448] 6. AMF#2 can transmit the DL TEID to NG-RAN#2 by sending an Nsmf_PDUSession_UpdateSMContext Request message to the SMFs associated with each PDU Session. Additionally, after updating the DL TEID associated with each PDU Session, the SMF can respond to AMF#2 via an Nsmf_PDUSession_UpdateSMContext Response message (S1606).

[0449] 7. AMF#2 can transmit the result of the Handover request for the UE to AMF#1 via the Namf_Communication_CreateUEContext Response message (S1607).

[0450] 8. AMF#1 can send a handover command message to NG-RAN#1 (S1608).

[0451] 9. The remaining process during the NG-based handover (Execution phase) procedure may be executed in accordance with Clause 4.9.1.3.3 in TS 23.502 (S1609).

[0452] Although FIGS. 15 and 16 assume an NG-based handover situation, it is also possible for the UE to move from NG-RAN#1 to NG-RAN#2 using Xn-based handover.

[0453] In this case, when NG-RAN#1 selects a target cell of NG-RAN#2, it may also refer to the list of cells capable of operating in hybrid access mode in NG-RAN#2 (which was exchanged during the Xn Setup process).

[0454] Additionally, NG-RAN#1 can include the Mobility Restriction List information received from the AMF in the Xn Handover Request message and transmit it to NG-RAN#2. NG-RAN#2 can determine whether the UE operates as a normal type UE or a CAG type UE in the target cell by considering the Mobility Restriction List information and the access mode of the target cell. If the handover request for the UE is accepted, NG-RAN#2 can transmit information regarding the UE's type and hybrid access mode to the SMF via the AMF.

[0455] After the Xn-based handover procedure is completed, SMF can trigger a PDU Session Modification procedure toward NG-RAN#2 to update QoS according to the type of UE.

[0456] This specification may have various effects.

[0457] For example, during the UE registration process, the AMF can control access to UEs by considering the UE's CAG capability, the access mode of the serving cell the UE is currently accessing (or the target cell to be handed over), and CAG information within the UE's subscription.

[0458] For example, in a handover procedure, the target NG-RAN can control access to UEs by considering the UE's CAG capability, the access mode of the serving cell (or target cell to be handed over) that the UE is currently accessing, and CAG information within the UE's subscription.

[0459] For example, if a UE accesses through a hybrid cell, the SMF can provide appropriate QoS depending on the type of UE.

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

[0461] 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 a method performed by an access movement management node, A step of receiving access mode information of the cell to which the UE (User Equipment) connects from the base station; A step of determining the type information of the UE based on the access mode information of the cell and the CAG (Closed Access Group) support capability of the UE; A step of determining whether to perform CAG connection control based on at least one of the type information of the UE and the CAG information of the UE; A step of transmitting access mode information of the cell and type information of the UE to a session management node; and A method comprising the step of obtaining information related to Quality of Service (QoS) set based on type information of the UE and access mode information of the cell from the session management node.

2. A method according to claim 1, wherein the access mode of the cell includes at least one of an open access mode, a hybrid access mode, or a closed access mode.

3. A method according to claim 1, wherein the type information of the UE includes at least one of a normal type that does not use a CAG function or a CAG type that uses a CAG function.

4. A method in which, in the third paragraph, the type information of the UE is determined to be the CAG type based on the fact that the UE supports the CAG function and the access mode of the cell is a hybrid access mode or a closed access mode.

5. A method in which, in the third paragraph, the type information of the UE is determined to be the normal type based on the fact that the UE does not support the CAG function and the access mode of the cell is a hybrid access mode or a closed access mode.

6. A method in which, in claim 3, it is determined that the CAG connection control is not performed based on the fact that the type information of the UE is a normal type and the CAG information does not include a CAG-only indicator.

7. A method in which, in claim 3, it is determined that the CAG connection control is performed based on the fact that the type information of the UE is a normal type and the CAG information includes a CAG-only indicator.

8. A method in which, in claim 3, it is determined that the CAG connection control is performed based on the fact that the type information of the UE is a CAG type.

9. A method in which a registration request of the UE is rejected according to the CAG connection control based on the fact that the type information of the UE is the normal type and the CAG information includes a CAG-only indicator.

10. A method according to claim 1, wherein, based on the fact that the cell to which the UE connects is a hybrid cell, the type information of the UE is stored in the context of the UE within the access mobility management node or transmitted to another access mobility management node upon handover.

11. A method according to claim 1, wherein the information related to the QoS includes QoS parameters that are differently set based on the type information of the UE.

12. A method of applying a low QoS in the case where the type of the UE in claim 11 is a normal type.

13. A method for applying high QoS in the case where the type of the UE in claim 11 is a CAG type.

14. In claim 1, the method further comprises the step of transmitting a message including a response message to a registration request of the UE to the base station, and The above message does not include a list of allowed CAGs based on the type information of the UE being the normal type, and The above message is a method that includes a list of allowed CAGs based on the fact that the type information of the UE is the CAG type.

15. The method according to claim 1, wherein the base station is a femto base station.

16. In Paragraph 1, The above base station is a method in which the target base station for handover is a handover.

17. In claim 16, the method of receiving access mode information of the cell from the target base station through a handover request confirmation message.

18. In Paragraph 16, A method of receiving access mode information of the above cell from the source connection mobility management node of the above handover.

19. In an access mobility management node, the access mobility management node is: One or more processors; and It includes one or more memories that can be connected to operate with the above one or more processors, and The above one or more memories store instructions that perform operations based on execution by the above one or more processors, and The above operation is: A step of receiving access mode information of the cell to which the UE (User Equipment) connects from the base station; A step of determining the type information of the UE based on the access mode information of the cell and the CAG (Closed Access Group) support capability of the UE; A step of determining whether to perform CAG connection control based on at least one of the above UE type information and the above UE's CAG information; A step of transmitting access mode information of the cell and type information of the UE to a session management node; An access mobility management node comprising the step of obtaining information related to Quality of Service (QoS) set based on type information of the UE and access mode information of the cell from the session management node.

20. In a method performed by a session management node, A step of receiving access mode information of a cell to which a UE (User Equipment) connects and type information of said UE from an access mobility management node; and A method comprising the step of transmitting information related to the Quality of Service (QoS) set based on the type information of the UE and the access mode information of the cell to the access mobility management node.

21. In a session management node, the session management node is: One or more processors; and It includes one or more memories that can be connected to operate with the above one or more processors, and The above one or more memories store instructions that perform operations based on execution by the above one or more processors, and The above operation is: A step of receiving access mode information of a cell to which a UE (User Equipment) connects and type information of said UE from an access mobility management node; and A session management node comprising the step of transmitting information related to the Quality of Service (QoS) set based on the type information of the UE and the access mode information of the cell to the access mobility management node.

Images