Support for CAG having validity condition in 5g femto

Abstract

Provided are a method for supporting a closed access group (CAG) having a validity condition in a 5G femto, and an apparatus related thereto. An access and mobility management node performs a step of receiving, from a base station, information related to a cell accessed by a user equipment (UE). The access and mobility management node performs a step of performing access control of the UE on the basis of the information and subscription data of the UE. The access and mobility management node performs a step of transmitting, to the base station, information of a CAG associated with a validity condition on the basis of the access control. The access and mobility management node performs a step of determining the validity condition associated with the CAG. The access and mobility management node performs a step of changing a valid state of the CAG according to the determination result of the validity condition. The access and mobility management node performs a step of transmitting, to the base station, information related to the change of the valid state of the CAG.

Description

CAG support with validity conditions in 5G femto.

[0001] This specification relates to CAG support having validity conditions 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 wireless communication systems, various access control mechanisms have been introduced to meet diverse deployment scenarios and operator requirements. Particularly in small-scale cell deployment environments, access control and differentiation of quality of service for specific user groups have emerged as critical requirements.

[0005] To meet these requirements, the Closed Access Group (CAG) function was introduced, enabling the operation of cell access modes in three forms: open, hybrid, and closed. In particular, a cell operating in hybrid access mode (hereinafter referred to as a 'hybrid cell') is a cell shared by the Public Land Mobile Network (PLMN) and the CAG, allowing for simultaneous service to both CAG-supporting terminals (hereinafter referred to as 'CAG UEs') and general terminals that do not support CAG (hereinafter referred to as 'normal UEs'). Access control and Quality of Service (QoS) for CAG UEs and normal UEs can be configured differentially based on operator policies or base station and network settings.

[0006] Meanwhile, small cell services can also be provided through CAGs with validity conditions. These validity conditions mean that the validity of a specific CAG can be changed based on time, location, or other dynamic parameters.

[0007] However, the introduction of these validity conditions may lead to several technical issues. For example, a terminal connected to a hybrid cell may pass CAG connection control and receive high-quality service (i.e., enhanced QoS), but the corresponding CAG may become invalid due to a change in the validity conditions. In such a case, the network may be unable to maintain the high QoS provided to the terminal through the CAG cell and may have to switch to providing relatively lower-quality service through the PLMN cell. Conversely, if a previously invalid CAG becomes valid again due to a change in the validity conditions, the network must be able to provide the terminal with enhanced QoS through the CAG cell again.

[0008] Furthermore, additional issues may arise regarding the handover procedure. When a terminal moves to a target small cell via Xn-based handover, if the target cell is a hybrid cell, a situation may occur where the target base station cannot clearly determine whether the terminal can receive services through the PLMN cell or if it must receive services exclusively through the CAG. This lack of information can cause difficulties for the target base station in applying appropriate access control and QoS policies, potentially leading to handover failure or service quality degradation.

[0009] Therefore, an improved method and device may be required to efficiently manage the connection mode change and QoS switching of a terminal in a CAG environment with validity conditions, and to enable the target base station to accurately identify the terminal's available connection mode during handover.

[0010] 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 information related to 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 transmitting information of a Closed Access Group (CAG) associated with a validity condition based on access control to a base station by the access mobility management node.

[0011] This method includes the step of determining the validity condition associated with the CAG by an access mobility management node. This method includes the step of changing the validity state of the CAG by the access mobility management node according to the result of determining the validity condition. This method includes the step of transmitting information related to the change in the validity state of the CAG to a base station by the access mobility management node.

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

[0013] This specification may have various effects.

[0014] For example, AMF may provide a lower level of service than before without immediately disconnecting the connection to the UE even if a specific CAG becomes invalid due to a validity condition. Conversely, if a specific CAG becomes valid due to a validity condition, it may provide a higher level of service to the UE.

[0015] More specifically, even if the validity of a CAG is lost, the network can maintain service continuity by switching the terminal to be serviced via a PLMN cell. This allows terminal users to continue using communication services without interruption, even when transitioning from CAG-based enhanced service quality to standard PLMN service quality. Conversely, if a specific CAG becomes valid again based on validity conditions, the network can improve the level of service provided to that terminal. In other words, as the validity of the CAG is restored, a terminal that previously received standard service via a PLMN cell can automatically receive higher QoS, enabling dynamic service quality management.

[0016] For example, even if the cell cannot continuously service the UE due to reasons such as radio quality, when handing the terminal over to another nearby cell, even the lowest level of service can be provided continuously without interruption.

