Aerial communication

Abstract

One embodiment disclosed in the present disclosure provides a method. The method may comprise the steps of: transmitting, to a first network entity, a registration request message including capability information of a UE; receiving a registration acceptance message from the first network entity; and selecting a PLMN on the basis of subscriber information and a PLMN list included in the registration acceptance message.

Description

public communications

[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] Methods supporting aerial communication for terminals are being discussed. However, conventional technology has the problem of lacking a method for effectively performing aerial communication and / or ensuring security related to aerial communication.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include: transmitting a registration request message including capability information of a UE to a first network entity; receiving a registration acceptance message from the first network entity; and selecting a PLMN based on subscriber information and a PLMN list included in the registration acceptance message.

[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: receiving a PLMN information request message including subscriber information of a UE from a first network entity associated with mobility; determining a PLMN list for the UE based on location information of the UE and the subscriber information; and transmitting a PLMN information response message including the PLMN list to the first network entity.

[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. 7A and FIG. 7B are examples of PLMN selection according to one embodiment of the disclosure of the present specification.

[0016] FIG. 8A and FIG. 8B are first examples of a procedure according to one embodiment of the disclosure of the present specification.

[0017] FIG. 9a and FIG. 9b are a second example of a procedure 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 provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs 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] The Network (NW) informs the terminal of the Preferred PLMN list to be used, and the terminal can select a PLMN.

[0183] For example, a terminal (e.g., MS, UE) may select a PLMN other than the one associated with the current connection and establish a new connection to that PLMN. Alternatively, the terminal may power on and select a new PLMN to establish a connection. In these cases, the terminal may select a different PLMN / Access technology combination and attempt registration according to the following sequence.

[0184] A terminal can perform PLMN selection by utilizing all information related to PLMN selection stored within the terminal's SIM. For example, the terminal's SIM may contain a User Controlled PLMN selector with Access Technology and an Operator Controlled PLMN selector with Access Technology.

[0185] The above Operator Controlled PLMN selector with Access Technology can be stored and utilized within the terminal or within the SIM. This Operator Controlled PLMN selector with Access Technology can include access technologies associated with each PLMN entry. In this case, the access technologies refer to NG-RAN, E-UTRAN, etc.

[0186] For example, when switching on or recovering from lack of coverage, the terminal may perform actions related to the automatic network selection mode procedure.

[0187] MS may select and attempt registration with other PLMN / access technology combinations in the following order, if available:

[0188] 1. The terminal can use HPLMN (if the EHPLMN list is empty or non-existent) or the highest priority EHPLM thaa (if the EHPLMN list is present).

[0189] 2. The terminal can use each PLMN / access technology combination (in priority order) present in the SIM's "User Controlled PLMN Selector with Access Technology" data file.

[0190] 3. The terminal can use each PLMN / access technology combination (priority) that is present in the SIM's "Operator Controlled PLMN Selector with Access Technology" data file (priority) or stored in the ME.

[0191] 4. The terminal can use high-quality signals received in any order and other PLMN / access technology combinations.

[0192] 5. The terminal may use other PLMN / access technology combinations with lower or decreasing signal quality.

[0193] For example, the terminal can select a PLMN or PLMN / Access Technology selected from the values ​​of HPLMN, EHPLMN, “User controlled PLMN Selector with Access Technology”, “Operator Controlled PLMN Selector with Access Technology” stored and managed as Ef files in the SIM card, and “Operator Controlled PLMN Selector with Access Technology” stored and managed in the ME of the terminal.

[0194] In the above example, the Operator Controlled PLMN Selector with Access Technology value can be a fixed value stored in the SIM card or a value stored in the terminal. The value stored in the terminal can be notified by the HPLMN via NAS signaling of the “Operator Controlled PLMN Selector with Access Technology” value to be used in the PLMN selection process in the terminal. The process related to this is referred to as 5G roaming steering over the control plane, and Annex C of TS23.122 V18.4.0 can be referenced.

[0195] The HPLMN can inform the UE of the PLMN or PLMN / Access Technology list values ​​to be used by the UE through NAS signaling. The HPLMN may perform this operation to inform the NW of the PLMN to be used by the UE as the Operator's preferred PLMN list. For example, the NW can inform the UE of the PLMN list to be used by the UE for the PLMN Selection procedure during or after the registration procedure through the Steering of roaming procedure as in the example below. For example, the NW can inform the UE of the PLMN list in the form of a list of preferred PLMN / access technology combinations through NAS signaling.

[0196] 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 / 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.

[0197] FIG. 7A and FIG. 7B are examples of PLMN selection according to one embodiment of the disclosure of the present specification.

[0198] 1) The UE can send a registration request message to the VPLMN AMF.

[0199] 2) The registration process may be initiated.

[0200] For example, AMF can send a Nudm_UECM_Registration request message to UDM.

[0201] For example, if the NAS registration type is “initial” or “emergency”, the UDM may delete the “ME support of SOR-CMCI” indicator.

[0202] For example, UDM can send a Nudm_UECM_Registration response message to AMF.

[0203] For example, AMF can send a Nudm_SDM_Get request message to UDM.

[0204] For example, AMF may send a registration acceptance message to the UE.

[0205] 3a) The UDM may decide to transmit the steering of roaming information, whether to request an ACK from the UE, how to obtain the list of preferred PLMN / access technology combinations, or secure packets.

[0206] 3b) UDM can send Nsoraf_SoR_Get request message to SOR-AF.

[0207] 3c) For example, the SOR-AF may transmit an Nsoraf_SoR_Get response message to the HPLMN UDM. The Nsoraf_SoR_Get response message may contain, for example, a list of preferred PLMN / access technology combinations, a SOR-CMCI (if present), and a "Store SOR-CMCI in ME" indicator (if present) or a security packet, or neither.

[0208] SOR-AF, one of the NW entities, can inform the HPLMN UDM of the list of preferred PLMN / access technology combinations through the Nsoraf_SoR_Get response.

[0209] Afterwards, VPLMN AMF, one of the NW entities, can transparently secure the received steering of roaming information and transmit it to the terminal through a REGISTRATION ACCEPT message (e.g., in step 6).

[0210] 3d) UDM can protect information.

[0211] 4) UDM can send Nudm_SDM_Get response message to AMF.

[0212] 5) AMF can send a Nudm_SDM_Subscribe request message to UDM.

[0213] 6) AMF may send a registration acceptance message to the UE.

[0214] The registration acceptance message may include steering of roaming information.

[0215] A terminal (e.g., UE) can receive a preferred PLMN / access technology combination list included in the steering of roaming information.

[0216] In this case, the terminal can store the list of preferred PLMN / access technology combinations received via NAS signaling as a replacement for the Operator Controlled PLMN Selector with Access Technology list stored in the terminal.

[0217] Therefore, through this Steering of roaming procedure, the HPLMN can re-establish the PLMN list in which the terminal has priority.

