C2 communication-related method

Abstract

One disclosure of the present specification provides a method. The method comprises steps in which an unmanned aerial vehicle-related network node: receives an authentication request from an NEF; transmits a response to the authentication request to the NEF; receives a first C2 connectivity-related connectivity information request from a UAV, the connectivity information request including information about a specific flight route of the UAV; acquires C2 connectivity assistance information from the NEF on the basis of the connectivity information request, the C2 connectivity assistance information including reliability information about the first C2 connectivity; and transmits a response to the connectivity information request to the UAV on the basis of the C2 connectivity assistance information.

Description

C2 communication related methods

[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 in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

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

[0005] The reliability of C2 communication is ensured by providing information about the reliability of the C2 connection.

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

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

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

[0009] Figure 4 is a structural diagram of a next-generation mobile communications network.

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

[0011] Figures 6 and 7 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0012] Figure 8 illustrates an example of a UE-initiated PDU session establishment procedure for C2 communication.

[0013] Figures 9a and 9b illustrate examples of the UUAA procedure during PDU session establishment.

[0014] Figure 10 illustrates an example of a reliability support procedure for C2 communication according to the disclosure of this specification.

[0015] Figure 11 illustrates the procedure of a network node related to an unmanned aerial vehicle for the disclosure of this specification.

[0016] Figure 12 illustrates the procedure of the UAV for the disclosure of this 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 multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via 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 E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses 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." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[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] Wireless devices (100a to 100f) refer to devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) 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 functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0035] For example, a UAV may be an aircraft that is unmanned and navigated by radio control signals.

[0036] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in the real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in the real world. For example, a holographic device may include a device that implements 360-degree stereoscopic images by recording and reproducing three-dimensional information using the light interference phenomenon that occurs when two laser lights, called holograms, meet.

[0037] For example, a public safety device may include an image relay device or imaging device that can be worn on the user's body.

[0038] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. Examples include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0039] For example, a medical device may be a device used for the purpose of diagnosing, treating, mitigating, curing, or preventing a disease. For example, a medical device may be a device used for the purpose of diagnosing, treating, mitigating, or correcting an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, an (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0040] For example, a security device may be a device installed to prevent potential hazards and maintain safety. For example, a security device may be a camera, closed-circuit television (CCTV), recorder, or black box.

[0041] For example, a fintech device may be a device capable of providing financial services, such as mobile payments. For example, a fintech device may include a payment device or a point-of-sale system.

[0042] For example, a weather / environment device may include a device that monitors or predicts the weather / environment.

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

[0044] 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, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). 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.

[0045] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0046] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0047] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0048] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0049] NR supports multiple numerologies, or subcarrier spacing (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.

[0050] 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 NR systems, FR1 can mean the "sub-6GHz range," and FR2 can mean the "above 6GHz range," which can be referred to as millimeter wave (mmW).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0065] 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 instruction codes, commands 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.

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

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

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

[0069] 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. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0071] 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 specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

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

[0074] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present 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 the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present 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 the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

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

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

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

[0078] The UE (100) includes a processor (102), memory (104), 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).

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

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

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

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

[0083] The display (143) outputs the 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).

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

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

[0086] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0087] 5GC (5G Core) may include various components, and in FIG. 5, some of them include AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0088] The UE (100) is connected to a data network via UPF (440) through a Next Generation Radio Access Network (NG-RAN) including a gNB (20).

[0089] The UE (100) can also receive data services via untrusted non-3GPP access, such as a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0090] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G system. When UE (100) is connected to non-3GPP access (e.g., WiFi, referred to as IEEE 801.11), UE (100) can be connected to 5G system through N3IWF (490). N3IWF (490) performs control signaling with AMF (410) and is connected to UPF (440) through N3 interface for data transmission.

[0091] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

[0092] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communications.

[0093] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains a data path between the gNB (20) and the SMF (420). In addition, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform a function of handling PDUs. For mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), the UPF can route packets. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined before 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0094] The illustrated PCF (430) is a node that controls the business operator's policy.

[0095] The illustrated AF (450) is a server for providing various services to the UE (100).

[0096] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home Subscriber Server) of 4th generation mobile communications. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0097] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

[0098] For reference, the drawing symbols for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0099] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

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

[0102] - AUSF (Authentication Server Function)

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

[0104] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0105] - USDF (Unstructured Data Storage Function)

[0106] - NEF (Network Exposure Function)

[0107] - I-NEF (Intermediate NEF)

[0108] - NRF (Network Repository Function)

[0109] - NSSF (Network Slice Selection Function)

[0110] - PCF (Policy Control Function)

[0111] - SMF (Session Management Function)

[0112] - UDM (Unified Data Management)

[0113] - UDR (Unified Data Repository)

[0114] - UPF (User Plane Function)

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

[0116] - AF (Application Function)

[0117] - UE (User Equipment)

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

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

[0120] - NWDAF (Network Data Analytics Function)

[0121] - CHF (CHarging Function)

[0122] Additionally, the following network features may be considered:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] <PDU 세션 수립 절차>

[0150] Describes the PDU session establishment procedure. See Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0151] Figures 6 and 7 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0152] Establishing a PDU session may involve:

[0153] - UE-initiated PDU session establishment procedure

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

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

[0156] - Network-triggered PDU session establishment procedure

[0157] A PDU session may be associated with either (a) a single connection type at a given time, i.e., either a 3GPP connection or a non-3GPP connection, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) capable UE.

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

[0159] In the procedures shown in Figures 6 and 7, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0160] First, the procedure of Fig. 6 is explained.

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

[0162] The UE initiates the PDU session establishment procedure requested by the UE by sending an NAS message containing a PDU session establishment request message within the N1 SM container. The PDU session establishment request message includes the PDU session ID, the requested PDU session type, the requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), the SM PDU DN Request Container, and the UE Integrity Protection Maximum Data Rate.

[0163] If the PDU session establishment is a request to establish a new PDU session, the request type is "Initial Request." If the request refers to an existing PDU session switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing packet data network (PDN) connection in the EPC, the request type is "Existing PDU Session." If the PDU session establishment is a request to establish a PDU session for emergency services, the request type is "Emergency Request." If the request refers to an existing PDU session for emergency services switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type is "Existing Emergency PDU Session."

[0164] The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If a mapping of allowed NSSAIs (Mapping of Allowed NSSAIs) is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAIs and the corresponding S-NSSAI of the HPLMN from the mapping of allowed NSSAIs.

[0165] (2) Step 2: AMF selects an SMF. If the request type indicates "Initial Request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID.

[0166] If the request type is "Initial Request" and the message also contains a previous PDU Session ID representing an existing PDU Session, AMF selects an SMF and stores the association of the new PDU Session ID, S-NSAI(s), and the selected SMF ID.

[0167] If the request type indicates "Existing PDU Session," AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.

[0168] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

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

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

[0171] Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0172] AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session".

[0173] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0174] The AMF transmits the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also transmits the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.

[0175] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

[0176] If a UE in limited service state is registered for emergency services without providing SUPI, the AMF provides PEI instead of SUPI. If a UE in limited service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered unauthenticated.

[0177] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in non-roaming cases and the visited PCF (V-PCF) in LBO roaming cases.

[0178] (4) Step 4: If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, or HPLMN is not available, the SMF can retrieve the session management subscription data from the UDM and be notified when the subscription data is modified.

