Method by which user equipment performs communication in wireless communication system and apparatus therefor

Abstract

Disclosed are a method performed by a user equipment (UE), according to various embodiments, and an apparatus therefor. Disclosed are a method and an apparatus therefor, the method comprising the steps of: measuring interference in a connection between a UE and a base station; and reporting, to the base station, interference information including the interference strength of the measured interference.

Description

Method for a terminal to perform communication in a wireless communication system and device therefor

[0001] This relates to a method for a terminal to perform communication in a wireless communication system and a device therefor.

[0002] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0005] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive machine type communication (MTC), and ultra-reliable and low latency communication (URLLC) can be called new radio access technology (RAT) or new radio (NR). NR can also support vehicle-to-everything (V2X) communication.

[0006] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0007] In relation to V2X communication, in RATs prior to NR, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) were mainly discussed. V2X messages may include location information, dynamic information, attribute information, etc. For example, a terminal may transmit a CAM of a periodic message type and / or a DENM of an event triggered message type to another terminal.

[0008] For example, a CAM may include basic vehicle information such as dynamic vehicle status information, such as direction and speed, static vehicle data, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast a CAM, and the latency of the CAM may be less than 100 ms. For example, in the event of an emergency, such as a vehicle breakdown or accident, a terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0009] Since then, various V2X scenarios have been proposed in NR in relation to V2X communications. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0010] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles in the group can receive periodic data from the lead vehicle. For example, vehicles in the group can use this periodic data to narrow or widen the gap between vehicles.

[0011] For example, based on improved driving, vehicles can become semi-autonomous or fully automated. For example, each vehicle can adjust its trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0012] For example, based on extended sensors, raw data, processed data, or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers. Thus, for example, a vehicle can perceive its environment better than it can perceive using its own sensors.

[0013] For example, based on remote driving, a remote driver or V2X application can operate or control the remote vehicle for people who cannot drive or for remote vehicles located in hazardous environments. For example, in cases where the route is predictable, such as public transportation, cloud computing-based driving can be utilized to operate or control the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0014] Meanwhile, a method to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, expanded sensors, and remote driving, is being discussed in NR-based V2X communication.

[0015] The technical problem to be solved by the present invention is to provide a method for performing communication more accurately and efficiently.

[0016] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0017] A method by a UE (user equipment) according to one aspect includes the steps of measuring interference for a connection between the UE and a base station; and the step of reporting interference information including an interference intensity of the measured interference to the base station, wherein based on the interference being related to a mobile IAB (integrated access backhaul) node, the interference information may further include location information of the mobile IAB node.

[0018] Alternatively, the interference information is characterized in that it further includes information on the amount of change in signal strength of the mobile IAB node.

[0019] Alternatively, the location information of the mobile IAB node is characterized by including information on the estimated location and height of the mobile IAB node measured by the UE.

[0020] Alternatively, the interference information is characterized in that it further includes mobility information for the UE.

[0021] Alternatively, the interference information is characterized in that it further includes at least one of a cell ID (identifier), a Public Land Mobile Network (PLMN) and information about a donor IAB node associated with the mobile IAB node.

[0022] Alternatively, based on the UE being connected to the mobile IAB node, the UE is characterized in that it transmits a message related to position adjustment of the mobile IAB node to the mobile IAB node.

[0023] Alternatively, the mobile IAB node is characterized as an IAB node that moves via an Unmanned Aerial Vehicle (UAV).

[0024] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the method described above may be provided.

[0025] According to another aspect, a UE performing the above-described method may be provided.

[0026] According to another aspect, a processing device may be provided for controlling a UE performing the above-described method.

[0027] A method performed by a base station according to another aspect may include the steps of: receiving interference information from a user equipment (UE) including an interference strength for interference measured for a connection between the UE and the base station; and transmitting a message requesting a change of location of a mobile integrated access backhaul (IAB) node to a mobile IAB node or a donor node of the mobile IAB node based on the interference information further including location information of the mobile IAB node.

[0028] According to another aspect, a base station performing the above-described method may be provided.

[0029] According to one embodiment, communication can be performed more accurately and efficiently in a wireless communication system.

[0030] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0031] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0032] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0033] Figure 2 shows the structure of the LTE system.

[0034] Figure 3 shows the structure of the NR system.

[0035] Figure 4 shows the structure of a radio frame of NR.

[0036] Figure 5 shows the slot structure of an NR frame.

[0037] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0038] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0039] Figure 8 shows a radio protocol architecture for SL communication.

[0040] Figure 9 shows a terminal performing V2X or SL communication.

[0041] Figure 10 shows resource units for V2X or SL communication.

[0042] FIG. 11 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0043] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0044] Figure 13 is a diagram for explaining the control plane procedure of L2 U2N relay (UE-to-Network Relay).

[0045] Figure 14 is a drawing for explaining the U2X system.

[0046] Figures 15 and 16 are drawings for briefly explaining the IAB node.

[0047] FIGS. 17 and 18 are drawings illustrating a method for adjusting the position of a UAV mobile IAB node.

[0048] FIG. 19 is a diagram illustrating a method for a UE to report indirect information related to a mobile IAB node to a base station.

[0049] FIG. 20 is a diagram illustrating a method for a base station to adjust the location of a mobile IAB node based on indirect information related to the mobile IAB node.

[0050] Figure 21 illustrates a communication system applied to the present invention.

[0051] Figure 22 illustrates a wireless device applicable to the present invention.

[0052] Figure 23 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0053] Figure 24 illustrates a vehicle or autonomous vehicle to which the present invention is applied.

[0054] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0055] Sidelink refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). Sidelink is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0056] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0057] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0058] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0059] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0060] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0061] Figure 2 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0062] Referring to FIG. 2, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0063] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0064] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0065] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0066] Figure 3 shows the structure of the NR system.

[0067] Referring to FIG. 3, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, the gNB is connected to the access and mobility management function (AMF) via the NG-C interface, and the gNB is connected to the user plane function (UPF) via the NG-U interface.

[0068] Figure 4 shows the structure of a radio frame of NR.

[0069] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0070] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0071] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0072] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0073] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0074] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0075] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0076] In NR, multiple numerologies, or SCSs, can be supported to support various 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60 kHz or higher SCS can support bandwidths greater than 24.25 GHz to overcome phase noise.

[0077] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0078] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0079] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0080] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0081] Figure 5 shows the slot structure of an NR frame.

[0082] Referring to Figure 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0083] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0084] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0085] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0086] New network characteristics in 6G may include:

[0087] - Satellite integrated network

[0088] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).

[0089] - Seamless integration of wireless information and energy transfer

[0090] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.

[0091] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:

[0092] - small cell networks

[0093] - Ultra-dense heterogeneous network

[0094] - High-capacity backhaul

[0095] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0096] - Softwarization and virtualization

[0097] Below, the core implementation technologies of the 6G system are described.

[0098] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0099] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0100] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0101] - Large-scale MIMO technology

[0102] - Hologram beamforming (HBF)

[0103] - Optical wireless technology

