Method and apparatus for applying plurality of pieces of altitude-based configuration information in next-generation mobile communication system

The method enables efficient altitude-based measurement reporting in mobile communication systems, addressing interference challenges for UAVs by using altitude thresholds to optimize measurement settings and improve network performance.

WO2024232594A1PCT designated stage expired Publication Date: 2024-11-14SAMSUNG ELECTRONICS CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/005943
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-02
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current mobile communication systems face challenges in efficiently managing altitude-related settings for terminal operations, particularly for uncrewed aerial vehicles (UAVs) that experience high interference from multiple cells, which affects measurement reporting and network performance.

Method used

A method and device that allow terminals to obtain and report altitude-based measurement setting information, using altitude thresholds to determine when to trigger measurement reports, enhancing measurement efficiency and network optimization.

Benefits of technology

This approach improves measurement reporting accuracy and efficiency by tailoring measurement settings to the UAV's altitude, reducing interference and enhancing network performance in altitude-dependent scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024005943_14112024_PF_FP_ABST
    Figure KR2024005943_14112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to one embodiment, a method performed by means of a terminal of a wireless communication system may comprise the steps of: acquiring, from a base station, measurement configuration information including altitude-related information; measuring at least one cell with respect to at least one altitude on the basis of the altitude-related information; and reporting a measurement result for the at least one cell to the base station on the basis of the altitude-related information, wherein the altitude-related information includes at least one altitude threshold value for determining whether to trigger a report for the at least one measurement result.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for applying multiple configuration information based on altitude in next-generation mobile communication system

[0001] The present disclosure relates to the operation of a mobile communication system terminal and base station. More specifically, it relates to a method and device for applying multiple configuration information based on the altitude of a terminal.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave), such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] An object of the present invention is to propose a method for efficiently performing and reporting measurements by setting parameters based on the altitude of a terminal.

[0009] The technical problems to be achieved in the embodiments of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0010] According to one embodiment of the present disclosure, a method performed by a terminal of a wireless communication system comprises the steps of: obtaining measurement configuration information including altitude-related information from a base station; performing measurement on at least one cell for at least one altitude based on the altitude-related information; and reporting a measurement result on the at least one cell to the base station based on the altitude-related information, wherein the altitude-related information includes at least one altitude threshold value for determining whether to trigger a report on the at least one measurement result.

[0011] According to another embodiment of the present disclosure, a method performed by a base station of a wireless communication system, comprising: transmitting, to a terminal, measurement configuration information including altitude-related information; and receiving, from the terminal, a measurement result for at least one cell measured based on the altitude-related information, wherein the altitude-related information includes at least one altitude threshold value related to whether to trigger a report for the at least one measurement result. According to another embodiment of the present disclosure, a terminal of a wireless communication system, comprising: a transceiver for transmitting and receiving signals; and a control unit, wherein the control unit obtains, from a base station, measurement configuration information including altitude-related information, performs measurement for at least one cell for at least one altitude based on the altitude-related information, and reports the measurement result for the at least one cell to the base station based on the altitude-related information, wherein the altitude-related information includes at least one altitude threshold value for determining whether to trigger a report for the at least one measurement result.

[0012] According to another embodiment of the present disclosure, a base station of a wireless communication system comprises a transceiver for transmitting and receiving signals; and a control unit, wherein the control unit transmits measurement setting information including altitude-related information to a terminal, and receives, from the terminal, measurement results for at least one cell measured based on the altitude-related information, wherein the altitude-related information includes at least one altitude threshold value related to whether to trigger a report for the at least one measurement result.

[0013] According to one embodiment of the present disclosure, measurements can be performed and reported efficiently by setting parameters based on the altitude of the terminal.

[0014] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0015] FIG. 1a is a diagram illustrating the structure of a long term evolution (LTE) system according to one embodiment of the present disclosure.

[0016] FIG. 1b is a diagram illustrating a wireless protocol structure in a long term evolution (LTE) system according to an embodiment of the present disclosure.

[0017] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0018] FIG. 1d is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0019] FIG. 1e is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0020] FIG. 1f is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0021] FIG. 1g is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0022] FIG. 1h is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0023] FIG. 1i is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0024] FIG. 1j is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0025] FIG. 1k is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0026] FIG. 1l is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.

[0027] FIG. 1m is a block diagram illustrating the internal structure of a base station according to one embodiment of the present disclosure.

[0028] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0029] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0030] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0031] For convenience of explanation, the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE standard. However, the present invention is not limited to these terms and names and can be equally applied to systems conforming to other standards. In the present invention, the term "eNB" may be used interchangeably with "gNB" for convenience of explanation. In other words, a base station described as an eNB may also represent a gNB.

[0032] It will be appreciated that each block of the processing flowchart drawings and combinations of the flowchart drawings in the present disclosure can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, such that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, such that the instructions stored in the computer-available or computer-readable memory can also produce an article of manufacture that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0033] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0034] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0035] In this disclosure, phrases such as “A and / or B,” “A or B,” “at least one of and B,” “or at least one of B,” “B or C,” “at least one of B and C,” and “at least one of B or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0036] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 described below may mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs in a 5G core network (CN).

[0037] FIG. 1a is a diagram illustrating the structure of a long term evolution (LTE) system according to one embodiment of the present disclosure.

[0038] Referring to FIG. 1a, as illustrated, the wireless access network of the LTE system is composed of next-generation base stations (Evolved Node Bs, hereinafter referred to as ENBs, Node Bs or base stations) (1a-05, 1a-10, 1a-15, 1a-20), an MME (1a-25, Mobility Management Entity) and an S-GW (1a-30, Serving-Gateway). A user equipment (UE or terminal) (1a-35) accesses an external network through the ENBs (1a-05 to 1a-20) and the S-GW (1a-30).

[0039] In Fig. 1a, ENBs (1a-05, 1a-10, 1a-15, 1a-20) correspond to existing Node Bs of a UMTS system. ENBs are connected to UEs (1a-35) via a wireless channel and perform a more complex role than existing Node Bs.

[0040] In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via Internet Protocol, is serviced through a shared channel. Therefore, a device is required to collect status information such as buffer status, available transmission power status, and channel status of UEs and perform scheduling. This is handled by ENB (1a-05, 1a-10, 1a-15, 1a-20).

[0041] A single ENB typically controls multiple cells. For example, to achieve a transmission rate of 100 Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth. It also employs adaptive modulation and coding (AMC), which determines the modulation scheme and channel coding rate based on the channel conditions of the terminal.

[0042] The S-GW (1a-30) is a device that provides data bearers and creates or removes them under the control of the MME (1a-25). The MME is responsible for various control functions as well as mobility management for terminals and is connected to multiple base stations.

[0043] FIG. 1b is a diagram illustrating a wireless protocol structure in a long term evolution (LTE) system according to an embodiment of the present disclosure.

[0044] Referring to Figure 1b, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), and MAC (Medium Access Control 1b-15, 1b-30) in the terminal and ENB, respectively. PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.

[0045] - Header compression and decompression (ROHC only)

[0046] - User data transfer function

[0047] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

[0048] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0049] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0050] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0051] - Encryption and decryption functions (Ciphering and deciphering)

[0052] - Timer-based SDU discard in uplink.

[0053] Radio Link Control (RLC) (1b-10, 1b-35) reconfigures PDCP PDUs (Packet Data Units) to an appropriate size and performs ARQ operations, etc. The main functions of RLC are summarized as follows.

[0054] - Data transfer function (Transfer of upper layer PDUs)

[0055] - ARQ function (Error Correction through ARQ (only for AM data transfer))

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

[0057] - Re-segmentation of RLC data PDUs (only for AM data transfer)

[0058] - Reordering of RLC data PDUs (only for UM and AM data transfer)

[0059] - Duplicate detection (only for UM and AM data transfer)

[0060] - Error detection function (Protocol error detection (only for AM data transfer))

[0061] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0062] - RLC re-establishment function

[0063] MAC (1b-15, 1b-30) connects to multiple RLC layer devices configured in a single terminal, and multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

[0064] - Mapping function (Mapping between logical channels and transport channels)

[0065] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)

[0066] - Scheduling information reporting function

[0067] - HARQ function (Error correction through HARQ)

[0068] - Priority handling between logical channels of one UE

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

[0070] - MBMS service identification function

[0071] - Transport format selection function

[0072] - Padding function

[0073] The physical layer (1b-20, 1b-25) performs the operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to the upper layer.

[0074] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0075] Referring to FIG. 1c, as illustrated, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 2g) is composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (1c-10) and an NR CN (1c-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (1c-15) accesses an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0076] In Fig. 1c, the NR gNB (1c-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (1c-15) via a wireless channel and can provide a service superior to that of the existing Node B. In the next-generation mobile communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and the NR NB (1c-10) is responsible for this.

[0077] A single NR gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to current LTE, it can exceed the existing maximum bandwidth and utilize Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology, with additional beamforming technology. Furthermore, Adaptive Modulation & Coding (AMC), which determines the modulation scheme and channel coding rate based on the terminal's channel conditions, is applied.

[0078] The NR CN (1c-05) performs functions such as mobility support, bearer setup, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management for terminals and is connected to multiple base stations. Furthermore, the next-generation mobile communication system can also be interoperable with the existing LTE system, and the NR CN is connected to the MME (1c-25) via a network interface. The MME is connected to the existing base station, the eNB (1c-30).

[0079] FIG. 1d is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0080] Referring to FIG. 1d, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (NR Service Data Adaptation Protocol, 1d-01, 1d-45), NR PDCP (NR Packet Data Convergence Protocol, 1d-05, 1d-40), NR RLC (NR Radio link control, 1d-10, 1d-35), and NR MAC (NR Medium Access Control, 1d-15, 1d-30) in the terminal and the NR base station, respectively.

[0081] Key features of NR SDAP (1d-01, 1d-45) may include some of the following:

[0082] - Transfer of user plane data

[0083] - Mapping function between QoS flow and data bearer for both DL and UL

[0084] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0085] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0086] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can be instructed to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink with the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

[0087] The main functions of NR PDCP (1d-05, 1d-40) may include some of the following functions:

[0088] - Header compression and decompression (ROHC only)

[0089] - User data transfer function

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

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

[0092] - PDCP PDU reordering for reception

[0093] - Duplicate detection of lower layer SDUs

[0094] - Retransmission function (Retransmission of PDCP SDUs)

[0095] - Encryption and decryption functions (Ciphering and deciphering)

[0096] - Timer-based SDU discard in uplink.

[0097] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or may include a function of transmitting data directly without considering the order, may include a function of recording lost PDCP PDUs by reordering the order, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

[0098] The main features of NR RLC(1d-10, 1d-35) may include some of the following:

[0099] - Data transfer function (Transfer of upper layer PDUs)

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

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

[0102] - ARQ function (Error Correction through ARQ)

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

[0104] - Re-segmentation of RLC data PDUs

[0105] - Reordering of RLC data PDUs

[0106] - Duplicate detection function

[0107] - Protocol error detection

[0108] - RLC SDU discard function

[0109] - RLC re-establishment function

[0110] The in-sequence delivery function of the NR RLC device above refers to the function of sequentially transmitting RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and transmitting RLC SDUs when an RLC SDU is originally received divided into multiple RLC SDUs, may include a function of reordering received RLC PDUs based on RLC SN (sequence number) or PDCP SN (sequence number), may include a function of recording lost RLC PDUs by reordering the sequence, may include a function of reporting the status of lost RLC PDUs to the transmitting side, may include a function of requesting retransmission of lost RLC PDUs, may include a function of sequentially transmitting only RLC SDUs up to the lost RLC SDU to an upper layer when there is a lost RLC SDU, or may include a function of sequentially transmitting all RLC SDUs received before the timer starts when a predetermined timer expires even when there is a lost RLC SDU. Or, even if there are lost RLC SDUs, if a predetermined timer has expired, it may include a function to sequentially deliver all RLC SDUs received up to the upper layer. In addition, the RLC PDUs may be processed in the order they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of sequence (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and then delivered to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0111] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0112] NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

