Method and apparatus for configuring and signaling plurality of measurement report trigger events in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a communication system includes receiving measurement configuration information including information on a predefined event, where the predefined event corresponds to a first event and a second event; identifying, based on the information about the predefined event, whether an entry condition of the predefined event is satisfied, where the entry condition of the predefined event is satisfied in a case where both the entry condition of the first event and the entry condition of the second event are achieved; and transmitting a measurement report based on the identification.

Description

Technical Field

[0001] The present disclosure may relate to terminal and base station operations in a wireless communication system. Background Art

[0002] Fifth-generation (5G) mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It is achievable not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves (mmWave), including 28 GHz and 39 GHz. Furthermore, consideration has been given to implementing 6G mobile communication technology (referred to as a "super 5G system") in the terahertz frequency band (e.g., the 95 GHz to 3 THz band) in order to achieve transmission rates fifty times faster than 5G mobile communication technology and ultra-low latency one-tenth that of 5G mobile communication technology.

[0003] At the start of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), there has been ongoing standardization on the following items: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission range in millimeter waves, parameter sets supporting dynamic operation for efficient utilization of millimeter wave resources and time slot formats (such as operation of multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and wideband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity-check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information at altitude), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as V2X (Vehicle-to-Everything) for assisting autonomous vehicles in driving determination based on information about the position and status of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation intended to comply with various regulatory requirements in unlicensed bands, NR UE power saving, non-terrestrial networks (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not possible), and positioning.

[0005] In addition, in the field of air interface architecture / protocols, there is ongoing standardization of technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization of 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, as well as system architecture / services for mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices, which has been growing exponentially, will be connected to the communication network. Accordingly, it is expected that enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will become necessary. To this end, new research is planned related to extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc.; 5G performance improvements and complexity reduction through the use of artificial intelligence (AI) and machine learning (ML); AI service support, metaverse service support, and drone communications.

[0007] Furthermore, this development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and RIS (Reconfigurable Smart Surfaces), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for delivering services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the Invention

[0009] Technical issues

[0010] The present disclosure is to provide an apparatus and method capable of effectively providing services in a communication system.

[0011] The technical objectives to be achieved by the embodiments of the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art may consider other technical objectives not mentioned from the embodiments of the present disclosure to be described below.

[0012] Technical Solution

[0013] According to an embodiment, a method performed by a user equipment (UE) in a communication system is provided.

[0014] According to an embodiment, the method includes: receiving measurement configuration information including information about predefined events, wherein the predefined events correspond to a first event and a second event; based on the information about the predefined events, identifying whether an entry condition of the predefined event is met, wherein the entry condition of the predefined event is met when both the entry condition of the first event and the entry condition of the second event are met; and sending a measurement report based on the identification.

[0015] According to an embodiment, the first event is associated with a measurement of a cell and the second event is associated with an altitude of the UE.

[0016] According to an embodiment, the first event is one of event A3, event A4 and event A5.

[0017] According to an embodiment, the second event is one of event H1 and event H2.

[0018] According to an embodiment, the method further comprises: in case both the exit condition of the first event and the exit condition of the second event are met, identifying that the exit condition of the predefined event is satisfied.

[0019] According to an embodiment, the information about the predefined event includes a first parameter of the first event and a second parameter of the second event.

[0020] According to an embodiment, a user equipment (UE) in a communication system is provided.

[0021] According to an embodiment, a UE includes: a transceiver; and a processor coupled to the transceiver and configured to: receive measurement configuration information including information about predefined events, wherein the predefined events correspond to a first event and a second event; based on the information about the predefined events, identify whether an entry condition for the predefined event is met, wherein the entry condition for the predefined event is met if both the entry condition for the first event and the entry condition for the second event are met; and send a measurement report based on the identification.

[0022] According to an embodiment, the first event is associated with a measurement of a cell and the second event is associated with an altitude of the UE.

[0023] According to an embodiment, the first event is one of event A3, event A4 and event A5.

[0024] According to an embodiment, the second event is one of event H1 and event H2.

[0025] According to an embodiment, the processor is further configured to identify that the exit condition of the predefined event is satisfied if both the exit condition of the first event and the exit condition of the second event are met.

[0026] According to an embodiment, the information about the predefined event includes a first parameter of the first event and a second parameter of the second event.

[0027] According to an embodiment, a method performed by a base station in a communication system is provided.

[0028] According to an embodiment, the method comprises: sending measurement configuration information including information about predefined events, wherein the predefined events correspond to a first event and a second event; and receiving a measurement report associated with the measurement configuration information.

[0029] According to an embodiment, the entry condition of the predefined event is satisfied in case both the entry condition of the first event and the entry condition of the second event are met.

[0030] According to an embodiment, the first event is associated with a measurement of a cell and the second event is associated with an altitude of a user equipment (UE).

[0031] According to an embodiment, the first event is one of event A3, event A4 and event A5.

[0032] According to an embodiment, the second event is one of event H1 and event H2.

[0033] According to an embodiment, the exit condition of the predefined event is satisfied in case both the exit condition of the first event and the exit condition of the second event are met.

[0034] According to an embodiment, the information about the predefined event includes a first parameter of the first event and a second parameter of the second event.

[0035] According to an embodiment, a base station in a communication system is provided.

[0036] According to an embodiment, a base station includes: a transceiver; and a processor, which is coupled to the transceiver and configured to: send measurement configuration information including information about predefined events, wherein the predefined events correspond to a first event and a second event; and receive a measurement report associated with the measurement configuration information.

[0037] According to an embodiment, the entry condition of the predefined event is satisfied in case both the entry condition of the first event and the entry condition of the second event are met.

[0038] According to an embodiment, the first event is associated with a measurement of a cell and the second event is associated with an altitude of a user equipment (UE).

[0039] According to an embodiment, the first event is one of event A3, event A4 and event A5.

[0040] According to an embodiment, the second event is one of event H1 and event H2.

[0041] According to an embodiment, the exit condition of the predefined event is satisfied in case both the exit condition of the first event and the exit condition of the second event are met.

[0042] According to an embodiment, the information about the predefined event includes a first parameter of the first event and a second parameter of the second event.

[0043] The various embodiments described above of the present disclosure are only some preferred embodiments of the present disclosure, and those skilled in the art can derive and understand various embodiments reflecting the technical features of the present disclosure based on the following detailed description of the present disclosure.

[0044] Beneficial effects

[0045] The present disclosure may provide an apparatus and method capable of efficiently providing services in a communication system.

[0046] Effects that can be achieved by the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned will be clearly understood by those skilled in the art from the following description.

[0047] Before proceeding with the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated therewith" and their derivatives may mean including, included within, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, proximate to, bound to or bound with, having, having the property of, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device being implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0048] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof, suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random-access memory (RAM), hard drives, compact disks (CDs), digital video disks (DVDs), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes both media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical disks or erasable memory devices.

