Control information

Abstract

The present disclosure provides a method. The method may comprise the steps of: receiving control information related to an access technology; and performing PLMN selection, cell selection, or cell reselection on the basis of the control information related to the access technology.

Description

Control information

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] According to the prior art, there is a problem that mobility restrictions are not effectively applied to terminals.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include: receiving control information related to an access technology; and performing PLMN selection, cell selection, or cell reselection based on the control information related to the access technology.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include transmitting control information related to an access technology to a UE.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

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

[0015] FIG. 7 is a first example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

[0016] FIG. 8 is a second example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

[0017] FIG. 9 is a third example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

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

[0019] 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 wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

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

[0021] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0022] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0023] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0024] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0025] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

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

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

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

[0029] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0030] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

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

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

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

[0034] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0035] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0036] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

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

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

[0039] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0040] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0041] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

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

[0043] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

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

[0045] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

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

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

[0048] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0049] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0050] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

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

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

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

[0054] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0055] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

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

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

[0058] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0060] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

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

[0063] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0064] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0065] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

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

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

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

[0069] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

[0071] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0072] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0073] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

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

[0075] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0076] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0077] - AUSF (Authentication Server Function)

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

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

[0080] - USDF (Unstructured Data Storage Function)

[0081] - NEF (Network Exposure Function)

[0082] - I-NEF (Intermediate NEF)

[0083] - NRF (Network Repository Function)

[0084] - NSSF (Network Slice Selection Function)

[0085] - PCF (Policy Control Function)

[0086] - SMF (Session Management Function)

[0087] - UDM (Unified Data Management)

[0088] - UDR (Unified Data Repository)

[0089] - UPF (User Plane Function)

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

[0091] - AF (Application Function)

[0092] - UE (User Equipment)

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

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

[0095] - NWDAF (Network Data Analytics Function)

[0096] - CHF (CHarging Function)

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

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

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

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

[0101] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0102] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0103] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0104] The 5G system architecture includes the following benchmarks:

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

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

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

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

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

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

[0111] The following benchmarks illustrate the interactions that exist between NF services in NF.

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

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

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

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

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

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

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

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

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

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

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

[0123] In some cases, two NFs may need to be interconnected to serve a UE.

[0124] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

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

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

[0127] - Initial registration for 5GS; or

[0128] - mobility registration update; or

[0129] - Periodic registration update; or

[0130] - Emergency registration

[0131] The general registration procedures of Figures 5 and 6 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0132] The general registration procedures of Figures 5 and 6 can also be used to register a UE for a 3GPP connection when it is already registered for a non-3GPP connection, and vice versa. Registering a UE for a 3GPP connection when it is already registered for a non-3GPP connection scenario may require an AMF change.

[0133] First, the procedure of Fig. 5 is described.

[0134] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0135] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 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 an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

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

[0137] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

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

[0139] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0140] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0141] iv) Native 5G-GUTI allocated by another PLMN (if available);

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

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

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

[0145] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

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

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

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

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

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

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

[0152] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0153] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

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

[0155] (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 to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

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

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

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

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

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

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

[0162] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0163] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0164] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0165] (13) Step 13: When step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

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

[0167] (15) Step 15: New AMF can select PCF.

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

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

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

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

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

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

[0174] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0175] The allowed NSSAI (allowed NSSAI or partially allowed NSSAI) provided in the Registration Accept message is valid in the registration area and applies to all PLMNs that have a tracking area included in the registration area. The mapping of the allowed NSSAI (Mapping Of (partially) allowed NSSAI) maps the HPLMN S-NSSAI to each S-NSSAI of the allowed NSSAI. The mapping of the configured NSSAI maps the HPLMN S-NSSAI to each S-NSSAI of the configured NSSAI for the serving PLMN.

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

[0177] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0178] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

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

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

[0181] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

[0182] Describes examples of cell selection and cell reselection. For reference, 3GPP TS 38.304 V18.2.0 can be referenced.

[0183] The UE may perform measurements for cell selection and cell reselection as specified in TS 38.133 V18.5.0.

[0184] For reselection evaluation, the UE may evaluate the Srxlev and Squal of the non-serving cell. In this case, the UE may use the parameters provided by the serving cell, and for final confirmation of the cell selection criteria, the UE may use the parameters provided by the target cell for cell reselection.

[0185] By indicating the Radio Access Technology (RAT) associated with the selected Public Land Mobile Network (PLMN) and maintaining a list of forbidden registration areas and an equivalent PLMN, the NAS (e.g., the NAS layer of the UE) can control the RAT for which cell selection should be performed. The UE can select an appropriate cell based on RRC_IDLE state measurements or RRC_INACTIVE state measurements and cell selection criteria.

[0186] To expedite the cell selection process, the UE may use stored information about multiple RATs, if available.

[0187] When a UE camps on a cell, it may periodically search for a better cell based on cell reselection criteria. Once a better cell is found, the UE may select that cell. A cell change may also include a RAT change. Details on the performance requirements for cell reselection are specified in TS 38.133 V18.5.0.

[0188] The NAS (e.g., the NAS layer of the UE) may be informed when cell selection and reselection result in changes in the receiving system information relevant to the NAS.

[0189] For typical services, the UE camps on a suitable cell and monitors the control channel of that cell so that the UE can:

[0190] - The UE can receive system information from the PLMN or SNPN;

[0191] - The UE can receive registration area information (e.g., tracking area information) from the PLMN or SNPN; and

[0192] - The UE can receive other AS and NAS information; and

[0193] - When the UE is registered, the UE can receive paging messages and notification messages from the PLMN or SNPN, and the UE can initiate a transition to connected mode.