[0113] - Mapping function (Mapping between logical channels and transport channels)

[0114] - Multiplexing / demultiplexing of MAC SDUs

[0115] - Scheduling information reporting function

[0116] - HARQ function (Error correction through HARQ)

[0117] - Priority handling between logical channels of one UE

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

[0119] - MBMS service identification function

[0120] - Transport format selection function

[0121] - Padding function

[0122] The NR PHY layer (1d-20, 1d-25) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0123] FIG. 1e is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0124] An Uncrewed Aerial Vehicle (UAV) terminal can refer to a terminal capable of flight. Therefore, a UAV terminal can have a higher probability of line of sight (LOS) than a terrestrial UE.

[0125] Therefore, UAV terminals may suffer from downlink (DL) interference from more cells than ground terminals. In other words, UAV terminals are characterized by receiving higher levels of DL interference from more surrounding cells than ground terminals. Similarly, UAV terminals are characterized by causing uplink (UL) interference from more cells than ground terminals.

[0126] In this disclosure, a method for reporting a MeasurementReport to a base station according to the above UAV terminal characteristics is proposed.

[0127] Referring to FIG. 1e, at step 1e-05, a UAV terminal (UAV UE, 1e-01) may establish a radio resource control (RRC) connection with an NR base station (gNB, 1e-02) and be in RRC connected mode (RRC_CONNECTED).

[0128] At step 1e-10, the UAV terminal (1e-01) can report the terminal's capabilities to the base station (1e-02).

[0129] For example, the UAV terminal (1e-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1e-02). The terminal capability information message may include an indicator (heightMeas) indicating whether the terminal supports Event H1 / H2.

[0130] At step 1e-15, the base station (1e-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1e-01).

[0131] For example, the above measurement configuration information (MeasConfig) may include measurement object configuration information (MeasObjectToAddModList) for objects on which the terminal (1e-01) performs measurement, report configuration information (ReportConfigToAddModList), measurement identifier configuration information (MeasIdToAddModList) that identifies a measurement configuration by linking one report configuration and one measurement object configuration information, and measurement quantity configuration information (QuantityConfig) that contains measurement quantities and layer 3 filtering coefficients for measurements.

[0132] The above MeasConfig can have the following ASN.1 (Abstract Syntax Notation number One) structure.

[0133]

[0134] The above MeasObjectToAddModList can store MeasObjectNR, and MeasObjectNR can have the following ASN.1 structure.

[0135]

[0136]

[0137]

[0138]

[0139] The above ReportConfigToAddModList can store ReportConfigNR, and ReportConfigNR can have the following ASN.1 structure.

[0140]

[0141]

[0142]

[0143]

[0144]

[0145]

[0146]

[0147]

[0148] For convenience of explanation, the present disclosure will be described based on the assumption that the reportType of the ReportConfigNR is set to eventTriggered and the eventId of the EventTriggerConfig contained in eventTriggered is set to eventA4. However, this is for convenience of explanation, and the scope of the present invention is not limited thereto. For example, the following description can be equally applied to other event conditions (e.g., eventA3, condEventA3, condEventA4, eventA5, condEventA5).

[0149] Event A4 refers to an event in which a neighbor cell becomes better than a threshold, and the specific details may be as follows. For reference, in the present disclosure, a single a4-Threshold may be set for the Event A4, and the MeasTriggerQuantity set as the a4-Threshold may include one of rsrp (RSRP-Range), rsrq (RSRQ-Range), and sinr (SINR-Range).

[0150] 5.5.4.5 Event A4 (Neighbor becomes better than threshold)

[0151] The UE shall:

[0152] 1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;

[0153] 1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled.

[0154] Inequality A4-1 (Entering condition)

[0155] Mn + Ofn + Ocn - Hys > Thresh

[0156] Inequality A4-2 (Leaving condition)

[0157] Mn + Ofn + Ocn + Hys < Thresh

[0158] The variables in the formula are defined as follows:

[0159] Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

[0160] Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

[0161] Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

[0162] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

[0163] Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event).

[0164] Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0165] Ofn, Ocn, Hys are expressed in dB.

[0166] Thresh is expressed in the same unit as Mn.

[0167] NOTE: The definition of Event A4 also applies to CondEvent A4.

[0168] 1e-20 단계에서, 상기 단말(1e-01)은 1e-15 단계에서 수신한 측정 설정 정보에 기반하여 측정을 수행할 수 있다. (Preform measurements based on the received MeasConfig)

[0169] 이 때, 상기 단말(1e-01)이 Layer 3 필터링을 수행하는 방법은 하기와 같다.

[0170] 5.5.3.2 Layer 3 filtering

[0171] The UE shall:

[0172] 1> for each cell measurement quantity, each beam measurement quantity, each sidelink measurement quantity as needed in clause 5.8.10, for each CLI measurement quantity that the UE performs measurements according to 5.5.3.1, and for each candidate L2 U2N Relay UE measurement quantity according to 5.5.3.4:

[0173] 2> filter the measured result, before using for evaluation of reporting criteria or for measurement reporting, by the following formula:

[0174]

[0175] where

[0176] is the latest received measurement result from the physical layer;

[0177] is the updated filtered measurement result, that is used for evaluation of reporting criteria or for measurement reporting;

[0178] is the old filtered measurement result, where is set to when the first measurement result from the physical layer is received; and for MeasObjectNR, a = 1 / 2 (ki / 4) , where k i is the filterCoefficient for the corresponding measurement quantity of the i:th QuantityConfigNR in quantityConfigNR-List, and i is indicated by quantityConfigIndex in MeasObjectNR; for other measurements, a = 1 / 2 (k / 4) , where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig; for UTRA-FDD, a = 1 / 2 (k / 4), where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfigUTRA-FDD in the QuantityConfig;

[0179] 2> adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing that the filterCoefficient k assumes a sample rate equal to X ms; The value of X is equivalent to one intra-frequency L1 measurement period as defined in TS 38.133

[0014] assuming non-DRX operation, and depends on frequency range.

[0180] 상기 단말(1e-01)은 하기 절차에 따라 Later 3 필터링된 셀 측정 결과와 Layer 3 필터링된 빔 측정 결과를 각각 도출할 수 있다.

[0181] 5.5.3.3 Derivation of cell measurement results

[0182] The network may configure the UE in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS / PBCH block or CSI-RS).

[0183] The UE shall:

[0184] 1> for each cell measurement quantity to be derived based on SS / PBCH block:

[0185] 2> if nrofSS-BlocksToAverage is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE / RRC_INACTIVE; or

[0186] 2> if absThreshSS-BlocksConsolidation is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE / RRC_INACTIVE; or

[0187] 2> if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:

[0188] 3> derive each cell measurement quantity based on SS / PBCH block as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9];

[0189] 2> else:

[0190] 3> derive each cell measurement quantity based on SS / PBCH block as the linear power scale average of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation where the total number of averaged beams shall not exceed nrofSS-BlocksToAverage, and where each beam measurement quantity is described in TS 38.215 [9];

[0191] 2> if in RRC_CONNECTED, apply layer 3 cell filtering as described in 5.5.3.2;

[0192] 1> for each cell measurement quantity to be derived based on CSI-RS:

[0193] 2> consider a CSI-RS resource to be applicable for deriving cell measurements when the concerned CSI-RS resource is included in the csi-rs-CellMobility including the physCellId of the cell in theCSI-RS-ResourceConfigMobility in the associated measObject;

[0194] 2> if nrofCSI-RS-ResourcesToAverage in the associated measObject is not configured; or

[0195] 2> if absThreshCSI-RS-Consolidation in the associated measObject is not configured; or

[0196] 2> if the highest beam measurement quantity value is below or equal to absThreshCSI-RS-Consolidation:

[0197] 3> derive each cell measurement quantity based on applicable CSI-RS resources for the cell as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9];

[0198] 2> else:

[0199] 3> derive each cell measurement quantity based on CSI-RS as the linear power scale average of the highest beam measurement quantity values above absThreshCSI-RS-Consolidation where the total number of averaged beams shall not exceed nrofCSI-RS-ResourcesToAverage;

[0200] 2> apply layer 3 cell filtering as described in 5.5.3.2.

[0201] 5.5.3.3a Derivation of layer 3 beam filtered measurement

[0202] The UE shall:

[0203] 1> for each layer 3 beam filtered measurement quantity to be derived based on SS / PBCH block;

[0204] 2> derive each configured beam measurement quantity based on SS / PBCH block as described in TS 38.215[9], and apply layer 3 beam filtering as described in 5.5.3.2;

[0205] 1> for each layer 3 beam filtered measurement quantity to be derived based on CSI-RS;

[0206] 2> derive each configured beam measurement quantity based on CSI-RS as described in TS 38.215 [9], and apply layer 3 beam filtering as described in 5.5.3.2.

[0207] At step 1e-25, the terminal (1e-01) can determine whether a measurement report should be triggered based on the measurement configuration information received at step 1e-15. (Determine whether measurement reporting for a configured event is triggered or not)

[0208] First, the terminal (1e-01) can determine the cells applicable to eventA4 as follows depending on whether useAllowedCellList is set to true in eventA4.

[0209] - If useAllowedCellList is set to true, the terminal may consider any neighboring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is included in the allowedCellsToAddModList defined within the VarMeasConfig for this measId.

[0210] - If useAllowedCellList is not set to true (else), the terminal may consider any neighboring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId, unless the measId is included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId.

[0211] And, the terminal can determine whether the eventA4 described above in step 1e-15 has the first cell that satisfies the following entry condition.

[0212] - If the reportType is set to eventTriggered and the entry condition of eventA4 is satisfied, that is, the eventId of reportConfig within VarMeasConfig is eventA4, and all measurements that have performed layer 3 filtering on one or more cells applied to the eventA4 satisfy the entering condition described above in step 1e-15 during the timeToTrigger defined in the event, and the VarMeasReportList does not include the measId associated with the event (measId means an identifier that connects the reporting configuration and the measurement object, and here means the measId that connects the reportConfig and the MeasObjectNR mapped to it) (if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event))

[0213] 상기 조건이 충족하는 경우, 상기 단말(1e-01)은 하기 절차를 수행할 수 있다.

[0214] - include a measurement reporting entry within the VarMeasReportList for this measId;

[0215] - set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

[0216] - include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0217] - if useT312 is set to true in reportConfig for this event:

[0218] ■ if T310 for the corresponding SpCell is running; and

[0219] ■ if T312 is not running for corresponding SpCell:

[0220] ◆ start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

[0221] - initiate the measurement reporting procedure, as specified in 1e-30;

[0222] Alternatively, the terminal (1e-01) can determine whether there is a subsequent cell that satisfies the entry condition described above in step 1e-15.

[0223] - If the reportType is set to eventTriggered and the entry condition of eventA4 is satisfied, i.e., the eventId of the reportConfig within VarMeasConfig is eventA4, and all measurements that have performed layer 3 filtering for one or more applicable cells not included in the cellsTriggeredList satisfy the entering condition described above in step 1e-15 during the timeToTrigger defined in the event (else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e., the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event))

[0224] If the above conditions are met, the terminal can perform the following procedures.

[0225] - set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

[0226] - include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0227] - if useT312 is set to true in reportConfig for this event:

[0228] ■ if T310 for the corresponding SpCell is running; and

[0229] ■ if T312 is not running for corresponding SpCell:

[0230] ◆ start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

[0231] - initiate the measurement reporting procedure, as specified in 1e-30;

[0232] Alternatively, the terminal (1e-01) can determine whether there are cells that satisfy the leaving condition described above in step 1e-15.

[0233] - If the reportType is set to eventTriggered and the leaving condition of eventA4 is satisfied, that is, if the eventId of reportConfig in VarMeasConfig is eventA4 and all measurements for which layer 3 filtering was performed for one or more applicable cells included in cellsTriggeredList satisfy the leaving condition described above in step 1e-15 during the timeToTrigger defined in the event (if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event)

