Method and apparatus for updating flight path in next generation mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the invention provides a method and equipment for updating a flight path. According to an embodiment of the present disclosure, a method performed by a terminal comprises the steps of: transmitting a User Assistance Information (UAI) message to a base station, the UAI message including information indicating the presence of flight path information; receiving a first message for requesting flight path information from the base station; and transmitting a second message for reporting the flight path information to the base station.

Description

Technical Field

[0001] The present disclosure relates to the field of communications and to the operation of terminals and base stations. Specifically, the present disclosure relates to a method for updating a flight path and a terminal, a base station, and a communication system related thereto. Background Art

[0002] 5G mobile communication technology defines a wide frequency band to achieve high transmission rates and new services, and can be implemented not only in the "sub-6 GHz" frequency band such as 3.5 GHz, but also in the ultra-high frequency ("above 6 GHz") frequency band called millimeter waves (such as 28 GHz and 39 GHz). In addition, it has been considered to implement 6G mobile communication technology (referred to as a super 5G system) in the terahertz frequency band (for example, 95 GHz to 3 THz frequency band) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet the performance requirements regarding enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been carried out on the following technologies: beamforming and massive multiple-input multiple-output (MIMO) for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves; support parameters for dynamic operation for efficient use of millimeter wave resources and time slot formats (for example, operating multiple subcarrier spacings); initial access technology for supporting multi-beam transmission and wide frequency bands; definition and operation of bandwidth parts (BWPs); new channel coding methods such as low-density parity-check (LDPC) codes for large data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing a dedicated network dedicated to a specific service.

[0004] Currently, regarding the services supported by 5G mobile communication technology, the industry is continuously discussing improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization has been completed on the following technologies, for example: vehicle-to-everything (V2X) for assisting driving decisions based on information about the position and status of a vehicle sent by the vehicle and for improving user convenience, new radio unlicensed (NR-U) aiming for system operation to comply with various regulatory requirements in unlicensed frequency bands, NR UE energy saving, non-terrestrial networks (NTN) as UE satellite direct communication for ensuring coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, the standardization of air interface architectures / protocols for the following technologies has been continuously progressing, such as: Industrial Internet of Things (IIoT) for supporting new services through interoperability and integration with other industries; IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access (two-step RACH for NR) for simplifying the random access process. At the same time, the standardization of system architectures / services for the following technologies is also continuously progressing: 5G baseline architectures that combine network function virtualization (NFV) and software-defined network (SDN) technologies (e.g., service-based architectures or service-based interfaces); and mobile edge computing (MEC) for receiving services based on UE location.

[0006] If such a 5G mobile communication system is commercialized, exponentially growing connected devices will access the communication network, and thus enhanced functions and performance of the 5G mobile communication system and integrated operation of connected devices are expected to be necessary. For this purpose, new research on the following technologies has been put on the agenda: extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvement and complexity reduction by leveraging artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] In addition, such development of the 5G mobile communication system will not only lay the foundation for the development of the following technologies: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas; metasurface-based lenses and antennas for improving the coverage of terahertz band signals; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable intelligent surfaces (RIS), but also lay the foundation for the development of the following technologies: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and enhancing the system network; AI-based communication technologies for achieving system optimization from the design phase by leveraging satellites and artificial intelligence (AI) and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for realizing services with a complexity level beyond the UE operation ability limit by leveraging ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical Problem

[0009] Embodiments described herein are to provide an apparatus and method capable of effectively providing services in a wireless communication system.

[0010] Solution to the Problem

[0011] According to an embodiment of the present disclosure, a method performed by a terminal includes: transmitting a User Assistance Information (UAI) message to a base station, the UAI message including information indicating that flight path information is available; receiving a first message from the base station for requesting the flight path information; and transmitting a second message to the base station for reporting the flight path information.

[0012] According to an embodiment of the present disclosure, a method performed by a base station includes: receiving a User Assistance Information (UAI) message from a terminal, the UAI message including information indicating that flight path information is available; transmitting a first message to the terminal for requesting the flight path information; and receiving a second message from the terminal for reporting the flight path information.

[0013] Advantageous Effects of the Invention

[0014] The present disclosure provides an apparatus and a method capable of effectively providing services in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1A Shows the structure of an LTE system according to an embodiment of the present disclosure.

[0016] Figure 1B Shows the radio protocol structure in an LTE system according to an embodiment of the present disclosure.

[0017] Figure 1C Shows the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0018] Figure 1D Shows the radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0019] Figure 1E Shows the process of a Unmanned Aerial Vehicle (UAV) UE reporting flight path information to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0020] Figure 1F Shows the process of a Unmanned Aerial Vehicle (UAV) UE reporting the availability of flight path information to a base station through UE Assistance Information in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0021] Figure 1G Shows the method of a Unmanned Aerial Vehicle (UAV) UE managing flight information assistance configuration information (flightPath - AssistanceConfig) in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0022] Figure 1H Disclosed is a method for a Unmanned Aerial Vehicle (UAV) UE to manage flight information assistance configuration information (flightPath - AssistanceConfig) in a next - generation mobile communication system according to an embodiment of the present disclosure.

[0023] Figure 1I Disclosed is a process for exchanging flight path information (FlightPathReport) transmitted by a Unmanned Aerial Vehicle (UAV) UE between base stations in a next - generation mobile communication system according to an embodiment of the present disclosure.

[0024] Figure 1J Disclosed is a process for a Unmanned Aerial Vehicle (UAV) UE to report flight path information to a base station in a next - generation mobile communication system according to an embodiment of the present disclosure.

[0025] Figure 1K Disclosed is a process for a Unmanned Aerial Vehicle (UAV) UE to report flight path information to a base station in a next - generation mobile communication system according to an embodiment of the present disclosure.

[0026] Figure 1L It is a block diagram showing the structure of a UE according to an embodiment of the present disclosure.

[0027] Figure 1M It is a block diagram showing the structure of a base station according to an embodiment of the present disclosure. Detailed Description of the Invention

[0028] Hereinafter, the operation principle of the present disclosure will be described in detail with reference to the accompanying drawings. When describing the present disclosure below, detailed descriptions of known functions or configurations incorporated herein will be omitted when it is determined that such descriptions may make the subject matter of the present disclosure unnecessarily unclear. The terms to be described below are terms defined in consideration of the functions in the present disclosure and may vary according to the user, the user's intention, or habit. Therefore, the definitions of the terms should be determined based on the content throughout the specification.

[0029] For the same reason, in the drawings, some elements may be exaggerated, omitted, or schematically shown. Additionally, the size of each element does not fully reflect the actual size. In the corresponding drawings, the same or corresponding elements are assigned the same reference numerals.

[0030] Advantages, features, and implementation methods of the present disclosure will be apparent by referring to the embodiments described in detail below with reference to the accompanying drawings. However, the present disclosure is not limited to the embodiments stated below but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements.

[0031] In this text, it should be understood that each block in the flowchart illustration and combinations of blocks in the flowchart illustration can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing device create means for implementing the functions specified in one or more of the flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more of the flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device, thereby producing a computer-implemented process, such that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more of the flowchart blocks.

[0032] In addition, each block in the flowchart illustration can represent a module, a segment of code, or a portion of code that includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions recited in the blocks may occur out of order. For example, depending on the functions involved, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order.

[0033] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, the meaning of "unit" is not always limited to software or hardware. A "unit" can be constructed to be stored in an addressable storage medium or to execute on one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, the elements and "units" can be implemented as one or more CPUs within a reproduction device or a secure multimedia card. In addition, a "unit" in an embodiment can include one or more processors. In the following description of the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of known functions or configurations incorporated herein will be omitted. Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0034] In the following description, for convenience of description, terms for identifying access nodes, terms for referring to network entities, terms for referring to messages, terms for referring to interfaces between network entities, terms for referring to various identification information, etc. are illustratively used. Thus, the present disclosure is not limited to the terms described below, and other terms referring to a subject having an equivalent technical meaning can also be used.

[0035] In the following description of the present disclosure, for convenience of description, terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard will be used. However, the present disclosure is not limited to these terms and names, and can be applied to systems conforming to other standards in the same manner. In the present disclosure, for convenience of description, the term "eNB" can be used interchangeably with the term "gNB". That is, a base station described as an "eNB" can refer to a "gNB".

[0036] In the following description of the present disclosure, for convenience of description, terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard will be used. However, the present disclosure is not limited to these terms and names, and can be applied to systems conforming to other standards in the same manner. In the present disclosure, for convenience of description, the term "eNB" can be used interchangeably with the term "gNB". That is, a base station described as an "eNB" can refer to a "gNB".

[0037] In the following description, a base station is an entity that allocates resources to terminals and can be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, and a node on the network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. Of course, the examples given above are not restrictive.

[0038] In particular, the present disclosure can be applied to 3GPP NR (the fifth-generation mobile communication standard). In addition, the present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technologies (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety-related services, etc.). In the present disclosure, for convenience of description, the term "eNB" may be used interchangeably with the term "gNB". That is, a base station described as an "eNB" may refer to a "gNB". Additionally, the term "terminal" may refer not only to mobile phones, NB-IoT devices, and sensors, but also to any other wireless communication device.

[0039] Wireless communication systems are evolving into broadband wireless communication systems to provide high-speed and high-quality packet data services and typical voice-based services using communication standards such as 3GPP's High-Speed Packet Access (HSPA), LTE (Long-Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), Advanced LTE (LTE-A), LTE-Pro, 3GPP2's High-Speed Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, etc.

[0040] As a typical example of a broadband wireless communication system, the LTE system adopts an Orthogonal Frequency Division Multiplexing (OFDM) scheme in the downlink (DL) and a Single-Carrier Frequency Division Multiple Access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the radio link through which a user equipment (UE) (or a mobile station (MS)) transmits data or control signals to a base station (BS, eNode B, or gNode B), and the downlink refers to the radio link through which the base station transmits data or control signals to the UE. The above multiple access schemes separate the data or control information of corresponding users by allocating and operating time-frequency resources for transmitting data or control information for each user so as to avoid overlapping with each other (i.e., to establish orthogonality).

[0041] Since the 5G communication system, which is a post-LTE communication system, must freely reflect various requirements of users, service providers, etc., it must support services that meet various requirements. Services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low-latency communication (URLLC), etc.

[0042] According to an embodiment, eMBB aims to provide a higher data rate than that supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, for a single base station, eMBB must provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink. In addition, the 5G communication system must provide an increased user-perceived data rate as well as a maximum data rate for the UE. To meet such requirements, it may be necessary to improve the transmission / reception technology including further enhanced multiple-input multiple-output (MIMO) transmission technology. Additionally, the data rate required by the 5G communication system can be obtained using a frequency bandwidth of more than 20 MHz in a frequency band of 3 to 6 GHz or 6 GHz or higher, rather than using a transmission bandwidth of at most 20 MHz in the 2 GHz frequency band used in LTE to transmit signals.