[0104] - Free-space optical transmission backhaul network (FSO backhaul network)

[0105] - Quantum communication

[0106] - Cell-free communication

[0107] - Integration of wireless information and power transmission

[0108] - Integration of wireless communication and sensing

[0109] - Integrated access and backhaul network

[0110] - Big data analysis

[0111] - Reconfigurable intelligent surface

[0112] - metaverse

[0113] - Blockchain

[0114] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0115] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0116] Figure 8 illustrates a radio protocol architecture for SL communication. Specifically, Figure 8 (a) illustrates the user plane protocol stack of NR, and Figure 8 (b) illustrates the control plane protocol stack of NR.

[0117] Below, the SL synchronization signal (Sidelink Synchronization Signal, SLSS) and synchronization information are described.

[0118] SLSS is an SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may detect an initial signal and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and the S-SSS.

[0119] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in NR V2X, for evaluating PSBCH performance, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0120] S-PSS, S-SSS, and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in frequency to discover the S-SSB in the carrier.

[0121] Meanwhile, in the NR SL system, multiple numerologies having different SCS and / or CP lengths may be supported. In this case, as the SCS increases, the length of the time resource for a transmitting terminal to transmit an S-SSB may become shorter. Accordingly, the coverage of the S-SSB may decrease. Therefore, in order to ensure the coverage of the S-SSB, the transmitting terminal may transmit one or more S-SSBs to a receiving terminal within one S-SSB transmission period according to the SCS. For example, the number of S-SSBs that the transmitting terminal transmits to the receiving terminal within one S-SSB transmission period may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission period may be 160 ms. For example, an S-SSB transmission period of 160 ms may be supported for all SCSs.

[0122] For example, when the SCS is 15 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 30 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 60 kHz at FR1, the transmitting terminal can transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission period.

[0123] For example, when the SCS is 60 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, or 32 S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 120 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, 32, or 64 S-SSBs to the receiving terminal within one S-SSB transmission period.

[0124] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. In addition, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may be different depending on the CP type. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, when the CP type is NCP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, when the CP type is ECP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, the PSBCH may be mapped to the first symbol within the S-SSB transmitted by the transmitting terminal. For example, the receiving terminal receiving the S-SSB may perform an Automatic Gain Control (AGC) operation in the first symbol section of the S-SSB.

[0125] Figure 9 shows a terminal performing V2X or SL communication.

[0126] Referring to FIG. 9, the term "terminal" in V2X or SL communication may primarily refer to a user's terminal. However, if a network device such as a base station transmits and receives signals according to a communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0127] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect a signal from terminal 1 within the resource pool.

[0128] Here, if terminal 1 is within the connection range of the base station, the base station can inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal can inform terminal 1 of the resource pool, or terminal 1 can use a pre-configured resource pool.

[0129] In general, a resource pool can be composed of multiple resource units, and each terminal can select one or multiple resource units to use for its SL signal transmission.

[0130] Figure 10 shows resource units for V2X or SL communication.

[0131] Referring to Figure 10, the entire frequency resources of the resource pool can be divided into NF units, and the entire time resources of the resource pool can be divided into NT units. Therefore, a total of NF * NT resource units can be defined within the resource pool. Figure 13 illustrates an example where the resource pool repeats with a cycle of NT subframes.

[0132] As shown in Figure 10, a single resource unit (e.g., Unit #0) may appear periodically and repeatedly. Alternatively, to achieve diversity effects in the time or frequency dimensions, the index of the physical resource unit to which a single logical resource unit is mapped may change in a predetermined pattern over time. In this resource unit structure, a resource pool may refer to a set of resource units that a terminal wishing to transmit an SL signal can use for transmission.

[0133] Resource pools can be subdivided into several categories. For example, based on the content of the SL signal transmitted from each resource pool, resource pools can be categorized as follows:

[0134] (1) Scheduling Assignment (SA) may be a signal that includes information such as the location of resources used by a transmitting terminal for transmission of an SL data channel, MCS (Modulation and Coding Scheme) or MIMO (Multiple Input Multiple Output) transmission method required for demodulation of other data channels, and TA (Timing Advance). SA may also be transmitted multiplexed with SL data on the same resource unit, in which case the SA resource pool may mean a resource pool in which SA is multiplexed with SL data and transmitted. SA may also be called an SL control channel.

[0135] (2) The SL data channel (Physical Sidelink Shared Channel, PSSCH) may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted together with SL data on the same resource unit, only the SL data channel excluding SA information may be transmitted from the resource pool for the SL data channel. In other words, the REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool may still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.

[0136] (3) A discovery channel may be a resource pool for transmitting terminals to transmit information such as their IDs. Through this, transmitting terminals can enable neighboring terminals to discover them.

[0137] Even if the content of the SL signal described above is the same, different resource pools may be used depending on the transmission and reception properties of the SL signal. For example, even if it is the same SL data channel or discovery message, it may be again divided into different resource pools depending on the transmission timing determination method of the SL signal (for example, whether it is transmitted at the time of reception of a synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the resource allocation method (for example, whether the base station designates transmission resources for individual signals to individual transmitting terminals or whether individual transmitting terminals independently select individual signal transmission resources within the resource pool), the signal format (for example, the number of symbols each SL signal occupies in one subframe or the number of subframes used for transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

[0138] FIG. 11 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 11, it is assumed that there are three BWPs.

[0139] Referring to Figure 11, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0140] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and Point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0141] SLSS (Sidelink Synchronization Signal) is a SL (sidelink) specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal) and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS and length-127 Gold sequences may be used for S-SSS. For example, a terminal may detect an initial signal (signal detection) and obtain synchronization using S-PSS. For example, the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.

[0142] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0143] S-PSS, S-SSS, and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in frequency to discover the S-SSB in the carrier.

[0144] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0145] Referring to (a) of FIG. 12, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S1200, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0146] For example, a first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures / allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures / allocates to the first terminal via DCI and / or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.

[0147] In step S1510, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S1240, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

[0148] Referring to (b) of FIG. 12, in resource allocation mode 2, a terminal can determine an SL transmission resource within the SL resources set by the base station / network or within the preset SL resources. For example, the set SL resources or the preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting a resource within the set resource pool. For example, the terminal can select a resource within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S1210, a first terminal that has selected a resource within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal using the resource. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0149] Referring to (a) or (b) of FIG. 12, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0150] Referring to (a) or (b) of FIG. 12, in step S1530, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

[0151] Referring to (a) of FIG. 12, in step S1540, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0152] Figure 13 is a diagram for explaining the control plane procedure of L2 U2N relay (UE-to-Network Relay).

[0153] The PC5-RRC aspect PC5 unicast link establishment procedure of Rel-16 NR V2X can be reused to establish a secure unicast link for L2 U2N relay (layer 2 UE-to-Network relaying) between the remote UE and the relay UE before the remote UE establishes a Uu RRC connection with the network via the relay UE.