[0234] If the above conditions are met, the terminal (1e-01) can perform the following procedure.

[0235] - remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0236] - if reportOnLeave is set to true for the corresponding reporting configuration:

[0237] ■ initiate the measurement reporting procedure, as specified in 1e-30;

[0238] - if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

[0239] ■ remove the measurement reporting entry within the VarMeasReportList for this measId;

[0240] ■ stop the periodic reporting timer for this measId, if running;

[0241] At step 1e-30, the terminal (1e-01) can report the measurement results to the base station (1e-02).

[0242] Specifically, when the measurement report procedure is initiated at step 1e-25, the terminal (1e-01) can transmit a measurement result message (MeasurementReport) to the base station (1e-02) according to the following procedure.

[0243] For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

[0244] 1> set the measId to the measurement identity that triggered the measurement reporting;

[0245] 1> for each serving cell configured with servingCellMO:

[0246] 2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0247] 3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available:

[0248] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0249] 2> else:

[0250] 3> if SSB based serving cell measurements are available:

[0251] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0252] 3> else if CSI-RS based serving cell measurements are available:

[0253] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0254] 1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any;

[0255] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0256] 2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0257] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0258] 2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting:

[0259] 3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0260] 4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR;

[0261] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0262] 5> for each best non-serving cell included in the measurement report:

[0263] 6> include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0264] 1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2:

[0265] 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0266] 3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following:

[0267] 4> include carrierFreq of the E-UTRA serving frequency;

[0268] 4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;

[0269] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0270] 5> set the measResultServFreqListEUTRA-SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

[0271] 1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5:

[0272] 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0273] 3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following:

[0274] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0275] 5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG:

[0276] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0277] 4> else:

[0278] 5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0279] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0280] 5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0281] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0282] 4> if results for the serving cell derived based on SSB are included:

[0283] 5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell;

[0284] 4> if results for the serving cell derived based on CSI-RS are included:

[0285] 5> include the refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the MeasObjectNR of the serving cell;

[0286] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0287] 5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0288] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0289] 5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0290] 6> set the measResultNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;

[0291] 7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0292] 8> for each best non-serving cell included in the measurement report:

[0293] 9> include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0294] 1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report:

[0295] 2> if the reportType is set to eventTriggered or periodical:

[0296] 3> perform as follows:

[0297] 4> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

[0298] 5> if the reportType is set to eventTriggered and eventId is not set to eventD1:

[0299] 6> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

[0300] 5> else:

[0301] 6> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0302] 5> for each cell that is included in the measResultNeighCells, include the physCellId;

[0303] 5> if the reportType is set to eventTriggered or periodical:

[0304] 6> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

[0305] 7> if the measObject associated with this measId concerns NR:

[0306] 8> if rsType in the associated reportConfig is set to ssb:

[0307] 9> set resultsSSB-Cell within the measResult to include the SS / PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0308] 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

[0309] 8> else if rsType in the associated reportConfig is set to csi-rs:

[0310] 9> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0311] 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

[0312] 1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

[0313] 1> stop the periodical reporting timer, if running;

[0314] 1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

[0315] 2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

[0316] 1> else:

[0317] 2> if the reportType is set to periodical or cli-Periodical or rxTxPeriodical:

[0318] 3> remove the entry within the VarMeasReportList for this measId;

[0319] 3> remove this measId from the measIdList within VarMeasConfig;

[0320] 1> else if the UE is in (NG)EN-DC:

[0321] 2> if SRB3 is configured and the SCG is not deactivated:

[0322] 3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0323] 2> else:

[0324] 3> submit the MeasurementReport message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331

[0010] .

[0325] 1> else if the UE is in NR-DC:

[0326] 2> if the measurement configuration that triggered this measurement report is associated with the SCG:

[0327] 3> if SRB3 is configured and the SCG is not deactivated:

[0328] 4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0329] 3> else:

[0330] 4> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;

[0331] 2> else:

[0332] 3> submit the MeasurementReport message via SRB1 to lower layers for transmission, upon which the procedure ends;

[0333] 1> else:

[0334] 2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

[0335] 상기 5.5.5.2 절의 빔 측정 결과는 하기의 절차에 따라 단말이 MeasurementReport에 수납할 수 있다.

[0336] For beam measurement information to be included in a measurement report the UE shall:

[0337] 1> if reportType is set to eventTriggered:

[0338] 2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity;

[0339] 1> set rsIndexResults to include up to maxNrofRS-IndexesToReport SS / PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows:

[0340] 2> if the measurement information to be included is based on SS / PBCH block:

[0341] 3> include within resultsSSB-Indexes the index associated to the best beam for that SS / PBCH block sorting quantity and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;

[0342] 3> if includeBeamMeasurements is set to true, include the SS / PBCH based measurement results for the quantities in reportQuantityRS-Indexes for each SS / PBCH block index;

[0343] 2> else if the beam measurement information to be included is based on CSI-RS:

[0344] 3> include within resultsCSI-RS-Indexes the index associated to the best beam for that CSI-RS sorting quantity and, if absThreshCSI-RS-Consolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshCSI-RS-Consolidation;

[0345] 3> if includeBeamMeasurements is set to true, include the CSI-RS based measurement results for the quantities in reportQuantityRS-Indexes for each CSI-RS index.

[0346] 상기 5.5.5.3 절의 셀 측정 결과는 하기의 절차에 따라 단말이 MeasurementReport에 수납할 수 있다.

[0347] The UE shall determine the sorting quantity according to parameters of the reportConfig associated with the measId that triggered the reporting:

[0348] 1> if the reportType is set to eventTriggered:

[0349] 2> for an NR cell, consider the quantity used in the aN-Threshold (for eventA1, eventA2 and eventA4) or in the a5-Threshold2 (for eventA5) or in the aN-Offset (for eventA3 and eventA6) as the sorting quantity;

[0350] According to one embodiment of the present disclosure, the report configuration information in which eventA4 is set can contain one a4-Threshold.

[0351] FIG. 1f is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0352] An Uncrewed Aerial Vehicle (UAV) terminal can refer to a terminal capable of flight. Therefore, a UAV terminal can have a higher probability of line of sight (LOS) than a terrestrial UE.

[0353] Therefore, UAV terminals may suffer from downlink (DL) interference from more cells than ground terminals. In other words, UAV terminals are characterized by receiving higher levels of DL interference from more surrounding cells than ground terminals. Similarly, UAV terminals are characterized by causing uplink (UL) interference from more cells than ground terminals.

[0354] In this disclosure, a method for reporting a MeasurementReport to a base station according to the above UAV terminal characteristics is proposed.

[0355] Referring to FIG. 1f, in step 1f-05, a UAV terminal (UAV UE, 1f-01) may be in RRC connected mode (RRC_CONNECTED) by establishing a radio resource control (RRC) connection with an NR base station (gNB, 1f-02).

[0356] At step 1f-10, the UAV terminal (1f-01) can report the terminal's capabilities to the base station (1f-02).

[0357] For example, the UAV terminal (1f-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1f-02). The terminal capability information message may follow the above-described embodiment.

[0358] Additionally, the terminal capability information message may include capability information (or an indicator) indicating that the terminal can support / apply specific one or more parameters stored in a single report configuration, including altitude-specific or altitude-range-specific setting values.

[0359] For example, if the a4-Threshold value for each altitude or altitude range is set in one report configuration, the terminal (1f-01) may include terminal capability information indicating that it can support / apply the value of a4-Threshold mapped to a specific altitude or altitude range set by the base station according to the flight altitude of the terminal (1f-01) (for example, the terminal may determine whether eventA4 is triggered by applying a4-Threshold 1 when its flight altitude is at a specific altitude or altitude range set by the base station, and may determine whether eventA4 is triggered by applying a4-Threshold 2 when its flight altitude is at another altitude or another altitude range set by the base station).

[0360] Note that the above terminal capabilities may only be supported if Event H1 / H2 is supported.

[0361] In step 1f-15, the base station (1f-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1f-01).

[0362] This may follow the above-described embodiment. For example, the measurement configuration information (MeasConfig) may include measurement object configuration information (MeasObjectToAddModList) for objects performing measurements, report configuration information (ReportConfigToAddModList), measurement identifier configuration information (MeasIdToAddModList) that identifies a measurement configuration by linking one report configuration and one measurement object configuration information, and measurement quantity configuration information (QuantityConfig) that contains measurement quantities and layer 3 filtering coefficients for measurements.

[0363] Additionally, one report configuration information set by the base station (1f-02) according to one embodiment of the present disclosure to the terminal (1f-01) may include a configuration value for each altitude or altitude range in one or more specific parameters. For example, multiple a4-Thresholds for eventA4 may be set, and each a4-Threshold may have its MeasTriggerQuantity set to match a specific altitude or altitude range.

[0364] A base station (1f-02) according to an embodiment of the present disclosure may set the same type of threshold (Same CHOICE name for the MeasurementTriggerQuantity for each a4-Threshold for a specific height (or height region) i.e. same rsrp or same rsrq or same sinr) even when setting MeasurementTriggerQuantity for each altitude or altitude range.

[0365] This is because when different types of thresholds (different CHOICE name for the MeasurementTriggerQuantity for each a4-Threshold for a specific height (or height region)) are set as a4-Threshold, when the terminal changes its flight altitude and applies a different a4-Threshold from the previously applied a4-Threshold, the terminal must derive new measurement results according to the changed a4-Threshold or manage VarMeasReportList according to the changed a4-Threshold, so the measurement results according to the previously applied a4-Threshold may become meaningless.

[0366] For reference, a new timer may be set in the above measurement configuration information. The terminal (1f-01) may activate the new timer when entering an altitude or altitude range set by the base station (1f-02). When the activated timer expires, the terminal (1f-01) may apply the a4-Threshold associated with the corresponding altitude or altitude range.

[0367] Of course, the terminal (1f-01) can stop the running timer if the flight altitude of the terminal enters the (previous) altitude or altitude range set by the base station before the timer is run, or enters another new altitude or altitude range set by the base station.

[0368] Note that the terminal may not activate the new timer when initially applying the a4-Threshold. Of course, if the terminal enters an altitude or altitude range set by the base station without the timer operating, the terminal may immediately apply the a4-Threshold associated with that altitude or altitude range.

[0369] In step 1f-20, the terminal (1f-01) can perform measurement based on the measurement configuration information (MeasConfig) received in step 1f-15.

[0370] The measurement may follow the above-described embodiment. At this time, the terminal may be measured according to its altitude.

[0371] The above-described embodiment can be applied by applying a4-Threshold mapped to the altitude or altitude range set in step 1f-15.

[0372] In step 1f-25, the terminal (1f-01) can determine whether to trigger a measurement report based on the measurement setting information received in step 1f-20.

[0373] This may follow the aforementioned embodiment. At this time, the terminal may apply the aforementioned embodiment by applying the a4-Threshold mapped to the altitude or altitude range set in step 1f-15 according to its altitude.

[0374] At step 1f-30, the terminal (1f-01) can report the measurement results to the base station (1f-02).

[0375] Specifically, when the measurement report procedure is initiated in step 1f-25, the terminal (1f-01) can transmit a measurement result message (MeasurementReport) to the base station (1f-02) according to the following procedure. This may follow the above-described embodiment.

[0376] At step 1f-35, the terminal (1f-01) can apply a threshold value associated with a new altitude (or altitude range) based on the altitude of the terminal (1f-01).

[0377] For example, when the terminal (1f-01) flies to a (new) altitude different from the altitude at which it was flying in step 1f-20, step 1f-25, or step 1f-30 and enters a new altitude or altitude range set in step 1f-15, it may apply an a4-Threshold different from the a4-Threshold applied in step 1f-20, step 1f-25, or step 1f-30 (i.e., an a4-Threshold mapped to the new altitude or altitude range).