[0043] In addition, in the 5G communication system, mMTC is regarded as supporting application services such as the Internet of Things (IoT). mMTC may have requirements such as supporting the connection of a large number of UEs within a cell, enhancing the coverage of UEs, increasing battery life, reducing the cost of UEs, etc., in order to effectively provide the IoT. Since the IoT provides communication functions while being provided to various sensors and various devices, it must support a large number of UEs in the cell (e.g., 1,000,000 UEs / km 2 ). In addition, UEs supporting mMTC may require a wider coverage range than other services provided by the 5G communication system, because UEs are likely to be located in shadow areas such as the basements of buildings, which are not covered by the cell due to the nature of the service. UEs supporting mMTC must be configured to be inexpensive and may require a very long battery life time, such as 10 to 15 years, because it is difficult to replace the battery of the UE frequently.

[0044] Finally, URLLC, as a cellular-based mission-critical wireless communication service, can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, telemedicine, emergency alerts, etc. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC should meet an air interface latency of less than 0.5 ms, and also require 10 -5Or a smaller packet error rate. Therefore, for services supporting URLLC, the 5G system must provide a shorter transmission time interval (TTI) than other services, and may also require designs for allocating a large amount of resources within the frequency band to ensure the reliability of the communication link.

[0045] The above three services considered in the 5G communication system (i.e., eMBB, URLLC, and mMTC) can be multiplexed and transmitted in a single system. In this case, different transmission / reception techniques and transmission / reception parameters can be used between services to meet the different requirements of the corresponding services. However, mMTC, URLLC, and eMBB as described above are only examples of different service types, and the service types to which the present disclosure is applied are not limited to those mentioned above.

[0046] In the following description of the embodiments of the present disclosure, the LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) system will be described by way of example, but the embodiments of the present disclosure can be applied to other communication systems having a similar background or channel type. Additionally, based on the judgment of those skilled in the art, the embodiments of the present disclosure can be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0047] Figure 1A Shows the structure of an LTE system according to an embodiment of the present disclosure.

[0048] Reference Figure 1A , as shown in the figure, the radio access network of the LTE system includes next-generation base stations (evolved Node B, hereinafter referred to as ENB, Node B, or base station) 1a-05, 1a-10, 1a-15, and 1a-20, a mobility management entity (MME) 1a-25, and a serving gateway (S-GW) 1a-30. A user equipment (hereinafter referred to as UE or terminal) 1a-35 accesses an external network through ENBs 1a-05 to 1a-20 and S-GW 1a-30.

[0049] In Figure 1AAmong them, ENBs 1a-05 to 1a-20 may correspond to regular Node Bs in a Universal Mobile Telecommunications System (UMTS). The ENBs are connected to UEs 1a-35 via radio channels and play a more complex role than regular Node Bs. In an LTE system, since all user services including real-time services such as Voice over Internet Protocol (VoIP) are served via a shared channel, a device for collecting status information (such as the buffer status, available transmit power status, and channel status of the UE) is required, and ENBs 1a-05 to 1a-20 act as such a device. Generally speaking, one ENB can control multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system may use Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) in a 20 MHz bandwidth, for example, as the radio access technology. Obviously, the examples given above are not restrictive. In addition, ENBs 1a-05 to 1a-20 may adopt an Adaptive Modulation and Coding (hereinafter referred to as AMC) scheme to determine the modulation scheme and channel coding rate according to the channel status of the UE. The S-GW 1a-30 is a device that provides data bearers and generates or removes data bearers under the control of the MME 1a-25. The MME is a device responsible for various control functions of the UE and the mobility management function and is connected to multiple base stations.

[0050] Figure 1B FIG. shows a radio protocol structure in an LTE system according to an embodiment of the present disclosure.

[0051] Reference Figure 1B , the radio protocol of the LTE system includes a Packet Data Convergence Protocol (PDCP) 1b-05 or 1b-40, a Radio Link Control (RLC) 1b-10 or 1b-35, and a Media Access Control (MAC) 1b-15 or 1b-30 on each of the UE and ENB sides. The Packet Data Convergence Protocol (PDCP) 1b-05 or 1b-40 is responsible for operations such as IP header compression / reconstruction. The main functions of PDCP are summarized as follows. Obviously, the examples given below are not restrictive.

[0052] - Header compression and decompression: only Robust Header Compression (ROHC)

[0053] - Transmission of user data

[0054] - Sequentially deliver upper layer PDUs during the PDCP reconstruction process for RLC AM

[0055] - For split bearers in DC (only RLC AM supported): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0056] - For RLC AM, re-detect the lower layer SDUs during PDCP re-establishment

[0057] - For RLC AM, re-transmit PDCP SDUs during handover, and for split bearers in DC, re-transmit PDCP PDUs during PDCP data recovery

[0058] - Encryption and decryption

[0059] - Timer-based SDU discard in the uplink

[0060] Radio Link Control (hereinafter referred to as RLC) 1b-10 or 1b-35 can reconfigure the PDCP protocol data unit (PDU) into an appropriate size to perform ARQ operations. The main functions of RLC are summarized as follows. Obviously, the examples given below are not restrictive.

[0061] - Transmission of upper layer PDUs

[0062] - Error correction by ARQ (only for AM data transmission)

[0063] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transmission)

[0064] - Re-segmentation of RLC data PDUs (only for AM data transmission)

[0065] - Re-ordering of RLC data PDUs (only for UM and AM data transmission)

[0066] - Duplicate detection (only for UM and AM data transmission)

[0067] - Protocol error detection (only for AM data transmission)

[0068] - RLC SDU discard (only for UM and AM data transmission)

[0069] - RLC re-establishment

[0070] MAC 1b-15 or 1b-30 can be connected to several RLC layer devices configured in a single terminal, and multiplex RLC PDUs into MAC PDUs and demultiplex MAC PDUs into RLC PDUs. The main functions of MAC are summarized as follows. Obviously, the examples given below are not restrictive.

[0071] - Mapping between logical channels and transport channels

[0072] - Multiplex MAC SDUs belonging to one or different logical channels into transport blocks (TBs) delivered to the physical layer on a transport channel / Demultiplex MAC SDUs belonging to one or different logical channels from transport blocks (TBs) delivered from the physical layer on a transport channel

[0073] - Scheduling information reporting

[0074] - Error correction by HARQ

[0075] - Priority handling between the logical channels of a UE

[0076] - Priority handling between UEs by means of dynamic scheduling

[0077] - MBMS service identification

[0078] - Transport format selection

[0079] - Padding

[0080] The physical layer 1b - 20 or 1b - 25 performs the following operations: performing channel coding and modulation on the upper layer data to obtain OFDM symbols and delivering them via a radio channel; or demodulating the OFDM symbols received via the radio channel, performing channel decoding on them, and delivering them to the upper layer. Obviously, the examples given above are not restrictive.

[0081] Figure 1C Shows the structure of a next - generation mobile communication system according to an embodiment of the present disclosure.

[0082] Reference Figure 1C , the radio access network of a wireless communication system (hereinafter referred to as a next - generation mobile communication system, NR or 5G) may include a new radio node B (hereinafter referred to as an NR gNB or an NR base station) 1c - 10 and a new radio core network (NR CN) 1c - 05. A user terminal (a new radio user equipment, hereinafter referred to as an NR UE or an NR terminal) 1c - 15 may access an external network via the NR gNB 1c - 10 and the NR CN 1c - 05.

[0083] In Fig. 1c, the NR gNB 1c-10 may correspond to an evolved Node B (eNB) in a conventional LTE system. The NR gNB is connected to the NR UE 1c-15 via a radio channel and can provide outstanding services compared to a conventional Node B. In the next-generation mobile communication system, since all user services are served through a shared channel, a device for collecting status information (such as the buffer status, available transmit power status, and channel status of the UE) and performing scheduling accordingly is required, and the NR gNB 1c-10 can act as such a device. Generally, one NR gNB can control multiple cells.

[0084] According to an embodiment of the present disclosure, in order to achieve ultra-high-speed data transmission beyond the current LTE, the next-generation mobile communication system can provide a wider bandwidth than the existing maximum bandwidth, can adopt orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as a radio access technology, and can additionally integrate beamforming technology therewith. Further, according to an embodiment of the present disclosure, the NR gNB 1c-10 can adopt an adaptive modulation and coding (hereinafter referred to as AMC) scheme to determine a modulation scheme and a channel coding rate according to the channel status of the UE. The NR CN 1c-05 can perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN 1c-05 is a device responsible for various control functions of the UE and mobility management functions and can be connected to multiple base stations. Additionally, the next-generation mobile communication system can interoperate with the existing LTE system, and the NR CN 3-05 can be connected to the MME 1c-25 via a network interface. The MME can be connected to the eNB 1c-30 which is an existing base station.

[0085] Figure 1D Fig. shows a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0086] Reference Figure 1D , the radio protocol of the next-generation wireless communication system may include an NR service data adaptation protocol (SDAP) 1b-01 or 1b-45, an NR packet data convergence protocol (PDCP) 1b-05 or 1b-40, an NR radio link control (RLC) 1b-10 or 1b-35, and an NR media access control (MAC) 1b-15 or 1b-30 on each of the UE and NR base station sides.

[0087] According to an embodiment of the present disclosure, the main functions of the NR SDAP 1d-01 or 1d-45 may include some of the following functions. Obviously, the examples given below are not restrictive.

[0088] - Transmission of user plane data

[0089] - Mapping between QoS Flows and DRBs for both DL and UL

[0090] - Marking QoS Flow ID in both DL and UL packets

[0091] - Reflective QoS Flow to DRB mapping for UL SDAP PDUs

[0092] Regarding the SDAP layer device, whether to use the header of the SDAP layer device or the function of the SDAP layer device can be configured for the UE through an RRC message according to the PDCP layer device, according to the bearer, or according to the logical channel. If the SDAP header is configured, the non-access stratum (NAS) quality of service (QoS) reflection configuration 1-bit indicator (NAS reflective QoS) and the access stratum (AS) QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header can indicate to the UE that the UE can update or reconfigure the mapping information of QoS flows and data bearers for the uplink and downlink. The SDAP header can include QoS Flow ID information indicating QoS. The QoS information can be used as data processing priority information, scheduling information, etc. to smoothly support services.

[0093] According to an embodiment of the present disclosure, the main functions of NR PDCP 1d-05 or 1d-40 may include some of the following functions. Obviously, the examples given below are not restrictive.

[0094] - Header compression and decompression: only ROHC

[0095] - Transmission of user data

[0096] - In-sequence delivery of upper layer PDUs

[0097] - Out-of-sequence delivery of upper layer PDUs

[0098] - PDCP PDU reordering for reception

[0099] - Duplicate detection of lower layer SDUs

[0100] - Retransmission of PDCP SDUs

[0101] - Encryption and decryption

[0102] - Timer-based SDU discard in the uplink