[0179] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

[0180] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0181] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

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

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

[0184] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

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

[0186] (9) Step 9: The SMF may provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by the SMF.

[0187] (10) Step 10: If the request type indicates an "Initial Request," the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF.

[0188] In step 10a, the SMF can send an N4 session establishment / modification request to the UPF, providing packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. In step 10b, the UPF can confirm by sending an N4 session establishment / modification response.

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

[0190] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

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

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

[0193] - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE;

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

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

[0196] - UE integrity protection maximum data rate received in PDU Session Establishment Request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0197] - RSN (redundancy sequence number) parameter

[0198] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0199] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

[0200] If the PDU session establishment fails between steps 5 and 11, the N1N2 message forwarding message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0201] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

[0202] (13) Step 13: The (R)AN may perform AN-specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of the NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0203] (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes (R)AN resource additions related to the received N2 command.

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

[0205] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described.

[0206] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

[0207] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

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

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

[0210] After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.

[0211] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF may register with the UDM for the given PDU session.

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

[0213] After this step, AMF forwards the relevant events to which SMF subscribes.

[0214] (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g., IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted.

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

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

[0217] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe from modifications to the session management subscription data if the SMF no longer processes the UE's PDU session.

[0218] <C2 Communication>

[0219] C2 communication is a user plane link that conveys messages containing command and control information for UAV operations from a UAV controller or Uncrewed Aerial System Traffic Management (UTM) to the UAV, or reports telemetry data from the UAV to its UAV controller or UTM.

[0220] When using a 3GPP network as a transport network to support UAS (Uncrewed Aerial System) services, the following C2 communications may be considered to provide UAS services by guaranteeing QoS for C2 communications.

[0221] Direct C2 Communication: The UAV controller and the UAV can establish a direct C2 link to communicate with each other and perform direct C2 communication using radio resources set up and reserved in the 5G network for direct C2 communication. The UAV controller and the UAV register with the 5G network.

[0222] Network-Assisted C2 Communication: The UAV controller and UAVs register and establish their own unicast C2 communication links to the 5G network and communicate with each other via the 5G network. Furthermore, the UAV controller and UAVs can register to the 5G network via different NG-RAN nodes. The 5G network must support mechanisms to handle reliable routing of C2 communications.

[0223] UTM-Navigated C2 Communication: A UAV may be provided with a pre-planned flight plan (e.g., a 4D polygonal array) for autonomous flight. However, the UTM can regularly monitor the UAV's flight status, check its flight status with the latest dynamic constraints, provide route updates, and maintain a C2 communication link with the UAV to navigate the UAV whenever necessary.

[0224] Typically, direct C2 and network-assisted C2 communications are used by human operators using UAV controllers. UTM-navigated C2 communications are used to provide authorized flight paths and route updates from the UTM. To ensure service availability and reliability of C2 communications for UAS operations, especially when the UAV flies beyond the operator's line of sight (BLOS), a redundant C2 communication link can be established between the UAV controller or UTM to the UAV.

[0225] Considering reliability and service availability, more than one C2 communication can be activated, including one backup link for C2 communication, or switching between applicable links for C2 communication is possible.

[0226] - For example, you can initially use Direct C2 communication and then switch to Network-Assisted C2 communication when the UAV flies BLOS.

[0227] For example, UTM navigation C2 communications can be utilized whenever necessary, such as for air traffic control, when a UAV approaches a drone-free zone, or when a potential security threat is detected.

[0228] There are four control modes considered for C2 communications for UAV operations with varying requirements (e.g., message spacing, size, and end-to-end latency). These control modes include waypoint control, direct stick control, autonomous flight by UTM, and access to autonomous navigation infrastructure.

[0229] - Waypoint-based control: Control messages include flight declarations. For example, waypoints transmitted from the UAV controller or UTM to the UAV. This control mode is used for both direct command-and-control (C2) and network-assisted command-and-control (NAC2) communications.

[0230] - Direct Stick Control: Control messages include directional instructions from the UAV controller to the UAV, and optionally video traffic is provided as feedback from the UAV to the UAV controller. This control mode is used for both Direct C2 and Network-Assisted C2 communications.

[0231] - UTM-driven autonomous flight: Control messages include a pre-planned flight plan. For example, using a 4D polygon array transmitted from the UTM to the UAV, the UAV then flies autonomously, with periodic position reports. This control mode is used in UTM-Navigated C2 communications.

[0232] - Approaching autonomous navigation infrastructure: Control messages include directional guidance, such as waypoints, altitude, and speed, from the UTM to the UAV. When the UAV lands or departs, the UTM collaborates more closely with the autonomous navigation infrastructure (e.g., a vertical takeoff and landing airfield or package distribution center). This control mode is used in UTM-Navigated C2 communications.

[0233] C2 communication via PC5 can be used to enable the aforementioned Direct C2 communication.

[0234] Describes V2X (vehicle-to-everything) communication. The following definitions can be used for V2X communication.

[0235] - V2X Application: An application that uses one or more V2X services (e.g., active safety applications for vehicles, emergency warnings, vehicle safety and awareness, etc.). A V2X application can operate toward a V2X application server.

[0236] - V2X communication: Communication to support V2X services by utilizing Uu and / or PC5 reference points. V2X services are implemented through various types of V2X applications, such as V2V (vehicle-to-vehicle), V2P (vehicle-to-pedestrian), V2I (vehicle-to-infrastructure), and V2N (vehicle-to-network).

[0237] - V2X message: A dedicated messaging type for V2X services (e.g. ITS (intelligent transport system) message).

[0238] - V2X Service: A data service provided to V2X applications and optionally V2X application servers. A V2X service belongs to a single V2X service type. A V2X service can be connected to one or more V2X applications, and a V2X application can be connected to one or more V2X services.

[0239] - V2X service type: V2X service type identified by ITS-AID (ITS application identifier), PSID (provider service identifier), or AID (Application Identifier).

[0240] V2X communication has two operating modes: V2X communication via the PC5 reference point and V2X communication via the Uu reference point. These two operating modes can be used independently by the UE for transmission and reception.

[0241] V2X communication via PC5 reference point is supported by LTE and / or NR.

[0242] V2X communication via Uu reference points is supported by E-UTRA connected to 5GC and / or NR connected to 5GC. V2X communication via Uu reference points can only be unicast.

[0243] <C2 통신을 위한 UE 시작 PDU 세션 수립(UE initiated PDU Session Establishment for C2 Communication)>

[0244] Figure 8 illustrates an example of a UE-initiated PDU session establishment procedure for C2 communication.

[0245] 0) step 0

[0246] The UAV has performed a successful UUAA with the USS (UUAA-SM or UUAA-MM) and the USS has subscribed to the PDU Session Status event in the NEF for that GPSI.

[0247] 1) Step 1

[0248] When a UAV needs to establish C2 communication, the UAV determines that a new dedicated PDU session is required to connect to UAV-C. The UE initiates a PDU session setup procedure for the dedicated DNN / S-NSSAI to connect to UAV-C. The PDU session setup request must include the CAA-level UAV ID and the C2 Aviation Payload to be used for C2 authorization and be passed to the SMF. The pairing information includes the CAA-level UAV ID of the requesting UAV and the identification information of the UAV-C to be paired may be included in the C2 Aviation Payload. The UAV may also include other information, such as flight authorization information. The USS may also use locally configured pairing information to authorize pairing between the UAV and UAV-C, which takes precedence over the pairing information provided by the UAV.

