Method for performing communication by device in wireless communication system and apparatus for the same

By reporting capability information through network-controlled repeaters (NCRs) and configuring backhaul link beams based on predefined rules, the lack of standard beam configuration in existing technologies is resolved, thereby improving the reliability and efficiency of wireless communication systems.

CN119054313APending Publication Date: 2024-11-29LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035044.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-09-30
Filing Date
2023-04-21
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In the existing technology, there is a lack of clear standards and rules for backhaul link beam configuration, which makes it impossible to effectively configure the beam when the base station does not provide instructions, thus affecting the reliability and efficiency of the communication system.

Method used

The network-controlled repeater (NCR) reports capability information and configures the backhaul link beams based on predefined rules or base station instructions, including Transmission Configuration Indicator (TCI) status identifiers or Scheduling Request Indicators (SRIs), to ensure proper beam configuration.

Benefits of technology

It enables clear prediction and configuration of backhaul link beams without instructions from the base station, improving the reliability and efficiency of wireless communication systems and ensuring the standardization of beam configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054313A_ABST
    Figure CN119054313A_ABST
Patent Text Reader

Abstract

According to various embodiments, a method for configuring a beam for a backhaul link for forwarding by a network controlled repeater (NCR) in a wireless communication system, and an apparatus for the method are disclosed. Disclosed are a method and an apparatus for the same, the method comprising the steps of: reporting capability information related to beam configuration of a backhaul link to a base station through a control link; and configuring a beam of the backhaul link based on the reporting of the capability information, based on a predefined rule or indication information received from the base station, where the indication information includes a transmission configuration indicator (TCI) status identifier (ID) or a scheduling request indicator (SRI) related to a control link for configuring the beam for the backhaul link.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure relate to a method for setting (or configuring) a beam for a backhaul link required for forwarding through a network controlled repeater (NCR) in a wireless communication system, and a device used for the method. Background Art

[0002] Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. Generally, wireless communication systems are multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems.

[0003] As more and more communication devices require greater communication capacity when sending and receiving signals, there is a need for improved mobile broadband communications relative to traditional radio access technologies. Therefore, communication systems that take into account services / UEs that are sensitive to reliability and latency are being discussed. The next generation of radio access technologies that take into account enhanced mobile broadband communications, massive machine type communications (MTC), and ultra-reliable and low-latency communications (URLLC) may be referred to as new radio access technologies (RATs) or new radios (NRs). Summary of the invention

[0004] Technical issues

[0005] An object of the present disclosure is to provide a method and apparatus for defining capability information about whether beam instructions for a backhaul link required for forwarding are possible, clearly predicting whether the beam of the backhaul link will operate based on the instructions, and thereby ensuring the beam configuration (beam setting) of the backhaul link according to clear criteria through predefined rules even if there is no beam instruction from a base station (BS) according to the capability information.

[0006] Those skilled in the art will understand that the purposes that can be achieved using various embodiments of the present disclosure are not limited to those specifically described above, and the above and other purposes that can be achieved by various embodiments of the present disclosure will be more clearly understood from the following detailed description.

[0007] Technical Solution

[0008] According to one aspect of the present disclosure, a method for setting a beam of a backhaul link for forwarding through a network controlled repeater (NCR) in a wireless communication system may include: reporting capability information related to the beam configuration of the backhaul link to a base station (BS) through a control link; and configuring the beam for the backhaul link based on instruction information or predefined rules received from the base station (BS) based on the report of the capability information, wherein the instruction information includes a transmission configuration indicator (TCI) state identifier (ID) or a scheduling request indicator (SRI) related to the control link for configuring the beam for the backhaul link.

[0009] The capability information may include information on whether instruction for a beam of a backhaul link is possible.

[0010] The capability information may include information on whether a beam different from a beam for a control link can be used for a backhaul link.

[0011] Based on the fact that instruction information is not received through the time resource for the backhaul link and the time resource does not overlap with the time resource of the control link, the beam for the backhaul link may be configured based on a predefined rule.

[0012] According to a predefined rule, a downlink reception beam for the backhaul link is determined based on a control resource set (CORESET) having a specific index among CORESETs related to the control link.

[0013] The specific index may be the lowest index among the indexes for the CORESET.

[0014] Based on a predefined rule, a downlink reception beam for the backhaul link may be determined as a beam for the control link used to receive a downlink signal in a specific search space among a plurality of search spaces related to the control link.

[0015] Based on a predefined rule, the beam for the backhaul link may be determined to be the same beam as the beam for the control link.

[0016] According to another aspect of the present disclosure, a device for configuring a beam of a backhaul link for forwarding in a network controlled repeater (NCR) in a wireless communication system may include: a radio frequency (RF) transceiver; and a processor connected to the RF transceiver, wherein the processor is configured to: under the control of the RF transceiver, report capability information related to the beam configuration of the backhaul link to a base station (BS) via a control link; and based on the report of the capability information, configure the beam for the backhaul link based on instruction information received from the base station (BS) or one of predefined rules, wherein the instruction information includes a transmission configuration indicator (TCI) state identifier (ID) or a scheduling request indicator (SRI) related to the control link for configuring the beam for the backhaul link.

[0017] The capability information may include information on whether a beam for the backhaul link can be configured based on the instruction information.

[0018] Through the reporting of capability information, based on the received instruction information, the downlink (DL) receive beam for the backhaul link can be set to a beam corresponding to the TCI state ID included in the instruction information among the multiple beams for the control link, and the uplink transmit beam for the backhaul link can be set to a beam corresponding to the SRI included in the instruction information among the multiple beams for the control link.

[0019] Based on the fact that instruction information is not received through the time resource for the backhaul link and the time resource does not overlap with the time resource of the control link, the beam for the backhaul link may be configured based on a predefined rule.

[0020] According to a predefined rule, a downlink reception beam for the backhaul link is determined based on a control resource set (CORESET) having a specific index among CORESETs related to the control link.

[0021] According to another aspect of the present disclosure, a chipset for configuring a beam of a backhaul link for forwarding in a wireless communication system may include: at least one processor; and at least one memory, which is operatively connected to the at least one processor and is configured to cause the at least one processor to perform operations when executed, wherein the operations include: reporting capability information related to the beam configuration of the backhaul link to a base station (BS) via a control link; and configuring the beam for the backhaul link based on instruction information received from the base station (BS) or one of predefined rules based on the reporting of the capability information, wherein the instruction information includes a transmission configuration indicator (TCI) state identifier (ID) or a scheduling request indicator (SRI) related to the control link for configuring the beam for the backhaul link.

[0022] According to another aspect of the present disclosure, a computer-readable storage medium configured to store at least one computer program in a wireless communication system may include: at least one computer program for allowing at least one processor in the wireless communication system to perform operations for configuring a beam for forwarding for a backhaul link, the computer-readable storage medium being configured to store the at least one computer program, wherein the operations include: reporting capability information related to the beam configuration of the backhaul link to a base station (BS) via a control link; and configuring the beam for the backhaul link based on the report of the capability information, based on instruction information received from the base station (BS) or one of predefined rules, wherein the instruction information includes a transmission configuration indicator (TCI) state identifier (ID) or a scheduling request indicator (SRI) related to the control link for configuring the beam for the backhaul link.

[0023] Beneficial Effects

[0024] Various embodiments may define capability information about whether beam instructions for the backhaul link required for forwarding are possible, may clearly predict whether to operate the beam for the backhaul link based on the beam instructions, and may thus ensure beam configuration (beam setting) for the backhaul link according to clear criteria through predefined rules even if there is no beam instruction from the base station (BS) according to the capability information.

[0025] The effects to be achieved by the embodiments are not limited to the contents specifically described above, and those skilled in the art to which the embodiments belong will more clearly understand other effects not mentioned herein according to the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the disclosure and together with the description serve to explain the principle of the disclosure.

[0027] Figure 1 The structure of an LTE system to which the embodiment is applied is illustrated.

[0028] Figure 2 The structure of an NR system to which an embodiment is applicable is illustrated.

[0029] Figure 3 The structure of an NR radio frame to which an embodiment is applicable is illustrated.

[0030] Figure 4 The time slot structure of the NR frame applicable to the implementation mode is illustrated.

[0031] Figure 5 An example of mapping physical channels in time slots is illustrated.

[0032] Figure 6 An exemplary PDCCH transmission / reception procedure is illustrated.

[0033] Figure 7 Examples of parent links and child links are schematically illustrated.

[0034] Figure 8 is a diagram illustrating an example of a topology in which a network controlled relay (NCR) performs transmission and reception between a gNB and a UE.

[0035] Fig. 9 is a diagram illustrating a radio frequency (RF) repeater and an NCR.

[0036] Fig.10 This is a diagram illustrating a method in which an NCR configures a beam for a backhaul link required for forwarding.

[0037] Fig.11 A communication system applied to the present disclosure is illustrated.

[0038] Fig.12 A wireless device suitable for use with the present disclosure is illustrated.

[0039] Fig.13 Another example of a wireless device to which the present disclosure is applied is illustrated. DETAILED DESCRIPTION

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

[0041] Sidelink refers to a communication scheme that establishes a direct link between user equipments (UEs) to directly exchange voice or data between UEs without assistance from a base station (BS). Sidelink is seen as a way to resolve the burden on the BS caused by the rapidly increasing data traffic.

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

[0043] As more and more communication devices require greater communication capacity when sending and receiving signals, there is a need for improved mobile broadband communications relative to traditional radio access technologies. Therefore, communication systems that take into account services / UEs that are sensitive to reliability and latency are being discussed. The next generation of radio access technologies that take into account enhanced mobile broadband communications, massive MTC, and ultra-reliable and low-latency communications (URLLC) may be referred to as new radio access technologies (RATs) or new radios (NRs). Even in NRs, V2X communications may be supported.

[0044] The techniques described herein can be used for various wireless access systems such as 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), etc. CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using Evolved UTRA (E-UTRA). 3GPP LTE adopts OFDMA for downlink and SC-FDMA for uplink. LTE-A is the evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0045] 5G NR is the successor technology of LTE-A and is a new clean-state mobile communication system characterized by high performance, low latency, and high availability. 5G NR can use all available spectrum resources, including low frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high frequency (millimeter) bands of 24 GHz or more.

[0046] For clarity of explanation, LTE-A or 5G NR is mainly described, but the technical spirit of the implementation manner is not limited thereto.

[0047] Figure 1The structure of the LTE system to which the present disclosure is applicable is illustrated. This may also be referred to as an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or an LTE / LTE-A system.

[0048] Reference Figure 1 , E-UTRAN includes an evolved Node B (eNB) 20 that provides a control plane and a user plane to UE 10. UE 10 may be fixed or mobile, and may also be referred to as a mobile station (MS), a user UE (UT), a subscriber station (SS), a mobile UE (MT), or a wireless device. eNB 20 is a fixed station that communicates with UE 10, and may also be referred to as a base station (BS), a base transceiver system (BTS), or an access point.

[0049] The eNBs 20 may be connected to each other via an X2 interface. The eNBs 20 are connected to an Evolved Packet Core (EPC) 39 via an S1 interface. More specifically, the eNBs 20 are connected to a Mobility Management Entity (MME) via an S1-MME interface, and to a Serving Gateway (S-GW) via an S1-U interface.

[0050] The EPC 30 includes an MME, an S-GW, and a packet data network gateway (P-GW). The MME has access information or capability information about the UE, which is mainly used for mobility management of the UE. The S-GW is a gateway with the E-UTRAN as an endpoint, and the P-GW is a gateway with a packet data network (PDN) as an endpoint.

[0051] Based on the lowest three layers of the open system interconnection (OSI) reference model known in communication systems, the radio protocol stack between the UE and the network can be divided into layer 1 (L1), layer 2 (L2), and layer 3 (L3). These layers are defined in pairs between the UE and the evolved UTRAN (E-UTRAN) for data transmission via the Uu interface. The physical (PHY) layer at L1 provides information transfer services on physical channels. The radio resource control (RRC) layer at L3 is used to control radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the eNB.

[0052] Figure 2 The structure of the NR system to which the present disclosure is applicable is illustrated.

[0053] Reference Figure 2 , the next generation radio access network (NG-RAN) may include next generation Node Bs (gNBs) and / or eNBs that provide user plane and control plane protocol terminations to the UE. Figure 3In the figure, for example, NG-RAN is shown as including only gNB. gNB and eNB are connected to each other via Xn interface. gNB and eNB are connected to 5G core network (5GC) via NG interface. More specifically, gNB and eNB are connected to access and mobility management function (AMF) via NG-C interface, and to user plane function (UPF) via NG-U interface.

[0054] Figure 3 The structure of an NR radio frame to which the present disclosure is applicable is illustrated.

[0055] Reference Figure 3 , a radio frame can be used for UL transmission and DL transmission in NR. The length of a radio frame is 10ms and can be defined by two 5ms half frames. HF may include five 1ms subframes. A subframe may be divided into one or more slots, and the number of slots in a SF may be determined according to a subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM (A) symbols depending on a cyclic prefix (CP).