[0017] For example, since the target base station can accurately identify information regarding the terminal's available access mode and service level during the handover process, service continuity can be guaranteed by applying appropriate access control and QoS policies even when the target cell is a hybrid cell.

[0018] For example, through these improved mechanisms, networks can perform more flexible and efficient resource management, and terminal users can receive stable and continuous communication services despite various changes in conditions. In addition, operators can effectively implement differentiated service policies through dynamic access control based on validity conditions, which can contribute to supporting various business models and service scenarios.

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

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

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

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

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

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

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

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

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

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

[0029] FIGS. 12 and FIGS. 13 illustrate examples of CAG support procedures considering validity conditions to which the implementation of the present specification applies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] 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 considering 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. FIG. 2 illustrates an example of a wireless device to which the implementation of this specification applies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] - AUSF (Authentication Server Function)

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

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

[0091] - USDF (Unstructured Data Storage Function)

[0092] - NEF (Network Exposure Function)

[0093] - I-NEF (Intermediate NEF)

[0094] - NRF (Network Repository Function)

[0095] - NSSF (Network Slice Selection Function)

[0096] - PCF (Policy Control Function)

[0097] - SMF (Session Management Function)

[0098] - UDM (Unified Data Management)

[0099] - UDR (Unified Data Repository)

[0100] - UPF (User Plane Function)

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

[0102] - AF (Application Function)

[0103] - UE (User Equipment)

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

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

[0106] - NWDAF (Network Data Analytics Function)

[0107] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0139] - Mobility registration update; or

[0140] - Periodic registration update; or

[0141] - Emergency registration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0240] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0283] A CAG-only cell (or closed cell) may refer to a CAG cell where normal services are provided only to the CAG UE.

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

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

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

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

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

[0289] - NR Femto nodes can activate PLMN cells that legacy UEs can connect to without CAG connection control;

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

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

[0292] Looking at the first bullet, there is an Open cell (i.e., a PLMN cell) that can be accessed by legacy UEs. Looking at the third bullet, there is a Closed cell (i.e., a CAG cell) that provides service only to UEs among CAG-supported UEs that have a CAG ID supported by the cell in the Allowed CAG list.

[0293] Finally, there is a Shared cell that is recognized as a CAG cell by CAG-supported UEs that have the CAG ID supported by the cell in the Allowed CAG list, and as an Open cell by CAG-non-supporting UEs. Since this Shared cell primarily supports CAG-supporting UEs while additionally supporting CAG-non-supporting UEs, access control and QoS for CAG-supporting and CAG-non-supporting UEs can be configured differently depending on operator policies or base station and network settings.

[0294] 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 service through 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 if a UE that does not support CAG accesses the service by perceiving the shared cell as a PLMN cell, the AMF may reject the registration request by performing CAG access control. This is because the AMF (since it does not know that the UE accessed the service through a shared cell) assumes the UE accessed the service through a CAG cell. Therefore, during the registration process, the AMF may need to be aware that the UE is accessing the AMF through a shared cell.

[0295] Additionally, when a UE is accessing via a shared cell, the UE may be a CAG non-supporting UE accessing via a PLMN cell, or a CAG supporting UE accessing via a CAG cell. The network may apply different QoS to CAG non-supporting and CAG supporting UEs. For example, in a shared cell situation, the network may provide a higher quality of service (or better QoS) to CAG supporting UEs than to CAG non-supporting UEs.

[0296] During Rel-18, SA2 worked on standard specifications for CAGs with specific time and / or location conditions (i.e., validity conditions) to provide localized services via NPN at specific times and / or locations. Through this, if the validity condition for a specific CAG regarding time and / or location is satisfied, it can be included in the Allowed CAG list for UEs; however, if the condition is not satisfied, the CAG is no longer valid and cannot be included in the Allowed CAG list.

[0297] According to the WID regarding Rel-19 NR Femto, NR Femto must be provided even through CAGs with validity conditions. Therefore, a situation may arise where a UE accessing a Shared cell passes through CAG access control to receive high-quality service (i.e., better QoS), but some CAGs become invalid due to validity conditions. In this case, the network must be able to provide a relatively lower-quality service (or lower QoS) through the PLMN cell, in accordance with the validity conditions, while continuing to provide good QoS to the UE through the CAG cell. Conversely, if some CAGs become valid again due to validity conditions, the network must be able to provide better QoS to the UE again through the CAG cell.