[0049] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0051] Figure 1 The structure of the NR system according to an embodiment of the present disclosure is shown;

[0052] Figure 2 The wireless protocol structure in the NR system according to an embodiment of the present disclosure is shown;

[0053] Figure 3 An example of a process in which a UAV terminal sends a measurement report to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown;

[0054] Figure 4 An example of the relationship among MO, measId, and reportConfig including one event configuration information according to an embodiment of the present disclosure is shown;

[0055] Figure 5 An example of a relationship among measId, MO, and reportConfig including a plurality of event configuration information according to an embodiment of the present disclosure is shown;

[0056] Figure 6 An example of a structure in which one measId is associated with multiple reportConfigs according to an embodiment of the present disclosure is shown;

[0057] Figure 7 An example of a structure showing that one measId can be associated with events indicated in multiple reportConfigs according to an embodiment of the present disclosure;

[0058] Figure 8 An example of a process in which a UAV terminal sends a measurement report to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown;

[0059] Figure 9 shows the structure of a terminal according to an embodiment of the present disclosure; and

[0060] Figure 10 The structure of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0061] Discussed below Figures 1 to 10 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0062] Hereinafter, preferred embodiments of the present disclosure will be described with reference to the accompanying drawings. Here, in the accompanying drawings, identical or similar elements are represented by identical or similar reference numerals as much as possible. In addition, detailed descriptions of known functions or structures that may obscure the subject matter of the present disclosure may be omitted.

[0063] When describing the embodiments of the present disclosure, descriptions of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. By omitting unnecessary descriptions, the gist of the present disclosure can be conveyed more clearly without obscuring the subject matter.

[0064] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In each accompanying drawing, the same or corresponding elements are provided with the same reference numerals.

[0065] The advantages and features of the present disclosure and the manner in which they are achieved will be apparent by reference to the embodiments described in detail below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but may be implemented in a variety of different forms. The embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0066] It will be understood that the blocks in a flowchart or process flow diagram can be executed by computer program instructions. Because these computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device, the instructions, when executed by the processor of the computer or other programmable data processing device, create means for performing the functions described in the flowchart block(s). The computer program instructions can be stored in a computer-usable or computer-readable memory capable of instructing the computer or other programmable data processing device to implement the functions in a specific manner. Thus, the instructions stored in the computer-usable or computer-readable memory can also be used to produce an article of manufacture containing the instruction means for performing the functions described in the flowchart block(s). The computer program instructions can also be loaded into a computer or other programmable data processing device. Thus, when a series of operations are executed in the computer or other programmable data processing device, the instructions for operating the computer or other programmable data processing device by generating a computer-implemented process can provide operations for performing the functions described in the flowchart block(s).

[0067] In addition, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specified logical function (or functions). It should also be noted that in some alternative implementations, the functions mentioned in the blocks may not occur in order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order based on the corresponding functions.

[0068] As used herein, the term "unit" refers to a software component or hardware component, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), that performs a specific function. However, the term "unit" is not limited to software or hardware. A "unit" can be implemented in an addressable storage medium or can be implemented to operate one or more processors. Thus, for example, the term "unit" can refer to components such as software components, object-oriented software components, class components, and task components, and can include processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functionality provided by a component or "unit" can be associated with a smaller number of components or "units" or can be further divided into additional components or "units." Furthermore, a component or "unit" can be embodied as one or more CPUs in a reproduction device or secure multimedia card.

[0069] Hereinafter, a base station is an entity that allocates resources to a terminal and may be at least one of a Node B, a base station (BS), an eNodeB (eNB), a gNodeB (gNB), a radio access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types as the embodiments of the present disclosure described below. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by those skilled in the art, without significantly departing from the scope of the present disclosure.

[0070] For example, these technologies may include fifth-generation mobile communication technologies (5G, New Radio (NR)) developed beyond LTE-A, and in the following description, 5G may be a concept that covers existing LTE, LTE-A, or other similar services. In addition, based on the determination of those skilled in the art, the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0071] In the following description, for the sake of convenience, terms for identifying access nodes, terms related to network entities or network functions (NFs), terms related to messages, terms related to interfaces between network entities, terms related to various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms referring to subjects having equivalent technical meanings may be used.

[0072] In the following description, for ease of description, the present disclosure will be described using terms and names defined in the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standard and / or the 3GPP New Radio (NR) standard. However, the present disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards.

[0073] Figure 1 The structure of the NR system according to an embodiment of the present disclosure is shown.

[0074] refer to Figure 1 , the wireless communication system can be constructed to include several base stations (e.g., gNB 100, ng-eNB 110, ng-eNB 120, and gNB 130), an access and mobility management function (AMF) 140, and a user plane function (UPF) 150. Obviously, the wireless communication system is not limited to Figure 1 The structures shown are for purposes of illustration and may include more or fewer components.

[0075] According to an embodiment of the present disclosure, a user terminal (hereinafter referred to as UE or terminal) 160 may access an external network through the base stations 100 , 110 , 120 , 130 and the UPF 150 .

[0076] exist Figure 1 In NR, base stations 100, 110, 120, and 130 can provide radio access to terminals accessing the network as access nodes of the cellular network. For example, base stations 100, 110, 120, and 130 can collect terminal status information, such as buffer status, available transmission power status, and channel status, perform scheduling to serve user services, and support connections between terminals and the core network (CN) (particularly, the CN of NR can be referred to as 5GC). Base stations 100, 110, 120, and 130 can be connected to each other via an Xn interface. Base stations 100, 110, 120, and 130 can also be connected to the 5GC via an NG interface.

[0077] exist Figure 1 In the present invention, the gNB 100, 130 can control multiple cells and can apply an adaptive modulation and coding (hereinafter, AMC) scheme to determine a modulation scheme and a channel coding rate according to the channel state of the terminal.

[0078] The core network is a device that is responsible for not only the mobility management function of the terminal but also various control functions, and can be connected to multiple base stations. In addition, 5GC can be interlocked with the existing LTE system.

[0079] Meanwhile, in a wireless communication system, a user plane (UP) related to the transmission of actual user data and a control plane (CP) related to connection management can be constructed separately. Figure 1 In the 5GC, gNB 100 and gNB 130 can use the UP and CP techniques defined in the NR technology, and ng-eNB 110 and ng-eNB 120 can use the UP and CP techniques defined in the Long Term Evolution (LTE) technology, although they are connected to the 5GC.

[0080] The AMF 140 may be a device / node responsible not only for the mobility management function of the terminal but also for various control functions, and may be connected with a plurality of base stations.

[0081] UPF 150 may indicate a gateway device / node that provides data transmission. Figure 1 Although not shown in the figure, the NR wireless communication system may include a session management function (SMF). The SMF can manage packet data network connections to be provided to the terminal, such as protocol data unit (PDU) sessions.

[0082] Figure 2 The wireless protocol structure in the NR system according to an embodiment of the present disclosure is shown.