[0056] In the case of normal CP (NCP), each time slot may include 14 symbols, and in the case of extended CP (ECP), each time slot may include 12 symbols. Herein, a symbol may be an OFDM symbol (or CP-OFDM symbol) or an SC-FDMA symbol (or DFT-s-OFDM symbol).

[0057] Table 1 below lists the number of symbols N per time slot according to the SCS configuration μ in the NCP case slot symb , the number of time slots per frame N frame,u slot And the number of time slots N in each subframe subframe,u slot .

[0058] [Table 1]

[0059] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0060] The following Table 2 lists the number of symbols per time slot, the number of time slots per frame, and the number of time slots per subframe according to SCS in the ECP case.

[0061] [Table 2]

[0062] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz(u=2) 12 40 4

[0063] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a TTI) (collectively referred to as a time unit (TU) for convenience) including the same number of symbols may be configured to be different for the aggregated cells.

[0064] In NR, various parameter sets or SCS can be supported to support various 5G services. For example, with an SCS of 15kHz, wide areas in traditional cellular bands can be supported, while with an SCS of 30kHz / 60kHz, dense urban areas, lower latency, and wide carrier bandwidths can be supported. When the SCS is 60kHz or higher, bandwidths wider than 24.25GHz can be supported to overcome phase noise.

[0065] The NR frequency band may be defined by two types of frequency ranges FR1 and FR2. The two types of frequency ranges may be FR1 and FR2. The numerical values ​​of the frequency ranges may be changed. For example, the two types of frequency ranges may be configured as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 may mean "a range below 6 GHz", and FR2 may mean "a range above 6 GHz", and may be referred to as millimeter wave (mmW).

[0066] [Table 3]

[0067] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 450MHz-6000MHz 15kHz, 30kHz, 60kHz FR2 24250MHz-52600MHz 60kHz, 120kHz, 240kHz

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

[0069] [Table 4]

[0070] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 410MHz-7125MHz 15kHz, 30kHz, 60kHz FR2 24250MHz-52600MHz 60kHz, 120kHz, 240kHz

[0071] Figure 4 The time slot structure of the NR frame applicable to the present disclosure is illustrated.

[0072] Reference Figure 4, a time slot includes multiple symbols in the time domain. For example, a time slot may include 14 symbols in the normal CP case and 12 symbols in the extended CP case. Alternatively, a time slot may include 7 symbols in the normal CP case and 6 symbols in the extended CP case.

[0073] A carrier may include multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A bandwidth part (BWP) may be defined as a plurality of consecutive (P) RBs in the frequency domain, and a BWP may correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed in an activated BWP. In a resource grid, each element may be referred to as a resource element (RE) and may be mapped to a complex symbol.

[0074] The wireless interface between UEs or the wireless interface between UE and the network may include L1 layer, L2 layer and L3 layer. In various embodiments of the present disclosure, L1 layer may represent a physical layer. L2 layer may represent at least one of a MAC layer, an RLC layer, a PDCH layer or an SDAP layer. L3 layer may represent an RRC layer, for example.

[0075] Bandwidth Part (BWP)

[0076] In an NR system, each component carrier (CC) can support up to 400MHz. If a UE operating on a wideband CC always utilizes RF operation for all enabled CCs, the battery power consumption of the UE may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating within a wideband CC, different parameter sets (e.g., subcarrier spacing) may be supported for different frequency bands within a specific CC. Alternatively, the capabilities for maximum bandwidth may be different between UEs. In view of this, the BS may instruct the UE to operate only in part of the bandwidth, rather than in the entire bandwidth of the wideband CC. For simplicity, a partial bandwidth is defined as a bandwidth part (BWP). Here, a BWP may be composed of resource blocks (RBs) that are continuous on the frequency axis and may correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / mini-slot duration).

[0077] The BS may configure multiple BWPs in one CC configured for the UE. For example, a BWP occupying a relatively small frequency domain may be configured in the PDCCH monitoring time slot, and the PDSCH indicated by the PDCCH in the larger BWP may be scheduled. Alternatively, when the UE is concentrated in a specific BWP, some of the UEs may be configured in another BWP to balance the load. Alternatively, considering the frequency domain inter-cell interference elimination between adjacent cells, the spectrum in the middle of the entire bandwidth may be punctured and the two BWPs on both sides may be configured in the same time slot. That is, the BS may configure at least one DL / UL BWP for the UE associated with the broadband CC (through L1 signaling, MAC CE or RRC signaling, etc.), and activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time. The BS may instruct the UE to switch to another configured DL / UL BWP (through L1 signaling, MAC CE or RRC signaling, etc.). Alternatively, when the timer expires, the UE may switch to a predetermined DL / UL BWP. The activated DL / UL BWP is defined as the activated DL / UL BWP. During the initial access procedure or before establishing an RRC connection, the UE may not be able to receive the DL / UL BWP configuration. The DL / UL BWP assumed by the UE in this situation is defined as the initially activated DL / UL BWP.

[0078] Figure 5 An example of mapping physical channels in time slots is illustrated.

[0079] The time slot may include a DL control channel, DL or UL data, a UL control channel, etc., all of which are included. For example, the first N symbols in the time slot may be used to send a DL control channel (hereinafter referred to as a DL control region), and the last M symbols in the time slot may be used to send a UL control channel (hereinafter referred to as an UL control region). N and M are each integers greater than or equal to 0. The resource area (hereinafter referred to as a data area) between the DL control region and the UL control region may be used for DL ​​data transmission or UL data transmission. The time gap for DL ​​to UL or UL to DL switching may exist between the control region and the data region. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. Some symbols of the time when switching from DL to UL in the time slot may be used as time gaps.

[0080] In the NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and UL channels can all be included in one time slot. For example, the first N symbols of a time slot can be used to carry a DL channel (e.g., PDCCH) (hereinafter referred to as the DL control region), and the last M symbols of the time slot can be used to carry a UL channel (e.g., PUCCH) (hereinafter referred to as the UL control region). Each of N and M is an integer equal to or greater than 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region can be used to send DL data (e.g., PDSCH) or UL data (e.g., PUSCH). The guard period (GP) provides a time gap for switching from a transmit mode to a receive mode or from a receive mode to a transmit mode. Some symbols in a subframe when switching from DL to UL can be configured as GPs.