[0103] According to an embodiment of the present disclosure, reordering of the NR PDCP device may refer to the function of reordering PDCP PDUs received from the lower layer based on the PDCP sequence number (SN). The reordering of the NR PDCP device may include at least one of the following: the function of transmitting data to the upper layer according to the reordered sequence, the function of directly transmitting data regardless of the order, the function of rearranging the order to record lost PDCP PDUs, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting retransmission of lost PDCP PDUs.

[0104] According to an embodiment of the present disclosure, the main functions of NR RLC 1d-10 or 1d-35 may include some of the following functions. Obviously, the examples given below are not restrictive.

[0105] - Transmission of upper layer PDUs

[0106] - In-sequence delivery of upper layer PDUs

[0107] - Out-of-sequence delivery of upper layer PDUs

[0108] - Error correction by ARQ

[0109] - Concatenation, segmentation, and reassembly of RLC SDUs

[0110] - Resegmentation of RLC data PDUs

[0111] - Reordering of RLC data PDUs

[0112] - Duplicate detection

[0113] - Protocol error detection

[0114] - RLC SDU discard

[0115] - RLC reconstruction

[0116] The sequential delivery of the NR RLC device may refer to the following function: If there are missing RLC SDUs, only the RLC SDUs preceding the missing RLC SDU are delivered to the upper layer in sequence. The sequential delivery may include at least one of the following: the function of recombining several RLC SDUs and transmitting the recombined RLC SDU if one original RLC SDU is divided into several RLC SDUs and then the RLC SDUs are received; the function of rearranging the received RLC PDUs with reference to the RLC sequence number (SN) or the PDCP sequence number (SN); the function of rearranging the order to record the missing RLC PDUs; the function of reporting the status of the missing RLC PDUs to the transmitting side; the function of requesting retransmission of the missing RLC PDUs; the function of only transmitting to the upper layer in sequence the RLC SDUs preceding the missing RLC SDU if there are missing RLC SDUs; the function of transmitting to the upper layer in sequence all the RLC SDUs received before the timer starts if a predetermined timer has expired despite the existence of missing RLC SDUs; and the function of transmitting to the upper layer in sequence all the RLC SDUs received so far if a predetermined timer has expired despite the existence of missing RLC SDUs.

[0117] In addition, according to an embodiment of the present disclosure, NR RLC 1d-1- or 1d-35 may include the function of processing RLC PDUs in the order of reception (in the order of arrival regardless of the sequence number order) and delivering them to the PDCP device regardless of the order (out-of-sequence delivery), and may include the function of receiving, in the case of fragmentation, the fragments stored in the buffer or to be received later, reconfiguring them into a complete RLC PDU, processing it, and delivering it to the PDCP device. NR RLC 1d-10 or 1d-35 may not include the concatenation function, which may be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer. Obviously, the examples given above are not restrictive.

[0118] The out-of-sequence delivery of the NR RLC device 1d-10 or 1d-35 may include the function of directly delivering the RLC SDUs received from the lower layer to the upper layer regardless of the order, and may include at least one of the following: the function of recombining and delivering the multiple RLC SDUs into which one original RLC SDU has been segmented and received; and the function of storing the RLC SN or PDCP SN of the received RLC PDUs, reordering them, and recording the missing RLC PDUs.

[0119] According to an embodiment of the present disclosure, NR MAC 1d-15 or 1d-30 may be connected to multiple NR RLC layer devices configured in a UE, and the main functions of NR MAC may include at least some of the following functions. Obviously, the examples given below are not restrictive.

[0120] - Mapping between logical channels and transport channels

[0121] - Multiplexing / demultiplexing of MAC SDUs

[0122] - Scheduling information reporting

[0123] - Error correction via HARQ

[0124] - Priority handling between logical channels of a UE

[0125] - Priority handling between UEs by means of dynamic scheduling

[0126] - MBMS service identification

[0127] - Transport format selection

[0128] - Padding

[0129] According to an embodiment of the present disclosure, NR PHY layer 1b-20 or 1b-25 may perform the following operations: performing channel coding and modulation on upper layer data to obtain OFDM symbols and delivering them through a radio channel; or demodulating the OFDM symbols received through the radio channel, performing channel decoding on them, and delivering them to the upper layer. Obviously, the examples given above are not restrictive.

[0130] Figure 1E Illustrates a process in which an unmanned aerial vehicle (UAV) UE reports flight path information to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0131] Reference Figure 1E , UE 1e-01 may configure an RRC connection with base station 1e-02 and may be in the RRC connected mode (RRC_CONNECTED) (operation 1e-05).

[0132] In operation 1e-10, UE 1e-01 in the RRC connected mode may transmit a UE capability information message to base station 1e-02. The UE capability information message may include an indicator (or indication information) indicating that flight path information can be reported.

[0133] In operation 1e-15, the base station 1e-02 may transmit an RRC connection release message (RRCRelease) to the UE 1e-01 in the RRC connected mode. The RRC connection release message may include suspend configuration information (suspendConfig). That is, when the RRC connection release message includes suspend configuration information, the UE 1e-01 may transition (operation 1e-20) to the RRC inactive mode (RRC_INACTIVE). On the other hand, when the RRC connection release message does not include suspend configuration information, the UE 1e-01 may transition (operation 1e-20) to the RRC idle mode (RRC_IDLE).

[0134] In operation 1e-20, the UE 1e-01 that has transitioned to the RRC inactive mode may perform an RRC connection resume procedure with the base station 1e-02. Specifically, the UE 1e-01 may transmit (operation 1e-25) an RRC resume request message (RRCResumeRequest or RRCResumeRequest1) to the base station 1e-02. The base station 1e-02 that has received the RRC resume request message may transmit (operation 1e-30) an RRC resume message (RRCResume) to the UE 1e-01. The UE 1e-01 that has received the RRC resume message may transition (operation 1e-35) to the RRC connected mode. The UE 1e-01 that has transitioned to the RRC connected mode may transmit (operation 1e-40) an RRC resume complete message (RRCResumeComplete) to the base station 1e-02. If the UE 1e-01 has flight path information (if the UE has available flight path information), the UE 1e-01 may include an indicator (flightPathInfoAvailable) indicating that the flight path information is included in the RRC resume complete message.

[0135] In operation 1e-20, the UE 1e-01 transitioning to the RRC idle mode can perform an RRC connection setup procedure with the base station 1e-02. Specifically, the UE 1e-01 can transmit (operation 1e-25) an RRC setup request message (RRCSetupRequest) to the base station 1e-02. The base station 1e-02 that receives the RRC setup request message can transmit (operation 1e-30) an RRC setup message (RRCSetup) to the UE 1e-01. The UE 1e-01 that receives the RRC setup message can transition (operation 1e-35) to the RRC connected mode. The UE 1e-01 that has transitioned to the RRC connected mode can transmit (operation 1e-40) an RRC setup complete message (RRCSetupComplete) to the base station 1e-02. If the UE 1e-01 has flight path information (if the UE has available flight path information), the UE 1e-01 can include an indicator (flightPathInfoAvailable) indicating that the flight path information is included in the RRC setup complete message.

[0136] In operation 1e-45, the base station 1e-02 can transmit a UE information request message (UEInformationRequest) to the UE 1e-01. The flightPathInfoReq information can be included in the UE information request message. At least one of the following pieces of information can be included in the flightPathInfoReq information. However, the present disclosure is not limited to the above examples.

[0137] -includeTimeStamp: Indicates whether the time stamp of each waypoint can be reported in the flight path information report if the time stamp information is available at the UE.

[0138] -maxWayPointNumber: Indicates the maximum number of waypoints that the UE can include in the flight path information report (if this information is available at the UE).

[0139] In operation 1e-50, if the UE information request message received in operation 1e-45 includes the flightPathInfoReq information and UE 1e-01 has flight path information (if the UE has available flight path information), then UE 1e-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to the base station 1e-02. The UE information response message may include one or more WayPointLocation. If includeTimeStamp is set to true, then UE 1e-01 may include in the UE information response message information about the time at which the UE intends to reach each waypoint (if includeTimeStamp is set to true, the UE sets the field timeStamp to the time at which the UE intends to reach each waypoint (if such information is available at the UE)).

[0140] As a reference, according to an embodiment of the present disclosure, if UE 1e-01 has flight path information (if the UE has available flight path information), then the UE may include an indicator (flightPathInfoAvailable) indicating that the flight path information is included in the RRC connection reestablishment complete message (RRCReestablishmentComplete) or the RRC connection reconfiguration complete message (RRCReconfigurationComplete) and transmit it to the base station 1e-02. Thus, the base station 1e-02 may retrieve the flight path information (FlightPathInfoReport) from UE 1e-01 through operations 1e-45 and 1e-50.

[0141] Figure 1F A process is shown in which an unmanned aerial vehicle (UAV) UE reports the availability of flight path information to a base station through UE assistance information (UEAssistanceInformation) according to an embodiment of the present disclosure.

[0142] As a reference, the following various scenarios may be supported by the UAV UE.

[0143] - Accident and crime scene investigation

[0144] - Aerial photography

[0145] - Agricultural inspection

[0146] - Construction inspection

[0147] - Crowd control

[0148] - Drug and gas detection

[0149] - Entertainment and movies

[0150] - Flash flood warning

[0151] - Fire location

[0152] - Intelligence collection

[0153] - Surveying and mapping

[0154] - Network tower inspection

[0155] - News collection

[0156] - Pilot reinforcement

[0157] - Pipeline / railway inspection

[0158] - Distribution tower inspection

[0159] - Search and rescue

[0160] - Security

[0161] - Small package delivery

[0162] - Traffic monitoring

[0163] - Wildlife and environmental monitoring, etc.

[0164] In the above scenarios, the UAV UE can move along a determined flight path at a predetermined time interval (e.g., for small package delivery), or can move along a variable flight path according to the situation at a predetermined time interval (e.g., for accident and crime scene investigation). That is, when the UE starts flying from a predetermined time point, the predetermined flight path can be changed according to the situation. In the present disclosure, the UE that supports the above scenarios is referred to as the UAV UE.

[0165] Reference Figure 1F , UE 1f-01 can configure an RRC connection with base station 1f-02 and can be in the RRC connected mode (RRC connection) (operation 1f-05).

[0166] In operation 1f-10, if UE 1f-01 has flight path information (if the UE has available flight path information), then UE 1f-01 can transmit an indicator (flightPathInfoAvailable) indicating the availability of the flight path information to base station 1f-02 through at least one of the following RRC messages.

[0167] - RRC Setup Complete message (RRCSetupComplete)

[0168] - RRC Resume Complete Message (RRCResumeComplete)

[0169] - RRC Reestablishment Complete Message (RRCReestablishmentComplete)

[0170] - RRC Reconfiguration Complete Message (RRCReconfigurationComplete)