[0194] To effectively control RAT utilization, discussions have begun on the Enhancement of Controlling RAT Utilization (ECRATU) item. In this case, the controlled RAT is limited to the radio access technology (RAT) defined in TS 36.304 and TS 38.304. However, according to the prior art, the RAT classification defined in TS 36.304 and TS 38.304 does not distinguish between, for example, NR and NR satellite, which are different RAT types. In this case, the prior art processes NR and NR satellite together as the same NR RAT, which poses a problem in that NR non-satellites and NR satellites cannot be controlled differently. Therefore, a more efficient RAT restriction (e.g., RAT utilization restriction) operation needs to be discussed.

[0195] Additionally, the item was approved to control RAT at the NAS layer of the UE without affecting the AS layer of the UE. However, there may be limitations in controlling idle mobility at the NAS layer when idle mobility occurs. Therefore, it is necessary to consider whether additional operation definitions are needed for efficient RAT restriction at the AS layer as well. In summary, additional discussion is needed on the precise definition and scope of RAT for efficient RAT control, and which layers (e.g., NAS, AS (RRC), upper layers than NAS) require support for RAT restriction operations.

[0196] RAT restrictions can be defined as follows: RAT restrictions define the 3GPP and non-3GPP Radio Access Technologies (RATs) that a UE cannot access in a PLMN. In a restricted RAT, a UE based on its subscription cannot access the network for that PLMN. For 3GPP access and CM-CONNECTED states, the radio access network considers PLMN RAT restrictions when determining the target RAT and target PLMN during a handover or redirection procedure. RAT restrictions are enforced by the network and are not provided to the UE.

[0197] UDM may provide AMF with subscriber's NR access restriction information or E-UTRA access restriction information.

[0198] UDM can provide AMF with information related to a subscriber's NR access restrictions or E-UTRA access restrictions. For example, the information provided by UDM can be defined in TS 23.008 V18.1.0. The information provided by UDM can be configured by the operator based on subscription and roaming scenarios. For example, the information provided by UDM may include the following examples:

[0199] For NR, for example, information related to NR access restrictions provided by UDM may include:

[0200] - NR is not allowed as a primary RAT. However, one of the NR categories listed below may still be allowed;

[0201] - NR is not allowed as a secondary RAT;

[0202] - NR is not allowed as primary RAT in unlicensed bands;

[0203] - NR is not allowed as a secondary RAT in unlicensed bands;

[0204] - NR (Low Earth Orbit: LEO) satellite access is not permitted as a primary RAT;

[0205] - NR (Medium Earth Orbit: MEO) satellite access is not permitted as a primary RAT;

[0206] - NR (Geostationary Orbit: GEO) satellite access is not allowed as a primary RAT;

[0207] - NR (OTHERSAT) satellite access is not permitted as primary RAT;

[0208] - NR RedCap is not allowed as a primary RAT; or

[0209] - NR eRedCap is not allowed as a primary RAT.

[0210] For E-UTRA, for example, information related to E-UTRA access restrictions provided by UDM may include:

[0211] - E-UTRA is not accepted as primary RAT;

[0212] - E-UTRA is not permitted as a secondary RAT;

[0213] - E-UTRA is not permitted as a secondary RAT in unlicensed bands;

[0214] - NB-IoT is not allowed as primary RAT;

[0215] - LTE-M is not allowed as primary RAT;

[0216] - WB-E-UTRAN (LEO) satellite access is not permitted as primary access;

[0217] - WB-E-UTRAN (MEO) satellite access is not permitted as primary access;

[0218] - WB-E-UTRAN (GEO) satellite access is not permitted as primary access;

[0219] - WB-E-UTRAN (OTHERSAT) satellite access is not permitted as primary access;

[0220] - NB-IoT (LEO) satellite access is not allowed as primary access;

[0221] - NB-IoT (MEO) satellite access is not allowed as primary access;

[0222] - NB-IoT (GEO) satellite access is not allowed as primary access;

[0223] - NB-IoT (OTHERSAT) satellite access is not permitted as primary access;

[0224] - LTE-M (LEO) satellite access is not permitted as primary access;

[0225] - LTE-M (MEO) satellite access is not permitted as primary access;

[0226] - LTE-M (GEO) satellite access is not permitted as primary access; or

[0227] - LTE-M (OTHERSAT) satellite access is not permitted as primary access.

[0228] For all primary RAT restrictions to apply, the relevant RATs must be deployed within different tracking area codes, and subscribers must not be allowed network access in TAs using a particular RAT.

[0229] If all secondary RAT restrictions apply, the subscriber is not permitted to use this RAT as a secondary RAT.

[0230] The RAT type can identify the transport technology of the access network used for both 3GPP access and non-3GPP access. For example, the RAT type can identify NR, NB-IoT, untrusted non-3GPP, trusted non-3GPP, trusted IEEE 802.11 non-3GPP access, wired, wired-cable, wired-BBF, etc.

[0231] LTE-M is a 3GPP RAT type identifier used only in core networks. LTE-M is defined as a subtype of the E-UTRA RAT type, and can be used to identify E-UTRA in the core network when a UE indicates Category M.

[0232] NR RedCap is a 3GPP RAT type identifier used only in the core network. NR RedCap is defined as a subtype of the NR RAT type and can be used to identify NR in the core network when a UE displays NR RedCap.

[0233] NR eRedCap is a 3GPP RAT type identifier used only in the core network. NR eRedCap is defined as a subtype of the NR RAT type, and can be used to identify NR in the core network when a UE indicates NR eRedCap.

[0234] Primary RAT means the RAT of the master RAN node when Dual Connectivity is used; otherwise, Primary RAT means the RAT of the RAN node.

[0235] Secondary RAT refers to the RAT of the secondary RAN node.