[0081] PDCCH transmits DCI. For example, PDCCH (i.e., DCI) may carry information about the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of high-level control messages (e.g., RAR sent on PDSCH), transmit power control commands, information about the activation / release of the configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (eg, system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for RAR, the CRC is masked by a random access-RNTI (RA-RNTI).

[0082] Figure 6 An exemplary PDCCH transmission / reception procedure is illustrated.

[0083] Reference Figure 6, the BS may send a control resource set (CORESET) configuration to the UE (S502). A CORESET is defined as a set of resource element groups (REGs) with a given parameter set (e.g., subcarrier spacing (SCS), cyclic prefix (CP) length, etc.). A REG is defined by one (physical) resource block (P)RB as one OFDM symbol. Multiple CORESETs for one UE may overlap with each other in the time / frequency domain. The CORESET may be configured by system information (e.g., a master information block (MIB)) or high-level signaling (e.g., radio resource control (RRC) signaling). For example, configuration information about a specific common CORESET (e.g., CORESET#0) may be sent in the MIB. For example, a PDSCH carrying system information block 1 (SIB1) may be scheduled by a specific PDCCH, and CORESET#0 may be used to send a specific PDCCH. The system information (SIB1) broadcast in the cell includes cell-specific PDSCH configuration information, PDSCH-ConfigCommon. PDSCH-ConfigCommon includes a list (or lookup table) of parameters related to time domain resource allocation, pdsch-TimeDomainAllocationList. Each pdsch-TimeDomainAllocationList can include up to 16 entries (or rows), each entry is jointly encoded {K0, PDSCH mapping type, PDSCH start symbol and length (SLIV)}. In addition to the pdsch-TimeDomainAllocationList configured by PDSCH-ConfigCommon, the pdsch-TimeDomainAllocationList can also be provided by the UE-specific PDSCH configuration, PDSCH-Config. The structure of the UE-specific configured pdsch-TimeDomainAllocationList is the same as the structure of the pdsch-TimeDomainAllocationList provided by the UE publicly. For K0 and SLIV of the pdsch-TimeDomainAllocationList, refer to the following description.

[0084] In addition, configuration information about CORESET#N (e.g., N>0) may be sent through RRC signaling (e.g., cell-common RRC signaling, UE-specific RRC signaling, etc.). For example, UE-specific RRC signaling carrying CORESET configuration information may include (but is not limited to) various types of signaling, such as RRC establishment message, RRC reconfiguration message, and / or BWP configuration information. Specifically, the CORESET configuration may include the following information / fields.

[0085] -controlResourceSetId: indicates the ID of the CORESET.

[0086] -frequencyDomainResources: Indicates the frequency domain resources of the CORESET. The resources are indicated by a bitmap where each bit corresponds to an RB group (= 6 (contiguous) RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit with a bit value of 1 is allocated as the frequency domain resource of the CORESET.

[0087] -duration: Indicates the time domain resource of CORESET. It indicates the number of consecutive OFDM symbols included in CORESET. duration has a value between 1 and 3.

[0088] -cce-REG-MappingType: indicates the control channel element (CCE) to REG mapping type. Both interleaved and non-interleaved types are supported.

[0089] -interleaverSize: Indicates the interleaver size.

[0090] -pdcch-DMRS-ScramblingID: indicates a value used for PDCCH DMRS initialization. When pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0091] -precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0092] -reg-BundleSize: Indicates the REG bundle size.

[0093] -tci-PresentInDCI: indicates whether the transmission configuration index (TCI) field is included in the DL-related DCI.

[0094] -tci-StatesPDCCH-ToAddList: indicates a subset of TCI states configured in pdcch-Config for providing a quasi co-location (QCL) relationship between DL RSs and PDCCH DMRS ports in an RS set (TCI state).

[0095] In addition, the BS may send a PDCCH search space (SS) configuration to the UE (S504). The PDCCH SS configuration may be sent through high-layer signaling (e.g., RRC signaling). For example, the RRC signaling may include (but is not limited to) various types of signaling, such as an RRC setup message, an RRC reconfiguration message, and / or BWP configuration information. Although for convenience of description, in Figure 5 In the embodiment, the CORESET configuration and the PDCCH SS configuration are shown to be signaled separately, but the present disclosure is not limited thereto. For example, the CORESET configuration and the PDCCH SS configuration may be sent in one message (eg, through one RRC signaling) or may be sent separately in different messages.

[0096] The PDCCH SS configuration may include information about the configuration of a PDCCH SS set. A PDCCH SS set may be defined as a set of PDCCH candidates monitored (e.g., blindly detected) by a UE. One or more SS sets may be configured for a UE. Each SS set may be a UE-specific search space (USS) set or a common search space (CSS) set. For convenience, a PDCCH SS set may be referred to as an "SS" or a "PDCCH SS".

[0097] The PDCCH SS set includes PDCCH candidates. PDCCH candidates are CCEs that the UE monitors to receive / detect PDCCH. Monitoring includes blind decoding (BD) of PDCCH candidates. One PDCCH (candidate) includes 1, 2, 4, 8 or 16 CCEs depending on the aggregation level (AL). One CCE includes 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one CORESET configuration. One SS is defined based on the SS configuration, and the SS configuration may include the following information / fields.

[0098] -searchSpaceId: indicates the ID of the SS.

[0099] -controlResourceSetId: Indicates the CORESET associated with the SS.

[0100] - monitoringSlotPeriodicityAndOffset: indicates the periodicity (in time slots) and offset (in time slots) of PDCCH monitoring.

[0101] -monitoringSymbolsWithinSlot: Indicates the first OFDM symbol used for PDCCH monitoring in a slot configured with PDCCH monitoring. The first OFDM symbol used for PDCCH monitoring is indicated by a bitmap where each bit corresponds to an OFDM symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol of the slot. The OFDM symbol corresponding to the bit set to 1 corresponds to the first symbol of the CORESET in the slot.

[0102] -nrofCandidates: indicates the number of PDCCH candidates per AL (one of the values ​​0, 1, 2, 3, 4, 5, 6 and 8), where AL = {1, 2, 4, 8, 16}.

[0103] -searchSpaceType: Indicates CSS or USS and the DCI format used in the corresponding SS type.

[0104] Subsequently, the BS may generate a PDCCH and send the PDCCH to the UE (S506), and the UE may monitor the PDCCH candidates in one or more SSs to receive / detect the PDCCH (S508). The timing (e.g., time / frequency resources) at which the UE is to monitor the PDCCH candidates is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

[0105] Table 5 shows the characteristics of each SS.

[0106] [Table 5]

[0107]

[0108] Table 6 shows the DCI format transmitted on the PDCCH.

[0109] [Table 6]

[0110]

[0111] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (or DL ​​grant DCI). DCI format 0_0 / 0_1 can be called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be called DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on a group common PDCCH (a PDCCH pointing to a group of UEs).

[0112] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

[0113] The CCE-to-REG mapping type is configured as one of an interleaved CCE-to-REG type and a non-interleaved CCE-to-REG type.

[0114] - Non-interleaved CCE to REG mapping (or localized CCE to REG mapping) ( Figure 5 ): 6 REGs for a given CCE are grouped into one REG bundle, and all REGs for a given CCE are contiguous. One REG bundle corresponds to one CCE.

[0115] - Interleaved CCE to REG mapping (or distributed CCE to REG mapping) ( Figure 6 ): 2, 3, or 6 REGs for a given CCE are grouped into one REG bundle, and the REG bundles are interleaved within a CORESET. In a CORESET that includes one or two OFDM symbols, a REG bundle includes 2 or 6 REGs, and in a CORESET that includes three OFDM symbols, a REG bundle includes 3 or 6 REGs. The REG bundle size is set based on the CORESET.

[0116] RRC signaling related to TCI status

[0117] Below, parameters used for RRC signaling including information related to the TCI state are described in detail (see 3GPP TS38.331).

[0118] In addition, in the NR system, the transmission configuration indicator (TCI) field included in the DL-related DCI is used to dynamically indicate one of the candidates of multiple QCL reference resources (e.g., CSI-RS resources or SSB resources) configured in the higher layer, similar to the PQI field of LTE.

[0119] Here, the QCL indication may include a QCL indication for a spatial parameter. For example, the TCI field among the multiple DL RS resources configured in the high layer may indicate through which DL RS beam the corresponding PDSCH is sent. The UE receiving the indication may receive the corresponding PDSCH beam by applying a receiving beam previously trained to be suitable for receiving the corresponding DL RS. In other words, the TCI state may be related to the determination or timing of the direction of the downlink receiving beam used to receive the PDSCH.

[0120] First, BWP-DownlinkDedicated can be used to configure the dedicated (UE-specific) parameters of the downlink BWP. Referring to Tables 7 and 8, information related to the TCI state can be included in the pdsch-Config of BWP-DownlinkDedicated, and the DL receive beam related to the BWP can be set based on the TCI state.

[0121] [Table 7]

[0122]

[0123]

[0124] [Table 8]

[0125]

[0126]

[0127]

[0128] IAB (Integrated Access / Backhaul)

[0129] Figure 7 An example of a network with such integrated access and backhaul links is shown, where an IAB node or relay node (rTRP) can multiplex the access and backhaul links in time, frequency, or space (e.g., beam-based operation).

[0130] The operation of different links can be on the same or different frequencies (also known as "in-band" and "out-of-band" relaying). Efficient support of out-of-band relaying is important in some NR deployment scenarios, but it is very important to understand the in-band operation requirements, which imply close interaction with access links operating on the same frequency, to accept duplex constraints and avoid / mitigate interference.

[0131] Additionally, operating NR systems in mmWave spectrum may present several unique challenges, including experiencing severe short-term congestion, which may not be easily mitigated by current RRC-based handover mechanisms due to the larger timescale required to complete the process compared to short-term congestion.

[0132] To overcome short-term congestion in mmWave systems, fast RAN-based mechanisms (which do not necessarily require core network intervention) may be needed for inter-rTRP exchanges.

[0133] The need to mitigate short-term congestion of NR operations in the mmWave spectrum, with the need to more easily deploy self-backhauled NR cells, may lead to the need to develop an integrated framework that enables fast switching of access and backhaul links.

[0134] Additionally, over-the-air (OTA) coordination between rTRPs may be considered to mitigate interference and support end-to-end routing selection and optimization.

[0135] The following requirements and aspects may need to be addressed by integrated access and radio backhaul (IAB) for NR.

[0136] - Efficient and flexible operation of in-band and out-of-band broadcasting in indoor and outdoor scenarios

[0137] -Multi-hop and redundant connections

[0138] - End-to-end routing and optimization

[0139] -Backhaul link support with high spectral efficiency

[0140] - Legacy NR UE support

[0141] The conventional NR (new RAT) is designed to support half-duplex devices. In addition, half-duplex for IAB scenarios is supported and is worth targeting. In addition, full-duplex IAB devices can be studied.

[0142] In the IAB scenario, if each IAB node or relay node (RN) does not have scheduling capability, the donor gNB (DgNB) must schedule all links between the DgNB-related RNs and the UE. In other words, the DgNB can collect service information from all related RNs, make scheduling decisions for all links, and then notify each RN of the scheduling information.

[0143] Figure 7 Examples of parent links and child links are schematically illustrated.

[0144] like Figure 7 As shown, the link between the IAB node and the parent node is called the parent link, and the link between the IAB node and the child node / UE is called the child link. That is, the link between the MT and the parent DU is called the parent link, and the link between the DU and the child MT / UE is called the child link.

[0145] However, depending on interpretation or perspective, the link between the IAB node and the parent node may be referred to as a backhaul link, and the link between the IAB node and the child node / UE may be referred to as an access link.

[0146] The IAB node may receive a timeslot format configuration for communicating with a parent node and a timeslot format configuration for communicating with a child node / access UE.

[0147] In the existing IAB node, TDM operation in which DU and MT operate through different time resources has been performed. On the other hand, for efficient resource operation, resource multiplexing such as SDM / FDM, FC, etc. is required between DU and MT. Figure 7 As shown, the link between the IAB node (IAB MT) and the parent node is called the parent link, and the link between the IAB node (IAB DU) and the child node (child MT) is called the child link. At this time, the TDM operation between the parent link and the child link has been discussed, and the SDM / FDM and FD operations are being discussed.

[0148] DU and MT present in the same IAB node (or co-location) cannot operate simultaneously due to intra-node interference, time slot / symbol boundary misalignment, power sharing, etc., but can operate in TDM. On the other hand, multiplexing of SDM / FDM can be used between DU and MT. This multiplexing is suitable for example cases where there is almost no interference between panels because DU and MT use different panels. In this case, DU and MT present in the same IAB node (or co-location) can send or receive data or information at the same time, but each of DU and MT cannot perform transmission and reception at the same time or receive and transmit at the same time.

[0149] Alternatively, FD can be used between DU and MT. This is applicable to the case where there is little interference between DU and MT (for example, when the frequency domain in which the DU operates is far away from the frequency domain in which the MT operates). In this case, the DU and MT present in the same IAB node (or co-located) can freely send and receive data at the same time. The DU and MT can send or receive data at the same time, and each of the DU and MT can also perform sending and receiving at the same time or performing receiving and sending at the same time.

[0150] There may be N MT-CCs and M DU-cells in an IAB node. Fig. 9 An example is shown in which an IAB node consists of three MT-CCs (where N=3) and three DU-cells (where M=3). The MT-CCs present in the IAB node may operate through the same or different frequency resources, and one MT-CC may be connected to one or more parent DU-cells. The DU-cells present in the IAB node may operate through the same or different frequency resources.

[0151] For a specific MT-CC / DU-cell pair within the IAB node, for the following four Tx / Rx direction combinations, the MT-CC and DU-cell may adopt a TDM relationship or a non-TDM relationship, and for each Tx / Rx combination, TDM or non-TDM may vary.

[0152] -DU-Tx / MT-Tx

[0153] -DU-Rx / MT-Rx

[0154] -DU-Tx / MT-Rx

[0155] -DU-Rx / MT-Tx

[0156] For example, for a specific MT-CC / DU-cell pair, all of the four Tx / Rx combinations may operate in TDM. In this case, the corresponding DU-cell and the corresponding MT-CC should always operate in TDM regardless of the Tx / Rx direction of the DU-cell and the MT-CC. In another example, for a specific MT-CC / DU-cell pair, all of the four Tx / Rx combinations may operate in non-TDM. In this case, the corresponding DU-cell and MT-CC may always operate simultaneously in non-TDM regardless of the Tx / Rx direction of the DU-cell and the MT-CC. In another example, for a specific MT-CC / DU-cell pair, DU-Tx / MT-Tx and DU-Rx / MT-Rx may operate in non-TDM, and DU-Tx / MT-Rx and DU-Rx / MT-Tx may operate in TDM. The above operations relate to a method (e.g., SDM / FDM) for allowing simultaneous operation when the Tx / Rx directions of the DU-cell and the MT-CC are the same, and the method can operate simultaneously when the Tx / Rx directions of the DU-cell and the MT-CC are the same. For each specific MT-CC / DU-cell pair within the IAB node, TDM / non-TDM information for each Tx / Rx combination can be configured / determined differently or independently.

[0157] At this time, the IAB MT may be connected to two parent DUs using, for example, a dual connectivity method or a DAPS-HO method.

[0158] Network Controlled Repeater (NCR) in NR

[0159] Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their deployment. The deployment of conventional full-stack cells is an option, but it may not always be possible (e.g., without the availability of backhaul) or economically viable. As a result, new types of network nodes are considered to increase the flexibility of network deployment for mobile operators. For example, integrated access and backhaul (IAB), a new type of network node that does not require a wired backhaul, was introduced in Rel-16 and enhanced in Rel-17. Another type of network node is an RF repeater, which simply amplifies and forwards any signal they receive. RF repeaters have extensive deployment in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. In Rel-17, RAN4 specifies RF and EMC requirements for such RF repeaters for NR targeting both FR1 and FR2. Although RF repeaters provide a cost-effective means of extending network coverage, they have their limitations. RF repeaters simply perform amplification and forwarding operations without being able to consider various factors that can improve performance. These factors may include information about semi-static and / or dynamic downlink / uplink configurations, adaptive transmitter / receiver spatial beamforming, ON-OFF states, etc.

[0160] A network-controlled repeater is an enhancement of a conventional RF repeater with the ability to receive and process side control information from the network. The side control information may allow the network-controlled repeater to perform its amplification and forwarding operations in a more efficient manner. Potential benefits may include reduced unnecessary noise amplification, transmission and reception with better spatial directionality, and simplified network integration.

[0161] Figure 8 is a diagram illustrating an example of a topology in which a network controlled relay (NCR) performs transmission and reception between a gNB and a UE.

[0162] Reference Figure 8 , NCR may include a radio unit (RU) and a mobile terminal (MT).

[0163] The gNB may include a central unit (CU) and / or a distributed unit (DU), and the NCR may be connected to the gNB. In the NCR, the MT may form a control link with the gNB, and the RU may form a forwarding link for backhaul with the gNB and a forwarding link for access with the UE.

[0164] The RU of the NCR may consist of only the RF layer. The RU may receive a signal sent by the gNB through a forwarding link at the RF end, and may forward the received signal to the UE. As a result, the signal received from the UE may be received by the RF end, and the received signal may be forwarded to the gNB. The RU may send signals only between the gNB and the UE, and may not generate signals / channels by itself and send the generated signals / channels to the gNB / UE. Alternatively, the RU receives signals / channels from the gNB / UE but does not detect the received signals / channels. In order to forward the received signals, the RU may control the direction of the Tx / Rx beam, the DL / UL direction, ON / OFF information, the transmit (Tx) power, etc. at the RF end. However, this RU operation cannot be determined by the NCR itself, but may be fully controlled by the gNB.

[0165] The MT of the above-mentioned NCR may include an RF layer and L1, L2 and / or L3 layers. For example, the MT may include only an RF layer and an L1 layer, or may include L1 and L2 layers. Alternatively, the MT may include an RF layer and L1 / L2 / L3 layers. The MT may detect / receive a signal / channel sent by the gNB, and may generate a signal / channel to be sent to the gNB. In addition, the MT may receive information required to control the operation of the RU (e.g., side control information) from the gNB. In addition, the MT may not perform transmission and reception with the UE.

[0166] Fig. 9 is a diagram illustrating a radio frequency (RF) repeater and an NCR.

[0167] Reference Fig. 9 (a), existing RF repeaters can perform beamforming that applies omnidirectional or fixed direction. Fig. 9 (b), the NCR can adaptively adjust the transmit / receive beam direction of the NCR according to the UE position and the UE's channel conditions, thereby obtaining beamforming gain.

[0168] In addition, in the case of an existing RF repeater, since the DL / UL directions are not distinguished from each other in a TDD system, transmission and reception in the DL and UL directions are always performed simultaneously. Alternatively, only a fixed TDD configuration is applied to the existing RF repeater, so that switching between the DL direction and the UL direction is performed using a fixed time pattern. In contrast, the NCR can perform DL / UL switching while taking into account the TDD configuration. Thus, switching is considered. As a result, the NCR can enable adaptive DL / UL operation, which can minimize power consumption caused by forwarding unnecessary signals, and can also minimize interference.

[0169] In addition, in the case of existing RF repeaters, the power of received signals is always amplified and transmitted regardless of whether the gNB and UE transmit signals. As a result, unnecessary power consumption and interference to the surrounding environment are inevitably increased. In contrast, NCR performs ON / OFF operation, and when there is no signal to be sent to the gNB and UE, the operation of RU is turned off, so as not to transmit unnecessary signals.

[0170] In addition, in the case of existing RF repeaters, the power of the signal received at a fixed ratio is amplified and transmitted. When the signal is transmitted at an unnecessary high power, the interference affecting the surrounding environment can be reduced by reducing the transmission (Tx) power of the NCR. When the signal is transmitted at a low power, the transmission (Tx) power of the NCR is increased so that the signal can be stably transmitted to the receiver.

[0171] In addition, existing RF repeaters have been operating without identifying DL / UL time slot boundaries. On the other hand, in order for the NCR to adaptively adjust beamforming, ON / OFF, DL / UL direction, transmit power, etc. as described above, the NCR must know the transmit / receive (Tx / Rx) boundary of the downlink (DL). As a result, the RU operation can be applied differently for each unit time (e.g., time slot / symbol).

[0172] Side control information for NCR

[0173] In the following, for ease of description, operations in NCR will be assumed. However, the contents described below may be applied to devices outside NCR. Specifically, the contents described below may be applied to operations in RIS. For this reason, the NCR mentioned in the present disclosure may be replaced with "RIS" and expanded / interpreted. In this case, the RU may be used to forward signals from the gNB to the UE in the RIS, and to forward signals from the UE to the gNB in ​​the RIS, and the MT may be used to receive side control information required for signal transmission of the control RU from the gNB. At this time, the term "network" may be interpreted as "gNB" or "CU / DU" hereinafter. In addition, the term "gNB" may be interpreted as "network", "CU" or "DU" hereinafter.

[0174] In order for the NCR to forward the signal received by the RU, it is possible to consider adjusting the direction of the transmit / receive (Tx / Rx) beam, DL / UL direction, ON / OFF state, transmit (Tx) power, etc. at the RF end. However, the RU operation cannot be determined by the NCR itself, but can be completely controlled by the gNB. To this end, the MT can receive the information required to control the RU operation (i.e., side control information) from the gNB. The side control information can be sent through L1 / L2 signaling such as MAC-CE and DCI.

[0175] The above-mentioned side control information may include all or part of the following information.

[0176] - Beamforming information: Information about the transmit / receive (Tx / Rx) beam direction of the RU

[0177] Here, the beamforming information may include a beam direction for UL transmission to the gNB, a beam direction for DL ​​reception from the gNB, a beam direction for DL ​​transmission to the UE, and / or a beam direction for UL reception from the UE.

[0178] - Timing information for aligning the transmit / receive boundaries of the Network Controlled Repeater (NCR): Information for aligning the RU with the transmit / receive (Tx / Rx) slot symbol boundaries

[0179] - Information about UL-DL TDD configuration: Information about the DL / UL direction of the RU

[0180] -ON-OFF information for efficient interference management and improved energy efficiency: Information about the ON-OFF operation of the RU

[0181] -Power control information for efficient interference management: Information about the transmit (Tx) power of the RU, and such information may include the UL transmit (Tx) power to the gNB and / or the DL transmit (Tx) power to the UE.

[0182] The above-mentioned side control information may be applied differently for each time resource. In this case, it is necessary to indicate different kinds of side control information for each time resource. Specifically, when the side control information is sent through MAC-CE and / or DCI, the side control information may be sent through different MAC-CE and / or DCI for each time resource unit. In this case, it is necessary to send the side control information for each time resource unit. Taking this situation into consideration, when sending the side control information once, it may be considered to indicate the side control information for multiple time resource units. In this case, there may be a disadvantage in that the side control information for multiple time resource units must be determined and configured in advance, but efficient signaling is possible.

[0183] A method for instructing a beam change from RU to NCR based on various side control information during NCR operation in an NR environment will hereinafter be described in detail with reference to the accompanying drawings.

[0184] Indication of beam direction of gNB to RU link for NCR

[0185] Even when a fixed NCR without mobility is used, changes in scattering may occur. Alternatively, an NCR with mobility may also be used. Considering this situation, instructions for beam adaptation between the gNB and the RU (i.e., the RU included in the NCR) may be required. However, if only the RF layer is included in the RU, the RU cannot directly receive information related to the control of sending and receiving beams. Alternatively, even if there is an additional layer other than the RF layer in the RU, since the RU needs to relay transmission and reception, it is also possible to consider receiving or sending beam information related to beam adaptation from the MT. In addition, since it cannot be ruled out that the NCR with mobility after Rel-19 may be discussed instead of the fixed NCR, it is necessary to propose a method for instructing the MT using the beam information between the gNB and the RU by considering the above situation.

[0186] Since the RU cannot perform data communication with the gNB (i.e., it is impossible for the RU to directly receive information for the RU from the gNB), the NCR can basically determine or recognize that the transmit / receive (Tx / Rx) beam used by the MT is used as the transmit / receive (Tx / Rx) beam of the RU. However, since the transmit / receive (Tx / Rx) beam used by the MT is not fixed to one type, it is necessary to define which of the transmit / receive (Tx / Rx) beams of the MT will be used by the NCR as the RU beam. In this regard, at least one of the following methods can be considered.

[0187] For all scenarios and alternatives described below, the gNB may indicate beam information for the RU based on at least one of the scenarios and alternatives described below according to the capabilities of the NCR. Here, the capabilities of the NCR may be information about whether the backhaul link (RU) and the C-link (i.e., the control link of the MT) of the NCR can operate based on different beam directions. That is, the fact that the backhaul link has a different beam from the C-link means that a separate beam instruction for the backhaul link is possible, and the capability information may also be defined as a capability indicating whether a beam direction indication for the backhaul link is possible for the RU. In this case, if the capability that the beam direction indication for each of the C-link and the backhaul link is possible is reported to the gNB (or a report of the fact that the C-link and the backhaul link can operate based on different beams, or a report of the capability that the C-link and the backhaul link can operate based on different beams), the NCR may explicitly receive instruction information about the beam direction of the backhaul link from the gNB. In this case, for the beam direction of the backhaul link, the following scenario 1 may be applied. In other words, if capability information is reported that separate beam direction instructions for the backhaul link are possible, the NCR can receive explicit instructions about the beam direction of the backhaul link from the gNB.

[0188] On the other hand, if capability information that a separate beam direction instruction for the backhaul link is possible is reported (or, if capability information that the C-link and the backhaul link cannot operate based on different beams is reported), the NCR cannot receive an explicit instruction about the beam direction of the backhaul link from the gNB, so that the NCR can receive an instruction about the beam direction of the backhaul link according to a predetermined convention or protocol (scenario 2). In other words, if the backhaul link and the C-link use the same beam (i.e., there is no capability to receive an instruction about a separate beam direction for the backhaul link), the NCR can determine the beam direction for the backhaul link based on a predefined rule.

[0189] Hereinafter, a link for forwarding formed between a RU included in the NCR and the gNB (i.e., a gNB-RU link) will be defined as a backhaul link, and a link formed between a MT included in the NCR and the gNB (i.e., a gNB-MT link) will be defined as a C-link. In addition, a DL receive beam and / or UL transmit beam of the RU to be described below may correspond to a DL receive beam and / or UL receive beam for the backhaul link, and a DL receive beam and / or UL transmit beam of the MT may correspond to a DL receive beam and / or UL receive beam for the C-link. Hereinafter, for ease of explanation, a DL receive beam and / or UL receive beam for the C-link will be defined as a DL receive beam and / or UL transmit beam of the MT, and a DL receive beam and / or UL receive beam for the backhaul link will be defined as a DL receive beam and / or UL transmit beam of the RU.

[0190] Regarding scenarios 1 and 2 to be described below, for the beam of the forward return link of the NCR (or NCR-Fwd), the same TCI state as the TCI state configured for the operation of the MT (or NCR-MT) can be assumed (see RAN1#109-e session). In this case, an additional definition is used to indicate which TCI state among the multiple TCI states configured in the MT will be used to configure / apply the DL receive beam of the RU. For example, for time resources corresponding to specific time resources for DL ​​reception through the return link, the TCI state to be applied to the DL receive beam of the RU for the return link can be assumed to be the same as the TCI state to be applied to the MT. At this point, it is necessary to additionally consider the method for determining the TCI state to be applied to the DL receive beam of the RU when the MT does not perform DL reception in a specific time resource.

[0191] Alternatively, the DL receive beam to be applied to the RU or the TCI state of the RU's return link may be configured and / or determined independently of the TCI state currently applied to the MT. In this case, it is necessary to additionally consider a method for configuring the DL receive beam to be applied to the RU or the TCI state of the forward return link of the RU. Alternatively, it is also necessary to discuss a method for determining the beam direction of the UL transmission to be applied to the return link. If the UL in the C-link (or control link) for the MT of the NCR and the UL in the return link are based on TDM operations, the method of determining the UL transmission beam of the return link based on a specific time resource as described above may be inappropriate. Taking this situation into account, the beam of the RU for the return link in the time resource where the MT does not perform data transmission / reception can be determined as a beam to be applied to the RU (or return link) independently of the beam to be applied to the MT, as follows.

[0192] - A beam direction to be applied to a backhaul link (or forward backhaul link) is explicitly indicated (related to scenario 1 to be described later).

[0193] - The beam direction to be applied to the backhaul link is determined to be a beam corresponding to a beam applied to a specific signal / channel by the MT (related to scenario 2 which will be described later).

[0194] - The beam direction to be applied to the backhaul link is determined to be the beam corresponding to the beam most recently applied by the MT for transmission and reception (related to scenario 3 which will be described later).

[0195] In this regard, the RU beam for the backhaul link can be determined / applied by considering the relationship between the time resources for the backhaul link and the time resources for the control link. First, when the MT performs a sending and / or receiving operation in a specific time resource for performing sending / receiving for the backhaul link (i.e., when a sending action is performed simultaneously in the backhaul link and the control link), the beam of the forward backhaul link can be applied or determined as a beam corresponding to the beam direction (e.g., TCI state) to be applied to the NCR-MT (related to scenario 3). In contrast, if the MT does not perform a sending and / or receiving operation in a specific time resource (i.e., when simultaneous sending is not performed in the backhaul link and the control link), the beam of the RU for the forward backhaul link can be applied according to scenario 1 or scenario 2 to be described below. Hereinafter, scenarios 1 to 3 will be described in detail based on the above content.

[0196] 1. Scenario 1 - Explicit beam instructions for backhaul links

[0197] NCR can receive the transmit / receive beam of RU (or Tx / Rx beam of RU or Tx / Rx beam for NCR-Fwd) from gNB based on Tx / Rx beam information of MT (or Tx / Rx beam for C link). For example, gNB can directly indicate CR (or MT) on Tx / Rx beam information for backhaul link via C link. In this case, NCR (or MT) can be indicated by using Tx / Rx beam of RU (or beam direction of backhaul link) that is different in direction from Tx / Rx beam of MT from gNB.

[0198] (1) Method for indicating DL receive beam of RU

[0199] Among the beams of the RU, the DL receive beam for the backhaul link may be indicated (or notified) by the gNB through the following method. Here, the DL receive beam of the RU may be applied as the receive beam of the MT corresponding to the instruction from the gNB, or may be aligned with the MT receive beam corresponding to such an instruction. That is, the gNB may indicate (notify) the DL receive beam of the RU by instructing the MT or NCR to identify the SSB index, CSI-RS index, TCI state ID, etc. related to the MT (or C-link) via RRC / MAC-CE / DCI.

[0200] In addition, the TCI state ID may be a UE-specific PDSCH configuration indicating a BWP (BWP-DownlinkDedicated) defined in the above-mentioned "PDSCH-Config" (see "3GPP TS 38.331"). That is, since the CSI-RS and / or TCI state ID are BWP-specific to the MT (for example, since the CSI-RS and / or TCI state ID are not cell-common configurations but UE-specific values ​​or configurations), it is necessary to pre-define a reference (standard) indicating which BWP will be indicated by the DL receive beam of the RU through the CSI-RS index and / or TCI state ID. The reference BWP used as a standard may be pre-committed / agreed upon. For example, the reference BWP (or the BWP corresponding to the TCI state ID used to indicate the DL receive beam of the RU) may be the default BWP of the MT, or may be the initial BWP of the MT. Alternatively, the gNB may indicate or specify at least one of the BWPs of the MT as a reference BWP via RRC / MAC-CE / DCI. For example, the gNB may indicate one of the multiple beams configured for the C-link as a DL receive beam for the backhaul link via a TCI state ID associated with the C-link.

[0201] That is, when the gNB determines that beam instruction for the backhaul link of the NCR is possible based on the capability information, the gNB may indicate the beam for the backhaul link through information (via RRC signaling) about a TCI state ID associated with at least one beam among multiple beams configured for the control link. In this case, the NCR may configure / determine the beam for the backhaul link (or the DL reception beam for the backhaul link) as a beam corresponding to the indicated TCI state ID among multiple beams for the control link.

[0202] Alternatively, when the gNB indicates the DL receive beam (or the DL receive beam of the RU), the gNB may also send information about the number of time slots, which is the time slot offset (hereinafter referred to as time offset information). Here, the time offset information may include information about the time offset in units of time slots, subframes, or symbols. For example, when the time offset information for K time slots is also indicated together with the indication of the DL receive beam of the RU, the gNB may expect that after the beam change has been indicated (or after the DL RS of the beam change has been indicated), the change or switching of the DL receive beam of the RU will be performed from K time slots relative to the MT position. Alternatively, even if the time slot offset information of the number of time slots is not separately indicated, it may be defined that the change of the DL receive beam of the RU indicated after a certain time has passed according to a predefined commitment or agreement may be applied. For such a time offset, a specific operation may be agreed as a default behavior. For example, if a time slot offset (or number of time slots) is indicated, the indicated DL receive beam may be applied to the RU during a time period corresponding to the indicated time slot offset from a predetermined commitment time. Alternatively, when the change of the RU's DL beam and the time offset (K time slots / K subframes / K symbols) are indicated together, the RU's DL beam direction can be configured toward the indicated beam direction during a time period corresponding to the time offset from the predetermined commitment time. In addition, after the above-mentioned time period has passed, the direction of the RU's DL beam can be changed to the direction of the previous DL beam used before the instruction of the beam direction, or can be changed to a pre-agreed default beam direction.

[0203] Alternatively, when an explicit RU DL beam direction (or a backhaul link beam direction) is not indicated, the DL beam direction of the RU may be applied or determined as a default beam through a predetermined protocol or commitment (for example, if capability information indicating that a beam direction for the backhaul link is possible is reported, but explicit instruction information has not yet been received). The default beam may be configured or committed through an indication method in scenario 2 to be described later. Here, the application time of the default beam or the time of the default beam may indicate an example case where there is no indication of an explicit beam direction after the valid time for the indication of the explicit beam direction expires, may be an example case where there is no valid DL beam for the RU in a specific time resource, or may be an example case where the backhaul link is shut down. In other words, if there is no indication of an explicit beam direction or if there is no valid RU DL beam (or a backhaul link beam) in a specific time resource, a previously committed / agreed default beam may be applied as the DL beam of the RU. Such a default beam may be determined / configured by the method of scenario 2 to be described below, etc. Alternatively, the forwarding operation through the backhaul link may not be performed during specific time resources (or during the time when the default beam is applied).

[0204] (2) Method for indicating the UL transmit beam of an RU

[0205] The gNB may explicitly indicate (via the MT) the UL transmit beam of the RU for the backhaul link (among the beams of the RU). Here, the gNB may indicate the UL transmit beam direction of the RU by indicating the beam direction corresponding to the transmit beam of the MT.

[0206] Specifically, the gNB can instruct the MT to identify the UL transmit beam of the RU by indicating the UL transmit beam of the MT via SRI, etc. Similar to the DL receive beam of the RU mentioned above, the UL transmit beam of the MT is a BWP-specific configuration, so that the BWP to which the UL transmit beam of the RU is indicated can be defined in advance by a predetermined protocol / commitment. For example, the BWP to which the UL transmit beam of the RU is indicated can be a default BWP for the MT, or can be an initial BWP for the MT. Alternatively, the gNB may designate or prescribe (or configure) at least one BWP among the BWPs of the MT as a BWP including a TCI state ID (or SRI) for indicating the UL transmit beam of the RU through RRC / MAC-CE / DCI.

[0207] That is, if the gNB determines that the beam of the backhaul link can be indicated through the capability information, the gNB may indicate the UL transmission beam of the backhaul link (related to at least one of the multiple beams configured for the control link) through the SRI for the control link. In this case, the NCR may receive an instruction for a beam (e.g., a UL transmission beam) to be used for the backhaul link among the multiple beams of the control link through the indicated SRI.

[0208] Alternatively, when the gNB indicates the UL transmit beam (or the UL transmit beam of the RU), the gNB may also send information about the number of time slots (hereinafter referred to as time offset information). Here, the time offset information may include information about the time offset in units of time slots, subframes, or symbols. For example, when the time offset information for K time slots is also indicated together with the indication of the UL transmit beam of the RU, the gNB may expect that after the beam change has been indicated (or after the instruction for the beam change has been received), the change or switching of the UL transmit beam of the RU will be performed starting from K time slots relative to the MT position. Alternatively, even if the time slot offset information of the number of time slots is not separately indicated, it may be defined that the change of the UL transmit beam of the RU indicated after a certain time has passed according to a predefined commitment or agreement may be applied. For such a time offset, a specific operation may be agreed as a default behavior. For example, if a time slot offset (or number of time slots) is indicated, the indicated UL transmit beam may be applied to the RU during a time period corresponding to the indicated time slot offset from the committed time. Alternatively, when a change of the UL beam of the RU and a time offset (K slots / K subframes / K symbols) are indicated together, the beam direction of the UL of the RU toward the indicated beam direction can be configured during a time period corresponding to the time offset from the predetermined commitment time. In addition, after the above-mentioned time period has passed, the direction of the DL beam of the RU can be changed to the direction of the previous DL beam used before the beam direction instruction, or can be changed to a pre-agreed default beam direction.

[0209] Alternatively, when an explicit RU UL beam (or a beam for a backhaul link) is not indicated, the UL beam direction of the RU may be applied or determined as a default beam by a predetermined protocol or commitment. The default beam may be configured or committed by the indication method in scenario 2 to be described later. Here, the application time of the default beam or the time of the default beam may indicate an example case where there is no indication of an explicit beam direction after the valid time for the indication of the explicit beam direction expires, may be an example case where there is no valid UL beam of the RU in a specific time resource, or may be an example case where the backhaul link is shut down. In other words, if there is no indication of an explicit beam direction or if there is no valid RU UL beam (or backhaul link beam) in a specific time resource, the previously committed / agreed default beam may be applied as the UL beam of the RU. Such a default beam may be determined / configured by the method of scenario 2 to be described below, etc. Alternatively, forwarding operations through the backhaul link may not be performed during a specific time resource (or during the time when the default beam is applied).

[0210] (3) RU beam instructions when there is no distinction between RU DL receive beams and RU UL transmit beams

[0211] Alternatively, in the case where there is no distinction between the DL receive beam of the RU and the UL transmit beam of the RU, the gNB may explicitly indicate the beam of the RU for the backhaul link (or the RU DL receive beam and the RU UL transmit beam) by the above method. That is, the gNB may indicate the change of the DL receive beam of the RU and the UL transmit beam of the RU for the backhaul link by a single instruction. For example, the gNB may indicate the change of both the DL receive beam of the RU and the UL transmit beam of the RU by indicating specific information for the beam change of the RU to the MT. Here, the single instruction (or the instruction of the specific information) may be indicated based on the DL receive beam of the MT, or may be indicated based on the UL transmit beam of the MT. In addition, for ease of explanation, in the following description, the DL receive beam of the RU and the UL transmit beam of the RU will be defined as the beam of the RU or the beam of the backhaul link.

[0212] For example, the gNB may instruct the MT to change the beam of the RU for the backhaul link using an SSB index, a CSI-RS index, a TCI state ID, etc. through RRC / MAC-CE / DCI. Alternatively, the gNB may instruct the MT to change the beam of the RU for the backhaul link using an SRI, etc. In addition, there may be no independent beam report in the RU, so that the beam of the RU may be aligned based on the beam of the MT. Therefore, the QCL relationship between the transmit / receive (Tx / Rx) beams of the MT may be equally applied to the (receive / transmit) beams of the RU. For example, with respect to the above method, if the gNB instructs the MT to identify the SSB index and / or CSI-RS index for the beam change of the RU, the DL receive beam of the RU may be aligned with the DL receive beam of the MT corresponding to the indicated SSB index and / or CSI-receive index, and the UL transmit beam of the RU may be aligned with the UL transmit beam of the MT corresponding to the indicated SSB index and / or CSI-receive index. In other words, the gNB can indicate the beam of the RU through the SSB index and / or CSI reception index related to the control link for the MT.

[0213] Alternatively, time offset information (or information about the number of time slots) may be sent together with the beam instruction of the RU. Here, the time offset information may include information about the time offset in units of time slots, subframes, or symbols. For example, when time offset information for K time slots is also indicated together with the beam instruction of the RU, the gNB may expect that after the beam change has been indicated (or after the instruction for the beam change has been received), the change or switching of the beam of the RU will be performed starting from K time slots relative to the MT position. Alternatively, even if the time slot offset information for the number of time slots is not indicated separately, it may be defined that the application indicates the change of the beam of the RU after a certain time has passed according to a predefined commitment or agreement. For such a time offset, a specific operation may be agreed as a default behavior. For example, if a time slot offset (or number of time slots) is indicated, the indicated RU beam may be applied to the RU during a time period corresponding to the indicated time slot offset starting from a predetermined commitment time. Alternatively, when the beam change and time offset (K slots / K subframes / K symbols) of the RU are indicated together, the beam direction of the RU toward the indicated beam direction can be configured during a time period corresponding to the time offset from the predetermined commitment time. In addition, after the above time period has passed, the beam of the RU can be changed to the direction of the previous DL beam used before the beam direction instruction, or can be changed to a pre-agreed default beam direction.

[0214] Alternatively, when an explicit RU beam (or a beam for a backhaul link) is not indicated, the beam of the RU may be applied or determined as a default beam by a predetermined protocol or commitment. The default beam may be configured or committed by the instruction method in scenario 2 to be described later. Here, the application time of the default beam or the time of the default beam may indicate an example case where there is no instruction for an explicit beam direction after the validity time of the instruction for the explicit beam direction expires, may be an example case where there is no valid RU beam in a specific time resource, or may be an example case where the backhaul link (NCR-Fwd) is shut down. In other words, if there is no instruction for an explicit beam direction or if there is no valid RU beam (or a beam for a backhaul link) in a specific time resource, a previously committed / agreed default beam may be applied as the beam of the RU. Such a default beam may be determined / configured by the method of scenario 2 to be described below, etc. Alternatively, forwarding operations through the backhaul link may not be performed during a specific time resource (or during the time when the default beam is applied).

[0215] In addition, the above-mentioned "using a single instruction to indicate the change of the DL receive beam and / or the UL transmit beam, instead of executing the instructions of the DL receive beam and the UL transmit beam separately" can be performed based on the integrated TCI framework. Here, the integrated TCI framework is a concept introduced in Rel-17 MIMO, and is different from the existing TCI framework that independently indicates the TCI state for each DL / UL channel / RS. For example, the existing TCI framework has advantages in flexibility but disadvantages in signaling overhead and delay. That is, for most UEs to which only one beam is applied at a time, the gNB must execute a beam change instruction for each DL / UL channel / RS separately in order to perform the beam change of the UE. In contrast, the integrated TCI framework (in Rel-17 MIMO) can support integrated beam control for DL / UL data channels (PDSCH / PUSCH), DL / UL control channels (PDCCH / PUCCH), AP CSI-RS and SRS based on the (indicated) TCI state after defining the joint TCI state. For example, the integrated TCI framework can use the DL DCI format (1_1 / 1_2) in a DCI-based manner, and can include or omit PDSCH allocation information (ie, data assignment). That is, in the integrated TCI framework, the above DL DCI format can be used for beam instructions through TCI states even if there is no data / channel to be sent and / or received. In this case, some of the existing TCI field indicator values ​​in the DCI can be changed and indicated for use as beam instructions.

[0216] Based on the above scenario (or based on the integrated TCI framework), in the manner of "indicating the change of the DL receive beam or the UL transmit beam with a single instruction, rather than executing the instructions of the DL receive beam and the UL transmit beam separately", the gNB can instruct the NCR to simultaneously change the beams of the RUs included in the NCR (or the DL receive beam and the UL transmit beam of the RU) by indicating the joint TCI state. Here, the joint TCI state may be a TCI state related to the C link as a control link. In this way, when the change of the DL receive beam and the UL transmit beam of the RU is indicated by the instruction of the joint TCI state, the application time of the joint TCI state and the indicated application time of the joint TCI state may be indicated together with the instruction of the ID of the joint TCI state. Alternatively, it may be considered that the application time of the joint TCI state and the indicated application time of the joint TCI state are configured by a predetermined protocol or commitment. For example, the application time of the joint TCI state may be applied continuously after a specific number of time slots / symbols have passed since the instruction of the joint TCI state was received through the NCR or MT, or may be applied from the reception time point.

[0217] 2. Scenario 2 - RU beam determination based on predefined rules

[0218] Scenario 2 describes a case where the transmit / receive (Tx / Rx) beam of the RU is not directly indicated, but uses a beam corresponding to a specific transmit / receive beam (i.e., a predefined rule) of the MT that is pre-agreed / defined / configured (e.g., when the NCR does not have the capability to receive instructions for the beams of the backhaul link, or even if the NCR has the capability, the NCR does not receive beam instructions from the gNB). For example, although the gNB does not directly indicate the transmit / receive beams for the backhaul link to the MT, the gNB may expect that the transmit / receive beams for the backhaul link will be configured based on a predetermined commitment or protocol to be described below. In this case, the transmit / receive beams of the RU may be pre-defined / agreed / configured to correspond to the beams used by the MT for transmission and reception of a specific signal / channel. In this case, the transmit / receive beams of the RU and the transmit / receive beams of the MT may be different from each other according to the beam directions indicated by the gNB to the MT of the NCR.

[0219] Hereinafter, scenario 2 described below may be applied (or limited) to situations where the frequency of MT operation and the frequency of RU operation are the same or at least belong to the same band. That is, scenario 2 may be applied to situations where the time and / or frequency resources between MT and RU are consistent, or the time and / or frequency resources of MT and RU partially overlap, or even if the time and / or frequency resources of MT and RU do not actually overlap, the frequency bands are closely adjacent to each other, so that the transmission situation may exist as an adjacent frequency band between the transmission of MT and the reception of RU (and / or between the transmission of RU (or NCR-Fwd) and the reception of MT). Among the above situations, the following alternatives may be considered to indicate the DL receive beam of RU. Alternatively, as described above, scenario 2 may be applied to situations where the transmission or reception for the control link and the transmission or reception for the return link are not performed simultaneously.

[0220] For example, whether to apply scenario 2 described below can be determined based on whether the time resources of the MT or C link overlap with the time resources of the RU or the return link. For example, when the time resources of the MT or C link and the time resources of the RU or the return link do not overlap (and / or when there is no explicit instruction according to scenario 1), the beam of the return link can be determined according to the predefined rules described in scenario 2.

[0221] In addition, the alternative scheme to be described below may be based on the integrated TCI framework. That is, when the NCR determines the DL receive beam of the RU by the method to be described below, the NCR may determine that the UL transmit beam of the RU is changed to a UL transmit beam connected to the DL receive beam of the RU, which UL transmit beam has been pre-agreed / defined / configured, or the NCR may determine that the beam change has been instructed. Alternatively, the NCR may determine that the UL transmit beam of the RU is changed to a UL transmit beam connected to the DL receive beam of the RU, which UL transmit beam has been pre-agreed / defined / configured, or the NCR may determine that the beam change has been instructed. Here, the connection between the DL receive beam and the UL transmit beam of the RU may be determined based on the joint TCI state of the NCR.

[0222] When the DL receive beam and the UL transmit beam of the RU are changed by the instruction of the joint TCI state, the application time of the joint TCI state and the indicated application time of the joint TCI state may be configured by a predetermined protocol or commitment. For example, the application time of the above-mentioned joint TCI state may be located after a specific number of time slots / symbols from the time point indicating the joint TCI state, or may correspond to the indicated time.

[0223] (1) Alternative 1 - Based on predefined CSS

[0224] The (DL) receive beam of the RU may be predefined / configured / agreed to be aligned or correspond to the receive beam of the MT applied to receive the PDCCH in the Type0-PDCCH CSS. In other words, the DL receive beam of the RU for the backhaul link may correspond to the receive beam of the MT used to receive the signal used by the gNB to broadcast system information.

[0225] Regarding the instruction of the DL receive beam (or the DL downlink receive beam of the RU), the gNB may also pre-agree / define / configure the time offset information of the number of time slots (or time offset) related to the instruction of the DL receive beam (or the time offset information may be sent together). For example, the DL receive beam of the RU may be changed from a specific time to correspond to a specific beam direction of the MT according to a predetermined commitment or protocol. Alternatively, the beam change according to alternative 1 of scenario 2 may be applied to a time period other than the instruction of the beam change and time offset according to the above scenario 1. For example, as described above, the beam change according to alternative 1 of scenario 2 may be defined as a default operation. Specifically, when the change to the first DL receive beam and the time offset of K time slots are indicated together according to scenario 1, the NCR may change the DL receive beam of the RU to the first DL receive beam based on the K time slot time, but when the application of the first DL receive beam change according to scenario 1 is terminated, the DL receive beam of the RU may be configured / changed according to alternative 1. Alternatively, when there is no instruction for beam changing according to scenario 1, beam changing according to alternative 1 of scenario 2 may be applied.

[0226] (2) Alternative 2 - Based on a predefined search space

[0227] In alternative 2, the reception beam of the RU may be pre-agreed / defined / configured to correspond to a (DL) reception beam used by the MT for PDCCH reception in a specific search space (search space) among the reception beams of the MT. Here, the specific search space may be a search space corresponding to a search space ID indicated by the gNB.

[0228] Specifically, the receive beam of the RU may be pre-agreed / defined / configured to correspond to a receive beam of the MT configured for receiving a specific search space that is not used for the purpose of broadcasting system information. Alternatively, when the gNB sends an MT-specific (or UE-specific) control signal that is not used for the purpose of broadcasting system information, the receive beam of the RU may be pre-defined / agreed / configured to correspond to a receive beam of the MT used to receive the control signal. As described above, since the search space ID used to send the MT-specific control signal is sent using the MT-specific BWP (or UE-specific BWP), the receive beam of the RU must specify / define which of the BWPs is associated with the receive beam of the MT. For example, the receive beam of the RU may correspond to the receive beam of the MT in the search space associated with a specific BWP of the MT (e.g., a default BWP or an initial BWP, etc.) according to a predetermined agreement or commitment. Alternatively, the gNB may also indicate the search space ID for the MT corresponding to the receive beam of the RU and the ID of the corresponding BWP.

[0229] In addition, the application time of the receive beam of the RU according to alternative 2 of scenario 2 may be determined based on a predefined / configured / agreed time offset, or may be a time period in which the beam change and time offset according to scenario 1 are not applied. For example, as described above, the beam change according to alternative 2 of scenario 2 may be defined as a default operation. Specifically, when a beam change and a time offset of K time slots for the first DL receive beam are instructed together according to scenario 1, the NCR may change the DL receive beam of the RU to the first DL receive beam based on the K time slot time, but when the application of the change of the first DL receive beam according to scenario 1 is terminated, the DL receive beam of the RU may be configured / changed according to alternative 1. Alternatively, when there is no instruction for a beam change according to scenario 1, the beam change according to alternative 2 of scenario 2 may be applied.

[0230] Alternatively, with respect to the application of alternative 2, if the gNB does not indicate a search space ID for a specific search space, the ID of the specific search space may be pre-agreed / committed. That is, even without an explicit instruction of a specific search space from the gNB, the receive beam of the RU may be pre-agreed / committed to correspond to the receive beam used or applied by the MT in the pre-agreed / committed specific search space. For example, the specific search space may be pre-agreed / committed to be a search space with the lowest index, the highest index, or an intermediate index among the search spaces of the MT. In this case, the BWP associated with the pre-agreed / committed specific search space may also be pre-agreed / committed to be an active BWP, a default BWP, an initial BWP, or a BWP with the highest index (or a BWP with the lowest index).

[0231] (3) Alternative 3 - Based on predefined CORESET

[0232] In alternative 3, the receive beam of the RU may be pre-committed / defined / configured to correspond to the receive beam that the MT is to use for a specific CORESET among the receive beams of the MT. Here, the specific CORESET may be configured / determined by a CORESET ID indicated by the gNB. Alternatively, a specific CORESET may be pre-committed / agreed / defined.

[0233] Alternatively, unlike alternatives 1 and 2 above, the gNB may indicate the receive beam of the MT by indicating the CORESET ID without indicating a specific search space to the MT. Since the CORESET is also BWP-specific, similar to alternative 2, the CORESET may be a specific CORESET indicated for a specific BWP (e.g., default BWP or initial BWP, etc.) of the MT, which has been pre-agreed / committed. Alternatively, the gNB may indicate the CORESET ID and BWP ID (related to the receive beam of the RU) of the MT together.

[0234] Alternatively, information about the number of time slots (which is time offset information) may also be indicated in the instruction of the DL receive beam. For example, if the gNB indicates K time slots for a specific CORESET ID together with the receive beam of the MT, the gNB may expect that after indicating the DL RS for beam change, the DL receive beam of the RU will switch to the indicated direction starting from K time slots based on the MT position. Alternatively, even if the time offset information for the number of time slots is not indicated, the indicated change of the DL receive beam may be applied starting from a specific time according to a predetermined commitment or agreement. This may mean that a specific operation is agreed as a default operation for the time slot offset (i.e., included in the time offset information), and if the time slot offset is not indicated, the default operation is performed, and if the time slot offset is indicated, the indicated operation is performed. For example, if the time slot offset is indicated, the indicated DL receive beam may be applied to the RU during a time period corresponding to the indicated time slot offset starting from the committed time. For example, when a DL beam change and K time offset (K slots / K subframes / K symbols) of a RU are indicated, the DL receive beam of the RU is set to the indicated beam (or beam direction) during a time period corresponding to the K time offset (K slots / K subframes / K symbols) starting from the commitment time. After the time period has passed, the DL receive beam of the RU may be set to the DL receive beam before such instruction, or may be set to a pre-agreed default beam.

[0235] Alternatively, with respect to the application of alternative 3, when the gNB does not indicate a specific CORESET ID, a specific CORESET ID may be pre-committed / agreed to. That is, even if there is no explicit indication of the gNB for a specific CORESET ID, the receive beam of the RU may be pre-committed / agreed to correspond to a receive beam to be used or applied by the MT, which corresponds to a specific CORESET ID that has been explicitly pre-committed / agreed to. For example, the specific CORESET ID may be pre-committed / agreed to be the lowest index, the highest index, or the middle index among the (configured) CORESET IDs for the MT. In this case, the BWP associated with the specific CORESET ID that has been pre-committed / agreed to may also be committed / agreed to be an active BWP, a default BWP, an initial BWP, or a BWP with the highest index (or a BWP with the lowest index).

[0236] Alternatively, as described above, when there is no overlap between time resources for the control link and time resources for the backhaul link (i.e., when transmission or reception in the control link and transmission or reception in the backhaul link are not performed simultaneously), alternative 3 may be applied. In addition, when there is no explicit instruction according to scenario 1, or when there is no ability to receive an explicit instruction according to scenario 1, the predefined rule according to alternative 3 may be applied. For example, when transmission or reception in the control link and transmission or reception in the backhaul link are not performed simultaneously and there is no explicit instruction according to scenario 1, or when there is no ability to receive an explicit instruction according to scenario 1, a beam for the backhaul link may be determined according to alternative 3 based on a CORESET with a lowest index among CORESETs related to the control link. As described above, a beam for the backhaul link may be determined by considering a QCL related to a CORESET with a lowest index.

[0237] (4) Alternative 4 - Based on TCI Status ID

[0238] The receive beam of the RU may be pre-committed / defined to correspond to the receive beam of the MT to which the TCI state ID indicated by the gNB is applied.

[0239] Alternatively, information about the number of time slots (which is time offset information) may also be indicated in the instruction of the DL receive beam. For example, if the gNB indicates K time slots for a specific CORESET ID together with the receive beam of the MT, the gNB may expect that after indicating the DL RS for beam change, the DL receive beam of the RU will be switched to the indicated direction starting from K time slots based on the MT position. Alternatively, even if the time offset information of the number of time slots is not indicated, the indicated change of the DL receive beam may be applied starting from a specific time according to a predetermined commitment or agreement. This may mean that a specific operation is agreed as a default operation for a time slot offset (i.e., included in the time offset information), and if the time slot offset is not indicated, the default operation is performed, and if the time slot offset is indicated, the indicated operation is performed. For example, if a time slot offset is indicated, the indicated DL receive beam may be applied to the RU during a time period corresponding to the indicated time slot offset from the committed time. For example, when a DL beam change and a K time offset (K slots / K subframes / K symbols) of a RU are indicated together, the DL receive beam of the RU is set to the indicated beam (or beam direction) during a time period corresponding to the K time offset (K slots / K subframes / K symbols) from the commitment time. After the time period has passed, the DL receive beam of the RU may be set to the DL receive beam before such instruction, or may be set to a pre-agreed default beam.

[0240] Alternatively, with respect to alternative 4, when the TCI state ID is not indicated from the gNB, a specific TCI state ID associated with the determination of the receive beam of the RU may be pre-committed or defined. For example, the specific TCI state ID may be pre-committed / agreed to be the lowest index or the highest index among the (configured) TCI state IDs for the MT. In this case, the BWP associated with the specific TCI state ID that has been pre-committed / agreed may also be committed / agreed to be the active BWP, the default BWP, the initial BWP, or the BWP with the highest index (or the BWP with the lowest index).

[0241] Alternatively, as described above, when there is no overlap between time resources for the control link and time resources for the backhaul link (i.e., when transmission or reception in the control link and transmission or reception in the backhaul link are not performed simultaneously), alternative scheme 4 may be applied. In addition, when there is no explicit instruction according to scenario 1, or when there is no ability to receive an explicit instruction according to scenario 1, the predefined rule according to alternative scheme 4 may be applied. For example, when transmission or reception in the control link and transmission or reception in the backhaul link are not performed simultaneously and there is no explicit instruction according to scenario 1, or when there is no ability to receive an explicit instruction according to scenario 1, the beam for the backhaul link may be determined by applying the integrated TCI for the control link according to alternative scheme 4 to the DL and / or UL for the backhaul link.

[0242] (5) Alternative 5 - Based on the reception of side control information

[0243] In alternative 5, when the side control information for controlling the backhaul link of the RU among the receive beams of the MT is used, the receive beam of the RU may be pre-committed / defined / configured to correspond to the receive beam to be used by the MT. In this case, the side control information may be sent via the PDCCH in the search space for the MT, via the PDSCH, or via both the PDCCH and the PDSCH. For each case, the following options 1, 2, and 3 may be considered.

[0244] 1) Option 1: When the side control information is transmitted only via PDCCH in the search space

[0245] In this case, since the search space corresponds to the MT-specific search space, the proposed method of the above-mentioned "Alternative Solution 2" can be used. However, since there are multiple search spaces to which such side control information is sent, it is necessary to clearly define whether Option 1 is applied to the case of sending side control information for a specific search space (here, the case of directly indicating the search space ID can be the same as the above-mentioned Alternative Solution 2). For example, the MT may assume that the change of the DL receive beam of the RU is indicated based on the side control information received in the predefined / agreed specific search space. In this case, the NCR may determine the DL receive beam of the MT applied to the specific search space to receive the side control information as the DL receive beam of the RU, or may assume that such determination is indicated by the gNB. For example, the specific search space may be a search space with the smallest or highest index among the search space IDs. Alternatively, the specific search space ID may be pre-agreed / defined as at least one ID among multiple search space IDs for the MT. At this time, the specific search space may be limited to the BWP for the MT to receive the side control information, may be configured for a specified specific BWP, or may be a search space for a specific BWP according to a predetermined agreement / commitment. For example, the specific search space may be a default BWP or an initial BWP, or may refer to a BWP with a lowest or highest BWP ID.

[0246] 2) Option 2: When the MT side control information is sent only via PDSCH