[0218] The steering of roaming information may include a list of preferred PLMN / access technology combinations. In this case, the ME of the terminal may replace the highest priority entry of the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the received list of preferred PLMN / access technology combinations. If a PLMN identified in the list of preferred PLMN / access technology combinations is in the list of prohibited PLMNs and the list of prohibited PLMNs for GPRS services, the ME of the terminal may remove the identified PLMN from this list.

[0219] Additionally, the basic registration procedure for Unmanned Aircraft System (UAS) terminals is as follows.

[0220] Before a terminal connects to 5GS for UAS service, the terminal supporting the UAS service may have an assigned CAA-level UAV ID. Additionally, the terminal may register for UAS service if a valid aerial subscription exists within the UE subscription.

[0221] If the UE supports UAS service, the UE may set the UAS bit to "UAS service supported" in the 5GMM Capability IE included in the REGISTRATION REQUEST message. If the UE supports A2X over E-UTRA-PC5, the UE may set the A2XEPC5 bit to "A2X over E-UTRA-PC5 supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over NR-PC5, the UE may set the A2XNPC5 bit to "A2X over NR-PC5 supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over Uu, the UE may set the A2X-Uu bit to "A2X over Uu supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message.

[0222] When a UE supporting UAS service initiates initial registration for a UAS service, the UE may include a Service Level Device ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and set the Service Level Device ID value to a CAA level UAV ID. The UE may include a Service Level-AA server address in the Service Level-AA container IE of the REGISTRATION REQUEST message and set the value to a USS address if provided by a higher layer. The UE may include a Service Level-AA payload in the Service Level-AA container IE of the REGISTRATION REQUEST message and set the Service Level-AA payload type if the Service Level-AA payload is provided by a higher layer.

[0223] Aerial communications of UEs may be supported. A UE capable of performing aerial communications may be referred to as an Aerial UE.

[0224] For example, NR connectivity to a UE capable of over-the-air communication can be supported through the following features:

[0225] - Subscription-based Aerial UE identification and authorization;

[0226] - Altitude reporting based on measurement events where the UE's altitude exceeds a reference altitude threshold set in the network;

[0227] - Altitude-dependent configurations that apply only to certain altitude regions;

[0228] - Interference detection based on measurement reports that are triggered when a set number of cells (e.g., one or more) simultaneously meet the trigger criteria;

[0229] - Signaling of flight path information from UE to NG-RAN and from source gNB to target gNB during handover;

[0230] - Reporting of position information including horizontal and vertical speed of the UE;

[0231] - Transmission of BRID and DAA messages via PC5 interface.

[0232] An example of subscription-based Aerial UE identification is as follows:

[0233] For example, support for the Aerial UE feature can be stored in the user subscription information of the UDM. The UDM can transmit this information to the AMF during registration, service request, and mobility registration update procedures.

[0234] The AMF can provide Aerial UE subscription information to the NG-RAN node via the NGAP Initial Context Setup Request message during registration, mobility registration update, and service request procedures. The subscription information can also be updated via the NGAP UE context modification procedure and the NGAP path switch request procedure. Additionally, for Xn-based handover, the source NG-RAN node can include Aerial UE subscription information in the XnAP HANDOVER REQUEST message and RETRIEVE UE CONTEXT RESPONSE message that it sends to the target NG-RAN node.

[0235] For NG-based handovers within and between AMFs, the AMF may provide Aerial UE subscription information to the target NG-RAN node after the handover procedure is completed.

[0236] Altitude-based reporting for Aerial UE communications can be performed.

[0237] For example, for Aerial UEs, event-based measurement reporting based on altitude (e.g., eventH1 and eventH2 in 3GPP TS38.331 V17.7.0) can be configured. For example, the Aerial UE can send a measurement report when the altitude rises or falls below a configured threshold. If configured by the NG-RAN, the UE includes altitude and position information in the measurement report. When altitude reporting is configured, the UE can always report RSRP / RSRQ / SINR measurement results.

[0238] Additionally, Aerial UEs can be configured to trigger measurement reports only when both altitude dependent and RSRP / RSRQ / SINR based conditions are met (e.g. eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1 and eventA5H2 of 3GPP TS38.331 V17.7.0, commonly denoted as eventAxHy). The same rules for eventH1 and eventH2 described above can be applied to the content of eventAxHy measurement reports.

[0239] For example, altitude-dependent settings for Aerial UE communications may be applied.

[0240] For example, for an Aerial UE, multiple altitude-dependent settings can be configured, each applicable to a given altitude range. Altitude-dependent settings can be provided independently by the measurement object, and the Aerial UE can use them when in the RRC_CONNECTED state.

[0241] For example, interference detection and mitigation can be applied for Aerial UE communications.

[0242] For example, for interference detection, the Aerial UE can be configured with RRM event A3, A4, A5 or AxHy to trigger a measurement report when individual (cell-specific) RSRP / RSRQ / SINR values ​​(for A3, A4, A5 events) or when the RSRP / RSRQ / SINR and the altitude of the measured cell meet the configured event (for AxHy event). Once these conditions are met and a measurement report is sent, the list of triggered cells can be updated when subsequent cells meet the event. However, when the list of triggered cells is greater than or equal to the configured number of cells, no further measurement reports are sent unless reportOnLeave is configured.

[0243] Flight path information reporting for Aerial UE communications may be supported.

[0244] For example, the NG-RAN may request an aerial UE to report flight path information based on an indication from the aerial UE that flight path information is available, or without such an indication from the aerial UE. Flight path information may be configured with multiple waypoints defined by 3D positions. If the UE has flight path information available, the Aerial UE may report up to the configured number of waypoints. If configured by the NG-RAN and available to the UE, the report may include a time stamp per waypoint.

[0245] For example, flight path information can be provided from the source gNB to the target gNB during a handover. If the relevant distance- or time-based conditions for indication reporting, set by the NG-RAN, are met for a waypoint, the Aerial UE can indicate the availability of updated flight path information. Additionally, the Aerial UE can indicate the availability of updated flight path information if a new waypoint is added or a future waypoint is removed from the flight path information.

[0246] For example, position reporting for Aerial UE communications can be performed.

[0247] For example, position information for Aerial UE communications may include horizontal and vertical velocities, if configured. Position information may be included in RRM reports and altitude-based reports.

[0248] Broadcasting UAV ID (BRID) and Detect and Avoid (DAA) via Aircraft-to-Everything (A2X) communication may be supported.

[0249] Aerial UEs support A2X communications. BRID relies on broadcast, while DAA can be provided via unicast or broadcast transmissions on the NR sidelink. BRID and DAA message transmissions are supported in both in-coverage and out-of-coverage scenarios and can only rely on the UE's autonomous resource selection for NR sidelink communications.

[0250] NG-RAN can configure separate SL Tx resource pools for BRID and DAA.

[0251] To support NTZ, one or more of the following examples must be supported:

