Joint learning

Abstract

One disclosure of the present disclosure provides a method for an AMF to perform communication. The method may comprise the steps of: receiving a registration request message including core network capability information from a UE; evaluating validity conditions that allow entries included in the CAG list; and determining that the allowed CAG list needs to be updated for the NG-RAN.

Description

Technical Field

[0001] This specification relates to radio communications. Background Art

[0002] The Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for high-speed packet communications. Many proposals have been made for LTE, including those aimed at reducing user and provider costs, improving service quality, and expanding and increasing coverage and system capacity. 3GPP LTE mandates lower cost per bit, increased service availability, flexible use of frequency bands, a simple architecture, open interfaces, and appropriate power consumption in terminals as high-level requirements.

[0003] Work has begun within the International Telecommunication Union (ITU) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary for successful standardization of the new RAT to meet both immediate market demands and the longer-term requirements set forth by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to use any frequency band up to at least 130 GHz, which will be available for wireless communications even in the distant future.

[0004] NR aims to be a single technology framework that addresses all use cases, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), etc. NR should be inherently forward-compatible.

[0005] The AMF may need to update the allowed closed access group (CAG) list for the terminal. In the past, the update process caused service interruption and inefficient update for the terminal. Summary of the Invention

[0006] Technical Solution

[0007] In one aspect, a method for performing communication with an AMF is provided. The method may include: receiving a registration request message including core network capability information from a UE; evaluating a validity condition of an entry included in a list of allowed CAGs; and determining that the list of allowed CAGs needs to be updated for NG-RAN.

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

[0009] In one aspect, a method for performing communication by a UE is provided. The method may include: sending a registration request message including core network capability information to an AMF; and receiving a registration message including a list of allowed CAGs from the AMF.

[0010] In another aspect, a device for implementing the above method is provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 An example of a communication system to which an implementation of the present disclosure is applied is shown.

[0012] Figure 2 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0013] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0014] Figure 4 An example of a 5G system architecture to which implementations of the present disclosure are applied is shown.

[0015] Figure 5 and Figure 6 An example of a registration process to which an implementation of the present disclosure is applied is shown.

[0016] Figure 7a and Figure 7b A first example of a process for checking a validity condition according to one embodiment of the present disclosure is illustrated.

[0017] Figure 8a and Figure 8b A second example of a process for checking a validity condition according to one embodiment of the present disclosure is illustrated.

[0018] Figure 9 An example of a UE configuration update procedure according to one embodiment of the present disclosure is illustrated.

[0019] Figure 10 An example of a process performed according to one embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0020] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio 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 using radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-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-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).

[0021] For ease of description, implementations of the present disclosure will be primarily described with respect to a 3GPP-based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of the present disclosure that are not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems.

[0022] For terms and techniques not specifically described among the terms and techniques used in the present disclosure, reference may be made to wireless communication standard documents published prior to the present disclosure.

[0023] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." In other words, "A or B" in the present disclosure may be interpreted as "A and / or B." For example, "A, B, or C" in the present disclosure may mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0024] In the present disclosure, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0025] In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and / or B” in the present disclosure may be interpreted as being the same as “at least one of A and B”.

[0026] In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” In addition, “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.”

[0027] In addition, the brackets used in this disclosure may mean "for example". Specifically, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, the "control information" in this disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when it is shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0028] The technical features described separately in one drawing of the present disclosure can be implemented separately or simultaneously.

[0029] Although not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0030] Hereinafter, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise specified, the same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0031] Figure 1 An example of a communication system to which an implementation of the present disclosure is applied is shown.

[0032] Figure 1 The 5G usage scenarios shown in are only exemplary, and the technical features of the present disclosure can be applied to Figure 1 Other 5G usage scenarios not shown.

[0033] The three main requirement categories for 5G include (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low-latency communication (URLLC) category.

[0034] Reference Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Figure 1 A 5G network is shown as an example of the network of the communication system 1 , but implementations of the present disclosure are not limited to the 5G system and may be applied to future communication systems other than the 5G system.

[0035] The BS 200 and the network 300 may be implemented as wireless devices, and certain wireless devices may operate as BS / network nodes relative to other wireless devices.

[0036] Wireless devices 100a to 100f represent devices that communicate using a radio access technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. Wireless devices may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of communicating between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, digital signage, a vehicle, a robot, and the like. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0037] In the present disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, an unmanned aerial vehicle (UAV), an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or financial device), a security device, a weather / environmental device, a device related to 5G services, or a device related to the Fourth Industrial Revolution.

[0038] Wireless devices 100a to 100f can connect to a network 300 via a BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to an AI server 400 via the network 300. The network 300 can be configured using a 3G network, a 4G network (e.g., LTE), a 5G network (e.g., NR), and a beyond 5G network. Although wireless devices 100a to 100f can communicate with each other via the BS 200 / network 300, wireless devices 100a to 100f can perform direct communication (e.g., sidelink communication) with each other without going through the BS 200 / network 300. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0039] Wireless communications / connections 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BSs 200. Herein, wireless communications / connections may be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, and inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)). Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f may transmit / receive radio signals to / from each other via wireless communications / connections 150a, 150b, and 150c. For example, wireless communications / connections 150a, 150b, and 150c may transmit / receive signals via various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of the resource allocation process can be performed based on the various proposals of the present disclosure.

[0040] NR supports multiple parameter sets (and / or multiple subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15kHz, wide areas can be supported in traditional cellular bands, and if the SCS is 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0041] The NR frequency band can be defined as two types of frequency ranges, namely, frequency range 1 (FR1) and frequency range 2 (FR2). The numerical value of the frequency range can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be shown in Table 1 below. For ease of explanation, in the frequency range used in the NR system, FR1 can mean "below 6 GHz range", FR2 can mean "above 6 GHz range", and can be referred to as millimeter wave (mmW).

[0042] [Table 1]

[0043] Frequency range name Corresponding frequency range Subcarrier spacing FR1 450MHz-6000MHz 15kHz, 30kHz, 60kHz FR2 24250MHz-52600MHz 60kHz, 120kHz, 240kHz

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

[0045] [Table 2]

[0046] Frequency range name Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15kHz, 30kHz, 60kHz FR2 24250MHz-52600MHz 60kHz, 120kHz, 240kHz

[0047] Here, the radio communication technology implemented in the wireless device in the present disclosure may include narrowband IoT (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of an LPWAN technology and may be referred to as various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine type communication and / or 7) LTE M, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device of the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and may not be limited to the above names. For example, ZigBee technology can generate a personal area network (PAN) associated with low-power / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to by various names.

[0048] Figure 2 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0049] exist Figure 2 , the first wireless device 100 and / or the second wireless device 200 may be implemented in various forms depending on the use case / service. For example, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 1 At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / components and / or modules.

[0050] The first wireless device 100 may include at least one transceiver (eg, transceiver 106 ), at least one processing chip (eg, processing chip 101 ), and / or one or more antennas 108 .

[0051] The processing chip 101 may include at least one processor (eg, processor 102 ) and at least one memory (eg, memory 104 ). Additionally and / or alternatively, the memory 104 may be located outside the processing chip 101 .

[0052] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104.

[0053] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store firmware and / or software code 105 that implements code, commands, and / or command sets that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, firmware and / or software code 105 may implement instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, firmware and / or software code 105 may control processor 102 to execute one or more protocols. For example, firmware and / or software code 105 may control processor 102 to execute one or more layers of a radio interface protocol.

[0054] In this document, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0055] The second wireless device 200 may include at least one transceiver (eg, transceiver 206 ), at least one processing chip (eg, processing chip 201 ), and / or one or more antennas 208 .

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

[0057] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204.

[0058] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store firmware and / or software code 205 that implements code, commands, and / or command sets that, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, firmware and / or software code 205 may implement instructions that, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, firmware and / or software code 205 may control processor 202 to execute one or more protocols. For example, firmware and / or software code 205 may control processor 202 to execute one or more layers of a radio interface protocol.

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

[0060] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure, and provide the generated signals to the one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure.

[0061] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. For example, one or more processors 102 and 202 may be configured by a group of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104 and 204 may be configured by random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPROM), flash memory, volatile memory, non-volatile memory, hard disk drive, register, buffer memory, computer-readable storage medium, and / or a combination thereof. The one or more memories 104 and 204 may be located inside and / or outside the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0062] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0063] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208. Additionally and / or alternatively, one or more transceivers 106 and 206 may include one or more antennas 108 and 208. One or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in the present disclosure through one or more antennas 108 and 208. In the present disclosure, one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

[0065] although Figure 2 Although not shown in the figures, the wireless devices 100 and 200 may also include additional components. The additional components 140 may be configured differently depending on the type of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a drive device, and a computing device. The additional components 140 may be coupled to one or more processors 102 and 202 via various technologies, such as wired or wireless connections.

[0066] In implementations of the present disclosure, a UE may operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). Within implementations of the present disclosure, a base station (BS) may operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for ease of description, it is primarily assumed that the first wireless device 100 acts as a UE and the second wireless device 200 acts as a base station (BS). For example, the processor 102 connected to, installed on, or activated in the first wireless device 100 may be adapted to perform UE operations according to implementations of the present disclosure, or to control the transceiver 106 to perform UE operations according to implementations of the present disclosure. The processor 202 connected to, installed on, or activated in the second wireless device 200 may be adapted to perform BS operations according to implementations of the present disclosure, or to control the transceiver 206 to perform BS operations according to implementations of the present disclosure.

[0067] In this disclosure, a BS is also referred to as a Node B (NB), an eNodeB (eNB), or a gNB.

[0068] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0069] Reference Figure 3 , UE 100 may correspond to Figure 2 The first wireless device 100 is configured to:

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

[0071] The processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The layers of the radio 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, a GPU, and a modem (modulator and demodulator). The processor 102 may be implemented in a manner such as by SNAPDRAGON MANUFACTURED TM series processors, Manufactured by EXYNOS TMseries processors, A series processors manufactured by Manufactured by HELIO TM series processors, ATOM manufactured TM Examples of processor 102 are found in the NVIDIA ...

[0072] The memory 104 is operably coupled to the processor 102 and stores various information used to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiment is implemented in software, the techniques described herein may be implemented with modules (e.g., processes, functions, etc.) that execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed in this disclosure. The modules may be stored in the memory 104 and executed by the processor 102. The memory 104 may be implemented within the processor 102 or external to the processor 102, in which case those memories may be communicatively coupled to the processor 102 via various means known in the art.

[0073] The transceiver 106 is operatively coupled to the processor 102 and transmits and / or receives radio signals. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry for processing radio frequency signals. The transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0074] The power management module 141 manages the power of the processor 102 and / or the transceiver 106. The battery 142 provides power to the power management module 141.

[0075] The display 143 outputs the results processed by the processor 102. The keyboard 144 receives input to be used by the processor 102. The keyboard 144 may be shown on the display 143.

[0076] The SIM card 145 is an integrated circuit designed to securely store an International Mobile Subscriber Identity (IMSI) number and its associated keys, which are used to identify and authenticate subscribers on mobile telephony devices such as mobile phones and computers. It is also capable of storing contact information associated with many SIM cards.

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

[0078] Figure 4 An example of a 5G system architecture to which implementations of the present disclosure are applied is shown.

[0079] The 5G system (5GS) architecture includes the following network functions (NFs).

[0080] -Authentication Server Function (AUSF)

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

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

[0083] -Unstructured Data Storage Function (UDSF)

[0084] -Network Exposure Function (NEF)

[0085] -Intermediate NEF (I-NEF)

[0086] -Network Repository Function (NRF)

[0087] -Network Slice Selection Function (NSSF)

[0088] -Policy Control Function (PCF)

[0089] -Session Management Function (SMF)

[0090] -Unified Data Management (UDM)

[0091] -Unified Data Repository (UDR)

[0092] -User Plane Function (UPF)

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

[0094] -Application Function (AF)

[0095] -User Equipment (UE)

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

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

[0098] -Network Data Analysis Function (NWDAF)

[0099] -Billing function (CHF)

[0100] In addition, the following network functions can be considered.

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

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

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

[0104] Figure 4 Depicts the 5G system architecture in a non-roaming scenario, using reference points that show how the various network functions interact with each other.

[0105] exist Figure 4 In the figure, for the sake of clarity of the point-to-point diagram, UDSF, NEF and NRF are not depicted. However, all depicted network functions can interact with UDSF, UDR, NEF and NRF as needed.

[0106] For clarity, Figure 4 The UDR and its connections to other NFs (e.g., PCF) are not depicted in the figure. Figure 4 The NWDAF and its connections with other NFs (eg, PCF) are not depicted.

[0107] The 5G system architecture includes the following reference points:

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

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

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

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

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

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

[0114] The following reference points illustrate the interactions that exist between NF services in a NF.

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

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

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

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

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

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

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

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

[0123] -N15: Reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario.

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

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

[0126] In some cases, several NFs may need to be associated with each other to serve a UE.

[0127] A registration process is described. Please refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0128] Figure 5 and Figure 6 An example of a registration process to which an implementation of the present disclosure is applied is shown.

[0129] The UE needs to register with the network to obtain authorization to receive services, to enable mobility tracking and to achieve reachability. The UE initiates the registration procedure using one of the following registration types:

[0130] - Initial registration with 5GS; or

[0131] - Mobility Registration Update; or

[0132] - Periodic registration renewal; or

[0133] - Emergency registration.

[0134] Figure 5 and Figure 6 The general registration procedures in apply to all of these registration procedures, but periodic registration updates do not need to include all parameters used in other registration situations.

[0135] Figure 5 and Figure 6 The general registration procedure in is also used for the case where the UE registers in 3GPP access when it is already registered in non-3GPP access and vice versa. Registration in 3GPP access may require AMF changes when the UE is already registered in non-3GPP access scenario.

[0136] First, describe Figure 5 process.

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

[0138] The registration request message may include AN parameters. In the case of NG-RAN, the AN parameters include, for example, 5G SAE Temporary Mobile Subscriber Identity (5G-S-TMSI) or Globally Unique AMF ID (GUAMI), the selected Public Land Mobile Network (PLMN) ID (or PLMN ID and Network Identifier (NID)) and the requested Network Slice Selection Assistance Information (NSSAI). The AN parameters also include the establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter.