[0171] In operation 1f-15, the UE 1f-01 in RRC connected mode can transmit a UE Capability Information message to the base station 1f-01. The UE Capability Information message can include information indicating the capability of the UE 1f-01 to notify the base station 1f-02, via a UE Assistance Information message, of an indicator (initialOrUpdatedFlightPathInfoAvailable) indicating that initial flight path information or updated flight path information is available. Additionally, the UE Capability Information message can include information indicating the capability of the UE 1f-01 to notify the base station, via a UE Assistance Information message, of an indicator (noFlightPathInfoAvailable) indicating that flight path information is no longer available. For reference, the UE 1f-01 can notify the base station of the above initial flight path information, updated flight path information, indicator indicating flight path unavailability, etc. as one piece of capability information. Additionally, according to an embodiment, the description made in operation 1f-01 can correspond to operation 1e-01 in the above embodiment. Additionally, according to an embodiment, operation 1f-15 can be performed before operation 1f-10.

[0172] In operation 1f-20, the base station 1f-02 can configure otherConfig for the UE 1f-01 via a predetermined RRC message. For example, the predetermined RRC message can mean an RRC Connection Reconfiguration message (RRCReconfiguration) or an RRC Resume message (RRCResume). otherConfig can include flight path assistance configuration information (flightPath-AssistanceConfig). The flight path assistance configuration information can include at least one of the following pieces of information. However, the present disclosure is not limited to the following examples.

[0173] - flightPath-AssistanceProhibitTimer: A timer value that can be configured as one of one or more values.

[0174] - WayPointDiff: can be configured as a distance difference among one or more values. For example, the base station can configure WayPointDiff for the UE as a value indicating a predetermined distance difference from each waypoint transmitted through the UE Information Response message.

[0175] - TimeStampDiff: can be configured as a time difference among one or more values. For example, the base station can configure TimeStampDiff for the UE as a value indicating a predetermined time difference from the timestamp associated with each waypoint transmitted through the UE Information Response message.

[0176] - 1-bit indicator: indicates whether the UE can transmit, through the UE Assistance Information message, an indicator indicating that the initial flight path information or updated flight path information is available.

[0177] In operation 1f-25, the UE 1f-01 can transmit a UE Assistance Information message to the base station 1f-02. The UE Assistance Information message can include an indicator or information element indicating that the (updated) flight path information is available. The UE 1f-01 can transmit the UE Assistance Information message to the base station 1f-02 only if at least one of the following conditions is met. However, the present disclosure is not limited to the following examples.

[0178] - Condition 1: is the case where the UE 1f-01 has not transmitted flightPathInfoAvailable to the base station 1f-02 through operation 1f-10 and the UE 1f-01 has flight path information or updated flight path information (if the UE has available flight path information or if the UE has available updated flight path information).

[0179] - Condition 2: is the case where the UE 1f-01 has flight path information or updated flight path information but has not transmitted the flight path information to the base station 1f-02.

[0180] - Condition 3: is the case where the UE 1f-01 has transmitted flightPathInfoAvailable through operation 1f-10, but the flight path information to be transmitted is updated thereafter (in this case, the unupdated flight path information and the updated flight path information have not been transmitted to the base station 1f-02).

[0181] UE 1f-01 can activate or reactivate a timer value having a value configured by flightPath-AssistanceProhibitTimer. When the timer value has expired but the actual flight path information has not been transmitted to base station 1f-02, UE1f-01 may not otherwise retransmit a UE assistance information message to base station 1f-02. That is, UE 1f-01 may not retransmit the UE assistance information message to prevent unnecessary retransmission of the same message to base station 1f-02.

[0182] Flight path information can be generated after operation 1f-10, and thus in operation 1f-10 it is the case that UE 1f-01 cannot transmit flightPathInfoAvailable to base station 1f-02. Therefore, UE 1f-01 can notify base station 1f-02 of information indicating that flight path information is available through operation 1f-25, such that when necessary, the base station can later retrieve the flight path information from UE 1f-01.

[0183] In operation 1f-30, base station 1f-02 can transmit a UE information request message (UEInformationRequest) to UE 1f-01. The UE information request message can include flightPathInfoReq information. The fligthPathInfoReq information can include at least one of the following pieces of information. However, the present disclosure is not limited to the following examples.

[0184] - includeTimeStamp: Indicates whether the time stamp of each waypoint can be reported in the flight path information report if the time stamp information is available at the UE.

[0185] - maxWayPointNumber: Indicates the maximum number of waypoints that the UE can include in the flight path information report (if this information is available at the UE).

[0186] In operation 1f-35, if the UE information request message received in operation 1f-30 includes the flightPathInfoReq information and UE 1f-01 has (updated) flight path information (if the UE has available (updated) flight path information), then UE 1f-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to base station 1f-02. The flightPathInfoReport may include one or more WayPointLocation. If includeTimeStamp is set to true, in the UE information response message, UE 1f-01 may include in the UE information response message information about the time at which the UE intends to reach each waypoint (if includeTimeStamp is set to true, the UE sets the field timeStamp to the time at which the UE intends to reach each waypoint (if such information is available at the UE)).

[0187] In operation 1f-40, if at least one of the following conditions is met, then UE 1f-01 may transmit a UE assistance information message (UEAssistanceInformation) including an indicator or information element indicating that (updated) flight path information is available to base station 1f-02. However, the present disclosure is not limited to the following examples.

[0188] - Condition 3: is a case where at least one is updated according to the flightPathReport transmitted through operation 1f-35.

[0189] - Condition 4: is a case where Condition 3 is satisfied and a timer activated or reactivated with a value configured by the flightPath-AssistanceProhibitTimer expires.

[0190] - Condition 5: is a case where at least one waypoint has a difference equal to or greater than the WayPointDiff in the flightPathReport transmitted through operation 1f-35. In this case, when comparing the differences, the flightPathReport transmitted through operation 1f-30 is compared with the flight path along which UE 1f-01 is actually moving or the flight path along which the UE expects to move.

[0191] - Condition 6: is a case where Condition 5 is satisfied and a timer activated or reactivated with a value configured by the flightPath-AssistanceProhibitTimer expires.

[0192] - Condition 7: is the case where at least one timestamp has a difference equal to or greater than the TimeStampDiff in the flightPathReport transmitted by operation 1f-35. In this case, when comparing the differences, the flightPathReport transmitted by operation 1f-30 is compared with the time point when the UE actually reaches the flight path or the time point when the UE is expected to reach.

[0193] - Condition 8: is the case where Condition 7 is satisfied and the timer activated or reactivated using the value configured by flightPath-AssistanceProhibitTimer expires.

[0194] - Condition 9: is the case where both Condition 5 and Condition 7 are satisfied.

[0195] - Condition 10: is the case where Condition 9 is satisfied and the timer activated or reactivated using the value configured by flightPath-AssistanceProhibitTimer expires.

[0196] In operation 1f-50, the base station 1f-02 may transmit a UE information request message (UEInformationRequest) to the UE 1f-01. The UE information request message may include flightPathInfoReq information. This may correspond to the description made in operation 1f-30.

[0197] In operation 1f-55, if the UE information request message received in operation 1f-50 includes flightPathInfoReq information and the UE 1f-01 has (updated) flight path information (if the UE has available (updated) flight path information), then the UE 1f-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to the base station 1f-02.

[0198] In operation 1f-60, the UE 1f-01 may transmit a UE assistance information message to the base station 1f-02. The UE assistance information message includes a field containing an indicator or information element indicating that (updated) flight path information is available, but may not include the indicator or information element included in the field, or may include an indicator indicating that the flight path information is no longer available. The UE 1f-01 may transmit a UE assistance information message to the base station 1f-02 only when at least one of the following conditions is satisfied.

[0199] - Condition 10: is the case where the flight path transmitted in operation 1f-35 or 1f-55 has ended and the flight path information is no longer available.

[0200] - Condition 11: This is the case where Condition 10 is satisfied and the timer activated or reactivated using the value configured by flightPath - AssistanceProhibitTimer expires.

[0201] - Condition 12: This is the case where a flight path has been transmitted in Operation 1f - 35 or 1f - 55 but the flight path information is no longer available (if the UE no longer has available flight information).

[0202] - Condition 13: This is the case where Condition 12 is satisfied and the timer activated or reactivated using the value configured by flightPath - AssistanceProhibitTimer expires.

[0203] - Condition 14: This is the case where flightPathInfoAvailable has been transmitted through Operation 1f - 10 but the UE does not have flight path information at the current time point (this also applies to Operation 1f - 25).

[0204] For reference, the reason why UE 1f - 01 provides flight path information to base station 1f - 02 is to allow base station 1f - 02 to efficiently use resources according to the flight path of UE 1f - 01 based on the flight path information. That is, the base station can provide seamless service to UE 1f - 01 by selecting a target cell for handover according to a given time slot and ensuring the resources to be used in advance. Therefore, UE 1f - 01 reports expected flight path information to base station 1f - 02 to achieve a win - win effect for both UE 1f - 01 and base station 1f - 02. Additionally, as in Operation 1f - 60, if UE 1f - 01 notifies base station 1f - 02 that the flight path information is no longer available, there is an additional expected effect that base station 1f - 02 can efficiently use the available resources for other UEs.

[0205] Figure 1G A method for an unmanned aerial vehicle (UAV) UE to manage flight information assistance configuration information (flightPath - AssistanceConfig) in a next - generation mobile communication system according to an embodiment of the present disclosure is shown.

[0206] Reference Figure 1G , UE 1g - 01 can configure an RRC connection with base station 1g - 02 and can be in the RRC connected mode (RRC connection) (Operation 1g - 05).

[0207] In operation 1g-10, a UE 1g-01 in RRC connected mode may transmit a UE capability information message (UECapabilityInformation) including an indicator indicating the ability to report or update flight path information to a base station 1g-02. This may correspond to operation 1f-15 in the above embodiment.

[0208] In operation 1g-20, the base station 1g-02 may configure otherConfig for the UE 1g-01 via a predetermined RRC message. For example, the predetermined RRC message may mean an RRC connection reconfiguration message (RRCReconfiguration) or an RRC resume message (RRCResume). otherConfig may include flight path assistance configuration information (flightPath-AssistanceConfig). This may correspond to operation 1f-20 in the above embodiment.

[0209] In operation 1g-25, the UE 1g-01 may determine that at least one of the following conditions is met. For reference, the following conditions are described in detail in section 5.3.7.2 of 3GPP TS 38.331 specification.

[0210] 1> According to 5.3.10, when a radio link failure of the MCG is detected and t316 is not configured; or

[0211] 1> According to 5.3.10, when the SCG transmission is suspended while a radio link failure of the MCG is detected; or

[0212] 1> According to 5.3.10, when a PSCell change or PSCell addition is in progress while a radio link failure of the MCG is detected; or

[0213] 1> According to 5.3.10, when the SCG is deactivated while a radio link failure of the MCG is detected; or

[0214] 1> According to clause 5.3.5.8.3, when the reconfiguration synchronization of the MCG fails; or