[0252] 1) NTZ application can be applied to UEs that are UAV UEs (aka Aerial UEs) with aerial subscriptions.

[0253] 2) NTZ can be supported for both LTE and NR.

[0254] 3) An NTZ may be mapped to one or more cells or parts of cells, or may overlap with other cells in the mobile operator's network.

[0255] 4) Regardless of the service type, transmission in restricted frequency bands is not permitted from UAV UEs located in the NTZ (three-dimensional considering height restrictions).

[0256] 5) No UAV UE may transmit or attempt to transmit within the restricted frequencies, locations, and heights defined by the NTZ. However, UAV UEs may transmit and receive normally outside these restrictions.

[0257] 6) Since the UAV UE supporting NTZ regulations is configured with NTZ information, the UAV UE can recognize the existence of NTZ.

[0258] 7) UAV UEs located in the NTZ may be permitted to receive downlink data from the network, provided that this does not violate regulatory requirements.

[0259] For UAV UEs, NTZ support information needs to be set or provided. UAV UEs need to apply NTZ.

[0260] For example, one or more of the following NTZ support information (or NTZ policies) may be configured / provisioned on the UAV UE:

[0261] - List of restricted frequency bands with geographic areas (including coordinates with longitude, latitude and altitude restrictions).

[0262] The above NTZ support information can be used by the UAV UE using one or more of the following methods:

[0263] - Presets;

[0264] - During the registration process, AMF may provide / update NTZ support information to UE;

[0265] - AMF can provide / update NTZ support information to UE during UE configuration update procedure;

[0266] - During the attach procedure, the MME can provide / update NTZ support information to the UE;

[0267] - During the TAU procedure, the MME can provide / update NTZ support information to the UE;

[0268] - PCF can provide / update NTZ support information to UE;

[0269] - AF can provide / update NTZ support information to UE (e.g. NTZ AF, USS, TPAE).

[0270] A UAV UE supporting NTZ may perform one or more of the following examples:

[0271] a) The UE can apply NTZ based on the configured / provisioned NTZ support information.

[0272] b) When NTZ is applied, the UAV UE may not transmit any signals or data.

[0273] c) The UE may not fully select / reselect a cell affected by NTZ.

[0274] Regarding NTZ, there is a need to discuss how to support preventing areal UEs from transmitting on certain bands / frequencies in certain regions and countries.

[0275] The following examples are examples of ECC rules related to NTZ.

[0276] In addition to the technical requirements already coordinated for MFCN band and spectrum compatibility, spectrum operation restrictions may apply. This can be accomplished using NTZs, which are geographic areas defined at the national level where Aerial UE operation in certain frequency bands is prohibited. Additional OOB emission restrictions specific to Aerial UEs may also be defined to avoid interference with other services in other bands.

[0277] For example, an NTZ may be defined as a geographical area where an Aerial UE cannot transmit for spectrum compatibility purposes in a given harmonized MFCN band or portion thereof.

[0278] There is a need to ensure that Aerial UEs are NTZ compliant.

[0279] For example, with respect to NTZ, operating conditions such as the examples below are discussed.

[0280] For example, operating conditions defined and implemented at the national level provide additional measures to technical conditions to protect other services.

[0281] 703-733MHz: DTT receiver and RAS site protection

[0282] Aerial UEs operating in 703-733 MHz must not transmit below 30 m above ground level to avoid interference with DTT receivers;

[0283] For Aerial UEs operating in the 703-718 MHz frequency band, nationally determined no-transmission zones may be required around RAS sites operating in the 1400-1427 MHz band (where appropriate).

[0284] 832-837MHz: RAS site protection

[0285] For Aerial UEs operating in the 832-837 MHz frequency band, nationally determined no-transmission zones may be required around RAS sites operating in the 1660-1670 MHz band (where appropriate).

[0286] 2500-2570MHz / 2570-2620MHz: RAS site and radar protection

[0287] For aeronautical UEs operating in the 2500-2570 MHz or 2570-2620 MHz frequency bands, nationally determined no-transmit zones may be required around RAS sites operating in the 2690-2700 MHz band (where appropriate);

[0288] For Aerial UEs operating in the 2500-2570 MHz or 2570-2620 MHz frequency bands, a nationally determined no-transmit zone may be required around radars operating in the 2700-2900 MHz band.

[0289] Methods to support aerial communication of UE are being discussed.

[0290] However, according to the prior art, there is a problem in that there is no method for effectively performing public communication and / or no method for ensuring security related to public communication.

[0291] For example, there has been no discussion at all about how UEs can perform over-the-air communications based on the No Transmit Zone (NTZ).

[0292] To account for NTZ, it is necessary to prevent aerial UEs from transmitting on certain bands / frequencies in certain regions and countries.

[0293] However, there is still no discussion on how to perform PLMN selection at a specific location for Aerial UE subscription terminals and how to provision PLMNs for Aerial UEs.

[0294] For example, it is not defined how NTZ will be set up or how the network will inform the UE of NTZ.

[0295] Meanwhile, in certain areas, regional reasons or operator policies may prevent terminals from transmitting signals and data. Even if a terminal is already connected to a specific PLMN cell and in connected mode, the PLMN may change in several cases, including the ones listed below. Furthermore, when a terminal is in idle mode, the PLMN to be selected may vary depending on the region.

[0296] Typically, when a terminal performs PLMN selection, it can do so using multiple PLMN lists stored in its USIM. However, there may be instances where the NW needs to dynamically inform terminals supporting UAS (i.e., UAVs) of PLMNs.

[0297] In this case, since the terminal is prevented from transmitting for a specific band / frequency in a specific area, there is a problem that the terminal can transmit a signal without NTZ restrictions in a band / frequency that is not a restricted band / frequency.

[0298] Some PLMNs may deploy restricted bands / frequencies, while others may not. Furthermore, NTZs are not static information and may be subject to updates. For example, the areas covered by NTZs and / or restricted bands / frequencies may change as radar facilities are installed or expanded.

[0299] For these reasons, a method is needed for the NW to provision PLMNs for NTZ handling to terminals. Terminals need a way to receive this PLMN information and perform new PLMN selection.

[0300] For example, according to the prior art, there is no discussion on how a terminal related to an Aerial UE subscription performs PLMN selection at a specific location and how to provision the PLMN of the Aerial UE to the terminal.

[0301] Also, for example, a terminal may be moving to a location where two PLMNs are available, and PLMN#1 may not be able to transmit Tx to NTZ, while PLMN#2 may be able to transmit TxRx. In this case, if the terminal is connecting to PLMN#1 and transmitting data, the network may need to notify the terminal of a new list of available PLMNs so that the terminal can connect to PLMN#2.

[0302] Additionally, for example, there may be a fixed flight trajectory (or operating route) for the terminal, and it may be necessary to notify a new PLMN list different from the previous one to the Aerial terminal flying along the flight trajectory.

