Communication based on ntz

Abstract

One disclosure of the present specification provides a method. The method may comprise the steps of: receiving a registration request message from a UE; transmitting the registration request message to a mobility-related network entity; receiving a registration acceptance message from the mobility-related network entity; transmitting the registration acceptance message to the UE; receiving NTZ-related information related to the UE from the mobility-related network entity; and determining whether to transmit a downlink message to the UE.

Description

NTZ-based communication

[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 80 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] For aviation-related communications, such as UAVs, a No-Transmit Zone (NTZ) has been introduced. Conventionally, the core network could determine whether a terminal was within the NTZ. However, the core network did not provide NTZ-related information to the base station. This caused the base station to be unable to determine whether a terminal was within the NTZ. Consequently, the base station had difficulty transmitting messages received from the CN or messages transmitted by the base station to the UE.

[0006] In one aspect, a method is provided. The method may include: receiving a registration request message from a UE; transmitting the registration request message to a network entity associated with mobility; receiving a registration acceptance message from the network entity associated with mobility; transmitting the registration acceptance message to the UE; receiving NTZ-related information associated with the UE from the network entity associated with mobility; and determining whether to transmit a downlink message to the UE.

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

[0008] In one aspect, a method is provided. The method comprises the steps of: receiving a registration request message of a UE from a base station; transmitting a registration acceptance message for the UE to the base station; and transmitting NTZ-related information related to the UE to the base station.

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

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

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

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

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

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

[0015] FIG. 7 illustrates an example of a procedure related to NTZ-related information according to one embodiment of the disclosure of the present specification.

[0016] FIG. 8 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

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

[0018] 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. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

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

[0020] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0036] 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, at least some of the 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 based on various proposals of the present specification.

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

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

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

[0040] 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. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0075] - AUSF (Authentication Server Function)

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

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

[0078] - USDF (Unstructured Data Storage Function)

[0079] - NEF (Network Exposure Function)

[0080] - I-NEF (Intermediate NEF)

[0081] - NRF (Network Repository Function)

[0082] - NSSF (Network Slice Selection Function)

[0083] - PCF (Policy Control Function)

[0084] - SMF (Session Management Function)

[0085] - UDM (Unified Data Management)

[0086] - UDR (Unified Data Repository)

[0087] - UPF (User Plane Function)

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

[0089] - AF (Application Function)

[0090] - UE (User Equipment)

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

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

[0093] - NWDAF (Network Data Analytics Function)

[0094] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0125] - Initial registration for 5GS; or

[0126] - mobility registration update; or

[0127] - Periodic registration update; or

[0128] - Emergency registration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0180] 3GPP is discussing ways to support UAVs in Phase 3 of its Rel-19 standard, Study on Phase 3 for Uncrewed Aerial Systems (UAS), Uncrewed Aerial Vehicles (UAVs), and Urban Air Mobility (UAM) (FS_UAS_Ph3) (TR 23.700-59). Specifically, the study is focused on the following objectives (SP-231801).

[0181] To support additional scenarios and requirements for UAVs and UAM, potential architectural and system-level improvements need to be investigated and identified.

[0182] Specifically, the following examples may be included in the objective:

[0183] - Based on SA1 requirements and input from aviation fora, study whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for i.e. pre-mission flight planning, in-mission flight monitoring, C2 communication reliability, interfacing with UTM (e.g. supporting the scenario of multiple USS serving the geographical areas corresponding to the UAV flight path)

[0184] - Based on SA1 requirements, it is necessary to study whether and how to enable network-assisted / ground-based mechanism for DAA (Detect And Avoid) that leverages information collected and generated in the 5GS, including whether and what new information is needed.

[0185] - There is a need to discuss how to support no-transmit zones (NTZ) for UAVs.

[0186] Regarding the need to discuss how to support no-transmit zones (NTZ) for UAVs, the following interim conclusion is stated in TR 23.700-59v1.0.0:

[0187] Key Issue: Describes interim conclusions regarding support for No Transmit Zones (NTZs). Reference may be made to TR 23.700-59v1.0.0 S8.3.

[0188] To support NTZ, one or more of the following principles may be applied:

[0189] 1) NTZ enforcement may apply to UEs that are UAV UEs with an aerial subscription (aka aeriel UE).

[0190] 2) NTZ is supported in both LTE and NR.

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

[0192] 4) UAV UEs located within the NTZ (in three-dimensional space taking into account altitude restrictions) are not permitted to transmit in the restricted frequency band, regardless of the service type.

[0193] 5) UAV UEs will not transmit or attempt to transmit within the restricted frequencies, locations, and altitudes defined by the NTZ. However, UAV UEs may transmit and receive normally outside these restricted areas.

[0194] 6) For UAV UEs that support NTZ regulation, NTZ information can be set. Such UAV UEs can recognize the presence of NTZ.

[0195] 7) UAV UEs located in the NTZ may receive downlink data from the network, as long as they do not violate regulatory requirements.

[0196] For a UAV UE, an example of setting up and / or provisioning NTZ support information is described. An example of NTZ enforcement by a UAV UE is also described.

[0197] NTZ support information (or NTZ policies) such as the following examples can be configured and / or provisioned for the UAV UE:

[0198] - A list of geographical areas (including coordinates including longitude, latitude, and altitude / height restrictions) and restricted frequency bands.

[0199] Note that if local regulations require NTZ, NTZ support information may be set on the UAV UE before the UAV UE accesses the operator's network.

[0200] The above NTZ support information can be provided to the UAV UE using one or more of the following methods:

[0201] - NTZ support information can be pre-configured;

[0202] - NTZ support information may be provided and / or updated by AMF during the registration process;

[0203] - NTZ support information may be provided and / or updated by AMF during the UE configuration update procedure specified in S4.2.4.2 of TS 23.502 V18.5.0;

[0204] - NTZ support information may be provided or updated during the attach procedure by the Mobility Management Entity (MME);

[0205] - NTZ support information may be provided or updated during the Tracking Area Update (TAU) procedure by the MME;

[0206] - NTZ support information may be provided or updated by PCF;

[0207] - NTZ support information may be provided or updated by the Application Function (AF) (e.g. NTZ AF, UAS (Uncrewed Aerial System) Service Supplier (USS), TPAE).

[0208] UAV UE can perform NTZ enforcement independently of 3GPP releases.

[0209] UAV UEs that support NTZ (e.g., UAV UEs in Rel-19 and later releases) can perform the following actions:

[0210] a) The UE can implement NTZ based on configured and / or provisioned NTZ support information.

[0211] b) When NTZ enforcement is applied, the UAV UE does not transmit signals or data.

[0212] c) The UE does not select / reselect a cell that is fully affected by NTZ.

[0213] For reference, the UAV UE may also transmit information related to NTZ support to the network entity involved in mobility (e.g., AMF or MME).

[0214] Note that registration updates may be required before a UAV UE enters the NTZ, so that the network can detect the presence of a UAV within the NTZ. Alternatively, registration updates may also be required when a UAV UE exits the NTZ. Alternatively, the AMF may provide the NTZ as an AoI to the NG-RAN for registration.

[0215] Note that extension of service restrictions for NTZ may be required using Restricted Transmission Areas (RTAs) mapped from NTZ information.

[0216] For aviation-related communications, such as UAVs, a No-Transmit Zone (NTZ) has been introduced. Conventionally, the core network can determine whether a terminal is within the NTZ. However, the core network did not provide NTZ-related information to the base station. This resulted in the base station not knowing whether a terminal is within the NTZ. Consequently, the base station had difficulty transmitting messages received from the CN or messages transmitted by the base station to the UE. The problems of the conventional technology are described in detail below.