[0249] 2) Step 2

[0250] The SMF determines that authorization is required based on the fact that the request includes the requested DNN / S-NSSAI combination (Air Service Indicator setting) and the Service Level Device ID (CAA-level UAV ID) specifically for air services. The SMF then sends the Nnef_Authentication_AuthenticateAuthorize request to the UAS NF / NEF, which is used to request authorization to pair the UAV with the UAV-C. This request includes the GPSI, CAA-level UAV ID, and C2 airborne payload, and optionally, if provided by the AMF, the UAV location (e.g., cell ID), and the DNN and S-NSSAI of the PDU session.

[0251] If the requested DNN / S-NSSAI is dedicated to airborne services but no service-level device ID (CAA-level UAV ID) was provided with the request, the SMF will reject the PDU session setup, indicating the reason / reason that USS authentication is required.

[0252] The SMF also provides a notification endpoint to the UAS NF / NEF. By providing the notification endpoint, the SMF implicitly subscribes to receive notifications from the UAS NF / NEF regarding reauthentication, authentication data updates, or C2 connection cancellation if the C2 authentication result is successful in Step 5.

[0253] 3) Step 3

[0254] The UAS NF / NEF verifies that a valid UUAA is stored for the GPSI and forwards the received authentication request to the USS as a Naf_Authentication_AuthenticateAuthorize request. If not, the request is not forwarded to the USS and the PDU session is rejected.

[0255] The UAS NF / NEF also provides a notification endpoint to the USS. By providing a notification endpoint, the UAS NF / NEF is implicitly subscribed to receive notifications from the USS regarding reauthentication, updated authentication data, or C2 connection cancellation if the UUAA result is successful in step 5.

[0256] USS can trigger UAV re-authentication / re-certification in response to queries from UAS NF / NEF.

[0257] 4) Step 4

[0258] The USS performs C2 authentication based on the received information and sends a Naf_Authentication_AuthenticateAuthorize response to the UAS NF / NEF containing a service-level device ID (e.g., CAA-level UAV-ID) (potentially new), the C2 authentication result, and the C2 authentication payload (e.g., C2 pairing information and C2 security information).

[0259] 5) Step 5

[0260] UAS-NF / NEF includes the information received from USS in the Nnef_Authentication_AuthenticateAuthorize response and forwards it to SMF.

[0261] 6) Step 6

[0262] To inform the UE of the C2 authorization result, the SMF sends the PDU session acceptance to the UE along with the authorization result and optionally the new CAA level UAV ID if received from the USS, and continues the remaining procedures until the PDU session setup procedure is completed.

[0263] If the USS receives a failed C2 authorization result, the SMF instead rejects the PDU setup and includes a reason code indicating that it is not authorized.

[0264] 7) Step 7

[0265] [Conditional] If C2 authorization is successful, the USS subscribes to the PDU session status event for the PDU session used for C2 via the UAS-NF and includes the GPSI of the UAV in the request. The UAS NF determines the DNN and S-NSSAI corresponding to the PDU session used for C2 communication and subscribes to the PDU session status event to the SMF using this DNN and S-NSSAI. When the PDU session is established, the SMF detects it and sends a PDU session status event report to the UAS NF / NEF via an Nsmf_EventExposure_Notify message, including the GPSI and the UE IP address. The UAS NF / NEF then forwards the event message to the USS.

[0266] 8) Step 8

[0267] [Conditional] The USS stores the received UE IP address and calls the USS-initiated pairing policy configuration procedure with the received PDU session IP address and the IP address of the authorized paired UAV-C as input to request the UPF to allow the corresponding traffic in the PDU session.

[0268] This procedure does not invoke any interaction with the UE, AMF or RAN unless dedicated QoS for the C2 flow is requested.

[0269] <PDU 세션 수립 중 UUAA (USS UAV Authorization / Authentication)>

[0270] Figures 9a and 9b illustrate examples of the UUAA procedure during PDU session establishment.

[0271] The UUAA-SM (UUAA At PDN Connection / PDU Session Establishment) procedure can be performed as described below.

[0272] It is assumed that the UE / UAV is already registered with AMF.

[0273] 0) step 0

[0274] Steps 1 to 5 of TS 23.502 v18.4.0 FIG. 4.3.2.2.1-1 can be performed.

[0275] The UAV may include a service-level device ID (e.g., a CAA-level UAV ID for UVA) and the PDU session setup request may include an authentication server address (e.g., a USS address) and optionally authentication data (e.g., a UUAA airborne payload).

[0276] The SMF determines that it should invoke the UAS NF / NEF service operation for UUAA authentication / authorization of the PDU session setup request based on the fact that the provided DNN / S-NSSAI combination is dedicated to airborne services (Airborne Service Indicator set) and a service-level device ID (CAA-Level-UAV ID) is included in the request. If the provided APN / DNN is dedicated to airborne services but a service-level device ID (CAA-Level-UAV ID) is not provided, the SMF rejects the PDU session setup and steps 1-9 are not performed.

[0277] The SMF identifies the UAS NF / NEF through NF discovery procedure using local configuration or DNN / S-NSSAI and / or UE provided ID (e.g. USS address).

[0278] 1) Step 1

[0279] The SMF calls the Nnef_Authentication_AuthenticateAuthorize service operation with the service-level device ID (including the CAA-level UAV ID of the UAV), the DNN, the S-NSSAI, and if provided by the UE, the authentication server address (i.e., USS address), the UUAA airborne payload, GPSI, optionally the UAV location, PEI if available, and the UE IP address if available. The UAV location is the user location information (e.g., cell ID) provided by the AMF. The UAS NF / NEF selects the USS based on the service-level device ID (i.e., the CAA-level UAV ID of the UAV) or the authentication server address (i.e., USS address).

[0280] The SMF also provides a notification endpoint to the UAS NF / NEF, allowing the UAS NF / NEF to include this notification endpoint with updated UUAA parameters. By providing the notification endpoint, the SMF implicitly subscribes to the UAS NF / NEF to notify it of re-authentication of the UAV, updated authorization data, or revocation if the UUAA result is successful in Step 4.

[0281] 2) Step 2

[0282] From UAS NF / NEF to USS: The Naf_Authentication_AuthenticateAuthorize service operation forwards the authentication request information received from the SMF. The UAS NF can convert the cell ID received as part of the UAV location in the Nnef_Authentication_AuthenticateAuthorize request in step 1 into the corresponding geographic area, or can use location service procedures to obtain additional UE location information and include it in the Naf_Authentication_AuthenticateAuthorize message to the USS to support geo-caging functionality.

[0283] The UAS NF / NEF also provides a notification endpoint to the USS, which the USS can include with updated UUAA parameters. By providing a notification endpoint, the UAS NF / NEF implicitly subscribes to the USS to notify the UAV of re-authentication, updated authorization data, or revocation if the UUAA result is successful in step 4.

[0284] 3) Step 3

[0285] [Conditional] Multiple round-trip messages required depending on the authentication method used by the USS. This step may be performed if the Naf_Authentication_AuthenticateAuthorize response message from the USS in step 3a does not contain a UUAA result (success / failure). The Naf_Authentication_AuthenticateAuthorize response message from the USS must include GPSI and an authentication message based on the authentication method used, which is transparently conveyed to the UE via the NAS MM transport message. The authentication message in step 3e may include UUAA airborne payloads requested by the USS if not previously provided by the UE.