[0215] 1> According to clause 5.4.3.5, when the movement from NR fails; or

[0216] 1> When an integrity check failure indication for SRB1 or SRB2 from the lower layer is detected, unless an integrity check failure is detected on the RRCReestablishment message; or

[0217] 1> According to clause 5.3.5.8.2, when the RRC connection reconfiguration fails; or

[0218] 1> When a radio link failure of the SCG is detected while the MCG transmission is suspended in NR-DC according to clause 5.3.10.3 or in NE-DC according to clause 5.3.11.3 of TS 36.331

[10] ; or

[0219] 1> When the reconfiguration synchronization of the SCG fails while the MCG transmission is suspended according to clause 5.3.5.8.3; or

[0220] 1> When the SCG change fails while the MCG transmission is suspended according to clause 5.3.5.7a of TS 36.331

[10] ; or

[0221] 1> When the SCG configuration fails while the MCG transmission is suspended in NR-DC according to clause 5.3.5.8.2 or in NE-DC according to clause 5.3.5.5 of TS 36.331

[10] ; or

[0222] 1> When an integrity check failure indication of SRB3 from the lower layer of the SCG is received while the MCG is suspended; or

[0223] 1> When T316 expires according to clause 5.7.3b.5; or

[0224] 1> When a sidelink radio link failure is detected by an L2 U2N remote UE in RRC connected state according to clause 5.8.9.3; or

[0225] 1> When an RRC connected L2 U2N remote UE receives an indication including indicationType of NotificationMessageSidelink according to clause 5.8.9.10; or

[0226] 1> When an upper layer at an RRC connected L2 U2N remote UE indicates a PC5 unicast link release.

[0227] In operation 1g-30, UE 1g-01 may initiate an RRC connection re-establishment procedure. That is, UE 1g-01 may perform the following procedure (Chapter 5.3.7.2 of 3GPP TS 38.331 specification).

[0228] After initiating this procedure, the UE shall: 1> Stop timer T310 (if it is running); 1> Stop timer T312 (if it is running); 1> Stop timer T304 (if it is running); 1> Start timer T311; 1> Stop timer T316 (if it is running); 1> If the UE is not configured with attemptCondReconfig : 2> Reset MAC; 2> Release spCellConfig (if configured); 2> Suspend all RB and BH RLC channels of the IAB-MT and the Uu relay RLC channels of the L2 U2N relay UE, except for SRB0 and the broadcast MRB; 2> Release the MCG SCell (if configured); 2> If MR-DC is configured: 3> Perform the MR-DC release as specified in Clause 5.3.5.10; 2> Release delayBudgetReportingConfig (if configured), and stop timer T342 (if it is running); 2> Release overheatingAssistanceConfig (if configured), and stop timer T345 (if it is running); 2> Release idc-AssistanceConfig (if configured); 2> Release btNameList (if configured); 2> Release wlanNameList (if configured); 2> Release sensorNameList (if configured); 2> Release the drx-PreferenceConfig of MCG (if configured), and stop the timer T346a associated with MCG (if it is running); 2> Release the maxBW-PreferenceConfig of MCG (if configured), and stop the timer T346b associated with MCG (if it is running); 2> Release the maxCC-PreferenceConfig of MCG (if configured), and stop the timer T346c associated with MCG (if it is running); 2> Release the maxMIMO-LayerPreferenceConfig of MCG (if configured), and stop the timer T346d associated with MCG (if it is running); 2> Release the minSchedulingOffsetPreferenceConfig of MCG (if configured), stop the timer T346e associated with MCG (if it is running); 2> Release the rlm-RelaxationReportingConfig(if configured), and stop the timer T346j associated with the MCG (if it is running); 2> Release the bfd-RelaxationReportingConfig (if configured), and stop the timer T346k associated with the MCG (if it is running); 2> Release releasePreferenceConfig (if configured), stop the timer T346f (if it is running); 2> Release onDemandSIB-Request (if configured), and stop the timer T350 (if it is running); 2> Release referenceTimePreferenceReporting (if configured); 2> Release sl-AssistanceConfigNR (if configured); 2> Release obtainCommonLocation (if configured); 2> Release musim-GapAssistanceConfig (if configured), and stop the timer T346h (if it is running); 2> Release musim-LeaveAssistanceConfig (if configured); 2> Release ul-GapFR2-PreferenceConfig (if configured); 2> Release scg-DeactivationPreferenceConfig (if configured), and stop the timer T346i (if it is running); 2> Release propDelayDiffReportConfig (if configured); 2> Release rrm-MeasRelaxationReportingConfig (if configured); 2> Release maxBW-PreferenceConfigFR2-2 (if configured); 2> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured); 2> Release minSchedulingOffsetPreferenceConfigExt (if configured); 1> Release successHO-Config (if configured); 1> If any DAPS bearers are configured: 2> Reset the source MAC and release the source MAC configuration; 2> For each DAPS bearer: 3> Release the RLC entity or the entity specified in clause 5.1.3 of TS 38.322 [4] and the associated logical channels of the source SpCell; 3> Reconfigure the PDCP entity to release DAPS, as specified in TS 38.323 [5]; 2> For each SRB: 3> Release the PDCP entity of the source SpCell; 3> Release the RLC entity specified in clause 5.1.3 of TS 38.322 [4], and the associated logical channels of the source SpCell; 2> Release the physical channel configuration of the source SpCell; 2> Discard the keys (K gNB key, K RRCenc key, K RRCint key, K UPint keys and K UPenc keys) (if any) used in the SpCell; 1> Release sl-L2RelayUE-Config (if configured); 1> Release sl-L2RemoteUE-Config (if configured); 1> Release the SRAP entity (if configured); 1> If the UE is acting as an L2 U2N remote UE: 2> If it is determined to release the PC5-RRC connection with the U2N relay UE: 3> Instruct the upper layer to trigger the release of the PC5 unicast link; 3> Perform cell selection according to the cell selection process specified in TS 38.304

[20] , or perform relay selection as specified in clause 5.8.15.3, or both; 2> Otherwise (i.e., keep the PC5 RRC connection): 3> Consider the connected L2 U2N relay UE as suitable and perform the operations specified in clause 5.3.7.3a; Note 1: Whether to release or retain the current PC5 unicast link depends on the remote UE implementation.

[0229] 1> Otherwise: 2> Perform cell selection according to the cell selection process specified in TS 38.304

[20] .

[0230] Note 2: For an L2 U2N remote UE, if suitable cells and suitable relays are available, the UE can choose either based on its implementation.

[0231] The present disclosure proposes to release the flightPath - AssistanceConfig information, which is configured in operation 1g - 20, when the RRC configuration re - establishment process is initiated by UE 1g - 01. Additionally, the present disclosure proposes to stop the timer Txxx if the UE is running a timer with a value of flightPath - AssistanceProhibitTimer configured by the flightPath - AssistanceConfig information. For example, the proposed operations can be performed according to the following procedure.

[0232] 1> If the UE is not configured with attemptCondReconfig : …

[0233] 2> Release flightPath-AssistanceConfig (if configured), and stop the timer Txxx (if it is running); In operation 1g - 35, UE 1g - 01 can select a suitable NR cell while the T311 timer is running and then perform the following procedure.

[0234] After selecting a suitable NR cell, the UE shall: 1> Ensure that it has valid and up - to - date basic system information as specified in Clause 5.2.2.2; 1> Stop the timer T311; 1> If T390 is running: 2> Stop the timer T390 for all access categories; 2> Perform the actions specified in 5.3.14.4; 1> Stop the relay (re) - selection process (if it is in progress); 1> If cell selection is triggered due to detection of a radio link failure in the MCG or MCG re - configuration synchronization failure or failure to move from NR, and 1> If configured attemptCondReconfig ; and 1> If the selected cell is not configured with CondEventT1 , or the selected cell is configured with CondEventT1 and the departure condition has not been met yet; and 1 If the selected cell is reconfigurationWithSync included in the VarConditionalReconfig in the masterCellGroup one of the candidate cells in the MCG 2> If the UE supports RLF - Report for conditional handover, then VarRLF-Report in the choCellIdSet it to the global cell identifier if available, otherwise set it to the physical cell identifier and carrier frequency of the selected cell; 2> Apply the stored one associated with the selected cell condRRCReconfig and perform the actions specified in 5.3.5.3; Remark 1: In the case of CHO-based recovery after handover failure, how to avoid key stream reuse without key change depends on the network implementation 1> Otherwise: 2> If the UE is configured with attemptCondReconfig : 3> Reset the MAC; 3> Release spCellConfig (if configured); 3> Release the MCG SCell (if configured); 3> Release delayBudgetReportingConfig (if configured), and stop timer T342 if it is running; 3> Release overheatingAssistanceConfig (if configured), and stop timer T345 if it is running; 3> If MR-DC is configured: 4> Perform the MR-DC release as specified in clause 5.3.5.10; 3> Release idc-AssistanceConfig (if configured); 3> Release btNameList (if configured); 3> Release wlanNameList (if configured); 3> Release sensorNameList (if configured); 3> Release the drx-PreferenceConfig of the MCG (if configured), and stop the timer T346a associated with the MCG if it is running; 3> Release the maxBW-PreferenceConfig of the MCG (if configured), and stop the timer T346b associated with the MCG if it is running; 3> Release the maxCC-PreferenceConfig of the MCG (if configured), and stop the timer T346c associated with the MCG if it is running; 3> Release the maxMIMO-LayerPreferenceConfig of the MCG (if configured), and stop the timer T346d associated with the MCG if it is running; 3> Release the minSchedulingOffsetPreferenceConfig(if configured), and stop the timer T346e associated with the MCG (if it is running); 3> Release the rlm-RelaxationReportingConfig (if configured), and stop the timer T346j associated with the MCG (if it is running); 3> Release the bfd-RelaxationReportingConfig (if configured), and stop the timer T346k associated with the MCG (if it is running); 3> Release releasePreferenceConfig (if configured), and stop the timer T346f (if it is running); 3> Release onDemandSIB-Request (if configured), and stop the timer T350 (if it is running); 3> Release referenceTimePreferenceReporting (if configured); 3> Release sl-AssistanceConfigNR (if configured); 3> Release obtainCommonLocation (if configured); 3> Release scg-DeactivationPreferenceConfig (if configured), and stop the timer T346i (if it is running); 3> Release musim-GapAssistanceConfig (if configured), and stop the timer T346h (if it is running); 3> Release musim-LeaveAssistanceConfig (if configured); 3> Release propDelayDiffReportConfig (if configured); 3> Release ul-GapFR2-PreferenceConfig (if configured); 3> Release rrm-MeasRelaxationReportingConfig (if configured); 3> Release maxBW-PreferenceConfigFR2-2 (if configured); 3> Release maxMIMO-LayerPreferenceConfigFR2-2 (if configured); 3> Release minSchedulingOffsetPreferenceConfigExt (if configured); 3> Suspend all RB and BH RLC channels of the IAB-MT except SRB0 and the broadcast MRB; 2> Remove all entries (if any) within the MCG VarConditionalReconfig ; 2> For each measId , if the associated reportConfig ofreportType Set to condTriggerConfig : 3> For the associated reportConfigId : 4> Remove the entry with the matching reportConfigId from within the VarMeasConfig ; reportConfigList Remove; 3> If the associated measObjectId is only associated with the reportType set to condTriggerConfig : reportConfig associated: 4> Remove the entry with the matching measObjectId from within the VarMeasConfig ; measObjectList Remove 3> Remove the entry with the matching measId from within the VarMeasConfig ; measIdList Remove; 2> Release the PC5 RLC entity of SL-RLC0 (if any); 2> Start timer T301; 2> Apply the default L1 parameter values specified in the corresponding physical layer specification, except for the parameters that provide values in SIB1 ; 2> Apply the default MAC cell group configuration specified in 9.2.2; 2> Apply the CCCH configuration specified in 9.1.1.2; 2> Apply the SIB1 included in timeAlignmentTimerCommon ; 2> Initiate the transmission of the RRCReestablishmentRequest message according to 5.3.7.4; Remark 2: This procedure also applies if the UE returns to the source PCell.