[0083] refer to Figure 2 The wireless protocol of the NR system may include a service data adaptation protocol (SDAP) layer 200, 290, a packet data convergence protocol (PDCP) layer 210, 280, a radio link control (RLC) layer 220, 270, a medium access control (MAC) layer 230, 260, and a physical (PHY) layer 240, 250 in the terminal and the base station, respectively.

[0084] The Service Data Adaptation Protocol (SDAP) layer 200, 290 can perform the following operations: delivering user data, mapping Quality of Service (QoS) flows to specific Data Radio Bearers (DRBs) for uplink and downlink, marking QoS flow identifiers / identifications (IDs) for downlink and uplink, and mapping Reflective QoS flows to data bearers for uplink SDAP PDUs. The SDAP configuration corresponding to each DRB can be provided by the higher RRC layer. Obviously, the SDAP layer is not limited to the examples described above.

[0085] The Packet Data Convergence Protocol (PDCP) layer 210, 280 may be responsible for Internet Protocol (IP) header compression / decompression operations. Furthermore, the PDCP layer 210, 280 may provide in-sequence and out-of-sequence delivery functions, and may also provide reordering, duplicate detection, retransmission, encryption, and decryption functions. However, it is apparent that the PDCP layer is not limited to the examples described above.

[0086] The radio resource control (RRC) layer 220, 270 can reconstruct the PDCP protocol data unit (PDU) into an appropriate size. Furthermore, the RLC layer 220, 270 can provide in-sequence and out-of-sequence delivery functions, as well as automatic repeat request (ARQ) functions, concatenation functions, segmentation functions, reassembly functions, resegmentation functions, reordering functions, duplicate detection functions, and error detection functions. Obviously, the RLC layer is not limited to the examples described above.

[0087] The MAC layer 230, 260 can connect to various RLC layer devices built into a terminal and perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. Furthermore, the MAC layer 230, 260 can provide mapping functions, scheduling information reporting functions, HARQ functions, priority processing between logical channels, priority processing between terminals, Multimedia Broadcast Multicast Service (MBMS) service identification functions, transport format selection functions, and padding functions. Obviously, the MAC layer is not limited to the examples described above.

[0088] The physical (PHY) layer 240, 250 can perform the following operations: channel coding and modulating higher-layer data to generate orthogonal frequency division multiplexing (OFDM) symbols and transmitting the OFDM symbols over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting the demodulated and channel-decoded OFDM symbols to higher layers. In addition, hybrid ARQ (HARQ) can be used for additional error correction in the physical layer, and the receiving end can use a single bit to transmit information about whether a packet sent by the transmitting end has been received. This single bit of information can be referred to as HARQ acknowledgement (ACK) / negative acknowledgement (NACK) information.

[0089] In LTE, downlink HARQ ACK / NACK information for uplink data transmission can be transmitted via the Physical Hybrid ARQ Indicator Channel (PHICH). In NR, whether retransmission is required or a new transmission should be performed can be determined by the terminal's scheduling information in the Physical Dedicated Control Channel (PDCCH), which is a channel used to transmit downlink / uplink resource allocations, etc. This is because asynchronous HARQ is applied in NR. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted via physical channels such as the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The PUCCH is typically transmitted via the uplink of the PCell described above. However, if the base station supports the terminal, the PUCCH can also be transmitted to the SCell in the corresponding terminal, as will be described below. The SCell is referred to as the PUCCH SCell.

[0090] Although not in Figure 2 , but a radio resource control (RRC) layer may exist above the PDCP layer of each of the terminal and the base station, and the RRC layer may transmit and receive access and measurement-related configuration control messages for radio resource control.

[0091] Meanwhile, the physical layer can include one or more frequencies / carriers, and the technology for simultaneously configuring and using multiple frequencies is called carrier aggregation technology (hereinafter referred to as CA). Communication between a terminal (or user equipment (UE)) and a base station (eNB or gNB) already uses one carrier, but CA technology can additionally use a primary carrier and one or more subcarriers, thereby significantly increasing the amount of data to be transmitted through multiple subcarriers. Meanwhile, in LTE / NR, a cell within a base station using a primary carrier can be called a primary cell or PCell, and a cell within a base station using a subcarrier can be called a secondary cell or SCell.

[0092] Figure 3 An example of a process in which an unmanned aerial vehicle (UAV) terminal transmits a measurement report to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0093] refer to Figure 3 In operation 320, the UAV terminal 300 may establish an RRC connection with the NR base station 310 and be in RRC connection mode (RRC_CONNECTED).

[0094] In operation 330, the base station may transmit a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) including measurement configuration information (e.g., MeasConfig) to the terminal. For example, MeasConfig may have an abstract syntax notation one (ASN.1) structure as shown in Table 1. For example, MeasConfig may include one or more of the information elements (IEs) shown in Table 1. Table 1 is an example of the structure of MeasConfig, and the present disclosure is not limited thereto.

[0095] [Table 1]

[0096]

[0097]

[0098] According to an embodiment of the present disclosure, measurement configuration information may include measurement object information (e.g., which may be referred to as measObjectToAddModList), which includes conditions for the measurement object. measObjectToAddModList may include one or more MeasObjectToAddMods. For example, measObjectToAddModList and MeasObjectToAddMod may have the ASN.1 structure shown in Table 2. For example, measObjectToAddModList and MeasObjectToAddMod may each include one or more of the IEs shown in Table 2. Table 2 is an example of the structure of measObjectToAddModList and MeasObjectToAddMod, and the present disclosure is not limited thereto.

[0099] [Table 2]

[0100]

[0101] According to an embodiment of the present disclosure, measurement configuration information may include report configuration information (e.g., reportConfigToAddModList), which includes measurement report trigger event configuration and report-related configuration information. reportConfigToAddModList may include one or more ReportConfigToAddMods. For example, reportConfigToAddModList and ReportConfigToAddMod may have the ASN.1 structure shown in Table 3. For example, reportConfigToAddModList and ReportConfigToAddMod may each include one or more of the IEs shown in Table 3. Table 3 is an example of the structure of reportConfigToAddModList and ReportConfigToAddMod, and the present disclosure is not limited thereto.

[0102] [Table 3]

[0103]

[0104] According to an embodiment of the present disclosure, ReportConfigToAddMod may include a reportConfig field that configures one of the reportConfigIds, where the reportConfigId indicates the corresponding reportConfig and reportConfig type. For example, ReportConfigNR, which is a ReportConfig of NR, may have an ASN.1 structure as shown in Table 4. For example, ReportConfigNR may include one or more of the IEs shown in Table 4. Table 4 is an example of the structure of ReportConfigNR, and the present disclosure is not limited thereto.

[0105] [Table 4]

[0106]