[0303] In this specification, terms such as aerial UE, UAV (Uncrewed Aerial Vehicle), UAV UE, UE, UE with aerial subscription, terminal, etc. may be used as terms with the same meaning.

[0304] In this specification, NTZ information, NTZ assistance information, NTZ policy, NTZ area restriction, NTZ area restriction information, etc. may be used as terms with the same meaning.

[0305] In this specification, the preferred PLMN list may be used as a list of preferred PLMN / access technology combinations to replace the “Operator Controlled PLMN Selector with Access Technology” provided by the NW.

[0306] For example, the UE may receive a preferred PLMN list and an “Operator Controlled PLMN Selector with Access Technology” from the network. If the UE receives the preferred PLMN list, the PLMN information in the “Operator Controlled PLMN Selector with Access Technology” that the UE has may be replaced with the received preferred PLMN list.

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

[0308] For example, a network entity (or network node) may perform actions such as the following examples: The network entity (or network node) may be a UAS-AF, an AMF, a UDM, etc.

[0309] For example, one or more of the following actions may be performed:

[0310] 1. The UAV UE can support NTZ capability. In this case, when the terminal has NTZ capability, the NW (e.g., UAS-AF, etc.) can inform the terminal of a preferred list that is only applicable to the NTZ region. In this case, the NW can inform the UAV UE of the preferred PLMN list that the UAV UE will use.

[0311] For example, the UAS AF may perform the USS UAV Authorization / Authentication (UUAA) procedure. For example, if authentication for the UE is successful, the UAS AF may provide the UE with a list of preferred PLMNs to use based on the list of authenticated PLMNs.

[0312] For example, a terminal can use the NTZ capability as a new capability. The NW can use the capability as a new capability to inform terminals with the NTZ capability of the preferred list considering NTZ.

[0313] 2. A network entity (e.g., UAS-AF) can check whether there is a Preferred PLMN list corresponding to an area related to No transmit zone within the movement trajectory of the terminal. For example, the network entity (e.g., UAS-AF) can receive and check information (e.g., Preferred PLMN list information corresponding to an area related to NTZ) from another NW entity (e.g., PCF, UDM, AMF). For another example, UAS-AF can also check whether there is a Preferred PLMN list corresponding to an area related to No transmit zone within the movement trajectory of the terminal using pre-configured information.

[0314] For example, a terminal may have PLMN list information related to NTZ.

[0315] For example, information regarding which PLMNs are available at a specific location (specific geographic area and altitude range, time information) can be set in the PCF based on a subscription for a specific terminal (e.g., a UAV terminal) or based on an OMA. The PCF can transmit a PLMN list related to the NTZ to the terminal.

[0316] 3. Using these two pieces of information (e.g., time-related information and location-related information), UAS-AF can delete PLMNs that are no longer available due to being in the No transmit zone category from the Preferred PLMN list used by the existing UAV UE. Then, UAS-AF can perform a provisioning procedure to notify the UE of the new Preferred PLMN list.

[0317] 4. UAS-AF can newly provision a Preferred PLMN list to the terminal based on the terminal location information received from AMF or the terminal location information held by UAS-AF.

[0318] The terminal can utilize the newly provisioned Preferred PLMN list based on its subscription information and capability information (e.g., NTZ-related capability information). For example, the terminal may receive the Preferred PLMN list from the AMF and perform a PLMN selection procedure based on the Preferred PLMN list.

[0319] Actions such as the following examples may be performed:

[0320] For Aerial UEs supporting NTZ, a Preferred list of PLMN / Access technology may be provided.

[0321] A network (e.g., AMF, UAS-AF, etc.) can provide a preferred list of PLMNs / access technologies to a terminal on a subscription basis. For example, if a terminal has a specific subscription, the network (e.g., AMF) provides a preferred list of available PLMNs / access technologies.

[0322] For example, NW (e.g. AMF, UAS-AF, etc.) can inform NTZ support UEs with Aerial Subscription of its Preferred list of PLMN / Access technology.

[0323] For example, based on the SOR procedure, SOR-AF or UAS-AF can inform the NW (e.g., AMF) of the Preferred list of PLMN / Access technology available for each location.

[0324] For example, a NW (e.g., AMF, UAS-AF, etc.) can request subscriber information of a terminal from the HPLMN UDM. In this case, the HPLMN UDM can check the terminal capability through the registration request. The HPLMN UDM can check the capability and subscription of the requested terminal. In this case, the HPLMN UDM can determine that the terminal supports NTZ and has an Aerial subscription, and the Network (e.g., OAM, AMF, UDM, PCF, UAS-AF, LMF, etc.) provides a PLMN list for NTZ functionality. For example, the OAM can inform the OAM of available PLMNs, not the network entity. The UAS-AF, etc. can know the PLMN list according to the location of the terminal, as in the examples of FIGS. 8a and 8b below. When LMF informs NW (e.g., AMF, UAS-AF, etc.) of actual UE location information, NW NW (e.g., AMF, UAS-AF, etc.) can know whether actual UE is inside NTZ. UDM, PCF, AMF, etc. can know the PLMN list of terminal.

[0325] Then, the HPLMN UDM can request the SOR-AF or UAS-AF to provide a PLMN list. After receiving the PLMN list from the SOR-AF or UAS-AF, the UDM can provide a list of available preferred PLMNs to terminals with Aerial Subscription.

[0326] For example, a terminal may transmit a capability to a NW (e.g., AMF, UAS-AF, etc.) regarding whether it can handle a Preferred PLMN list considering NTZ. In addition, the NW (e.g., AMF, UAS-AF, etc.) may inform the terminal of a Preferred PLMN list based on NTZ for the terminal performing NTZ handling. Alternatively, the NW (e.g., AMF, UAS-AF, etc.) may provide the terminal with an NW capability including a Preferred PLMN list based on NTZ handling.

[0327] For example, UDM may have a UE context indicating whether or not the Aerial UE supporting NTZ transmits the PLMN list via the SOR procedure.

[0328] For example, in connection with the registration process, the AMF can check the terminal subscription from the UDM. The UDM can check the subscription of the terminal. If the terminal subscription includes an Aerial UE subscription, the UDM can obtain the available Preferred PLMN list from the SOR-AF or UAS-AF.

[0329] For example, when NW (e.g., UDM) notifies the terminal of the Preffered PLMN list, NW transparently notifies the terminal of the PLMN list received from SOR-AF or UAS-AF through UDM and AMF.

[0330] For example, the NW (e.g., AMF, UAS-AF, etc.) can inform the UE that the Preferred PLMN list is the Preferred PLMN list for UEs with Aerial UE subscription.

[0331] For example, also, the NW (e.g., AMF, UAS-AF, etc.) can perform the following actions considering the NTZ area restriction. For example, the NW (e.g., AMF, UAS-AF, etc.) can delete the PLMNs that are not available at the location of the corresponding UAV-UE from the Preferred PLMN list, and create (or set) a new Preferred PLMN list considering the NTZ area restriction. The NW (e.g., AMF, UAS-AF, etc.) can transmit the newly created (or set) Preferred PLMN list to the UE.