[0286] 4) Step 4

[0287] The USS can send a Naf_Authentication_AuthenticateAuthorize response to the UAS NF / NEF.

[0288] The USS sends a Naf_Authentication_AuthenticateAuthorize response to the UAS NF / NEF. This response includes the authentication / authorization result (success / failure) for the UAS NF, whether the UUAA can release UAS service-related network resources if re-authentication or re-authorization fails, optionally the authorized CAA-level UAV ID, the requested policy information, and the service-level device ID containing the UUAA authorization payload. The requested policy information from the USS may include the DN authorization profile index and / or the DN authorized session AMBR. The USS may include the new CAA-level UAV ID as the authorized CAA-level UAV ID.

[0289] The USS stores a mapping between the CAA-level UAV ID and an external identifier. The external identifier (GPSI) and / or UAV IP address can later be used by the USS to access various services exposed on the 3GPP network, such as location information retrieval, event configuration monitoring, and dedicated policy requests for C2.

[0290] 5) Step 5

[0291] The UAS NF / NEF confirms successful authentication / authorization of the PDU session. The UAS NF / NEF stores the UUAA result along with the GPSI. If received from the USS, the UAS NF / NEF forwards the authentication / authorization result, the authorized CAA-level UAV ID, and the service-level device ID containing the authorization data (i.e., the UUAA authorization payload) to the SMF.

[0292] 6) Step 6

[0293] [Conditional] If authentication / authorization is successful, the USS subscribes to PDU session status events. This step can be performed in parallel with Step 4. The UAS NF / NEF determines the DNN and S-NSSAI to subscribe to PDU session status event notifications.

[0294] 7) Step 7

[0295] The PDU session setup is complete. In step 7b of Figures 6 and 7, when the SMF receives the DN authorization profile index from the UAS NF / NEF, it sends the DN authorization profile index to the PCF to retrieve the PDU session-related policy information and PCC rules. When the SMF receives the DN authorization session AMBR from the UAS NF / NEF, it sends the DN authorization session AMBR within the session AMBR to the PCF to retrieve the authorization session AMBR.

[0296] The SMF transmits to the UAV the authentication / authorization result, the service-level device ID containing the authorized CAA-level UAV ID, and the authorization data (i.e., the UUAA authorization payload) if it received it from the UAS NF.

[0297] If the authentication / authorization result is a failure, SMF rejects the PDU session establishment with an appropriate cause value.

[0298] 8) Step 8

[0299] [Conditional] If the USS subscribes to the PDU Session Status event in step 6, the SMF detects when a PDU session is established and sends a PDU session establishment event report to the UAS NF / NEF via an Nsmf_EventExposure_Notify message, including the GPSI and UE IP address. The UAS-NF / NEF then forwards the event message to the USS.

[0300] If UUAA-SM fails during re-authentication and re-authorization and USS indicates that network resources can be released, SMF can trigger PDU session release for UAS service with appropriate cause value.

[0301] If UUAA-SM fails during re-authentication and the USS does not indicate that it can release network resources, the USS may initiate UUAA revocation.

[0302] If a C2 information reference is available from the USS during the initial PDU session setup procedure, the SMF can interact with the PCF to establish a predefined PCC rule profile for C2 communication.

[0303] When the PDU session is released, the SMF can unsubscribe the UAS NF / NEF, and then the UAS NF / NEF can clear the UUAA-SM context and update the USS.

[0304] The proposed method may consist of a combination of one or more of the actions / configurations / steps described herein.

[0305] In this specification, UE (User Equipment), terminal, and UAV are used interchangeably.

[0306] In this specification, an Uncrewed Aerial Vehicle-Controller (UAV-C) may or may not be considered a UE.

[0307] In this specification, UAS (Uncrewed Aerial System) NF and NEF are used interchangeably.

[0308] In this specification, USS (UAS Service Supplier) and UTM (Uncrewed Aerial System Traffic Management) are used interchangeably.

[0309] In this specification, the terms flight route and flight path are used interchangeably.

[0310] In this specification, C2 communication, C2 link, C2 connection, and C2 connectivity are used interchangeably.

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

[0312] This specification primarily describes the proposed content. For UAS-related operations and procedures, TS 23.256 v18.2.0 is primarily referenced.

[0313] In this specification, the PDU session establishment procedure may be applied to the contents of FIGS. 6 to 9 (FIGS. 9a and 9b).

[0314] In this specification, a method for improving NEF service for C2 communication stability can be proposed.

[0315] In this specification, it may be proposed whether and how to enhance NEF services to support service exposure and interaction between MNO and UTM functions to support C2 communication stability.

[0316] In this specification, a method for improving NEF service and supporting NEF for USS / UTM to ensure C2 communication stability can be proposed.

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

[0318] Figure 10 illustrates an example of a reliability support procedure for C2 communication according to the disclosure of this specification.

[0319] 1) Step 1

[0320] The UAV (or UAV-C, UE) can establish a PDU session for C2 communication as described in clause 5.2.3 of TS 23.256 v18.2.0 (or FIG. 9a, FIG. 9b).

[0321] 2) Step 2

[0322] Flight path setting can be performed between the UAV (or paired UAV-C) and the USS / UTM. As a result, the USS / UTM can obtain information about the UAV's (or UE's) flight path and flight start / end times.

[0323] The flight start time can be the present time or any point in the future.

[0324] 3) Step 3