[0217] In a No Transmit Zone (NTZ), UEs are not permitted to transmit. However, as specified in Section 8.3.1, Item 7) of TR 23.700-59, the UE may be able to receive downlink data from the network. Accordingly, two types of NTZs may exist:

[0218] 1) NTZ where neither transmission by the UE nor transmission to the UE (e.g. reception by the UE) is allowed; or

[0219] 2) NTZ where transmission by UE is not allowed, but transmission to UE (e.g. reception by UE) is allowed.

[0220] A message (e.g., data, NAS message, paging message, etc.) that needs to be transmitted to a UE may be generated in the Core Network (CN). In this case, the CN may want to transmit this message to the UE for various reasons. For example, the CN may consider / determine that the UE is located in the NTZ corresponding to 2) above. In this case, the CN may want to transmit a message to the UE located in the NTZ. For another example, the CN may include the NTZ corresponding to 1) above in the Registration Area (RA) of the UE, but the CN may not be able to determine whether the UE is located in the NTZ because the UE is in idle mode. In this case, the CN may want to transmit a message to the UE located in the NTZ.

[0221] When the CN transmits a message to the UE, the RAN (e.g., base station) can receive this message. The RAN (base station) can attempt to forward the message sent by the CN to the UE. For 5GS, the RAN can receive the message to the UE from the AMF or UPF. For Evolved Packet System (EPS), the RAN can receive the message to the UE from the MME or Serving Gateway (S-GW). The RAN, which receives the message to the UE from the CN, can attempt to forward the message to the UE.

[0222] However, if the UE is located in the NTZ, transmission by the UE is not permitted. Therefore, even if the UE receives a message from the base station, the UE cannot respond to the network or transmit an uplink message. The base station may expect a response or uplink message from the UE. In this case, if the RAN does not have NTZ-related information, the RAN may determine that the message transmission to the UE has failed. This may result in the RAN repeatedly attempting to transmit the message to the UE.

[0223] As in the example above, instead of the RAN receiving a message from the CN to the UE, the RAN itself may want to generate and transmit a message (e.g., an RRC message) to the UE. Even in this case, transmission by the UE is not permitted if the UE is located in the NTZ. Therefore, even if the UE receives a message from the RAN, the UE cannot respond to the network or transmit an uplink message. Similarly, in this case, the RAN expects a response or uplink message from the UE. However, if the RAN does not have NTZ-related information, the RAN may determine that the message transmission to the UE has failed. Accordingly, the RAN may repeatedly attempt to transmit the message to the UE.

[0224] Repeated transmission attempts to UEs located in the NTZ, as described above, can waste network resources. Therefore, a solution is needed.

[0225] The method proposed in this disclosure may be composed of a combination of one or more of the operations / configurations / steps described below.

[0226] In this specification, UE (User Equipment), terminal, UAV (Uncrewed Aerial Vehicle), UAV UE, and Aerial UE may be used as terms with the same meaning.

[0227] In this specification, NG-RAN may be used as a term with the same meaning as base station, RAN, etc.

[0228] In this specification, transmission by a UE may mean transmission / transmission of an uplink (UL) message (or data) from the UE.

[0229] In this specification, transmission to a UE may mean sending / transmitting a downlink (DL) message (or data) to the UE, or receiving a DL message (or data) by the UE.

[0230] In this specification, a message in an uplink message from a UE and a downlink message to a UE may be interpreted as including one or more of data, traffic, and signaling.

[0231] The various examples disclosed in this specification are described primarily with respect to NTZ scenarios. However, these are merely examples. For example, the methods proposed in this specification can be applied universally not only to NTZ scenarios but also to scenarios where transmission by the UE is not permitted.

[0232] The methods presented below may be performed or used in combination or complementary manner.

[0233] In this specification, descriptions of content identical to prior art will be omitted, and the description will primarily focus on the content proposed in the disclosure of this specification. For UAS-related operations and procedures, reference will be made primarily to TS 23.256 V18.4.0.