[0107] According to an embodiment of the present disclosure, ReportConfigNR can be one of several predetermined reportTypes. For example, ReportConfigNR can be in the form of EventTriggerConfig, which is eventTriggered based on an event and is one of the reportTypes. For example, EventTriggerConfig can have an ASN.1 structure as shown in Table 5. For example, EventTriggerConfig can include one or more IEs shown in Table 5. Table 5 is an example of the structure of EventTriggerConfig, and the present disclosure is not limited thereto.

[0108] [Table 5]

[0109]

[0110]

[0111]

[0112]

[0113] According to an embodiment of the present disclosure, EventTriggerConfig may be composed of an eventId field indicating measurement report triggering event configuration information and other report-related configuration fields. For example, the eventId field may indicate the corresponding event-related configuration information of an event selected from the A1, A2, A3, A4, A5, A6, X1, X2, and D1 events defined in the NR standard. For example, each event may be as follows:

[0114] Event A1: Service becomes better than the absolute threshold;

[0115] Event A2: Service becomes worse than the absolute threshold;

[0116] Event A3: The neighbor (near neighbor) becomes better than the PCell (primary cell) / PSCell (primary secondary cell, primary SCG (secondary cell group) cell) by one offset;

[0117] Event A4: The neighbor becomes better than the absolute threshold;

[0118] Event A5: PCell / PSCell becomes worse than absolute threshold 1, and neighbor / SCell (secondary cell) becomes better than another absolute threshold 2;

[0119] Event A6: The neighbor becomes one offset better than the SCell;

[0120] Event X1: The serving L2 (Layer 2) U2N (UE to Network) relay UE becomes worse than an absolute threshold 1, and the NR cell becomes better than another absolute threshold 2;

[0121] Event X2: Serving L2 U2N relay UE becomes worse than an absolute threshold; and

[0122] Event D1: The distance between the UE and the reference location referenceLocation1 becomes greater than the configured threshold distance ThreshFromReference1, and the distance between the UE and the reference location referenceLocation2 becomes shorter than the configured threshold distance ThreshFromReference2.

[0123] UAV terminals can operate at higher locations than terrestrial terminals (UEs). Therefore, UAV terminals may have a longer visual range than terrestrial UEs. Consequently, UAV terminals may receive downlink (DL) interference from more cells than terrestrial UEs. In other words, UAV terminals may receive higher levels of DL interference from more surrounding cells than terrestrial UEs. Similarly, UAV terminals may cause uplink (UL) interference to more cells than terrestrial UEs.

[0124] Therefore, the base station needs to be configured to trigger a measurement report only when the UAV terminal is in a high position. The method / standard for determining / identifying "when the UAV terminal is in a high position" can refer to the description of the following embodiments. This may mean that in addition to the events defined in the existing NR system, it is also necessary to consider altitude-based events in the measurement report triggering events of the UAV terminal. In other words, in addition to and / or independently of the events defined in the existing NR standard, the measurement report triggering events of the UAV terminal may include altitude-based events (of the UAV terminal).

[0125] According to an embodiment of the present disclosure, in addition to the events defined in the NR standard, events H1 and H2, which are events based on altitude, may be added to the candidate events of eventId. In this case, EventTriggerConfig may have an ASN.1 structure as shown in Table 6. For example, EventTriggerConfig may include one or more of the IEs shown in Table 6. Table 6 is an example of the structure of EventTriggerConfig, and the present disclosure is not limited thereto.

[0126] [Table 6]

[0127]

[0128]

[0129]

[0130]

[0131] According to an embodiment of the present disclosure, the eventId field may include configuration information for a specific event. For example, the eventId field may include at least one of the following configuration information for event H1. For example, the event H1 configuration information in Table 6 (and in this disclosure, for example, Tables 11, 12, 13, 16, and related descriptions) may include at least one of the following information:

[0132] heightThreshRef: It can indicate the height threshold used for entering or leaving conditions;

[0133] h1-ThresholdOffset: It can indicate the offset value compared to the altitude threshold used for entry or exit conditions;

[0134] h1- Hysteresis: It indicates the hysteresis value to prevent ping-pong phenomenon; and

[0135] reportOnLeave: This field can indicate whether the terminal reports measurements when the leave condition is met. For example, if it is TRUE, it can indicate that the measurement is reported, and if it is FALSE, it can indicate that the measurement is not reported. As another example, if reportOnLeave is included, it can be interpreted as an indication that measurement reporting can be performed, and if reportOnLeave is not included, it can be interpreted as an indication that measurement reporting can be performed.

[0136] According to an embodiment of the present disclosure, the entry and exit conditions of event H1 indicated by the eventId field may be configured as shown in Table 7. In other words, the entry and exit conditions of event H1 may be configured based on one or more of the contents included in Table 7.

[0137] [Table 7]

[0138]

[0139] According to an embodiment of the present disclosure, the eventId field may include at least one of the following configuration information for event H2. For example, the event H2 configuration information in Table 6 (and the present disclosure, for example, Tables 11, 12, 13, 16 and related descriptions) may include at least one of the following information:

[0140] heightThreshRef: It can indicate the height threshold used for entering or leaving conditions;

[0141] h2-ThresholdOffset: It can indicate the offset value compared to the height threshold used for entry or exit conditions;

[0142] h2- Hysteresis: It indicates the hysteresis value to prevent ping-pong phenomenon; and

[0143] reportOnLeave: This field can indicate whether the terminal reports measurements when the leave condition is met. For example, if it is TRUE, it can indicate that the measurement is reported, and if it is FALSE, it can indicate that the measurement is not reported. As another example, if reportOnLeave is included, it can be interpreted as an indication that measurement reporting can be performed, and if reportOnLeave is not included, it can be interpreted as an indication that measurement reporting can be performed.

[0144] In one embodiment of the present disclosure, the entry and exit conditions of event H2, which may be indicated by the eventId field, may be configured as shown in Table 8. That is, the entry and exit conditions of event H2 may be configured based on one or more of the contents included in Table 8.

[0145] [Table 8]

[0146]

[0147] According to an embodiment of the present disclosure, measurement configuration information (e.g., MeasConfig) may include a measIdToAddModList so that the terminal can add or modify a MeasId. The measIdToAddModList may include one or more MeasIdToAddMods. For example, MeasIdToAddMod may include at least one of a measId field, a measObjectId field, and a reportConfigId field. Accordingly, a specific measId may be associated with a measObject corresponding to the measObjectId and a reportConfig corresponding to the reportConfigId. For example, MeasIdToAddMod may have an ASN.1 structure as shown in Table 9. For example, MeasIdToAddMod may include one or more of the IEs shown in Table 9. Table 9 is an example of the structure of MeasIdToAddMod, and the present disclosure is not limited thereto.

[0148] [Table 9]

[0149] Reference again Figure 3 For example, in operation 340 , the terminal may perform a measurement operation based on the measurement configuration information (eg, MeasConfig) in operation 330 .

[0150] In operation 350 , the terminal may trigger a measurement report based on the measurement configuration information (eg, MeasConfig) configured by the base station in operation 330 .