[0298] During the process of a UE moving to a target NR Femto via Xn-based Handover, the target NR Femto cannot determine whether the UE may receive services through a PLMN cell when the target cell is a shared cell. Therefore, a method to resolve this may be necessary.

[0299] In this disclosure, NR Femto provides information regarding a cell accessed by a UE (e.g., a Cell CAG list, a cell sharing indicator, etc.) to an access mobility management node (e.g., AMF), and based on this information, the access mobility management node performs access control for the UE. Additionally, the access mobility management node can determine whether to continue providing the UE with a low-quality service by checking the validity condition for a specific CAG, if the specific CAG becomes invalid. The access mobility management node also provides information regarding whether to continue providing the UE with a low-quality service. Finally, based on the information received from the access mobility management node, NR Femto provides a method to appropriately select a target cell during the handover process for the UE or to determine the quality of service to be provided in the target cell.

[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 validity condition for CAG 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. 10 illustrates an example of a method to which the implementation of the present specification is applied.

[0308] In particular, FIG. 10 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 S1001, the access mobility management node may perform the step of receiving information related to the cell to which the UE (User Equipment) connects from the base station.

[0310] For example, information related to the cell to which the UE connects may include at least one of the UE's support capability information, a list of CAGs supported by the cell, or an indicator of whether the cell is shared.

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

[0312] In step S1002, the access mobility management node can perform access control of the UE based on the information and the UE's subscription data.

[0313] In step S1003, the access mobility management node can transmit information of the CAG associated with the validity condition based on access control to the base station.

[0314] For example, the information of a CAG associated with the above validity condition may include at least one of a list of authorized CAGs or PLMN cell handling information based on the above validity condition.

[0315] For example, PLMN cell handling information may be referred to as a PLMN cell handling indicator, a PLMN cell handling flag, or a PLMN cell indicator.

[0316] For example, the above-mentioned authorized CAG list may include one or more CAG IDs that satisfy a time validity condition or a location validity condition among the above validity conditions.

[0317] For example, the above-mentioned authorized CAG list may not include the value or content of the above-mentioned validity condition.

[0318] For example, based on the fact that the PLMN cell handling information is false and the cell that the UE connects to is a shared cell, the cell that the UE connects to may be considered a CAG cell.

[0319] Based on the fact that the above PLMN cell handling information is true and the cell that the UE connects to is a shared cell, the cell that the UE connects to can be considered a PLMN cell.

[0320] For example, the PLMN cell handling information may be true based on at least one of the following: (i) the CAG ID supported by the shared cell is not included in the authorized CAG list; (ii) the CAG ID supported by the shared cell does not satisfy the validity condition so that the UE cannot access the CAG cell; (iii) the UE lacks the ability to support CAG; or (iv) there is no authorized CAG list for the UE.

[0321] For example, the PLMN cell handling information may be false based on (i) the cell that the UE connects to is a shared cell, and (ii) there is a matching CAG ID in the authorized CAG list and the CAG list supported by the shared cell.

[0322] In step S1004, the access movement management node can determine the validity conditions associated with the CAG.

[0323] In step S1005, the access movement management node can change the validity status of the CAG based on the result of determining the validity condition.

[0324] For example, (i) when the validity conditions for one or more CAGs included in the above authorized CAG list are changed from a satisfied state to an unsatisfied state, and (ii) when the UE's authorized CAG list is updated, the validity status of the CAG can be changed to an invalid state.

[0325] For example, (i) when the validity conditions for one or more CAGs included in the above authorized CAG list are changed from an unmet state to a met state, and (ii) when the UE's authorized CAG list is updated, the validity state of the CAG can be changed to a valid state.

[0326] In step S1006, the access mobility management node can transmit information related to the change in the effective status of the CAG to the base station.

[0327] For example, a supported shared cell or closed cell from the authorized CAG list can be selected as the target cell in the handover.

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

[0329] In particular, FIG. 11 shows an example of a method performed by a base station in a wireless communication system. For example, the base station may be an NR Femto.

[0330] In step S1101, the base station can transmit information related to the cell to which the UE (User Equipment) connects to the access mobility management node.

[0331] For example, information related to the cell to which the UE connects may include at least one of the UE's support capability information, a list of CAGs supported by the cell, or an indicator of whether the cell is shared.

[0332] In step S1102, the base station can receive information of a Closed Access Group (CAG) associated with a validity condition based on the fact that access control of the UE is performed based on the above information and the subscription data of the UE.

[0333] For example, the information of a CAG associated with the above validity condition may include at least one of a list of authorized CAGs or PLMN cell handling information based on the above validity condition.

[0334] For example, the above-mentioned authorized CAG list may include one or more CAG IDs that satisfy a time validity condition or a location validity condition among the above validity conditions.

[0335] For example, the above-mentioned authorized CAG list may not include the value or content of the above-mentioned validity condition.

[0336] For example, based on the fact that the PLMN cell handling information is false and the cell that the UE connects to is a shared cell, the cell that the UE connects to may be considered a CAG cell.

[0337] Based on the fact that the above PLMN cell handling information is true and the cell that the UE connects to is a shared cell, the cell that the UE connects to can be considered a PLMN cell.

[0338] For example, the PLMN cell handling information may be true based on at least one of the following: (i) the CAG ID supported by the shared cell is not included in the authorized CAG list; (ii) the CAG ID supported by the shared cell does not satisfy the validity condition so that the UE cannot access the CAG cell; (iii) the UE lacks the ability to support CAG; or (iv) there is no authorized CAG list for the UE.

[0339] In step S1103, the base station can receive information related to a change in the effective status of the CAG from the access mobility management node.

[0340] For example, (i) when the validity conditions for one or more CAGs included in the above authorized CAG list are changed from a satisfied state to an unsatisfied state, and (ii) when the UE's authorized CAG list is updated, the validity status of the CAG can be changed to an invalid state.

[0341] For example, (i) when the validity conditions for one or more CAGs included in the above authorized CAG list are changed from an unmet state to a met state, and (ii) when the UE's authorized CAG list is updated, the validity state of the CAG can be changed to a valid state.

[0342] The above base station may be implemented by the second wireless device (200) described in FIG. 2. The base station includes one or more memories that can be connected to operate with one or more processors, and the one or more memories may store instructions that perform the operation described in FIG. 11 based on execution by the one or more processors.

[0343] FIGS. 12 and FIGS. 13 illustrate examples of CAG support procedures considering validity conditions to which the implementation of the present specification applies.

[0344] FIGS. 12 and 13 present a method for providing services differently by considering the UE's CAG capability, the UE's subscription data, and the list of CAG IDs supported in the serving cell in a situation where the AMF can determine that a specific CAG within the Allowed CAG list for the UE is no longer valid according to a validity condition.

[0345] In this specification, NG-RAN#1 and NG-RAN#2 may be NR Femto or gNB. In FIGS. 12 and 13, NG-RAN#1 is assumed to be NR Femto#1 and will be described later.

[0346] First, Figure 12 will be explained.

[0347] 0a., 0b. To create an NG interface between each NG-RAN and AMF, the NG-RAN may initiate an NG Setup procedure with the AMF (S1201, S1202).

[0348] In addition, NG-RANs can start an NG Setup procedure to create an Xn interface.

[0349] If NG-RAN#1 and / or NG-RAN#2 is an NR Femto, information related to the cell shared by PLMN and PNI-NPN (i.e., Shared cell by PLMN and PNI-NPN) (e.g., cell ID, CAG ID, PLMN ID, etc.) can be transmitted to the other party.

[0350] 1. A UE may attempt to register with the network by sending a Registration Request message to the AMF via NR Femto#1 (i.e., NG-RAN #1). At this time, if the UE has the capability to verify the capability for the CAG and / or the validity condition for the CAG, it may notify the AMF of this fact via the UE 5GMM Core Network CapabilityIE within the Registration Request message (S1203).

[0351] When a UE accesses a shared cell of NR Femto #1, NR Femto #1 notifies the AMF via an INITIAL UE MESSAGE message that the UE has accessed a shared cell (i.e., the Femto shared cell indication), along with the list of CAG IDs supported by the UE's serving cell (i.e., Cell CAG list). A shared cell may be recognized as a closed cell (i.e., a CAG cell) to a CAG-supporting UE, and as an open cell (i.e., a PLMN cell) to a CAG-non-supporting UE.

[0352] 2. The AMF may send an initial context setup request to NG-RAN#1 (S1204). The AMF may decide whether to permit the registration request for said UE by considering UE 5GMM Core Network Capability information, UE subscription data, Cell CAG list, cell sharing indicator (Femto shared cell indicator), etc. (i.e., perform access control considering CAG). If it is decided to accept it, it may proceed with a request to create a UE context to NR Femto#1 using an initial context setup request message. In addition, the AMF also generates a Registration Accept message to be delivered to the terminal and delivers it to NR Femto#1 using the initial context setup request message. AMF can pass the following Allowed CAG list contents to NR Femto#1, including the Mobility Restriction List component contained in the Initial Context Setup Request message.

[0353] a) CAG ID(s) unrelated to the validity condition