[0234] For 5G system related operations and procedures, reference may be made to TS 23.501 V18.5.0, TS 23.502 V18.5.0, TS 23.503 V18.5.0, TS 38.413 V18.1.0, TS 38.423 V18.1.0, TS 38.331 V18.1.0, etc.

[0235] For EPS related operations and procedures, please refer to TS 23.401 V18.5.0, TS 36.413 V18.1.0, TS 36.423 V18.1.0, TS 36.331 V18.1.0, etc.

[0236] In relation to the 5G System, various examples of the disclosure of this specification are described.

[0237] A network entity (e.g., AMF) involved in mobility may provide one or more of the following information related to the UE's operating mode / characteristics to the NG-RAN. Information such as the examples of i) to v) below may be provided explicitly, implicitly, implicitly, or in a combination thereof:

[0238] i) Information related to the UE being located in the NTZ, or information related to the UE being located in the NTZ.

[0239] ii) Information related to whether the UE can only receive (or only transmit to the UE), or whether the UE can only receive (or only transmit to the UE). For example, this information may be interpreted as information related to whether the UE is operating or is likely to operate in Receive-only mode / state.

[0240] iii) Information related to the UE being unable to transmit (or receive from the UE), or information related to the UE being unable to transmit (or receive from the UE).

[0241] iv) Information that the entire Registration Area of ​​the UE is NTZ or that the entire Registration Area of ​​the UE may be NTZ.

[0242] v) Information that part of the UE's Registration Area is NTZ or that part of the UE's Registration Area may be NTZ.

[0243] For reference, information related to the operation mode / characteristics of the UE according to examples i) to v) may also be referred to as information related to NTZ.

[0244] For example, information related to the UE's operating mode / characteristics according to examples i) to v) may be interpreted as information to inform the NG-RAN that the UE cannot or will not transmit a response or uplink message to the network.

[0245] The AMF may recognize and / or determine that the UE is capable of transmitting a response or uplink message to the network (or that the UE is capable of performing normal operations). In this case, the AMF may notify the NG-RAN of this. The AMF may notify the NG-RAN of this explicitly, implicitly, in an implicit or a combination thereof. For example, the AMF may provide the NG-RAN with information contrary to i) to v) above. In another example, the AMF may not provide the NG-RAN with information related to the UE's operation mode / characteristics according to the examples of i) to v) above.

[0246] The reason why AMF provides UE operation mode / characteristics related information according to examples i) to v) to NG-RAN may be based on one or more of the following conditions / information. For example, based on one or more of the conditions / information a) to l), AMF may provide one or more of the information i) to v) to NG-RAN:

[0247] a) When the subscriber information of the UE (subscriber information stored in the UDM) includes aerial subscription information;

[0248] b) If the UE's subscriber information includes the ability to provide information related to the UE's operating mode / characteristics to the base station;

[0249] c) NTZ information (e.g. NTZ assistance information);

[0250] d) If the UE is recognized / determined to be located or likely to be located in the NTZ;

[0251] e) when the UE is aware and / or is likely to be located in an NTZ where transmission to (e.g. reception by) the UE is permitted;

[0252] f) If the UE is aware and / or is likely to be located in a location where transmission by the UE is not permitted;

[0253] g) When the UE is aware / determined to be in a position where transmission by the UE is not permitted and transmission to the UE (i.e. reception by the UE) is permitted, or is likely to be in a position;

[0254] h) If all or part of the UE’s Registration Area is NTZ;

[0255] i) When the UE’s Registration Area and NTZ overlap;

[0256] j) If the UE is a UAV / drone;

[0257] k) local configuration of AMF; and / or

[0258] l) Business policy.

[0259] AMF may provide UE operation mode / characteristics related information to NG-RAN according to examples i) to v) in one or more of the following cases or through procedures or messages:

[0260] i) When AMF provides context information about the UE to NG-RAN (e.g., configuration, change), it may transmit UE operation mode / characteristics-related information to NG-RAN. For example, AMF may transmit a message containing context information about the UE and one or more of UE operation mode / characteristics-related information from i) to v) to NG-RAN.