[0325] A UAV (or a UE via a paired UAV-C (which may be a UAV's paired UAV-C making a request or a UAV indicating a request via a paired UAV-C)) may request C2 connection related information from the USS / UTM via a C2 connection related information request message. For example, a UAV (or a UAV-C, UE) may request C2 connection related information from the USS / UTM (e.g., a current UAV's C2 connection or a C2 connection to which it intends to connect in the future).

[0326] The request message may contain information about the C2 connection (e.g., the current UAV's C2 connection or a C2 connection to be connected in the future).

[0327] The request message may include an identifier of the UAV (or UE) (e.g. GPSI, CAA-level UAV ID).

[0328] The request message may include information about the UAV's (or UE's) flight path and flight start / end time, reporting mode (event-generated or periodic) and / or an alternative flight path request.

[0329] The above flight path may include information about the start location of the flight and the end location of the flight.

[0330] The starting point and arrival point of the alternative flight path may be the same as the starting point and arrival point of the above flight path.

[0331] The flight path of the above UAV (or UE) may mean the path that the UAV (or UE) flies from the flight start time to the flight end time.

[0332] If the request message does not include a flight start time, the time at which the request message is transmitted (or the time at which the request is made) may be considered the flight start time.

[0333] The request message may include information that the UAV (or UAV-C, UE) does not have another C2 link (or cannot form another C2 link) instead of (or in addition to) the alternative flight path request.

[0334] The request message may also include candidate flight route(s) instead of (or in addition to) the alternative flight route request.

[0335] The terminal may include information regarding the reporting mode in the request message. The report may be a report regarding connection information related to the first C2 connection provided by the network to the terminal. The information regarding the reporting mode may include information regarding the format in which the report should be performed. Based on the information regarding the reporting mode (e.g., information indicating that the terminal desires to receive a report from the network when a specific event occurs, information indicating that the terminal desires to receive a report from the network at a specific interval), the network may transmit a report to the terminal.

[0336] If the reporting mode is not provided via the request message, the USS / UTM or NEF may internally determine the reporting mode (event-generated or periodic) based on settings, etc.

[0337] When the reporting mode is triggered by a specific event, the terminal can receive a report from the network when a specific event occurs.

[0338] For example, a particular event may be that the reliability of C2 communication (e.g., C2 connection requested by UAV) for a flight path (e.g., flight path included by UAV / UE in request message) cannot be provided / supported / sustained.

[0339] For example, a reporting mode may be set so that the network sends a report to the terminal when a specific event (e.g., when the reliability of C2 communication (e.g., the C2 connection requested by the UAV) for a flight path (e.g., the flight path included by the UAV / UE in the request message) cannot be provided / supported / maintained) occurs. In this case, when the specific event (e.g., when the reliability of C2 communication (e.g., the C2 connection requested by the UAV) for a flight path (e.g., the flight path included by the UAV / UE in the request message) cannot be provided / supported / maintained) occurs, the UAS NF may provide a report / notification to the USS / UTM. Then, the USS / UTM may provide a report / notification to the UAV (or UAV-C).

[0340] If the reporting mode is periodic, reporting cycle information may be provided with the request message. If reporting cycle information is not provided, it may be determined by the USS / UTM or NEF.

[0341] The above request message (request for C2 connection related information) can be transmitted via an application layer message transmitted by the UAV (or UAV-C) to the USS / UTM.

[0342] Alternatively, the above request message (request for C2 connection related information) may be transmitted to the USS / UTM via the user plane.

[0343] Alternatively, the above request message (request for C2 connection related information) may be sent to the USS / UTM during the Authorization for C2 over Uu procedure.

[0344] When the request message (request for C2 connection related information) is transmitted during the C2 authentication (Authorization for C2 over Uu) procedure (e.g., when the request message is transmitted in the UUAA-SM procedure of FIGS. 9a and 9b), the UAV (or UE) may provide the request message (request for C2 connection related information) to the USS / UTM through step 0 of FIG. 9a. For example, the request message (request for C2 connection related information) may be included in the 'C2 Aviation Payload' of the PDU Session Establishment Request message.

[0345] A request for C2 connectivity related information may also be referred to as a C2 connectivity assistance request, a C2 communication reliability request, etc.

[0346] 4) Step 4

[0347] The USS / UTM may decide to derive information regarding the C2 connection request and request supporting information from the NEF.

[0348] USS / UTM can derive a candidate flight path if an alternative flight path is requested in step 3. The starting location of the candidate flight path may be identical to the starting location of the UAV's flight path. The arrival location of the candidate flight path may be identical to the arrival location of the UAV's flight path.

[0349] Based on the information received from the UAV (or UE) (e.g., the flight path of the UAV), the USS / UTM can determine a candidate flight path for the UAV (or UE).

[0350] Based on a request from the UAV (or UE), the USS / UTM may decide to request assistance information from the NEF.

[0351] Even if the request message in step 3 does not include an alternative flight path request, the USS / UTM can still determine a candidate flight path. Furthermore, the USS / UTM can request (or decide to request) assistance information for the determined candidate flight path from the NEF.

[0352] Alternatively, the NEF may decide to provide support information for a candidate flight path to the USS / UTM. For example, even if the USS / UTM does not request support information for a candidate flight path from the NEF (and even if the USS / UTM does not decide to request support information for a candidate flight path from the NEF), the NEF may determine a candidate flight path and transmit support information for it to the USS / UTM.

[0353] 5) Step 5

[0354] The USS / UTM can send a C2 connection assistance request to the NEF (a request for assistance information for a C2 connection requested from a UAV).

[0355] The above C2 connection support request may include the UAV identifier (e.g. GPSI), the flight path and flight start / end time information of the UAV (or paired UAV-C) (or UE) (information acquired by the USS / UTM in step 2 or step 3), and / or the reporting mode (event triggered or periodic).

[0356] If the request message of step 3 includes an alternative flight path request, the C2 connection support request may include information about a candidate flight path (e.g., a first candidate flight path). Alternatively, even if the request message of step 3 does not include an alternative flight path request, the C2 connection support request may include information about a candidate flight path (e.g., a first candidate flight path).

[0357] The above C2 connection support request may include a request for support information for a candidate flight path (e.g., a first candidate flight path).

[0358] The above C2 connection assistance request may include information that an alternate flight path is required.

[0359] Even if the UAV (or paired UAV-C) (or UE) does not request C2 connection related information from the USS / UTM in step 3, the USS / UTM may request C2 connection assistance information from the NEF based on the results of step 2 or internal decisions.

[0360] 6) Step 6

[0361] NEF can map parameters (or information) included in a USS / UTM request to information used in the 3GPP system (e.g. mapping a geographical area to an area of ​​interest expressed as a Cell ID, gNB ID, or TAI list).

[0362] NEF can determine the services required for a request (e.g. NWDAF analytics services (QoS sustainability analysis, network performance analysis)).

[0363] Additionally, the NEF can determine parameters (e.g., QoS requirements, S-NSSAI related to C2 communication) used to request the corresponding service (e.g., NWDAF analysis service (QoS sustainability analysis, network performance analysis)). Using the determined parameters, the NEF can request the service required for the request (e.g., NWDAF analysis service (QoS sustainability analysis, network performance analysis)) (step 9). For example, the NEF can send an analysis (e.g., QoS sustainability analysis, network performance analysis) request message including the determined parameters to the NWDAF (step 9).

[0364] NEF may decide to subscribe to QoS Sustainability Analytics and Network Performance Analytics.

[0365] Additionally, NEF may decide to subscribe to various analytics defined in TS 23.288 v18.4.0.

[0366] Additionally, the NEF may decide to perform procedures to provide C2 connection support information to the USS / UTM. For example, the NEF may decide to perform procedures such as determining the flight path of the UAV (or UE), determining the position of the UAV (or UE) along the candidate flight path (e.g., using Section 5.3 "UAV Tracking" of TS 23.256 v18.2.0), etc.

[0367] 7) Step 7

[0368] NEF may provide a response to the USS / UTM for the above C2 connection support request.

[0369] If the NEF cannot provide the C2 connection support information (support information requested for a C2 connection) to the USS / UTM, the NEF may respond to the USS / UTM with a rejection of the C2 connection support request. If possible, the NEF may include a detailed reason for the rejection in the response.

[0370] 8) Step 8

[0371] The USS / UTM can provide a response to step 3 to the UAV (or paired UAV-C) (or UE).

[0372] If the USS / UTM receives a rejection response from the NEF in step 7, the USS / UTM may provide a response to the UAV (or paired UAV-C) (or UE) rejecting the request for C2 connection-related information. The response may include a detailed reason, if available.

[0373] 9) Step 9

[0374] NEF may request analytics to provide C2 connection support information. Based on the services determined by NEF in step 6, NEF may request analytics from NWDAF.

[0375] NEF can subscribe to notifications for QoS sustainability analysis and network performance analysis provided by NWDAF as defined in TS 23.288 v18.4.0.

[0376] For example, NEF may request analysis from MWDAF to provide C2 connection support information.