[0332] For example, when the terminal receives a newly configured PLMN list considering the NTZ, the terminal can perform PLMN selection using the newly configured Preferred PLMN list based on the UAV UE subscription.

[0333] Referring to the examples of FIGS. 8A and 8B, an example of a procedure according to the first example of the disclosure of the present specification is described.

[0334] 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 / 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.

[0335] FIG. 8A and FIG. 8B are first examples of a procedure according to one embodiment of the disclosure of the present specification.

[0336] 1) The UE can send a registration request message to the AMF.

[0337] The registration request message may include NTZ capability information and UAV-ID.

[0338] 2) AMF can send a request message to UDM. For example, AMF can send a Nudm_UECM_Registration request message.

[0339] For example, the request message may include NTZ capability information of the UE, NTZ PLMN indicator, and UAV-ID.

[0340] For example, the NTZ PLMN indicator is an indicator indicating whether the AMF supports the function of notifying the PLMN list to the NTZ support UE.

[0341] 3) UAV UE capability information can be stored in the UE context.

[0342] For example, UAV UE capability information can be stored in the UE context stored by the UDM. AMF, PCF, UAS-AF, etc. can obtain the UE context from the UDM.

[0343] AMF, UDM, PCF, and UAS-AF can store UAV UE capability information in the UE context.

[0344] For example, the PCF can store UAV UE capability information in the UE context based on network policy. Based on network policy, when the UE transmits the UE's subscription to the AMF, and the AMF transmits the UE's subscription to the PCF, the PCF can store the UE's subscription including the UAV UE capability information.

[0345] For example, since UAS-AF receives settings from the UE's application, it can store UAV UE capability information in the UE context.

[0346] Based on the NTZ PLMN indicator of the NW and the NTZ capability information of the UE, UAV UE capability information can be stored in the UE context.

[0347] 4) AMF can send the Nudm_SDM_Get message to UDM. This message can contain the UAV-ID.

[0348] 5) UAV UE subscriber information can be obtained.

[0349] 6) AMF can obtain UE location information from LMF.

[0350] For example, the AMF may transmit a message related to the Nlmf_location_get service to the LMF and obtain the UE's location information from the LMF. The message transmitted by the AMF to the LMF may include a UAV-ID.

[0351] 7. AMF can send a message requesting PLMN information to UAS-AF. For example, AMF can send a Nuasf_NTZPLMNInfo request message to UAS-AF.

[0352] The message transmitted by AMF to UAS-AF may include UAV-ID, NTZ capability information of UE, subscriber information of UE, and location information of UE.

[0353] 8) UAS-AF can determine the preferred PLMN list based on NTZ area restriction information based on the location of the UAV UE and subscriber information of the UE.

[0354] 9) UAS-AF may send a response message to AMF. For example, the response message may be a Nuasf_NTZPLMNInfo response message.

[0355] The response message transmitted by the UAS-AF to the AMF may include a list of preferred PLMNs based on the UAV-ID and NTZ information. The list of preferred PLMNs based on NTZ information may be a list including preferred PLMNs that take NTZ information into account.

[0356] 10) AMF may send a registration acceptance message to the UE.

[0357] The registration acceptance message may include a UAV UE ID (i.e., UAV-ID) and a preferred PLMN list. The preferred PLMN list may be a preferred PLMN list based on NTZ information.

[0358] The registration acceptance message may also include a preferred PLMN list and NTZ information. For example, in the example of FIG. 8b, "preferred PLMN list with NTZ info" may mean a PLMN list and NTZ information.

[0359] 11) The UE may also send a registration completion message (e.g. containing the UAV-ID) to the AMF.

[0360] 12) The UE may update the preferred PLMN list based on the received Preferred PLMN list for the UE's UAV UE subscriber information.

[0361] 13) The UE can operate in IDLE mode.

[0362] 14) The UE can select a PLMN based on a preferred PLMN list based on NTZ information.

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

[0364] The terminal can manage the Preferred PLMN list received from the NW and / or perform PLMN selection.

[0365] The terminal can manage different operator controlled PLMN selector with Access Technology values ​​for each terminal subscription.

[0366] For example, each terminal can manage a subscription-based Operator Control PLMN list.

[0367] For example, based on the Preferred PLMN list value provided by NW, the terminal can manage different operator controlled PLMN selector with Access Technology values ​​for each subscription.

[0368] For example, the UE can utilize the Preferred PLMN list associated with the Aerial subscription.

[0369] For example, a terminal can check if it has an Aerial subscription and use the Preferred PLMN list associated with its subscription.

[0370] A UE with an Aerial subscription may use the preferred PLMN list corresponding to that subscription, which may mean the following: For example, if a terminal (e.g., UE / MS) has an Aerial subscription, the terminal may use a PLMN / access technology combination within the "Operator Controlled PLMN Selector with Access Technology" according to the corresponding subscriber information (subscription).

[0371] For example, if the UE selects a PLMN based on an automatic network selection mode procedure, the UE may perform actions according to the following examples.

[0372] The terminal may select and attempt registration with other PLMN / access technology combinations, if available, in the order in which i, ii, iii, iv, v are allowed, as in the following examples:

[0373] i) The terminal can select the HPLMN (if the EHPLMN list is empty or non-existent) or the highest priority EHPLMN available (if the EHPLMN list is present);

[0374] ii) The terminal can select each PLMN / Access Technology combination (in order of priority) in the SIM's "User Controlled PLMN Selector with Access Technology" data file;

[0375] iii) The terminal can select each PLMN / Access Technology combination (priority) stored in the SIM's "Operator Controlled PLMN Selector with Access Technology" data file (priority) or in the ME;

[0376] iv) The terminal can select any order of received high quality signals and other PLMN / access technology combinations;

[0377] v) The terminal may select other PLMN / access technology combinations in descending order of signal quality.

[0378] When a terminal selects a PLMN, as in the example above, the following explanation may apply. For example, if a terminal (e.g., UE / MS) has an Aerial subscription, the terminal may use a PLMN / access technology combination within the "Operator Controlled PLMN Selector with Access Technology" according to the corresponding subscriber information (subscription).

[0379] In various examples of the disclosure of this specification, “the terminal manages different operator controlled PLMN selectors with Access Technology values ​​for each subscription” and / or “the terminal manages each subscription-based Operator Control PLMN list” may mean the following examples.

[0380] For example, HPLMN can update the "Operator controlled signal threshold per access technology with NTZ area restriction indicator" based on operator policy, UE's subscription information and / or capabilities, and / or UE's location information.

[0381] Additionally, in various examples of the disclosure of the present specification, “when the terminal receives a newly set PLMN list based on NTZ, the UAV UE terminal performs PLMN selection using the newly set Preferred PLMN list based on subscription” may mean the following examples.