[0151] In operation 360 , the terminal may send a measurement report to the base station based on the measurement configuration information (eg, MeasConfig) configured in operation 330 .

[0152] Figure 4 An example of the relationship among measObject (MO), measId, and reportConfig according to an embodiment of the present disclosure is shown.

[0153] refer to Figure 4For example, a total of N MOs can be configured as MO 1, MO 2, ..., MO N. Each MO can include a measurement frequency (ssbFrequency) and other measurement object-related configuration information (other fields). A total of K measIds can be configured as measId 1, measId 2, ..., measId K. Each measId can be associated with one MO and one ReportConfig. A total of M ReportConfigs can be configured as reportConfig1, reportConfig2, ..., reportConfigM. Each ReportConfig can include an eventId and other report-related configuration information (other fields) 422.

[0154] refer to Figure 4 , measId 410 may have an associated relationship with one MO ( MO1 ) 400 indicated by MeasIdToAddMod and one reportConfig ( reportConfig1 ) 420 indicated by MeasIdToAddMod.

[0155] For example, MO 400 may include measurement frequency (ssbFrequency) 401 and other measurement object related configuration information (other fields 402 ). reportConfig 420 may include trigger event configuration information (eventId) 421 and other report related configuration information (other fields 422 ).

[0156] For example, an MO can be associated with one or more measIds, and a reportConfig can be associated with one or more measIds. For example, MO 2 can be associated with measId 2 and measId K. For example, reportingConfig 1 can be associated with measId 1 and measId 2.

[0157] According to the existing NR standard, there is a reportConfig associated with a measId. Therefore, since a trigger event is indicated in the reportConfig, a specific measId can have only one measurement report triggering event.

[0158] However, the base station may need to trigger measurement reports through existing events defined in NR to manage the mobility of UAV terminals only when the UAV terminals are moving at high locations. Therefore, when triggering measurement reports, a new measurement configuration method may be required to configure the measurement reports to be triggered only when both the altitude-based events and the existing events defined in NR are met.

[0159] In the present disclosure, events that are satisfied (or considered) simultaneously may include events that are satisfied (or considered) within the same time interval (e.g., the time interval from t1 to t2), and events that are satisfied (or considered) within different time intervals (e.g., the time interval from t1 to t3 and the time interval from t2 to t4). That is, in the present disclosure, events being satisfied (or considered) simultaneously means that multiple events are satisfied (or considered), but may not mean that the events must be satisfied (or considered) at the same time or at the same time interval.

[0160] According to an embodiment of the present disclosure, when a specific measId has an association relationship with multiple events, a measurement report including the corresponding measId may be triggered by simultaneously considering the multiple events.

[0161] For example, when a specific measId is associated with multiple events, a measurement report including the corresponding measId may be triggered only when entry conditions of the multiple events are all satisfied during a specific time (eg, TimeToTrigger).

[0162] For example, when the sizes of TimeToTrigger corresponding to a plurality of events are different, a measurement report including a corresponding measId may be triggered only when entry conditions of the plurality of events are satisfied during the TimeToTrigger corresponding to each event.

[0163] For example, when the sizes of TimeToTrigger corresponding to multiple events are different, a measurement report including corresponding measId can be triggered only when entry conditions of the multiple events are satisfied within a corresponding time period based on the maximum value among the TimeToTrigger corresponding to each event.

[0164] For example, when the sizes of TimeToTrigger corresponding to multiple events are different, a measurement report including corresponding measId can be triggered only when entry conditions of the multiple events are satisfied within a corresponding time period based on the minimum value among the TimeToTrigger corresponding to each event.

[0165] According to an embodiment of the present disclosure, when a specific measId has an association relationship with multiple events, a measurement report including the corresponding measId may be triggered by simultaneously considering the multiple events.

[0166] For example, when there are multiple events associated with a specific measId and reportOnLeave is configured as TRUE, a measurement report including the corresponding measId can be triggered only when all the leaving conditions of the multiple events with reportOnLeave configured as TRUE are met within a specific time (TimeToTrigger).

[0167] For example, when the sizes of TimeToTrigger corresponding to multiple events for which reportOnLeave is configured as TRUE are different, a measurement report including the corresponding measId may be triggered only when the leaving conditions of the multiple events for which reportOnLeave is configured as TRUE are satisfied during the TimeToTrigger corresponding to each event.

[0168] For example, when the sizes of TimeToTrigger corresponding to multiple events for which reportOnLeave is configured as TRUE are different, a measurement report including the corresponding measId can be triggered only when the leaving conditions of the multiple events for which reportOnLeave is configured as TRUE are all met within the corresponding time period based on the maximum value among the TimeToTrigger corresponding to each event.

[0169] For example, when the sizes of TimeToTrigger corresponding to multiple events for which reportOnLeave is configured as TRUE are different, a measurement report including the corresponding measId can be triggered only when the leaving conditions of the multiple events for which reportOnLeave is configured as TRUE are all met within the corresponding time period based on the minimum value among the TimeToTrigger corresponding to each event.

[0170] Figure 5 is a diagram showing an example of the relationship among measId, MO and reportConfig including a plurality of trigger event configuration information according to an embodiment of the present disclosure. Figure 4 The content shown in the is a detailed description of the content that is repeated.

[0171] refer to Figure 5, a specific measId (measId 1) 500 may be associated with one MO (MO 1) 501 indicated by the corresponding MeasIdToAddMod and one reportConfig (reportConfig 1) 502. In this case, the structure of the reportConfig associated with the corresponding measId may be changed or expanded so that the corresponding measId 500 may have multiple triggering events (eventId 511, heightEventId 512).

[0172] A specific measId may be associated with a reportConfig indicated by the corresponding MeasIdToAddMod. The associated reportConfig may be configured as ReportConfigNR. The reportType of ReportConfigNR may be configured as EventTriggerConfig. EventTriggerConfig may be extended to indicate multiple event configuration information by defining multiple eventId fields in EventTriggerConfig. In this case, a measurement report including the corresponding measId may be triggered by simultaneously considering multiple events indicated by EventTriggerConfig.

[0173] For example, EventTriggerConfig may include two eventId fields.

[0174] For example, the first eventId field may be an eventId indicating one of A1, A2, A3, A4, A5, A6, X1, X2, and D1, and the second eventId field may be an eventId indicating an altitude-based event (one of H1 and H2).

[0175] For example, the first eventId field may be an eventId indicating one of A1, A2, A3, A4, A5, A6, X1, X2, D1, H1, and H2, and the second eventId field may be an eventId indicating one of A1, A2, A3, A4, A5, A6, X1, X2, D1, H1, and H2.

[0176] For example, only one of the first eventId field and the second eventId field may be restricted to indicate an altitude-based event (H1, H2).

[0177] For example, the additionally configured eventId field may or may not exist as an optional field. For example, one of the two eventId fields in EventTriggerConfig may be an optional field.