[0377] If NEF subscribes to notifications regarding QoS sustainability analysis and network performance analysis provided by NWDAF as defined in TS 23.288 v18.4.0, NEF may provide NWDAF with parameters necessary for such analysis. For example, NEF may provide NWDAF with location information (or Area of ​​Interest (AoI)) corresponding to the UAV's flight path and location information (or AoI) corresponding to the candidate flight path.

[0378] Based on NEF's subscriptions / requests, NEF may receive analytics from NWDAF.

[0379] 10) Step 10

[0380] NEF can generate (or determine) C2 connection support information based on the analysis received through step 9.

[0381] NEF can obtain relevant information through the service determined in step 6 and the subscription / request based on that service in step 9. Based on the information obtained, NEF can determine the C2 connection support information to be transmitted to the USS / UTM.

[0382] C2 connection support information may include one or more of the following information:

[0383] - Information that the reliability (or connection, a state satisfying a certain QoS) of C2 communication (e.g., C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) cannot be maintained during the flight path of the UAV (or paired UAV-C) (or UE) (C2 communication reliability cannot be sustained)

[0384] - If the C2 connection support request in step 5 includes information about a candidate flight path (e.g., the first candidate flight path) (or if there is a request for an alternative flight path in step 3), information that the reliability (or connection, a state satisfying a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) on the candidate flight path (e.g., the first candidate flight path) cannot be maintained.

[0385] - Information that the reliability (or connection, a state satisfying a certain QoS) of C2 communication (e.g., C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) can be maintained during the flight path of the UAV (or paired UAV-C) (or UE) (C2 communication reliability can be sustained)

[0386] - If the C2 connection support request in step 5 includes information about a candidate flight path (or information that an alternative flight path is required) (or if there is a request for an alternative flight path in step 3), information about a candidate flight path (e.g., the first candidate flight path requested by the NEF or the flight path determined by the NWDAF) on which the reliability (or connection, satisfying a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) can be maintained.

[0387] - If the C2 connection support request of step 5 includes information about a candidate flight path (e.g., the first candidate flight path), information that the reliability (or connection, a state satisfying a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) on the candidate flight path (e.g., the first candidate flight path) can be maintained.

[0388] - Information that the reliability of C2 communication (e.g., C2 connection requested by the UAV) for a UAV (or paired UAV-C) (or UE) can be maintained (or connection, state satisfying a certain QoS) in a plurality of candidate flight paths (e.g., first candidate flight path, second candidate flight path, etc.) (e.g., when the reliability of C2 communication of a plurality of candidate flight paths can be provided / supported / continued), one of the plurality of candidate flight paths and / or the reliability of C2 communication (e.g., C2 connection requested by the UAV) in the one flight path can be maintained

[0389] - In a case where the reliability (or connection, satisfying a certain QoS) of C2 communication (e.g., C2 connection requested by the UAV) for the UAV (or paired UAV-C) (or UE) can be maintained in a plurality of candidate flight paths (e.g., first candidate flight path, second candidate flight path, etc.) (e.g., in a case where the reliability of C2 communication (e.g., C2 connection requested by the UAV) of the plurality of candidate flight paths can be provided / supported / continued), information about the plurality of candidate flights and / or information that the reliability of C2 communication (e.g., C2 connection requested by the UAV) of the plurality of candidate flight paths can be maintained

[0390] Information that the reliability (or connection, a state that satisfies a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) cannot be maintained on a specific flight path (the flight path of the UAV or a candidate flight path) may be expressed as information that the quality / reliability of the C2 communication on the specific flight path cannot be guaranteed.

[0391] Information that the reliability (or connection, satisfying a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) on a specific flight path (the flight path of the UAV or a candidate flight path) cannot be maintained can be expressed as information that a change in the C2 link is required.

[0392] Information that the reliability (or connection, a state that satisfies a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) can be maintained on a specific flight path (the flight path of the UAV or a candidate flight path) can be expressed as information that the quality / reliability of the C2 communication on the specific flight path can be guaranteed.

[0393] Information that the reliability (or connection, satisfying a certain QoS) of the C2 communication (e.g., the C2 connection requested by the UAV) on a specific flight path (the flight path of the UAV or a candidate flight path) can be maintained can be expressed as information that no change of the C2 link is required.

[0394] 11) Step 11

[0395] NEF may provide a response to the USS / UTM for the above C2 connection support request.

[0396] NEF can provide USS / UTM with C2 connection support information determined / generated in step 10.

[0397] 12) Step 12

[0398] The USS / UTM can provide a response to step 3 to the UAV (or paired UAV-C) (or UE).

[0399] USS / UTM can determine C2 connection related information.

[0400] The above response may include information related to the C2 connection determined above.

[0401] The above C2 connection related information may include one or more of the following information:

[0402] - Information that the C2 connection persists during the flight path of the UAV (or paired UAV-C) (or UE).

[0403] - Information that the C2 connection cannot be sustained on the flight path of the UAV (or paired UAV-C) (or UE).

[0404] - Information that QoS is continuously satisfied with a certain QoS during the flight path of the UAV (or paired UAV-C) (or UE).

[0405] - Information that QoS cannot be continuously satisfied during the flight path of the UAV (or paired UAV-C) (or UE).

[0406] - Information that the C2 connection of the UAV (or paired UAV-C) (or UE) will be maintained when the UAV (or paired UAV-C) (or UE) flies along a candidate flight path provided (or determined) by the USS / UTM (or NEF).

[0407] - Information that the QoS of the C2 connection of the UAV (or paired UAV-C) (or UE) continuously satisfies a certain QoS when the UAV (or paired UAV-C) (or UE) flies along a candidate flight path provided (or determined) by the USS / UTM (or NEF).

[0408] - Information that the C2 connection requested by the UAV (or paired UAV-C) (or UE) through a request for C2 connection-related information to the USS / UTM (or NEF) needs to be changed.

[0409] - Information about one or more candidate flight paths (candidate flight paths on which QoS can be sustained).

[0410] - One or more of the information included in the C2 connection support information described in step 10.

[0411] If information on multiple candidate flight paths for which reliability of C2 communication can be maintained is received through Step 11 (if information on multiple candidate flight paths for which reliability of C2 communication can be maintained is included in the C2 connection support information of Step 10), the USS / UTM can determine one flight path from among the information on the multiple candidate flight paths. The USS / UTM can provide information on the determined one flight path to the UAV (or paired UAV-C) (or UE).

[0412] Alternatively, information about all of the above multiple candidate flight paths may be provided to the UAV (or paired UAV-C) (or UE). Then, the UAV (or paired UAV-C) (or UE) can determine one of them as a flight path.

[0413] The USS / UTM can transmit C2 connection-related information to the UAV (or UAV-C) using application layer messages. Alternatively, the USS / UTM can transmit C2 connection-related information to the UAV (or UAV-C) via the user plane.

[0414] Alternatively, the USS / UTM may transmit C2 connection-related information to the UAV (or UAV-C) via 5GC. For example, if the request for C2 connection-related information in step 3 is performed as part of the Authorization for C2 over Uu procedure, the USS / UTM may transmit C2 connection-related information to the UAV (or UAV-C) via 5GC. This is not limited to only this case.

[0415] When the USS / UTM transmits C2 connection related information to the UAV (or UAV-C) via 5GC, the 5GC may use various NAS related procedures (e.g., PDU Session Modification procedure).