[0235] After selecting an inter-RAT cell, the UE shall: 1> Perform the actions specified in 5.3.11 when transitioning to RRC_IDLE, where the release cause is "RRC connection failure".

[0236] The present disclosure proposes to release the flightPath - AssistanceConfig configured in operation 1g - 20 when the UE performs operation 1g - 35. Additionally, the present disclosure proposes to stop the timer if the UE is running a timer Txxx with a value of flightPath - AssistanceProhibitTimer configured by the flightPath - AssistanceConfig. For example, the proposed operations can be performed according to the following procedure.

[0237] 1> Ensure having valid and up - to - date basic system information as specified in Clause 5.2.2.2; 1> Stop timer T311; 1> If T390 is running: 2> Stop timer T390 for all access categories; 2> Perform the actions specified in 5.3.14.4; 1> Stop the relay (re) - selection process (if in progress); 1> If cell selection is triggered due to detecting a radio link failure of the MCG or an MCG re - configuration synchronization failure or a failure to move from NR, and 1> If configured attemptCondReconfig ; and 1> If the selected cell is not configured with CondEventT1 , or the selected cell is configured with CondEventT1 and the departure condition has not been met; and 1 If the selected cell is reconfigurationWithSync included in the VarConditionalReconfig in the masterCellGroup one of the candidate cells in the MCG: 2> If the UE supports RLF - Report for conditional handover, set VarRLF-Report in the choCellId to the global cell identity (if available), otherwise set it to the physical cell identity and carrier frequency of the selected cell; 2> Apply the stored condRRCReconfig associated with the selected cell and perform the actions specified in 5.3.5.3; Remark 1: In the case of CHO - based recovery after a handover failure, how to avoid key stream reuse without a key change depends on the network implementation.

[0238] 1> Otherwise: 2> If the UE is configured withattemptCondReconfig : … 3> Release flightPath-AssistanceConfig (if configured), and stop timer Txxx (if it is running); In operation 1g-40, UE 1g-01 may transmit an RRC connection reestablishment request message to base station 1g-02. In response to this message, base station 1g-02 may transmit (operation 1g-45) an RRC connection reestablishment message (RRCReestablishment) to UE. UE 1g-01 that has received the RRC connection reestablishment message may apply this message, transmit (operation 1g-50) an RRC connection reestablishment complete message (RRCReestablishmentComplete) to base station 1g-02 and successfully execute the RRC connection reestablishment process.

[0239] The present disclosure proposes to release the flight path - assistance configuration information (flightPath - AssistanceConfig) configured for UE 1g-01 in operation 1g-20 when or during the execution of the RRC connection reestablishment process. The present disclosure further proposes to stop the timer if UE is running a timer Txxx with a value of flightPath - AssistanceProhibitTimer configured by the flight path - assistance configuration information (flightPath - AssistanceConfig). This is because UE1g-01 performs a cell selection process during the RRC connection reestablishment process, and thus the newly selected cell and base station 1g-02 in operation 1g-20 may be different. For example, for the newly selected cell, flightPath - AssistanceConfig may be configured with another value, or the newly selected cell may not support the configuration of flightPath - AssistanceConfig, so this allows UE to perform subsequent operations according to the configuration of the newly selected cell. If not, then UE may unnecessarily transmit a UE assistance information message, or may transmit a UE assistance information message including incorrect information to the new cell.

[0240] Figure 1H A method for a unmanned aerial vehicle (UAV) UE to manage flight path - assistance configuration information (flightPath - AssistanceConfig) in a next - generation mobile communication system according to an embodiment of the present disclosure is shown.

[0241] Reference Figure 1H , UE 1h-01 may configure an RRC connection with base station 1h-02 and may be in the RRC connected mode (RRC connection) (operation 1h-05).

[0242] In operation 1h-10, a UE 1h-01 in RRC connected mode may transmit a UE capability information message (UECapabilityInformation) including an indicator indicating the ability to report or update flight path information to a base station 1h-01. This may correspond to operation 1f-15 in the above embodiments.

[0243] In operation 1h-20, the base station 1h-02 may configure otherConfig for the UE 1h-01 via a predetermined RRC message. For example, the predetermined RRC message may mean an RRC connection reconfiguration message (RRCReconfiguration) or an RRC resume message (RRCResume). otherConfig may include flight information assistance configuration information (flightPath-AssistanceConfig). This may correspond to operation 1f-20 in the above embodiments.

[0244] In operation 1h-25, the base station 1h-02 may transmit an RRC connection release message (RRCRelease) including suspend configuration information (suspendConfig) to the UE 1h-01. The present disclosure proposes that the UE 1h-01 stores the flight information configuration information configured in operation 1h-02 in the UE inactive AS context. This is to quickly apply and use this information during subsequent RRC connection release procedures.

[0245] In operation 1h-30, the UE 1h-01 may transition to the RRC inactive mode (RRC_INACTIVE).

[0246] In operation 1h-35, the UE 1h-01 in RRC inactive mode may initiate an RRC connection resume procedure. The present disclosure proposes that the UE 1h-01 releases the flight information configuration information stored in the UE inactive AS context during the RRC connection resume procedure. Additionally, the present disclosure proposes that if a timer Txxx is running according to the flight information configuration information, the UE 1h-01 stops the timer. The UE 1h-01 may transmit an RRC connection resume request message (RRCResumeRequest or RRCResumeRequest1) to the base station 1h-02.

[0247] In operation 1h-40, the base station 1h-02 may transmit an RRC connection resume message (RRCResume) to the UE 1h-01.

[0248] In operation 1h-45, the UE 1h-01 may transmit an RRC connection resume complete message (RRCResumeComplete) to the base station 1h-02.

[0249] The present disclosure proposes that the UE 1h-01 stores flight path assistance information (flightPath-AssistanceConfig) in the UE inactive AS context and transitions to the RRC inactive mode, and releases the flight path assistance configuration information stored in the UE inactive AS context by the UE 1h-01 during the RRC connection recovery process (stop the timer if the timer Txxx is running according to it). The present disclosure proposes that the UE 1h-01 releases this information during the RRC connection recovery process, but the UE may not release this information during the RRC connection recovery process according to the indication of the base station 1h-02 (system information or RRC connection release message).

[0250] Figure 1I The process of exchanging flight path information (FlightPathReport) transmitted by an unmanned aerial vehicle (UAV) UE between base stations in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0251] Reference Figure 1I , the UE 1i-01 can configure the RRC connection with the base station 1i-01 and is in the RRC connected mode (RRC connection) (operation 1i-05). In the present disclosure, the base station is referred to as the master node base station (hereinafter referred to as MN).

[0252] In operation 1i-10, if the UE 1i-01 has flight path information (if the UE has available flight path information), the UE 1i-01 can transmit an indicator (flightPathInfoAvailable) indicating the availability of flight path information to the base station 1i-02 through at least one of the following RRC messages.

[0253] - RRC setup complete message (RRCSetupComplete)

[0254] - RRC resume complete message (RRCResumeComplete)

[0255] - RRC reestablishment complete message (RRCReestablishmentComplete)

[0256] - RRC reconfiguration complete message (RRCReconfigurationComplete)

[0257] In operation 1i-11, a UE 1i-01 in RRC connected mode may transmit a UE capability information message (UECapabilityInformation) including an indicator indicating the ability to report or update flight path information to an MN base station 1i-02. This may correspond to operation 1f-15 or 1e-10 in the above embodiments.

[0258] In operation 1i-12, the MN base station 1i-02 may configure otherConfig for the UE 1i-01 via a predetermined RRC message. For example, the predetermined RRC message may mean an RRC connection reconfiguration message (RRCReconfiguration) or an RRC resume message (RRCResume). otherConfig may include flight information assistance configuration information (flightPath-AssistanceConfig). This may correspond to operation 1f-20 in the above embodiments.

[0259] In operation 1i-13, a secondary node (SN) (hereinafter referred to as SN) base station (1i-03) may be added, and dual connectivity (hereinafter referred to as DC) may be configured for the UE 1i-01.

[0260] In operation 1i-15, the MN base station 1i-02 may transmit a UE information request message (UEInformationRequest) to the UE 1i-01. The UE information request message may include flightPathInfoReq information. The flightPathInfoReq information may include at least one of the following pieces of information.

[0261] - includeTimeStamp: Indicates whether the timestamp of each waypoint can be reported in the flight path information report if the timestamp information is available at the UE.

[0262] - maxWayPointNumber: Indicates the maximum number of waypoints that the UE may include in the flight path information report (if this information is available at the UE).

[0263] In operation 1i-20, if the UE information request message received in operation 1i-15 includes flightPathInfoReq information and the UE has flight path information (has available flight path information), then UE 1i-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to MN base station 1i-02. The UE information response message may include one or more WayPointLocation. If includeTimeStamp is set to true, then UE 1i-01 may include in the message information about the time at which the UE intends to reach each waypoint (if includeTimeStamp is set to true, the UE sets the field timeStamp to the time at which the UE intends to reach each waypoint (if such information is available at the UE)).

[0264] In operation 1i-25, MN base station 1i-02 may transmit the flightPathInfoReport received from UE 1i-01 in operation 1i-20 to source SN base station 1i-03. This disclosure proposes that MN base station 1i-02 transmit the flightPathInfoReport retrieved from the UE to source SN base station 1i-03 via a predetermined inter-node message or an Xn message. Source SN base station 1i-03 may select a target SN cell to be changed later, or determine whether to release the current SN base station based on the flightPathInfoReport.

[0265] In operation 1i-30, source SN base station 1i-03 may transmit an SN change request message to MN base station 1i-02 to change the SN base station. For example, the determination to change the SN base station may be performed based on the flightPathInfoReport received in operation 1i-30.