[0178] For example, the first or second eventId field of EventTriggerConfig (e.g., which may be called heightEventId) may indicate eventH1 or eventH2. In this case, eventH1 may indicate eventH1 configuration information, and eventH2 may indicate eventH2 configuration information. For example, EventTriggerConfig may have an ASN.1 structure as shown in Table 10. For example, EventTriggerConfig may include one or more of the IEs shown in Table 10. Table 10 is an example of the structure of EventTriggerConfig, and the present disclosure is not limited thereto.

[0179] [Table 10]

[0180]

[0181]

[0182]

[0183]

[0184] For example, a specific measId may be associated with the reportConfig indicated by the corresponding MeasIdToAddMod. The associated reportConfig may be configured as ReportConfigNR. The reportType of ReportConfigNR may be configured as a newly defined reportType (e.g., it may be called EventTriggerConfigUAV). EventTriggerConfigUAV may utilize multiple eventId fields to indicate multiple pieces of event configuration information. Therefore, a measurement report including the corresponding measId may be triggered by simultaneously considering multiple events indicated by EventTriggerConfigUAV.

[0185] For example, EventTriggerConfigUAV may include two eventId fields 511 , 512 .

[0186] For example, the first eventId field 511 may be an eventId indicating one of A1, A2, A3, A4, A5, A6, X1, X2, and D1, and the second eventId field 512 may be an eventId field indicating an altitude-based event (one of H1 and H2).

[0187] For example, the first eventId field 511 may indicate one of A1, A2, A3, A4, A5, A6, X1, X2, D1, H1, and H2, and the second eventId field 512 may indicate one of A1, A2, A3, A4, A5, A6, X1, X2, D1, H1, and H2.

[0188] For example, only one of the two eventId fields can be limited to indicating an event based on altitude. For example, one of the two eventId fields can indicate eventH1 or eventH2. In this case, eventH1 can indicate eventH1 configuration information, and eventH2 can indicate eventH2 configuration information.

[0189] For example, in addition to the multiple eventId fields 511 and 512, EventTriggerConfigUAV may further include other report-related fields (other fields) 513. For example, in addition to and / or independently of the multiple eventId fields 511 and 512, EventTriggerConfigUAV may include other report-related fields 513.

[0190] For example, EventTriggerConfigUAV may have an ASN.1 structure as shown in Table 11. For example, EventTriggerConfigUAV may include one or more of the IEs shown in Table 11. Table 11 is an example of the structure of EventTriggerConfigUAV, and the present disclosure is not limited thereto.

[0191] [Table 11]

[0192]

[0193]

[0194]

[0195]

[0196]

[0197] According to the embodiments of the present disclosure described above, since one ReportConfig is connected to one measId, compared with connecting multiple ReportConfigs, there is an advantage in that overlapping fields in each ReportConfig do not need to be configured multiple times on the terminal.

[0198] For example, the EventTriggerConfigUAV may include only one eventId field. For example, the EventTriggerConfigUAV may include one eventId field instead of multiple eventId fields. For example, the EventTriggerConfigUAV may not include other report-related fields besides the one eventId field. For example, the eventId field of the EventTriggerConfigUAV may only indicate events based on altitude.

[0199] For example, EventTriggerConfigUAV may have an ASN.1 structure as shown in Table 12. For example, EventTriggerConfigUAV may include one or more of the IEs shown in Table 12. Table 12 is an example of the structure of EventTriggerConfigUAV, and the present disclosure is not limited thereto.

[0200] [Table 12]

[0201]

[0202] For example, the EventTriggerConfigUAV may include only one eventId field. For example, the EventTriggerConfigUAV may include one eventId field instead of multiple eventId fields. For example, the EventTriggerConfigUAV may not include other report-related fields except for the one eventId field. For example, the eventId field of the EventTriggerConfigUAV may indicate an altitude-based event or all events defined in an existing NR.

[0203] For example, EventTriggerConfigUAV may have an ASN.1 structure as shown in Table 13. For example, EventTriggerConfigUAV may include one or more of the IEs shown in Table 13. Table 13 is an example of the structure of EventTriggerConfigUAV, and the present disclosure is not limited thereto.

[0204] [Table 13]

[0205]

[0206]

[0207]

[0208]

[0209] Figure 6 An example of a structure in which one measId is associated with multiple reportConfigs according to an embodiment of the present disclosure is shown. Figure 4 and Figure 5 Detailed description of the content repeated by the illustrated content.

[0210] refer to Figure 6 , a specific measId (measurement ID) can be associated with one MO and multiple reportConfigs. measId can treat all corresponding events indicated by multiple reportConfigs as measurement report triggering events. Therefore, a measurement report including measId can be triggered by considering multiple events together.

[0211] For example, measurement ID 1 600 may be associated with one MO 1 (601) and two reportConfigs (reportConfig 1 602 and reportConfig 2 603). reportConfig 1 602 may include eventId 611 and other report-related fields (other fields) 612. reportConfig 2 603 may include heightEventId 621 and other report-related fields (other fields) 622. In measurement ID 1 600, eventId 611 and heightEventId 621 indicated in reportConfig 1 602 and reportConfig 2 603 may both correspond to measurement report triggering events.

[0212] According to one embodiment of the present disclosure, measIdToAddModListExt is newly defined, and a corresponding field (for example, it may be called measIdToAddModListExt) may be added to MeasConfig.

[0213] For example, measIdToAddModListExt may include one or more MeasIdToAddModExt.

[0214] For example, MeasIdToAddModExt can be introduced to add new fields to MeasIdToAddMod in addition to the existing fields. In this case, the fields of MeasIdToAddModExt can be interpreted as additional fields of MeasIdToAddMod.

[0215] For example, the number of MeasIdToAddModExt included in measIdToAddModListExt may be the same as the number of measIdToAddMod included in measIdToAddModList included in the same MeasConfig.

[0216] For example, the order of MeasIdToAddModExt included in measIdToAddModListExt may be the same as the order of the corresponding MeasIdToAddMod included in measIdToAddModList. In other words, measIdToAddModListExt may be interpreted as follows.

[0217] If measIdToAddModListExt is configured, it contains the same number of entries as measIdToAddModList, in the same order.

[0218] For example, MeasConfig and MeasIdToAddModListExt may have an ASN.1 structure as shown in Table 14. For example, MeasConfig and MeasIdToAddModListExt may each include one or more of the IEs shown in Table 14. Table 14 is an example of each structure of MeasConfig and MeasIdToAddModListExt, and the present disclosure is not limited thereto.

[0219] [Table 14]

[0220]

[0221]

[0222] For example, a MeasIdToAddModExt may include a reportConfigIdList field that indicates one or more reportConfigs. The reportConfigIdList field may include one or more ReportConfigIds. Accordingly, a specific measId may be associated with both the reportConfig indicated by the corresponding MeasIdToAddMod and the one or more reportConfigs indicated by the corresponding MeasIdToAddModExt.