[0416] Based on the C2 connection information, the UAV (or paired UAV-C) (or UE) can determine one or more of the following:

[0417] - Whether to use the flight path included in the request message in step 3

[0418] - Whether to maintain the current C2 connection

[0419] - Whether to change the current C2 connection to another C2 connection (e.g., C2 link via EPS, direct C2 link via PC5 reference point)

[0420] - In step 11, if a candidate flight path is received where the reliability of C2 communication can be maintained, whether to use the candidate flight path.

[0421] For example, based on the C2 connection related information, the UAV (or paired UAV-C) (or UE) may decide i) to maintain the current C2 connection and ii) to fly on the candidate flight path received in step 11.

[0422] For example, based on C2 connection related information, the UAV (or paired UAV-C) (or UE) may decide to change the current C2 connection to another C2 connection.

[0423] For example, changing to (using) a different C2 connection may mean switching (or converting) a standby C2 connection to an active C2 connection.

[0424] If the UAV (or paired UAV-C) (or UE) changes the current C2 connection to another C2 connection, the UAV (or paired UAV-C) (or UE) can perform the procedure of step 3 for the changed C2 connection. Based on this, the procedure after step 3 can be performed.

[0425] USS / UTM can be used to represent the enhanced NEF service consumer of Figure 10. The consumer can also be another entity (e.g., a Third Party Authorized Entity (TPAE)).

[0426] The above-described procedures may be performed as the UAV initiates flight or as the flight is planned.

[0427] UAS NF / NEF can provide C2 link support services.

[0428] The USS / UTM can provide C2 connection related information to the UAV (or paired UAV-C) (or UE).

[0429] By providing the USS / UTM with C2 connection-related information (e.g., whether C2 communication is reliable / sustainable) to the UAV (or paired UAV-C) (or UE), C2 communication between the UAV and UAV-C can be performed reliably.

[0430] The following actions can be performed:

[0431] - The USS / UTM may request C2 connection support from the NEF. This request may be based on a request from a UAV (or UAV-C). This request may be regarding the UAV's flight path.

[0432] - NEF can subscribe to various analytics (e.g., QoS Sustainability Analytics, Network Performance Analytics) with NWDAF to process C2 connection support requests from USS / UTM.

[0433] - The NEF may provide C2 link support information to the USS / UTM based on analysis received from the NWDAF. For example, C2 link support information may indicate that C2 communications (e.g., a C2 link requested by a UAV) for the flight path cannot be reliably provided / supported / sustained.

[0434] - USS / UTM can provide C2 connection related information to UAV (or UAV-C) based on C2 connection support information provided from NEF.

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

[0436] Figure 11 illustrates the procedure of a network node related to an unmanned aerial vehicle for the disclosure of this specification.

[0437] 1. Unmanned aerial vehicle-related network nodes can receive authentication requests from the Network Exposure Function (NEF).

[0438] 2. The above unmanned aerial vehicle-related network node can transmit a response to the above authentication request to the above NEF.

[0439] 3. The above unmanned aerial vehicle-related network node can receive a connection information request related to the first C2 connection from an uncrewed aerial vehicle (UAV).

[0440] The above connection information request may include information about a specific flight path of the UAV.

[0441] 4. Based on the above connection information request, the unmanned aerial vehicle-related network node can obtain C2 connection support information from the NEF.

[0442] The above C2 connection support information may include reliability information for the first C2 connection.

[0443] 5. Based on the above C2 connection support information, the unmanned aerial vehicle-related network node can transmit a response to the connection information request to the UAV.

[0444] The above C2 connection support information may include information on whether the first C2 connection can be maintained on the specific flight path.

[0445] The above C2 connection support information may include information that the first C2 connection can be maintained on the specific flight path.

[0446] The response to the above connection information request may include information that the first C2 connection can be maintained on the particular flight path.

[0447] The above C2 connection support information may include a first candidate flight path.

[0448] The reliability of the first C2 connection can be maintained in the first candidate flight path.

[0449] The response to the above connection information request may include information about the first candidate flight path.

[0450] The above C2 connection support information may include a first candidate flight path and a second candidate flight path.

[0451] The reliability of the first C2 connection can be maintained in the first candidate flight path.

[0452] The reliability of the first C2 connection can be maintained in the second candidate flight path.

[0453] The above unmanned aerial vehicle-related network node can determine one of the first candidate flight path and the second candidate flight path.

[0454] The response to the above connection information request may include information about one of the determined paths.

[0455] The response to the above connection information request may include the first candidate flight path and the second candidate flight path.

[0456] The start and end locations of the above specific flight path may be the same as the start and end locations of the first candidate flight path.

[0457] The start and end locations of the above specific flight path may be the same as the start and end locations of the second candidate flight path.

[0458] The above connection information request may include a request for an alternative flight path.

[0459] Based on the request for the alternative flight path, the unmanned aerial vehicle-related network node can determine a first candidate flight path for the UAV.

[0460] The step of obtaining the C2 connection support information may include: the step of the unmanned aerial vehicle-related network node transmitting a first request to the NEF; and the step of the unmanned aerial vehicle-related network node receiving the C2 connection support information from the NEF.

[0461] The above first request may include the above determined first candidate flight path.

[0462] The above C2 connection support information may include information on whether the first C2 connection can be maintained on the determined first candidate flight path.

[0463] The response to the connection information request may include information that the UAV should change the first C2 connection to another C2 connection.

[0464] The above unmanned aerial vehicle-related network node may be a USS (UAS Service Supplier) or UTM (Uncrewed Aerial System Traffic Management).

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

[0466] Figure 12 illustrates the procedure of the UAV for the disclosure of this specification.

[0467] 1. Uncrewed Aerial Vehicle (UAV) can establish PDU sessions.

[0468] 2. The above UAV can transmit a connection information request related to the first C2 connection to an unmanned aerial vehicle-related network node.

[0469] The above connection information request may include information about a specific flight path of the UAV.

[0470] 3. The UAV can receive a response to the connection information request from an unmanned aerial vehicle-related network node.

[0471] The response to the above connection information request may include reliability information for the first C2 connection.

[0472] The response to the connection information request may include information on whether the first C2 connection can be maintained on the particular flight path.

[0473] The above connection information request may include a request for an alternative flight path.

[0474] Based on the request for the alternative flight path, the response to the connection information request may include information about the first candidate flight path.

[0475] The reliability of the first C2 connection can be maintained in the first candidate flight path.

[0476] The response to the connection information request may include information that the UAV should change the first C2 connection to a second C2 connection.

[0477] Based on the response to the connection information request, the UAV can change the first C2 connection to the second C2 connection.

[0478] The UAV may transmit a connection information request related to the second C2 connection to the unmanned aerial vehicle-related network node.

[0479] The above unmanned aerial vehicle-related network node may be a USS (UAS Service Supplier) or UTM (Uncrewed Aerial System Traffic Management).

[0480] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0481] For example, a device may include a processor, a transceiver, and memory.

[0482] For example, a processor may be configured to be operatively coupled with memory and a processor.