[0378] At this time, the terminal (1f-01) may apply the a4-Threshold mapped to the new altitude or altitude range if at least one of the following is satisfied. Note that the terminal may apply a single a4-Threshold at a given specific time or altitude.

[0379] - When the above terminal (1f-01) enters a new altitude or altitude range set in step 1f-15, the a4-Threshold set by mapping to the new altitude or altitude range can be immediately applied.

[0380] - When the terminal (1f-01) enters a new altitude or altitude range set in step 1f-15, a new timer can be started, and when the started timer expires, the a4-Threshold set by mapping to the new altitude or altitude range can be applied.

[0381] - When the above terminal (1f-01) enters a new altitude or altitude range set in step 1f-15,

[0382] 1) After a certain set period of time has elapsed, or

[0383] 2) After a certain time set by the base station (e.g. TimeToTrigger(TTT)), or

[0384] 3) When the terminal flies at a new altitude or a specific altitude within an altitude range,

[0385] The a4-Threshold set by mapping to the above new altitude or altitude range can be applied.

[0386] The above terminal (1f-01) may enter a new altitude or altitude range, apply the a4-Threshold described above, and perform at least one of the following:

[0387] - Option 1:

[0388] ■ The UE can remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, to the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0389] ■ The terminal can stop the periodic reporting timer, if running, and reset the TTT (TimeToTrigger) for this measId.

[0390] - Option 2:

[0391] ■ The UE may not remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, in the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0392] ■ The UE may not stop the periodic reporting timer if it is running and may not reset the TTT for this measId.

[0393] - Option 3:

[0394] ■ The UE may not remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, in the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0395] ■ The terminal can stop the periodic reporting timer, if running, and reset the TTT (TimeToTrigger) for this measId.

[0396] - Option 4:

[0397] ■ Depending on the base station settings, the terminal can perform one of the above options (Based on network indication, UE performs either Option 1 or 2 or 3)

[0398] The terminal may then determine whether to trigger a measurement report based on the measurement configuration information received in step 1f-20. This may follow step 1f-25.

[0399] At step 1f-40, the terminal (1f-01) can report the measurement results to the base station (1f-02).

[0400] Specifically, when the measurement report procedure is initiated in step 1f-35, the terminal (1f-01) can transmit a measurement result message (MeasurementReport) to the base station (1f-02) according to the following procedure. This may follow the above-described embodiment.

[0401] According to one embodiment of the present disclosure, the report configuration information that sets eventA4 can store a4-Thresholds for each altitude or altitude range, and the terminal can apply a specific a4-Threshold according to its own flight altitude, and at this time, a method of managing measurement result entries, a periodic timer, and TTT is proposed.

[0402] For reference, when a base station according to an embodiment of the present disclosure sets a4-Threshold for each altitude or altitude range, the measurement trigger quantity value (MeasTriggerQuantity) set as a4-Threshold may be set to the same type of value (e.g., MeasTriggerQuantity is set to the same rsrp with only a different RSRP-Range value) for each altitude or altitude range.

[0403] FIG. 1g is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal transmits an event-based measurement result message to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0404] An Uncrewed Aerial Vehicle (UAV) terminal can refer to a terminal capable of flight. Therefore, a UAV terminal can have a higher probability of line of sight (LOS) than a terrestrial UE.

[0405] Therefore, UAV terminals may suffer from downlink (DL) interference from more cells than ground terminals. In other words, UAV terminals are characterized by receiving higher levels of DL interference from more surrounding cells than ground terminals. Similarly, UAV terminals are characterized by causing uplink (UL) interference from more cells than ground terminals.

[0406] In this disclosure, a method for reporting a MeasurementReport to a base station according to the above UAV terminal characteristics is proposed.

[0407] Referring to FIG. 1g, at step 1g-05, a UAV terminal (UAV UE, 1g-01) may be in radio resource control (RRC) connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR base station (gNB, 1g-02).

[0408] At step 1g-10, the UAV terminal (1g-01) can report the terminal's capabilities to the base station (1g-02).

[0409] For example, the UAV terminal (1g-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1g-02). This may follow at least one of the embodiments described above.

[0410] In step 1g-15, the base station (1g-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1g-01).

[0411] This may follow at least one of the embodiments described above. For example, the measurement configuration information (MeasConfig) may include measurement object configuration information (MeasObjectToAddModList) for objects performing measurements, report configuration information (ReportConfigToAddModList), measurement identifier configuration information (MeasIdToAddModList) that identifies a measurement configuration by linking one report configuration and one measurement object configuration information, and measurement quantity configuration information (QuantityConfig) that contains measurement quantities and layer 3 filtering coefficients for measurements.

[0412] Additionally, according to an embodiment of the present disclosure, a single report configuration information set by a base station (1f-02) to the terminal (1f-01) may include a configuration value for each altitude or altitude range in one or more specific parameters. For example, multiple a4-Thresholds may be set for eventA4, and each a4-Threshold may have its MeasTriggerQuantity set to match a specific altitude or altitude range.

[0413] Additionally, even if the base station (1g-02) according to one embodiment of the present disclosure sets MeasurementTriggerQuantity according to altitude or altitude range, each MeasurementTriggerQuantity may be set with a different type of threshold (different CHOICE name for the MeasurementTriggerQuantity for each a4-Threshold for a specific height (or height region) i.e. one for rsrp and the other for rsrq).

[0414] In step 1g-20, the terminal (1g-01) can perform measurement based on the measurement setting information received in step 1g-15. This can follow at least one of the embodiments described above.

[0415] In step 1g-25, the terminal (1g-01) may determine whether to trigger a measurement report based on the measurement configuration information received in step 1g-20. This may follow at least one of the embodiments described above.

[0416] At step 1g-30, the terminal (1g-01) can report the measurement results to the base station (1g-02).

[0417] Specifically, when the measurement report procedure is initiated in step 1g-25, the terminal (1g-01) may transmit a measurement result message (MeasurementReport) to the base station (1g-02) according to the following procedure. This may follow at least one of the embodiments described above.

[0418] At step 1g-35, the terminal (1g-01) can apply a threshold value associated with a new altitude (or altitude range) based on the altitude of the terminal (1g-01).

[0419] For example, when the terminal (1g-01) flies to a (new) altitude different from the altitude at which it was flying in step 1g-20, step 1g-25, or step 1g-30 and enters a new altitude or altitude range set in step 1g-15, it may apply an a4-Threshold different from the a4-Threshold applied in step 1g-20, step 1g-25, or step 1g-30 (i.e., an a4-Threshold mapped to the new altitude or altitude range).

[0420] At this time, the terminal (1g-35) may apply the a4-Threshold mapped to the new altitude or altitude range if at least one of the following is satisfied. Note that the terminal may apply a single a4-Threshold at a given specific time or altitude.

[0421] - When the above terminal (1g-01) enters a new altitude or altitude range set in step 1g-15, the a4-Threshold set by mapping to the new altitude or altitude range can be immediately applied.

[0422] - When the terminal (1g-01) enters a new altitude or altitude range set in step 1g-15, a new timer can be started, and when the started timer expires, the a4-Threshold set by mapping to the new altitude or altitude range can be applied.

[0423] - When the above terminal (1g-01) enters a new altitude or altitude range set in step 1g-15,

[0424] 1) After a certain set period of time has elapsed, or

[0425] 2) After a specific time set by the base station (e.g. TimetoTrigger(TTT)), or

[0426] 3) When the terminal flies at a new altitude or a specific altitude within an altitude range,

[0427] The a4-Threshold set by mapping to the above new altitude or altitude range can be applied.

[0428] The above terminal (1g-01) may enter a new altitude or altitude range, apply the a4-Threshold described above, and perform at least one of the following procedures.

[0429] For reference, the above-described embodiment can be followed when the same type of threshold is set for a4-Threshold. That is, the following description is for the case when a different type of threshold is set for a4-Threshold.

[0430] - Option 1:

[0431] ■ The UE can remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, to the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0432] ■ The terminal can stop the periodic reporting timer, if running, and reset the TTT (TimeToTrigger) for this measId.

[0433] - Option 2:

[0434] ■ The UE can remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, to the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0435] ■ The UE may not stop the periodic reporting timer if it is running and may not reset the TTT for this measId.

[0436] - Option 3:

[0437] ■ Depending on the base station settings, the terminal can perform one of the above options (Based on network indication, UE performs either Option 1 or 2)

[0438] Note that the terminal can keep the periodic timer running and only reset the TTT. In this case, when the periodic timer expires, it may not be restarted unless a subsequent measurement report is triggered. Alternatively, the terminal can reset only the TTT and stop the peridic timer.

[0439] The terminal can then determine whether to trigger a measurement report based on the measurement configuration information received in step 1g-20. This can follow step 1g-25.

[0440] At step 1g-40, the terminal (1g-01) can report the measurement results to the base station (1g-02).

[0441] Specifically, when the measurement report procedure is initiated in step 1g-35, the terminal (1g-01) may transmit a measurement result message (MeasurementReport) to the base station (1g-02) according to the following procedure. This may follow the above-described embodiment.

[0442] According to one embodiment of the present disclosure, the report configuration information that sets eventA4 can store a4-Thresholds for each altitude or altitude range, and the terminal can apply a specific a4-Threshold according to its own flight altitude, and at this time, a method of managing measurement result entries, periodic timer, and TTT is proposed.

[0443] When a base station according to an embodiment of the present disclosure sets a4-Threshold for each altitude or altitude range, the measurement trigger quantity value (MeasTriggerQuantity) set as a4-Threshold may be set to a different type of value (e.g., MeasTriggerQuantity is set to RSRP-Range for one a4-Threshold and MeasurementQuantity is set to RSRQ-Range for another a4-Threshold) for each altitude or altitude range.

[0444] FIG. 1h is a flowchart of a process in which a UAV (Uncrewed Aerial Vehicle) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[0445] A UAV (Uncrewed Aerial Vehicle) terminal can refer to a terminal capable of flight.

[0446] Referring to FIG. 1h, at step 1h-05, a UAV terminal (UAV UE, 1h-01) may establish a radio resource control (RRC) connection with an NR base station (gNB, 1h-02) and be in RRC connected mode (RRC_CONNECTED). At step 1h-10, the UAV terminal (1h-01) may report its capabilities to the base station (1h-02).

[0447] For example, the terminal (1h-01) can transmit a terminal capability information message (UECapabilityInformation) to the base station (1h-02).

[0448] The above terminal capability information message may include whether the measurement reporting configuration supports numberOfTriggeringCells (multipleCellsMeasExtension). The multipleCellsMeasExtension indicates whether the terminal can report a MeasurementReport to the base station by simultaneously determining whether a number of cells (numberOfTriggeringCells) set by the base station, rather than a single cell, satisfy a specific event condition when determining whether the terminal satisfies a specific event condition.

[0449] At step 1h-15, the base station (1h-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1h-01).

[0450] For example, the above measurement configuration information may contain report configuration information (reportConfigToAddModList) containing event triggering conditions.

[0451] ReportConfigToAddModList can consist of one or more ReportConfigToAddMod, and each ReportConfigToAddMod can be configured as follows.

[0452]

[0453]

[0454]

[0455]

[0456]

[0457]

[0458]

[0459]

[0460]

[0461] According to one embodiment of the present disclosure, reportType may be set to eventTriggered, and numberOfTriggeringCells may be included in the predetermined event setting information (e.g., EventA3, EventA4, EventA5, EventB1, EventB2).

[0462] The above numberOfTriggeringCells may mean the number of cells detected that are required to fulfill an event for a measurement report to be triggered.

[0463] For reference, the above event conditions may be as follows:

[0464] 5.5.4.4 Event A3 (Neighbor becomes offset better than SpCell)

[0465] The UE shall:

[0466] 1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;

[0467] 1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;

[0468] 1> use the SpCell for Mp, Ofp and Ocp.

[0469] NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.

[0470] Inequality A3-1 (Entering condition)

[0471] Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

[0472] Inequality A3-2 (Leaving condition)

[0473] Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off