[0139] The Registration Request message may include a Registration Type. The Registration Type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates a registration procedure due to mobility or because the UE needs to update its capabilities or protocol parameters or requests a change in the set of network slices it is allowed to use), a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates a registration procedure due to expiration of the periodic registration update timer), or an emergency registration (i.e., the UE is in a restricted service state).

[0140] When the UE is performing an initial registration, the UE shall indicate its UE identity in the Registration Request message as follows, listed in descending order of preference:

[0141] i) if the UE has a valid EPS GUTI, the 5G Globally Unique Temporary Identifier (5G-GUTI) mapped from the Evolved Packet System (EPS) GUTI;

[0142] ii) the local 5G-GUTI assigned by the PLMN with which the UE is attempting to register, if available;

[0143] iii) the local 5G-GUTI assigned by the equivalent PLMN to the PLMN with which the UE is attempting to register, if available;

[0144] iv) Local 5G-GUTI assigned by any other PLMN, if available;

[0145] v) Otherwise, the UE shall include its Subscriber Suppression Identifier (SUCI) in the Registration Request message.

[0146] When a UE performing initial registration has both a valid EPS GUTI and a local 5G-GUTI, the UE shall also indicate the local 5G-GUTI as an additional GUTI. If more than one local 5G-GUTI is available, the UE shall select the 5G-GUTI in descending order of preference from items (ii)-(iv) in the above list.

[0147] When the UE is performing an initial registration with its local 5G-GUTI, the UE shall indicate the relevant GUAMI information in the AN parameters. When the UE is performing an initial registration with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.

[0148] For emergency registration, if the UE does not have a valid 5G-GUTI available, the SUCI shall be included; when the UE does not have a Subscriber Permanent Identifier (SUPI) and does not have a valid 5G-GUTI, the Permanent Equipment Identifier (PEI) shall be included. In other cases, the 5G-GUTI is included and it indicates the last serving AMF.

[0149] The Registration Request message may also include security parameters, PDU Session Status, etc. Security parameters are used for authentication and integrity protection. The PDU Session Status indicates the previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU Session Status indicates the established PDU session of the current PLMN in the UE.

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

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

[0152] If the UE is in the CM connected state, the (R)AN may forward the Registration Request message to the AMF based on the UE's N2 connection.

[0153] If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request message to an AMF in the (R)AN that has been configured to perform AMF selection.

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

[0155] The registration request message may include all information and / or part of the information included in the registration request message received from the UE described in step 1.

[0156] The Registration Request message may include N2 parameters. When using NG-RAN, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell identity related to the cell in which the UE is camped, and a UE Context Request indicating that a UE context including security information needs to be established at the NG-RAN. When using NG-RAN, the N2 parameters should also include the establishment cause.

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

[0158] (4) Step 4: If the UE’s 5G-GUTI is included in the Registration Request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation against the old AMF by including a complete Registration Request Non-Access Stratum (NAS) message to request the UE’s SUPI and UE context.

[0159] (5) Step 5: The old AMF may respond to the new AMF for the Namf_Communication_UEContextTransfer call by including the UE’s SUPI and UE context.

[0160] (6) Step 6: If the UE has neither provided SUCI nor retrieved SUCI from the old AMF, the Identity Request procedure may be initiated by sending an Identity Request message to the UE requesting SUCI via the new AMF.

[0161] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI by using the provisioned public key of the Home PLMN (HPLMN).

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

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

[0164] (10) Step 10: If the AMF has changed, the new AMF may notify the old AMF that the UE registration with the new AMF is complete by invoking the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, the registration will be rejected and the new AMF may invoke the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication cause code towards the old AMF. The old AMF may continue as if the UE Context Transfer service operation had never been received.

[0165] (11) Step 11: If the UE has not provided the PEI and has not retrieved it from the old AMF, the Identity Request procedure may be initiated by the new AMF sending an Identity Request message to the UE to retrieve the PEI. The PEI shall be transmitted encrypted unless the UE performs an emergency registration and cannot be authenticated.

[0166] (12) Step 12: Optionally, the new AMF may initiate an ME identity check by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0167] Now, the description in Figure 5 After the process Figure 6 process.

[0168] (13) Step 13: If step 14 below is to be performed, the new AMF may select a UDM based on the SUPI, and the UDM may then select a UDR instance.

[0169] (14) Step 14: The new AMF may register with the UDM.

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

[0171] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0172] (17) Step 17: The new AMF may send an update / release SM context message (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0173] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE Context Modification Request to the N3IWF / TNGF / W-AGF.

[0174] (19) Step 19: N3IWF / TNGF / W-AGF may send a UE Context Modification Response to the new AMF.

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

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

[0177] The new AMF sends a Registration Accept 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 RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the Registration Accept message for both registrations. If the 5G-GUTI is not included in the Registration Accept message, the UE shall use the 5G-GUTI assigned to the existing registration also for the new registration. If the new AMF assigns a new registration area, it shall send this registration area to the UE via the Registration Accept message. If the registration area is not included in the Registration Accept message, the UE shall consider the old registration area to be valid. Mobility restrictions are included in case mobility restrictions apply to the UE and the registration type is not an emergency registration. The new AMF indicates the established PDU session to the UE in the PDU Session Status. The UE locally removes any internal resources associated with the PDU session that was not marked as established in the received PDU Session Status. When a UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE shall locally remove any internal resources related to the PDU Sessions of the current PLMN that are not marked as established in the received PDU Session Status. If the PDU Session Status information is in the Registration Request message, the new AMF shall indicate the PDU Session Status to the UE.

[0178] The allowed NSSAI provided in the registration accept message is valid in the registration area and applies to all PLMNs whose tracking areas are included in the registration area. The mapping of allowed NSSAI is the mapping of each single network slice selection assistance information (S-NSSAI) of the allowed NSSAI to the HPLMN S-NSSAI. The mapping of configured NSSAI is the mapping of each S-NSSAI of the configured NSSAI for the serving PLMN to the HPLMN S-NSSAI.

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

[0180] (22) Step 22: The UE may send a Registration Complete message to the new AMF when it has successfully updated itself.

[0181] The UE may send a Registration Complete message to the new AMF to confirm whether a new 5G-GUTI is assigned.

[0182] (23) Step 23: For registration via 3GPP access, if the new AMF has not released the signaling connection, the new AMF may send RRC Inactive Assistance Information to the NG-RAN. For registration via non-3GPP access, if the UE is also in CM Connected state on 3GPP access, the new AMF may send RRC Inactive Assistance Information to the NG-RAN.

[0183] (24) Step 24: The new AMF may perform information update for the UDM.

[0184] (25) Step 25: The UE may perform network slice specific authentication and authorization procedures.

[0185] According to the prior art, there are problems such as the following examples.

[0186] For example, it is necessary to enable the UE to discover, select and access a non-public network (NPN) as a hosted network and receive localized services.

[0187] If the UE uses the subscription / credentials of the home network to access the hosted network, only two cases can be considered:

[0188] - If the home network is a PLMN, the hosted network can be a PNI-NPN or SNPN.

[0189] - If the home network is a SNPN, the hosted network can only be a standalone non-public network (SNPN).

[0190] If the UE accesses the hosted network using credentials other than the subscription / credentials from the UE's home network, the determination of the subscription used to access the hosted network before automatic network selection is implementation specific.

[0191] Examples of content used to access localization services include:

[0192] For manual selection, existing SIB information (eg, HRNN and / or application layer information) may be used without any regulatory impact.

[0193] For automatic selection, consider the following:

[0194] a. In the case of an SNPN as a hosted network, for automatic SNPN selection, the existing priority list of preferred SNPNs (and GINs) controlled by the voucher holder is extended with time and location validity information for each entry in the list. An entry can include only time validity, only location validity, or both. The location validity information can take the form of a geographic location and / or the TAI of the serving PLMN / SNPN.

[0195] NOTE: The location validity information is used to help the UE search for the location of the SNPN in the CH list and is not used for any enforcement.

[0196] b. For automatic cell reselection:

[0197] - In case of PNI-NPN with CAG, the allowed CAG list may include time validity information.

[0198] In the case of PNI-NPN using S-NSSAI, the SOR may include S-NSSAI information, or may use S-NSSAI validity information including time and location.

[0199] The following describes where and how the UE obtains information for accessing localized services.

[0200] The UE may obtain information for localized services from the home network or localized service provider in the application layer through a method outside the scope of 3GPP.

[0201] The following provides information for selecting a hosting network:

[0202] 1. Information for hosted network, selection and access can be pre-configured in the UE or dynamically provided by the home network (via VPLMN when roaming) using existing mechanisms.

[0203] 2. In the case of SNPN as the hosting network, a priority list of hosted network information can be dynamically provided via SoR:

[0204] i. The home network UDM may determine a priority list for updating the hosted network information to the UE using the SoR procedure. The following triggers may apply:

[0205] -UE location as part of the registration process.

[0206] - UE subscription data changes, eg provided via external parameters.

[0207] 3. In case of PNI-NPN as hosting network, dynamic provision of allowed CAG ID list reusing existing process

[0208] This section describes how to use localized service information in UE.

[0209] The following examples may apply.For the purposes of this disclosure, the terms "credential" and "certificate" may be used interchangeably.

[0210] 1. If the UE uses the home network credentials to access the hosted network:

[0211] a. When the terminal user intends to access the localized service and the validity conditions of the localized service are met, the UE initiates the hosted network selection using the hosted network selection information.

[0212] i. For SNPN as hosted network, the UE can switch between PLMN selection and hosted network selection for SNPN selection with the following differences:

[0213] - If the UE is configured with priority lists of preferred SNPNs and GINs controlled by the certificate holder, and these lists include entries with validity conditions and the validity condition of at least one of these entries is met, then the UE may select the relevant SNPN even if the subscribed SNPN (if any) is available (i.e., the hosted network may have a higher priority than the subscribed SNPN). How the UE switches among network selections depends on the UE's implementation.

[0214] ii. For a PNI-NPN that is a hosted network associated with a CAG ID, the UE considers an entry in the allowed CAG list valid only if (and if) it satisfies all conditions (if any) for that entry.

[0215] b. Automatic hosted network selection is controlled by the home network via the SoR procedure with SoR information, which includes certain authorization criteria, such as time. Based on the SoR information, the UE performs automatic hosted network selection:

[0216] i. For manual managed network selection, the UE presents the available localized service information it has received to the end user.

[0217] 2. If the UE needs to obtain a new set of credentials / subscription to access the hosted network:

[0218] A. It is up to the UE implementation to decide how to switch to a new subscription profile for accessing the hosted network.

[0219] 3. The UE determines whether the SNPN access mode is activated / deactivated using implementation-specific means or using the received localized serving / hosted network assistance information as input.

[0220] Describes the credentials used to access a managed network and how to obtain them.

[0221] Based on the evaluation, the following principles can be applied to the SNPN as a hosted network, as illustrated in the following example.

[0222] 1. The UE checks whether it can reuse the home network credentials to access the hosted network by performing the following operations:

[0223] a. If the UE uses the CH / user controlled priority list portion of the home network subscription profile, or if the UE uses hosted network related information (part of the localized service information) from the home network that indicates support for CH credentials, the UE determines that the home network credentials can be used to register with the selected hosted network.

[0224] 2. If the UE has default credentials and the UE determines that new credentials are needed for accessing the hosted network, the UE uses the default credentials for the onboarding mechanism with ON-SNPN as the hosted network, with the following enhancements:

[0225] a. In the case where the UE is pre-configured with PVS address information and the UE receives the PVS address information from the SMF during the PDU Session Setup Accept message, the UE may determine whether to apply or ignore the PVS address information provided by the SMF based on local configuration.

[0226] Based on the evaluation, for the case of PNI-NPN as a hosting network, the following principles can be recommended for standardization work:

[0227] 3. Only UEs equipped with a USIM configured with PLMN credentials can access the hosted network as a PNI-NPN. When the UE requests access to the hosted network, the home PLMN credentials are used during the authentication process.

[0228] Describes how to access localized services on a hosted network.

[0229] Based on the assessment, the following principles can be discussed:

[0230] 1. The validity conditions provided to the UE as part of the localized service information may be used to restrict the UE's access to the hosting network.

[0231] 2. Existing methods such as network slicing, prohibited area restrictions, service area restrictions, CAG, LADN, and URSP rules can also be used to restrict UE access, i.e., no additional normative work is required for access control in the managed network.

[0232] 3. To restrict access to the managed network to specific areas, the managed network operator can deploy and broadcast multiple managed network IDs in different areas based on localized service area validity. This is the SNPN ID for SNPNs and the CAG ID for PNI-NPNs. Each localized service is mapped to a specific managed network ID. If multiple localized service areas have the same permitted service area, they can be mapped to the same managed network ID. Managed networks also use validity conditions to restrict access.

[0233] Discussions can be held on how to provide localized service via NPN at specific times and / or locations.

[0234] There are problems such as the following example.

[0235] It is necessary to support UE to discover, select and access the NPN as the hosting network and receive localized services.

[0236] In order to provide localized services to the UE, the UE must be able to discover, select, and access a hosted network for localized services. The discovery mechanism can be based on providing appropriate information to the UE. For example, TS 22.261 V18.8.0, Sections 6.41.2.3, 6.41.2.4, and 6.41.2.5 define various requirements for discovering, selecting, and accessing a hosted network.

[0237] For the following solutions, the following assumptions can be considered:

[0238] - The UE may (but does not necessarily) have a previous subscription with the hosting network and / or localized service provider.

[0239] - Information for discovering a hosted network providing localized services may be provided to the UE via the hosted network, the UE's home network, the UE's serving network, or a localized service provider. This information allows the UE to discover, select, and access a hosted network providing localized services.

[0240] - Receipt and use of configurations provided by the localization service provider for discovery and access to the hosted network and localization services is subject to the policies of the home network operator and the agreement between the localization service provider and the hosted network operator, including taking into account prior service agreements with the localization service provider and the absence of prior subscriptions to the hosted network.

[0241] - If the UE is able to obtain service from both networks simultaneously, it may additionally select the hosted network.

[0242] - The selection of the hosted network may be done at the user's request (i.e. using manual selection), except that the UE may maintain PDU sessions established with the home network and preserve services provided by the home network on these PDU sessions while selecting the hosted network.

[0243] - Automatic selection of the hosting network needs to be allowed by the home network of the subscription / credentials used by the UE.

[0244] -Localization service agreement has been established.

[0245] This key question aims to address the following:

[0246] - Study what type of information needs to be exchanged between the hosting network and the localized service provider so that the UE can perform discovery, selection and connection to the hosting network and access the localized services provided via the hosted network.

[0247] Note: A hosting network can also serve as a service provider for localization services.

[0248] - Due to the nature of localized services and hosted networks (e.g., time and location constraints), what are the provisioning mechanisms and information required for the UE to discover, select and access a suitable hosted network for localized services, including information that enables the UE to be aware of services accessible via the hosted NPN.

[0249] - The process of discovering and selecting a hosted network and localized services provided by the hosted network for the UE to receive localized services. Both automatic selection and manual selection by the end user are applicable.

[0250] - How a UE registered in a network (PLMN or NPN) can discover a suitable hosted network and localized services provided by the hosted network when such hosted networks and / or localized services become available.

[0251] - How to ensure that the UE accesses the localized service according to the conditions of time and place that allow the UE to access the localized service.

[0252] - How to provide the UE with credentials for accessing selected localized services provided via the hosted network (if required).

[0253] -Mechanisms for authorizing UE to access the hosted network.

[0254] One of the above-mentioned agendas involves studying how to convey information to terminals about the time or location where the hosting network providing localized services is valid, ie, validity conditions.

[0255] In addition, it can be discussed how to provide services via VMR (ie MBSR) at specific times and / or locations. This is discussed in TR 23.700-05.

[0256] It is necessary to control the UE to access the 5GS via the mobile base station relay.

[0257] Based on the requirements of TS 22.261 V18.8.0, it should be possible to support the provision and configuration mechanism to control the UE's selection and access to the mobile base station relay (ie, IAB node) based on geographical or time restrictions.

[0258] These requirements need to be addressed. Potential solutions should allow fine-grained and efficient control of idle mode or connected mode UE access to MBSR, for example, when the UE is connected or mobile. In particular, the following aspects should be addressed:

[0259] - Whether and how to manage access control for UE access to IAB nodes;

[0260] - Whether and how UE access to IAB nodes is managed (e.g., allowed / restricted) for specific geographic locations, time windows, or other conditions / criteria;

[0261] - Whether and how to improve control over new UEs.

[0262] If the validity conditions for the time and / or location of a particular CAG are met, it can be included in the terminal's allowed CAG list. If the conditions are not met, the CAG is no longer valid and cannot be included in the allowed CAG list.

[0263] Some CAG IDs may be removed from the terminal's allowed CAG list. In this case, according to the prior art, the AMF should send the newly updated allowed CAG list to the terminal via the UE configuration update process and then perform NAS release. The same operation can be applied to a hosted network that provides localized services. In this case, based on the validity conditions, some CAGs may no longer be valid. The AMF should then update the allowed CAG list of the terminal and release the connection with the terminal. Although the terminal may still be able to receive services from the cell, it may be inconvenient to re-establish a new connection with the device and resume the service. For example, the device may receive localized services and use other home network services (e.g., voice calls) at the same time. In this case, releasing the connection with the terminal may cause the terminal's service to be interrupted.

[0264] For example, a CAG may be valid for a service provided at a specific location and time (e.g., a localized service such as a concert). In this case, the CAG may become invalid when the concert ends. According to the prior art, the network connection is terminated for UEs for which the CAG associated with the concert is invalid. In this case, the UE's network connection is terminated even though the UE may be able to perform its normal non-concert services well. The problem is that the UE needs to reconnect in situations where it may be able to be well served by existing services.

[0265] Furthermore, there may be terminals that are not capable of checking the validity conditions of CAGs. These terminals may be served by a network where the validity of a particular CAG changes due to the validity conditions. In this case, the network should appropriately update the terminal's allowed CAG list based on the change in validity conditions, but existing technologies do not support this operation.

[0266] A way to support CAG with validity conditions in NG-RAN is needed. Note that in the disclosure of this disclosure, the terms "validity condition" and "validity condition" can be used interchangeably.

[0267] According to this disclosure, the NG-RAN can send the AMF a capability to determine the validity conditions of a specific CAG. Based on this capability, it is recommended that the AMF configure and provide the NG-RAN with an allowed CAG list including validity conditions. Based on the allowed CAG list including validity conditions, the NG-RAN can continuously check the validity conditions of the terminal. If a specific CAG is no longer valid in the terminal's allowed CAG list, a method for the NG-RAN to hand over the terminal is described.

[0268] For example, a terminal may not be capable of checking the validity conditions of a CAG. For these terminals, the AMF can still appropriately set the allowed CAG list by checking the validity conditions of each CAG. The AMF can send the allowed CAG list to the terminal. There may also be cases where some CAGs in the terminal's allowed CAG list are no longer valid due to validity conditions. In this case, the AMF can maintain the current NG connection without triggering AN release. The AMF can then forward the updated allowed CAG list to the NG-RAN.

[0269] In this disclosure, the following examples are presented. For example, the AMF may be informed of whether the NG-RAN has the capability to check the validity conditions of a specific CAG. Based on this capability, the AMF may decide whether to provide the NG-RAN with the validity condition information of the specific CAG in the allowed CAG list. Furthermore, the NG-RAN may be provided with the validity condition information of the specific CAG. In this case, the NG-RAN may continuously check this condition. If the specific CAG is no longer valid, the NG-RAN may determine whether the terminal can continue to be served by the cell to which the terminal is connected. If the cell can no longer serve the terminal, the NG-RAN may hand over the terminal to another cell.

[0270] For some service operations between core NFs described below, new service operations may be defined and used. In addition, for some or all NG messages between the AMF and NG-RAN described below, new NG messages may be defined and used. In addition, for some or all RRC messages between the NG-RAN and terminals described below, new RRC messages may be defined and used.

[0271] In the following procedures, some steps may be performed simultaneously / in parallel or in an alternate order.

[0272] The names of the instructions or parameter information suggested below are examples and may be replaced with other names and interpreted with respect to the proposed process / purpose / method.

[0273] In the following, reference will be made to Figure 7a and Figure 7b This section describes an example of how NG-RAN and AMF check the validity conditions of CAG.

[0274] The following figures are intended to illustrate specific embodiments of the present disclosure. The names of specific devices or specific signals / messages / fields shown in the figures are for illustrative purposes only, and the technical features of the present disclosure are not limited to the specific names used in the following figures.

[0275] Figure 7a and Figure 7b A first example of a process for checking a validity condition according to one embodiment of the present disclosure is illustrated.

[0276] Figure 7a and Figure 7b This document illustrates an example scenario where the NG-RAN and AMF can determine, based on a validity condition, that a specific CAG in the terminal's allowed CAG list is no longer valid. In this case, the NG-RAN and / or AMF can continue to provide services (e.g., localized services, etc.) to the terminal.

[0277] NG-RAN can continuously check the validity condition of each CAG to determine whether the CAG value is valid within the allowed CAG list.

[0278] Step 0: To establish the NG interface between each NG-RAN and the AMF, the NG-RAN may send an NGAP NG SETUP REQUEST message to the AMF. This initiates the NG setup procedure. If the individual NG-RAN has the capability to check the validity conditions of the CAG, the NG-RAN informs the AMF of this fact in the NGAP NG SETUP REQUEST message. The AMF responds to the NG-RAN by sending an NGAP NG SETUP RESPONSE message. If the AMF supports the CAG with validity conditions functionality, the AMF may also inform the NG-RAN of its support for CAG with validity conditions in the NGAP NG SETUP RESPONSE message.

[0279] NG-RAN may also use the Xn interface to exchange information about whether each node has the capability to check the validity conditions of the CAG.

[0280] Step 1: The terminal may send a Registration Request message to the AMF via NG-RAN#1. The terminal may attempt to register with the network. At this point, the terminal may have the capability to check the validity conditions of the CAG. The terminal may inform the AMF of the capability to check the validity conditions of the CAG via the UE5GMM Core Network Capability IE in the Registration Request message.

[0281] Step 2: If the AMF decides to accept the terminal's registration request, it requests NG-RAN#1 to create a UE context using an Initial Context Setup Request message. The AMF may also generate a Registration Accept message to be delivered to the terminal. The AMF may send an Initial Context Setup Request message including the Registration Accept message to NG-RAN#1.

[0282] At this time, for the terminal with the ability to check the validity conditions of CAG, the AMF can send a registration acceptance message including the allowed CAG list information. Here, the allowed CAG list information is shown in the following example:

[0283] - CAG ID not related to validity conditions

[0284] CAG ID including validity conditions, e.g. CAG + time validity condition and / or location validity condition

[0285] There may also be a case where a terminal does not have the capability to check the validity conditions of a CAG, but the terminal's subscription data includes a CAG with validity conditions. In this case, the AMF may send a Registration Accept message including the allowed CAG list information.

[0286] Here, the allowed CAG list information is as shown in the following example:

[0287] CAG ID not related to validity conditions

[0288] If a time validity condition exists and is met, the CAG ID associated with that validity condition (→ information about the time validity condition is not sent to the terminal)

[0289] If a location validity condition exists, the CAG ID associated with that validity condition (→ information about the location validity condition is not sent to the terminal)

[0290] The AMF may include the following Allowed CAG List content in the Mobility Restriction List IE included in the Initial Context Setup Request message. This allows the AMF to forward the Initial Context Setup Request message including the Allowed CAG List to NG-RAN#1. An example of the Allowed CAG List is shown below:

[0291] A) CAG ID is not related to validity conditions.

[0292] B) CAG ID associated with the validity condition, if a time validity condition exists and is met (→ information about the time validity condition is not sent to the terminal).

[0293] For example, the AMF may configure the information in the example of B) as an optional IE, such as the following CAG IE with validity conditions. The AMF may also send the information in the example of B) (configured as an optional IE) to NG-RAN#1.

[0294] For reference, the examples in Tables 3 to 6 below show the Mobility Restriction List Information Element (IE), NPN Mobility Information IE, and Allowed PNI-NPN List IE defined in TS 38.413.

[0295] An example of a mobility restriction list is described.

[0296] This IE defines roaming or access restrictions for subsequent mobility actions that provide information about the destination of a UE's mobility action (e.g., handover) or define roaming or access restrictions for SCG selection or appropriate RNA assignment during dual connectivity actions. The NG-RAN operation when receiving this IE is specified in TS 23.501.

[0297] Table 3 is an example of a mobility restriction list.

[0298] [Table 3]

[0299]

[0300]

[0301]

[0302] For reference, in the example of Table 3, 9.3.3.5, 9.3.3.10, 9.3.1.184, and 9.3.1.126 may be subclauses of TS38.413 V17.3.0.

[0303] The example in Table 4 shows an example of NPN mobility information.

[0304] This IE indicates the access restrictions associated with the NPN.

[0305] [Table 4]

[0306]

[0307] Note that in the example of Table 4, 9.3.3.42 and 9.3.3.45 may be subclauses of TS 38.413 V17.3.0.

[0308] Table 5 shows an example of an allowed PNI-NPN list.

[0309] This IE includes information about the allowed UE mobility in PNI-NPN. It includes the allowed PNI-NPNs and, for each PLMN, whether the UE is allowed to access non-CAG cells.

[0310] [Table 5]

[0311]

[0312] Note that in the example of Table 5, 9.3.3.5 and 9.3.3.43 may be subclauses of TS 38.413 V17.3.0.

[0313] The example in Table 6 is an example of a CAG including a validity condition.

[0314] This IE is used together with the PLMN identifier to identify the public network integrated NPN with validity conditions.

[0315] [Table 6]

[0316]

[0317] Even if the NG-RAN does not inform the AMF in the NGAP NG SETUP REQUEST message in step 0 that the NG-RAN has the capability to check the validity condition of the CAG, if the CAG IE with the validity condition including the content in B) has its criticality set to REJECT, the NG-RAN that does not have the capability to check the validity condition of the CAG can inform the AMF via an NGAP ERROR INDICATION or other NGAP message that the NG-RAN cannot understand the IE. Therefore, the AMF can use step 2 to determine whether the NG-RAN has the capability to check the validity condition of the CAG. Alternatively, the NG-RAN can separately inform the AMF that it has the capability to check the validity condition of the CAG via an NGAP HANDOVER REQUEST, NGAP HANDOVER REQUEST, or NGAP PATH SWITCH REQUEST message, etc.

[0318] The criticality of the IE with validity conditions for a CAG including the content of B) may be set to be ignored. In this case, an NG-RAN that does not have the capability to check the validity conditions of the CAG shall ignore the content of the CAG with validity conditions IE. The NG-RAN shall only consider the existing CAG information included in the Allowed PNI-NPN List IE. The terminal may be handed over to an NG-RAN that has the capability to check the validity conditions of the CAG. In this case, the AMF may refer to the capabilities of the NG-RAN and send a new list of allowed CAGs with validity conditions to the NG-RAN. For example, if the NG-RAN to which the terminal is handed over supports the capabilities related to the validity conditions, the AMF may send a new list of allowed CAGs including the validity conditions to the new NG-RAN.

[0319] Alternatively, a terminal may be handed over from an NG-RAN that does not have the capability to check the validity conditions of CAGs to an NG-RAN that does. In this case, the NG-RAN may request a new list of allowed CAGs including validity conditions from the AMF based on capability information previously exchanged over the Xn interface. Alternatively, the AMF may always send the allowed CAG list including validity conditions to the NG-RAN during the handover process. A terminal may move from an NG-RAN that supports CAG validity conditions to an NG-RAN that does not. In this case, the AMF or the source NG-RAN may check the validity conditions and determine that they are valid. In this case, the AMF may include the CAG without validity conditions in the allowed CAG list and send it to the target NG-RAN.

[0320] Step 3: NG-RAN#1 may send the registration accept message received from the AMF in step 2 to the terminal.

[0321] Step 4: Will execute Figure 5 and Figure 6 The remaining steps of the registration process.

[0322] Step 5: Step 5 may be performed as follows for two example cases: when NG-RAN1 supports CAG with validity conditions and the AMF is aware of this, and when NG-RAN1 does not support CAG with validity conditions and the AMF is aware of this.

[0323] If NG-RAN1 supports CAGs with validity conditions and the AMF is aware of this, the AMF and NG-RAN#1 can still check the validity conditions of each CAG included in the terminal's allowed CAG list. The AMF can determine that NG-RAN#1 is able to determine that the CAG is valid. If a specific CAG is no longer valid (i.e., the validity conditions of the CAG are not met), NG-RAN#1 should determine that the terminal is not served by the CAG. If a specific invalid CAG meets the validity conditions again, the corresponding CAG has changed to a valid state, so NG-RAN#1 should determine that the terminal can be served in the CAG again.