[0154] For both in-coverage and out-of-coverage scenarios, when a remote UE initiates the first RRC message to establish a connection with a gNB, the PC5 L2 configuration for transmissions between the remote UE and the U2N relay UE can be based on the RLC / MAC configuration defined in the standard. The establishment of Uu SRB1 / SRB2 and DRB of the remote UE follows the legacy Uu configuration procedure for the L2 U2N relay.

[0155] A given scenario (TS 38.300) describes the control plane procedures of an L2 U2N relay as follows:

[0156] In step S1300, the remote UE and relay UE can perform a discovery procedure and establish a PC5-RRC connection in step S1301 based on the existing Rel-16 procedure.

[0157] In step S1302, the remote UE can transmit the first RRC message (i.e., RRCSetupRequest) to establish a connection with the gNB via the relay UE using the default L2 configuration of PC5. The gNB responds to the remote UE with an RRCSetup message (S1303). The RRCSetup delivery to the remote UE uses the default configuration of PC5. If the relay UE is not initiated in RRC_CONNECTED, it must perform its own connection establishment upon receiving the message for the default L2 configuration of PC5.

[0158] In step S1304, the gNB and the relay UE perform a relay channel setup procedure via Uu. Depending on the configuration of the gNB, the relay / remote UE establishes an RLC channel for relaying SRB1 to the remote UE via PC5. This step prepares the relay channel for SRB1.

[0159] In step S1305, a remote UE SRB1 message (e.g., an RRCSetupComplete message) is transmitted to the gNB via the relay UE using the SRB1 relay channel over PC5. The remote UE is then RRC connected over Uu.

[0160] In steps S1306 and S1307, the remote UE and the gNB establish security according to legacy procedures, and the security message is transmitted through the Relay UE.

[0161] In steps S1308 and S1309, the gNB transmits RRCReconfiguration to the remote UE via the relay UE to set up the relay SRB2 / DRB. The remote UE responds by transmitting RRCReconfigurationComplete to the gNB via the relay UE.

[0162] In step S1310, the gNB establishes an additional RLC channel between the gNB and the relay UE for traffic relay. Depending on the configuration of the gNB, the relay / remote UE establishes an additional RLC channel between the remote UE and the relay UE for traffic relay.

[0163] In the above scenario, in addition to the connection setup procedure, for L2 UE-to-Network relay:

[0164] - RRC reconfiguration and RRC disconnection procedures can reuse legacy RRC procedures with message content / configuration design left in the WI phase.

[0165] - The RRC connection re-establishment and RRC connection resumption procedures can be reused as a baseline by considering the connection establishment procedure of the L2 U2N relay above to handle relay-specific parts along with the message content / structure design. The message content / structure can be defined later.

[0166] UAV (Unmanned Aerial Vehicle)-to-everything (U2X)

[0167] Figure 14 is a drawing for explaining the U2X system.

[0168] The key points of the proposed U2X solution in the given scenario (TR 23.700-58) are as follows:

[0169] - U2X can support BRID and Direct DAA by leveraging the V2X mechanism defined in TS 23.287. In this case, both LTE PC5 and NR PC5 defined in TS 23.285 are supported, and RAT selection can be performed based on U2XP.

[0170] - Communication mode: BRID (Broadcasting UAV identification) can use Broadcast communication mode. DAA can use Broadcast communication mode to advertise UAV information. Broadcast via PC5 or unicast via PC5 can be used between two or more UAVs for DAA de-collision. Unicast via Uu via U2X AS may not be supported in the above-mentioned U2X solution. Groupcast mode for NR-based PC5 may not be supported in the above-mentioned U2X solution. When NR PC5 is selected, connectionless groupcast communication can be used for DAA. Meanwhile, application layer managed groupcast may not be considered in this release due to lack of clear requirements.

[0171] - U2X can be supported by a U2X Application Server that interfaces with the operator network via NEF, as in the case of a V2X Application Server.

[0172] Meanwhile, the above given scenario / solution needs to allow for multiple deployment scenarios where a dedicated service set can be defined and the U2X AS and USS providing the UAV are the same or different entities.

[0173] - A U2X policy (U2XP) can be defined to provide configuration parameters to a UE for U2X communication via a PC5 reference point or a Uu reference point. The configuration parameters can be preset in a Mobile Equipment (ME), set in a universal IC card (UICC), pre-set in the ME and set in the UICC, provided / updated by a U2X application server via a policy control function (PCF) and / or a V1 reference point, or provided / updated to the UE by the PCF. Here, the UE needs to consider the U2X policies in the following order of priority: those provided / updated by the PCF, those provided / updated by the U2X application server via the V1 reference point, those configured in the UICC, and those pre-configured in the ME. A de-conflicting policy can be a policy indicating a communication mode for de-conflicting (unicast or broadcast), a communication frequency for de-conflicting, etc.

[0174] - As with V2X, the Tx profile or NR Tx profile can be determined based on the U2XP mapping of the U2X service type.

[0175] - Both UAVs with UICC and UAVs without UICC (i.e. not subscribed to an MNO) can be supported. Here, UAVs without UICC can perform U2X communication only if they are approved as “Not provided in E-UTRA” and “Not provided in NR.”

[0176] - U2X communication parameters of the U2X application server or PCF can be transmitted via the UAV-C UE.

[0177] - In addition to the existing parameters for V2X, PC5 RAT-specific radio parameters (e.g., LTE PC5, NR PC5) may be configured, including geographic area, altitude restrictions, and validity timers. Such additional information / parameters may be required to policy-specifically control PC5 usage based on the specific location of the UAV.

[0178] - The definition of DAA / UAV service types may go beyond the scope of the given scenarios described above.

[0179] - For UAVs with UICC to use PC5-based communications for BRID and DAA, successful UUAA authentication / authorization as defined in TS 23.256 and authorization via U2XP are required. However, the FAA does not require specific authorization for the use of PC5 for BRID or DAA. For UAVs without UICC, the use of PC5-based communications for BRID and DAA can only be authorized via U2XP. Meanwhile, U2X services can be identified by one of the following values ​​specifically defined for aviation applications: ITS Application Identifier (ITS-AID), Provider Service Identifier (PSID), or Application Identifier (AID).

[0180] - As in TS 23.287, security for broadcast U2X communications over the PC5 reference point can be supported in U2X application layer schemes developed in other SDOs.

[0181] Referring to FIG. 14, a non-roaming 5G system architecture for U2X communication via PC5 can be configured as illustrated in FIG. 14. Here, the non-roaming 5G system architecture for U2X communication via PC5 can be applied with the reference point of TS 23.287, and the following differences may exist.

[0182] - U2X1: As a reference point between the UE and the UAV-C and the U2X application of the U2X application server, this reference point may be outside the scope of the above-mentioned scenario.

[0183] - U2X5: As a reference point between U2X applications within the UE, this reference point may / may not be specified in the release of a given scenario.

[0184] - N1: In addition to the relevant functions defined in TS 23.501 for N1, it can also be used to transfer U2X policies and parameters (including service authorization) from AMF to UE for U2X services, and PC5 functions for U2X capabilities and U2X information of UE to AMF.