[0247] Option 2 can be an example case where the gNB instructs the MT to change the DL receive beam of the RU via PDSCH. In this case, the gNB can expect that the DL receive beam of the RU will be changed to the beam for which the MT has received the corresponding PDSCH.

[0248] 3) Option 3: When the side control information of the MT is transmitted through both PDCCH and PDSCH in the search space

[0249] In option 3, the DL receive beam of the RU can be configured by mixing the methods of option 1 and option 2. Specifically, the DL receive beam of the RU can be aligned with the beam of the search space where the MT receives the side control information, or can be aligned with the receive beam of the MT of the PDSCH that receives the side control information. In this case, there may be a difference in the change of the DL receive beam of the RU in the first case where the side control information is indicated as the search space and in the second case where the side control information is indicated as the PDSCH. For example, the timing point of changing the DL receive beam of the RU in the first case may be different from the timing point of changing the DL receive beam of the RU in the second case. For example, in the first case where the side control information is indicated as the search space, the DL receive beam of the RU may be changed after a specific time offset that has been indicated (or pre-committed). In the second case where the side control information is indicated as the PDSCH, the DL receive beam of the RU may be changed from a specific time that has been pre-committed (for example, from the start time resource of the next subframe). Alternatively, when indicated as a search space, the RU's DL receive beam may change only during specific time resources that have been indicated (or pre-committed), and when indicated as a PDSCH, the RU DL receive beam may change starting from a specific time that has been pre-committed.