[0236] However, RAT restriction according to the prior art is possible only when the terminal is in the CM-CONNECTED state, through a handover or redirection procedure. In this case, RAT restriction information applied by the network is not provided to the UE.

[0237] For example, network operators can restrict a terminal's mobility by setting mobility restrictions. However, according to the prior art, mobility restrictions information is only reported by the core network to the base station, and is not transmitted to the terminal. Therefore, if mobility occurs in idle mode, the terminal is unaware that mobility restrictions are applied. As a result, the terminal first attempts to access the network. Thereafter, the terminal either follows the mobility settings controlled by the network, or receives a rejection for the access attempt and retries access to a different network, resulting in a waste of signaling.

[0238] In fact, there have been concerns raised about increased signaling load caused by roaming devices, especially in situations where traditional European telecommunications networks struggle to provide service. Furthermore, previously discussed solutions have the drawback of requiring devices to first attempt to access restricted networks.

[0239] Regarding Access Stratum (AS), examples of authorization are described. For example, the network may determine whether to grant and / or authenticate a terminal's connectivity request to the core network and RAN nodes based on the terminal's subscription information.

[0240] Once a user is successfully identified and authenticated, authorization for the services the user can access can be evaluated based on the subscriber's 5GC connection and subscription (e.g., operator-imposed restrictions, roaming restrictions, current access type, and RAT type). This authorization can be performed during the UE registration process.

[0241] When performing inter-RAT mobility to or from NB-IoT, the tracking area in which the UE initiates the mobility registration procedure must not include both NB-IoT and other RAT (e.g. WB-E-UTRA, NR) cells. The AMF must not assign a TAI list containing NB-IoT and other RAT tracking areas to the UE.

[0242] An example network configuration is described. Currently, the network does not differentiate the TAI list by RAT for a tracking area (TA) supporting more than one RAT. Consequently, signaling overhead for Mobility Registration Updates may not be incurred. However, NB-IoT RAT is an exception.

[0243] To avoid additional signaling overhead caused by a Mobility Registration Update occurring for each RAT change, it may be desirable not to generate a RAT-specific TAI list for UEs supporting more than one RAT.

[0244] For 3GPP, based on the global RAN node ID associated with the N2 interface and the tracking area indicated by the NG-RAN, the AMF can determine the type of RAT the UE is camping on. If the UE accesses NR using an unlicensed band as defined in TS 23.501 V18.5.0 clause 5.4.8, an indication may be provided on the N2 interface as defined in TS 38.413 V18.1.0.

[0245] AMF can also determine more accurate RAT type information based on information received from NG-RAN:

[0246] - AMF can determine the RAT type as LTE-M as defined in TS 23.501 clause 5.31.20.

[0247] - AMF may determine the RAT type as NR using unlicensed bands as defined in TS 23.501 clause 5.4.8.

[0248] - AMF may determine the RAT type as one of the RAT types for satellite access, as defined in TS 23.501 clause 5.4.10.

[0249] - AMF may determine NR RedCap as a RAT type as defined in TS 23.501 clause 5.41.

[0250] For non-3GPP access, the AMF can determine the RAT type that the UE is camping on based on the 5G-AN node connected to the N2 interface as follows:

[0251] - If the 5G-AN node has a global N3IWF node ID, the RAT type is untrusted non-3GPP.

[0252] - If the 5G-AN node has a Global TNGF Node ID or a Global TWIF Node ID, the RAT type is Trusted Non-3GPP; and

[0253] - If the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF that supports a Wireline BBF access network, the RAT type is Wireline-BBF. If the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF that supports a wired cable access network, the RAT type is Wireline-Cable. If the two cannot be distinguished, the RAT type is Wireline.

[0254] According to prior art, access may not be granted to a UE supporting access in a specific RAT based on subscription information. In this case, the network may reject the UE's access attempt, resulting in signaling overhead and service continuity issues. For example, see C1-242122.

[0255] For example, a network entity involved in mobility (e.g., AMF) may send the following 5GMM cause to the UE:

[0256] For example, a network entity involved in mobility may send the 5GMM cause “Cause #12 - Tracking area not allowed” to the UE. This 5GMM cause may be sent to the UE when the UE requests service in a tracking area that the HPLMN or SNPN determines is not permitted for the UE to operate due to its subscription, or when the network initiates a deregistration request.

[0257] For example, a network entity involved in mobility may send the 5GMM cause “Cause #15 - No suitable cells in tracking area” to the UE. This 5GMM cause may be sent to the UE when the UE requests service in a tracking area in which the UE is not permitted to operate by subscription, or when the network initiates a de-registration request, or when the UE needs to find another allowed tracking area in the same PLMN or an equivalent PLMN or the same SNPN or an equivalent SNPN.

[0258] Note that the difference between Cause #15 and Cause #12 is that Cause #12 does not trigger the UE to search for other allowed tracking areas within the same PLMN or SNPN.

[0259] For example, a network entity involved in mobility may send the 5GMM cause “Cause #27 - N1 mode not allowed” to the UE. This 5GMM cause may be sent to the UE when the UE requests service in a PLMN or SNPN where operation in N1 mode is not permitted according to subscription or operator policy, or when the network initiates a deregistration request.

[0260] For example, a network entity involved in mobility may send the UE an EMM cause “Cause #14 - EPS services not allowed in this PLMN.” This EMM cause may be sent when the UE requests services in a PLMN that does not provide EPS services for the UE, or when the network initiates a detach request.

[0261] For example, a network entity involved in mobility may send an EMM cause “Cause #25 - Not authorized for this CSG” to the UE. This EMM cause may be sent to the UE if it requests access, or if the network initiates a detach request in a CSG cell with a CSG ID where the UE either has no subscription to operate or the UE's subscription has expired and it should find another cell in the same PLMN or an equivalent PLMN.