[0185] - N2: In addition to the relevant functions defined in TS 23.501 for N2, it can also be used to convey U2X policies and parameters (including service authorization) from AMF to NG-RAN for U2X services.

[0186] - The above-described solution can support UAV UEs utilizing Uu connections and UAV UEs that do not utilize Uu connections (i.e., UAV UEs that are either Uu capable or Uu non-capable). UAVs that do not utilize Uu capabilities can use U2X for BRID and DAA and can be configured via U2X1 for transmissions outside the scope of 3GPP. On the other hand, UAV UEs that do not utilize Uu capabilities can be part of the 3GPP ecosystem as they use U2X1 for configuration by U2X application servers and implement PC5 connections as specified by 3GPP.

[0187] A 5G system architecture between Public Land Mobile Networks (PLMNs) for U2X communication over PC5 reference points could be as follows.

[0188] - For U2X communication between PLMNs via PC5 reference point, PC5 parameters need to be set in a consistent manner between UEs within a specific area.

[0189] - The architecture for Inter-PLMN PC5 may be similar to that defined in the non-roaming 5G system architecture for U2X communication over PC5 described with reference to FIG. 14.

[0190] AF-based service parameter provisioning for U2X communication can be defined as follows.

[0191] - As defined in TS 23.287, 5G systems may provide NEF services to enable communication between NFs and U2X application servers in PLMNs. Service parameters may also be pre-configured on the UAV using methods outside the scope of 3GPP (e.g., when not utilizing Uu functionality).

[0192] In a U2X scenario, the following may be considered:

[0193] - Usage / Usage of U2X for BRID: Message content for BRID can be defined according to regional regulations for BRID (e.g. message sets of ASTM F3411.19 or ASD-STAN prEN 4709-002 P1) and optionally according to regional means in compliance documents.

[0194] - Usage / Usage of U2X for DAA: Message content for DAA is defined by local regulations for DAA and may go beyond the scope of the given scenarios described above.

[0195] The impact on services, entities and interfaces related to the above-described U2X may be as shown in Tables 5 and 6 below.

[0196] 1. UE: In addition to the capabilities defined in the given scenario (TS 23.501), the UE may support the following capabilities:- Report U2X capabilities (including DAA capabilities) and PC5 capabilities to the 5GC via the N1 reference point.- Indicate U2X policy provisioning requests in the UE policy container for UE-triggered U2X policy provisioning.- Receive U2X parameters from the 5GC via the N1 reference point.- U2X communication procedures via the PC5 reference point.- Configuration of parameters for U2X communication. The parameters may be pre-configured in the UE or may be provisioned or updated by signalling from the PCF in the HPLMN via the N1 reference point or from the U2X application server via the U2X1 reference point, if applicable. 2. AMF: In addition to the functions defined in the given scenario (TS 23.501), the AMF may:- Obtain subscription information related to U2X from the UDM and store it as part of the UE context data.- Select a PCF that supports U2X policy / parameter provisioning and report PC5 capabilities for U2X to the selected PCF.- Obtain PC5 QoS information related to U2X from the PCF and store it as part of the UE context data.- Provide an indication to the NG-RAN about the UE authorization status for U2X communications over the PC5 reference point.- Provide PC5 QoS parameters related to U2X communications to the NG-RAN.- PCF: In addition to the functions defined in the given scenario (TS 23.501), the PCF may include the functions described in the given scenario (TS 23.287) to provide the UE and the AMF with the parameters required to enable U2X communications.- UDM: Subscription management for U2X communications over the PC5 reference point. UE subscription data types can be extended. 3. U2X Application Server: Specific scenarios (TS 23.287) may implement a subset of the V2X AS capabilities specified in: - Includes AF capabilities and may support at least the following capabilities: - For U2X service parameter provisioning, the U2X AS may provide parameters for U2X communication via PC5 and Uu reference points to the 5GC and UAV UE (perhaps via UAVC). - UDR: In addition to the capabilities defined in the given scenario (TS 23.501), the UDR may store U2X service parameters. - NRF: In addition to the capabilities defined in the given scenario (TS 23.501), the NRF may perform PCF lookup taking into account the U2X capabilities. - NEF: In case of a U2X AS, the NEF may support U2X service parameters.

[0197] U2X Subscription data NR U2X Service Authorization Indicates whether the UE is authorized to use NR sidelink for U2X services as a UAV UE, UAV-C UE, or Authority UE. LTE U2X Service Authorization Indicates whether the UE is authorized to use LTE sidelink for U2X services as a UAV UE, UAV-C UE, or Authority UE. NR UE-PC5-AMBRU AMBR of the NR sidelink (i.e., PC5) communications of the UE for 2X services. LTE UE-PC5-AMBRU AMBR of the LTE sidelink (i.e., PC5) communications of the UE for 2X services

[0198] Additionally, recent discussions regarding measurement reporting in relation to the above-described scenarios include:

[0199] - Using LTE principles as a baseline, similar events H1 (aerial UE height becomes higher than threshold) and H2 (aerial UE height becomes lower than threshold) are introduced. FFS: Further discussion on whether additional NR enhancement is needed. Research on scaling of RRM parameters (e.g., which parameters and what is the purpose / benefit of scaling and how).

[0200] -- FFS: How to limit excessive measurement and measurement reporting.

[0201] -- FFS: FFS: Study of vertical movement and related mobility of UAV UEs when user consent is required for location reporting in CONNECTED.

[0202] - Rel-18 NR can support height, position, and velocity reporting from UAV UEs. Further discussion is needed regarding accuracy and reporting mechanisms, as well as whether further improvements are needed.

[0203] - Similar to LTE, flight path planning reporting has been introduced. A list of waypoints (3D position information) and timestamps are adopted as the basic content of flight path reporting. Whether timestamps are mandatory or optional in NR is FFS. Whether further improvements are needed is FFS.

[0204] - A feature similar to LTE (numberofTriggeringCells) has been introduced. FFS: Whether numberoftriggerbeams is required for NR or whether there are other improvements. FFS: How to avoid sending measurement reports primarily due to reportOnLeave.

[0205] - A waypoint is a planned location for a UE along a flight path and is described via the existing parameter type LocationCoordinates defined in a given scenario (TS 37.355).

[0206] - The timestamp provides the UTC time associated with the expected time of arrival at the waypoint as a baseline. FFS: Discussion of granularity.

[0207] - There are no requirements for the spatial distribution of path points.

[0208] - The UE may indicate whether flight plan information is available within the RRCReconfigurationComplete, RRCReestablishmentComplete, RRCResumeComplete, or RRCSetupComplete messages. Flight path reporting may be used as a basis for the UE information request / response procedure.

[0209] - The UE can indicate to the network that a new flight path is available for use by the UE (whether it is initial or update). The normal request / response procedure for flight path reporting can then be reused.

[0210] - The UAI message can also be used to indicate to the UE that a flight path is available.

[0211] - FFS: whether and what triggering conditions are specified for flight update. FFS The maximum number of waypoints within flight path plan is left FFS.