[0474] The variables in the formula are defined as follows:

[0475] Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

[0476] Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

[0477] Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

[0478] Mp is the measurement result of the SpCell, not taking into account any offsets.

[0479] Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).

[0480] Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.

[0481] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

[0482] Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).

[0483] Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0484] Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

[0485] NOTE 2: The definition of Event A3 also applies to CondEvent A3.

[0486] 5.5.4.5 Event A4 (Neighbour becomes better than threshold)

[0487] The UE shall:

[0488] 1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;

[0489] 1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled.

[0490] Inequality A4-1 (Entering condition)

[0491] Mn + Ofn + Ocn - Hys > Thresh

[0492] Inequality A4-2 (Leaving condition)

[0493] Mn + Ofn + Ocn + Hys < Thresh

[0494] The variables in the formula are defined as follows:

[0495] Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

[0496] Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

[0497] Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

[0498] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

[0499] Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event).

[0500] Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0501] Ofn, Ocn, Hys are expressed in dB.

[0502] Thresh is expressed in the same unit as Mn.

[0503] NOTE: The definition of Event A4 also applies to CondEvent A4.

[0504] 5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2)

[0505] The UE shall:

[0506] 1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as specified below, are fulfilled;

[0507] 1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least one of the two, as specified below, is fulfilled;

[0508] 1> use the SpCell for Mp.

[0509] NOTE 1: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.

[0510] Inequality A5-1 (Entering condition 1)

[0511] Mp + Hys < Thresh1

[0512] Inequality A5-2 (Entering condition 2)

[0513] Mn + Ofn + Ocn - Hys > Thresh2

[0514] Inequality A5-3 (Leaving condition 1)

[0515] Mp - Hys > Thresh1

[0516] Inequality A5-4 (Leaving condition 2)

[0517] Mn + Ofn + Ocn + Hys < Thresh2

[0518] The variables in the formula are defined as follows:

[0519] Mp is the measurement result of the NR SpCell, not taking into account any offsets.

[0520] Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

[0521] Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

[0522] Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

[0523] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

[0524] Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event).

[0525] Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR for this event).

[0526] Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0527] Ofn, Ocn, Hys are expressed in dB.

[0528] Thresh1is expressed in the same unit as Mp.

[0529] Thresh2 is expressed in the same unit as Mn.

[0530] NOTE 2: The definition of Event A5 also applies to CondEvent A5.

[0531] 5.5.4.8 Event B1 (Inter RAT neighbour becomes better than threshold)

[0532] The UE shall:

[0533] 1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

[0534] 1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled.

[0535] Inequality B1-1 (Entering condition)

[0536] Mn + Ofn + Ocn - Hys > Thresh

[0537] Inequality B1-2 (Leaving condition)

[0538] Mn + Ofn + Ocn + Hys < Thresh

[0539] The variables in the formula are defined as follows:

[0540] Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.

[0541] Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-RAT cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell).

[0542] Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.

[0543] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

[0544] Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT for this event, b1-ThresholdUTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).

[0545] Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

[0546] Ofn, Ocn, Hys are expressed in dB.

[0547] Thresh is expressed in the same unit as Mn.

[0548] 5.5.4.9 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)

[0549] The UE shall:

[0550] 1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as specified below, are fulfilled;

[0551] 1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled;

[0552] Inequality B2-1 (Entering condition 1)

[0553] Mp + Hys < Thresh1

[0554] Inequality B2-2 (Entering condition 2)

[0555] Mn + Ofn + Ocn - Hys > Thresh2

[0556] Inequality B2-3 (Leaving condition 1)

[0557] Mp - Hys > Thresh1

[0558] Inequality B2-4 (Leaving condition 2)

[0559] Mn + Ofn + Ocn + Hys < Thresh2

[0560] The variables in the formula are defined as follows:

[0561] Mp is the measurement result of the PCell, not taking into account any offsets.

[0562] Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.

[0563] Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the inter-RAT neighbour cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell).

[0564] Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.

[0565] Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

[0566] Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for this event).

[0567] Thresh2 is the threshold parameter for this event (ie b2-Threshold2EUTRA as defined within reportConfigInterRAT for this event, b2-Threshold2UTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).

[0568] Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.

[0569] Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbor cell.

[0570] Ofn, Ocn, Hys are expressed in dB.

[0571] Thresh1 is expressed in the same unit as Mp.

[0572] Thresh2 is expressed in the same unit as Mn.

[0573] In step 1h-20, the terminal (1h-01) can determine whether to trigger a measurement report based on the measurement setting information received in step 1h-15.

[0574] Specifically, the terminal (1h-01) can be determined to trigger a measurement report when at least one of the following conditions is satisfied.

[0575] 2> if the reportType is set to eventTriggered and if the corresponding reportConfig includes numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig:

[0576] 3> If the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

[0577] 4> include a measurement reporting entry within the VarMeasReportList for this measId;

[0578] 3> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

[0579] 4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0580] 3> else:

[0581] 4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0582] 4> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

[0583] 5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

[0584] 5> initiate the measurement reporting procedure, as specified in 1h-25

[0585] 2> if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

[0586] 3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

[0587] 3> if reportOnLeave is set to TRUE for the corresponding reporting configuration and concerned cell(s) in the cellsTriggeredList are removed defined within the VarMeasReportList for this measId;

[0588] 4> initiate the measurement reporting procedure, as specified in 1h-25;

[0589] 3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

[0590] 4> remove the measurement reporting entry within the VarMeasReportList for this measId;

[0591] 4> stop the periodical reporting timer for this measId, if running;

[0592] 1h-25 단계에서, 상기 단말 (1h-01)은 상기 기지국(1h-02)로 측정 결과를 보고 할 수 있다.

[0593] Specifically, if the terminal (1h-01) determines that a measurement report is triggered in step 1h-20, it can transmit a MeasurementReport to the base station (1h-02). The specific procedure for the terminal (1h-01) to transmit a MeasurementReport to the base station (1h-01) may be as follows.

[0594] For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

[0595] 1> set the measId to the measurement identity that triggered the measurement reporting;

[0596] 1> for each serving cell configured with servingCellMO:

[0597] 2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0598] 3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available:

[0599] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0600] 2> else:

[0601] 3> if SSB based serving cell measurements are available:

[0602] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0603] 3> else if CSI-RS based serving cell measurements are available:

[0604] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0605] 1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any;

[0606] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0607] 2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0608] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0609] 2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting:

[0610] 3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0611] 4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR;

[0612] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0613] 5> for each best non-serving cell included in the measurement report:

[0614] 6> include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0615] 1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2:

[0616] 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0617] 3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following:

[0618] 4> include carrierFreq of the E-UTRA serving frequency;

[0619] 4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;

[0620] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0621] 5> set the measResultServFreqListEUTRA-SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

[0622] 1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5:

[0623] 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0624] 3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following:

[0625] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0626] 5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG:

[0627] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0628] 4> else:

[0629] 5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0630] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0631] 5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0632] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0633] 4> if results for the serving cell derived based on SSB are included:

[0634] 5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell;

[0635] 4> if results for the serving cell derived based on CSI-RS are included:

[0636] 5> include the refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the MeasObjectNR of the serving cell;

[0637] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0638] 5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0639] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0640] 5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0641] 6> set the measResultBestNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;

[0642] 7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0643] 8> for each best non-serving cell included in the measurement report:

[0644] 9> include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0645] 1> if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId:

[0646] 2> set the rssi-Result to the linear average of sample value(s) provided by lower layers in the reportInterval;

[0647] 2> set the channelOccupancy to the rounded percentage of sample values which are beyond the channelOccupancyThreshold within all the sample values in the reportInterval;

[0648] 1> if the UE is acting as L2 U2N Remote UE:

[0649] 2> set the sl-MeasResultServingRelay to include the SL-RSRP of the serving L2 U2N Relay UE;

[0650] NOTE 1: In case of no data transmission from L2 U2N Relay UE to L2 U2N Remote UE, it is left to UE implementation whether to use SL-RSRP or SD-RSRP when setting the sl-MeasResultServingRelay of the serving L2 U2N Relay UE.

[0651] 1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report:

[0652] 2> if the reportType is set to eventTriggered or periodical:

[0653] 3> if the measurement report concerns the candidate L2 U2N Relay UE:

[0654] 4> set the sl-MeasResultsCandRelay in measResultNeighCells to include the best candidate L2 U2N Relay UEs up to maxReportCells in accordance with the following:

[0655] 5> if the reportType is set to eventTriggered:

[0656] 6> include the L2 U2N Relay UEs included in the relaysTriggeredList as defined within the VarMeasReportList for this measId;

[0657] 5> else:

[0658] 6> include the applicable L2 U2N Relay UEs for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0659] 5> for each L2 U2N Relay UE that is included in the sl-MeasResultsCandRelay:

[0660] 6> include the sl-RelayUE-Identity;

[0661] 5> for each included L2 U2N Relay UE, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

[0662] 6> set the sl-MeasResult to include the quantity(ies) indicated in the reportQuantityRelay within the concerned reportConfigRelay in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best L2 U2N Relay UE is included first;

[0663] 3> else:

[0664] 4> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

[0665] 5> if the reportType is set to eventTriggered and eventId is not set to eventD1:

[0666] 6> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

[0667] 5> else:

[0668] 6> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0669] 5> for each cell that is included in the measResultNeighCells, include the physCellId;

[0670] 5> if the reportType is set to eventTriggered or periodical:

[0671] 6> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

[0672] 7> if the measObject associated with this measId concerns NR:

[0673] 8> if rsType in the associated reportConfig is set to ssb:

[0674] 9> set resultsSSB-Cell within the measResult to include the SS / PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0675] 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

[0676] 8> else if rsType in the associated reportConfig is set to csi-rs:

[0677] 9> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0678] 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

[0679] 7> if the measObject associated with this measId concerns E-UTRA:

[0680] 8> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0681] 7> if the measObject associated with this measId concerns UTRA-FDD and if ReportConfigInterRAT includes the reportQuantityUTRA-FDD:

[0682] 8> set the measResult to include the quantity(ies) indicated in the reportQuantityUTRA-FDD within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;

[0683] 2> else:

[0684] 3> if the cell indicated by cellForWhichToReportCGI is an NR cell:

[0685] 4> if plmn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained:

[0686] 5> include the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), trackingAreaList (if available), ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the plmn-IdentityInfoList;

[0687] 5> include frequencyBandList if available;

[0688] 5> for each PLMN-IdentityInfo in plmn-IdentityInfoList:

[0689] 6> if the gNB-ID-Length is broadcast:

[0690] 7> include gNB-ID-Length;

[0691] 4> if nr-CGI-Reporting-NPN is supported by the UE and npn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained:

[0692] 5> include the npn-IdentityInfoList including npn-IdentityList, trackingAreaCode, ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the npn-IdentityInfoList;

[0693] 5> for each NPN-IdentityInfo in NPN-IdentityInfoList:

[0694] 6> if the gNB-ID-Length is broadcast:

[0695] 7> include gNB-ID-Length;

[0696] 5> include cellReservedForOtherUse if available;

[0697] 4> else if MIB indicates the SIB1 is not broadcast:

[0698] 5> include the noSIB1 including the ssb-SubcarrierOffset and pdcch-ConfigSIB1 obtained from MIB of the concerned cell;

[0699] 3> if the cell indicated by cellForWhichToReportCGI is an E-UTRA cell:

[0700] 4> if all mandatory fields of the cgi-Info-EPC for the concerned cell have been obtained:

[0701] 5> include in the cgi-Info-EPC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to EPC;

[0702] 4> if the UE is E-UTRA / 5GC capable and all mandatory fields of the cgi-Info-5GC for the concerned cell have been obtained:

[0703] 5> include in the cgi-Info-5GC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to 5GC;

[0704] 4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI in the associated measObject have been obtained:

[0705] 5> include the freqBandIndicator;

[0706] 5> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;

[0707] 5> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;

[0708] 1> if the corresponding measObject concerns NR:

[0709] 2> if the reportSFTD-Meas is set to true within the corresponding reportConfigNR for this measId:

[0710] 3> set the measResultSFTD-NR in accordance with the following:

[0711] 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

[0712] 4> if the reportRSRP is set to true;

[0713] 5> set rsrp-Result to the RSRP of the NR PSCell derived based on SSB;

[0714] 2> else if the reportSFTD-NeighMeas is included within the corresponding reportConfigNR for this measId:

[0715] 3> for each applicable cell which measurement results are available, include an entry in the measResultCellListSFTD-NR and set the contents as follows:

[0716] 4> set physCellId to the physical cell identity of the concerned NR neighbour cell.

[0717] 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

[0718] 4> if the reportRSRP is set to true:

[0719] 5> set rsrp-Result to the RSRP of the concerned cell derived based on SSB;

[0720] 1> else if the corresponding measObject concerns E-UTRA:

[0721] 2> if the reportSFTD-Meas is set to true within the corresponding reportConfigInterRAT for this measId:

[0722] 3> set the measResultSFTD-EUTRA in accordance with the following:

[0723] 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

[0724] 4> if the reportRSRP is set to true;

[0725] 5> set rsrpResult-EUTRA to the RSRP of the EUTRA PSCell;

[0726] 1> if average uplink PDCP delay values are available:

[0727] 2> set the ul-PDCP-DelayValueResultList to include the corresponding average uplink PDCP delay values;

[0728] 1> if PDCP excess delay measurements are available:

[0729] 2> set the ul-PDCP-ExcessDelayResultList to include the corresponding PDCP excess delay measurements;

[0730] 1> if the includeCommonLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of commonLocationInfo of the locationInfo as follows:

[0731] 2> include the locationTimestamp;

[0732] 2> include the locationCoordinate, if available;

[0733] 2> include the velocityEstimate, if available;

[0734] 2> include the locationError, if available;

[0735] 2> include the locationSource, if available;

[0736] 2> if available, include the gnss-TOD-msec,

[0737] 1> if the coarseLocationRequest is set to true in the corresponding reportConfig for this measId:

[0738] 2> if available, include coarseLocationInfo;

[0739] 1> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the wlan-LocationInfo of the locationInfo in the measResults as follows:

[0740] 2> if available, include the LogMeasResultWLAN, in order of decreasing RSSI for WLAN APs;

[0741] 1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the BT-LocationInfo of the locationInfo in the measResults as follows:

[0742] 2> if available, include the LogMeasResultBT, in order of decreasing RSSI for Bluetooth beacons;

[0743] 1> if the includeSensor-Meas is configured in the corresponding reportConfig for this measId, set the sensor-LocationInfo of the locationInfo in the measResults as follows:

[0744] 2> if available, include the sensor-MeasurementInformation;

[0745] 2> if available, include the sensor-MotionInformation;

[0746] 1> if there is at least one applicable transmission resource pool for NR sidelink communication (for measResultsSL):

[0747] 2> set the measResultsListSL to include the CBR measurement results in accordance with the following:

[0748] 3> if the reportType is set to eventTriggered:

[0749] 4> include the transmission resource pools included in the poolsTriggeredList as defined within the VarMeasReportList for this measId;

[0750] 3> else:

[0751] 4> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0752] 3> if the corresponding measObject concerns NR sidelink communication, then for each transmission resource pool to be reported:

[0753] 4> set the sl-poolReportIdentity to the identity of this transmission resource pool;

[0754] 4> set the sl-CBR-ResultsNR to the CBR measurement results on PSSCH and PSCCH of this transmission resource pool provided by lower layers, if available;

[0755] NOTE 1: Void.

[0756] 1> if there is at least one applicable CLI measurement resource to report:

[0757] 2> if the reportType is set to cli-EventTriggered or cli-Periodical:

[0758] 3> set the measResultCLI to include the most interfering SRS resources or most interfering CLI-RSSI resources up to maxReportCLI in accordance with the following:

[0759] 4> if the reportType is set to cli-EventTriggered:

[0760] 5> if trigger quantity is set to srs-RSRP i.e. i1-Threshold is set to srs-RSRP:

[0761] 6> include the SRS resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId;

[0762] 5> if trigger quantity is set to cli-RSSI i.e. i1-Threshold is set to cli-RSSI:

[0763] 6> include the CLI-RSSI resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId;

[0764] 4> else:

[0765] 5> if reportQuantityCLI is set to srs-rsrp:

[0766] 6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0767] 5> else:

[0768] 6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0769] 4> for each SRS resource that is included in the measResultCLI:

[0770] 5> include the srs-ResourceId;

[0771] 5> set srs-RSRP-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first;

[0772] 4> for each CLI-RSSI resource that is included in the measResultCLI:

[0773] 5> include the rssi-ResourceId;

[0774] 5> set cli-RSSI-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering CLI-RSSI resource is included first;

[0775] 1> if there is at least one applicable UE Rx-Tx time difference measurement to report:

[0776] 2> set measResultRxTxTimeDiff to the latest measurement result;

[0777] 1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

[0778] 1> stop the periodical reporting timer, if running;

[0779] 1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

[0780] 2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

[0781] 1> else:

[0782] 2> if the reportType is set to periodical or cli-Periodical or rxTxPeriodical:

[0783] 3> remove the entry within the VarMeasReportList for this measId;

[0784] 3> remove this measId from the measIdList within VarMeasConfig;

[0785] 1> if the measurement reporting was configured by a sl-ConfigDedicatedNR received within the RRCConnectionReconfiguration:

[0786] 2> submit the MeasurementReport message to lower layers for transmission via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified TS 36.331

[0010] , clause 5.6.28;

[0787] 1> else if the UE is in (NG)EN-DC:

[0788] 2> if SRB3 is configured and the SCG is not deactivated:

[0789] 3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0790] 2> else:

[0791] 3> submit the MeasurementReport message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331

[0010] .

[0792] 1> else if the UE is in NR-DC:

[0793] 2> if the measurement configuration that triggered this measurement report is associated with the SCG:

[0794] 3> if SRB3 is configured and the SCG is not deactivated:

[0795] 4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0796] 3> else:

[0797] 4> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;

[0798] 2> else:

[0799] 3> submit the MeasurementReport message via SRB1 to lower layers for transmission, upon which the procedure ends;

[0800] 1> else:

[0801] 2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

[0802] According to one embodiment of the present disclosure, one numberOfTriggeringCells can be set for one report configuration regardless of altitude.

[0803] For reference, embodiments of the present disclosure may be applied simultaneously with at least one of the embodiments described above.

[0804] FIG. 1i is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0805] A UAV (Uncrewed Aerial Vehicle) terminal can refer to a terminal capable of flight.

[0806] Referring to FIG. 1i, at step 1i-05, a UAV terminal (UAV UE, 1i-01) may establish a radio resource control (RRC) connection with an NR base station (gNB, 1i-02) and be in an RRC connected mode (RRC_CONNECTED).

[0807] At step 1i-10, the UAV terminal (1i-01) can report the terminal's capabilities to the base station (1i-02).

[0808] For example, the terminal (1i-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1i-02). This may follow at least one of the embodiments described above.

[0809] Additionally, the terminal capability information message may include capability information (or an indicator) indicating that the terminal can support / apply specific one or more parameters stored in a single report configuration, including altitude-specific or altitude-range-specific setting values.

[0810] For example, if the value of numberOfTriggeringCells for each altitude or altitude range is set in one report configuration, the terminal may include terminal capability information indicating that the terminal can support / apply the value of numberOfTriggeringCells mapped to a specific altitude or altitude range set by the base station according to the terminal's flight altitude (for example, the terminal can determine whether eventA4 is triggered by applying numberOfTriggeringCells1 when its flight altitude is at a specific altitude or a specific altitude range set by the base station, and can determine whether eventA4 is triggered by applying numberOfTriggeringCells1 when its flight altitude is at another altitude or another altitude range set by the base station).

[0811] Note that the above terminal capabilities may only be supported when Event H1 / H2 is supported, multipleCellsMeasExtension is supported, or both Event H1 / H2 and multipleCellsMeasExtension are supported.

[0812] At step 1i-15, the base station (1i-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1i-01).

[0813] This may follow at least one of the embodiments described above.

[0814] Additionally, one report configuration information set by the base station (1i-01) according to one embodiment of the present disclosure to the terminal (1i-01) may include a configuration value for each altitude or altitude range in one or more specific parameters. For example, multiple numberOfTriggeringCells may be set for eventA4, and each numberOfTriggeringCells may be set for a specific altitude or altitude range.

[0815] For reference, a new timer may be set in the above measurement configuration information. The terminal may activate the new timer when entering an altitude or altitude range set by the base station. When the activated timer expires, the terminal may apply the numberOfTriggeringCells associated with the altitude or altitude range. Of course, the terminal may stop the running timer if, while the timer is in operation, the terminal's flight altitude enters the (previous) altitude or altitude range set by the base station before the timer is activated, or if the terminal enters another new altitude or altitude range set by the base station.

[0816] Note that the above terminal may not activate the new timer when first applying numberOfTriggeringCells. Of course, if the terminal enters an altitude or altitude range set by the base station without the timer operating, it may immediately apply numberOfTriggeringCells associated with that altitude or altitude range.

[0817] In step 1i-20, the terminal (1i-01) can determine whether to trigger a measurement report based on the measurement setting information received in step 1i-15.

[0818] At step 1i-25, the terminal (1i-01) can report the measurement results to the base station (1i-02).

[0819] Specifically, if the terminal (1i-01) determines that a measurement report is triggered in step 1i-20, it may transmit a MeasurementReport to the base station (1i-02). This may follow at least one of the embodiments described above.

[0820] At step 1i-30, the terminal (1g-01) may apply numberOfTriggeringCells associated with a new altitude (or altitude range) based on the altitude of the terminal (1g-01).

[0821] For example, when the terminal (1i-01) flies at a (new) altitude different from the altitude at which it was flying in step 1i-20 or 1i-25 and enters a new altitude or altitude range set in step 1i-15, it may apply a numberOfTriggeringCells different from the numberOfTriggeringCells applied in step 1i-20 or 1i-25 (i.e., numberOfTriggeringCells mapped to the new altitude or altitude range). In this case, the terminal may apply the numberOfTriggeringCells mapped to the new altitude or altitude range if at least one of the following is satisfied. For reference, the terminal may apply a single numberOfTriggeringCells at a given specific time or altitude.

[0822] - When the terminal (1i-01) enters a new altitude or altitude range set in step 1i-15, the numberOfTriggeringCells set by mapping the new altitude or altitude range can be applied immediately.

[0823] - When the terminal (1i-01) enters a new altitude or altitude range set in step 1i-15, a new timer is started, and when the started timer expires, the numberOfTriggeringCells set by mapping to the new altitude or altitude range can be applied.

[0824] - When the above terminal (1i-01) enters a new altitude or altitude range set in step 1i-15,

[0825] 1) After a certain set period of time has elapsed, or

[0826] 2) After a specific time set by the base station (e.g. TimetoTrigger(TTT)), or

[0827] 3) When the terminal flies at a new altitude or a specific altitude within an altitude range,

[0828] The numberOfTriggeringCells set can be applied by mapping to the above new altitude or altitude range.

[0829] The above terminal (1i-01) may enter a new altitude or altitude range, apply the above-described numberOfTriggeringCells, and perform at least one of the following:

[0830] - Option 1:

[0831] ■ The UE can remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, to the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0832] ■ The terminal can stop the periodic reporting timer, if running, and reset the TTT (TimeToTrigger) for this measId.

[0833] - Option 2:

[0834] ■ The UE may not remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, in the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0835] ■ The UE may not stop the periodic reporting timer if it is running and may not reset the TTT for this measId.

[0836] - Option 3:

[0837] ■ The UE may not remove the measurement reporting entry for this measId associated with this reportConfigId from the VarMeasReportList, if included, in the reportConfigId (i.e., the reportConfigId for which the above eventA4 is set).