[0261] II) When the AMF transmits a paging message to the NG-RAN for the UE, it may include one or more UE operation mode / characteristics-related information from i) to v). For example, the AMF may transmit a paging message including one or more of i) to v) to the NG-RAN.

[0262] III) When the AMF transmits a NAS message to the UE and transmits it to the NG-RAN, it may also provide one or more pieces of UE operation mode / characteristics-related information from i) to v). For example, the AMF may transmit a NAS message containing one or more pieces of information from i) to v) to the NG-RAN.

[0263] IV) When one or more of the UE operation mode / characteristics information among i) to v) changes, the AMF may notify the NG-RAN of the change. For example, the AMF may transmit information to the NG-RAN regarding a change in one or more of the information among i) to v).

[0264] The NG-RAN may store UE operation mode / characteristics related information (e.g., one or more of i) to v) provided (or received) from the AMF) in context information for the UE. The NG-RAN may also transmit the UE operation mode / characteristics related information (e.g., one or more of i) to v)) to the target NG-RAN during handover.

[0265] The NG-RAN may receive a downlink message destined for the UE from the CN (e.g., from the AMF or from the UPF). In this case, the NG-RAN may transmit, or attempt to transmit, the downlink message destined for the UE to the UE. The NG-RAN may also have received UE operation mode / characteristics related information (e.g., one or more of i) to v) from the AMF. In this case, the NG-RAN may determine, based on the UE operation mode / characteristics related information (e.g., one or more of i) to v), that it is possible or meaningful for the NG-RAN to transmit a downlink message to the UE. Based on this determination, the NG-RAN may transmit, or attempt to transmit, the downlink message destined for the UE to the UE.

[0266] In some implementations, the NG-RAN may have received UE operation mode / characteristics related information (e.g., one or more of i) to v) from the AMF. In this case, based on the UE operation mode / characteristics related information (e.g., one or more of i) to v), the NG-RAN may determine that the UE cannot respond to the NG-RAN's transmission or transmission attempt, or that the UE cannot transmit an uplink message. For example, based on the UE operation mode / characteristics related information (e.g., one or more of i) to v), the NG-RAN may determine and / or determine that transmission from the UE is not permitted. If the NG-RAN determines / decides that transmission from the UE is not permitted, the NG-RAN may make one or more of the following decisions:

[0267] A) The NG-RAN may determine that the downlink message transmission or transmission attempt to the UE was successful.

[0268] B) The NG-RAN may determine that the downlink message transmission or transmission attempt to the UE did not fail.

[0269] C) The NG-RAN may decide that there is no need to retransmit or attempt to retransmit the downlink message to the UE.

[0270] D) NG-RAN may decide that it does not need to perform abnormal handling for the UE.

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

[0272] FIG. 7 illustrates an example of a procedure related to NTZ-related information according to one embodiment of the disclosure of the present specification.

[0273] The example of FIG. 7 illustrates an example of a procedure according to various examples of the disclosure of the present specification described above. For example, according to the example of FIG. 7, the AMF may provide the NG-RAN with information related to the UE operation mode / characteristics (or NTZ-related information) (e.g., one or more of i) to v). Based on this information, the NG-RAN may determine whether to transmit a downlink message to the UE. Furthermore, after the NG-RAN transmits the downlink message, the NG-RAN may determine whether to determine that the transmission is successful.

[0274] Below, the procedure according to the example of Fig. 7 is described in detail.

[0275] 1. The NG-RAN can receive the registration request message transmitted by the UE to the network.

[0276] 2. NG-RAN can forward the above registration request message to AMF.

[0277] 3. AMF can perform serving AMF registration for UEs using UDM. For example, AMF can perform serving AMF registration for UEs based on the Nudm_UECM_Registration service.