[0223] For example, when a specific measId has an association relationship with a plurality of reportConfigs, the corresponding measId may have an association relationship with all of the plurality of events indicated by the plurality of associated reportConfigs.

[0224] For example, reportConfigIdList of MeasIdToAddModExt is an optional field and may or may not exist.

[0225] For example, MeasIdToAddModExt may have the following ASN.1 structure. For example, MeasIdToAddModExt may include one or more IEs shown in Table 15. Table 15 is an example of the structure of MeasIdToAddModExt, and the present disclosure is not limited thereto.

[0226] [Table 15]

[0227]

[0228] For example, when a specific measId is associated with multiple reportConfigs, the field configured multiple times may exist as a field common to the multiple reportConfigs (a common field). In this case, for example, the base station may configure the common field to have the same value in all reportConfigs. For example, when the common field has a numerical value, it may be configured based on the minimum value among the values ​​configured for the corresponding field in the multiple reportConfigs when performing a measurement report including the corresponding measId. In other words, the value of the common field may be configured based on the minimum value among the values ​​configured in the multiple reportConfigs. For example, when the common field has a numerical value, it may be configured based on the maximum value among the values ​​configured for the corresponding field in the multiple reportConfigs when performing a measurement report including the corresponding measId. In other words, the value of the common field may be configured based on the maximum value among the values ​​configured in the multiple reportConfigs.

[0229] For example, when a specific measId is associated with multiple reportConfigs, one of the multiple reportConfigs is considered a reference reportConfig, and measurement reporting can be performed based on the reference reportConfig. For example, the reference reportConfig can be the reportConfig indicated by MeasIdToAddMod corresponding to the corresponding measId. For example, the base station can explicitly indicate the reference reportConfig by adding a new field (e.g., refReportConfigId) to the measConfig.

[0230] For example, when a specific measId is associated with multiple reportConfigs, a method for resolving problems caused by common fields of multiple reportConfigs can be provided. For example, when a specific measId is associated with multiple reportConfigs, the reportType of only one reportConfig can be configured as EventTriggerConfig, and the reportType of the other reportConfigs can be configured as EventTriggerConfigUAV, which is a new reportType. For example, EventTriggerConfigUAV can include only one eventId field. For example, the eventId field of EventTriggerConfigUAV can only indicate events based on altitude. For example, the eventId field of EventTriggerConfigUAV can indicate an event based on altitude and one of all events defined in the NR standard.

[0231] According to the embodiments of the present disclosure described above, when a new measId is allocated, a pre-configured reportConfig can be reused, thereby providing an advantage of flexible base station configuration. Furthermore, in terms of terminal implementation, there may be an advantage in that multiple reportConfigs can be easily identified as being associated with one measId.

[0232] Figure 7 An example of a structure in which one measId according to an embodiment of the present disclosure can be associated with events indicated in multiple reportConfigs is shown. Figures 4 to 6 The content shown duplicates a detailed description of the content.

[0233] refer to Figure 7, a specific reportConfig may be configured as ReportConfigNR, and the reportType of ReportConfigNR may be configured as EventTriggerConfig. A measId list (for example, which may be referred to as relatedMeasIdList) indicating one or more measIds is added to EventTriggerConfig, so that an association relationship may be additionally configured between each measId included in the relatedMeasIdList and an event indicated by EventTriggerConfig. In this case, each measId included in the relatedMeasIdList may have an association relationship with both the event of the reportConfig indicated by the corresponding measIdToAddMod and the event of the EventTriggerConfig including the relatedMeasIdList. For example, a measId list (for example, which may be referred to as relatedMeasIdList) indicating one or more measIds is added to EventTriggerConfig, so that an association relationship may be additionally established between each measId included in the corresponding relatedMeasIdList and the reportConfig including the corresponding EventTriggerConfig.

[0234] For example, relatedMeasIdList of EventTriggerConfig is an optional field and may or may not exist.

[0235] For example, when relatedMeasIdList includes a plurality of measIds, all of the plurality of measIds may have an association relationship with the event of the EventTriggerConfig including the relatedMeasIdList.

[0236] refer to Figure 7, measId1 (measurement ID 1) 700 may be associated with the event (eventId) 711 of the ReportConfig (reportConfig 1 710) indicated by the corresponding measIdToAddMod. ReportConfig 1 710 may include eventId 711 and other report-related fields (other fields) 712. ReportConfig 2 720 may include relatedMeasIdList in EventTriggerConfig, and in this case, measId 1 723 may be included in the corresponding fields (i.e., ReportConfig 2 720 may include eventId 721, other report-related fields 722, and relatedMeasIdList (including measId 1 723)). Therefore, measId 1 may be associated with the event corresponding to eventId of the EventTriggerConfig including the relatedMeasIdList. Consequently, measId 1 may have two measurement report triggering events 711 and 721. For example, an EventTriggerConfig including relatedMeasIdList may indicate only altitude-based events. For example, an EventTriggerConfig including relatedMeasIdList may indicate an altitude-based event and one of all (or at least some) events defined in the NR. For example, an EventTriggerConfig including relatedMeasIdList may have an ASN.1 structure as shown in Table 16. For example, an EventTriggerConfig including relatedMeasIdList may include one or more of the IEs shown in Table 16. Table 16 is an example of the structure of an EventTriggerConfig including relatedMeasIdList, and the present disclosure is not limited thereto.

[0237] [Table 16]

[0238]

[0239]

[0240]

[0241]

[0242] According to the embodiments of the present disclosure described above, since there is no need to introduce a new MeasIdToAddModListExt, there may be an advantage in that signaling overhead is relatively small.

[0243] According to an embodiment of the present disclosure, multiple MeasIdToAddMods included in the measIdToAddModList of a measConfig may indicate the same measId. For example, multiple MeasIdToAddMods indicating the same measId may have the same measObjectId. For example, multiple MeasIdToAddMods indicating the same measId may have different reportConfigIds. In this case, the corresponding measId may be associated with the multiple reportConfigIds indicated by the corresponding multiple MeasIdToAddMods.

[0244] According to an embodiment of the present disclosure, a new event may be defined by integrating an altitude-based event and existing events defined in the NR standard.

[0245] For example, when defining a new event by integrating multiple events, the entry conditions of the newly defined event can be configured so that all entry conditions of the integrated event are met (reached) at the same time. For example, the exit conditions of the newly defined event can be configured so that all exit conditions of the integrated event are met at the same time.

[0246] For example, a new event K can be defined by integrating an altitude-based event Hn (n is 1 or 2) and an event Ax (x can be one of 1, 2, 3, 4, 5, and 6). For example, the entry conditions of the new event K can be defined to include both the entry conditions of event Hn and the entry conditions of event Ax, such that the entry conditions of event K are satisfied only when both entry conditions are satisfied. For example, the exit conditions of the new event K can be defined to include both the exit conditions of event Hn and the exit conditions of event Ax, such that the exit conditions of event K are satisfied only when both exit conditions are satisfied.