[0354] b) If a time validity condition exists and is satisfied, the CAG ID(s) related to that validity condition (→ Details regarding the time validity condition are not transmitted to NR Femto#1.)

[0355] For example, if a time validity condition exists and information related to the current UE's time satisfies the time validity condition, the AMF may include the corresponding CAG ID in the authorized CAG list.

[0356] c) If a location validity condition exists and is satisfied, the CAG ID(s) related to that validity condition (→ The details regarding the location validity condition are not passed to NR Femto#1.)

[0357] For example, if a location validity condition exists and the current UE's location satisfies the location validity condition, the AMF may include the corresponding CAG ID in the authorized CAG list.

[0358] If the AMF accepts the UE's network registration request, it may notify NR Femto#1 by including the Allowed CAG list and / or PLMN cell handling indicators (which may refer to information allowing the Shared cell to provide services to terminals that are not originally serviced by the CAG cell, such as UEs that cannot connect to the CAG cell because they are not included in the Allowed CAG list or do not satisfy the validity condition, or UEs that cannot connect to the CAG because they lack CAG capability) in the Initial Context Setup Request message. In this case, the Allowed CAG list and PLMN cell handling indicators may be configured as follows.

[0359] (A) When the UE accesses an open cell (i.e., a PLMN cell) (i.e., when NR Femto#1 does not include the Cell CAG list and the cell sharing indicator (Femto shared cell indicator) in the INITIAL UE MESSAGE message):

[0360] 1) PLMN cell handling indicator set to True

[0361] 2) If the Allowed CAG list is stored in the UE's subscription data, it is transmitted to NR Femto, and if the Allowed CAG list information is not in the UE's subscription data, it may be omitted.