[0250] Alternatively, in Option 1 to Option 3, the receive beam of the RU is described as a beam for receiving downlink (DL) data in the backhaul link, but as described above, it can be seen that not only a change in the DL receive beam for the backhaul link but also a change in the UL receive beam for the backhaul link is indicated. In other words, the methods proposed in Option 1 to Option 5 may be interpreted as indicating changes in both the DL receive beam and the UL transmit beam of the RU. That is, there may be no independent beam report related to the beam of the RU so that the beam of the RU can be aligned with the beam of the MT, and furthermore, the QCL relationship between the transmit / receive (Tx / Rx) beams of the MT may be equally applied to the receive / transmit (Tx / Rx) beams of the RU. For example, when the gNB instructs the MT to change the beam of the RU through the CORESET ID (and / or BWP ID), the DL receive beam of the RU can be aligned with the receive beam of the MT corresponding to the instructed CORESET ID (and / or BWP ID), and can be aligned with the transmit beam of the MT corresponding to the instructed CORESET ID (and / or BWP ID).

[0251] Alternatively, information about the number of time slots (which is time offset information) can also be indicated in the instruction of the RU's DL receive beam and UL transmit beam. For example, when the gNB indicates the MT's receive beam and K time slots together, the gNB can expect that after such an instruction has appeared, the instructed directions of the RU's DL receive beam and the RU's UL transmit beam will change from K time slots based on the MT position. Alternatively, even if the time offset information for the number of time slots is not indicated, the change of the indicated RU's DL receive beam and the indicated RU's UL transmit beam can be applied from a specific time according to a predetermined commitment or agreement. This can mean that a specific operation is agreed to be a default operation for a time slot offset (i.e., included in the time offset information), and if the time slot offset is not indicated, the default operation is performed, and if the time slot offset is indicated, the indicated operation is performed. For example, if a time slot offset is indicated, the indicated DL receive beam and the indicated DL transmit beam can be applied to the RU during a time period corresponding to the indicated time slot offset starting from the committed time. For example, when the RU's DL receive beam changes, the RU's UL transmit beam changes, and the K time offset (K time slots / K subframes / K symbols) are indicated together, the RU's DL receive beam and the RU's UL transmit beam are set to the indicated beam (or beam direction) during a time period corresponding to the K time offset (K time slots / K subframes / K symbols) starting from the commitment time. After the time period has passed, the RU's DL receive beam may be set to the RU's DL receive beam before such an instruction has appeared, and the RU's UL transmit beam may be set to the RU's UL transmit beam before such an instruction has appeared, or may be set to a pre-agreed default beam.