[0278] 4. AMF can obtain subscriber information of the UE from the UDM. For example, AMF can obtain subscriber information of the UE based on the Nudm_SDM_Get service.

[0279] 5. AMF may subscribe to a service for providing / receiving notification of changes in subscriber information for UEs from UDM. For example, AMF may subscribe to a service for providing and / or receiving notification of changes in subscriber information for UEs from UDM based on the Nudm_SDM_Subscribe service.

[0280] 6. AMF can send a registration acceptance message. NG-RAN can receive the registration acceptance message sent by AMF to UE.

[0281] 7. NG-RAN can forward the above registration acceptance message to the UE.

[0282] 8. The AMF may determine whether to provide the NG-RAN with UE operation mode / characteristics related information (or NTZ related information) related to the UE. The UE operation mode / characteristics related information (or NTZ related information) may include one or more of the information from i) to v) described above. For example, the AMF may determine whether to provide the NG-RAN with the UE operation mode / characteristics related information (or NTZ related information) related to the UE based on one or more of the conditions and / or information from a) to l).

[0283] 9. AMF may provide NG-RAN with UE operation mode / characteristics related information (or NTZ related information) related to the UE (e.g., including one or more of i) to v).

[0284] 10. The UPF can receive downlink data from the UE. Accordingly, the UPF can transmit the downlink data from the UE to the NG-RAN.

[0285] Although not shown in the example of FIG. 7, it is assumed that a PDU (Protocol Data Unit or Packet Data Unit) Session is established after the UE registers with the network. For example, after receiving a registration acceptance message, the UE may transmit a PDU Session Establishment Request message to the NG-RAN, and the NG-RAN may transmit the PDU Session Establishment Request message to the AMF. The AMF may transmit the UE's PDU Session Establishment Request message to a network entity (e.g., SMF) involved in the session. The SMF may transmit a PDU Session Establishment Acceptance message to the AMF, the AMF may transmit a PDU Session Establishment Acceptance message to the NG-RAN, and the NG-RAN may transmit a PDU Session Establishment Acceptance message to the UE.

[0286] 11. The NG-RAN that receives downlink data to the UE can decide whether to transmit a downlink message to the UE.

[0287] For example, the NG-RAN, which has received downlink data to the UE, may determine that it is possible or meaningful to transmit a downlink message to the UE based on the UE operation mode / characteristics related information (or NTZ related information) (e.g., including one or more of i) to v) provided from the AMF in step 9).

[0288] 12. The NG-RAN may transmit downlink data to the UE. For example, the NG-RAN may transmit downlink data to the UE based on the decision made in step 11.

[0289] And the NG-RAN may determine that the UE cannot respond to the above transmission or transmission attempt or transmit the uplink message based on the UE operation mode / characteristics related information (or NTZ related information) provided by the AMF (e.g., including one or more of i) to v). In this case, if the NG-RAN determines and / or determines that transmission from the UE is not permitted, the NG-RAN may make one or more of the decisions from A) to D).

[0290] With respect to EPS, various examples of the disclosures herein may be applied. For example, operations related to AMF in the disclosures herein may be interpreted as operations related to MME. Operations related to NG-RAN may be interpreted as operations related to eNB. Operations related to UPF may be interpreted as operations related to S-GW.

[0291] In some implementations, the various examples described in the disclosure of this specification may be generalized and applied to operations between a CN and a RAN and / or to operations of the RAN.

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

[0293] FIG. 8 illustrates an example of a procedure performed according to one embodiment of the disclosure of the present specification.

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

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

[0296] In the example of FIG. 8, the network entity may be, for example, a network entity related to mobility. For example, the network entity related to mobility may be an AMF.

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

[0298] In step (S802), the base station may transmit a registration request message to the network entity.

[0299] At step (S803), the network entity may transmit a registration acceptance message for the UE.

[0300] In step (S804), the base station may transmit a registration acceptance message to the UE.