[0483] The operations performed by the processor may include: a step of the unmanned aerial vehicle-related network node receiving an authentication request from a NEF; a step of the unmanned aerial vehicle-related network node transmitting a response to the authentication request to the NEF; a step of the unmanned aerial vehicle-related network node receiving a connection information request related to a first C2 connection from a UAV; the connection information request including information on a specific flight path of the UAV, and based on the connection information request, the unmanned aerial vehicle-related network node obtaining C2 connection support information from the NEF; and a step of the C2 connection support information including reliability information on the first C2 connection, and based on the C2 connection support information, the unmanned aerial vehicle-related network node transmitting a response to the connection information request to the UAV.

[0484] Below, a processor of a device for providing communication according to some embodiments of the present specification is described.

[0485] The operations performed by the processor may include: a step in which a UAV-related network node receives an authentication request from a NEF; a step in which the UAV-related network node transmits a response to the authentication request to the NEF; a step in which the UAV-related network node receives a connection information request related to a first C2 connection from a UAV; the connection information request includes information on a specific flight path of the UAV, and based on the connection information request, the UAV-related network node obtains C2 connection support information from the NEF; and a step in which the C2 connection support information includes reliability information on the first C2 connection, and based on the C2 connection support information, the UAV-related network node transmits a response to the connection information request to the UAV.

[0486] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

[0487] According to some embodiments of the present disclosure, the technical features of the present disclosure may be implemented directly in hardware, software executed by a processor, or a combination of the two. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, the software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0488] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

[0489] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0490] For example, nonvolatile computer-readable media may include random access memory (RAM), such as synchronized dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media may also include combinations of the above.

[0491] Additionally, the methods described herein can be realized at least in part by a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0492] According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more stored instructions can be executed by a processor of a base station.

[0493] The one or more stored instructions may include: a step for a UAV-related network node to receive an authentication request from a NEF; a step for the UAV-related network node to transmit a response to the authentication request to the NEF; a step for the UAV-related network node to receive a connection information request related to a first C2 connection from a UAV; the connection information request including information on a specific flight path of the UAV, and based on the connection information request, the UAV-related network node to obtain C2 connection support information from the NEF; and a step for the C2 connection support information to include reliability information on the first C2 connection, and based on the C2 connection support information, the UAV-related network node to transmit a response to the connection information request to the UAV.

[0494] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

[0495] This specification may have various effects.

[0496] For example, through the procedures disclosed in this specification, the reliability of C2 communication can be ensured.

[0497] The effects that can be achieved through 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.

[0498] 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. As a method, A step in which an unmanned aerial vehicle-related network node receives an authentication request from a Network Exposure Function (NEF); A step in which the above unmanned aerial vehicle-related network node transmits a response to the authentication request to the NEF; A step in which the above unmanned aerial vehicle-related network node receives a connection information request related to a first C2 connection from an Uncrewed Aerial Vehicle (UAV); The above connection information request includes information about a specific flight path of the UAV, A step of the unmanned aerial vehicle-related network node obtaining C2 connection support information from the NEF based on the connection information request; The above C2 connection support information includes reliability information for the first C2 connection, A method comprising a step of the unmanned aerial vehicle-related network node transmitting a response to the connection information request to the UAV based on the C2 connection support information.

2. In paragraph 1, A method wherein the C2 connection support information includes information on whether the first C2 connection can be maintained on the specific flight path.

3. In paragraph 2, The above C2 connection support information includes information that the first C2 connection can be maintained on the specific flight path, A method wherein a response to the connection information request includes information that the first C2 connection can be maintained on the specific flight path.

4. In paragraph 1 or 2, The above C2 connection support information includes the first candidate flight path, The reliability of the first C2 connection can be maintained in the first candidate flight path, A method wherein a response to the connection information request includes information about the first candidate flight path.

5. In paragraph 1 or 2, The above C2 connection support information includes a first candidate flight path and a second candidate flight path, The reliability of the first C2 connection can be maintained in the first candidate flight path, A method in which the reliability of the first C2 connection can be maintained in the second candidate flight path.

6. In paragraph 5, The above unmanned aerial vehicle-related network node further includes a step of determining one of the first candidate flight path and the second candidate flight path, A method in which a response to the above connection information request includes information about the determined one path.

7. In paragraph 5, A method wherein a response to the connection information request includes the first candidate flight path and the second candidate flight path.

8. In any one of the clauses 4 to 7, The starting and ending positions of the above specific flight path are the same as the starting and ending positions of the first candidate flight path.

9. In any one of paragraphs 5 to 7, The starting and ending positions of the above specific flight path are the same as the starting and ending positions of the second candidate flight path.

10. In any one of paragraphs 1 to 9, The above connection information request includes a request for an alternative flight path, Based on the request for the alternative flight path, the unmanned aerial vehicle-related network node further comprises a step of determining a first candidate flight path for the UAV; The steps for obtaining the above C2 connection support information are: The step of the above unmanned aerial vehicle-related network node transmitting a first request to the NEF; and The step of the above unmanned aerial vehicle-related network node receiving the C2 connection support information from the NEF, The above first request includes the above determined first candidate flight path, A method wherein the C2 connection support information includes information on whether the first C2 connection can be maintained on the determined first candidate flight path.

11. In any one of paragraphs 1 to 10, A method wherein a response to the connection information request includes information that the UAV should change the first C2 connection to another C2 connection.

12. In any one of paragraphs 1 to 11, The above unmanned aerial vehicle-related network node is a method of USS (UAS Service Supplier) or UTM (Uncrewed Aerial System Traffic Management).

13. As a method, Steps for an Uncrewed Aerial Vehicle (UAV) to establish a PDU session; A step in which the UAV transmits a connection information request related to a first C2 connection to an unmanned aerial vehicle-related network node; The above connection information request includes information about a specific flight path of the UAV, The step of the UAV receiving a response to the connection information request from an unmanned aerial vehicle-related network node, A method wherein a response to the connection information request includes reliability information for the first C2 connection.

14. In paragraph 13, A method wherein a response to the connection information request includes information on whether the first C2 connection can be maintained on the specific flight path.

15. In paragraph 13, The above connection information request includes a request for an alternative flight path, Based on the request for the alternative flight path, the response to the connection information request includes information about the first candidate flight path, A method in which the reliability of the first C2 connection can be maintained in the first candidate flight path.

16. In paragraph 13, The response to the connection information request includes information that the UAV should change the first C2 connection to a second C2 connection, A step of the UAV changing the first C2 connection to the second C2 connection based on a response to the connection information request; and A method further comprising the step of the UAV transmitting a connection information request related to the second C2 connection to the unmanned aerial vehicle-related network node.

17. In any one of the clauses 13 to 16, The above unmanned aerial vehicle-related network node is a method of USS (UAS Service Supplier) or UTM (Uncrewed Aerial System Traffic Management).

18. As a network node related to unmanned aerial vehicles that performs communication, At least one transmitter and receiver; Contains at least one processor, An unmanned aerial vehicle-related network node, wherein the operation performed by at least one processor is a method according to any one of claims 1 to 12.

19. As an uncrewed aerial vehicle (UAV) that performs communication, At least one transmitter and receiver; Contains at least one processor, A UAV in which the operation performed by at least one processor is a method according to any one of claims 1 to 7.

20. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, A device wherein the operation performed based on the command being executed by the at least one processor is a method according to any one of claims 1 to 12.

21. A non-volatile computer-readable storage medium that records commands, A non-volatile computer-readable storage medium, wherein the instructions, when executed by one or more processors, cause the one or more processors to perform an operation according to any one of claims 1 to 12.

Images