[0838] ■ The terminal can stop the periodic reporting timer, if running, and reset the TTT (TimeToTrigger) for this measId.

[0839] - Option 4:

[0840] ■ Depending on the base station settings, the terminal can perform one of the above options (Based on network indication, UE performs either Option 1 or 2 or 3)

[0841] The terminal can then determine whether to trigger a measurement report based on the measurement configuration information received in step 1i-15. This can follow step 1i-20.

[0842] At step 1i-35, the terminal (1e-01) can report the measurement results to the base station (1e-02).

[0843] Specifically, when the measurement report procedure is initiated in step 1f-30, the terminal (1i-01) can transmit a measurement result message (MeasurementReport) to the base station (1i-02) according to the following procedure. This may follow the embodiment described above.

[0844] According to one embodiment of the present disclosure, the report configuration information that sets a specific event may each store numberOfTriggeringCells by altitude or altitude range, and the terminal may apply a specific numberOfTriggeringCells according to its own flight altitude, and a method of managing measurement result entries, periodic timers, and TTTs is proposed.

[0845] For reference, embodiments of the present disclosure may be applied simultaneously with at least one of the embodiments described above.

[0846] Referring to FIG. 1j, at step 1j-05, a UAV terminal (UAV UE, 1j-01) may establish a radio resource control (RRC) connection with an NR base station (1j-02) and be in RRC connected mode (RRC_CONNECTED).

[0847] A UAV (Uncrewed Aerial Vehicle) terminal can refer to a terminal capable of flight.

[0848] At step 1j-10, the UAV terminal (1j-01) can report the terminal's capabilities to the base station (1j-02).

[0849] For example, the terminal (1j-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1j-02). The message may include an indicator (heightMeas) indicating whether the terminal supports Event H1 / H2.

[0850] In step 1j-15, the base station (1j-02) can transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (1j-01).

[0851] The above measurement configuration information may include the reference altitude threshold (heightThreshRef) of eventH1 and eventH2 of the report configuration information (ReportConfigNR). The altitude threshold may mean one of the integer values, and one integer value may mean a specific altitude.

[0852] For example, a value of 0 could mean -420 m. Note that the altitude can be set based on a specific altitude. For example, it can be expressed as a specific altitude value based on sea level.

[0853] Note that the above reference altitude threshold may be expressed as a range rather than a single value. For example, a value of 0 could represent -420 m to -410 m.

[0854] The above measurement configuration information may include NR report configuration information (reportConfigNR) containing event H1 or event H2 triggering conditions. In the present disclosure, the reportType of the ReportConfigNR is set to eventTriggered, and eventH1 or eventH2 may be newly defined in the corresponding EventTriggerConfig as follows. For reference, the base station may configure one or more ReportConfigNRs for the terminal.

[0855]

[0856]

[0857]

[0858]

[0859]

[0860] The configuration information contained in the above eventH1 or eventH2 is an example, and other integer values ​​may be included. For reference, the measurement configuration information may have the following ASN.1 structure, and the terminal may apply the measurement configuration information received from the base station.

[0861]

[0862] In step 1j-20, the base station (1j-02) can transmit cell group configuration (CellGroupConfig) information to the terminal (1j-01).

[0863] Specifically, the base station (1j-02) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing cell group configuration information (CellGroupConfig) to the terminal (1j-01) to configure one or more Secondary Cells (SCells) and / or Spcell Cells (SpCells). The CellGroupConfig may include configuration information (ServingCellConfig) exclusive to the terminal for each cell, and MeasObjectId may be set in ServingCellMO for each ServingCellConfig.

[0864] Specifically, for each SpCell, MeasObjectId must always be set in ServingCellMO, and for each SCell, the base station may optionally set MeasObjectId in ServingCellMO. Note that steps 1j-20 may be performed together with steps 1j-15, or steps 1j-15 may be performed after steps 1j-20.

[0865] In step 1j-25, the terminal (1j-01) can perform measurement based on the measurement setting information received in step 1j-15.

[0866] In step 1j-30, the terminal (1j-01) can determine whether to trigger a measurement report based on the measurement setting information received in step 1j-15.

[0867] Specifically, the terminal (1j-01) can determine that a measurement report is triggered when at least one of the following conditions is satisfied.

[0868] - If the reportType is set to eventTriggered and if eventId is set to eventH1 or eventH2 and if the entry (or entering) condition applicable for this event, ie the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event, while the VarMeasReportList does not include a measurement reporting entry for this measId:

[0869] ■ include a measurement reporting entry within the VarMeasReportList for this measId;

[0870] ■ set the numberOfReportSent defined within the VarMeasReportList for this measId to 0;

[0871] ■ initiate the measurement reporting procedure, as specified in 1j-35

[0872] - If the reportType is set to eventTriggered and if eventId is set to eventH1 or eventH2 and if the leaving condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event:

[0873] ■ remove the measurement reporting entry within the VarMeasReportList for this measId;

[0874] ■ If reportOnLeave is set to true for the corresponding reporting configuration:

[0875] ◆ Initiate the measurement reporting procedure, as specified in 1j-35

[0876] 참고로, 상기 단말(1j-01)은 Event H1 또는 Event H2의 entry (or entering) condition 을 만족하는 지 또는 Event H1 또는 Event H2의 leaving condition을 만족하는 지는 하기 내용에 기반할 수 있다.

[0877] Event H1 (The Aerial UE height is above a threshold)

[0878] The UE shall:

[0879] 1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled;

[0880] 1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled;

[0881] Inequality H1-1 (Entering condition)

[0882]

[0883] Inequality H1-2 (Leaving condition)

[0884]

[0885] The variables in the formula are defined as follows:

[0886] Ms is the Aerial UE height, not taking into account any offsets.

[0887] Hys is the hysteresis parameter (i.e. h1-Hysteresis as defined within ReportConfigNR) for this event.

[0888] Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

[0889] Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h1-ThresholdOffset as defined within ReportConfigNR)

[0890] Ms is expressed in meters.

[0891] Thresh is expressed in the same unit as Ms.

[0892] Event H2 (The Aerial UE height is below a threshold)

[0893] The UE shall:

[0894] 1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled;

[0895] 1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled;

[0896] Inequality H2-1 (Entering condition)

[0897]

[0898] Inequality H2-2 (Leaving condition)

[0899]

[0900] The variables in the formula are defined as follows:

[0901] Ms is the Aerial UE height, not taking into account any offsets.

[0902] Hys is the hysteresis parameter (i.e. h2-Hysteresis as defined within ReportConfigNR) for this event.

[0903] Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

[0904] Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h2-ThresholdOffset as defined within ReportConfigNR)

[0905] Ms is expressed in meters.

[0906] Thresh is expressed in the same unit as Ms.

[0907] 1j-35 단계에서, 상기 단말(1j-01)은 상기 기지국(1j-02)으로 측정 결과를 보고 할 수 있다.

[0908] For example, if measurement reporting is triggered by eventH1 or eventH2 in step 1j-30, the terminal (1j-01) can transmit a measurement result message (MeasurementReport) to the base station (1j-02). Specifically, the terminal (1j-01) can transmit the measurement result message to the base station (1j-02) according to the following procedure.

[0909] For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

[0910] 1> set the measId to the measurement identity that triggered the measurement reporting;

[0911] 1> for each serving cell configured with servingCellMO:

[0912] 2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0913] 3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available:

[0914] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0915] 2> else:

[0916] 3> if SSB based serving cell measurements are available:

[0917] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0918] 3> else if CSI-RS based serving cell measurements are available:

[0919] 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0920] 1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any;

[0921] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0922] 2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0923] 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0924] 2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting:

[0925] 3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0926] 4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR;

[0927] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0928] 5> for each best non-serving cell included in the measurement report:

[0929] 6> include beam measurement information according to the associated reportConfig as described in 5.5.5.2;

[0930] 1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2:

[0931] 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0932] 3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following:

[0933] 4> include carrierFreq of the E-UTRA serving frequency;

[0934] 4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;

[0935] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0936] 5> set the measResultServFreqListEUTRA-SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

[0937] 1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5:

[0938] 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0939] 3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following:

[0940] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:

[0941] 5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG:

[0942] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;

[0943] 4> else:

[0944] 5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0945] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;

[0946] 5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:

[0947] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;

[0948] 4> if results for the serving cell derived based on SSB are included:

[0949] 5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell;

[0950] 4> if results for the serving cell derived based on CSI-RS are included:

[0951] 5> include the refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the MeasObjectNR of the serving cell;

[0952] 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0953] 5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0954] 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0955] 5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0956] 6> set the measResultNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;

[0957] 7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0958] 8> for each best non-serving cell included in the measurement report:

[0959] 9> include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0960] 1> if the includeCommonLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of commonLocationInfo of the locationInfo as follows:

[0961] 2> include the locationTimestamp;

[0962] 2> include the locationCoordinate, if available;

[0963] 2> include the velocityEstimate, if available;

[0964] 2> include the locationError, if available;

[0965] 2> include the locationSource, if available;

[0966] 2> if available, include the gnss-TOD-msec,

[0967] 1> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the wlan-LocationInfo of the locationInfo in the measResults as follows:

[0968] 2> if available, include the LogMeasResultWLAN, in order of decreasing RSSI for WLAN APs;

[0969] 1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the BT-LocationInfo of the locationInfo in the measResults as follows:

[0970] 2> if available, include the LogMeasResultBT, in order of decreasing RSSI for Bluetooth beacons;

[0971] 1> if the includeSensor-Meas is configured in the corresponding reportConfig for this measId, set the sensor-LocationInfo of the locationInfo in the measResults as follows:

[0972] 2> if available, include the sensor-MeasurementInformation;

[0973] 2> if available, include the sensor-MotionInformation;

[0974] 1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

[0975] 1> stop the periodical reporting timer, if running;

[0976] 1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

[0977] 2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

[0978] 1> else:

[0979] 2> if the reportType is set to periodical or cli-Periodical or rxTxPeriodical:

[0980] 3> remove the entry within the VarMeasReportList for this measId;

[0981] 3> remove this measId from the measIdList within VarMeasConfig;

[0982] 1> else if the UE is in (NG)EN-DC:

[0983] 2> if SRB3 is configured and the SCG is not deactivated:

[0984] 3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0985] 2> else:

[0986] 3> submit the MeasurementReport message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331

[0010] .

[0987] 1> else if the UE is in NR-DC:

[0988] 2> if the measurement configuration that triggered this measurement report is associated with the SCG:

[0989] 3> if SRB3 is configured and the SCG is not deactivated:

[0990] 4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;

[0991] 3> else:

[0992] 4> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;

[0993] 2> else:

[0994] 3> submit the MeasurementReport message via SRB1 to lower layers for transmission, upon which the procedure ends;

[0995] 1> else:

[0996] 2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

[0997] 참고로, 빔 측정 결과는 하기의 절차에 따라 단말(1j-01)이 MeasurementReport에 수납할 수 있다.

[0998] For beam measurement information to be included in a measurement report the UE shall:

[0999] 1> if reportType is set to eventTriggered:

[1000] 2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity;

[1001] 1> set rsIndexResults to include up to maxNrofRS-IndexesToReport SS / PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows:

[1002] 2> if the measurement information to be included is based on SS / PBCH block:

[1003] 3> include within resultsSSB-Indexes the index associated to the best beam for that SS / PBCH block sorting quantity and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;

[1004] 3> if includeBeamMeasurements is set to true, include the SS / PBCH based measurement results for the quantities in reportQuantityRS-Indexes for each SS / PBCH block index;

[1005] 2> else if the beam measurement information to be included is based on CSI-RS:

[1006] 3> include within resultsCSI-RS-Indexes the index associated to the best beam for that CSI-RS sorting quantity and, if absThreshCSI-RS-Consolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshCSI-RS-Consolidation;

[1007] 3> if includeBeamMeasurements is set to true, include the CSI-RS based measurement results for the quantities in reportQuantityRS-Indexes for each CSI-RS index.