[0266] In operation 1i-35, MN base station 1i-02 may transmit an SN addition request message to target SN base station 1i-04.

[0267] In operation 1i-40, target SN base station 1i-04 may transmit an SN addition request confirmation message including the configuration information required to change the SN base station to MN base station 1i-02.

[0268] In operation 1i-50, UE 1i-01 may change the SN base station to target SN base station 1i-04 by successfully performing an RRC connection reconfiguration procedure. DC is configured for UE 1i-01, MN base station 1i-02, and target SN base station 1i-04.

[0269] Figure 1J The process in which a Unmanned Aerial Vehicle (UAV) UE reports flight path information to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0270] Reference Figure 1J , UE 1j-01 may configure an RRC connection with base station 1j-02 and may be in the RRC connected mode (RRC Connected) (operation 1j-05).

[0271] In operation 1j-10, if UE 1j-01 has flight path information (if the UE has available flight path information), the UE may transmit an indicator (flightPathInfoAvailable) indicating that the flight path information is available to base station 1j-02 via at least one of the following RRC messages.

[0272] - RRC Setup Complete message

[0273] - RRC Resume Complete message

[0274] - RRC Reestablishment Complete message

[0275] - RRC Reconfiguration Complete message

[0276] In operation 1j-15, UE 1j-01 in the RRC connected mode may transmit a UE Capability Information message to base station 1j-2. The UE Capability Information message may include an indicator indicating that flight path information can be reported. This may correspond to operation 1e-10 or 1f-15 in the above embodiment. Additionally, the UE Capability Information message may further include information about the capability to transmit an indicator indicating additional flight path information to be transmitted when reporting the UE information response message including the flight path information.

[0277] In operation 1f-10, if UE 1j-01 has flight path information (if the UE has available flight path information), then UE 1j-01 may transmit an indicator (flightPathInfoAvailable) indicating that the flight path information is available to base station 1f-02 via at least one of the following RRC messages.

[0278] RRC Setup Complete message

[0279] RRC Resume Complete Message (RRCResumeComplete)

[0280] RRC Reestablishment Complete Message (RRCReestablishmentComplete)

[0281] RRC Reconfiguration Complete Message (RRCReconfigurationComplete)

[0282] In operation 1j-20, base station 1j-02 may transmit a UE Information Request message (UEInformationRequest) to UE 1j-01. The UE Information Request message may include flightPathInfoReq information. The flightPathInfoReq information may include at least one of the following pieces of information.

[0283] - includeTimeStamp: Indicates whether the time stamp of each waypoint can be reported in the flight path information report if the time stamp information is available at the UE.

[0284] - maxWayPointNumber: Indicates the maximum number of waypoints that the UE can include in the flight path information report (if this information is available at the UE).

[0285] - includeMoreFlightPath: Is an indicator or information element that indicates whether, if the flight path information cannot be fully stored in the UE Information Response message, the untransmitted flight path information can be transmitted by attaching UE Information Response information.

[0286] In operation 1j-25, if the UE information request message received in operation 1j-20 includes the flightPathInfoReq information and UE 1j-01 has flight path information (if the UE has available flight path information), then UE 1j-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to base station 1j-02. This message may include one or more WayPointLocation. If includeTimeStamp is set to true, then UE 1j-01 may include in this message information about the time at which the UE intends to reach each waypoint (if includeTimeStamp is set to true, the UE sets the field timeStamp to the time at which the UE intends to reach each waypoint (if this information is available at the UE)). The present disclosure proposes that if the flight path information to be transmitted cannot all be stored in the UEInformationResponse message, then only the storable flight path message is included and an indicator is included indicating that there is still flight path information to be transmitted by UE 1j-01 in the UEInformationResponse message. Additionally, if includeMoreFlightPath is configured in operation 1j-20, then UE 1j-01 may subsequently send the remaining flight path information to base station 1j-02 via the UEInformationResponse message or the UE assistance information message. In this case, if the flight path information to be transmitted is no longer available, then the indicator described in operation 1j-25 above may not be included separately, or an indicator indicating that the flight path information to be transmitted is no longer available may be included.

[0287] In operation 1j-30, base station 1j-02 may transmit a UE information request message (UEInformationRequest) to UE 1j-01.

[0288] In operation 1j-35, if the UE information request message received in operation 1j-20 includes the flightPathInfoReq information and UE 1j-01 has flight path information (if the UE has available flight path information), then UE 1j-01 may transmit a UE information response message (UEInformationResponse) including flightPathInfoReport to the base station 1j-02. The UE information response message may include only the flight path information that could not be stored in operation 1j-25. If the UE information response message does not include the flight path information to be transmitted, the indicator described in operation 1j-25 above may not be included separately, or an indicator indicating that the flight path information to be transmitted is no longer available may be included.

[0289] Figure 1K The process of a Unmanned Aerial Vehicle (UAV) UE reporting flight path information to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0290] Reference Figure 1K , UE 1k-01 may configure an RRC connection with the base station 1k-02 and may be in the RRC connected mode (RRC connection) (operation 1k-05).

[0291] In operation 1k-10, if UE 1k-01 has flight path information (if the UE has available flight path information), then the UE may transmit an indicator (flightPathInfoAvailable) indicating the availability of the flight path information to the base station 1k-02 through at least one of the following RRC messages.

[0292] - RRC Setup Complete message (RRCSetupComplete)

[0293] - RRC Resume Complete message (RRCResumeComplete)

[0294] - RRC Reestablishment Complete message (RRCReestablishmentComplete)

[0295] - RRC Reconfiguration Complete message (RRCReconfigurationComplete)

[0296] In operation 1k-15, the UE 1k-10 in the RRC connected mode may transmit a UE capability information message to the base station 1k-02. This may correspond to operations 1j-10, 1e-10, or 1f-15 in the above embodiments. Additionally, the UE capability information message may include capability information related to whether UL DCCH segmentation of the UEInformationResponse message is supported. As a reference, the capability information related to whether UL DCCH segmentation of the UEInformationResponse message is supported may be included in another predetermined UL RRC message.

[0297] In operation 1k-20, the base station 1k-02 may transmit a UE Information Request (UEInformationRequest) to the UE 1k-01. The UE information request message may include flightPathInfoReq information. The flightPathInfoReq information may include at least one of the following pieces of information.

[0298] - includeTimeStamp: Indicates whether the time stamp of each waypoint can be reported in the flight path information report if the time stamp information is available at the UE.

[0299] - maxWayPointNumber: Indicates the maximum number of waypoints that the UE can include in the flight path information report (if this information is available at the UE).

[0300] - rrcSegAllowed: Represents an indicator that indicates that the UE information response message can be segmented and transmitted if the flight path information is not fully stored in it.

[0301] In operation 1k-25, if the UE information request message received in operation 1k-20 includes flightPathInfoReq information and the UE has flight path information, UE 1k-01 may transmit a UE information response (UEInformationResponse) including flightPathInfoReport to base station 1k-02. The UE information response message may include one or more WayPointLocation. If includeTimeStamp is set to true, UE 1j-01 may include in the message information about the time when the UE intends to reach each waypoint (if includeTimeStamp is set to true, the UE sets the field timeStamp to the time when the UE intends to reach each waypoint (if such information is available at the UE)). In the present disclosure, if the flight path information to be transmitted cannot be fully stored in the UEInformationResponse message, UE 1k-01 may transmit the flight path information to base station 1k-02 via ULDedicatedMessageSegment. Specifically, UE 1k-01 may transmit the flight path information to the base station through the following process.

[0302] 5.7.7.2 Initiation

[0303] When the following conditions are met, a UE in RRC connection and capable of UL RRC message segmentation will initiate this process: 1> If based on the received field rrc-SegAllowed to enable RRC message segmentation, and 1> If the encoded RRC message is larger than the maximum supported size of the PDCP SDU specified in TS 38.323 [5]; After initiating this process, the UE shall: 1> Initiate ULDedicatedMessageSegment the transmission of the message, as specified in 5.7.7.3; 5.7.7.3 Actions related to ULDedicatedMessageSegment the transmission of the message The UE shall segment the encoded RRC PDU based on the maximum supported size of the PDCP SDU specified in TS 38.323 [5]. The UE shall minimize the number of segments and set ULDedicatedMessageSegment the content of the message as follows: 1> For each new UL DCCH message, set the segmentNumber of the first message segment to 0 and increment segmentNumber for each subsequent RRC message segment; 1> Setrrc-MessageSegmentContainer configured to include a fragment of a UL DCCH message corresponding to segmentNumber ; 1> If rrc-MessageSegmentContainer the fragment included in is the last fragment of the UL DCCH message: 2> Set rrc-MessageSegmentType to lastSegment; 1> Otherwise: 2> Set rrc-MessageSegmentType to notLastSegment ; 1> Submit all ULDedicatedMessageSegment messages generated for the segmented RRC message to the lower layer for transmission in ascending order based on segmentNumber and end the process.

[0304] Figure 1L is a block diagram showing the structure of a UE according to an embodiment of the present disclosure.

[0305] Referring to the accompanying drawings, the UE may include a radio frequency (RF) processor 1l-10, a baseband processor 1l-20, a storage unit 1l-30, and a controller 1l-40. Of course, the examples given above are not restrictive, and the UE may include fewer or more components than Figure 1L those shown.

[0306] The RF processor 1l-10 may perform functions for transmitting and receiving signals via a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 1l-10 may up-convert the baseband signal provided from the baseband processor 1l-20 to an RF band signal, may transmit the RF band signal through an antenna, and may down-convert the RF band signal received through the antenna to a baseband signal. For example, the RF processor 1l-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although only one antenna is shown in FIG. 1l, the UE may include multiple antennas. In addition, the RF processor 1l-10 may include multiple RF chains. In addition, the RF processor 1l-10 may perform beamforming. To perform beamforming, the RF processor 1l-10 may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processor 1l-10 may perform MIMO and may receive multiple layers when performing MIMO operations.

[0307] The baseband processor 1l-20 can perform the conversion function between baseband signals and bit strings according to the physical layer specifications of the system. For example, during data transmission, the baseband processor 1l-20 can generate complex symbols by encoding and modulating the transmitted bit stream. Additionally, during data reception, the baseband processor 1l-20 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided by the RF processor 1l-10. For example, in the case of applying the orthogonal frequency division multiplexing (OFDM) scheme, during data transmission, the baseband processor 1l-20 can generate complex symbols by encoding and modulating the transmitted bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through inverse fast Fourier transform (IFFT) calculation and cyclic prefix (CP) insertion. Additionally, during data reception, the baseband processor 1l-20 can separate the baseband signal provided by the RF processor 1l-10 at the OFDM symbol level, can recover the signal mapped to subcarriers through fast Fourier transform (FFT) operations, and can recover the received bit string through demodulation and decoding.