[0252] Alternatively, separately from the instruction of the DL receive beam of the RU described above, the transmit beam direction of the MT applied when the MT transmits a specific signal / channel may be indicated as the UL transmit beam of the RU. That is, in order to indicate a change in the UL transmit beam of the RU, when the gNB indicates a RACH opportunity or a specific RACH preamble for the MT through side control information, the UL transmit beam of the RU may be aligned with the UL transmit beam of the MT during the transmission of the RACH preamble or the RACH opportunity. Alternatively, in order to indicate a change in the UL transmit beam of the RU, when the gNB indicates a specific SRI for the MT through side control information, the UL transmit beam of the RU may be aligned with the UL transmit beam of the MT (in which the SRS corresponding to the specific SRI has been used or applied).

[0253] 3. Scenario 3 - Based on the beam currently applied to MT

[0254] Regarding scenario 3, the gNB may expect the currently applied transmit / receive (Tx / Rx) beam of the MT and the transmit / receive (Tx / Rx) beam of the RU (or NCR-Fwd) to be aligned, or may instruct the transmit / receive (Tx / Rx) beam of the MT and the transmit / receive (Tx / Rx) beam of the RU to be aligned. In this case, the gNB may expect that the transmit / receive (Tx / Rx) beam of the MT in the most recent time slot (or symbol) in which the MT has performed data transmission / reception before the start of the (nk)th time slot will be aligned with the transmit / receive (Tx / Rx) beam of the RU in the Nth time slot. Here, the time offset of K may be defined on a time slot or symbol basis. Scenario 3 may also be applied to applications after a change instruction of the transmit / receive (Tx / Rx) beam of the RU in scenario 1 or scenario 2. That is, when a change of a transmit / receive (Tx / Rx) beam of an RU is explicitly / implicitly indicated through side control information, the gNB can expect that the indicated transmit / receive (Tx / Rx) beam of the RU will be applied within a specific time period.