[0262] Therefore, when a UE attempts to register with a network, one or more of the following examples may need to be discussed to ensure that the UE does not attempt access on a RAT that the UE is not permitted to use:

[0263] - It is necessary to discuss how the network will convey RAT control information to the terminal;

[0264] - It is necessary to discuss how a terminal that receives RAT control information from the network will operate. It is necessary to discuss whether the terminal's operation will be supported only by the terminal's NAS layer operation, and / or whether the terminal's NAS layer will transmit information to the AS layer so that the AS layer will also use the RAT permission information during cell selection; and / or

[0265] - If the RAT information allowed to the UE changes due to changes in subscription information, etc., it is necessary to discuss how the UE will re-enable and use the RAT.

[0266] The description related to the operation of the terminal when the terminal receives RAT control information, as described in the example of the disclosure of this specification, may be composed of a combination of one or more of the following operations / configurations / steps.

[0267] In various examples of the present disclosure, RAT control information may refer to restricted RAT information that the operator has restricted use of in a specific PLMN. Additionally, the RAT control information of the present specification may refer to allowed RAT information that the operator has permitted use of in a specific PLMN.

[0268] For example, when a UE connects to PLMN-A, the network may allow the UE to connect via E-UTRAN, but may restrict the UE from connecting via NR satellite network. In this case, the RAT control information may be a PLMN identifier and a list of RATs allowed for use in the PLMN, or a PLMN identifier and a list of RATs restricted for use in the PLMN. The RAT control information may also be interpreted as control information for RAT utilization. For example, the RAT control information may be an allowed RAT list including PLMN-A and E-UTRAN permitted for use in PLMN-A, or a restricted RAT list including PLMN-A and NR satellite restricted for use in PLMN-A.

[0269] The Radio Access Technology (RAT) described in this specification is not limited to the RAT associated with the Radio access capability mentioned in TS 38.304 V18.2.0 or TS 36.304 V18.0.0, and may also include a RAT type identified by the RAT type value specified in TS 29.274 V18.5.0.

[0270] For reference, the RAT control information described herein may include one or more PLMN identifiers and restricted (or permitted) RAT list information for the corresponding PLMN. The RAT control information may have the same meaning as RAT restriction information, control information for RAT utilization, and access technology utilization control information. The PLMN identifier and restricted RAT list information for the corresponding PLMN may also be expressed as PLMN / RAT restriction information and PLMN / access technology utilization control information.

[0271] In this specification, descriptions of contents identical to those of the prior art are omitted, and the contents proposed in the disclosure of this specification are mainly described. For operations and procedures related to NAS signaling, AS signaling reception, cell selection, cell reselection, and PLMN selection, including basic Steering Of Roaming (SoR) information reception, TS 24.501 V18.5.0, TS 38.304 V18.2.0, and TS 23.122 V18.5.0 are basically referred to.

[0272] For reference, the first to third examples of the disclosure of this specification described below may be applied independently, or one or more of them may be applied in combination.

[0273] 1. First example of disclosure of this specification

[0274] In the first example of the disclosure of this specification, an example of a terminal (e.g., UE) receiving RAT control information is described. For example, RAT control information that is restricted or allowed for use for a specific PLMN may be received.

[0275] For reference, in the present disclosure, RAT control information may also be referred to as control information related to wireless access. For example, RAT control information may also be referred to as radio access technology utilization control information or access technology utilization control information.

[0276] RAT control information that is restricted or allowed for use for a specific PLMN may be preconfigured information in the UE.

[0277] RAT control information that is restricted or permitted for use in a specific PLMN can be communicated to the UE via RRC signaling, NAS signaling, or UICC. For example, a network (e.g., a network entity involved in mobility) can transmit RAT control information to the UE via NAS signaling.

[0278] RAT control information can be received along with a specific timer value. For example, the network can transmit a specific timer value and RAT control information to the UE. If a specific timer value is received together, the UE can perform operations utilizing the corresponding RAT control until the timer expires or until the timer is stopped by a specific event.

[0279] As an example, an example is described in which a UE receives RAT control information for a specific PLMN based on a Registration Accept message or a Configuration Update Command message.

[0280] For example, RAT control information can be transmitted to the UE through NAS signaling such as Registration Accept or Configuration Updated Command in the form of conveying Restricted RAT or Allowed RAT for a specific PLMN.

[0281] For example, RAT control information may include Restricted RAT or Allowed RAT for a specific PLMN. For example, the network may send NAS signaling, such as Registration Accept or Configuration Updated Command, to the UE, which includes RAT control information.

[0282] RAT control information may be composed of RAT information for a PLMN, as shown in the example in Table 4. RAT control information may be transmitted in bitmap format, as shown in the example in Table 4.

[0283] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0284] FIG. 7 is a first example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

[0285] In step (S701), the UE may transmit a registration request message to the AMF.

[0286] In step (S702), the AMF may send a registration acceptance message to the UE.

[0287] For example, the registration acceptance message may include control information related to the access technology (e.g., RAT control information). For example, the control information related to the access technology may be a list of PLMN / RAT restriction information or may include a list of PLMN / RAT restriction information.

[0288] In some implementations, the list of PLMN / RAT restriction information may be transmitted in the form of control information related to the access technology. For another example, the registration acceptance message may include control information related to the access technology, and the control information related to the access technology may include a list of PLMN / RAT restriction information.

[0289] Note that in step (S702), control information related to access technology (e.g., RAT control information) was included and transmitted in the registration acceptance message, but this is merely an example. For example, the AMF may not transmit the registration acceptance message, but may instead transmit only the control information related to the access technology to the UE. In another example, the AMF may transmit a message containing control information related to the access technology (e.g., RAT control information) to the UE.