[0324] If the NG-RAN1 does not support a CAG with a validity condition and the AMF is aware of this, the AMF may check the validity condition when the terminal is in an NG-RAN that does not support a CAG with a validity condition. If the validity changes, the AMF may update the allowed CAG list, i.e., the AMF continues to check the validity condition of each CAG in the terminal's allowed CAG list to determine whether the CAG is valid. If a specific CAG is no longer valid (i.e., the validity condition of the CAG is not met), the AMF sends signaling to the NG-RAN to exclude the CAG from the allowed CAG list. Alternatively, if a specific invalid CAG becomes valid by satisfying the validity condition again, the AMF sends signaling to the NG-RAN to add the CAG to the allowed CAG list.

[0325] Step 6: If step 5 determines that the terminal is not served in the specific CAG based on the validity condition, NG-RAN#1 may perform one or more of step 6a, step 6b, or step 6c.

[0326] If the cell that the terminal is currently accessing can still support one or more valid CAG IDs included in the allowed CAG list, NG-RAN#1 shall continue to serve the terminal through this cell without taking any further action. In this case, a new NGAP message may be defined, or a new cause value or indication may be added to an existing NGAP message to inform the AMF that the terminal can continue to be served by this cell.

[0327] There may be a situation where not all valid CAG IDs included in the allowed CAG list can be supported by the cell that the terminal is currently accessing. In this case, NG-RAN#1 can hand over the terminal to one of the neighboring cells that can support the valid CAG IDs included in the allowed CAG list (CAG IDs without validity conditions or CAG IDs that meet validity conditions, if any). Figure 7a and Figure 7b In the example shown in Figure 2, NG-RAN#1 performs an Xn-based handover or an NG-based handover to NG-RAN#2 for the terminal. The NG-RAN may notify the AMF that a handover has been initiated because the validity of a specific CAG has changed according to the validity conditions. To notify the AMF, the NG-RAN may include a new cause value or indication in the NGAP Handover Request or NGAP Path Handover Request message.

[0328] There may be a situation where all valid CAG IDs included in the allowed CAG list are not supported by the cell that the terminal is currently accessing, and the neighboring cells of NG-RAN#1 do not support those valid CAGs. In this case, NG-RAN#1 can request the release of the terminal by sending an NGAP UE CONTENT RELEASE REQUEST message to the AMF. In this case, NG-RAN#1 can notify the AMF that it cannot support all valid CAG IDs included in the allowed CAG list by means of a cause value or indication.

[0329] Even if the AMF does not know whether NG-RAN1 supports CAG with validity conditions, the AMF can also know the decision of NG-RAN#1 based on the cause value or indication sent by NG-RAN#1.

[0330] Step 7: The AMF may send the newly updated allowed CAG list to the terminal via the UE configuration update procedure only if the following two conditions are met:

[0331] - If the terminal does not have the capability to verify the validity conditions of the CAG, but the subscription data of the terminal includes a CAG with validity conditions.

[0332] - In step 5, if based on the validity condition, the validity of a particular CAG is changed (invalid CAG becomes valid CAG or valid CAG becomes invalid CAG)

[0333] At this time, the AMF may send a UE configuration update command message including the updated allowed CAG list information to the terminal. For example, the updated allowed CAG list information may include the following examples:

[0334] - CAG ID(s) not relevant to the validity condition

[0335] - if a time validity condition exists and is met, the CAGID(s) associated with the validity condition (in this case, information about the time validity condition is not sent to the terminal)

[0336] - If a location validity condition exists, the CAG ID(s) associated with that validity condition (in this case, information about the location validity condition is not sent to the terminal)

[0337] Note that the actions in step 7 can be performed before or concurrently with step 6. During step 6b, the AMF may request NG-RAN#1 to deliver the UE Configuration Update Command message. In this case, NG-RAN#1 may inform the AMF that it is unable to do so by sending an NGAP NAS Non-Delivery Indication message. In this case, after the handover of the terminal is completed, the AMF may forward the UE Configuration Update Command message to the terminal via NG-RAN#2.

[0338] The AMF may learn through step 0 or step 2 that the NG-RAN has the capability to check the validity condition of the CAG. If the AMF receives the NGAP UE Context Release Request message in step 6c, it may perform the UE Context Release procedure. Otherwise, the AMF may only forward the UE Configuration Update Command message to the terminal and may not perform the UE Context Release procedure.

[0339] Step 8: If the AMF receives step 6c from NG-RAN#1, the AMF performs the UE Context Release procedure. In this case, the AMF may forward the UE Configuration Update Command message in step 7a to the terminal. In this case, step 8 is performed after receiving the UE Configuration Update Complete message from the terminal.

[0340] In the following, reference Figure 8a and Figure 8b The example in describes an example where only the AMF checks the validity condition of the CAG.

[0341] The following figures are intended to illustrate specific embodiments of the present disclosure. The names of specific devices or specific signals / messages / fields shown in the figures are for illustrative purposes only, and the technical features of the present disclosure are not limited to the specific names used in the following figures.

[0342] Figure 8a and Figure 8b A second example of a process of checking a validity condition according to one embodiment of the present disclosure is illustrated.

[0343] Figure 8a and Figure 8bThis example illustrates how the AMF can determine, based on validity conditions, that a specific CAG in the terminal's allowed CAG list is no longer valid. In such a situation, it illustrates how the network can continue to provide services (e.g., localized services, VMR, etc.) to the terminal.

[0344] exist Figure 8a and Figure 8b In the example above, the NG-RAN may continue to check the validity condition of each CAG to determine whether the corresponding CAG value is valid within the allowed CAG list. However, the NG-RAN may not perform the validation unless requested by the AMF. Figure 7a and Figure 7b Alternatively, even if the NG-RAN has the capability to check the validity condition of the CAG, it may not continuously check the validity condition of the CAG. The NG-RAN may check the validity condition of each CAG only when it is needed to perform a handover for the terminal or when the terminal transitions from the RRC_INACTIVE state to the RRC_CONNECTED state. In these cases, the NG-RAN may determine whether the CAG value at this time is valid within the allowed CAG list. Alternatively, the NG-RAN may not have the capability to check the validity condition of the CAG at all. Therefore, even in the case where the AMF does not know whether the NG-RAN has the capability to check the validity condition of the CAG, Figure 8a and Figure 8b The example is also applicable.

[0345] Step 0: To establish the NG interface between each NG-RAN and the AMF, the NG-RAN may send an NGAP NG SETUP REQUEST message to the AMF. This initiates the NG setup procedure. If each NG-RAN has the capability to check the validity conditions of the CAG, the NG-RAN informs the AMF of this fact in the NGAP NG SETUP REQUEST message. The AMF responds by sending an NGAP NG SETUP RESPONSE message. If the AMF supports the CAG with validity conditions function, the AMF may also inform the NG-RAN of this support in the NGAP NG SETUP RESPONSE message.

[0346] NG-RAN may also use the Xn interface to exchange information about whether each node has the capability to check the validity conditions of the CAG.

[0347] Step 1: This can be done with Figure 7a and Figure 7b Follow the same steps as in step 1.

[0348] Step 2: If the AMF decides to authorize the terminal's registration request, it requests NG-RAN#1 to create a UE context using an Initial Context Setup Request message. The AMF may also generate a Registration Accept message to be delivered to the terminal. The AMF may send an Initial Context Setup Request message including the Registration Accept message to NG-RAN#1.

[0349] At this time, for the terminal with the ability to check the validity conditions of CAG, the AMF can send a registration acceptance message including the allowed CAG list information. Here, the allowed CAG list information is as shown in the following example:

[0350] - CAG ID(s) not relevant to the validity condition

[0351] - CAG ID(s) including validity conditions, e.g. CAG(s) + time validity condition and / or location validity condition

[0352] There may also be a situation where the terminal does not have the capability to check the validity conditions of CAG, but the terminal's subscription data includes CAG with validity conditions. In this case, the AMF may send a Registration Accept message including the allowed CAG list information.

[0353] Here, the CAG list information is allowed as shown in the following example:

[0354] - CAG ID(s) not relevant to the validity condition

[0355] - If a time validity condition exists and is met, the CAGID(s) associated with this validity condition (→ information about the time validity condition is not sent to the terminal)

[0356] - If a location validity condition exists, the CAG ID(s) associated with that validity condition (→ information about the location validity condition is not sent to the terminal)

[0357] The AMF may include the following Allowed CAG List content in the Mobility Restriction List IE included in the Initial Context Setup Request message. This allows the AMF to forward the Initial Context Setup Request message including the Allowed CAG List to NG-RAN#1. An example of the Allowed CAG List is shown below:

[0358] A) CAG ID(s) not associated with validity conditions.

[0359] B) If a time validity condition exists and is met, the CAG ID(s) associated with the validity condition (→ information about the time validity condition is not sent to the terminal)

[0360] Even if the NG-RAN does not inform the AMF in step 0 in the NGAP NG SETUP REQUEST message that the NG-RAN has the capability to check the validity condition of the CAG, if the CAG IE with the validity condition, including the content in B), has its criticality set to REJECT, the NG-RAN, which does not have the capability to check the validity condition of the CAG, can inform the AMF via an NGAP ERROR INDICATION or other NGAP message that the NG-RAN cannot understand the IE. Therefore, the AMF can use step 2 to determine whether the NG-RAN has the capability to check the validity condition of the CAG. Alternatively, the NG-RAN can separately inform the AMF of its capability to check the validity condition of the CAG via an NGAP HANDOVER REQUEST, NGAP HANDOVER REQUEST, or NGAP PATH SWITCH REQUEST message, etc.

[0361] The criticality of the CAG IE with validity conditions, including the content of B), can be set to ignore. In this case, an NG-RAN that does not have the capability to check the validity conditions of the CAG should ignore the content of the CAG IE with validity conditions. The NG-RAN only considers the existing CAG information included in the Allowed PNI-NPN List IE. The terminal may be handed over to an NG-RAN that has the capability to check the validity conditions of the CAG. In this case, the AMF can refer to the capabilities of the NG-RAN and send a new allowed CAG list with validity conditions to the NG-RAN. For example, if the NG-RAN to which the terminal is handed over supports the capabilities associated with the validity conditions, the AMF can send a new allowed CAG list including the validity conditions to the new NG-RAN.

[0362] Alternatively, a terminal may be handed over from an NG-RAN that does not have the capability to check the validity conditions of CAGs to an NG-RAN that does. In this case, the NG-RAN may request a new list of allowed CAGs including validity conditions from the AMF based on capability information previously exchanged over the Xn interface. Alternatively, the AMF may always send the allowed CAG list including validity conditions to the NG-RAN during the handover process. A terminal may move from an NG-RAN that supports CAG validity conditions to an NG-RAN that does not. In this case, the AMF or the source NG-RAN may check the validity conditions and determine that they are valid. In this case, the AMF may include the CAG without validity conditions in the allowed CAG list and send it to the target NG-RAN.

[0363] The AMF may know in advance that NG-RAN#1 does not have the ability to check the validity conditions of CAGs. In this case, the AMF may include the following allowed CAG list content in the Mobility Restriction List IE included in the Initial Context Setup Request message. The AMF may also send an Initial Context Setup Request message including the allowed CAG list to NG-RAN#1. The following is an example of an allowed CAG list:

[0364] a) CAG ID(s) not relevant to the validity condition

[0365] b) If a time validity condition exists and the condition is met, the CAG ID(s) associated with the validity condition (e.g., information about the time validity condition is not sent to the terminal)

[0366] c) If a location validity condition exists, the CAG ID(s) associated with that validity condition (e.g., information about the location validity condition is not sent to the terminal)

[0367] NOTE: In this case, an NG-RAN that does not have the capability to check the validity condition of a CAG may trigger a handover to an NG-RAN that has the capability to check the validity condition of a CAG. For example, to trigger such a handover, the NG-RAN may include information related to a), b) and c) in the CAG ID IE in the Allowed PNI-NPN List IE in TS 38.413. Thus, an NG-RAN that does not have the capability to check the validity condition of a CAG may select a cell that supports the CAG ID(s) in b) or c) as the target cell during the handover procedure. When the AMF becomes aware that the terminal has moved to an NG-RAN that has the capability to check the validity condition of a CAG via handover, it may forward the Allowed CAG List information back to that NG-RAN in the following example form:

[0368] - CAG ID(s) not relevant to the validity condition

[0369] - CAG ID(s) including validity conditions, i.e. CAG(s) + time validity condition and / or location validity condition

[0370] NOTE: When sending a CAG message to the AMF, the UDM may decide whether to include the validity condition based on whether the AMF supports the validity condition. For example, if the AMF supports the validity condition, the validity condition is included with the CAG message. If the AMF does not support the validity condition, the UDM may check the validity condition directly. Only when the validity condition is met, the UDM may exclude the validity condition and send only the CAG identifier that meets the validity condition in the CAG message. If the UDM wants to know the exact location / time zone information of the terminal, it can subscribe to AMF events about the location / time zone information of the terminal.

[0371] In this case, a new entry for the validity condition can be defined in the list of supported functions defined in clause 6.1.8 of TS 29.503 V18.0.0. Based on this, the AMF can inform the UDM whether it supports the validity condition. This also allows the UDM to decide whether to send the validity condition when sending the CAG information to the AMF. In the following example, the number of functions supported by the CAG validity condition is set to 16, but this is for illustrative purposes only and can be set to other values.

[0372] An example of capability negotiation in clause 6.1.8 of TS 29.503 is described.

[0373] The optional functions in Table 7 are defined for the Nudm_SDM API and shall be negotiated using the extension mechanism defined in clause 6.6 of 3GPP TS 29.500 V18.0.0.

[0374] Optional functions according to the example in Table 7 may be defined for the Nudm_SDM API. These functions may be negotiated using the extension mechanism defined in clause 6.6 of 3GPP TS 29.500 V18.0.0.

[0375] [Table 7]

[0376]

[0377]

[0378]

[0379] The examples in Table 17 are examples of supported functions.

[0380] Step 3: NG-RAN#1 may send the Registration Accept message received from the AMF in step 2 to the terminal.

[0381] Step 4: Will execute Figure 5 and Figure 6 Follow the remaining steps of the registration process.