[0255] Alternatively, the gNB may expect that the beam corresponding to the most recently indicated TCI state ID of the MT and the DL receive beam (and / or UL transmit beam) of the RU will be aligned. That is, the NCR may determine that the change of the DL receive beam of the RU is indicated to be changed to the beam corresponding to the most recently indicated TCI state ID to the MT. Here, the most recently indicated TCI state ID to the MT may refer to a TCI state ID configured to schedule PDCCH and / or PDSCH.

[0256] In addition, the most recent TCI state ID indicated to the NCR or MT may be defined as follows.

[0257] 1) First, the most recent TCI state ID may refer to a TCI state ID that has been successfully received by the NCR or MT. That is, the most recent TCI state ID may refer to the TCI state ID of the PDSCH that has been indicated from the gNB through the NCR or MT gNB. Alternatively, the most recent TCI state ID may refer to the TCI ID of the PDCCH that has been most recently monitored by the NCR or MT, or the TCI ID of the PDCCH detected by the NCR or MT.

[0258] That is, when the gNB instructs the NCR or MT to receive the PDCCH (or PDSCH) (i.e., schedules the PDCCH (or PDSCH)), the gNB may expect the RU's DL receive beam (and / or UL transmit beam) to be aligned with the MT's beam corresponding to the TCI state ID (or integrated TCI state ID) of the PDCCH (or PDSCH) scheduled to the MT. In this case, the MT may notify the gNB of the reception of information about the PDSCH (or PDCCH) scheduling through HARQ feedback.

[0259] Alternatively, since the gNB cannot clearly identify whether the MT has received the scheduling signal of the PDSCH (or PDCCH) including the TCI state ID, the gNB may perform an operation according to a predetermined protocol / commitment associated with the reception of the scheduling signal, which will be described later. For example, the NCR or MT may change the DL receive beam (and / or UL transmit beam) of the RU according to the TCI state ID of the most recently scheduled PDSCH (or PDCCH), or may change the DL receive beam (and / or UL transmit beam) of the RU according to the TCI state ID of the most recently monitored (or detected) PDCCH. In this case, the time point at which the DL receive beam (and / or UL transmit beam) of the RU is changed according to the TCI state ID may be the time point at which the NCR or MT sends the HARQ signal of the PDSCH or PDCCH scheduled by the scheduling signal to the gNB, or may be located after the sending point. Alternatively, in the absence of such a process with HARQ feedback, it may be determined that the NCR or MT will always receive the PDSCH (or PDCCH) including the TCI state ID. In this case, the NCR or MT can change the beam of the RU to the beam corresponding to the TCI state ID within a specific time after the reception (or detection, monitoring) of the PDSCH (or PDCCH), or can change the beam of the RU to the beam corresponding to the TCI state ID after a specific time has passed after the reception (or detection, monitoring) of the PDSCH (or PDCCH).

[0260] In addition, as described above, when time resources between the backhaul link and the control link overlap (ie, when transmission or reception in the control link and transmission or reception on the backhaul link are performed simultaneously), the method of scenario 3 may be applied.

[0261] Fig.10 This is a diagram illustrating a method in which the NCR configures a beam for a backhaul link required for forwarding.

[0262] Reference Fig.10, the NCR may report capability information related to the beam configuration of the backhaul link to the gNB (base station: BS) (S101). Here, the capability information may be capability information regarding whether an instruction for the beam of the backhaul link is possible. That is, the NCR may report capability information indicating that a beam for the backhaul link has been indicated to the gNB, or may report capability information indicating that an instruction for the beam of the backhaul link is not supported to the gNB. In addition, as described above, whether an instruction for the beam of the backhaul link is possible is related to whether different beams can be configured between the backhaul link and the control link (i.e., the link between the MT of the NCT and the gNB). For example, as described above, if different beams can be configured between the backhaul link and the control link, the NCR has the ability to receive explicit instructions for the beam of the backhaul link. In addition, the beam for the backhaul link may correspond to the DL receive beam / UL transmit beam of the RU as described above, and the beam for the control link may correspond to the DL receive beam / UL transmit beam of the MT as described above.

[0263] Next, the NCR may configure / determine the beam for the backhaul link based on the instruction information received from the gNB (base station) according to the report of the capability information, or may configure / determine the beam for the backhaul link based on a predefined rule (S103). For example, if the capability information includes information that an instruction for a beam for the backhaul link is possible, the NCR may receive the instruction information from the gNB (base station) through a control link, and may determine / configure the beam indicated by the instruction information among a plurality of beams related to the control link as the beam for the backhaul link. On the contrary, if the capability information includes information indicating that a beam for the backhaul link cannot be indicated, the NCR may determine the beam for the backhaul link based on a predefined rule without expecting to receive the instruction information. Here, the above instruction information may be sent to the NCR via a MAC CE (MAC control element), as described above.

[0264] Specifically, when capability information indicating that a beam instruction for a backhaul link is possible is reported, the NCR may expect to receive instruction information from the gNB (or BS). When the instruction information is received, the NCR may determine the beam for the backhaul link based on the instruction information. Here, the instruction information may include information indicating at least one beam among multiple beams related to the control link. For example, the instruction information may include information about a TCI state ID related to the control link, which TCI state ID indicates (via RRC signaling) at least one beam among multiple beams configured for the control link. In this case, the NCR can identify at least one beam among multiple beams for the control link as a beam for the backhaul link by the TCI state ID included in the instruction information. That is, the NCR may indicate at least one beam as a beam for the backhaul link. In other words, the NCR may configure / determine the beam for the backhaul link (or the DL receive beam for the backhaul link) as a beam corresponding to the TCI state ID among multiple beams for the control link based on the instruction information. Alternatively, the instruction information may include an SRI for the control link, and the NCR may be instructed by the SRI included in the instruction information to select a beam to be used for the backhaul link (eg, a UL transmission beam) from among multiple beams for the control link.