[0247] Through the embodiments of the present disclosure described above, a specific measId is associated with one event, but because the corresponding event integrates multiple events, the same effect of being associated with the multiple events can be obtained.

[0248] Figure 8 An example of a process in which a UAV terminal sends a measurement report to a base station in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0249] refer to Figure 8In operation 820, the UAV terminal 800 may establish an RRC connection with the NR base station 810 and be in RRC connection mode (RRC_CONNECTED).

[0250] In operation 830, the terminal may send a terminal capability information message (UECapabilityInformation) to the base station. The terminal capability information message may include information regarding whether the terminal supports at least some of the methods provided in the embodiments of the present disclosure. For example, according to an embodiment of the present disclosure, the terminal capability information message may include whether a configuration function (multiEventExtention) in which a measId is associated with multiple events is supported.

[0251] In operation 840, if the terminal supports the multiEventExtention function, the base station may configure a specific measId to have an association relationship with multiple events through measConfig.

[0252] In operation 850, the terminal configured by measConfig may perform a measurement operation. In operation 860, the terminal may trigger a measurement report including a specific measId by considering multiple events associated with the corresponding measId. In operation 870, the terminal may perform measurement reporting.

[0253] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of operations, the various operations in each figure can overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, an operation can be omitted or replaced by another operation.

[0254] Figure 9 The structure of a terminal according to an embodiment of the present disclosure is shown.

[0255] refer to Figure 9 , the terminal 900 may include a transceiver 920, a controller 910, and a memory 930. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0256] The transceiver 920 may transmit and receive signals to and from other network entities. The transceiver 920 may receive, for example, system information from a base station and may receive a synchronization signal or a reference signal.

[0257] The controller 910 may control the overall operation of the terminal 900 according to the embodiments provided in the present disclosure. For example, the controller 910 may control the transceiver 920 or the memory 930 to perform operations according to the embodiments described above. Specifically, according to the embodiments of the present disclosure, the controller 910 may control the transceiver 920 to transmit and receive configuration information, control information, or data with a base station.

[0258] The memory 930 may store at least one of information transmitted and received by the transceiver 920 and information generated by the controller 910 .

[0259] Figure 10 The structure of a base station according to an embodiment of the present disclosure is shown.

[0260] refer to Figure 10 , the base station 1000 may include a transceiver 1020, a controller 1010, and a memory 1030. In the present disclosure, the controller 1010 may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0261] The transceiver 1020 may send signals to and receive signals from other network entities. The transceiver 1020 may send, for example, system information to the UE and may send a synchronization signal or a reference signal.

[0262] The controller 1010 may control the overall operation of the base station 1000 according to the embodiments provided in the present disclosure. For example, the controller 1010 may control the transceiver 1020 or the memory 1030 to perform operations according to the embodiments described above. Specifically, according to the embodiments of the present disclosure, the controller 1010 may control the transceiver 1020 to transmit and receive configuration information, control information, or data with the terminal.

[0263] The memory 1030 may store at least one of information transmitted and received by the transceiver 1020 and information generated by the controller 1010 .

[0264] Although the figures illustrate different examples of user devices, various changes may be made to the figures. For example, the user devices may include any number of each component in any suitable arrangement. Generally, the figures do not limit the scope of the present disclosure to any particular configuration. Furthermore, although the figures illustrate operating environments in which various user device features disclosed in the patent documents can be used, these features can be used in any other suitable system.

[0265] Although the present disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover such changes and modifications as fall within the scope of the appended claims. Nothing in this application should be construed as implying that any particular element, operation, or function is essential to the scope of the claims. The scope of a patented subject matter is defined by the claims.

[0266] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a communication system, the method comprising: receiving measurement configuration information including information about a predefined event, wherein the predefined event corresponds to a first event and a second event; identifying, based on the predefined event, whether an entry condition of the predefined event is satisfied, wherein the entry condition is satisfied if both a first entry condition of the first event and a second entry condition of the second event are satisfied; and Based on the identification, a measurement report is sent.

2. The method according to claim 1, wherein The first event is associated with a measurement of a cell, and the second event is associated with an altitude of the UE.

3. The method according to claim 1, wherein The first event is one of event A3, event A4 and event A5, and The second event is one of event H1 and event H2.

4. The method according to claim 1, further comprising: Based on the predefined event, an exit condition of the predefined event is identified, wherein the exit condition is satisfied when both a first exit condition of the first event and a second exit condition of the second event are met.

5. The method according to claim 1, wherein The information about the predefined event includes a first set of configuration parameters for the first event and a second set of configuration parameters for the second event.

6. A user equipment (UE) in a communication system, the UE comprising: transceiver; as well as a processor coupled to the transceiver and configured to: receiving measurement configuration information including information about a predefined event, wherein the predefined event corresponds to a first event and a second event; identifying, based on the predefined event, whether an entry condition of the predefined event is satisfied, wherein the entry condition is satisfied if both a first entry condition of the first event and a second entry condition of the second event are satisfied; and Based on the identification, a measurement report is sent.

7. The UE according to claim 6, wherein: The first event is associated with a measurement of a cell, and the second event is associated with an altitude of the UE.

8. The UE according to claim 6, wherein: The first event is one of event A3, event A4 and event A5, and The second event is one of event H1 and event H2.

9. The UE according to claim 6, wherein: The processor is further configured to identify, based on the predefined event, whether an exit condition of the predefined event is met, wherein the exit condition is met if both a first exit condition of the first event and a second exit condition of the second event are met.

10. The UE according to claim 6, wherein: The information about the predefined event includes a first set of configuration parameters for the first event and a second set of configuration parameters for the second event.

11. A method performed by a base station in a wireless communication system, the method comprising: Sending measurement configuration information including a predefined event, wherein the predefined event corresponds to a first event and a second event; and receiving a measurement report associated with the measurement configuration information, Wherein, when both the first entry condition of the first event and the second entry condition of the second event are met, the entry condition of the predefined event is satisfied.

12. The method according to claim 11, wherein The first event is associated with a measurement of a cell, and the second event is associated with an altitude of a user equipment (UE).

13. A base station in a wireless communication system, the base station comprising: transceiver; as well as a processor coupled to the transceiver and configured to: Sending measurement configuration information including a predefined event, wherein the predefined event corresponds to a first event and a second event; and receiving a measurement report associated with the measurement configuration information, Wherein, when both the first entry condition of the first event and the second entry condition of the second event are met, the entry condition of the predefined event is satisfied.

14. The base station according to claim 13, wherein: The first event is associated with a measurement of a cell, and the second event is associated with an altitude of a user equipment (UE).

15. The base station according to claim 13, wherein: The first event is one of event A3, event A4h and event A5, The second event is one of event H1 and event H2.

Images