[0290] In step (S703), the UE may transmit a registration completion message to the AMF. Note that step (S703) may be optionally performed.

[0291] In step (S704), the AMF may send a configuration update command message to the UE.

[0292] For example, a configuration update command message may include control information related to access technology (e.g., RAT control information). For example, the control information related to access technology may include a list of PLMN / RAT restriction information. In this case, the PLMN / RAT restriction information may be composed of a PLMN identifier and a list of RATs permitted for use in the PLMN, or a PLMN identifier and a list of RATs restricted for use in the PLMN. This PLMN / RAT restriction information may be transmitted in the form of a list including information on multiple PLMNs.

[0293] Note that in step (S704), control information related to access technology (e.g., RAT control information) was included in the configuration update command message and transmitted, but this is merely an example. For example, the AMF may not transmit the configuration update command message, but may instead transmit only the control information related to the access technology to the UE. In another example, the AMF may transmit a message including control information related to the access technology (e.g., RAT control information) to the UE.

[0294] In some implementations, the AMF may also receive access technology-related control information (e.g., RAT control information) from the UDM. For example, the access technology-related control information may be a list of PLMN / RAT restriction information or may include a list of PLMN / RAT restriction information. Referring to FIG. 8, an example of the AMF receiving access technology-related control information (e.g., RAT control information) from the UDM is described.

[0295] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0296] FIG. 8 is a second example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

[0297] Step (S801) can be performed in the same manner as step (S701) of FIG. 7.

[0298] In step (S802), the AMF may transmit a request message related to UE context management (CM) to the UDM. For example, the AMF may transmit a Nudm_UECM_Registration request message to the UE.

[0299] In step (S803), the UDM may transmit a response message related to UE context management to the AMF. For example, the UDM may transmit a Nudm_UECM_Registration response message to the UE.

[0300] In step (S804), the UDM may transmit control information related to the access technology (e.g., RAT control information) to the AMF. For example, the control information related to the access technology may be a list of PLMN / RAT restriction information or may include a list of PLMN / RAT restriction information.

[0301] Steps (S805) to (S807) can be performed in the same manner as steps (S702) to (S704) of FIG. 7.

[0302] For reference, the examples of FIG. 7 and FIG. 8 are examples of a network providing information related to access technology to a UE via NAS signaling, and the scope of the disclosure of the present specification is not limited by the examples of FIG. 7 and FIG. 8. For example, control information related to access technology may be transmitted to a UE via a registration rejection message, a configuration update command message, a deregistration request message, or a service rejection message.

[0303] For example, in the examples of FIG. 7 and / or FIG. 8, the registration acceptance message may include control information related to the access technology (e.g., RAT control information). The control information related to the access technology (e.g., RAT control information) may include information related to a restricted RAT and / or an allowed RAT.

[0304] In some implementations, the UE may receive RAT control information for a specific PLMN. For example, the UE may receive RAT control information for a specific PLMN as SoR transparent container information.

[0305] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0306] FIG. 9 is a third example of a procedure related to receiving RAT control information according to one embodiment of the disclosure of the present specification.

[0307] In step (S901), the UE may transmit a registration request message to the AMF.

[0308] In step (S902), AMF may transmit a request message related to UE CM to UDM. For example, AMF may transmit a Nudm_UECM_Registration request message to UDM.

[0309] Note that step (S902) may be performed optionally.

[0310] At step (903), the UDM may transmit RAT restriction information per PLMN to the SOR-AF.

[0311] Here, the RAT restriction information per PLMN may be restriction information related to access technology (e.g., access technology utilization control information) or may be PLMN / access technology utilization control information. A list of PLMN / RAT restriction information may refer to one or more PLMNs and RAT restriction information or access technology utilization control information for each PLMN.

[0312] In step (S904), the UDM may transmit a response message related to the UE CM to the AMF. For example, the UDM may transmit a Nudm_UECM_Registration response message to the AMF.

[0313] Note that step (S904) may be performed optionally.

[0314] In step (S905), the UDM may transmit a request message related to SoR to the SOR-AF. For example, the UDM may transmit an Nsoraf_SoR_Get request message to the SOR-AF.

[0315] In step (S906), SoR-AF may transmit a response message related to SoR to UDM. For example, SoR-AF may transmit an Nsoraf_SoR_Get response message to UDM.

[0316] For example, a response message related to SoR may contain information such as the following examples:

[0317] - List of preferred PLMN / access technology combinations;

[0318] - SOR-CMCI;

[0319] - "Store SOR-CMCI in the ME" indicator;

[0320] - a secured packet; and / or

[0321] - A list of PLMN / RAT restriction information. For example, a list of PLMN / RAT restriction information may be included in access technology-related control information (e.g., access technology utilization control information).

[0322] In step (S907), the UDM may transmit a response message related to Subscriber data management (SDM) to the AMF. For example, the UDM may transmit the Nudm_SDM_Get response message to the AMF. The response message related to the SDM may include information such as the following example:

[0323] SoR information; and / or

[0324] A list of PLMN / RAT restriction information. For example, a list of PLMN / RAT restriction information may be included in control information related to access technologies. The list of PLMN / RAT restriction information may include: i) a list of PLMNs; and ii) a list of restricted RATs (or allowed RATs) per PLMN.

[0325] In step (S908), the AMF may transmit a request message related to the SDM. For example, the request message related to the SDM may be Nudm_SDM_Subscribe request. The request message related to the SDM may include a notification of changes in subscription data.

[0326] At step (S909), the AMF may send a registration acceptance message to the UE.