[0382] For example, PLMN selection for Aerial UEs supporting NTZ area restriction may be applied.

[0383] For example, a terminal (e.g., UE, MS) may support PLMN selection for an Aerial UE that supports NTZ zone restrictions.

[0384] MS / UE may be considered to apply PLMN selection for Aerial UEs supporting NTZ zone restrictions if the following conditions are met:

[0385] 1) The terminal may support NTZ PLMN indicator indicating that it supports NTZ function or the same;

[0386] 2) NW (e.g., AMF, UAS-AF, etc.) can provide the terminal with a list of PLMNs along with an "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator"; and

[0387] 3) The terminal has Aerial susbscription.

[0388] For example, "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" may include a PLMN list and a PLMN list by RAT type.

[0389] Additionally, the NW may provide an "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" that includes a list of PLMNs within the NTZ area and a list by RAT type, taking into account the NTZ area of ​​the terminal.

[0390] The terminal can perform PLMN selection based on information included in the "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator."

[0391] Additionally, the NW may include a list of PLMNs to be used in the NTZ area and a list by RAT type in the "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator." In this case, the NW may indicate whether the PLMN list included in the "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" is used in the NTZ area using the NTZ area restriction indicator.

[0392] Additionally, the NW may include the PLMN list and RAT type list to be used outside the NTZ area in the "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator." At this time, the NW may inform the UE that the PLMN list and RAT type list are used outside the NTZ area with the NTZ area restriction indicator. The UE determines whether the location of the UE is within the NTZ area, and then performs PLMN selection using the PLMN list and RAT type that match the NTZ area of ​​the UE based on the NTZ area restriction indicator.

[0393] When applying PLMN selection for Aerial UEs that support NTZ area restriction, MS / UE may use "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" instead of "Operator Controlled PLMN Selector with Access Technology".

[0394] In addition, in various examples of the disclosure of this specification, “when the terminal receives a newly set PLMN list based on NTZ, the UAV UE terminal performs PLMN selection based on a newly set Preferred PLMN list based on subscription.” can be expressed as in the following examples.

[0395] For example, when switching on or recovering from lack of coverage, the terminal may perform actions related to the automatic network selection mode procedure.

[0396] For example, if a terminal applies PLMN selection for an Aerial UE supporting NTZ zone restrictions, the following may apply. For example, the terminal may select and attempt registration on other PLMN / access technology combinations, if available, in the order in which i, ii, iii, iv, and v are allowed, as in the following example:

[0397] i) The terminal can select the HPLMN (if the EHPLMN list is empty or non-existent) or the highest priority EHPLMN available (if the EHPLMN list is present);

[0398] ii) The terminal can select each PLMN / Access Technology combination (in order of priority) in the SIM's "User Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" data file;

[0399] iii) The terminal can select each PLMN / access technology combination (priority) in the SIM's "erator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" data file or each PLMN / access technology combination (priority) stored in the ME;

[0400] iv) The terminal can select any order of received high quality signals and other PLMN / access technology combinations;

[0401] v) The terminal may select other PLMN / access technology combinations in descending order of signal quality.

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

[0403] According to the third example of the disclosure of this specification, the following description may be applied.

[0404] For example, a network entity (or network node) may perform actions such as the following examples: The network entity (or network node) may be a UAS-AF, an AMF, a UDM, etc.

[0405] For example, one or more of the following actions may be performed:

[0406] 1. The UAV UE can support NTZ capability. In this case, when the terminal has NTZ capability, the NW (e.g., UAS-AF, etc.) can inform the terminal of a preferred list that is only applicable to the NTZ region. In this case, the NW can inform the UAV UE of the preferred PLMN list that the UAV UE will use.

[0407] 2. A network entity (e.g., UAS-AF) can check whether there is a Preferred PLMN list corresponding to an area related to No transmit zone within the movement trajectory of the terminal. For example, the network entity (e.g., UAS-AF) can receive and check information (e.g., Preferred PLMN list information corresponding to an area related to NTZ) from another NW entity (e.g., PCF, UDM, AMF). For another example, UAS-AF can also check whether there is a Preferred PLMN list corresponding to an area related to No transmit zone within the movement trajectory of the terminal using pre-configured information.

[0408] For example, a terminal may have PLMN list information related to NTZ.

[0409] For example, information regarding which PLMNs are available at a specific location (specific geographic area and altitude range, time information) can be set in the PCF based on a subscription for a specific terminal (e.g., a UAV terminal) or based on an OMA. The PCF can transmit a PLMN list related to the NTZ to the terminal.

[0410] 3. Using these two pieces of information (e.g., time-related information and location-related information), UAS-AF can delete PLMNs that are no longer available due to being in the No transmit zone category from the Preferred PLMN list used by the existing UAV UE. Then, UAS-AF can perform a provisioning procedure to notify the UE of the new Preferred PLMN list.

[0411] 4. UAS-AF can newly provision a Preferred PLMN list to the terminal based on the terminal location information received from AMF or the terminal location information held by UAS-AF.

[0412] 5. NW (UAS-AF, AMF, UDM, etc.) can inform the terminal of the information (e.g., time information related to the PLMN, location information related to the PLMN) that will be used for the PLMN in the Preferred PLMN list. For example, NW (UAS-AF, AMF, UDM, etc.) can inform the terminal of the information that the Preferred PLMN in the Preferred PLMN list is valid.

[0413] The terminal can utilize the newly provisioned Preferred PLMN list based on its subscription information and capability information (e.g., NTZ-related capability information). For example, the terminal may receive the Preferred PLMN list from the AMF and perform a PLMN selection procedure based on the Preferred PLMN list.

[0414] For example, a terminal may perform a PLMN selection procedure based on the Preferred PLMN list only while the Preferred PLMN list is valid, based on the terminal's subscription, the terminal's capability, and the time information (and / or location information) during which the Preferred PLMN list is valid.

[0415] For example, if the time information and location information are invalid, the terminal can perform a PLMN selection procedure based on the existing Preferred PLMN list.

[0416] For Aerial UEs supporting NTZ, information related to the PLMN can be provided.

[0417] For example, a NW (e.g., AMF, UAS-AF, etc.) can inform a UE of its preferred list of PLMNs / Access technologies on a subscription basis. For example, if a UE has a specific subscription, the NW (e.g., AMF) informs the UE of the available preferred list of PLMNs / Access technologies.

[0418] For example, a NW (e.g., AMF, UAS-AF, etc.) can inform a Preferred PLMN or Preferred PLMN list to NTZ support UEs that have Aerial Subscription.

[0419] For example, based on the SOR procedure, SOR-AF or UAS-AF can inform the NW (e.g., AMF) of the Preferred list of PLMN / Access technology available for each location.