[0212] - When event H1 or H2 is triggered, the content of the measurement report can be configured by the network (i.e. it can contain UAV UE height, location information and / or RSRP / RSRQ measurement results). FFS whether UAV UE's height is mandatorily reported and which parameter / IE is used for height reporting.

[0213] - Joint use of height-dependent conditions and RSRP / RSRQ / SINR-based conditions for triggering measurement reports in NR Rel-18 UAVs may be supported. Combinations of existing events may be used.

[0214] - Height-dependent parameter scaling is not supported as part of Rel-18 NR.

[0215] - The Number of triggering cells mechanism is extended and does not apply to inter-RAT scenarios (i.e. event B1 and B2 triggering).

[0216] - The applicability of the number of triggering cells mechanism is not limited to FR1. That is, the number of triggering cells mechanism can be applied to FR1 and FR2 (depending on the network configuration).

[0217] - The UE shall not ignore or bypass the Number of triggering cells mechanism, once configured.

[0218] - Do not introduce the use of a "numberOfTriggeringBeams" mechanism.

[0219] - Do not introduce an alternative mechanism to the Number of triggering cells mechanism.

[0220] - Do not introduce an additional mechanism based on the number of changed cells.

[0221] - For the purpose of interference control (i.e. for number of trigger cells), do not introduce a prohibit timer mechanism.

[0222] - Report on leave is not triggered by a cell that was not previously included in the measurement report for the number of triggering cells.

[0223] - It can support setting multiple settings based on height, aiming at improving measurement and measurement reporting. The UE can apply corresponding settings based on the UE height. The proposed solution should aim to avoid RAN4 impact. FFS: How this would be configured (i.e. different MO configurations or different parameters) FFS Exact parameters and details.

[0224] - At the parameter / field level, more than one setting can be supported depending on the height (i.e. different fields / values ​​within the same MO). Here, different values ​​(or value ranges) of a parameter / field can be applied to different heights or height ranges.

[0225] -- For MO configuration parameters: at least the following will have the ability to be configured with height-dependent more-than-one configurations / values, each for a specific height region: SSB-ToMeasure. Details on how to specify is FFS. FFS on UE behavior on L1 and L3 measurement.

[0226] - For MR configuration parameters: at least the following will have the ability to be configured with height-dependent more-than-one configurations / values, each for a specific height region: Event A4 threshold and numberoftriggeringcells. Details on how to specify is FFS (i.e. maybe it can be achieved by combination of events).

[0227] - If two or more settings are provided based on height, the UE may apply the new value when moving to a new height (or height range), similar to the case of RRC reconfiguration. Codes, field descriptions, etc. may be required, as in legacy specifications.

[0228] - If a height-specific value is not explicitly configured for a certain height, whether to keep using the value that was used or consider the parameter as released (i.e. parameter / value not applicable at this height) should be looked into case by case, and can be clarified by need code, field description, or procedural text as needed.

[0229] Figures 15 and 16 are drawings for briefly explaining the IAB node.

[0230] Referring to Figure 15, the link between an IAB node and a parent node is defined as a parent link, and the link between an IAB node and a child node / UE is defined as a child link. That is, the link between an MT and a parent DU is called a parent link, and the link between a DU and a child MT / UE is called a child link.

[0231] However, depending on the interpretation or viewpoint, the link between the IAB node and the parent node is called a backhaul link, and the link between the IAB node and the child node / UE is called an access link.

[0232] An IAB node can be configured with a slot format for communication with a parent node and a slot format for communication with a child node / access UE.

[0233] In the existing IAB node, the DU and MT performed TDM (time division multiplexing) operation through different time resources. On the other hand, for efficient resource operation, it is required to perform resource multiplexing such as SDM (spatial division multiplexing) / FDM (frequency division multiplexing), and FD (full duplexing) between the DU and MT. As illustrated in Fig. 15, the link between the IAB node (IAB MT) and the parent node (parent DU) is called a parent link, and the link between the IAB node (IAB DU) and the child node (child MT) is called a child link. At this time, the TDM operation between the parent link and the child link has been previously discussed, and the SDM / FDM and FD operations are being discussed.

[0234] DUs and MTs within the same IAB node (or co-located) may not operate simultaneously due to intra-node interference, slot / symbol boundary misalignment, power sharing, etc., and may operate in TDM mode. On the other hand, SDM / FDM multiplexing may be used between DUs and MTs. This is applicable, for example, when DUs and MTs use different panels, with little interference between the panels. In this case, DUs and MTs within the same IAB node (or co-located) can transmit or receive simultaneously, but it is impossible for DUs and MTs to perform both transmission and reception, or reception and transmission, respectively.

[0235] Alternatively, full duplexing (FD) can be used between the DU and the MT. This is applicable in cases where there is little interference between the DU and the MT, such as when the frequency ranges where the DU operates and the MT operate are far apart. In such cases, the DU and MT within the same IAB node (or co-located) can freely transmit and receive simultaneously. The DU and MT can transmit or receive simultaneously, and it is also possible for the DU and MT to transmit and receive, or receive and transmit simultaneously.

[0236] There can be N MT-CCs and M DU-cells within an IAB node. MT-CCs within an IAB node can operate on the same or different frequency resources, and one MT-CC can be connected to one or more parent DU-cells. DU-cells within an IAB node can operate on the same or different frequency resources.

[0237] For a specific MT-CC / DU-cell pair within an IAB node, the MT-CC and DU-cell can be in a TDM or no-TDM relationship for the following four Tx / Rx direction combinations, and whether TDM / no-TDM is different for each Tx / Rx combination.

[0238] - DU-Tx / MT-Tx

[0239] - DU-Rx / MT-Rx

[0240] - DU-Tx / MT-Rx

[0241] - DU-Rx / MT-Tx

[0242] For example, for a specific MT-CC / DU-cell pair, all four Tx / Rx combinations may operate in TDM. In this case, the DU-cell and MT-CC must always operate in TDM regardless of the Tx / Rx directions of the DU-cell and MT-CC. As another example, for a specific MT-CC / DU-cell pair, all four Tx / Rx combinations may operate in no-TDM. In this case, the DU-cell and MT-CC can always operate simultaneously in no-TDM regardless of the Tx / Rx directions of the DU-cell and MT-CC. As another example, for a specific MT-CC / DU-cell pair, DU-Tx / MT-Tx and DU-Rx / MT-Rx may operate in no-TDM, and DU-Tx / MT-Rx and DU-Rx / MT-Tx may operate in TDM. This uses a method (e.g., SDM / FDM) that enables simultaneous operation when the Tx / Rx directions of the DU-cell and MT-CC are the same, and can operate simultaneously when the Tx / Rx directions of the DU-cell and MT-CC are the same. TDM / no-TDM information for each Tx / Rx combination can be set / determined differently / independently for each specific MT-CC / DU-cell pair within the IAB node.

[0243] At this time, the IAB MT can be connected to two parent DUs using, for example, dual-connectivity mode or DAPS-HO mode.