[0327] The registration acceptance message may include an SoR transparent container. For example, the SoR transparent container may include a list of PLMN / RAT restriction information. For example, the list of PLMN / RAT restriction information may be referred to as or included in control information related to access technologies. The list of PLMN / RAT restriction information may include: i) a list of PLMNs; and ii) a list of restricted RATs (or allowed RATs) per PLMN.

[0328] In step (S910), the UE may transmit a registration completion message to the AMF. Step (S910) may be omitted.

[0329] For example, the SOR transparent container according to the example of FIG. 9 may include control information related to access technology. For example, the SOR transparent container may include: SOR transparent container Information Element Identifier (IEI), Length of SOR transparent container contents, SOR header, SOR-MAC-I AUSF , Counter SOR , PLMN ID and access technology list, and / or control information related to the access technology (e.g., PLMN ID and RAT control list (or, list of PLMN ID and RAT control information)).

[0330] In some implementations, Table 3 is an example of control information related to access technologies (e.g., RAT control information). For example, Table 3 may be an example of a list of PLMN / RAT restriction information included in the control information related to access technologies.

[0331] PLMN ID 1Restricted RAT (or Allowed RAT)...PLMN ID nRestricted RAT (or Allowed RAT)

[0332] Referring to the example in Table 3, control information related to the access technology (e.g., RAT control information) may include one or more PLMN IDs and restricted RAT or allowed RAT information corresponding to each PLMN ID.

[0333] RAT control information may include RAT information for a specific PLMN, as shown in Table 3. For example, the RAT information may be Restricted RAT or Allowed RAT information.

[0334] The RAT information (e.g., restricted RAT information or allowed RAT information) included in the control information related to the access technology may be in the form of a bitmap, as shown in the example in Table 4.

[0335] 0Spare0Spare0Spare0SpareNB-IOTNR SatelliteE-UTRANNR

[0336] Referring to the example in Table 4, RAT information can be transmitted to the UE in the form of a bitmap as in the example in Table 4.

[0337] For example, the UE may receive control information related to an access technology from the AMF. For example, the control information related to an access technology may include information such as the example in Table 4. For example, if the UE receives control information related to an access technology in which NR Satellite is set to 1, access related to the satellite may be permitted or restricted for the UE.

[0338] RAT information (e.g., RAT information included in control information related to access technology) may include radio access technologies such as NR, E-UTRA, UTRA, GSM, etc., but this is only an example. The scope of the disclosure of the present specification is not limited thereto. For example, RAT information may include a RAT type defined in TS 29.274 V18.6.0 Table 8.17-1. RAT information may not be limited to 1 byte as in the example in Table 4, and may be expressed in 2 or more bytes.

[0339] In some implementations, the UE may store control information related to access technology for a particular PLMN (e.g., RAT control information) in the Subscriber Identity Module (SIM).

[0340] The UE can manage RAT control information for a specific PLMN as preconfigured information stored in the SIM. For example, in this case, when the UE is roaming, information to access E-UTRA rather than NR can be stored in the SIM.

[0341] Regarding the operation of UE storing information in SIM, the basic operation is referred to TS 31.102 V18.4.0, TS 31.111 V18.6.0.

[0342] For example, a data object related to control information related to an access technology (e.g., RAT control information) may include a PLMN identifier and RAT information. For example, a RAT control data object may include a PLMN identifier and RAT information (e.g., NR, E-UTRAN, satellite E-UTRA, etc.).

[0343] As another example, control information related to an access technology (e.g., RAT control information) may include RAT control information per PLMN / SNPN value, to which PLMN selection or cell selection is applicable. For example, the coding of the control information related to the access technology may be as follows. For example, the control information related to the access technology may be expressed as the bit sequence bit 8 b8, b7, b6, b5, b4, b3, b2, b1. For example, each bit may be defined to match a specific access technology. For example, the access technology for b2 may be defined as satellite NG-RAN. On the other hand, bits for which an access technology is not defined may be defined as spare bits. If the value of a specific bit for which an access technology is defined is set to 1, it may mean that access to the corresponding access technology is restricted. On the other hand, if the bit value is set to 0, it may mean that no restriction is applied to access to the corresponding access technology.

[0344] A terminal (e.g., UE) may perform an operation according to the second example of the disclosure of the present specification below after receiving control information related to an access technology (e.g., RAT control information).

[0345] 2. Second example of disclosure of this specification

[0346] A second example of the disclosure of the present specification describes an example of an action performed by a terminal after the terminal receives RAT control information including RAT control information that is restricted for use or allowed RAT information in relation to a specific PLMN.

[0347] For example, the NAS layer of a terminal may perform operations as illustrated in the example below. After receiving control information related to an access technology (e.g., RAT control information), the NAS layer of the UE may store the control information related to the access technology (e.g., RAT control information). When the NAS layer of the UE receives control information related to a new access technology (e.g., RAT control information), it may update the already stored information.

[0348] In some implementations, the UE may delete RAT control information received based on NAS signaling when switching off.

[0349] The NAS layer of the UE may also receive available PLMN lists, signal quality information, etc. from the AS layer of the UE. In this case, the NAS layer of the UE may perform PLMN selection based on the available PLMN lists, signal quality information, etc. received from the AS layer of the UE. For example, when the NAS layer of the UE performs PLMN selection based on the available PLMN lists, signal quality information, etc. received from the AS layer of the UE, it may utilize RAT control information.

[0350] For example, the NAS layer of the UE may forward control information related to the UE's access technology (e.g., RAT control information) to the AS layer. In this case, the NAS layer of the UE may not receive cell quality information related to a restricted RAT of a specific PLMN from the AS layer of the UE.