[0420] For example, a NW (e.g., AMF, UAS-AF, etc.) can request subscriber information of a terminal from the HPLMN UDM. In this case, the HPLMN UDM can check the terminal capability through the registration request. The HPLMN UDM can check the capability and subscription of the requested terminal. In this case, the HPLMN UDM can determine that the terminal supports NTZ and has an Aerial subscription, and the Network (e.g., OAM, AMF, UDM, PCF, UAS-AF, LMF, etc.) provides a PLMN list for NTZ functionality. For example, the OAM can inform the OAM of available PLMNs, not the network entity. The UAS-AF, etc. can know the PLMN list according to the location of the terminal, as in the examples of FIGS. 8a and 8b below. When LMF informs NW (e.g., AMF, UAS-AF, etc.) of actual UE location information, NW NW (e.g., AMF, UAS-AF, etc.) can know whether actual UE is inside NTZ. UDM, PCF, AMF, etc. can know the PLMN list of terminal.

[0421] Then, the HPLMN UDM can request the SOR-AF or UAS-AF to provide the Preferred PLMN list. After receiving the Preferred PLMN list from the SOR-AF or UAS-AF, the UDM can provide the available preferred PLMN list to terminals with Aerial Subscription.

[0422] For example, a terminal may transmit a capability to a NW (e.g., AMF, UAS-AF, etc.) regarding whether it can handle a Preferred PLMN list considering NTZ. In addition, the NW (e.g., AMF, UAS-AF, etc.) may inform the terminal of a Preferred PLMN list based on NTZ for the terminal performing NTZ handling. Alternatively, the NW (e.g., AMF, UAS-AF, etc.) may provide the terminal with an NW capability including a Preferred PLMN list based on NTZ handling.

[0423] For example, UDM may have a UE context indicating whether or not to transmit a preferred PLMN list via the SOR procedure of an Aerial UE supporting NTZ.

[0424] For example, in connection with the registration process, the AMF can check the terminal subscription from the UDM. The UDM can check the subscription of the terminal. If the terminal subscription includes an Aerial UE subscription, the UDM can obtain the available Preferred PLMN list from the SOR-AF or UAS-AF.

[0425] For example, when a NW (e.g., UDM) notifies a terminal of a Preferred PLMN list, the NW transparently notifies the terminal of the Preferred PLMN list received from SOR-AF or UAS-AF through UDM and AMF.

[0426] For example, the NW (e.g., AMF, UAS-AF, etc.) can inform the UE that the Preferred PLMN list is the Preferred PLMN list for UEs with Aerial UE subscription.

[0427] For example, also, the NW (e.g., AMF, UAS-AF, etc.) can perform the following actions considering the NTZ area restriction. For example, the NW (e.g., AMF, UAS-AF, etc.) can delete the PLMNs that are not available at the location of the corresponding UAV-UE from the Preferred PLMN list, and create (or set) a new Preferred PLMN list considering the NTZ area restriction. The NW (e.g., AMF, UAS-AF, etc.) can transmit the newly created (or set) Preferred PLMN list to the UE.

[0428] For example, when the terminal receives a newly configured Preferred PLMN list considering the NTZ, the terminal can perform PLMN selection using the newly configured Preferred PLMN list based on the UAV UE subscription.

[0429] For example, when a terminal performs PLMN selection, the terminal may select a PLMN based on the Preferred PLMN list only while the Preferred PLMN list is valid, based on the terminal's subscription, the terminal's capability, and the time information (and / or location information) for which the PLMN list is valid. For example, if the time information and location information related to the preferred PLMN list are not valid, the terminal may select a PLMN based on the existing Preferred PLMN list.

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

[0431] FIG. 9a and FIG. 9b are a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0432] 1~11) Steps 1 to 11 of FIGS. 9a and 9b can be performed in the same manner as steps 1 to 11 of FIG. 8.

[0433] 12) The UE can operate in IDLE mode.

[0434] 13) The UE may determine whether to use the PLMN list based on NTZ area restriction information or the PLMN list based on the UE's current location and the UE's subscriber information.

[0435] For example, the UE may perform a PLMN selection procedure based on a selected PLMN list.

[0436] For example, HPLMN can update "Operator controlled signal threshold per access technology with NTZ area restriction indicator" including location information and time information to be applied based on operator policy, subscription information of UE, and / or capability of UE, and / or location information of UE.

[0437] For example, PLMN selection for Aerial UEs supporting NTZ area restriction may be applied.

[0438] For example, a terminal (e.g., UE, MS) may support PLMN selection for an Aerial UE that supports NTZ zone restrictions.

[0439] An MS / UE may be considered to apply PLMN selection for Aerial UEs supporting NTZ area restrictions if one or more of the following conditions are met (or all of them are met):

[0440] 1) The terminal may support NTZ PLMN indicator indicating that it supports NTZ function or the same;

[0441] 2) NW can provide the terminal with a PLMN list along with "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator";

[0442] 3) The terminal has Aerial susbscription;

[0443] 4) The current UE's location belongs to the location information for the NTZ area; and

[0444] 5) The timer related to NTZ region restrictions has not expired;

[0445] When applying PLMN selection for Aerial UEs that support NTZ area restriction, MS / UE may use "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" instead of "Operator Controlled PLMN Selector with Access Technology".

[0446] For example, when switching on or recovering from lack of coverage, the terminal may perform actions related to the automatic network selection mode procedure.

[0447] For example, if a terminal applies PLMN selection for an Aerial UE supporting NTZ zone restrictions, the following may apply. For example, the terminal may select and attempt registration on other PLMN / access technology combinations, if available, in the order in which i, ii, iii, iv, and v are allowed, as in the following example:

[0448] i) The terminal can select the HPLMN (if the EHPLMN list is empty or non-existent) or the highest priority EHPLMN available (if the EHPLMN list is present);

[0449] ii) The terminal can select each PLMN / Access Technology combination (in order of priority) in the SIM's "User Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" data file;

[0450] iii) If the PLMN selection of an Aerial UE supporting NTZ area restrictions is not applied, the UE may select each PLMN / Access Technology combination (in order of priority) present in the "Operator Controlled PLMN Selector with Access Technology" data file of the SIM (in order of priority) or stored in the ME (in order of priority);

[0451] Note that “PLMN selection of Aerial UEs supporting NTZ area restrictions is not applied” may mean that none of the conditions described above are met (or, any of them are not met):

[0452] 1) The terminal may support NTZ PLMN indicator indicating that it supports NTZ function or the same;

[0453] 2) NW can provide the terminal with a PLMN list along with "Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator";

[0454] 3) The terminal has Aerial susbscription;

[0455] 4) The current UE's location belongs to the location information for the NTZ area; and

[0456] 5) The timer related to NTZ region restrictions has not expired;

[0457] In other cases, the terminal may select each PLMN / Access Technology combination (in order of priority) present in the SIM's "erator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator" data file;

[0458] iv) The terminal can select any order of received high quality signals and other PLMN / access technology combinations;

[0459] v) The terminal may select other PLMN / access technology combinations in descending order of signal quality.

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

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

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