[0362] (B) When the UE accessed through a Closed cell (i.e., a CAG cell) (i.e., when NR Femto#1 included only the Cell CAG list in the INITIAL UE MESSAGE message):

[0363] 1) PLMN cell handling indicator set to False

[0364] 2) Allowed CAG list in UE's subscription data

[0365] (C) When the UE accessed via a shared cell (i.e., when NR Femto#1 includes both the Cell CAG list and the cell sharing indicator (Femto shared cell indicator) in the INITIAL UE MESSAGE message):

[0366] (1) If an Allowed CAG list is stored in the UE's subscription data and there is one or more matching CAG IDs between that information and the Cell CAG list (i.e., if the CAG supporting UE has passed CAG access control):

[0367] 1) PLMN cell handling indicator set to False

[0368] 2) Allowed CAG list in UE's subscription data

[0369] (2) If the Allowed CAG list is stored in the UE's subscription data but there is no matching CAG ID between that information and the Cell CAG list (i.e., failed to pass CAG access control for a CAG-supporting UE or a CAG-non-supporting UE):

[0370] 1) PLMN cell handling indicator set to True

[0371] 2) Allowed CAG list in UE's subscription data

[0372] (3) If the Allowed CAG list is not stored in the UE's subscription data (i.e., for a CAG non-supporting UE):

[0373] PLMN cell handling indicator set to True

[0374] For example, when there is no matching CAG ID between the allowed CAG list in the subscription data of a UE accessed through a shared cell and the Cell CAG List sent by NR Femto#1, the AMF does not reject the registration request for said UE, but accepts it and considers that said UE is being serviced through a PLMN cell rather than a CAG cell, and can provide service through the PLMN cell.

[0375] For example, among CAG-supporting UEs accessed through a shared cell, a higher QoS may be provided to those that have passed CAG access control, while CAG-supporting UEs that have not passed it may be treated the same as or slightly better than CAG-non-supporting UEs accessed through the shared cell (e.g., lower QoS). Finally, CAG-non-supporting UEs accessed through the shared cell may be provided with the lowest treatment (e.g., lowest QoS).

[0376] If the AMF sets the PLMN cell handling indicator to True, it may be informing NR Femto#1 to consider the UE as being serviced through a PLMN cell. Conversely, if the AMF sets the PLMN cell handling indicator to False, it may be informing NR Femto#1 to consider the UE as being serviced through a CAG cell.