[1008] That is, when measurement reporting is triggered by event H1 or event H2, the terminal (1j-01) according to one embodiment of the present disclosure may have the following characteristics when transmitting a MeasurementReport to the base station (1j-02).

[1009] - Include measResultServingCellMOList

[1010] - Does not include measResultNeighCells

[1011] - Does not include measResultServFreqListEUTRA-SCG

[1012] - Does not include measResultServFreqListNR-SCG

[1013] For reference, MeasResults included in MeasurementReport can have the following ASN.1 structure.

[1014]

[1015]

[1016]

[1017]

[1018] FIG. 1k is a flowchart of a process in which an uncrewed aerial vehicle (UAV) terminal efficiently reports a MeasurementReport to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[1019] A UAV (Uncrewed Aerial Vehicle) terminal can refer to a terminal capable of flight.

[1020] Referring to FIG. 1k, at step 1k-05, a UAV terminal (UAV UE, 1k-01) may be in RRC connected mode (RRC_CONNECTED) by establishing a radio resource control (RRC) connection with an NR base station (gNB, 1k-02).

[1021] At step 1k-10, the UAV terminal (1k-01) can report the terminal's capabilities to the base station (1k-02).

[1022] For example, the terminal (1k-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1k-02). This may follow at least one of the embodiments described above.

[1023] At step 1k-15, the base station (1k-02) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the UAV terminal (1k-01). This may follow at least one of the embodiments described above.

[1024] According to one embodiment of the present disclosure, a base station can be configured to initiate a measurement reporting procedure when a terminal simultaneously satisfies an altitude-based event (e.g., eventH1 or eventH2) and a signal-based event (e.g., eventA3, eventA4, eventA5) through the measurement configuration information.

[1025] In step 1k-20, the terminal (1k-01) can perform measurement based on the measurement setting information received in step 1k-15.

[1026] At step 1k-25, the terminal can determine whether to trigger a measurement report based on the measurement configuration information received at step 1k-20.

[1027] Specifically, when measurement report triggering for eventHx and eventAx of the above-described embodiment are simultaneously satisfied, the terminal can determine whether to trigger a measurement report.

[1028] At step 1k-30, the terminal (1k-01) can report the measurement results to the base station (1k-02).

[1029] For example, if measurement reporting is triggered in step 1k-25, the terminal (1k-01) may transmit a measurement result message (MeasurementReport) to the base station (1k-02). This may follow at least one of the embodiments described above.

[1030] At step 1k-35, the terminal (1k-01) may apply one or more of numberOfTriggeringCells or a4-Threshold associated with a new altitude (or altitude range) based on the altitude of the terminal (1k-01).

[1031] Specifically, when the terminal (1k-01) flies at a (new) altitude different from the altitude at which it was flying at step 1k-20 or step 1k-25 or step 1k-30 and enters a new altitude or altitude range set at step 1k-15, it may apply a numberOfTriggeringCells (and / or a4-Threshold) different from the numberOfTriggeringCells (and / or a4-Threshold) applied at step 1k-20 or step 1k-25 and perform a terminal operation related thereto. This may follow at least one of the embodiments described above.

[1032] And it can be determined whether the above measurement report should be triggered. This can follow the 1k-25 steps.

[1033] At step 1k-40, the terminal (1k-01) can report the measurement results to the base station (1k-02).

[1034] For example, when the measurement report procedure is initiated at step 1k-35, the terminal (1k-01) can transmit a measurement result message (MeasurementReport) to the base station (1k-02) according to the following procedure.

[1035] FIG. 1l is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.

[1036] Referring to the above drawing, the terminal may include an RF (Radio Frequency) processing unit (1l-10), a baseband processing unit (1l-20), a storage unit (1l-30), and a control unit (1l-40).

[1037] The RF processing unit (11-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (11-10) may up-convert a baseband signal provided from the baseband processing unit (11-20) into an RF band signal and transmit the same through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (11-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (11-10) may include multiple RF chains.

[1038] Furthermore, the RF processing unit (11-10) can perform beamforming. For the beamforming, the RF processing unit (11-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO, and can receive multiple layers when performing the MIMO operation.

[1039] The baseband processing unit (11-20) above can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (11-20) can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processing unit (11-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (11-10).

[1040] For example, in the case of OFDM (orthogonal frequency division multiplexing), when transmitting data, the baseband processing unit (11-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. In addition, when receiving data, the baseband processing unit (11-20) can divide the baseband signal provided from the RF processing unit (11-10) into OFDM symbol units, restore signals mapped to subcarriers through FFT (fast Fourier transform), and then restore the received bit stream through demodulation and decoding.

[1041] The baseband processing unit (11-20) and the RF processing unit (11-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (11-20) and the RF processing unit (11-10) may be referred to as a transmitting unit, a receiving unit, a transceiver unit, or a communication unit.

[1042] Furthermore, at least one of the baseband processing unit (11-20) and the RF processing unit (11-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (11-20) and the RF processing unit (11-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. In addition, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band, a millimeter wave (mm wave) (e.g., 60GHz) band.

[1043] The above storage unit (1l-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (1l-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (1l-30) can provide the stored data upon request from the control unit (1l-40).

[1044] The above control unit (1l-40) can control the overall operations of the terminal. For example, the control unit (1l-40) can transmit and receive signals through the baseband processing unit (1l-20) and the RF processing unit (1l-10). In addition, the control unit (1l-40) can record and read data in the storage unit (1l-40).

[1045] To this end, the control unit (11-40) may include at least one processor. For example, the control unit (11-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[1046] FIG. 1m is a block diagram illustrating the internal structure of a base station according to one embodiment of the present disclosure.

[1047] As shown in the above drawing, the base station may be configured to include an RF processing unit (1m-10), a baseband processing unit (1m-20), a backhaul communication unit (1m-30), a storage unit (1m-40), and a control unit (1m-50).

[1048] The RF processing unit (1m-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1m-10) may up-convert a baseband signal provided from the baseband processing unit (1m-20) into an RF band signal and transmit the up-converted signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1m-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is illustrated, but the first access node may have multiple antennas. In addition, the RF processing unit (1m-10) may include multiple RF chains.

[1049] Furthermore, the RF processing unit (1m-10) can perform beamforming. For the beamforming, the RF processing unit (1m-10) can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[1050] The baseband processing unit (1m-20) above can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1m-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1m-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1m-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1m-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1m-20) divides the baseband signal provided from the RF processing unit (1m-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding.

[1051] The baseband processing unit (1m-20) and the RF processing unit (1m-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (1m-20) and the RF processing unit (1m-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[1052] The above backhaul communication unit (1m-30) can provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit (1m-30) can convert a bit string transmitted from the main base station to another node, such as an auxiliary base station or a core network, into a physical signal, and can convert a physical signal received from the other node into a bit string.

[1053] The storage unit (1m-40) can store data such as basic programs, application programs, and setting information for the operation of the main base station. In particular, the storage unit (1m-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (1m-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (1m-40) can provide stored data at the request of the control unit (1m-50).

[1054] The control unit (1m-50) can control the overall operations of the base station. For example, the control unit (1m-50) can transmit and receive signals through the baseband processing unit (1m-20) and the RF processing unit (1m-10) or through the backhaul communication unit (1m-30). In addition, the control unit (1m-50) records and reads data in the storage unit (1m-40). For this purpose, the control unit (1m-50) can include at least one processor.

[1055] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[1056] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[1057] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[1058] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[1059] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[1060] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples presented to easily explain the technical content of the present disclosure and facilitate understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art to which the present disclosure pertains that other modifications based on the technical concept of the present disclosure are possible. Furthermore, the above-described embodiments may be combined and operated as needed.

[1061] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[1062] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[1063] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

[1064] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. A method performed by a terminal of a wireless communication system, A step of obtaining measurement setting information including altitude-related information from a base station; A step of performing measurements for at least one cell for at least one altitude based on the above altitude-related information; and Comprising a step of reporting the measurement results for at least one cell to the base station based on the altitude-related information, A method characterized in that said altitude related information comprises at least one altitude threshold value for determining whether to trigger a report for said at least one measurement result.

2. In paragraph 1, A method characterized in that the above altitude-related information further includes information related to the number of cells (number of triggering cells) related to at least one of the above measurements.

3. In paragraph 1, The measurement results for at least one cell measured at the first altitude are deleted after the first timer running at the first altitude expires after the terminal enters the second altitude, or A method characterized in that the measurement results for at least one cell measured at the first altitude are deleted after the second timer newly run at the second altitude expires after the terminal enters the second altitude.

4. In paragraph 1, The measurement results for at least one cell measured at the first altitude are deleted when the terminal enters the second altitude, or A method characterized in that the measurement results for at least one cell measured at the first altitude are deleted according to the settings of the base station.

5. In paragraph 1, A method characterized in that when the terminal enters the second altitude, the operation of the periodic reporting timer is stopped and the time to trigger related to the measurement results for at least one cell measured at the first altitude is reset.

6. In paragraph 1, A method characterized in that, when the terminal enters a second altitude, the periodic reporting timer is kept running and the time to trigger related to the measurement results for at least one cell measured at the first altitude is maintained.

7. A method performed by a base station of a wireless communication system, A step of transmitting measurement setting information including altitude-related information to a terminal; and A step of receiving, from the terminal, a measurement result for at least one cell measured based on the altitude-related information, A method characterized in that the altitude-related information comprises at least one altitude threshold associated with whether to trigger a report for the at least one measurement result.

8. In paragraph 7, A method characterized in that the above altitude-related information further includes information related to the number of cells (number of triggering cells) related to at least one of the above measurements.

9. In the terminal of a wireless communication system, A transceiver for transmitting and receiving signals; and A control unit is included, wherein the control unit comprises: Obtain measurement setting information including altitude-related information from a base station, Based on the above altitude-related information, measurements are performed for at least one cell for at least one altitude, Reporting the measurement results for at least one cell to the base station based on the altitude-related information, A terminal characterized in that the altitude-related information includes at least one altitude threshold value for determining whether to trigger a report for at least one measurement result.

10. In paragraph 9, A terminal characterized in that the altitude-related information further includes information related to the number of cells (number of triggering cells) related to at least one of the measurements.

11. In paragraph 9, The measurement results for at least one cell measured at the first altitude are deleted after the first timer running at the first altitude expires after the terminal enters the second altitude, or A terminal characterized in that the measurement results for at least one cell measured at the first altitude are deleted after the second timer newly run at the second altitude expires after the terminal enters the second altitude.

12. In paragraph 9, The measurement results for at least one cell measured at the first altitude are deleted when the terminal enters the second altitude, or A terminal characterized in that the measurement results for at least one cell measured at the first altitude are deleted according to the settings of the base station.

13. In paragraph 9, When the terminal enters the second altitude, the periodic reporting timer is stopped and the time to trigger related to the measurement results for at least one cell measured at the first altitude is reset, or A terminal characterized in that, when the terminal enters a second altitude, the periodic reporting timer is kept running and the time to trigger related to the measurement results for at least one cell measured at the first altitude is maintained.

14. In a base station of a wireless communication system, A transceiver for transmitting and receiving signals; and A control unit is included, wherein the control unit comprises: Transmit measurement setting information including altitude-related information to the terminal, Receive measurement results for at least one cell measured based on the altitude-related information from the terminal, A base station, characterized in that the altitude-related information includes at least one altitude threshold associated with whether to trigger a report for the at least one measurement result.

15. In paragraph 14, A base station, characterized in that the altitude-related information further includes information related to the number of cells (number of triggering cells) related to at least one of the measurements.

Citation Information

Patent Citations

  • Bicycle

    KR102410926B1

  • Measurement reporting method and apparatus

    US20200187033A1

  • Device, method, and computer readable storage medium in wireless communication system

    US20200236573A1

  • Apparatus and method in wireless communication system and computer readable storage medium

    US20210160749A1

  • Apparatus and method in wireless communication system, and computer readable storage medium

    US20220303813A1