[0301] In some implementations, a network entity may decide whether to transmit NTZ-related information related to the UE to the base station.

[0302] For example, whether to transmit NTZ-related information related to the UE to the base station:

[0303] a) If the subscriber information of the above UE includes aerial subscription information;

[0304] b) If the subscriber information of the UE includes information related to the ability to provide NTZ-related information related to the UE to the base station;

[0305] c) NTZ support information;

[0306] d) If the UE is determined to be located in the NTZ;

[0307] e) If the UE is determined to be located in an NTZ where transmission to the UE is permitted;

[0308] f) If the UE is or is determined to be in a location where transmission by the UE is not permitted;

[0309] g) If the UE is determined to be in a position where transmission by the UE is not permitted and transmission to the UE is permitted;

[0310] h) If all or part of the registration area of ​​the above UE is NTZ;

[0311] i) When the above UE's light path area and the above NTZ overlap;

[0312] j) If the above UE is a UAV / drone;

[0313] k) local configuration of network entities related to mobility; and

[0314] l) may be determined based on one or more of the business policies.

[0315] At step (S805), the network entity can transmit information related to NTZ to the base station.

[0316] For example, the base station may receive NTZ-related information related to the UE from a network entity related to said mobility.

[0317] For example, NTZ-related information related to a UE may include one or more of: i) information related to the UE being located in an NTZ; ii) information related to only transmission to the UE being possible; iii) information related to the inability to receive from the UE; iv) information related to the entire Registration Area of ​​the UE being an NTZ; and v) information related to a portion of the Registration Area of ​​the UE being an NTZ.

[0318] In step (S806), the base station may determine whether to transmit a downlink message to the UE.

[0319] For example, step (S806) may be performed based on the base station receiving a downlink message related to the UE from a network entity (e.g., UPF) related to the user plane.

[0320] A method comprising the step of determining whether to transmit a downlink message to the UE based on NTZ-related information related to the UE.

[0321] The base station may decide to transmit a downlink message to the UE. In this case, the base station may transmit the downlink message to the UE.

[0322] In some implementations, based on NTZ-related information associated with a UE, the base station may determine that the UE cannot respond to a downlink message or that the UE cannot transmit an uplink message.

[0323] In some implementations, the base station may determine whether transmission of the downlink message was successful based on NTZ-related information associated with the UE.

[0324] For example, based on NTZ-related information related to the UE, the base station may determine one or more of: A) whether transmission of the downlink message was successful, B) whether transmission of the downlink message did not fail, C) whether retransmission of the downlink message is required, and / or D) whether to perform abnormal handling for the UE.

[0325] According to one embodiment of the disclosure of the present specification, the AMF may provide the NG-RAN with information related to the UE's operation mode / characteristics (or NTZ related information) (e.g., including one or more of i) to v).

[0326] According to one embodiment of the disclosure of the present specification, the NG-RAN may determine and / or judge whether to transmit a downlink message to the UE based on information related to the operation mode / characteristics of the UE (or NTZ related information) (e.g., including one or more of i) to v).

[0327] According to one embodiment of the disclosure of the present specification, when the NG-RAN transmits a downlink message to the UE, it can determine and / or judge whether a response / uplink message will be received from the UE based on information related to the UE's operation mode / characteristics (or NTZ related information) (e.g., including one or more of i) to v).

[0328] According to one embodiment of the disclosure of the present specification, if the NG-RAN determines / judges that a response / uplink message will be received from the UE, and the response / uplink message is not received, the NG-RAN may perform retransmission for the downlink message. Conversely, if the NG-RAN determines / judges that a response / uplink message will not be received from the UE, the NG-RAN may not perform retransmission for the downlink message even if the response / uplink message is not received.

[0329] This specification may have various effects.

[0330] For example, communication based on NTZ can be performed effectively.

[0331] For example, information related to NTZ can also be provided to base stations, thereby preventing unnecessary waste of network resources.