[0244] Regarding IAB, referring to the standard document 3GPP TS 38.874, IAB can reuse existing functions and interfaces defined for access. In particular, MT (Mobile-Termination), gNB-DU, gNB-CU, UPF, AMF, and SMF, and their interfaces NR Uu (between MT and gNB), F1, NG, X2, and N4, can be used as the basis of the IAB architecture. Modifications or enhancements to these functions and interfaces to support IAB can be explained in the context of the architecture discussion. Additional functions, such as multi-hop forwarding, can be included in the architecture discussion as they are necessary for understanding IAB operation and may require standardization in certain aspects. The MT function is defined as a component of the mobile equipment. MT is a function in the IAB node that can terminate the radio interface layer of the backhaul Uu interface toward the IAB donor or another IAB node.

[0245] Specifically, referring to FIG. 16, a reference diagram for an IAB in standalone mode, including one IAB-donor and multiple IAB-nodes, is illustrated. The IAB-donor may be treated as a single logical node comprising a set of functions, such as gNB-DU, gNB-CU-CP, gNB-CU-UP, and potentially other functions. In deployment, the IAB-donor may be partitioned based on the functionality of the above-described function sets, and these functions may or may not all be co-located as permitted by the 3GPP NG-RAN architecture. This partitioning may result in IAB-related aspects. Additionally, some functions currently associated with the IAB-donor may be moved outside the donor if it becomes clear that they no longer perform IAB-specific tasks.

[0246] Meanwhile, the aforementioned IAB can also be used as a mobile IAB node to expand coverage. In this case, the mobile IAB node can be interpreted as having mobility. For example, the mobile IAB node can be mounted and operated on a UAV (and / or AAM, aerial mobile device). Below, we will describe in detail the problems that may arise with the introduction of such mobile IAB nodes, solutions thereto, and methods for efficiently utilizing UAV-based mobile IAB nodes.

[0247] How to set the mobile IAB node's moving location

[0248] FIGS. 17 and 18 are drawings illustrating a method for adjusting the position of a UAV mobile IAB node.

[0249] Referring to Fig. 17, a mobile IAB node connected / mounted to a UAV can be utilized for coverage expansion. gNB_A can be a donor or donor node of the mobile IAB node, and the mobile IAB node can be allocated resources and receive control messages from gNB_A.