[0377] 3. NG-RAN #1 can accept registration from the UE (S1205). NR Femto #1 can create a UE context in response to the request from the AMF and deliver the Registration Accept message received from the AMF to the terminal.

[0378] If a PLMN cell handling indicator set to True is transmitted in Step 2, NR Femto#1 can know that the AMF has decided to continue servicing the UE even though the UE failed to pass CAG access control, and the UE can be considered to be serviced via a PLMN cell. If NR Femto#1 receives a PLMN cell handling indicator set to False, the UE can be considered to be serviced via a CAG cell.

[0379] NR Femto#1 can store PLMN cell handling indicators and / or Allowed CAG list received from AMF in the UE context.

[0380] 4. The remaining steps of the Registration procedure in Figure 4.2.2.2.2-1 in TS 23.502 can be executed (S1206).

[0381] 5. The AMF can continuously check the validity condition of individual CAGs included in the UE’s Allowed CAG list and determine whether the CAG is valid (S1207).

[0382] (CASE A) If a specific CAG is no longer valid (i.e., the validity condition for the CAG is not met) or if the UE's subscriber information is updated (i.e., the UE's Allowed CAG list is updated), it may be determined that the UE is not receiving service from the relevant CAG cell and a decision may be made to release the NAS connection with the UE. Alternatively, it may be determined that the UE is accessing the service through a PLMN cell rather than a CAG cell and a decision may be made to continue providing service.

[0383] (CASE B) If a specific invalid CAG satisfies the validity condition again, it can be determined that the CAG has changed to a valid state and therefore the UE can receive service again in that CAG cell. Alternatively, it can be determined that the UE can receive service again in that CAG cell due to a change in subscriber information. If service is currently being provided on the assumption that the UE is accessing through a PLMN cell, it can be decided to re-assign the UE accessing through a CAG cell and provide service accordingly.

[0384] Additionally, the AMF may continue to check the validity conditions for individual CAGs included in the UE's Allowed CAG list and transmit an updated Allowed CAG list to NR Femto#1 whenever the validity status changes. That is, the AMF may continue to check the validity conditions for individual CAGs included in the terminal's Allowed CAG list and determine whether the CAG is valid. If a specific CAG is no longer valid (i.e., the validity condition for that CAG is not met) or if a specific invalid CAG becomes valid again (i.e., the validity condition for that CAG is met again), the AMF may transmit a newly updated Allowed CAG list to NR Femto#1 in Step 6.

[0385] The following steps will be described later with reference to FIG. 13.

[0386] 6. The AMF may send a request to change the UE context to NG-RAN #1 (S1301). In CASE A, the AMF may transmit a PLMN cell handling indicator set to True to NR Femto #1 via a UE CONTEXT MODIFICATION REQUEST message or a separate NGAP message. If necessary, the AMF may also include information to update the Allowed CAG list. In this case, NR Femto #1 can recognize that it is CASE A. Additionally, during the subsequent handover process for the above UE, if the UE has an Allowed CAG list (the Allowed CAG list received in Step 2 or the updated Allowed CAG list if one was updated in Step 6), a Shared or Closed cell capable of supporting it may be given priority consideration as the Target cell. If this is not possible, a Shared cell may be considered as a PLMN cell and selected as the Target cell. If the Allowed CAG list was not received in Step 6, an Open or Shared cell may be given priority consideration as the Target cell during the Handover process.

[0387] If CASE B is determined, the AMF may transmit the PLMN cell handling indicator set to False to NR Femto#1 via the UE CONTEXT MODIFCATION REQUEST message or a separate NGAP message. If necessary, the AMF may also include information for updating the Allowed CAG list. NR Femto#1 can recognize that the situation is CASE B. When considering a handover to the above UE in the future, only Shared or Closed cells capable of supporting the UE's Allowed CAG list (the Allowed CAG list received in Step 2 or the updated Allowed CAG list if one exists in Step 6) may be considered as Target cells.

[0388] NR Femto#1 can update the Allowed CAG list and / or PLMN cell handling indicators stored in the UE context with the newly received values ​​from AMF.

[0389] NOTE: AMF can send the newly updated Allowed CAG list to NR Femto#1 via Step 8 instead of Step 6.

[0390] 7. NR Femto#1 may change the context for the above UE according to the content received in step S1301 and then respond to AMF via a UE CONTEXT MODIFATION RESPONSE message or a new NGAP message (S1302).