[0308] The baseband processor 1l-20 and the RF processor 1l-10 can transmit and receive signals as described above. Therefore, the baseband processor 1l-20 and the RF processor 1l-10 can be referred to as transmitters, receivers, transceivers, or communication units. In addition, at least one of the baseband processor 1l-20 and the RF processor 1l-10 can include multiple communication modules to support multiple different radio access technologies. Additionally, at least one of the baseband processor 1l-20 and the RF processor 1l-10 can include different communication modules to process signals in different frequency bands. For example, different radio access technologies can include wireless LAN (e.g., IEEE802.11), cellular networks (e.g., LTE), etc. Additionally, different frequency bands can include the super high frequency (SHF) (e.g., 2.NRHz) band and the millimeter wave (mmWave) (e.g., 60GHz) band. The UE can transmit / receive signals with the base station by using the baseband processor 1l-20 and the RF processor 1l-10, and the signals can include control information and data.

[0309] The storage unit 1l-30 can store data, such as a basic program for UE operation, an application program, or configuration information. In particular, the storage unit 1l-30 can store information related to a second access node that performs radio communication by using a second radio access technology. Additionally, the storage unit 1l-30 provides the stored data upon a request from the controller 1l-40. The storage unit 1l-30 can be configured by a storage medium (such as ROM, RAM, a hard disk, a CD-ROM, and a DVD) or a combination of storage media. Additionally, the storage unit 1l-30 can be configured by a plurality of memories. According to an embodiment, the storage unit 1l-30 can store a program for performing the method for updating a flight path as described above.

[0310] The controller 1l-40 can control the overall operation of the UE. For example, the controller 1l-40 can transmit / receive signals through the baseband processor 1l-20 and the RF processor 1l-10. Additionally, the controller 1l-40 records data in the storage unit 1l-30 and reads the data from the storage unit 1l-30. To this end, the controller 1l-40 can include at least one processor. For example, the controller 1l-40 can include a communication processor (CP) that performs communication control and an application processor (AP) that controls a higher layer such as an application program. Additionally, at least one component in the UE can be implemented as a single chip. Furthermore, according to an embodiment of the present disclosure, the controller 1l-40 can include a multi-connection processor 1l-45 that performs processing operations in a multi-connection mode.

[0311] According to an embodiment of the present disclosure, the controller 1l-40 can control components of the UE to perform the method for updating a flight path as described above. That is, the corresponding components of the UE can be operated to perform the above-described embodiments of the present disclosure.

[0312] Figure 1M The structure of a base station according to an embodiment of the present disclosure is shown.

[0313] As Figure 1M shown, the base station can include an RF processor 1m-10, a baseband processor 1m-20, a backhaul communication unit 1m-30, a storage unit 1m-40, and a controller 1m-50. Of course, the examples given above are not restrictive, and the base station can include a smaller or larger number of components than Figure 1M shown.

[0314] The RF processor 1m-10 can perform functions for transmitting and receiving signals via a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 1m-10 can up-convert the baseband signal provided from the baseband processor 1m-20 to an RF band signal, can transmit the RF band signal through an antenna, and can down-convert the RF band signal received through the antenna to a baseband signal. For example, the RF processor 1m-10 can include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although only one antenna is shown in the figure, the first access node can include multiple antennas. In addition, the RF processor 1m-10 can include multiple RF chains. Furthermore, the RF processor 1m-10 can perform beamforming. For beamforming, the RF processor 1m-10 can adjust the phase and amplitude of each of the signals transmitted and received through multiple antennas or antenna elements. The RF processor can perform downlink MIMO operations by transmitting one or more layers.

[0315] The baseband processor 1m-20 can perform a conversion function between a baseband signal and a bit string according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor 1m-20 can encode and modulate the transmitted bit string to generate complex symbols. In addition, during data reception, the baseband processor 1m-20 can demodulate and decode the baseband signal provided from the RF processor 1m-10 to recover the received bit string. For example, when following the OFDM scheme, during data transmission, the baseband processor 1j-20 can encode and modulate the transmitted bit string to generate complex symbols, can map the complex symbols to subcarriers, and can configure OFDM symbols through IFFT operations and CP insertion. In addition, during data reception, the baseband processor 1m-20 can separate the baseband signal provided from the RF processor 1m-10 at the OFDM symbol level, can recover the signal mapped to the subcarriers through FFT operations, and can recover the received bit string through demodulation and decoding. The baseband processor 1m-20 and the RF processor 1m-10 can transmit and receive signals as described above. Therefore, the baseband processor 1m-20 and the RF processor 1m-10 can be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The base station can transmit / receive signals with the UE by using the baseband processor 1m-20 and the RF processor 1m-10, and the signals can include control information and data.

[0316] The backhaul communication unit 1m-30 can provide an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1m-30 can convert the bit string transmitted from the master base station to other nodes (e.g., a secondary base station or a core network) into a physical signal, and can convert the physical signal received from other nodes into a bit string.

[0317] The storage unit 1m-40 stores data for the operation of the base station, such as default programs, application programs, and setting information. In particular, the storage unit 1m-40 can store information about the bearers allocated to the connected UEs, measurement results reported from the connected UEs, etc. Additionally, the storage unit 1m-40 can store information used as a reference for determining whether to provide multi-connection to the UE or to suspend the multi-connection. The storage unit 1m-40 can provide the stored data in response to a request from the controller 1m-50. Additionally, the storage unit 1m-40 provides the stored data upon the request of the controller 1m-50. The storage unit 1m-40 can be configured by a storage medium (such as ROM, RAM, hard disk, CD-ROM, and DVD) or a combination of storage media. Additionally, the storage unit 1m-40 can be configured by multiple memories. According to an embodiment, the storage unit 1m-40 can store a program for executing the method for updating the flight path as described above.

[0318] The controller 1m-50 controls the overall operation of the base station. For example, the controller 1m-50 can transmit / receive signals through the baseband processor 1m-20 and the RF processor 1m-10 or through the backhaul communication unit 1m-30. Additionally, the controller 1m-50 records data in the storage unit 1m-40 and reads the data from the storage 1m-40. To this end, the controller 1m-50 can include at least one processor. Additionally, at least one component in the base station can be implemented as a single chip. Additionally, the corresponding components of the base station can be operated to execute the above-described embodiments of the present disclosure.

[0319] The methods disclosed in the claims and / or the methods according to the embodiments described in the specification of the present disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0320] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) can be provided. One or more programs stored in the computer-readable storage medium can be configured to be executed by one or more processors within the electronic device. At least one program includes instructions that cause the electronic device to execute the methods defined by the appended claims and / or according to the various embodiments of the present disclosure disclosed herein.

[0321] These programs (software modules or software) can be stored in non-volatile memories, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disc-ROM (CD-ROM), digital versatile disc (DVD) or other types of optical storage devices, or magnetic tape cartridges. Alternatively, any combination of some or all of them can form the memory in which the programs are stored. Additionally, multiple such memories can be included in the electronic device.

[0322] In addition, the programs can be stored in an attachable storage device, which can access the electronic device through a communication network such as the Internet, intranet, local area network (LAN), wide LAN (WLAN), and storage area network (SAN) or a combination thereof. Such a storage device can access the electronic device via an external port. Additionally, a separate storage device on the communication network can access the portable electronic device.

[0323] In the above detailed embodiments of the present disclosure, according to the presented detailed embodiments, the elements included in the present disclosure are expressed in singular or plural. However, for ease of description, the singular or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to the elements expressed in singular or plural. Therefore, the elements expressed in plural can also include a single element, or the elements expressed in singular can also include multiple elements.

[0324] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes can be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Transmitting a User Assist Information (UAI) message to a base station, the UAI message including information indicating that flight path information is available; Receiving, from the base station, a first message for requesting the flight path information; And Transmitting, to the base station, a second message for reporting the flight path information.

2. The method according to claim 1 further comprises: Transmitting an RRC completion message to the base station, Wherein, based on the information indicating that the flight path information is available, the flight path information is one of initial flight path information and updated flight path information.

3. The method according to claim 1 further comprises: Transmitting terminal capability information to the base station, the terminal capability information indicating whether the terminal is capable of reporting the flight path information by using the UAI message.

4. The method according to claim 1 further comprises: Receiving, from the base station, configuration information, the configuration information including a threshold related to the flight path information, Wherein, the UAI message is transmitted based on a condition related to the threshold.

5. A method performed by a base station in a wireless communication system, the method comprising: Receiving a User Assist Information (UAI) message from a terminal, the UAI message including information indicating that flight path information is available; Transmitting, to the terminal, a first message for requesting the flight path information; And Receiving, from the terminal, a second message for reporting the flight path information.

6. The method according to claim 5 further comprises: Receiving an RRC completion message from the terminal, Wherein, based on the information indicating that the flight path information is available, the flight path information is one of initial flight path information and updated flight path information.

7. The method according to claim 5 further comprises: Receiving terminal capability information from the terminal, the terminal capability information indicating whether the terminal is capable of reporting the flight path information by using the UAI message.

8. The method according to claim 5 further comprises: Transmitting, to the terminal, configuration information, the configuration information including a threshold related to the flight path information, Wherein, the UAI message is received based on a condition related to the threshold.

9. A terminal in a wireless communication system, the terminal comprising: A transceiver; And A controller coupled to the transceiver, Wherein, the controller is configured to: Transmit a User Assist Information (UAI) message to a base station, the UAI message including information indicating that flight path information is available; Receive, from the base station, a first message for requesting the flight path information; And Transmit, to the base station, a second message for reporting the flight path information.

10. The terminal according to claim 9, wherein, The controller is configured to: transmit an RRC completion message to the base station, and Wherein, based on the information indicating that the flight path information is available, the flight path information is one of initial flight path information and updated flight path information.

11. The terminal according to claim 9, wherein, The controller is configured to: transmit terminal capability information to the base station, the terminal capability information indicating whether the terminal is capable of reporting the flight path information by using the UAI message.

12. The terminal according to claim 9, wherein, The controller is configured to: receive, from the base station, configuration information, the configuration information including a threshold related to the flight path information, and Wherein, the UAI message is transmitted based on a condition related to the threshold.

13. A base station in a wireless communication system, the base station comprising: a transceiver; and a controller coupled to the transceiver, wherein the controller is configured to: receive a User Assist Information (UAI) message from a terminal, the UAI message including information indicating that flight path information is available; transmit a first message to the terminal for requesting the flight path information; and receive a second message from the terminal for reporting the flight path information.

14. The base station according to claim 13, wherein, The controller is configured to: receive an RRC completion message from the terminal, and wherein, based on the information indicating that the flight path information is available, the flight path information is one of initial flight path information and updated flight path information.

15. The base station according to claim 13, wherein, The controller is configured to: receive terminal capability information from the terminal, the terminal capability information indicating whether the terminal is capable of reporting the flight path information by using the UAI message; and transmit configuration information to the terminal, the configuration information including a threshold related to the flight path information, and wherein the UAI message is received based on a condition related to the threshold.

Images