[0351] As another example, the NAS layer of the UE can receive (or be transferred) available PLMN lists, signal quality, etc. from the AS layer of the UE. Based on control information related to access technology (e.g., RAT control information) that the NAS layer of the UE has, the NAS layer of the UE can also transfer assistance information for performing cell selection to the AS layer. For example, the UE (e.g., the NAS layer of the UE) can transfer selected PLMN and restricted RAT or allowed RAT information for the corresponding PLMN to a lower layer (e.g., the AS layer). For example, the UE (e.g., the NAS layer of the UE) can transfer control information related to access technology (e.g., RAT control information) received from the network to a lower layer (e.g., the AS layer). Alternatively, for example, the UE (e.g., the NAS layer of the UE) may forward to a lower layer (e.g., the AS layer) information about a specific PLMN (e.g., a currently selected PLMN, a selected PLMN, a current PLMN) and PLMNs associated with the PLMN (e.g., equivalent PLMNs) and restricted RAT or allowed RAT information for these PLMNs based on control information (e.g., RAT control information) related to an access technology received from the network. Alternatively, for example, the UE (e.g., the NAS layer of the UE) may provide to a lower layer (e.g., the AS layer) information about a PLMN and access technology restrictions associated with the PLMN. The UE NAS layer may forward control information (e.g., access technology utilization control information) related to an access technology received from the network to the AS layer.The UE (e.g., the NAS layer of the UE) may provide the AS layer with information related to the PLMN and access technology restrictions associated with the PLMN.

[0352] The NAS (e.g., the NAS layer of the UE) can control the RAT(s) in which the cell selection should be performed. For example, by indicating the RAT(s) associated with the selected PLMN and maintaining a list of restricted registration areas and a list of equivalent PLMNs, the NAS (e.g., the NAS layer of the UE) can control the RAT(s) in which the cell selection should be performed.

[0353] The AS layer of the UE can perform actions such as the following examples:

[0354] For example, the UE AS layer can receive information about a specific PLMN (e.g., the currently selected PLMN, the current PLMN) and the RAT(s) associated with the PLMN from the NAS. The AS layer of the UE can perform cell selection. If the terminal (e.g., the UE) cannot find a suitable cell in all RATs, it can transition to the Any Cell Selection state. In this case, the order in which the terminal (e.g., the UE) scans the RAT for the PLMN to find a suitable cell can be as follows:

[0355] 1) The AS layer of the UE can first scan the associated RAT(s) (e.g., the restricted RAT list associated with the PLMN, the restricted access technology list associated with the PLMN) received from the NAS layer to find a suitable cell. For example, based on the PLMN associated with the RAT restriction, cells that are not suitable are not considered as candidates for selection (or reselection) by the UE.

[0356] 2) The AS layer of the UE may not be able to find a suitable cell in the associated RAT(s). In this case, the terminal (e.g., the AS layer of the UE) can find a suitable cell in the RAT(s) allowed in the PLMN based on the RAT control information.

[0357] 3) Based on the RAT control information, the terminal (e.g., the AS layer of the UE) may not be able to find a suitable cell in the RAT(s) allowed for the PLMN. In this case, the terminal searches for a suitable cell in all RAT(s) detected for the PLMN.

[0358] At this time, the terminal may camp on a suitable cell in a RAT other than the allowed RAT(s). In this case, the terminal may transition to the Any cell state or operate as if in the Any cell state. For example, the terminal may use only emergency services, not normal services.

[0359] The transmitted RAT control information, the RAT information received from the base station, or both may be utilized to perform cell selection operations or other AS layer operations (e.g., measurement).

[0360] The AS layer of the UE can perform SIB acquisition based on the RAT control information received from the NAS layer of the UE. For example, the UE can distinguish RATs based on frequency. In this case, the UE may not perform SIB acquisition for unauthorized frequencies based on the RAT control information (e.g., the UE does not read MIB / SIB1).

[0361] The AS layer of the UE can select a cell based on the RAT control information received from the NAS layer when performing inter-RAT cell reselection.

[0362] The AS layer of the UE may receive additional cell reselection priorities for inter-RAT reselection from the RAN node via dedicated RRC signaling (e.g., RRC release). The RAN node may also provide the UE with a timer value for applying the additional cell reselection priorities.

[0363] 3. Third example of disclosure of this specification

[0364] In the third example of the disclosure of this specification, an example of re-enabling RAT is described.

[0365] The UE can receive control information related to access technology (e.g., RAT control information). Upon receiving the RAT control information, the UE can delete RAT information whose use has been restricted when an event such as the following occurs. For example, deleting RAT information may involve deleting all RAT control information, or may involve deleting only information for a portion of the RAT control information, depending on the event.

[0366] For example, a UE may disable operations based on RAT control information when the following events occur. Furthermore, the UE may re-enable operations for a RAT that it had previously restricted. For example, a terminal (e.g., a UE) may have restricted cell selection / reselection, measurements, etc. for a restricted RAT. In this case, if the following events occur, the UE may re-enable cell selection / reselection, measurements, etc. for the RAT:

[0367] i) The UE's subscription information may be updated. In this case, the UE may receive update information (or indication) related to modification of RAT control information from the network.

[0368] For example, the update information (or indication) may be control information related to an updated access technology (or updated RAT control information).

[0369] For another example, the update information (or indication) may be information (or an indication) to delete control information (or RAT control information) related to previously received access technologies. For example, when the UE receives the update information (or indication), it may delete all control information (or RAT control information) related to the access technologies that it has stored.

[0370] ii) A UE may also access a restricted RAT through network control. In this case, the UE may move to the restricted RAT through a handover or redirection in connected mode, under network control. In this case, the UE may also lift the restriction on the RAT.

[0371] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

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

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