[0382] Step 5: The AMF may continue to check the validity conditions of each CAG included in the terminal's allowed CAG list and determine whether the CAG is valid. There may be a situation where a specific CAG is no longer valid (i.e., the validity conditions of the CAG are not met). In this case, the AMF may determine that the terminal is not served by the CAG. A CAG with invalid validity conditions may meet the validity conditions again (e.g., change from invalid to valid). In this case, the AMF may determine that the CAG has changed to a valid state, and the terminal is therefore eligible to obtain service in the CAG again.

[0383] NG-RAN1 does not support CAGs with validity conditions, and the AMF may be aware that NG-RAN1 does not support this. In this case, the following example operations may apply. A terminal may connect to an NG-RAN that does not support CAGs with validity conditions. In this case, the AMF may check the validity conditions and update the allowed CAG list if the validity has changed. In other words, the AMF may continue to check the validity conditions of each CAG included in the allowed CAG list of the terminal and determine whether the CAG is valid. If a specific CAG is no longer valid (i.e., the validity conditions of the CAG are not met), or if a specific invalid CAG becomes valid again (i.e., the validity conditions of the CAG are met again), the AMF may send the newly updated allowed CAG list to the NG-RAN in step 6.

[0384] The AMF may be aware that the terminal and NG-RAN#1 do not have the capability to check the validity conditions of the CAG. In this case, the AMF may omit steps 6 to 10 and initiate the UE configuration update procedure according to section 4.2.4.2 of TS 23.502.

[0385] Step 6: Step 6 may be performed as follows for two example cases: when NG-RAN1 supports CAG with validity conditions and when NG-RAN1 does not support CAG with validity conditions.

[0386] If NG-RAN1 supports CAGs with validity conditions, the following operations may be performed. In this case, in step 5, the AMF may determine that the terminal is not served by a specific CAG based on the validity conditions (i.e., the CAG is invalid). In this case, the AMF may send an NGAP CAG Update Indication message to NG-RAN#1 to inform it that a specific CAG included in the terminal's allowed CAG list has changed to an invalid state. Based on the message sent, the AMF may request confirmation that NG-RAN#1 can continue to support the terminal. Instead of using the NGAP CAG Update Indication message, the AMF may include an indication requesting re-evaluation of the CAG validity conditions in a regular message.

[0387] If NG-RAN1 does not support a CAG with a validity condition, the following operations may be performed. If a specific CAG becomes an invalid CAG according to the validity condition in step 5, the AMF may send a newly updated allowed CAG list to NG-RAN#1. If necessary (for example, if it determines that the terminal is no longer served by the current cell), the AMF may perform an AN release procedure.

[0388] Alternatively, in step 5, the AMF may determine that a specific CAG in the terminal's allowed CAG list is no longer valid (i.e., the validity condition of that CAG is not met). In this case, the AMF may send the newly updated allowed CAG list to NG-RAN1 and then perform one or more of the following actions according to the operator's policy:

[0389] -Based on a pre-configured timer, the AMF may delay the execution of the AN release procedure. If a handover of the terminal occurs before the timer expires, the AMF may skip the AN release procedure.

[0390] - There may also be a situation where a specific CAG is no longer valid in the terminal's allowed CAG list because its validity conditions are not met. In this case, the AMF may skip the AN release procedure. If the change in subscription information makes the CAG no longer valid in the terminal's allowed CAG list, the AMF may perform AN release.

[0391] NOTE: For reference, the AMF may also send the newly updated allowed CAG list to NG-RAN1 via step 9 instead of step 6.

[0392] Step 7: NG-RAN#1 may send a CAG Update Confirm message including action type information to the AMF.

[0393] If NG-RAN1 supports CAGs with validity conditions, NG-RAN#1 may determine the valid CAG IDs in the terminal's allowed CAG list based on the invalid CAG ID(s) received in step 6. NG-RAN#1 may compare the valid CAG IDs in the allowed CAG list with the CAG list supported by the cell currently accessed by the terminal. Accordingly, NG-RAN#1 may determine whether the current cell can continue to serve the terminal. NG-RAN#1 may also notify the AMF of the result of this decision via the Action Type IE included in the NGAP CAG Update Confirm message.

[0394] One or more valid CAG IDs included in the Allowed CAG List may still be supported by the cell the terminal is currently accessing. In this case, NG-RAN#1 may set "Action Type IE = Supported CAG" in the CAG Update Confirm message. Upon receiving this message, the AMF shall not take any further action (e.g., it shall not perform AN release) unless the execution conditions in step 9 are met.

[0395] If all valid CAG IDs included in the allowed CAG list cannot be supported by the cell that the terminal is currently accessing, and NG-RAN#1 decides to hand over the terminal to one of the neighboring cells that can support the valid CAG IDs included in the allowed CAG list, NG-RAN#1 can set the action type IE to "Action type IE = Handover triggered due to updated (multiple) CAGs". NG-RAN#1 can also forward the NGAP CAG update confirm message to the AMF and then perform step 8.

[0396] Alternatively, all CAG IDs included in the newly updated allowed CAG list may not be supported by the cell that the terminal is currently accessing, and the neighboring cells of NG-RAN#1 may not support those CAG IDs. In this case, NG-RAN#1 may decide to release the terminal. In this case, NG-RAN#1 may set the Action Type IE to "Action Type IE = Request release due to unsupported CAG(s)". The AMF that receives this Action Type IE may skip step 8 and execute steps 9 and 10.

[0397] NOTE: If NG-RAN#1 can determine the valid CAG ID in the allowed CAG list of the terminal based on the (multiple) invalid CAG IDs received in step 6, it is able to determine the valid CAG ID in the allowed CAG list of the terminal. NG-RAN#1 may not support the operation of comparing the valid CAG ID with the CAG list supported by the cell currently accessed by the terminal to determine whether the terminal can continue to be served by the current cell. In this case, NG-RAN#1 may send an NGAP CAG Update Reject or NGAP Error Indication message to the AMF to inform the AMF that it does not support this operation.

[0398] NOTE: Instead of informing NG-RAN#1 of the invalid CAG ID(s) in step 6, the AMF may simply request the CAG ID(s) supported by the cell that the terminal is currently accessing, and upon receiving such a request, NG-RAN#1 may forward a message including the CAG ID(s) supported by the cell that the terminal is currently accessing to the AMF in step 7, instead of an action type IE. Alternatively, whenever the cell serving the terminal changes, it may proactively inform the AMF of the CAG ID(s) that the cell can support. Based on this, the AMF may compare the valid CAG list in the allowed CAG list with the CAG list supported by the cell that the terminal is currently accessing to determine whether the terminal can continue to be served by the current cell.

[0399] The validity condition of one or more valid CAG IDs included in the allowed CAG list may change from invalid to valid, or from valid to invalid. One or more valid CAG IDs may still be supported by the cell that the terminal is currently accessing. In this case, the AMF should not take any further action except for meeting the execution conditions in step 9. All valid CAG IDs included in the allowed CAG list may not be supported by the cell that the terminal is currently accessing. In this case, the AMF can send an NGAP message to request NG-RAN#1 to hand over the terminal to one of the neighboring cells that can support the valid CAG IDs included in the allowed CAG list. In this case, NG-RAN#1 can perform step 8 based on the request sent by the AMF. Alternatively, all valid CAG IDs included in the allowed CAG list may not be supported by the cell that the terminal is currently accessing. In this case, the AMF can decide to initiate AN release for the terminal. Therefore, the AMF performs steps 9 and 10.

[0400] Step 8: In step 7, NG-RAN#1 may determine "Action Type IE = Handover triggered due to updated CAG(s)." In this case, NG-RAN#1 may trigger an Xn-based or NG-based handover for the terminal to one of the neighbor cells that can support a valid CAG ID included in the allowed CAG list.

[0401] Step 9: The AMF may send the newly updated allowed CAG list to the terminal via the UE configuration update procedure only if the following two conditions are met:

[0402] - If the terminal does not have the capability to verify the validity conditions of the CAG, but the subscription data of the terminal includes a CAG with validity conditions.

[0403] - In step 5, if based on the validity condition, the validity of a particular CAG is changed (invalid CAG becomes valid CAG or valid CAG becomes invalid CAG)

[0404] At this time, the AMF may send a UE configuration update command message including the updated allowed CAG list information to the terminal. For example, the updated allowed CAG list information may include the following examples:

[0405] - CAG ID(s) not relevant to the validity condition

[0406] - if a time validity condition exists and is met, the CAGID(s) associated with the validity condition (in this case, information about the time validity condition is not sent to the terminal)

[0407] - If a location validity condition exists, the CAG ID(s) associated with that validity condition (in this case, information about the location validity condition is not sent to the terminal)

[0408] The AMF may learn that NG-RAN#1 does not have the capability to check the validity conditions of the CAG. In this case, the AMF may include the updated content of the allowed CAG list in an NGAP downlink NAS transport message including the UE configuration update command message or in the mobility restriction list IE included in a separate NGAP message. For example, the AMF may send an NGAP downlink NAS transport message or a separate NGAP message including the updated content of the allowed CAG list to NG-RAN#1. An example of the updated content of the allowed CAG list is as follows:

[0409] - CAG ID(s) not relevant to the validity condition

[0410] - if a time validity condition exists and is met, the CAGID(s) associated with the validity condition (in this case, information about the time validity condition is not sent to the terminal)

[0411] - If a location validity condition exists, the CAG ID(s) associated with that validity condition (in this case, information about the location validity condition is not sent to the terminal)

[0412] In step 7, the AMF may have received "Action Type IE = Handover triggered due to updated CAG(s). In this case, after the handover procedure for the terminal to NG-RAN#2 is completed in step 8, the AMF may request the delivery of the UE Configuration Update Command message via NG-RAN#2.

[0413] Step 10: If in Step 7 the AMF receives "Action Type IE = Request for Release due to (Multiple) CAGs not being supported", the AMF can execute Step 10. At this time, in Step 9a, the AMF may have sent a UE configuration update command message to the terminal. In this case, the AMF can execute Step 10 after receiving the UE configuration update completion message from the terminal.

[0414] When the location validity condition is enforced by the AMF, NG-RAN or the terminal, refer to Figure 7a and Figure 7b and / or Figure 8a and Figure 8b The various embodiments of the present disclosure described can be applied in the same way. For example, the location validity condition can be provided to the AMF, NG-RAN or the terminal. Based on this validity condition, each node (such as the AMF, NG-RAN or the terminal) can determine whether a specific CAG is valid or invalid based on whether it meets the location validity condition. Therefore, the various examples of the present disclosure can be equally applicable to cases where the CAG validity status changes according to whether the location validity condition is met.

[0415] The various examples of the disclosure herein can be applied, such as the following examples

[0416] describe an extension of the CAG based on validity information.