[0250] A mobile IAB node can broadcast that it is a mobile IAB node or a UE corresponding to a mobile IAB node. For example, a mobile IAB node can broadcast that it is a mobile IAB node through messages such as a master information block / system information block (MIB / SIB). In addition, the mobility information (movement speed, change in movement speed, movement direction, and / or location (latitude and / or longitude, or specific area) of the mobile IAB node may also be broadcast. The terrestrial gNB and / or terrestrial UE that received the information about the broadcasted mobile IAB node may determine which mobile IAB node is a suitable IAB node for the connection before / after attempting a connection with the mobile IAB node, and may attempt ( / continue) a connection with the mobile IAB node determined to be a suitable IAB node. For example, the terrestrial UE may prefer a connection with a mobile IAB node (or a mobile IAB node UE) moving in the same direction as the terrestrial UE. In this case, when selecting a mobile IAB node (and / or gNB) with which the terrestrial UE wishes to establish a connection, the terrestrial UE may additionally consider mobility information such as the movement direction / speed of the mobile IAB node in addition to the simple signal strength of the IAB node.

[0251] Alternatively, when the ground UE is in an RRC connected state with the gNB_B, the ground UE may measure interference from a nearby mobile IAB node (and / or detect any characteristic that interferes with signal reception of the current serving cell). In this case, the ground UE may report information about the interference caused by the mobile IAB node to its serving cell, gNB_B. At this time, the ground UE may report the following information to the gNB_B.

[0252] - The amount of interference, the signal strength of adjacent / neighboring mobile IAB nodes, the signal strength relative to the serving gNB, and the change in signal strength of the mobile IAB node. Meanwhile, the directional information for the mobile IAB node can be provided through the change in signal strength (the degree of increase / decrease in signal strength) with respect to the mobile IAB node due to the movement of the mobile IAB node.

[0253] - Mobility information of the ground UE. Here, the mobility information may include the movement speed of the ground UE, the amount of increase / decrease in the movement speed, the movement direction, and / or the location information of the ground UE (latitude, longitude, height, specific region, and / or GPS value of the UE).

[0254] - Location information of the mobile IAB node measured / estimated by the ground UE (latitude, longitude, height, GPS values ​​received from a specific region and / or mobile IAB node, etc.)

[0255] - gNB, cell, and PLMN (Public Land Mobile Network) information for the mobile IAB node. And / or, information about the donor IAB or donor node of the mobile IAB node.

[0256] In this case, the gNB may, based on the interference information reported by the ground UE, recommend / request a movement of the location of the mobile IAB node to the donor IAB or donor node of the nearby / neighboring mobile IAB node that is currently affecting the ground UE through the backhaul interface. For example, gNB_B, which has received information about a mobile IAB node being interfered with from the ground UE, may notify the donor node (gNB_A or donor IAB) of the mobile IAB node of information about the interference / direction caused by the mobile IAB node and request the adjustment of the location of the mobile IAB node. In this case, the movement of the location of the mobile IAB node may include not only the movement in planar coordinates but also the movement in terms of height. For example, the gNB may specify a mobile IAB node requiring location adjustment based on location information about the mobile IAB node included in the interference information, and transmit a message to the specified mobile IAB node or a donor node of the mobile IAB node requesting that the mobile IAB node move in a predetermined direction or to a specific location.

[0257] Referring to FIG. 18, a ground UE or UEs may be connected to a mobile IAB node. In this case, the ground UE may request / recommend the mobile IAB node to which it is connected to move to a desired location of the ground UE. For example, the ground UE may transmit a message for adjusting the location of the mobile IAB node or a message related to location adjustment to the mobile IAB node or a donor node of the mobile IAB node. For example, the mobile IAB node may provide its location information (latitude, longitude, height, specific region, and / or GPS information, etc.) and / or mobility information (movement direction, movement speed, change in movement speed, etc.) to the UE. In this case, the ground UE may request / recommend the mobile IAB node to move to a specific location or a new location based on the location information (and / or mobility information) of the mobile IAB node and the location information (and / or mobility information) of the ground UE. Here, the terrestrial UE may inform the mobile IAB node of a new location or a specific location through latitude, longitude, height, a specific region and / or GPS coordinate information. (And / or) the terrestrial UE may set / provide information about an offset between the location of the terrestrial UE and the location of the mobile IAB node to the mobile IAB node. For example, the terrestrial UE may request / recommend the mobile IAB node to be located within the offset from the location of the terrestrial UE through the offset information. For example, the terrestrial UE may recommend / request / set the mobile IAB node to be located at a location where a difference between the location (longitude, latitude and / or height) of the terrestrial UE and the location (longitude, latitude and / or height) of the mobile IAB node does not exceed the offset.A mobile IAB node that receives such a message for recommendation / request / configuration may perform an operation (i.e., a position adjustment or position change operation) to position itself within the offset or at the specific location. For example, the mobile IAB node may adjust its location to a specific location or within the offset according to the recommendation / request / configuration message so that the link quality with the terrestrial UE can maintain a constant value. Such a position adjustment operation of the mobile IAB node may be an operation suitable for communication characteristics that are vulnerable to blockage, such as mmWave.

[0258] Alternatively, the mobile IAB node may transmit recommendation / request information regarding movement to the specific location transmitted from the ground UE or maintenance of the location within the offset to its donor node. At this time, the mobile IAB node may also transmit location information and / or mobility information of the ground UE to the donor node. In this case, the donor node may globally relocate the locations of the mobile IAB node (or mobile UAV UE) and / or other mobile IAB nodes (or other mobile UAV UEs) based on the recommendation / request information and the location information and / or mobility information of the ground UE. This is to enable the donor node to control the overall location distribution of the mobile IAB nodes. For example, a ground UE may request / recommend / set a location movement to its serving mobile IAB node, and another mobile IAB node may exist in the direction in which the ground UE is moving. In this case, the donor IAB may not or may not instruct the location movement of the serving mobile IAB node. For example, even if a ground UE requests to adjust / change the location of its serving mobile IAB node, the donor IAB may not need to adjust the location of the serving mobile IAB node because service provision is possible through another mobile IAB node in the direction of movement of the ground UE.

[0259] Alternatively, if a message recommending / requesting / configuring movement of a mobile IAB node is received from a specific ground UE, the mobile IAB node may command / instruct other ground UEs connected to it to report location information (and / or mobility information). In this case, the mobile IAB node may decide whether to change / adjust its location based on the location information reported from other ground UEs.

[0260] Meanwhile, a mobile IAB node may provide advance notice of its location change to its parent node and / or child nodes before moving its location. The advance notice may include location information (and / or mobility information) to which the mobile IAB node intends to move. This may be to enable nodes currently connected to the mobile IAB node to which the mobile IAB node is currently moving to perform actions to prepare in advance for the location change of the mobile IAB node through the advance notice. For example, child nodes connected to the mobile IAB node to which the mobile IAB node is currently moving may attempt to search for and (re)connect to other IAB nodes in advance based on the advance notice of the mobile IAB node.

[0261] Alternatively, the mobile IAB node can determine the location where it will have the highest communication performance based on integrated information obtained from the camera and sensors as well as the communication module.

[0262] In this way, in the proposed method, the ground UE can effectively adjust the location of the mobile IAB node connected to it. Alternatively, in the proposed method, when the ground UE connected to the gNB detects interference caused by the mobile IAB node, the gNB can be quickly notified that a change in the location of the mobile IAB node is necessary for effective removal of the interference by reporting interference information that additionally includes location information of the mobile IAB node as well as information on the magnitude of the interference. Alternatively, in the proposed method, by additionally including location information of the mobile IAB node in the interference information, the gNB can clearly identify the mobile IAB node that requires location adjustment and can quickly calculate the location to which the mobile IAB node will move for removal of the interference.

[0263] FIG. 19 is a diagram illustrating a method for a UE to report indirect information related to a mobile IAB node to a base station.

[0264] Referring to Figure 19, the UE can measure interference related to its connection with the base station (S191). For example, the UE can monitor whether interference exceeding a preset threshold is measured. Here, the interference may be caused by signals transmitted by other base stations / cells / IAB nodes adjacent to the base station.

[0265] Next, the UE may report interference information including the interference intensity for the measured interference to the base station (S193). For example, if the interference intensity of the measured interference is greater than or equal to a preset threshold, the UE may report interference information including information about the interference intensity to the base station. In this case, if the interference is caused by a mobile IAB node rather than a general cell / base station, the UE may additionally report other information in addition to the interference intensity to the base station. For example, the UE may further include at least one of information about the change in signal intensity of the mobile IAB node, the location of the mobile IAB node, mobility information of the mobile IAB node (speed, moving direction, etc.), mobility information of the UE, and identification information of the mobile IAB node (cell ID, PLMN, and / or donor IAB node) in the interference information, or report it to the base station together with the interference information. In this case, the UE may notify the base station that control of the location or movement direction of the mobile IAB node is necessary to alleviate / eliminate the interference intensity by additionally including information about the mobile IAB node in the interference information.

[0266] For example, the UE may report to the base station information on how much the signal strength of the mobile IAB node changes over a preset period of time to provide information on the directionality of the mobile IAB node. Alternatively, the UE may estimate / predict the location, altitude, etc. of the mobile IAB node based on the signal characteristics (Doppler effect, signal reception angle) of the mobile IAB node and / or cell information broadcast by the mobile IAB node, and may also estimate / predict the moving direction of the mobile IAB node. In this case, the UE may notify the base station that the location and / or moving direction of the mobile IAB node needs to be changed / adjusted in order to eliminate / mitigate the interference by reporting interference information that additionally includes information on the mobile IAB node. In addition, since the base station cannot know the location of the mobile IAB node of another donor node, the UE can provide the base station with the estimated / predicted location information and / or mobility information of the mobile IAB node so that the base station can clearly identify the mobile IAB node that caused the interference.

[0267] In this way, when the object that caused the interference is a mobile IAB node as described above, the UE can additionally provide the base station with information about the mobile IAB node in the interference information report, thereby informing the base station of which mobile IAB caused the interference and that mitigation / elimination of the interference is necessary through control of position adjustment / change of the mobile IAB node. In this case, the base station can identify / specify the mobile IAB node based on the information about the mobile IAB node additionally provided together with the interference information, and transmit a message for adjusting / changing the position of the identified / specified mobile IAB node to the mobile IAB node and / or a donor node associated with the mobile IAB node.

[0268] Alternatively, if the UE is connected to a mobile IAB node, the UE may directly provide a message to the mobile IAB node requesting / proposing adjustment / change of the location of the mobile IAB node.

[0269] Alternatively, as described above, the mobile IAB node may be an IAB node included / mounted on a UAV (Unmanned Aerial Vehicle) and moving at an altitude above a certain height.

[0270] FIG. 20 is a diagram illustrating a method for a base station to adjust the location of a mobile IAB node based on indirect information related to the mobile IAB node.

[0271] Referring to FIG. 20, a base station can receive interference information from a user equipment (UE) including interference strength for interference measured for a connection between the UE and the base station (S201). Next, based on the fact that the interference information further includes location information of a mobile IAB (integrated access backhaul) node, the base station can transmit a message requesting a change in location of the mobile IAB node to the mobile IAB node or a donor node of the mobile IAB node (S203).

[0272] For example, if the indirect information further includes location information about a mobile IAB node, the base station may recognize that it is necessary to control / change the location of the mobile IAB node to mitigate or eliminate interference generated for the UE. Specifically, the base station may determine where the mobile IAB node that has caused interference in the connection between the UE and the base station is located based on the location information of the mobile IAB node included in the interference information. The base station may determine, based on the location information of the UE and / or the location information of the mobile IAB node, to which location or in which direction the mobile IAB node needs to move to eliminate the interference. In this case, the base station may transmit a message including information about the location or direction in which the mobile IAB node needs to move to eliminate / mitigate the interference to the mobile IAB node and / or the donor node, thereby requesting / proposing an adjustment of the location of the mobile IAB node.

[0273] Alternatively, the base station may predict the direction in which the mobile IAB node moves based on the amount of change in the signal strength of the mobile IAB node included in the indirect information, and determine whether the interference can be eliminated / mitigated without controlling the location of the mobile IAB node. For example, if the amount of change in the signal strength of the mobile IAB node is determined to be gradually decreasing, the base station may determine that the mobile IAB node is moving away from the UE and may not perform location control of the mobile IAB node. Alternatively, if the amount of change in the signal strength of the mobile IAB node is determined to be gradually increasing, the base station may transmit a message to the mobile IAB node or a donor node for controlling the movement of the mobile IAB node so that the mobile IAB node can move in a different direction (e.g., an opposite direction) than its current moving direction.

[0274] In this way, the proposed method can efficiently control the location of a mobile IAB node based on interference information regarding the connection between a base station and a UE. In addition, the proposed invention can additionally include identification information of a mobile IAB node related to interference in the interference information regarding the connection between a UE and a base station, thereby enabling the base station to quickly control the location of the mobile IAB node for interference removal. Alternatively, the proposed invention can effectively maintain the link quality between the UE and the mobile IAB node even in an mmWave communication environment by having the UE directly provide information related to location adjustment / control to the mobile IAB node connected to it.

[0275] Examples of communication systems to which the invention applies

[0276] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0277] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0278] Figure 21 illustrates a communication system applied to the present invention.