[0391] 8a, 8b. The AMF may include the updated Allowed CAG list information in a UE Configuration Update Command message and transmit it to the corresponding UE. Subsequently, the AMF may receive a UE Configuration Update Complete message from the UE (S1303, S1304).

[0392] AMF may deliver the newly updated Allowed CAG list to the UE through the UE Configuration Update procedure only if the following two conditions are satisfied.

[0393] (1) When the UE does not have the capability to verify the validity condition of the CAG, but the subscription data for the UE contains a CAG with a validity condition

[0394] (2) When the validity of a specific CAG changes according to the Validity condition in Step 5 (when an invalid CAG becomes a valid CAG or a valid CAG becomes an invalid CAG)

[0395] At this time, the AMF can include the updated Allowed CAG list information in the UE Configuration Update Command message and deliver it to the corresponding UE as follows.

[0396] 1) CAG ID(s) unrelated to the validation condition

[0397] 2) If a time validity condition exists and is satisfied, the CAG ID(s) related to that validity condition (→ Details regarding the time validity condition may not be conveyed to the UE.)

[0398] 3) If a location validity condition exists, the CAG ID(s) related to that validity condition (→ Details regarding the location validity condition may not be conveyed to the UE.)

[0399] If the updated Allowed CAG list is not delivered to NR Femto#1 in Step 6, AMF may deliver the updated Allowed CAG list contents to NR Femto#1 by including them in the Mobility Restriction List IE contained in the NGAP DOWNLINK NAS TRANSPORT message containing the UE Configuration Update Command message or in a separate NGAP message.

[0400] 1) CAG ID(s) unrelated to the validation condition