[0463] For example, with respect to the example of FIG. 10, the operations described in the examples of FIGS. 1 to 9A and 9B 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.

[0464] In the example of FIG. 10, the first network entity may be a network entity related to mobility. For example, the first network entity may be an AMF.

[0465] The second network entity may be a network entity associated with the UAS. For example, the second network entity may be a UAS-AF.

[0466] In step (S1001), the UE may transmit a registration request message.

[0467] For example, a registration request message may include capability information.

[0468] For example, capability information may include information that supports capabilities related to NTZ.

[0469] In step (S1002), the second network entity may transmit a PLMN list to the first network entity.

[0470] For example, a second network entity may receive a PLMN information request message containing subscriber information of the UE from a first network entity.

[0471] For example, the PLMN information request message may further include at least one of capability information indicating that the UE supports capabilities related to NTZ, UAV ID information, and / or location information of the UE.

[0472] For example, a second network entity may determine a PLMN list for the UE based on the UE's location information and the subscriber information.

[0473] For example, based on the subscriber information relating to aerial subscriber information, the second network entity may determine the PLMN based on NTZ area restrictions.

[0474] For example, the second network entity may transmit a PLMN information response message including the PLMN list to the first network entity.

[0475] For example, the PLMN Information Response message may further include information related to the NTZ.

[0476] For example, the PLMN Information Response message may further include an Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator.

[0477] In step (S1003), the first network entity may transmit a registration acceptance message to the UE.

[0478] For example, a registration acceptance message may include a list of PLMNs.

[0479] For example, the PLMN list may be a preferred PLMN list based on NTZ information generated by a second network entity associated with an Unmanned Aircraft System (UAS).

[0480] For example, the PLMN list may not include PLMNs associated with NTZs within the UE's travel path.

[0481] For example, a registration acceptance message may include information related to the PLMN list and NTZ.

[0482] For example, the registration acceptance message may further include an Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator.

[0483] In step (S1004), the UE can select a PLMN.

[0484] For example, the UE may select a PLMN based on the subscriber information and the PLMN list included in the registration acceptance message.

[0485] For example, based on subscriber information relating to aerial subscriber information, the UE may select a PLMN based on No Transmit Zone (NTZ) area restrictions.

[0486] For example, the PLMN list received by the UE may not include PLMNs associated with NTZs within the UE's travel path. In this case, a second network entity may have determined the PLMN list so as not to include PLMNs associated with NTZs within the UE's travel path.

[0487] As another example, the UE may not select a PLMN related to an NTZ within its mobile route from among the PLMN list based on the received PLMN list and NTZ information.

[0488] For example, the UE may select a PLMN based on the NTZ area restriction based on at least one of the following conditions being met: the UE has aerial subscriber information, the guswo location of the UE falls within the location information for the NTZ area restriction, and / or a timer related to the NTZ area restriction has not expired.

[0489] According to one embodiment of the disclosure of the present specification, the NW can set a PLMN list according to the subscription of the terminal.

[0490] According to one embodiment of the disclosure of the present specification, a terminal can perform PLMN selection based on a PLMN list based on its subscription information.

[0491] This specification may have various effects.

[0492] For example, an aerial UE can perform communication taking NTZ into account.

[0493] For example, based on the Aerial subscription information of the terminal, the terminal can perform PLMN selection using the received PLMN list. For example, the terminal can receive a subscription-specific PLMN list. Additionally, the terminal and / or the network can dynamically utilize a PLMN list based on NTZ area restrictions.

[0494] For example, in various situations, the terminal can effectively select the PLMN desired by the NW.

[0495]

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

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

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

[0499] For reference, the operation of a network node (e.g., AMF, SMF, PCF, UDM, UAS-AF, LMF, 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 the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of 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.

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

[0501] 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 of the spirit and claims of this specification.

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

[0503] 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 transmitting a registration request message including capability information of User Equipment (UE) to a first network entity; receiving a registration acceptance message from the first network entity; and A step of selecting a PLMN based on subscriber information and a PLMN list included in the registration acceptance message, A method wherein the PLMN is selected based on a No Transmit Zone (NTZ) area restriction, based on the subscriber information being related to aerial subscriber information.

2. In paragraph 1, A method in which the above capability information includes information that supports capabilities related to NTZ.

3. In paragraph 1 or 2, A method wherein the above PLMN list is a preferred PLMN list based on NTZ information generated by a second network entity related to an Unmanned Aircraft System (UAS).

4. In any one of paragraphs 1 to 3, A method wherein the PLMN list does not include a PLMN related to an NTZ within the movement path of the UE.

5. In any one of paragraphs 1 to 4, A method wherein the above registration acceptance message includes information related to the PLMN list and NTZ.

6. In any one of paragraphs 1 to 5, A method according to claim 1, wherein the registration acceptance message further comprises an Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator.

7. In any one of paragraphs 1 to 6, A method in which the PLMN is selected based on the NTZ area restriction based on at least one of the following conditions: the UE has aerial subscriber information, the current location of the UE falls within location information for the NTZ area restriction, and / or a timer related to the NTZ area restriction has not expired.

8. In any one of paragraphs 1 to 6, A method wherein the PLMN is selected based on the NTZ area restriction based on at least one of the following conditions: the UE supports NTZ-related capabilities, the UE receives an operator-controlled PLMN selector having an access technology with an NTZ area restriction indicator, the UE has aerial subscriber information, the current location of the UE falls within the location information for the NTZ area restriction, and / or a timer related to the NTZ area restriction has not expired.

9. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; The actions performed based on the above instructions being executed by the one or more processors are: A device according to any one of claims 1 to 8.

10. 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 8.

11. 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.

12. A step of receiving a PLMN information request message including subscriber information of a User Equipment (UE) from a first network entity related to mobility; A step of determining a PLMN list for the UE based on the location information of the UE and the subscriber information; and A step of transmitting a PLMN information response message including the PLMN list to the first network entity, A method wherein the PLMN is determined based on a No Transmit Zone (NTZ) area restriction, based on the subscriber information relating to the aerial subscriber information.

13. In paragraph 12, A method wherein the PLMN information request message further includes at least one of capability information indicating that the UE supports a capability related to NTZ, UAV ID information, and / or location information of the UE.

14. In paragraph 12 or 13, A method wherein the PLMN list does not include a PLMN related to an NTZ within the movement path of the UE.

15. In any one of paragraphs 12 to 14, A method wherein the PLMN information response message further includes information related to NTZ.

16. In any one of paragraphs 12 to 15, The above PLMN list is a preferred PLMN list based on NTZ area restrictions.

17. In any one of paragraphs 12 to 16, A method wherein the PLMN information response message further includes an Operator Controlled PLMN Selector with Access Technology with NTZ area restriction indicator.

18. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; The actions performed based on the above instructions being executed by the one or more processors are: A device according to any one of claims 12 to 17.

Images