[0279] Referring to FIG. 21, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0280] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0281] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0282] Examples of wireless devices to which the present invention is applied

[0283] Figure 22 illustrates a wireless device applicable to the present invention.

[0284] Referring to FIG. 22, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 21.

[0285] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0286] Specifically, the first wireless device or first UE (100) may include a processor (102) and a memory (104) connected to a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 20.

[0287] The processor (102) can control the transceiver (106) to measure interference for a connection between a user equipment (UE) and a base station, and report interference information including the interference intensity of the measured interference to the base station. Here, based on whether the interference is related to a mobile IAB (integrated access backhaul) node, the interference information can further include location information of the mobile IAB node.

[0288] Alternatively, a processing device may be configured, including a processor (102) and a memory (104) for controlling a first UE that triggers a measurement report. In this case, at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the UE to: measure interference for a connection between the UE and a base station, and report interference information including an interference strength of the measured interference to the base station. Here, based on the interference being associated with a mobile IAB (integrated access backhaul) node, the interference information may further include location information of the mobile IAB node.

[0289] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0290] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver or RF transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 20.

[0291] The processor (202) controls the transceiver (206) to receive interference information including interference strength for interference measured for a connection between a user equipment (UE) and a base station from the UE, and based on the interference information further including location information of the mobile IAB (integrated access backhaul) node, transmit a message requesting a change in location of the mobile IAB node to the mobile IAB node or a donor node of the mobile IAB node.

[0292] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0293] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0294] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0295] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0296] Examples of wireless devices to which the present invention is applied

[0297] Figure 23 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 21).

[0298] Referring to FIG. 23, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 22 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 23. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 22. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0299] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 21, 100a), a vehicle (Fig. 21, 100b-1, 100b-2), an XR device (Fig. 21, 100c), a portable device (Fig. 21, 100d), a home appliance (Fig. 21, 100e), an IoT device (Fig. 21, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 21, 400), a base station (Fig. 21, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0300] In FIG. 23, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0301] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0302] Figure 24 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, car, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0303] Referring to FIG. 24, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 23, respectively.

[0304] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0305] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0306] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0307] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0308] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0309] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0310] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0311] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0312] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. A step for measuring interference in the connection between UE (user equipment) and a base station; and Comprising a step of reporting interference information including the interference intensity of the measured interference to the base station, A method wherein the interference information further includes location information of the mobile IAB node, based on the interference being associated with a mobile IAB (integrated access backhaul) node.

2. In paragraph 1, A method, characterized in that the above interference information further includes information on the amount of change in signal strength of the mobile IAB node.

3. In paragraph 1, A method, characterized in that the location information of the mobile IAB node includes information on the location and height of the mobile IAB node predicted by the UE.

4. In paragraph 1, A method, characterized in that the interference information further includes mobility information for the UE.

5. In paragraph 1, A method, characterized in that the interference information further includes at least one of a cell ID (identifier), a Public Land Mobile Network (PLMN) and information about a donor IAB node associated with the mobile IAB node.

6. In paragraph 1, A method, characterized in that, based on the UE being connected to the mobile IAB node, the UE transmits a message related to position adjustment of the mobile IAB node to the mobile IAB node.

7. In paragraph 1, A method, characterized in that the above mobile IAB node is an IAB node moving via a UAV (Unmanned Aerial Vehicle).

8. A computer-readable recording medium having recorded thereon a program for performing the method described in Article 1. 9.RF(Radio Frequency) Transmitter / Receiver; and comprising a processor connected to the RF transceiver; The processor controls the RF transceiver to measure interference for a connection between a UE (user equipment) and a base station, and reports interference information including the interference intensity of the measured interference to the base station. A UE, wherein the interference information further includes location information of the mobile IAB node, based on the interference being associated with a mobile IAB node.

10. In paragraph 9, A UE, characterized in that the above interference information further includes information on the amount of change in signal strength of the mobile IAB node.

11. In paragraph 9, A UE, characterized in that the location information of the mobile IAB node includes information on the location and height of the mobile IAB node predicted by the UE.

12. In a processing device controlling UE (User Equipment), at least one processor; and At least one memory coupled to said at least one processor and storing instructions, said instructions being executed by said at least one processor to cause said UE to: Measure interference for connection with a base station and report interference information including the interference intensity of the measured interference to the base station, A processing device, wherein the interference information further includes location information of the mobile IAB node, based on the interference being related to a mobile IAB (integrated access backhaul) node.

13. A step of receiving interference information including interference intensity for interference measured for a connection between a UE (user equipment) and a base station from the UE; and A method comprising: a step of transmitting a message requesting a change of location of a mobile IAB (integrated access backhaul) node to the mobile IAB node or a donor node of the mobile IAB node based on the interference information further including location information of the mobile IAB node.

14. In paragraph 13, A method, characterized in that the message further includes information about a direction of movement associated with a change in location of the mobile IAB node. 15.RF(Radio Frequency) Transmitter / Receiver; and comprising a processor connected to the RF transceiver; A base station, wherein the processor controls the RF transceiver to receive interference information including interference strength for interference measured for a connection between a UE (user equipment) and a base station from the UE, and transmits a message requesting a change of location of a mobile integrated access backhaul (IAB) node to the mobile IAB node or a donor node of the mobile IAB node based on the interference information further including location information of the mobile IAB node.

Images