[0332] For example, if a UE's transmission is not permitted but its reception is permitted, the network can transmit a downlink message to the UE. In this case, even if there is no response from the UE, the network can avoid unnecessary retransmissions to the UE, thereby avoiding unnecessary waste of network resources.

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

[0334] 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 (e.g., UE) 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 (105 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0335] 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 (e.g., UE) described in the disclosure of this specification.

[0336] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, UDM, etc.) or a base station (e.g., NG-RAN, gNB, 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 a network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of a terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

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

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

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

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

Claims

1. A step of receiving a registration request message from User Equipment (UE); A step of transmitting the above registration request message to a network entity related to mobility; A step of receiving a registration acceptance message from a network entity related to the above mobility; A step of transmitting the above registration acceptance message to the UE; A step of receiving No Transmit Zone (NTZ) related information related to the UE from a network entity related to the mobility; and A method comprising the step of determining whether to transmit a downlink message to the UE based on NTZ-related information related to the UE.

2. In paragraph 1, A method further comprising the step of transmitting the downlink message to the UE.

3. In paragraph 2, A method further comprising the step of determining whether transmission of the downlink message was successful based on NTZ-related information related to the UE.

4. In paragraph 2, A method further comprising, based on NTZ-related information related to the UE, determining one or more of: i) whether transmission of the downlink message was successful, ii) whether transmission of the downlink message did not fail, iii) whether retransmission of the downlink message is required, and / or iv) whether abnormal handling is to be performed for the UE.

5. In paragraph 2, A method further comprising the step of determining, based on NTZ-related information related to the UE, that the UE cannot respond to the downlink message or that the UE cannot transmit an uplink message.

6. In paragraph 1, NTZ related information related to the above UE: i) Information related to the location of the UE in the NTZ; ii) Information related to transmission only possible to the above UE; iii) Information related to the impossibility of reception from the UE; iv) Information that the entire registration area of ​​the above UE is NTZ; and v) Information that part of the registration area of ​​the above UE is NTZ; A method comprising one or more of:

7. At least one transmitter / receiver; at least one processor; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein at least one processor is adapted to perform a method according to any one of claims 1 to 6.

8. At least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, An apparatus, wherein at least one processor is adapted to perform a method according to any one of claims 1 to 6.

9. 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 6. CRM.

10. A step of receiving a registration request message of User Equipment (UE) from a base station; a step of transmitting a registration acceptance message for the UE to the base station; and A method comprising the step of transmitting No Transmit Zone (NTZ) related information related to the UE to the base station.

11. In paragraph 10, NTZ related information related to the above UE: i) Information related to the location of the UE in the NTZ; ii) Information related to transmission only possible to the above UE; iii) Information related to the impossibility of reception from the UE; iv) Information that the entire registration area of ​​the above UE is NTZ; and v) Information that part of the registration area of ​​the above UE is NTZ; A method comprising one or more of:

12. In paragraph 10, A method further comprising the step of determining whether to transmit NTZ-related information related to the UE to the base station.

13. In paragraph 12, Whether to transmit NTZ related information related to the above UE to the above base station: a) If the subscriber information of the above UE includes aerial subscription information; b) If the subscriber information of the UE includes information related to the ability to provide NTZ-related information related to the UE to the base station; c) NTZ support information; d) If the UE is determined to be located in the NTZ; e) If the UE is determined to be located in an NTZ where transmission to the UE is permitted; f) If the UE is or is determined to be in a location where transmission by the UE is not permitted; g) If the UE is determined to be in a position where transmission by the UE is not permitted and transmission to the UE is permitted; h) If all or part of the registration area of ​​the above UE is NTZ; i) When the above UE's light path area and the above NTZ overlap; j) If the UE is an Unmanned Aerial Vehicle (UAV) and / or drone; k) local configuration of network entities related to mobility; and l) A method determined based on one or more of the business policies.

14. 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; A device wherein at least one processor is adapted to perform a method according to any one of claims 10 to 13.

Images