[0374] For example, with respect to the example of FIG. 10, the operations described in the examples of FIGS. 1 to 9 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 10, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0375] In the example of FIG. 10, the first network entity may be a network entity related to mobility (e.g., AMF).

[0376] In step (S1001), the first network entity can transmit control information related to the access technology to the UE.

[0377] In some implementations, control information related to the access technology may be received via messages related to the Non Access Stratum (NAS). For example, the NAS-related messages may be a registration acceptance message, a registration rejection message, a configuration update command message, a deregistration request message, or a service rejection message.

[0378] In some implementations, the UE may transmit a first NAS message to the first network entity. For example, the first NAS message may be a registration request message. The first network entity may transmit a second NAS message to the UE, which includes control information related to the access technology. For example, the second NAS message may be a registration acceptance message or a registration rejection message.

[0379] In step (S1002), the UE may perform Public Land Mobile Network (PLMN) selection, cell selection, or cell reselection.

[0380] For example, the UE may perform PLMN selection, cell selection, or cell reselection based on control information related to the access technology.

[0381] For example, information related to access technology may include information related to a first PLMN, information related to a satellite, and information related to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0382] In some implementations, control information related to the access technology may be applied to the PLMN selection, the cell selection, or the cell reselection.

[0383] In some implementations, the UE may provide a list of PLMNs with associated access technology restrictions to a lower layer. For example, the UE may provide a list of PLMNs with associated access technology restrictions to a lower layer based on received control information related to the access technology. For example, the list of PLMNs with associated access technology restrictions may be provided to the lower layer for cell selection or for excluding restricted access technologies for cell selection.

[0384] In some implementations, if a cell with a restricted access technology is not suitable based on the list of PLMNs with the associated access technology restrictions, the terminal may not consider the cell with the restricted access technology as a candidate for reselection.

[0385] According to one embodiment of the present disclosure, a terminal may receive RAT control information from a first network to notify the second network of a restricted RAT. For example, the RAT control information may be delivered to the terminal in the form of a Registration Accept, Configuration Update Command, or SoR message. In another example, the RAT control information may be delivered to the terminal via RRC signaling (e.g., RRC release).

[0386] According to one embodiment of the present disclosure, a terminal may select a second network. In this case, the terminal may select a cell in which an RAT is allowed for network access based on RAT control information. For example, the terminal may not be able to select a suitable cell in an allowed RAT and only a restricted RAT may satisfy suitable cell signaling criteria. In this case, the terminal may select a cell in the restricted RAT and then transition to the "any cell" state.

[0387] This specification may have various effects.

[0388] For example, a terminal can perform mobility-related actions based on radio access technology information. This can reduce resource consumption due to power consumption and signaling consumption caused by UEs attempting to connect to restricted access networks and then being rejected.

[0389] For example, according to one embodiment of the disclosure of this specification, a network operator can apply to a terminal whether to permit the use of a specific RAT, regardless of the terminal's state (idle or connected). Accordingly, the network can perform RAT management flexibly and efficiently.

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

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

[0392] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0393] For reference, the operation of a network node or network entity (e.g., AMF, SMF, PCF, UDM, SOR-AF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, eNB, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of a network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of a terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0394] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

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

[0396] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0397] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A step of receiving control information related to access technology; and A step of performing Public Land Mobile Network (PLMN) selection, cell selection, or cell reselection based on control information related to the above access technology, A method wherein information related to the above access technology includes information related to the first PLMN, information related to a satellite, and information related to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

2. In paragraph 1, A method in which control information related to the above access technology is applied to the PLMN selection, the cell selection, or the cell reselection.

3. In paragraph 1 or 2, A method in which control information related to the above access technology is received through a message related to a Non Access Stratum (NAS).

4. In any one of paragraphs 1 to 3, A method in which a list of PLMNs with associated access technology restrictions is provided to a lower layer.

5. In paragraph 4, A method wherein a list of PLMNs having the associated access technology restrictions is provided to the lower layer for the cell selection or for excluding the restricted access technology for the cell selection.

6. In paragraph 4 or 5, A method in which, based on a list of PLMNs having the above-mentioned associated access technology restrictions, if a cell with a restricted access technology is not suitable, the cell with a restricted access technology is not considered as a candidate for reselection.

7. In any one of paragraphs 1 to 6, a step of transmitting a first NAS message to a network entity involved in mobility; and A method further comprising the step of receiving a second NAS message including control information related to the access technology from a network entity related to the mobility.

8. At least one transmitter / receiver; at least one processor; and At least one memory capable of storing instructions and being operable to connect to at least one processor, At least one processor of the above: A device adapted to perform a method according to any one of claims 1 to 7.

9. At least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, An operation performed based on the above command being executed by the at least one processor: A device according to any one of claims 1 to 7.

10. A non-transitory computer readable medium (CRM) that records commands, The above instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 7.

11. A step of transmitting control information related to access technology to User Equipment (UE), Control information related to the above access technology is related to Public Land Mobile Network (PLMN) selection, cell selection, or cell reselection performed by the UE, A method wherein information related to the above access technology includes information related to the first PLMN, information related to a satellite, and information related to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

12. In paragraph 11, A method in which control information related to the above access technology is applied to the PLMN selection, the cell selection, or the cell reselection.

13. In paragraph 11 or 12, A method in which control information related to the above access technology is transmitted through a message related to a Non Access Stratum (NAS).

14. In any one of paragraphs 11 to 13, A step of receiving a first NAS message from the UE related to mobility; and A method further comprising the step of transmitting a second NAS message including control information related to the access technology to the private UE.

15. At least one transmitter / receiver; at least one processor; and At least one memory capable of storing instructions and being operable to connect to at least one processor, At least one processor of the above: A device adapted to perform a method according to any one of claims 11 to 14.

Images