[0265] Alternatively, as described above, the instruction information may include information about an SSB index and a CSI-RS index (related to the control link), the CSI-RS index indicating one of the multiple beams configured for the control link. That is, the NCR may receive an explicit instruction indicating a beam for the backhaul link according to scenario 1. In addition, as described above, the NCR may receive an instruction indicating a DL receive beam and / or a UL transmit beam for the backhaul link based on the instruction information.

[0266] Alternatively, if capability information including information indicating that a beam instruction for the backhaul link is impossible is reported, or if capability information is not reported because a beam instruction for the backhaul link is impossible, the NCR may configure / determine a beam for the backhaul link according to a predefined rule. Here, the predefined rule is as described in Scenario 2 and / or Scenario 3 above. For example, the NCR may determine / configure a beam for the backhaul link according to a predefined rule based on a specific CORESET among multiple CORESETs associated with (or configured for) a control link, a specific search space among multiple search spaces associated with (or configured for) a control link, a joint TCI state for the control link, and a reception state of side control information for controlling the backhaul link. For example, the NCR may determine a beam for the backhaul link based on a CORESET with the lowest ID among the CORESETs configured for the control link according to a predefined rule. In this case, as described above, the NCR may determine a beam for the backhaul link by using a QCL estimate of the control link associated with the CORESET with the lowest ID. Alternatively, the NCR may determine the beam direction for the backhaul link based on the integrated TCI status indicated for the control link according to predefined rules.

[0267] Alternatively, even if the capability information is reported, if the instruction information is not received, or if the time resources for the backhaul link and the time resources for the control link do not overlap (i.e., if the MT does not perform transmission or reception at a specific time resource to be transmitted or received on the backhaul link as described above), the NCR may configure / determine the beam for the backhaul link according to predefined rules.

[0268] Alternatively, if the time resources for the backhaul link and the time resources for the control link overlap (i.e., if the MT performs transmission or reception at a specific time resource to be transmitted or received on the backhaul link as described above), the NCR can configure / determine the beam for the backhaul link to be the same beam as the beam to be applied to the control link.

[0269] Next, the NCR may receive a downlink (DL) signal from the gNB (or BS) via the backhaul link, or send an uplink (UL) signal to the gNB (BS) via the backhaul link using a beam for the backhaul link configured / determined based on predefined rules or instruction information (S105).

[0270] In this way, the NCR can report capability information indicating whether the beam instruction for the backhaul link required for forwarding is possible, so that the NCR can clearly determine whether to determine the beam for the backhaul link by receiving instruction information of the beam for the backhaul link from the gNB, or can clearly determine whether to determine the beam for the backhaul link by a predefined rule without using the instruction information. In addition, even if the beam instruction for the backhaul link is not expected by the instruction information of the gNB (base station) according to the report of the capability information, or even if the instruction information is not received, the beam configuration / determination of the backhaul link that can be clearly predicted between the gNB and the NCR by the predefined rule is possible.

[0271] Communication system example to which the present disclosure is applied

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

[0273] Hereinafter, it will be illustrated in more detail with reference to the accompanying drawings.In the following drawings / descriptions, unless otherwise specified, the same reference numerals may illustrate the same or corresponding hardware blocks, software blocks or functional blocks.

[0274] Fig.11 A communication system applied to the present disclosure is illustrated.

[0275] Reference Fig.11, the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, the wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or long term evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital sign, a vehicle, a robot, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0276] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0277] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation and resource mapping / demapping) and resource allocation processes can be performed based on various proposals of the present disclosure.

[0278] Examples of wireless devices to which the present disclosure is applied

[0279] Fig.12 A wireless device suitable for use with the present disclosure is illustrated.

[0280] Reference Fig.12 , the first wireless device 100 and the second wireless device 200 may transmit radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.11 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0281] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals 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 store software codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0282] According to one example, the first wireless device 100 or NCR may include a processor 102 and a memory 104 connected to an RF transceiver. The memory 104 may include a processor capable of executing the reference Fig. 9 and Fig.10 At least one procedure of operations related to the described embodiments.

[0283] Specifically, the processor 102 may control the RF transceiver 106 to report capability information related to beam configuration of the backhaul link to the gNB (or BS) through the control link, and may configure the beam for the backhaul link according to instruction information or predefined rules received from the gNB based on the report of the capability information. Here, the instruction information may include a transmission configuration indicator (TCI) state or a scheduling request indicator (SRI) related to the control link required to configure the beam for the backhaul link.

[0284] Alternatively, the processor 102 and the memory 104 may be included in a chipset. In this case, the chipset may include at least one processor and at least one memory, the at least one memory being operatively connected to the at least one processor and configured to cause the one or more processors to perform operations when executed. Here, the operations may include: reporting capability information related to the beam configuration of the backhaul link to the base station via a control link; and configuring the beam for the backhaul link according to instruction information or predefined rules received from the base station based on the reporting of the capability information, wherein the instruction information may include a TCI state or SRI related to the control link for configuring the beam for the backhaul link. In addition, the at least one processor may execute based on a program included in the memory. Fig. 9 and Fig.10 The operation of the embodiments described in .

[0285] Alternatively, a computer-readable storage medium may be provided, which includes at least one computer program for causing the at least one processor to perform operations. Here, the operations may include: reporting capability information related to the beam configuration of the backhaul link to the base station via a control link; and configuring the beam for the backhaul link according to instruction information or predefined rules received from the base station based on the report of the capability information, wherein the instruction information may include a TCI state or SRI related to the control link for configuring the beam for the backhaul link. In addition, the at least one processor may execute based on the program included in the memory. Fig. 9 and Fig.10 In addition, the computer program may include a computer program capable of executing the operation of the embodiment described in the embodiment. Fig. 9 and Fig.10 The procedures for the operation of the embodiments are described.

[0286] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained by processing 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 store software codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0287] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0288] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.

[0289] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.

[0290] One or more transceivers 106 and 206 may send the user data, control information and / or radio signal / channel mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive the user data, control information and / or radio signal / channel mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or wireless signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 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 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0291] Application examples of wireless devices to which the present disclosure is applied

[0292] Fig.13 Another example of a wireless device to which the present disclosure is applied is shown.

[0293] Reference Fig.13 , the wireless devices 100 and 200 may correspond to Fig.12The wireless devices 100 and 200 may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.12 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.12 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 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. The control unit 120 may send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0294] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the form of, but not limited to, a robot ( Fig.11 100a), vehicles ( Fig.11 100b-1 and 100b-2), XR devices ( Fig.11 100c), handheld device ( Fig.11 100d), household appliances ( Fig.11 100e), IoT devices ( Fig.11 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.11 400), BS( Fig.11 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.

[0295] exist Fig.13In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. In another example, the memory 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM)), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0296] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include LTE, NR and 6G in addition to narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of low-power wide area network (LPWAN) technology, and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. In addition or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, as an example, LTE-M technology may be an example of LPWAN technology, and may be referred to as various names such as eMTC (enhanced machine type communication). For example, LTE-M technology may be implemented according to 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 names. Additionally or alternatively, in consideration of low power communication, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification is at least one of ZigBee, Bluetooth, and a low power wide area network (LPWAN), and is not limited to the above names. As an example, ZigBee technology can generate a personal area network (PAN) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to as various names.

[0297] The above-mentioned embodiments are embodiments in which the components and features of the present disclosure are combined in a predetermined form. Unless otherwise clearly stated, each component or feature should be considered as optional. Each component or feature can be implemented in a form that is not combined with other components or features. In addition, the embodiments of the present disclosure can also be constituted by combining some components and / or features. The order of the operations described in the embodiments of the present disclosure can be changed. Some configurations or features of an embodiment can be included in other embodiments, or can be replaced with corresponding configurations or features of other embodiments. Obviously, the embodiments can be constructed by combining claims that do not have a clear reference relationship in the claims, or can be included as new claims by modifying after submission.

[0298] In this document, the embodiments of the present disclosure are described mainly based on the signal transmission / reception relationship between the terminal and the base station. Such a transmission / reception relationship is extended to the signal transmission / reception between the terminal and the repeater or between the base station and the repeater in the same / similar manner. In some cases, the specific operations described in this document as being performed by the base station can be performed by the node on it. That is, it is obvious that various operations performed in order to communicate with the terminal in a network including multiple network nodes containing the base station can be performed by the base station or by a network node other than the base station. The base station can be replaced by terms such as fixed station, node B, eNode B (eNB), access point, etc. In addition, the terminal can be replaced by terms such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS).

[0299] In hardware configuration, the embodiments of the present disclosure 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.

[0300] In firmware or software configuration, the method according to the embodiment of the present disclosure can be implemented in the form of modules, processes, functions, etc. The software code can be stored in a storage unit and executed by a processor. The memory is located inside or outside the processor and can send data to the processor and receive data from the processor via various known means.

[0301] As mentioned above, a detailed description of the preferred embodiments of the present disclosure has been given so that those skilled in the art can implement and perform the present disclosure. Although the preferred embodiments of the present disclosure have been referred to above, those skilled in the art will understand that various modifications and changes can be made to the present disclosure within the scope of the present disclosure.

[0302] Industrial Applicability

[0303] The above-mentioned embodiments of the present disclosure are applicable to various mobile communication systems.

Claims

1. A method for setting a beam of a backhaul link for forwarding by a network-controlled repeater NCR in a wireless communication system, the method comprising the following steps: reporting capability information related to beam setting of the backhaul link to a base station via a control link; as well as Based on the report of the capability information, configuring a beam for the backhaul link based on indication information or a predefined rule received from the base station, The indication information includes a transmission configuration indicator TCI state identifier ID or a scheduling request indicator SRI related to the control link for configuring the beam for the return link.

2. The method according to claim 1, wherein: The capability information includes information related to whether the beam for the backhaul link can be indicated.

3. The method according to claim 1, wherein: The capability information includes information on whether the beam different from the beam for the control link can be used for the backhaul link.

4. The method according to claim 1, wherein: By the report of the capability information, based on the received indication information, a downlink reception beam for the backhaul link is configured as the beam corresponding to the TCI state ID included in the indication information among a plurality of beams for the control link, and The uplink transmission beam for the backhaul link is configured as the beam corresponding to the SRI included in the indication information among the multiple beams for the control link.

5. The method according to claim 1, wherein: Based on the fact that the time resources for the backhaul link do not overlap with the time resources for the control link and the indication information is not received, the beam for the backhaul link is configured based on the predefined rule.

6. The method according to claim 5, wherein: According to the predefined rule, a downlink reception beam for the backhaul link is determined based on a CORESET of a specific index among a control resource set CORESET related to the control link.

7. The method according to claim 6, wherein: The specific index is the lowest index among the indexes for the CORESET.

8. The method according to claim 5, wherein: Based on the predefined rule, a downlink reception beam for the backhaul link is determined as the beam for the control link used to receive a downlink signal in a specific search space among a plurality of search spaces related to the control link.

9. The method according to claim 1, wherein: Based on a predefined rule, the beam for the backhaul link is determined to be the same beam as the beam for the control link.

10. A network controlled repeater NCR configured for forwarding a beam for a backhaul link in a wireless communication system, the NCR comprising: Radio frequency RF transceiver; as well as a processor connected to the RF transceiver, The processor controls the RF transceiver to report capability information related to the beam configuration of the backhaul link to the base station side control information through a control link, and configures the beam for the backhaul link based on the indication information or predefined rules received from the base station based on the report of the capability information, and the side control information The indication information includes a transmission configuration indicator TCI state or a scheduling request indicator SRI related to the control link for configuring a beam for the return link.

11. The NCR according to claim 10, wherein: The capability information includes information related to whether the beam for the backhaul link can be configured based on the indication information.

12. The NCR according to claim 10, wherein: Through the reporting of the capability information, based on the received indication information, the downlink receive beam for the return link is configured to be the beam corresponding to the TCI state ID included in the indication information among the multiple beams for the control link.

13. The NCR according to claim 10, wherein: Based on the time resources for the backhaul link not overlapping with the time resources for the control link and the indication information not being received, the beam for the backhaul link is configured based on the predefined rule.

14. A chipset for configuring a beam for a backhaul link for forwarding in a wireless communication system, the chipset comprising: at least one processor; as well as at least one memory, the at least one memory being operatively connected to the at least one processor and, when executed, causing the at least one processor to perform operations, The operations include: Reporting capability information related to configuration of the beam of the backhaul link to a base station through a control link; and Based on the report of the capability information, the beam for the backhaul link is configured based on indication information or a predefined rule received from the base station, The indication information includes a transmission configuration indicator TCI state or a scheduling request indicator SRI related to the control link for configuring a beam for the return link.

15. A computer-readable storage medium comprising at least one computer program in a wireless communication system, in, The at least one computer program is configured to cause at least one processor in the wireless communication system to perform an operation of configuring a beam for forwarding for a backhaul link, wherein the at least one computer program is stored on the computer-readable storage medium, and The operations include: Reporting capability information related to configuration of the beam of the backhaul link to a base station through a control link; and Based on the report of the capability information, the beam for the backhaul link is configured based on indication information or predefined rules received from the base station, The indication information includes a transmission configuration indicator TCI state or a scheduling request indicator SRI related to the control link for configuring a beam for the return link.