[0401] 2) If a time validity condition exists and is satisfied, the CAG ID(s) related to that validity condition (→ Details regarding the time validity condition may not be conveyed to NR Femto#1.)

[0402] 3) If a location validity condition exists, the CAG ID(s) related to that validity condition (→ Details regarding the location validity condition may not be conveyed to NR Femto#1.)

[0403] 9a, 9b. NR Femto #1 decides to hand over the UE based on the measurement results sent by the UE (S1305, S1306). In the process of determining the Target cell, NR Femto #1 may refer to the PLMN cell handling indicator and / or Allowed CAG list information currently stored in NR Femto #1. For example, for a UE in which a PLMN cell handling indicator set to True is stored in the UE context, NR Femto #1 prioritizes a Closed cell or Shared cell that can support the Allowed CAG list if it has one, and if it cannot, it may consider a Shared cell that cannot support the Allowed CAG list (i.e., considered a PLMN cell by the UE) as the Target cell. If NR Femto #1 does not have an Allowed CAG list, it may prioritize an Open cell or Shared cell.

[0404] For UEs where the PLMN cell handling indicator is set to False, NR Femto#1 can consider only Closed cells or Shared cells that support the Allowed CAG list as Target cells.

[0405] NR Femto #1 may know whether the target cell is a shared cell through the Xn Setup procedure of Step 0, but it is also possible for NR Femto #1 to determine the target cell to serve the UE without such information. Additionally, if NG-RAN #2, which receives a Handover request for a UE from NR Femto #1, is NR Femto, it may consider whether the target cell is a shared cell during the process of deciding whether to accept the handover request. Furthermore, if the target cell is a shared cell, NR Femto #1 may include the PLMN cell handling indicator received from AMF in the HANDOVER REQUEST message so that NG-RAN #2 can determine, through CAG access control, whether to provide the UE with high-quality service (or high QoS) via the CAG cell or low-quality service (or low QoS) via the PLMN cell.

[0406] This specification may have various effects.

[0407] For example, AMF may provide a lower level of service than before without immediately disconnecting the connection to the UE even if a specific CAG becomes invalid due to a validity condition. Conversely, if a specific CAG becomes valid due to a validity condition, it may provide a higher level of service to the UE.

[0408] More specifically, even if the validity of a CAG is lost, the network can maintain service continuity by switching the terminal to be serviced via a PLMN cell. This allows terminal users to continue using communication services without interruption, even when transitioning from CAG-based enhanced service quality to standard PLMN service quality. Conversely, if a specific CAG becomes valid again based on validity conditions, the network can improve the level of service provided to that terminal. In other words, as the validity of the CAG is restored, a terminal that previously received standard service via a PLMN cell can automatically receive higher QoS, enabling dynamic service quality management.

[0409] For example, even if the cell cannot continuously service the UE due to reasons such as radio quality, when handing the terminal over to another nearby cell, even the lowest level of service can be provided continuously without interruption.

[0410] For example, since the target base station can accurately identify information regarding the terminal's available access mode and service level during the handover process, service continuity can be guaranteed by applying appropriate access control and QoS policies even when the target cell is a hybrid cell.

[0411] For example, through these improved mechanisms, networks can perform more flexible and efficient resource management, and terminal users can receive stable and continuous communication services despite various changes in conditions. In addition, operators can effectively implement differentiated service policies through dynamic access control based on validity conditions, which can contribute to supporting various business models and service scenarios.

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

[0413] 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 information related to the cell to which the UE (User Equipment) connects from a base station; A step of performing access control of the UE based on the above information and the subscription data of the UE; A step of transmitting information of a Closed Access Group (CAG) associated with a validity condition based on the above access control to the base station; A step of determining the validity condition associated with the above CAG; A step of changing the valid state of the CAG according to the result of determining the above validity condition; A method comprising the step of transmitting information related to a change in the effective state of the CAG to the base station.

2. The method of claim 1, wherein the information related to the cell to which the UE connects includes at least one of the UE's support capability information, a CAG list supported by the cell, or a cell sharing indicator.

3. The method of claim 1, wherein the information of the CAG associated with the validity condition comprises at least one of a list of authorized CAGs based on the validity condition or PLMN cell handling information.

4. The method of claim 3, wherein the authorized CAG list includes one or more CAG IDs satisfying a time validity condition or a location validity condition among the validity conditions.

5. In claim 3, the method wherein the authorized CAG list does not include the value or content of the validity condition.

6. In Paragraph 3, based on the fact that the PLMN cell handling information is false and the cell connected by the UE is a shared cell, the cell connected by the UE is considered to be a CAG cell, and A method in which the cell connected by the UE is considered a PLMN cell based on the fact that the above PLMN cell handling information is true and the cell connected by the UE is a shared cell.

7. A method in which the PLMN cell handling information is true based on at least one of the following: (i) the CAG ID supported by the shared cell is not included in the authorized CAG list; (ii) the CAG ID supported by the shared cell does not satisfy the validity condition so that the UE cannot access the CAG cell; (iii) the UE lacks the ability to support CAG; or (iv) there is no authorized CAG list for the UE.

8. A method according to claim 6 in which the PLMN cell handling information is false, based on (i) the cell to which the UE connects is a shared cell, and (ii) there is a matching CAG ID in the authorized CAG list and the CAG list supported by the shared cell.

9. A method according to claim 3, wherein (i) the validity condition for one or more CAGs included in the authorized CAG list is changed from a satisfied state to a non-satisfied state, and (ii) the valid state of the CAG is changed to an invalid state when the authorized CAG list of the UE is updated.

10. A method of claim 3, wherein (i) the validity condition for one or more CAGs included in the authorized CAG list is changed from a state where it is not satisfied to a state where it is satisfied, and (ii) the validity status of the CAG is changed to a valid state when the authorized CAG list of the UE is updated.

11. A method in which a shared cell or a closed cell supported in the above-mentioned authorized CAG list is selected as a target cell in a handover.

12. 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 information related to the cell to which the UE (User Equipment) connects from a base station; A step of performing access control of the UE based on the above information and the subscription data of the UE; A step of transmitting information of a CAG associated with a validity condition to the base station based on the above access control; A step of determining the validity condition associated with the above CAG; A step of changing the valid state of the CAG according to the result of determining the above validity condition; An access mobility management node comprising the step of transmitting information related to a change in the effective state of the CAG to the base station.

13. In a method performed by a base station, A step of transmitting information related to the cell connected by the UE (User Equipment) to the access mobility management node; A step of receiving information of a Closed Access Group (CAG) associated with a validity condition based on the above information and the subscription data of the UE, wherein access control of the UE is performed based on the above information; The method includes the step of receiving information related to a change in the validity status of the above CAG from the access mobility management node; A method for changing the above valid state based on the result of judging the above validity condition.

14. In a base station, the above base station is: 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 transmitting information related to the cell connected by the UE (User Equipment) to the access mobility management node; A step of receiving information of a Closed Access Group (CAG) associated with a validity condition based on the above information and the subscription data of the UE, wherein access control of the UE is performed based on the above information; The method includes the step of receiving information related to a change in the validity status of the above CAG from the access mobility management node; A base station characterized by the change in the above-mentioned valid state being based on the result of determining the above-mentioned valid condition.

Images