[0417] According to the prior art, the PNI-NPN with CAG does not support hosting localized services. .[

[0418] The CAG identifiers allowed in the CAG list can be associated with time validity conditions.

[0419] <UE MM Core Network Capability Handling>

[0420] For UE MM core network capability handling, the various examples of the present disclosure can be applied.

[0421] The UE MM core network capabilities are divided into S1 UE network capabilities (mainly for core network parameters related to E-UTRAN access) and UE 5GMM core network capabilities (mainly including other UE capabilities related to 5GCN or EPS interworking), and include non-radio related capabilities, such as NAS security algorithms, etc. The S1 UE network capabilities are transmitted between all CN nodes when changing from AMF to AMF, AMF to MME, MME to MME, and MME to AMF. The UE 5GMM core network capabilities are only transmitted when changing from AMF to AMF. <s

[0422] In order to keep the UE MM core network capability information stored in the AMF up to date (e.g. to handle the case where the USIM is moved to another terminal out of coverage and the previous terminal does not send a detach message, and inter-RAT registration area updates), the following may apply: The UE shall send the UE MM core network capability information to the AMF in a NAS message during the initial registration and mobility registration update procedures.

[0423] The AMF shall always store the latest UE MM Core Network Capability received from the UE. When the UE provides the UE MM Core Network Capability via registration signaling, any UE MM Core Network Capability received by the AMF from the previous AMF / MME shall be replaced.

[0424] If the UE MM core network capability information of the UE changes (in CM connected state or CM idle state), the UE shall perform the mobility registration update procedure the next time it returns to NG-RAN coverage. Please refer to clause 4.2.2 of TS 23.502.

[0425] The UE shall indicate the capabilities supported by the UE in the UE 5GMM core network capabilities. For example, the following capability examples may be included in the UE 5GMM core network capabilities:

[0426] - Attach in EPC with request type "Handover" in the PDN Connection Request message.

[0427] -EPC NAS.

[0428] -SMS via NAS.

[0429] -LCS.

[0430] -5G SRVCC from NG-RAN to UTRAN.

[0431] -Radio Capability Signaling Optimization (RACS).

[0432] - Network slice specific authentication and authorization.

[0433] -Parameters in network operations to support 5G CIoT.

[0434] - Receive WUS assistance information (E-UTRA).

[0435] - Paging subgroup support indication (NR).

[0436] - CAG, clause 5.30.3.3 of TS 23.501 and various examples of disclosure in this disclosure.

[0437] - See CAG including validity conditions, clause 5.30.3.3 of TS 23.501, and various examples in the beginning of this disclosure.

[0438] - Subscription-based network slice concurrent registration restriction.

[0439] - Support for NSAG.

[0440] - Minimization of service interruption (MINT).

[0441] - Equivalent SNPN.

[0442] - Unavailable period.

[0443] A UE operating two or more USIMs may wish to support and use one or more multi-USIM features for a certain USIM in a PLMN. In this case, the UE shall indicate its support for such one or more multi-USIM features through the following indications in the UE 5GMM core network capabilities of the USIM:

[0444] - Support for connection release.

[0445] - Support for paging cause indication for voice services.

[0446] - Support for rejecting paging requests.

[0447] - Support for paging restrictions.

[0448] Otherwise, a UE with multi-USIM feature capabilities but not intending to use such capabilities shall not indicate support for one or more of these multi-USIM features.

[0449] A UE operating no more than two USIMs shall indicate non-support for multi-USIM features.

[0450] Note: A UE with more than one USIM does not need to use multi-USIM features on all USIMs.

[0451] <UE Configuration, Subscription Aspects, and Storage>

[0452] Various examples of this disclosure can also be applied to UE configuration, subscription aspects, and storage.

[0453] To use CAG, a UE supporting CAG (indicated as part of UE 5GMM core network capabilities) can be pre-configured or (re)-configured with the following CAG information, which is included in the subscription as part of mobility restrictions:

[0454] [[ID=--]]- Allowed CAG list, i.e., a list of CAG identifiers to which the UE is allowed access; and

[0455] - Optionally, a CAG-only indication, which indicates whether the UE is only allowed to access the 5GS via CAG cells (for information on how the UE identifies whether a cell is a CAG cell, see TS 38.304

[50] ); and

[0456] - Optionally, validity conditions (i.e. time and / or location) for each CAG identifier;

[0457] NOTE: The location validity information is used to assist the UE in searching for CAG cells and is not used for any enforcement.

[0458] The HPLMN may configure or reconfigure the above CAG information to the UE using the UE configuration update procedure for access and mobility management related parameters described in clause 4.2.4.2 of TS 23.502.

[0459] The above CAG information is provided by the HPLMN on a per-PLMN basis. In a PLMN, the UE shall only consider the CAG information provided for that PLMN. The CAG identifier with validity conditions shall be provided to the UE only if the UE indicates support for CAG with validity conditions. If the UE does not support CAG with validity conditions, the AMF shall include in the allowed CAG list:

[0460] - a CAG identifier that is not associated with a validity condition; and

[0461] - a CAG identifier associated with a temporal validity condition and excluding any validity condition if the temporal validity condition is satisfied; and

[0462] - A CAG identifier that is associated only with a location validity condition and does not include the location validity condition.

[0463] When the time validity condition becomes invalid, the AMF shall update the allowed CAG list of the unsupported UE to remove the corresponding CAG identifier that does not meet the time validity condition.

[0464] For example, when sending a CAG message to the AMF, the UDM can decide whether to include the validity condition based on whether the AMF supports the validity condition. For example, if the AMF supports the validity condition, the validity condition is included with the CAG message. If the AMF does not support the validity condition, the UDM can directly check the validity condition. Only when the validity condition is met can the UDM exclude the validity condition and send only the CAG identifier that meets the validity condition in the CAG message. If the UDM wants to know the exact location / time zone information of the terminal, it can subscribe to AMF events related to the terminal's location / time zone information.

[0465] When the subscribed CAG information changes, the UDM may set a CAG information subscription change indication and send the indication to the AMF. When the UDM indicates that the CAG information in the access and mobility subscription data has changed, the AMF may provide the CAG information to the UE. When the AMF receives an indication from the UDM that the CAG information in the access and mobility subscription has changed, the AMF may use the CAG information received from the UDM to update the UE. Once the AMF has updated the UE and received an acknowledgment from the UE, the AMF may notify the UDM that the update was successful. The UDM may remove the CAG information subscription change indicator flag.

[0466] The AMF may use the UE configuration update procedure after the registration procedure is completed, or update the UE by including new CAG information in a Registration Accept, Registration Reject, De-registration Request, or Service Reject.

[0467] When the UE is roaming and the serving PLMN provides CAG information, the UE may only update the CAG information provided for the serving PLMN and not update the CAG information stored for other PLMNs. When the UE is not roaming and the HPLMN provides CAG information, the UE may use the received CAG information for all PLMNs to update the CAG information stored in the UE.

[0468] The UE stores the latest available CAG information for all provided PLMNs and may retain this information even when the UE is de-registered or switched off.

[0469] CAG information can be applied to 5GS.

[0470] NOTE: CAG information does not affect whether and how the UE accesses 5GS via non-3GPP access.

[0471] <Network and cell (re)selection and access control>

[0472] Various examples of the present disclosure may be applied to network and cell (re)selection and access control.

[0473] The assumptions for network and cell selection and admission control are as follows:

[0474] -CAG cells can broadcast information so that only UEs supporting CAG can access the cell;

[0475] Note: The above means that the cell is a CAG cell or a regular PLMN cell. For network sharing scenarios between SNPN, PNI-NPN and PLMN, refer to clause 5.18 of TS 23.501.

[0476] - To prevent authorized UEs from accessing the NPN in case of network congestion / overload, the existing mechanisms defined in clause 5.19 for control plane load control, congestion and overload control may be used, and the access control and barring functions described in clause 5.2.5 or unified access control using access categories defined in TS 24.501 may be used.

[0477] - For automatic and manual network selection related to CAG, please refer to TS 23.122;

[0478] - For aspects of cell (re)selection, see TS 38.304;

[0479] - Mobility restriction shall be able to restrict the UE's mobility according to the allowed CAG list (if configured in the subscription). As described in clause 5.30.3.3, mobility restriction indicates whether the UE is only allowed to access the 5GS via CAG cells (if configured in the subscription);

[0480] - If a CAG identifier is associated with a time validity condition as described in clause 5.30.3.3, the AMF and NG-RAN shall check whether the time validity condition is met. If the UE is accessing a cell that supports a CAG identifier in the allowed CAG list and the time validity condition for this CAG identifier is invalid, the NG-RAN may trigger the handover procedure.

[0481] - During the transition from CM IDLE to CM CONNECTED and during registration following connected mode mobility from E-UTRAN to NG-RAN as described in clause 4.11.1.2.2 of TS 23.502 [3]:

[0482] - As described in clause 4.11.1.2.2 of TS 23.502, during the transition from CM IDLE to CM CONNECTED and during registration following connected mode mobility from E-UTRAN to NG-RAN:

[0483] -AMF can check whether mobility restrictions allow UE access:

[0484] NOTE 2: It is assumed that the AMF is aware of the CAG identifier(s) supported by the CAG cell via NG-RAN.

[0485] - If the UE accesses the 5GS via a CAG cell and if at least one of the CAG identifier(s) received from the NG-RAN is part of the UE's allowed CAG list, the AMF accepts the NAS request;

[0486] - If the UE accesses the 5GS via a CAG cell and if none of the CAG identifiers received from the NG-RAN is part of the UE's allowed CAG list, the AMF rejects the NAS request and the AMF shall include the CAG information in the NAS reject message. The AMF shall then release the NAS signalling connection for the UE by triggering the AN release procedure; and

[0487] - There may be a situation where the UE accesses the 5GS via a non-CAG cell and the UE's subscription includes an indication that the UE can only access CAG cells. In this case, the AMF shall reject the NAS request and the AMF shall include the CAG information in the NAS reject message. The AMF shall then trigger the AN release procedure to disconnect the NAS signaling to the UE.

[0488] During the transition from the RRC Inactive state to the RRC Connected state, the following operations may occur:

[0489] -The UE may initiate an RRC resumption procedure in a CAG cell to transition from the RRC inactive state to the RRC connected state. In this case, if the CAG identifiers supported by the CAG cell are not included in the UE's allowed CAG list according to the mobility restriction received from the AMF, or if the allowed CAG list is not received from the AMF, the NG-RAN may reject the UE's RRC resumption request.

[0490] - When a UE initiates an RRC resumption procedure in a non-CAG cell to transition from the RRC Inactive state to the RRC Connected state, the NG-RAN may reject the UE's resumption request if, according to the mobility restriction received from the AMF, the UE is only allowed to access CAG cells.

[0491] During an intra-NG-RAN connected mode mobility procedure (e.g., a handover procedure), the following actions may occur:

[0492] - if the target is a CAG cell and none of the CAG identifiers supported by that CAG cell is part of the UE's allowed CAG list in the mobility restriction list, or if the allowed CAG list is not received from the AMF, the source NG-RAN does not hand over the UE to the target NG-RAN node;

[0493] - If the UE is only allowed to access CAG cells based on the mobility restriction list, the source NG-RAN does not hand over the UE to a non-CAG cell;

[0494] - If the target cell is a CAG cell and none of the CAG identifiers supported by the CAG cell is part of the UE's allowed CAG list in the mobility restriction list, or if the allowed CAG list is not received from the AMF, the target NG-RAN may reject the N2 based handover procedure;

[0495] If the target cell is a non-CAG cell and the UE is only allowed to access CAG cells based on the mobility restriction list, the target NG-RAN may reject the N2-based handover procedure.

[0496] - For updates of mobility restrictions, the following examples may apply:

[0497] - If the AMF receives Nudm_SDM_Notification from the UDM and determines that the allowed CAG list or whether the UE is only allowed to access CAG cells has changed, the following may apply: The AMF may update the mobility restrictions of the UE and NG-RAN accordingly according to the conditions described in clause 4.2.4.2 of TS 23.502.

[0498] NOTE: If the UE is accessing the network for emergency services, the AMF conditions in clause 5.16.4.3 may apply.

[0499] Various examples of the present disclosure can also be applied to the following examples.

[0500] <Modification of AN release conditions due to update of allowed CAG list>

[0501] For example, based on an update of the allowed CAG list, the AN release conditions may be modified.

[0502] An updated list of allowed CAGs is under discussion.

[0503] If the UE's current serving cell is not included in the updated allowed CAG list, the AMF may trigger the AN release procedure. This procedure may be applied to the UE configuration update procedure as follows:

[0504] “The AMF may receive a Nudm_SDM_Notification to initiate the UE configuration update procedure, and the CAG information may have changed such that the CAG identifier is removed from the allowed CAG list, or the UE is only allowed to access CAG cells. In this case, the AMF may trigger the AN release procedure for UEs that are not receiving emergency services to disconnect the NAS signalling.”

[0505] Add a validity condition to each entry in the allowed CAG list, which can be described as follows:

[0506] "If the validity condition of an entry in the allowed CAG list changes between valid and invalid, the AMF may update the allowed CAG list in mobility restriction to the NG-RAN."

[0507] In other words, according to the prior art, whenever the validity condition changes and the UE's current serving cell is not in the allowed CAG list, the AMF should trigger the AN release procedure. The UE can receive home network services while receiving localized services. Therefore, if the UE has an ongoing service (e.g., a voice call), the service may be interrupted by the network, affecting the user experience.

[0508] There is also the issue of UDM operation being ambiguous when the AMF does not support CAG with validity conditions (such as in the case of roaming).

[0509] As explained below, when the AMF updates the allowed CAG list to the NG-RAN, the AMF may not trigger the AN release procedure.

[0510] The UDM operation when the AMF does not support CAG with validity conditions can be described.

[0511] According to the prior art, whenever the CAG validity condition changes, the UE service may be interrupted. Based on the following discussion, these problems can be solved.

[0512] In addition to the previously described <Network and Cell (Re)Selection and Access Control>, the following may apply.

[0513] During the transition from the RRC Inactive state to the RRC Connected state, the following operations may be performed:

[0514] - The UE may initiate an RRC resumption procedure for state transition from RRC Inactive to RRC Connected in a CAG cell. In this case, if none of the CAG identifiers supported in the CAG cell is included in the UE's allowed CAG list according to the mobility restriction received from the AMF, or if the allowed CAG list is not received from the AMF, the NG-RAN may reject the UE's RRC resumption request.

[0515] -The UE may initiate an RRC resume procedure for state transition from RRC Inactive to RRC Connected in a non-CAG cell. In this case, if the UE is only allowed to access CAG cells according to the mobility restriction received from the AMF, the NG-RAN shall reject the UE's resume request.

[0516] - If the AMF determines that the validity conditions of the allowed CAG list have changed, the updated allowed CAG list shall not be provided to the NG-RAN. The following interpretation may also apply:

[0517] -AMF can update the mobility restrictions of NG-RAN. AMF can trigger the AN release procedure.

[0518] - If the UE does not support CAG with validity information, the AMF may update the UE with the allowed CAG list.

[0519] NOTE: There may be cases where the AMF does not support CAG with validity conditions, such as in roaming situations. In this case, it is up to the operator policy to determine whether the UDM provides CAG information that satisfies the validity conditions (no validity conditions) to the AMF, and whether the CAG information is updated whenever the conditions change.

[0520] For example, if a CAG list update is required due to a subscription change on the terminal, the AMF may perform an AN release. If a CAG list update is required due to a change in validity conditions (no subscription change), the AMF may keep the terminal in connected mode without performing an AN release.

[0521] NOTE: If the UE accesses the network for emergency services, the AMF conditions in clause 5.16.4.3 of TS 23.501 may apply.

[0522] Furthermore, various examples of the present disclosure can be applied to the following examples.

[0523] For the previously described <Modification of AN release conditions due to update of allowed CAG list>, the following may additionally apply.

[0524] Reference Figure 9 The example in will describe an example process for UE configuration update of access and mobility management related parameters.

[0525] This procedure may be initiated by the AMF when it wants to update access and mobility management related parameters in the UE configuration.

[0526] This procedure may also be used to trigger the UE to perform the following example procedures based on network indication. This procedure may be, for example, a procedure to modify NAS parameters that require negotiation (e.g., MICO mode) in the CM connected state, or a mobility registration update procedure to direct the UE towards the EPC as specified in clause 5.31.3 of TS 23.501, or a mobility registration update procedure to allow NSSAI changes if re-registration is required after the UE enters the CM idle state. If a registration procedure is required, the AMF shall provide the UE with an indication to initiate the registration procedure.

[0527] If applicable, the UE configuration update shall be sent via the access type (e.g. 3GPP access or non-3GPP access) to which the UE configuration update applies. If the AMF wants to update the NAS parameters of the UE that require UE authorization, the AMF may indicate to the UE whether the UE should authorize the command. The AMF shall not request confirmation of the NITZ command. The AMF may request authorization for NSSAI information (e.g. allowed NSSAI), 5G-GUTI, TAI list and mobility restrictions, LADN information, MICO, operator-defined access class definition, PLMN-assigned UE radio function ID, and SMS subscription.

[0528] The following figures are intended to illustrate specific embodiments of the present disclosure. The naming of specific devices or the naming of specific signals / messages / fields shown in the figures are for illustrative purposes only, and the technical functions of this specification are not limited to the specific naming used in the following figures.

[0529] Figure 9 An example of a UE configuration update procedure according to one embodiment of the present disclosure is illustrated.

[0530] Figure 9 The example in shows an example of a UE configuration update procedure for access and mobility management related parameters.

[0531] 0. The AMF may determine that a UE configuration change is required or that the UE needs to perform a registration procedure for various reasons. For example, the various reasons may include a change in UE mobility, NW policy, receiving a subscriber data update notification from the UDM, a change in network slice configuration, a need to assign a UE radio function ID assigned by the PLMN, or a need to change enhanced coverage restriction information in the UE context. Here, the change in network slice configuration may include a change in the NSSRG information in the subscription information specified in clause 5.15.12 of TS 23.501 or a change in the NSAG information specified in clause 5.15.14 of TS 23.501. If the UE is in the CM Idle state, the AMF may wait until the UE enters the CM Connected state or triggers a network-triggered service request.

[0532] NOTE 1: It is up to the network implementation to decide whether the AMF can wait until the UE is in CM connected state or triggers a network-triggered service request.

[0533] NOTE 2: The AMF may check whether the network slice configuration needs to be updated by using the Nnssf_NSSelection_Get service operation. In this case, the AMF may compare the stored information with the output from the NSSF to decide whether an update to the UE is required.

[0534] When the coverage area restriction of a UE is updated, the AMF may include the mobility restriction list in the N2 message conveying the UE configuration update command to the UE.

[0535] 1. The AMF may send a UE Configuration Update Command message to the UE. The AMF may send a UE Configuration Update Command message including one or more UE parameters to the UE. The one or more UE parameters may include the following items: Configuration Update Indication, 5G-GUTI, TAI List, Allowed NSSAI, Mapping of Allowed NSSAI, Configured NSSAI of Serving PLMN, Mapping of Configured NSSAI, [NSSRG Information], Rejected S-NSSAI, NITZ, Mobility Restriction, LADN Information, MICO, Operator-defined Access Class Definition, SMS Subscription Indication, [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID Deletion Indication], ["List of (Multiple) PLMNs for Disaster Conditions"], [Disaster Roaming Waiting Range Information], [Disaster Return Waiting Range Information], [MPS Priority], [MCX Priority], [UAS Service Indication]. Optionally, the AMF may update the rejected S-NSSAI in the Update UE Configuration Command.

[0536] If the AMF wishes to update these NAS parameters without performing the UE registration procedure, the AMF may include one or more of the following items in the UE Configuration Update Command message: 5G-GUTI, TAI list, allowed NSSAI, mapping of allowed NSSAI, configured NSSAI of the serving PLMN, mapping of configured NSSAI, rejected S-NSSAI, network identity and time zone (NITZ), mobility restriction parameters, LADN information, operator-defined access class definition, UE radio capability ID assigned by the PLMN, or SMS subscription indication.

[0537] The AMF may also include a configuration update indication parameter in the UE configuration update command to indicate whether the settings have been updated:

[0538] - A network slice subscription change has occurred;

[0539] - The UE shall acknowledge the command; and

[0540] - Whether to request the registration process.

[0541] - A network slice subscription change has occurred;

[0542] - The UE shall acknowledge the command; and

[0543] - Whether to request the registration process.

[0544] When the AMF indicates a network slice subscription change, the UE locally deletes all network slice configurations for all PLMNs and, if possible, updates the configuration of the current PLMN based on the received information. If the AMF indicates a network slice subscription change, the UE receives a confirmation request in step 2.

[0545] The AMF may also include the new configured NSSAI of the serving PLMN in the UE Configuration Update Command message. In this case, the AMF shall also include the new allowed NSSAI and the mapping of the associated allowed NSSAI, if available. The AMF shall include the new allowed NSSAI unless the AMF cannot determine the new allowed NSSAI after the subscribed S-NSSAI is updated (in which case the AMF shall not include any allowed NSSAI in the UE Configuration Update Command message).

[0546] The UE may indicate in the UE 5GMM Core Network Function that it supports subscription-based restriction of the network slice co-registration capability. In this case, if available, the AMF may include the NSSRG information defined in clause 5.15.12 of TS 23.501 in the UE Configuration Update Command message. If the UE does not indicate support for subscription-based restriction of the network slice co-registration capability and the UE's subscription information includes NSSRG information, the AMF may provide the configured NSSAI to the UE. In this case, the configured NSSAI may include the S-NSSAI according to clause 5.15.12 of TS 23.501.

[0547] The UE may indicate in the 5G MM core network capabilities that it supports the NSAG functionality. In this case, if available, the AMF may include the NSAG information defined in clause 5.15.14 of TS 23.501 in the UE Configuration Update Command message. The AMF may include the NSAG information when providing a new configuration NSSAI including an S-NSSAI with an associated NSAG value, or when the NSAG information of some S-NSSAI in the configuration NSSAI changes. Once the NSAG information is provided to the UE, the AMF may request the UE to acknowledge the UE Configuration Command message.

[0548] The UE and AMF support RACS as defined in clause 5.4.4.1a of TS 23.501 and the AMF may already have UE radio capabilities other than NB-IoT radio capabilities for the UE and may configure the UE radio capability ID for the UE. In this case, the AMF may provide the UE with the UE radio capability ID for the UE radio capabilities returned to the AMF by the UCMF in the Nucmf_Assign service operation for that UE.

[0549] If the UE needs to be redirected to a dedicated band for S-NSSAI, the AMF can determine the target NSSAI on its own or by interacting with the NSSF using Nnssf_NSSelection_Get including the rejected S-NSSAI and the allowed NSSAI for RA. The AMF can determine the RFSP index associated with the target NSSAI by interacting with the PCF using Npcf_AMPolicyControl_Update including the target NSSAI to retrieve the corresponding RFSP index, or based on local configuration if PCF is not deployed. The target NSSAI and the RFSP index associated with the target NSSAI are provided to the NG-RAN in the N2 message carrying the UE Configuration Update Command message.

[0550] If the UE and AMF support disaster roaming services, the AMF may include the "PLMN list for disaster conditions", disaster roaming standby range information and disaster return standby range information as specified in TS 23.501 in the UE Configuration Command message. When the disaster conditions no longer apply, the serving AMF providing the disaster roaming service may inform the UE as specified in clause 5.40.5 of TS 23.501.

[0551] If the AMF receives a Subscriber Data Update Notification including MPS priority or MCX priority from the UDM, the AMF may include the MPS priority or MCX priority, respectively, in the UE Configuration Update Command as specified in clause 5.22.2 of TS 23.501.

[0552] If the UAS service is enabled or disabled (e.g. because a common subscription is part of the UE subscription data retrieved at UDM change time), the AMF may include an indication in the UE Configuration Update Command that the UAS service is enabled or disabled.

[0553] If the UE indicates support for per-S-NSSAI DNN and LADN in the UE MM Core Network Function during the registration procedure specified in clause 4.2.2.2.2, the AMF may include per-S-NSSAI DNN and LADN information.

[0554] 2a. The UE may send a UE Configuration Update Complete message to the AMF.

[0555] If the UE Configuration Update Indication requires confirmation of the UE Configuration Update Command, the UE shall send a UE Configuration Update Complete message to the AMF. The AMF shall request confirmation of all UE configuration updates, except when only NITZ is provided. If the registration procedure is not required, steps 3a, 3b, 3c, and 4 shall be omitted. If the UE Configuration Update Command message includes a Configuration Update Indication and a registration procedure is required based on other NAS parameters included in the UE Configuration Update Command, the UE shall perform steps 3a or 3b or steps 3c+4 as applicable.

[0556] If the PLMN-assigned UE Radio Capability ID is included in step 1, the AMF may store the UE Radio Capability ID in the UE context upon receiving the UE Configuration Update Complete message.

[0557] If the UE receives an instruction from the PLMN to delete the assigned UE radio function ID in step 1, the UE may delete the UE radio function ID assigned to the PLMN from the PLMN. If the UE configuration update is only used for this purpose, the subsequent steps will be omitted.

[0558] 2b. [Conditional] The AMF shall also use the Nudm_SDM_Info service operation to provide confirmation to the UDM that the UE has received the CAG information as part of the mobility restriction (if the CAG information has been updated) or the network slice subscription change indication (if indicated in step 1) and acted accordingly.

[0559] 2c.AMF can update RAN.

[0560] [Conditional] If the AMF has reconfigured the 5G-GUTI by 3GPP access, the AMF may inform the NG-RAN of the new UE Identity Index value (derived from the new 5G-GUTI) after receiving confirmation from the UE in step 2a.

[0561] [Conditional] There may be a situation where the UE is registered in the same PLMN via 3GPP access and non-3GPP access, the AMF reconfigures the 5G-GUTI via non-3GPP access, and the UE is in CM connected state via 3GPP access. In this case, the AMF may notify the NG-RAN of the new UE Identity Index value (derived from the new 5G-GUTI) after receiving the authorization from the UE in step 2a.

[0562] [Conditional] If the AMF has configured a UE Radio Capability ID assigned by the PLMN for the UE, upon receiving confirmation from the UE in step 2a, the AMF notifies the NG-RAN of the UE Radio Capability ID.

[0563] [Conditional] The UE's mobility restrictions have been updated, but they may not have been provided in the N2 message carrying the UE Configuration Update Command. In this case, the AMF may provide the updated mobility restrictions to the NG-RAN unless the AMF has released the UE in step 2c. The specific operation is as follows.

[0564] Based on the Nudm_SDM_Notification received by the AMF, the AMF may initiate a UE configuration update procedure and the CAG identifier may be removed from the allowed CAG list, or the CAG information may be changed so that the UE is only allowed to access CAG cells. In this case, the AMF may trigger the AN release procedure for the UE not receiving emergency services to release the NAS signaling connection as specified in TS 23.501.

[0565] If the AMF updates the allowed CAG list to the NG-RAN due to a change in validity conditions, the following operations may be performed. For example, the AMF may forward the updated allowed CAG list to the NG-RAN without triggering the AN release procedure. In another example, the AMF may trigger the AN release procedure for a UE that is not receiving emergency services to disconnect from NAS signaling.

[0566] NOTE: If the validity conditions apply just before the NG-RAN enforces the allowed CAG list, the AMF may trigger the AN release procedure without sending the updated allowed CAG list to the NG-RAN.

[0567] There may be cases where the UE supports CAGs but does not support CAGs that include validity conditions. In this case, if an entry in the allowed CAG list is associated with a validity condition in the subscription data and the validity condition is evaluated as true, the CAG identifier of the corresponding entry in the subscription data may be provided to the UE without the validity condition. If the validity condition is evaluated as false, the AMF may remove the CAG identifier from the entry in the allowed CAG list.

[0568] For example, if the evaluation result of the validity condition of an entry in the Allowed CAG List changes between true and false, the AMF may update the Allowed CAG List in the Cellular Restrictions. In this case, if the evaluation of the validity condition changes from true to false, the AMF may update the Allowed CAG List if the AMF has not disconnected the NAS signalling connection with the UE (based on the operator's policy).

[0569] A change in the validity conditions may require the AMF to update the allowed CAG list to the NG-RAN. In this case, for UEs not receiving emergency services, the AMF may update the allowed CAG list to the NG-RAN and maintain the NAS signalling association, or it may not update the allowed CAG list to the NG-RAN and trigger the AN release procedure to release the NAS signalling association.

[0570] NOTE: If validity conditions need to be applied before the NG-RAN enforces the allowed CAG list, the AMF may trigger AN release without sending the updated allowed CAG list to the NG-RAN.

[0571] The validity conditions may change, causing the AMF to update the allowed CAG list to the NG-RAN. In this case, the AMF may start a timer and not perform AN release for the terminal until the timer expires, i.e., it may keep the terminal connected. Then, when the timer expires, the AMF may perform AN release for the terminal. The timer may be stopped if the terminal becomes idle or if a handover occurs. In order to know when a handover occurs without updating the terminal's downlink N3 tunnel information, the AMF may use the NG-RAN location reporting procedure to the NG-RAN. Accordingly, the AMF may request the NG-RAN to report to the AMF whether the current serving cell has changed.

[0572] 2d. [Optional] In step 2a, a new 5G-GUTI is established for the UE via non-3GPP access, and the UE may be registered in the same PLMN via 3GPP access and non-3GPP access. In this case, the UE may forward the new 5G-GUTI to lower layers of the 3GPP access.

[0573] If the UE has configured a new 5G-GUTI via 3GPP access in step 2a, the UE may forward the new 5G-GUTI to the lower layers of the 3GPP access.

[0574] 3a. [Conditional] If only NAS parameters that can be updated without transitioning from CM Idle (e.g., MICO mode, enhanced coverage limitation information) are included, the UE may initiate a registration procedure immediately after confirmation to renegotiate the updated NAS parameters with the network. In this case, steps 3b, 3c, and 4 may be omitted.

[0575] 3b. [Conditional] The new allowed NSSAI and / or the new allowed NSSAI mapping and / or the new configured NSSAI provided by the AMF to the UE in step 1 do not affect the existing connection with the AMF. In this case, after receiving the authorization in step 2, the AMF does not need to disconnect the NAS signaling with the UE and does not need to register immediately. The UE can start immediately by using the new allowed NSSAI and / or the new allowed NSSAI mapping. If one or more PDU sessions use an S-NSSAI that is not included in the new allowed NSSAI, the AMF shall indicate the corresponding PDU session ID to the SMF, and each SMF may release these PDU sessions. Before the UE performs the registration procedure and includes the requested NSSAI based on the new configured NSSAI, the UE shall not associate with the S-NSSAI included in the newly established NSSAI of the serving PLMN but not included in the new allowed NSSAI. Steps 3c and 4 may be omitted.

[0576] Depending on the policy, the AMF may provide an indication that a registration procedure is required even if the UE configuration update command in step 1 does not affect existing connections to the network slice, in which case only step 3c may be omitted.

[0577] 3c. [Conditional] The new allowed NSSAI and / or the mapping of the new allowed NSSAI to the new allowed NSSAI and / or the newly established NSSAI provided by the AMF to the UE in step 1 may affect the existing connection with the AMF. In this case, the AMF may provide an indication that the UE needs to initiate a registration procedure.

[0578] 4. [Conditional] After receiving the authorization in step 2, if there is no established PDU Session associated with a regulatory priority service, the AMF may trigger the AN release procedure to release the NAS signaling association of the UE. If there is at least one established PDU Session associated with a regulatory priority service, the AMF may notify the SMF to release the PDU Session associated with the non-regulatory priority service of the UE.

[0579] The AMF shall reject all NAS messages from the UE carrying PDU Session Establishment Requests for non-emergency PDU Sessions until the UE has successfully completed the required registration procedures.

[0580] After the UE enters the CM IDLE state, the UE may initiate a registration procedure with registration type MOBILITY REGISTRATION UPDATE and the UE may not include the 5G-S-TMSI or GUAMI in the access stratum signaling, but may include the requested NSSAI in the access stratum signaling under the conditions specified in clause 5.15.9 of TS 23.501. If a PDU Session related to emergency services has been established and the UE is instructed to perform the registration procedure, the UE may initiate the registration procedure only after the PDU Session related to emergency services has been released.

[0581] Note that even if the UE receives the UE Configuration Update Command without any instruction requiring it to perform re-registration, the UE's registration procedure may be triggered due to other reasons.

[0582] The following figures are intended to illustrate specific embodiments of the present disclosure. The naming of specific devices or specific signals / messages / fields shown in the figures is for illustrative purposes only, and the technical functions of the present disclosure are not limited to the specific names used in the following figures.

[0583] Figure 10 An example of a process performed according to one embodiment of the present disclosure is illustrated.

[0584] It should be noted that Figure 10 The process shown in the figure is only an example and the scope of this disclosure is not limited to Figure 10 Limitations of the examples in .

[0585] For example, for Figure 10 For example, Figures 1 to 9 The operations described in the examples of the present disclosure may also be applied. For example, any operations, contents, etc. described in the various examples of the present disclosure may be applied even in Figure 10 Those operations, contents, etc. are not directly described in the examples.

[0586] In step S1001, the UE may send a registration request message to the AMF via the NG-RAN.

[0587] For example, the registration request message may include the MM core network capability. The core network capability information may include information related to whether the UE supports CAG with validity information (CAG with validity information).

[0588] The AMF may send a Registration Accept message to the UE. The Registration Accept message may include an allowed CAG list. For example, the Registration Accept message may include mobility restriction information. The mobility restriction information may include CAG information. The CAG information may include an allowed CAG list. For example, if the UE supports CAG and the AMF needs to update the UE's CAG information, the AMF may include the CAG information in the mobility restriction included in the Registration Accept message.

[0589] For example, the AMF may send a downlink NAS transport message to the NG-RAN. For example, the AMF may initiate the procedure by sending a downlink NAS transport message to the NG-RAN node. If the logical NG association associated with the UE has not yet been established, the AMF shall assign a unique AMF UE NGAP ID to the UE for use and include it in the downlink NAS transport message, and the NG-RAN node may receive the AMF UE NGAP ID IE in the downlink NAS transport message to establish the logical NG association associated with the UE.

[0590] Note that if the Mobility Restriction List IE is included in the downlink NAS transport message, the NG-RAN node may overwrite the previously stored mobility restriction information in the UE's context. The NG-RAN node may use the information included in the Mobility Restriction List IE as shown in the following example:

[0591] - The NG-RAN node determines the target of subsequent mobility operations and provides the UE with information about the target of the mobility operation;

[0592] -Select appropriate SCG for dual connectivity operation;

[0593] - Assigning an appropriate RNA to the UE when moving the UE to the RRC Inactive state.

[0594] In step S1002, the AMF may evaluate the validity conditions of the entries included in the allowed CAG list. For example, if the NG-RAN and / or the UE supports CAG based on validity information, the NG-RAN and / or the UE may also evaluate the validity conditions.

[0595] In step S1003, the AMF may determine whether the allowed CAG list needs to be updated.

[0596] For example, based on a change in the validity condition of one or more entries in the Allowed CAG List between true and false, the AMF may determine that the Allowed CAG List needs to be updated for the NG-RAN.

[0597] For example, based on the need for the AMF to update the allowed CAG list, the AMF may send a downlink NAS transport message including the updated allowed CAG list to the NG-RAN while maintaining NAS signaling.

[0598] In another example, the AMF may trigger the AN release procedure to disconnect the NAS signaling based on the need to update the allowed CAG list.

[0599] If the UE does not support CAG based on the validity information and the validity condition is evaluated as true, then based on at least one entry in the allowed CAG list being associated with the validity information, the AMF may send the CAG identifier of the at least one entry to the UE without the validity information. If the validity condition changes to false, the AMF may delete the CAG identifier of the at least one entry.

[0600] If the AMF updates the allowed CAG list to the NG-RAN due to a change in validity conditions, the following actions may occur. For example, the AMF may forward the updated allowed CAG list to the NG-RAN without triggering the AN release procedure. In another example, the AMF may trigger the AN release procedure for UEs that are not receiving emergency services to disassociate from NAS signaling. The AMF may disassociate NAS signaling by triggering the AN de-anonymization procedure for UEs that are not receiving emergency services.

[0601] Note that if the validity condition is applied just before the NG-RAN enforces the allowed CAG list, the AMF may trigger the AN release procedure without sending the updated allowed CAG list to the NG-RAN.

[0602] There may be cases where the UE supports CAGs but does not support CAGs that include validity conditions. In this case, if an entry in the allowed CAG list is associated with a validity condition in the subscription data and the validity condition is evaluated as true, the CAG identifier for that entry in the subscription data may be provided to the UE without the validity condition. If the evaluation result of the validity condition changes to false, the AMF may remove the CAG identifier from that entry in the allowed CAG list. If the evaluation result of the validity condition changes to false, the CAG identifier may be removed.

[0603] For example, if the evaluation of the validity condition of an entry in the Allowed CAG List changes between true and false, the AMF may update the Allowed CAG List in Mobility Restriction. In this case, if the evaluation of the validity condition changes from true to false, the AMF may update the Allowed CAG List if the AMF has not disconnected the NAS signalling connection with the UE (based on the operator's policy).

[0604] A change in the validity conditions may require the AMF to update the allowed CAG list to the NG-RAN. In this case, for UEs not receiving emergency services, the AMF may update the allowed CAG list to the NG-RAN and maintain the NAS signalling association, or the AMF may not update the allowed CAG list to the NG-RAN and trigger the AN release procedure to release the NAS signalling association.

[0605] Note that if the validity conditions need to be applied just before the NG-RAN enforces the allowed CAG list, the AMF may trigger the AN release without sending the updated allowed CAG list to the NG-RAN.

[0606] If the UE supports CAG based on validity information, the following example operations may be performed: If the UE is connected to a CAG cell and the corresponding entry in the allowed CAG list configured in the UE is associated with validity information, the UE may trigger a cell reselection and / or network selection procedure if the evaluation of the validity condition changes.

[0607] To use CAG, for a UE that supports CAG as part of its 5G MM core network capabilities, the following may be configured based on mobility restrictions. For example, as part of mobility restrictions, the UE may be provisioned or (re)provisioned with the following CAG information included in the subscription:

[0608] - Allowed CAG list, i.e. a list of CAG identifiers that the UE can access; and

[0609] - Each entry in the allowed CAG list can be associated with time validity information.

[0610] The above CAG information may be provided by the HPLMN on a per-PLMN basis. Within a PLMN, the UE may only consider the CAG information provided for that PLMN. Entries in the allowed CAG list with validity conditions may only be provided to the UE if the UE indicates that it supports CAGs with validity information.

[0611] Various drawings according to the present disclosure may be applied alone or in combination with other drawings.

[0612] According to various embodiments of the present disclosure, the NG-RAN may determine whether a specific CAG is valid at a specific time or location to determine whether to continue serving the terminal. For example, the NG-RAN may notify the AMF of its capability to check the validity conditions of the CAG during the NG establishment process. For example, the AMF may forward the allowed CAG list information including the validity conditions to the NG-RAN based on the capabilities received from the NG-RAN. For example, based on the validity conditions, the NG-RAN may verify the CAG to continue serving the terminal, hand over to another NG-RAN, or disconnect the terminal.

[0613] For example, the terminal may not be able to check the validity conditions of the CAG. In this case, the AMF can still check the validity conditions of each CAG, set the allowed CAG list accordingly, and send it to the terminal. There may also be cases where some CAGs in the terminal's allowed CAG list may become invalid due to the validity conditions. In this case, the AMF can also send the updated allowed CAG list to the NG-RAN without triggering the AN to release and maintain the current NG connection.

[0614] The present disclosure may have various effects.

[0615] For example, according to various examples of the present disclosure, a validity condition may cause a specific CAG to change from valid to invalid. In this case, the NG-RAN and AMF can determine whether the terminal can continue to be served on the cell to which the terminal is connected without immediately disconnecting the terminal. In addition, even if the cell cannot continue to serve the terminal, the NG-RAN and / or AMF can hand over the terminal to another nearby cell so that the NG-RAN and AMF can continue to provide services to the terminal.

[0616] For example, according to various examples of the present disclosure, a network in which the validity of a specific CAG is changed by a validity condition can provide services to a terminal that does not support the CAG including the validity condition. In addition, even if some CAGs in the terminal's allowed CAG list are no longer valid due to the validity condition, the AMF may not trigger AN release. Therefore, the network can continue to provide services to the terminal.

[0617] The effects that can be obtained from the specific examples of the present disclosure are not limited to those listed above. For example, a person of ordinary skill in the relevant art can understand or infer various technical effects from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those explicitly set forth herein, but can include various effects that can be understood or inferred from the technical features of the present disclosure.

[0618] For reference, the operation of the terminal (eg, UE) described in this specification can be performed by Figures 1 to 4For example, a terminal (eg, UE) may be Figure 2 The first device 100 or the second device 200 of the present invention may be a first device 100 or a second device 200. For example, the operations of the terminal (e.g., UE) described herein may be processed by one or more processors 102 or 202. The operations of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that can be executed by one or more processors 102 or 202. The one or more processors 102 or 202 control the one or more memories 104 or 204 and the one or more transceivers 106 or 206, and may perform the operations of the terminal (e.g., UE) described herein by executing the instructions / programs stored in the one or more memories 104 or 204.

[0619] In addition, instructions for performing the operations of a terminal (e.g., UE) described in the present disclosure of this specification may be stored in a non-volatile computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories 104 or 204. Furthermore, the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operations of the terminal (e.g., UE) described in the present disclosure of this specification.

[0620] For reference, the operations of the network nodes (e.g., BM-SC, PCRF, GCSE AS, AMF, SMF, UPF, PCF, AUSF, UDM, etc.) or base stations (e.g., (R)AN, NG-RAN, gNB, E-UTRAN, etc.) described herein may be performed by the following Figures 1 to 3 For example, a network node or base station can be Figure 2 The first device 100 or Figure 2 The second device 200 of the present invention. For example, the operations of the network node or base station described herein may be processed by one or more processors 102 or 202. The operations of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that can be executed by one or more processors 102 or 202. The one or more processors 102 or 202 may perform the operations of the network node or base station described herein by controlling the one or more memories 104 or 204 and the one or more transceivers 106 or 206 and executing the instructions / programs stored in the one or more memories 104 or 204.

[0621] In addition, instructions for executing the operations of the network node or base station described in the present disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium. The storage medium may be included in one or more memories 104 or 204. Furthermore, the instructions recorded in the storage medium are executed by one or more processors 102 or 202 to facilitate the execution of the operations of the network node or base station.

[0622] In the above, the preferred embodiments have been exemplarily described, but the present disclosure of this specification is not limited to such specific embodiments, and thus, modifications, changes, or improvements may be made.

[0623] In the exemplary system described above, the method is described as a series of steps or blocks based on the flowchart, but is not limited to the order of the steps described. Some steps may occur in a different order or simultaneously with other steps as described above. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and may include other steps, or one or more steps of the flowchart may be deleted without affecting the scope of the rights.

[0624] The claims described herein may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims of this specification and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims of this specification and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. A method for performing communication, the method being performed by an access and mobility management function (AMF) and comprising: receiving a registration request message including core network capability information from a user equipment (UE), The core network capability information includes information related to whether the UE supports a closed access group (CAG) with validity information; Evaluate the validity conditions for inclusion of entries in the CAG list; and Based on a validity condition of a first entry included in the allowed CAG list changing between true and false, it is determined that the allowed CAG list needs to be updated for a new generation (NG)-random access node (RAN).

2. The method according to claim 1, further comprising: Based on the need for the AMF to update the allowed CAG list, while maintaining the NAS signaling connection, a downlink NAS transport message including the updated allowed CAG list is sent to the NG-RAN.

3. The method according to claim 1, further comprising: Based on the need for the AMF to update the allowed CAG list, the access network (AN) process is triggered to release the non-access stratum (NAS) signaling connection.

4. The method according to any one of claims 1 to 3, further comprising: Based on the UE not supporting CAG with the validity information, and one or more entries in the allowed CAG list are associated with the validity information, when the validity condition is evaluated to be true, CAG identifiers of the one or more entries are sent to the UE without a validity condition.

5. The method according to claim 4, further comprising: When the validity condition changes to false, removing the CAG identifier of the one or more entries.

6. An access and mobility management function (AMF) for performing communications, the AMF comprising: one or more transceivers; one or more processors; as well as one or more memories storing instructions and operatively coupled to the one or more processors, Wherein, based on the execution of the instructions by the one or more processors, the operations being performed include the method according to any one of claims 1 to 5.

7. A method for performing communication, the method being performed by a user equipment (UE) and comprising: Send a registration request message including core network capability information to the Access and Mobility Management Function (AMF), The core network capability information includes information related to whether the UE supports a closed access group (CAG) with validity information; receiving a Registration Accept message including a list of allowed CAGs from the AMF, The information related to whether the UE supports the validity information is used by the AMF to send the CAG identifiers of one or more entries included in the allowed CAG list to the UE based on the evaluation of the validity condition.

8. The method according to claim 7, further comprising: The CAG identifier of one or more entries is received from the AMF.

9. The method according to claim 7 or claim 8, Based on the UE not supporting CAG with the validity information, and the one or more entries in the allowed CAG list are associated with the validity information, when the validity condition is evaluated to be true, the CAG identifiers of the one or more entries are received without a validity condition.

10. The method according to claim 9, in, When the validity condition changes to false, removing the CAG identifier of the one or more entries.

11. A user equipment (UE) for performing communication, the UE comprising: one or more transceivers; one or more processors; as well as one or more memories storing instructions and operatively coupled to the one or more processors, Wherein, based on the execution of the instructions by the one or more processors, the operations being performed include the method according to any one of claims 7 to 10.

12. A device for mobile communications, comprising: one or more processors; as well as one or more memories storing instructions and operatively coupled to the one or more processors, Wherein, based on the execution of the instructions by the one or more processors, the operations being performed include the method according to any one of claims 7 to 10.

13. A non-transitory computer readable medium (CRM) storing instructions, in, Based on the instructions being executed by one or more processors, the one or more processors are caused to perform operations including the method according to any one of claims 7 to 10.

Images