Signal transmission / reception method for wireless communication and apparatus therefor

Abstract

A terminal in a wireless communication system according to various embodiments: receives information on a first operation period for downlink reception through a backhaul link; setting a first beam of the backhaul link for the first operation period; and receiving a downlink signal to be forwarded to the terminal from the base station using a first beam of the backhaul link, and overlapping with the first operation period on at least one time resource based on a second operation period for receiving the downlink signal through the control link, a first beam of the backhaul link is set to be the same as a second beam of the control link for at least one time resource, and the second operation period may include a first time resource allocated through downlink control information and a second time resource set for monitoring a downlink signal.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to a method of transmitting or receiving an uplink / downlink signal in a wireless communication system and an apparatus thereof. 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 of transmitting and receiving signals more accurately and efficiently.

[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] In one aspect of the present disclosure, a method for performing communication in a wireless communication system by a device having a control link and a backhaul link formed with a base station (BS) is provided herein. The method includes: receiving information about a first operation duration for a backhaul link; configuring a first beam of the backhaul link for the first operation duration; and receiving a downlink signal to be forwarded to a user equipment (UE) from the BS based on the first beam of the backhaul link. Based on the second operation duration for receiving a downlink signal through a control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link can be set to the same beam as the second beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated by downlink control information and a second time resource configured to monitor a downlink signal.

[0009] Alternatively, the second time resource may include a time resource configured to monitor at least one of the following items related to the control link: a synchronization signal block (SSB), a system information block 1 (SIB1), a channel state information reference signal (CSI-RS), and a physical downlink control channel (PDCCH).

[0010] Alternatively, the method may further include receiving indication information indicating a beam used for the backhaul link.

[0011] Alternatively, even based on the reception of the indication information, the first beam of the backhaul link may be set to be the same beam as the second beam for the at least one time resource.

[0012] Alternatively, the first beam of the backhaul link may be set to the beam indicated by the indication information for the remaining time resources except the at least one time resource among the time resources included in the first operation duration.

[0013] Alternatively, the first beam of the backhaul link may be set to the beam indicated by the indication information only for the time resources earlier than the at least one time resource among the remaining time resources.

[0014] Alternatively, based on not receiving indication information indicating a beam for the return link, the first beam of the return link can be set to a beam determined based on a predefined rule for the remaining time resources other than the at least one time resource included in the first operation duration.

[0015] Alternatively, based on a predefined rule, the first beam of the backhaul link may be set to a beam corresponding to a control resource set (CORESET) having the lowest index among the CORESETs related to the control link.

[0016] Alternatively, the method may further include forwarding the downlink signal to the UE through an access link formed with the UE.

[0017] In another aspect of the present disclosure, a device is provided herein that is configured to perform communication based on a control link and a backhaul link formed with a BS in a wireless communication system. The device may include: a radio frequency (RF) transceiver; and a processor configured to control the RF transceiver. The processor is configured to: control the RF transceiver to receive information about a first operation duration for downlink reception through a backhaul link; configure a first beam of the backhaul link for the first operation duration; and receive a downlink signal to be forwarded to a UE from the BS based on the first beam of the backhaul link. Based on the second operation duration for receiving a downlink signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link may be set to the same beam as the second beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated by downlink control information and a second time resource configured to monitor a downlink signal.

[0018] In another aspect of the present disclosure, a processing device is provided herein that is configured to control a device having a control link and a backhaul link formed with a BS in a wireless communication system. The processing device includes: at least one processor; and at least one memory connected to the at least one processor and storing instructions, which instructions, based on being executed by the at least one processor, cause the UE to: receive information about a first operation duration for downlink reception through a backhaul link; configure a first beam of the backhaul link for the first operation duration; and receive a downlink signal to be forwarded to the UE from the BS based on the first beam of the backhaul link. Based on the second operation duration for receiving a downlink signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link can be set to the same beam as the second beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated by downlink control information and a second time resource configured to monitor a downlink signal.

[0019] In another aspect of the present disclosure, a method for performing communication in a wireless communication system by a BS having a control link and a backhaul link formed with a device is provided herein. The method includes: sending information about a first operation duration for downlink reception through a backhaul link; determining a third beam for sending a downlink signal through the backhaul link; and sending a downlink signal to be forwarded to a UE to the device based on the third beam of the backhaul link during the first operation duration. Based on the second operation duration for receiving a downlink signal through the control link overlapping with the first operation duration on at least one time resource, the third beam of the backhaul link is determined to be the same beam as the transmission beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

[0020] Beneficial Effects

[0021] According to one embodiment of the present disclosure, signal transmission and reception can be performed more accurately and efficiently in a wireless communication system.

[0022] 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

[0023] 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.

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

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

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

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

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

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

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

[0031] 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.

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

[0033] Fig.10 is a diagram for explaining a method of configuring a backhaul link beam based on whether backhaul link beam indication and simultaneous operation are performed.

[0034] Fig.11 is a diagram for explaining a method of configuring a backhaul link beam by a device having a control link and a backhaul link formed with a BS.

[0035] Fig.12 is a diagram for explaining a method of configuring a backhaul link beam by a BS having a control link and a backhaul link with a device.

[0036] Fig.13 A communication system applied to the present disclosure is illustrated.

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

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

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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 above.

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

[0046] Figure 1 The 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

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

[0052] 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 7 In 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.

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

[0054] 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).

[0055] 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).

[0056] 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 .

[0057] [Table 1]

[0058] <![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

[0059] 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.

[0060] [Table 2]

[0061] <![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

[0062] 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.

[0063] 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.

[0064] 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).

[0065] [Table 3]

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

[0067] 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 may be used for various purposes, for example, for vehicle communications (e.g., autonomous driving).

[0068] [Table 4]

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

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

[0071] 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.

[0072] 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.

[0073] 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.

[0074] Bandwidth Part (BWP)

[0075] 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).

[0076] 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.

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

[0078] 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.

[0079] 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.

[0080] 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).

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

[0082] 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. A 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 a 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.

[0083] In addition, configuration information about CORESET#N (e.g., N>0) may be sent via 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 setup message, RRC reconfiguration message, and / or BWP configuration information. Specifically, the CORESET configuration may include the following information / fields.

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

[0085] -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.

[0086] -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.

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

[0088] -interleaverSize: Indicates the interleaver size.

[0089] -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.

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

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

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

[0093] -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).

[0094] 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.

[0095] 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".

[0096] 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.

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

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

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

[0100] -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.

[0101] -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}.

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

[0103] 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.

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

[0105] [Table 5]

[0106]

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

[0108] [Table 6]

[0109]

[0110] 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).

[0111] 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.

[0112] 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.

[0113] - 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.

[0114] - 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.

[0115] RRC signaling for cell-specific signals or channels

[0116] Hereinafter, parameters of RRC signaling used for a cell-specific signal or channel will be described in detail (refer to 3GPP TS38.331).

[0117] First, TDD-UL-DL-ConfigCommon may be configuration information for determining / configuring a cell-specific UL / DL TDD configuration. TDD-UL-DL-ConfigCommon may include the parameters defined in Table 7.

[0118] [Table 7]

[0119]

[0120]

[0121] Next, BWP-DownlinkCommon is the configuration information for configuring the common parameters of DL BWP. In other words, BWP-DownlinkCommon may include "cell-specific" parameters. The common parameters of the initial BWP of PCell may also be provided through system information. For all other serving cells, the network may provide common parameters through dedicated signaling. Specifically, BWP-DownlinkCommon may include the parameters defined in Table 8.

[0122] [Table 8]

[0123]

[0124] Among the above parameters, PDCCH-ConfigCommon may be used to configure cell-specific PDCCH parameters provided not only in SIB but also through dedicated signaling. Referring to Table 9, PDCCH-ConfigCommon may include parameters for configuring a cell-specific PDCCH.

[0125] [Table 9]

[0126]

[0127]

[0128] In Table 10, PDSCH-ConfigCommon is configuration information for configuring a cell-specific PDSCH.

[0129] [Table 10]

[0130]

[0131] According to Table 11, the IE ServingCellConfigCommon may be used to configure cell-specific parameters of the serving cell of the UE. ServingCellConfigCommon may include parameters that the UE typically obtains from the SSB, MIB, or SIB when accessing a cell from an idle state.

[0132] [Table 11]

[0133]

[0134]

[0135]

[0136] According to Table 12, ServingCellConfigCommonSIB may be used to configure cell-specific parameters of the serving cell of the UE in SIB1.

[0137] [Table 12]

[0138]

[0139]

[0140] According to Table 13, BWP-UplinkCommon can be used to configure common parameters of uplink BWP. BWP-UplinkCommon can also configure parameters for cell-specific signals.

[0141] [Table 13]

[0142]

[0143]

[0144] According to Table 14, initialDownlinkBWP can be used to configure the initial downlink BWP.

[0145] [Table 14]

[0146]

[0147] Additionally, according to Table 15, PUCCH-ConfigCommon may also be used to configure cell-specific PUCCH parameters.

[0148] [Table 15]

[0149]

[0150]

[0151] According to Table 16, PUSCH-ConfigCommon can be used to configure cell-specific PUSCH parameters.

[0152] [Table 16]

[0153]

[0154] RACH-ConfigCommon defined in Table 17 may be used to specify or configure cell-specific random access parameters.

[0155] [Table 17]

[0156]

[0157]

[0158] In this way, RRC configuration information such as TDD-UL-DL-ConfigCommon, BWP-DownlinkCommon, PDCCH-ConfigCommon, PDSCH-ConfigCommon, ServingCellConfigCommonSIB, BWP-UplinkCommon, initialDownlinkBWP, PUCCH-ConfigCommon, PUSCH-ConfigCommon and RACH-ConfigCommon can provide configuration information about the transmission parameters and transmission resources of cell-specific signals or channels.

[0159] IAB (Integrated Access / Backhaul)

[0160] The network may form such an integrated access and backhaul link, where an IAB node or a relay node (rTRP) may multiplex the access and backhaul links in time, frequency, or space (eg, beam-based operation).

[0161] 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.

[0162] 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.

[0163] 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.

[0164] 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.

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

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

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

[0168] -Multi-hop and redundant connections

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

[0170] -Backhaul link support with high spectral efficiency

[0171] - Legacy NR UE support

[0172] 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.

[0173] 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.

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

[0175] 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.

[0176] 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.

[0177] 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.

[0178] 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.

[0179] 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.

[0180] 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.

[0181] There may be N MT-CCs and M DU-cells in an IAB node. Fig. 9An 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.

[0182] 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.

[0183] -DU-Tx / MT-Tx

[0184] -DU-Rx / MT-Rx

[0185] -DU-Tx / MT-Rx

[0186] -DU-Rx / MT-Tx

[0187] 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.

[0188] 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.

[0189] Network Controlled Repeater (NCR) in NR

[0190] 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 regarding semi-static and / or dynamic downlink / uplink configurations, adaptive transmitter / receiver spatial beamforming, ON-OFF states, etc.

[0191] A network controlled repeater is an enhancement to 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 directivity, and simplified network integration.

[0192] 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.

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

[0194] 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.

[0195] 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, 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.

[0196] 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.

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

[0198] 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.

[0199] 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.

[0200] 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 operations, 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.

[0201] 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.

[0202] 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).

[0203] Side control information for NCR

[0204] 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.

[0205] 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.

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

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

[0208] 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.

[0209] -Timing information for aligning the transmit / receive boundaries of the Network Controlled Repeater (NCR): Information for RUs to align transmit / receive (Tx / Rx) slot symbol boundaries

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

[0211] - On-off information for efficient interference management and improved energy efficiency: Information about the on-off operation of the RU

[0212] -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.

[0213] NCR can consist of two parts: NCR mobile terminal (NCR-MT), which receives side control information from gNB and sends reports to gNB; and NCR forwarding (NCR-Fwd), which receives transmission signals from gNB and forwards the signals to UE, or receives transmission signals from UE and forwards the signals to gNB.

[0214] In this regard, the following scenario can be considered.

[0215] -NCR mobile terminal (NCR-MT) can be defined as a functional entity that implements the exchange of control information (e.g., side control information) by communicating with the gNB via a control link (C link). The C link is based on the NR Uu interface. For reference, the side control information is used to control at least NCR-forwarding.

[0216] -NCR-Forward (NCR-Fwd) is defined as a functional entity that amplifies and forwards UL / DL RF signals between gNB and UE through backhaul link and access link. The operation of NCR-Fwd can be controlled based on the side control information received from the gNB.

[0217] In NR, since cost-effectiveness is important for NCR, it is assumed that NCR uses AF (amplify and forward) relays instead of DF (decode and forward) relays. Therefore, the signal received by NCR-Fwd from the UE and sent to the gNB is only amplified and forwarded without decoding. As a result, there may be limitations in sending the transmission signal from NCR-MT together on these transmission resources. For example, in order to multiplex the signal received from the UE and the transmission signal from NCR-MT, NCR-Fwd needs to know in advance the time domain / frequency domain or resources where the received signal from the UE exists. Additionally, the synchronization between the received signal and the transmitted signal should be fully aligned. However, such identification of the received signal time / frequency resources and synchronization alignment may not be allowed in the AF relay. Due to regulatory restrictions on the NCR transmission signal power, the uplink transmission of NCR-Fwd and the uplink transmission of NCR-MT may be difficult to occur on the same time resource. In this context, it can be assumed that the uplink transmission of NCR-MT and NCR-Fwd is based on TDM operation.

[0218] The beam adaptation between the gNB and the RU will be described below. Even for a fixed NCR without mobility, if scattering changes are considered, or if an NCR with mobility is considered later, beam adaptation indications between the gNB and the RU may be required. However, if the RU only exists in the radio frequency (RF) layer, the RU may not be able to directly receive information about transmit and receive beam control. Alternatively, even if there are other layers in the RU in addition to the RF layer, the RU may need to further receive beam information from the MT because the RU needs to perform relaying. Additionally, it is not ruled out that an NCR with mobility rather than a fixed NCR considered after Rel-19 will be discussed. In this context, a method for the MT to receive beam information between the gNB and the RU will be described.

[0219] Since the RU cannot directly send or receive data with the gNB (i.e., the RU cannot directly receive information for the RU from the gNB), one of the most basic methods to determine the RU beam is to use the Tx / Rx beam used by the MT as the Tx / Rx beam of the RU. However, since the Tx / Rx beam used by the MT is not fixed as a single beam, it is necessary to define which of the multiple Tx / Rx beams used by the MT will be used as the beam of the RU. The following describes in detail a method for determining / configuring the Tx / Rx beam of the RU based on at least one of the multiple Tx / Rx beams used by the MT.

[0220] The gNB may indicate the beam direction of the RU based on the capabilities of the NCR by at least one of the methods described in the following scenarios and alternatives. Here, the capabilities of the NCR may be related to whether the control link of the MT (C-link of the MT) and the backhaul link of the NCR (RU) can operate based on different beams. For example, if the NCR reports to the gNB that the NCR has the ability to operate with different beams for the C-link and the backhaul link, the NCR may explicitly receive the beam for the backhaul link from the gNB. In this case, the NCR may receive the beam direction of the backhaul link based on scenario 1 described later. In other words, an NCR node that supports the use of beams with different directions between the backhaul link and the C-link may explicitly receive a beam for the backhaul link (or a beam for the backhaul link).

[0221] 1. Scenario 1

[0222] The NCR (or MT) can be configured / indicated with information about the Tx / Rx beams of the RU based on the information about the Tx / Rx beams of the MT. In other words, the NCR (or MT) can directly receive the Tx / Rx beams (or the Tx / Rx beams of the RU) of the backhaul link (gNB to RU link or forwarding link) from the gNB. On the other hand, according to the beam direction that the gNB instructs the MT to use, the NCR can make the Tx / Rx beams of the RU different from the Tx / Rx beams of the MT.

[0223] (1) Method for indicating DL Rx beam of RU

[0224] In particular, the NCR (or MT) may receive the DL Rx beam of the backhaul link among the Tx / Rx beams of the RU from the gNB by a method described later. In order to notify the DL Rx beam of the RU, the gNB may provide the beam information as described below to the MT. Here, the gNB may indicate the Rx beam of the RU corresponding to the Rx beam of the MT. In other words, in order to indicate the DL Rx beam of the RU, the gNB may notify the MT of the SSB index, CSI-RS index, TCI state ID, etc. through RRC / MAC-CE / DCI. The TCI state ID may be defined by pdsch-Config, which is a UE-specific PDSCH configuration indicated for a single BWP (BWP-DownlinkDedicated) (see 3GPP TS 38.331). In other words, the CSI-RS and TCI state ID may be BWP-specific values ​​and UE-specific values ​​for the MT. Since a standard is required to determine a single BWP for the determination of the DL Rx beam of the RU, a single BWP related to the determination of the DL Rx beam of the RU may be defined by a previous agreement. For example, the single BWP may be the default BWP or the initial BWP of the MT. Alternatively, the gNB may indicate / configure a single BWP associated with the TCI state ID for indicating the DL Rx beam of the RU from among the BWPs of the MT through RRC / MAC-CE / DCI. Information about the number of time slots may also be included in the indication for the DL Rx beam. For example, if the number of time slots indicated is k, the gNB may expect that, based on the MT (time slot boundary), the DL Rx beam of the RU will switch to the indicated beam direction after k time slots from the time slot indicating the DL Rx beam of the RU (after the DL RS indicating the beam change). Alternatively, in the absence of a separate digital information indication, the beam direction of the DL Rx beam of the RU may be changed to the indicated beam direction after a specific time slot / symbol configured by a previous agreement or commitment.

[0225] Alternatively, for the number of time slots or time slot offset, a specific operation can be agreed as the default behavior. For example, when the number of time slots is indicated (together with the beam direction of the RU), the indicated beam direction of the RU (the DL Rx beam of the RU) can be applied as the beam direction of the RU during the duration corresponding to the indicated number of time slots from the pre-agreed time. For example, when the DL beam direction of the RU is indicated together with k time slots / subframes / symbols, the DL beam direction of the RU can be set to the beam direction indicated by the gNB during the duration corresponding to k time slots / subframes / symbols from the pre-agreed time. After the duration has passed, the DL beam of the RU can be switched to the DL beam direction before the beam direction indication, or the beam direction can be changed to a pre-agreed default beam.

[0226] Alternatively, if there is no explicit indication of the DL Rx beam of the RU or the beam direction of the backhaul link, a default beam based on a previous agreement or commitment may be applied as the DL Rx beam of the RU (see scenario 2). The default beam may be applied after the expiration of the effective time of the explicit indication, before any explicit beam direction indication is given, or for a time resource or time duration for which there is no valid backhaul link beam on a specific time resource. Alternatively, the method of turning off the RU or NCR-Fwd (i.e., when the forwarding operation of the NCR or RU is not performed) may also be regarded as a method of configuring a default beam. Alternatively, the method of turning off the RU or NCR-Fwd (i.e., when the forwarding operation of the NCR or RU is not performed) may also be regarded as a method of setting a default beam. For example, if there is no explicit indication of the beam direction for the backhaul link, or if no beam is configured or does not exist for the valid backhaul link on a specific time resource, or if there is no valid backhaul link beam on a specific time resource, a default beam based on a previous agreement or commitment may be applied.

[0227] (2) Method for indicating UL Tx beam of RU

[0228] Next, the MT or NCR may receive the UL Tx beam of the backhaul link among the RU beams from the gNB. In other words, the gNB may provide the UL Tx beam of the RU to the MT according to the following method. The Tx beam of the MT corresponding to the indication of the gNB may be applied as the UL Tx beam of the RU. For example, the gNB may provide the UL Tx beam of the RU to the MT through an SRS resource indicator (SRI). Similar to the DL Rx beam of the RU described above, the UL Tx beam of the MT is a BWP-specific configuration, so at least one BWP related to the indication of the UL Tx beam of the RU may be predefined or indicated by a previous agreement or commitment. For example, the pre-agreed BWP may be the default BWP or the initial BWP of the MT. Alternatively, the gNB may specify / indicate at least one of the BWPs of the MT as a BWP related to the SRI (or TCI state ID) used to indicate the UL Tx beam of the RU through RRC / MAC-CE / DCI. Information about the number of time slots may also be included in the indication for the DL Rx beam. For example, if the number of time slots is indicated as k, the gNB can expect that: based on the MT's (time slot boundary), the RU's UL Tx beam will switch to the indicated beam direction after k time slots from the time slot indicating the RU's DL Rx beam (after indicating the DL RS for beam change). Alternatively, without a separate quantity information indication, the beam direction of the RU's UL Tx beam may be changed to the indicated beam direction after a specific time slot / symbol configured by a previous agreement or commitment.

[0229] Alternatively, for the number of time slots or time slot offset, a specific operation may be agreed upon as the default behavior. For example, when the number of time slots is indicated together with (the beam direction of the RU), the indicated beam direction of the RU (the UL Tx beam of the RU) may be applied as the beam direction of the RU during a duration corresponding to the indicated number of time slots from a pre-agreed time. For example, when the direction of the UL Tx beam of the RU is indicated together with k time slots / subframes / symbols, the direction of the UL Tx beam of the RU may be set to the beam direction indicated by the gNB during a duration corresponding to k time slots / subframes / symbols from a pre-agreed time. After the duration has elapsed, the UL Tx beam of the RU may be switched to the direction of the UL Tx beam of the RU before the beam direction indication, or the beam direction may be changed to a pre-agreed default beam.

[0230] Alternatively, if there is no explicit indication of the UL Tx beam of the RU or the beam direction of the backhaul link, a default beam based on a previous agreement or commitment may be applied as the UL Tx beam of the RU (see scenario 2). The default beam may be applied after the expiration of the effective time of the explicit indication, before any explicit beam direction indication is given, or for a time resource or duration in which there is no valid backhaul link beam on a specific time resource. Alternatively, the method of turning off the RU or NCR-Fwd (i.e., when the forwarding operation of the NCR or RU is not performed) may also be regarded as a method of configuring a default beam. Alternatively, the method of turning off the RU or NCR-Fwd (i.e., when the forwarding operation of the NCR or RU is not performed) may also be regarded as a method of setting a default beam. For example, if there is no explicit indication of the beam direction for the backhaul link, or if no beam is configured or does not exist for the valid backhaul link on a specific time resource, or if there is no valid backhaul link beam on a specific time resource, a default beam based on a previous agreement or commitment may be applied.

[0231] (3) Indication of RU beams that do not distinguish between RU's DL Rx beam and UL Tx beam

[0232] Alternatively, the gNB may use the above method to explicitly indicate the RU beams (RU DL Rx beams and RU UL Tx beams) of the backhaul link without distinguishing between the DL Rx beams of the RU and the UL Tx beams of the RU. In other words, the gNB can notify the changes of the DL Rx beams and UL Tx beams of the RU of the backhaul link through a single indication. For example, the gNB can notify the changes of both the DL Rx beams and UL Tx beams of the RU by providing specific information about the RU beam changes to the MT. The single indication (or the indication of specific information) can be indicated based on the DL Rx beams of the MT or the UL Tx beams of the MT. For convenience of description, the DL Rx beams and UL Tx beams of the RU will be defined and described as the beams of the RU or the beams of the backhaul link.

[0233] For example, the gNB may notify the MT of the change of the RU beam used for the backhaul link using the SSB index, CSI-RS index, TCI state ID, etc. through RRC / MAC-CE / DCI. Alternatively, the gNB may use SRI to notify the MT of the change of the RU beam used for the backhaul link. The RU may not have an independent beam report, so the beam of the RU may be aligned based on the beam of the MT. Therefore, the QCL relationship (association) between the Tx / Rx beams of the MT may also be applied to the (Rx / Tx) beam of the RU. For example, in connection with the above method, when the gNB notifies the MT of the SSB index and / or CSI-RS index to change the beam of the RU, the DL Rx beam of the RU may be aligned with the DL Rx beam of the MT corresponding to the indicated SSB index and / or CSI reception index, and the UL Tx beam of the RU may be aligned with the UL Tx beam of the MT corresponding to the indicated SSB index and / or CSI reception 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 of the MT.

[0234] Alternatively, time offset information (or information about the number of time slots) may be sent together with the indication of the RU beam. Here, the time offset information may include information about the time offset in units of time slots, subframes, or symbols. For example, if time offset information about k time slots is indicated together with the indication of the RU beam, the gNB may expect that, based on the MT, the change or switching of the RU beam will be performed from k time slots after the beam change is indicated (or the beam change indication is received). Alternatively, even if the time slot offset information about the number of time slots is not separately indicated, the change to the indicated RU beam may be applied after a specific time based on a previous agreement or commitment. For the time offset, a specific operation may be agreed upon as the default behavior. For example, if the time slot offset (or the number of time slots) is indicated together, the indicated RU beam may be applied during a duration corresponding to the indicated time slot offset from the pre-agreed time. Alternatively, when the change of the RU beam and the time offset (k time slots / subframes / symbols) are indicated together, the RU beam can be set to the indicated beam direction during the duration corresponding to the time offset from the pre-agreed time. In addition, after the duration has passed, the RU beam can be changed to the previous RU beam used before the beam indication or the pre-agreed default beam.

[0235] Alternatively, if there is no explicit indication of the RU's beam (or the beam of the backhaul link), the RU's beam may be applied or determined as a default beam based on a previous agreement or commitment. The default beam may be configured or defined by the indication method described in Scenario 2, which will be discussed later. Here, the default beam may be applied after the validity period of the explicit beam direction indication expires. Alternatively, if there is no explicit beam direction indication, if there is no valid RU beam on a specific time resource, or if the backhaul link (NCR-Fwd) is closed, the default beam may be applied. In other words, if there is no explicit beam direction indication, or there is no valid RU beam (or the beam of the backhaul link) on a specific time resource, a pre-agreed default beam may be applied as the RU's beam. The default beam may be determined / configured by the method described in Scenario 2, which will be discussed later. 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).

[0236] "Indicating a change of a DL Rx beam and / or a UL Tx beam without performing separate indications for the DL Rx beam and the UL Tx beam" can be performed based on a unified TCI framework. Here, the unified TCI framework (introduced in Rel-17 MIMO) is different from the existing TCI framework, in which the TCI state is indicated independently for each DL / UL channel / RS. For example, the existing TCI framework has advantages in flexibility but disadvantages in signaling overhead and latency. In other words, for most UEs that apply one beam at a time, the gNB needs to perform beam change indication separately for each DL / UL channel / RS in order to change the beam of the UE. In contrast, the unified TCI framework (in Rel-17 MIMO) defines a joint TCI state, and based on the indicated TCI state, integrated beam control can be supported for DL / UL data channels (PDSCH / PUSCH), DL / UL control channels (PDCCH / PUCCH), antenna port (AP) CSI-RS, and sounding reference signal (SRS). For example, in the unified TCI framework, the DL DCI format (1_1 / 1_2) can be used for DCI-based methods, and PDSCH assignment information (i.e., data assignment) can be included or omitted. In other words, in the unified TCI framework, the above-mentioned DL DCI format can be used for beam indication through TCI state even if there is no data / channel to be sent or received. In this case, some of the existing TCI field indicator values ​​in the DCI can be changed and used for beam indication.

[0237] Based on this (i.e., based on a unified TCI framework), as a method of "indicating a change of a DL Rx beam or a UL Tx beam by a single indication without performing separate indications for the DL Rx beam and the UL Tx beam", the gNB can indicate the simultaneous change of the RU beams (or the DL Rx beams and the UL Tx beams of the RU) contained in the NCR by an indication of a joint TCI state. Here, the joint TCI state may be a TCI state related to the control link C link. In this way, when the change of the DL Rx beam and the UL Tx beam of the RU is indicated by an indication of a joint TCI state, the application time and period of the joint TCI state may be indicated together with the indication of the joint TCI state ID. Alternatively, the application time and period of the joint TCI state may be configured based on a previous agreement or commitment. For example, the application time of the joint TCI state may be continuously applied starting from a specific number of time slots / symbols after the NCR or MT receives the indication of the joint TCI state. Alternatively, the joint TCI state may be applied starting from the time the indication is received.

[0238] 2. Scenario 2 - Determine the RU beam based on predefined rules

[0239] Scenario 2 describes a case where the Tx / Rx beams of the RU are not directly indicated, but a pre-agreed / defined / configured (i.e., based on a predefined rule) beam corresponding to a specific Tx / Rx beam of the MT is used (for example, if the NCR lacks the capability to receive an indication of the beams for the backhaul link, or even if the NCR has the capability, the gNB does not indicate the beams). Although the gNB does not directly indicate the Tx / Rx beams of the backhaul link to the MT, the gNB may expect that the Tx / Rx beams of the backhaul link will be configured based on the following prior agreement or commitment. In this case, the Tx / Rx beams of the RU may be pre-defined / agreed / configured to correspond to the beams used by the MT to send and receive specific signals / channels. Depending on the beam direction indicated by the gNB to the MT of the NCR, the Tx / Rx beams of the RU and the Tx / Rx beams of the MT may be different from each other.

[0240] Scenario 2 described below can be applied (or limited) to when the frequency of MT operation is the same as or at least within the frequency band of RU operation. In other words, scenario 2 can be applied when the time and / or frequency resources between MT and RU match, or when the time and / or frequency resources between MT and RU partially overlap, or even if the time and / or frequency resources do not overlap, the frequency bands are so closely related that transmission may occur in adjacent frequency bands between the transmission of MT and the reception of RU (and / or the transmission of RU and the reception of MT). In order to indicate the DL Rx beam of RU, the following alternative scheme can be considered. Alternatively, as described above, scenario 2 can be applied when the transmission or reception on the control link and the transmission or reception on the backhaul link are not performed simultaneously.

[0241] For example, the application of scenario 2, which will be described later, 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 backhaul link. For example, if the time resources of the MT or C link do not overlap with the time resources of the RU or the backhaul link (and / or if there is no explicit indication described in scenario 1), the beam of the backhaul link can be determined based on the predefined rules described in scenario 2.

[0242] At the same time, the alternative scheme described later can be based on a unified TCI framework. In other words, when the NCR determines the DL Rx beam of the RU according to the method described later, the NCR can change the UL Tx beam of the RU to a UL Tx beam associated with the DL Rx beam of the RU, which is pre-agreed / defined / configured. Alternatively, the NCR may consider that the change has been indicated. Alternatively, the NCR may change the UL Tx beam of the RU to a UL Tx beam associated with the DL Rx beam of the RU, which is pre-agreed / defined / configured. Alternatively, the NCR may consider that the change has been indicated. The association between the DL Rx beam of the RU and the UL Tx beam can be determined based on the joint TCI state of the NCR.

[0243] When the DL Rx beam and UL Tx beam of the RU are changed by indication of the joint TCI state, the application time of the joint TCI state and the application period of the indicated joint TCI state can be configured based on a previous agreement or commitment. For example, the joint TCI state can be applied after a specific number of time slots / symbols from the time when the joint TCI state is indicated, or the application time of the joint TCI state can correspond to the time when the joint TCI state is indicated.

[0244] (1) Alternative 2-1 - Based on predefined CSS

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

[0246] Regarding the indication of the DL Rx beam (or the DL Rx beam of the RU), the gNB may also pre-agree / define / configure time offset information about the number of time slots (or time offset) (the time offset information may be sent together). For example, from a specific time based on a previous agreement or commitment, the DL Rx beam of the RU may be changed to a specific beam direction corresponding to the MT. Alternatively, the beam change according to alternative 2-1 of scenario 2 may be applied to a duration other than the indication of the beam change and time offset of scenario 1. For example, as described above, the beam change according to alternative 2-1 of scenario 2 may be defined as a default behavior. Specifically, when a beam change to the first DL Rx beam and a time offset of k time slots are indicated according to scenario 1, the NCR may change the DL Rx beam of the RU to the first DL Rx beam based on k time slots. Once the application of the change to the first DLLRx beam according to scenario 1 ends, the DL Rx beam of the RU may be configured / changed according to alternative 2-1. Alternatively, if there is no indication to perform beam changing according to scenario 1, beam changing according to alternative 2-1 of scenario 2 may be applied.

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

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

[0249] Specifically, it may be pre-agreed / defined / configured that the Rx beam of the RU corresponds to the Rx beam used by the MT to receive a specific search space set configuration instead of broadcasting system information. Alternatively, when the gNB sends an MT-specific (or UE-specific) control signal instead of broadcasting system information, it may be pre-defined / agreed / configured that the Rx beam of the RU corresponds to the Rx beam used by the MT to receive the control signal. As described above, the search space ID used to send the MT-specific control signal is sent in the MT-specific BWP (or UE-specific BWP), and therefore it is necessary to define / specify the Rx beam of which BWP of the MT the Rx beam of the RU corresponds to. For example, based on a previous agreement or commitment, the Rx beam of the RU may correspond to the Rx beam of the MT in a search space associated with a specific BWP of the MT (e.g., a default BWP or an initial BWP). Alternatively, the gNB may also indicate the search space ID of the MT corresponding to the Rx beam of the RU, together with the ID of the BWP corresponding to the search space ID.

[0250] The application time of the Rx beam of the RU according to alternative 2-2 of scenario 2 may be determined based on a predefined / configured / agreed time offset, or may be a duration during which the beam change and time offset of 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 behavior. Specifically, when a beam change to a first DL Rx beam and a time offset of k time slots are indicated according to scenario 1, the NCR may change the DL Rx beam of the RU to the first DL Rx beam based on k time slots. Once the application of the change to the first DL Rx beam according to scenario 1 ends, the NCR may configure / change the DL Rx beam of the RU according to alternative 2-2. Alternatively, if there is no indication of a beam change according to scenario 1, the beam change according to alternative 2-2 of scenario 2 may be applied.

[0251] Alternatively, with respect to the application of alternative 2-2, if the gNB does not indicate the search space ID of a specific search space, the ID of the specific search space may be pre-agreed / defined. In other words, the Rx beam of the RU may be pre-agreed / defined to correspond to the Rx beam used or applied by the MT in the pre-agreed / defined specific search space, even if there is no explicit indication of the specific search space from the gNB. For example, the specific search space may be pre-agreed / defined as the search space with the lowest index, the highest index, or the middle index among the search spaces of the MT. In this case, the BWP associated with the pre-agreed / defined specific search space may also be pre-agreed / defined as the active BWP, the default BWP, the initial BWP, or the BWP with the highest index (or the BWP with the lowest index).

[0252] (3) Alternative 2-3 - Based on a predefined CORESET

[0253] In alternative 2-3, the Rx beam of the RU may be pre-agreed / defined / configured to correspond to the Rx beam used by the MT in a specific CORESET among the Rx beams of the MT. Here, the specific CORESET may be configured / determined by the CORESET ID indicated by the gNB. Alternatively, the specific CORESET may be pre-agreed / defined.

[0254] Alternatively, unlike Alternative 2-1 and Alternative 2-2, the gNB may indicate the Rx beam of the MT by indication of the CORESET ID without indicating a specific search space of the MT. Since the CORESET is also BWP-specific, similar to Alternative 2-2, the CORESET may be a specific CORESET indicated for a pre-agreed / predefined MT-specific BWP (e.g., a default BWP or an initial BWP). Alternatively, the gNB may indicate both the CORESET ID and the BWP ID of the MT associated with the Rx beam of the RU.

[0255] Alternatively, in the indication of the DL Rx beam, time offset information such as the number of time slots may also be included. For example, if the gNB indicates the Rx beam of the MT and k time slots for a specific CORESET ID, the gNB may expect that the DL Rx beam of the RU based on the MT will switch to the indicated direction after k time slots from the indication of the DL RS of the beam change. Alternatively, even if the time offset information about the number of time slots is not indicated, the change to the indicated DL Rx beam may be applied from a specific time based on a previous agreement or commitment. For the time slot offset (included in the time offset information), a specific operation may be agreed as a default behavior. If the time slot offset is not indicated, the default behavior is performed; and if the time slot offset is indicated, the indicated operation is performed. For example, when the time slot offset is indicated, the DL Rx beam of the indicated RU may be applied for a duration corresponding to the indicated time slot offset from the pre-agreed time. For example, if a change in the DL Rx beam of the RU and a time offset k (k time slots / subframes / symbols) are indicated together, the DL Rx beam of the RU may be set to the indicated beam (or beam direction) for a duration corresponding to the time offset k (k time slots / subframes / symbols) from the pre-agreed time. After this duration, the beam may be set to the DL Rx beam before the indication or the pre-agreed default beam.

[0256] Alternatively, with respect to the application of alternatives 2-3, if the gNB does not indicate a specific CORESET ID, a specific CORESET ID may be pre-agreed / defined. In other words, the Rx beam of the RU may be pre-agreed / defined to correspond to the Rx beam used or applied by the MT for the specific CORESET ID, even if the gNB does not explicitly indicate the specific CORESET ID. For example, the specific CORESET ID may be pre-agreed / pre-defined as the lowest index, the highest index, or the middle index among the (configured) CORESET IDs of the MT. In this case, the BWP associated with the pre-agreed / predefined specific CORESET ID may also be pre-agreed / defined as the active BWP, the default BWP, the initial BWP, or the BWP with the highest index (or the BWP with the lowest index).

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

[0258] The Rx beam of the RU can be pre-agreed / pre-defined to correspond to the Rx beam of the MT to which the TCI state ID indicated by the gNB is applied.

[0259] Alternatively, in the indication of the DL Rx beam, time offset information such as the number of time slots may also be included. For example, if the gNB indicates the Rx beam of the MT and k time slots for a specific TCI state ID, the gNB may expect that the DL Rx beam of the RU, based on the MT, will switch to the indicated direction after k time slots from the indication of the DL RS of the beam change. Alternatively, even if the time offset information about the number of time slots is not indicated, the change to the indicated DL Rx beam may be applied from a specific time based on a previous agreement or commitment. For the time slot offset (included in the time offset information), a specific operation may be agreed as a default behavior. If the time slot offset is not indicated, the default behavior is performed; and if the time slot offset is indicated, the indicated operation is performed. For example, when a time slot offset is indicated, the DL Rx beam of the indicated RU may be applied for a duration corresponding to the indicated time slot offset from the pre-agreed time. For example, if a change in the DL Rx beam of the RU and a time offset k (k time slots / subframes / symbols) are indicated together, the DL Rx beam of the RU may be set to the indicated beam (or beam direction) for a duration corresponding to the time offset k (k time slots / subframes / symbols) from the pre-agreed time. After this duration, the beam may be set to the DL Rx beam before the indication or the pre-agreed default beam.

[0260] Alternatively, with respect to the application of alternatives 2-4, if the gNB does not indicate a TCI state ID, a specific TCI state ID associated with the Rx beam determination of the RU may be pre-agreed / defined. For example, the specific TCI state ID may be pre-agreed / pre-defined as the lowest or highest index among the TCI state IDs of the MT. In this case, the BWP associated with the pre-agreed / predefined specific TCI state ID may also be pre-agreed / defined as the active BWP, the default BWP, the initial BWP, or the BWP with the highest index (or the BWP with the lowest index).

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

[0262] In alternatives 2-5, the Rx beam of the RU can be pre-agreed / defined / configured to correspond to the Rx beam used by the MT to control the RU backhaul link when sending side control information. In this case, the side control information can be sent via PDCCH, PDSCH, or both PDCCH and PDSCH in the search space of the MT. For each case, the following options 1, 2, and 3 can be considered.

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

[0264] In this case, since the search space corresponds to the MT-specific search space, the method proposed in "Alternative Scheme 2-2" can be used. However, since there may be multiple search spaces for the transmission side control information, it is necessary to clearly define the search space for applying Option 1 to the transmission side control information (the case of directly indicating the search space ID may be the same as Alternative Scheme 2-2). For example, it can be assumed that the MT is instructed to change the DL Rx beam of the RU based on the side control information received in the predefined / pre-agreed specific search space. In this case, the NCR may determine the DL Rx beam of the RU that the MT applies to the DL Rx beam receiving the side control information in the specific search space, or the NCR may assume that the DL Rx beam of the MT is indicated by the gNB. For example, the specific search space may be the search space with the smallest or highest index among the search space IDs. Alternatively, the specific search space ID may be pre-agreed / pre-defined as at least one ID among the multiple search space IDs of the MT. In this case, the specific search space may be limited to the BWP where the MT receives the side control information. Alternatively, the specific search space may be configured for a specified specific BWP, or the specific search space may be a search space based on a previously agreed specific BWP. For example, the specific search space may be a default BWP, an initial BWP, a BWP with the lowest or highest BWP ID.

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

[0266] Option 2 may be the case where the gNB instructs the MT to change the RU’s DL Rx beam via PDSCH. In this case, the gNB can expect the RU’s DL Rx beam to change to the beam that the MT uses to receive PDSCH.

[0267] 3) Option 3: When the MT's side control information is sent via both PDCCH and PDSCH in the search space

[0268] In option 3, the methods of option 1 and option 2 can be combined, and the DL Rx beam of the RU can be configured accordingly. Specifically, the DL Rx beam of the RU can be aligned with the beam of the search space of the MT receiving side control information, or with the Rx beam related to the PDSCH of the MT receiving side control information. In this case, there may be differences in the change of the DL Rx beam of the RU depending on whether the side control information is indicated through the search space or through the PDSCH. For example, when the side control information is indicated through the search space, the change timing of the DL Rx beam of the RU may be different from that when the side control information is indicated through the PDSCH. For example, when the side control information is indicated through the search space, the DL Rx beam of the RU may change after an indicated (or pre-agreed) specific time offset. When the side control information is indicated through the PDSCH, the DL Rx beam of the RU may change from a pre-agreed time (for example, from the start time resource of the next subframe). Alternatively, when the side control information is indicated through the search space, the DL Rx beam of the RU may change only for an indicated (or pre-agreed) specific time resource. When side control information is indicated via PDSCH, the DLRx beam of the RU can be changed from a pre-agreed time.

[0269] Alternatively, in Option 1 to Option 3, the Rx beam of the RU is described as a beam for receiving DL signals / channels on the backhaul link. However, as described above, not only changes in the DL Rx beam indicating the backhaul link but also changes in the UL Tx beam may be considered. In other words, the methods proposed in Option 1 to Option 5 may be interpreted as indicating changes in both the DL Rx beam and the UL Tx beam of the RU. In other words, there may not be an independent beam report for the RU beam, and the RU beam may be aligned with the MT beam. In addition, the QCL relation between the Tx beam and the Rx beam of the MT may be applied to the Tx beam and the Rx beam of the RU in the same manner. For example, when the gNB notifies the MT about the change of the RU beam through the CORESET ID (and / or BWP ID), the DL Rx beam of the RU can be aligned with the Rx beam of the MT corresponding to the indicated CORESET ID (and / or BWP ID), and can be aligned with the Tx beam of the MT corresponding to the indicated CORESET ID (and / or BWP ID).

[0270] Alternatively, in the indication of the DL Rx beam and UL Tx beam of the RU, time offset information such as the number of time slots may also be included. For example, if the gNB indicates the Rx beam and k time slots together, the gNB may expect that: based on the MT, the DL Rx beam and UL Tx beam of the RU will switch to the indicated direction after k time slots from the indication. Alternatively, even if the time offset information about the number of time slots is not indicated, the change applied to the DL Rx beam and UL Tx beam of the indicated RU may be applied from a specific time based on a previous agreement or commitment. For the time slot offset (included in the time offset information), a specific operation may be agreed as a default behavior. If the time slot offset is not indicated, the default behavior is performed; and if the time slot offset is indicated, the indicated operation is performed. For example, when the time slot offset is indicated, the DL Rx beam and UL Tx beam of the indicated RU may be applied for a duration corresponding to the indicated time slot offset from the pre-agreed time. For example, if the change of the DL Rx beam and UL Tx beam of the RU is indicated together with the time offset k (k time slots / subframes / symbols), the DLRx beam and ULTx beam of the RU may be set to the indicated beam (or beam direction) for a duration corresponding to the time offset k (k time slots / subframes / symbols) from the pre-agreed time. After this duration, the beam may be set to the DLRx beam and ULTx beam of the RU before the indication or the pre-agreed default beam.

[0271] Alternatively, independently of the indication of the DLRx beam of the RU, the direction of the Tx beam applied by the MT when transmitting a specific signal / channel may be indicated as the ULTx beam of the RU. In other words, in order to indicate a change in the ULTx beam of the RU, if the gNB indicates a specific RACH preamble or RACH opportunity to the MT through the side control information, the ULTx beam of the RU may be aligned with the ULTx beam of the MT during the transmission of the RACH preamble or RACH opportunity. Alternatively, in order to indicate a change in the ULTx beam of the RU, if the gNB indicates a specific SRI for the MT to the MT through the side control information, the UL Tx beam of the RU may be aligned with the UL Tx beam used or applied by the MT when transmitting the SRS corresponding to the specific SRI.

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

[0273] Regarding scenario 3, the gNB may expect that the Tx / Rx beam currently applied to the MT will be aligned with the Tx / Rx beam of the RU, or the gNB may indicate that the Tx / Rx beam of the MT and the Tx / Rx beam of the RU are aligned. In this case, the gNB may expect that the Tx / Rx beam in the most recent time slot (or symbol) in which the MT performs transmission / reception before the (nk)th time slot will be aligned with the Tx / Rx beam of the RU in the nth time slot. Here, the time offset k may be in units of time slots or symbols. Scenario 3 may also be applied after the indication of the change of the Tx / Rx beam of the RU in scenario 1 or scenario 2. In other words, when the change of the Tx / Rx beam of the RU is explicitly / implicitly indicated by the side control information, the gNB may expect that the indicated Tx / Rx beam of the RU will be applied for a specific duration.

[0274] Alternatively, the gNB may expect that the beam corresponding to the most recent TCI state ID indicated to the MT will be aligned with the DL Rx beam (and / or UL Tx beam) of the RU. In other words, the NCR may determine that the DL Rx beam of the RU is indicated to change to the beam corresponding to the most recent TCI state ID indicated to the MT. Here, the most recent TCI state ID indicated to the MT may refer to the TCI state ID configured for scheduling PDCCH and / or PDSCH.

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

[0276] 1) First, the most recent TCI state ID may refer to the TCI state ID successfully received by the NCR or MT. In other words, the most recent TCI state ID may refer to the TCI state ID of the PDSCH indicated by the gNB to the NCR or MT. Alternatively, the most recent TCI state ID may refer to the TCI ID of the PDCCH most recently monitored by the NCR or MT, or the TCI ID of the PDCCH detected by the NCR or MT.

[0277] In other words, when the gNB instructs the NCR or MT to receive the PDCCH (or PDSCH) (i.e., when the gNB schedules the PDCCH (or PDSCH)), the gNB can expect that the DLRx beam (and / or UL Tx beam) of the RU will be aligned with the beam of the MT corresponding to the TCI state ID (or unified TCI state ID) scheduled to the MT for the PDCCH (or PDSCH). In this case, the MT can notify the gNB via HARQ feedback that the MT has received scheduling information about the PDSCH (or PDCCH).

[0278] Alternatively, since the gNB cannot know whether the signal of the scheduled PDSCH (or PDCCH) containing the TCI state ID is received by the MT, an operation based on a previous agreement / commitment related to the reception of the scheduling signal can be performed. For example, the NCR or MT can change the DL Rx beam (and / or UL Tx beam) of the RU based on the TCI state ID of the most recently scheduled PDSCH (or PDCCH). Alternatively, the NCR or MT can change the DL Rx beam (and / or UL Tx beam) of the RU based on the TCI state ID of the most recently monitored (or detected) PDCCH. In this case, the timing of changing the DL Rx beam (and / or UL Tx beam) of the RU based on the TCI state ID can be when or after the NCR or MT sends the HARQ signal of the PDSCH or PDCCH scheduled by the scheduling signal to the gNB. Alternatively, in the absence of such a HARQ feedback process, it can be assumed that the NCR or MT will always correctly receive the PDSCH (or PDCCH) containing 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 or after a specific time after receiving (detecting or monitoring) the PDSCH (or PDCCH).

[0279] In a certain scenario discussion (RAN1#109-e meeting), it has been discussed that the same TCI state as the TCI state configured for the operation of NCR-MT can also be applied to the backhaul link (NCR-Fwd link) to indicate the beam to the backhaul link. In this case, it is necessary to further define which of the multiple TCI states configured for NCR-MT will be applied to the DL Rx of the backhaul link (NCR-Fwd link).

[0280] - First, it can be assumed that the TCI state applied to the backhaul link (NCR-Fwd link) on a specific time resource is always the same as the TCI state applied to the NCR-MT on a specific time resource. In this case, it is necessary to further define a method for determining the TCI state applied to the backhaul link (NCR-Fwd link) on a time resource when the NCR-MT does not perform DL Rx.

[0281] - Alternatively, the TCI state applied to the NCR-Fwd link can be configured / determined independently of the TCI state currently applied to the NCR-MT. In this case, it is necessary to clearly define what the TCI state applied to the backhaul link (NCR-Fwd link) is.

[0282] Additionally, a method for determining the beam direction of the UL Tx beam applied to the backhaul link (NCR-Fwd link) needs to be defined. Considering that the UL of the control link and the UL of the backhaul link (NCR-Fwd link) are time division multiplexed (TDMed), it may not be appropriate to determine the UL Tx beam of the backhaul link (NCR-Fwd link) based only on the UL Tx beam of the control link.

[0283] In consideration of this problem, the following method may be considered to determine the beam of the backhaul link (NCR-Fwd link) independently of a time resource in which the NCR-MT does not perform transmission / reception or independently of a beam applied to the NCR-MT.

[0284] - The beam direction applied to the backhaul link (NCR-Fwd link) can be explicitly indicated.

[0285] - The beam direction applied to the backhaul link (NCR-Fwd link) can be determined / configured based on the beam used by the NCR-MT to transmit and receive specific signals / channels.

[0286] - The beam direction applied to the backhaul link (NCR-Fwd link) can be determined / configured based on the beams most recently applied by the NCR-MT for transmission and reception.

[0287] Based on these methods, the following methods can be further considered.

[0288] -When the NCR-MT performs a transmission / reception operation on a specific time resource, the beam direction (e.g., TCI state) applied to the NCR-MT can be applied to the transmission / reception operation of the backhaul link (NCR-Fwd link). For example, for a specific time resource where signal transmission / reception on the backhaul link and signal transmission / reception on the control link are performed simultaneously, the direction of the UL / DL Tx / Rx beam of the backhaul link can be applied / configured as the beam direction applied to the NCR-MT.

[0289] -When the NCR-MT does not perform a transmit / receive operation on a specific time resource, the beam direction of the transmit / receive operation on the backhaul link (NCR-Fwd link) may be determined / configured as the beam direction indicated / configured according to the above scenario 1 or scenario 2.

[0290] The following methods will be explained in detail below: a method for determining a specific time resource or a specific duration at which signal transmission / reception on a backhaul link and signal transmission / reception on a control link are performed simultaneously; and a method for determining the direction of the UL / DL Tx / Rx beam of the backhaul link on a specific time resource.

[0291] Simultaneous operation between control link and backhaul link

[0292] As described above, the beam of the backhaul link of the NCR can be configured / determined based on different indication methods, depending on whether simultaneous operation occurs between the control link and the backhaul link. Regarding this configuration / determination, the gNB and the NCR may need a criterion to determine / define the duration considered for the simultaneous operation between the control link and the backhaul link. For example, even if the gNB sends SSB, CSI-RS, etc., the time resources during which the NCR-MT does not perform (downlink signal) reception (or does not perform monitoring) can be determined as the duration during which the simultaneous operation between the control link and the backhaul link is not performed (i.e., the non-simultaneous operation duration). Alternatively, even if the NCR-MT does not perform reception, the duration or time resources during which the gNB sends SSB, CSI-RS, etc. can be regarded as the duration of simultaneous operation between the control link and the backhaul link. When determining the duration considered for the simultaneous operation between the control link and the backhaul link, it is not clearly defined whether the actual reception operation of the NCR is necessary. Therefore, it is necessary to resolve / prevent any misunderstanding / ambiguity between the gNB and the NCR when indicating the beam of the backhaul link (NCR-Fwd link). To this end, the duration of simultaneous operation between the control link and the backhaul link (or between NCR-MT and NCR-Fwd) needs to be clearly defined. In other words, when the gNB sends DL signals / channels but the NCR-MT does not perform DL signals from the gNB, additional definitions may be required to resolve any ambiguity as to whether simultaneous operation between the gNB and the NCR is performed.

[0293] The method for resolving the above ambiguity will be explained in detail below. The simultaneous operation of NCR is assumed and described as a criterion for selecting the beam of the backhaul link (NCR-Fwd link), but the simultaneous operation of NCR can also be regarded as a criterion of other indications (for example, indication of the access link of NCR-Fwd, ON / OFF operation of NCR, power control of NCR-Fwd, etc.). Therefore, the simultaneous operation between NCR-MT and NCR-Fwd can be considered for both DL and UL operations, or the simultaneous operation can be considered only for DL ​​or UL operations. For example, if the gNB determines that there is no simultaneous UL transmission capability between NCR-Fwd and NCR-MT based on the capability information signaling about the simultaneous operation between NCR-Fwd and NCR-MT, the simultaneous operation can be determined only based on the DL operation. Alternatively, if the capability information related to the simultaneous operation between NCR-Fwd and NCR-MT is for both DL and UL operations, the gNB can determine the simultaneous operation for each of the UL and DL operations and configure / indicate the beam of the backhaul link based on the capability information. In this case, the MT or NCR may distinguish the durations of DL and UL based on the time domain resource configuration received through RRC / MAC-CE / DCI, and may apply the definition of simultaneous operation differently for each duration.

[0294] For DL ​​(i.e., for the time resources determined by the NCR-MT as the DL duration), the duration of performing the simultaneous operation of the NCR can be defined as the duration of performing the DL reception operation of the gNB via the control link. In this case, the following alternatives can be considered.

[0295] For convenience of explanation, the simultaneous operation of NCR-MT and NCR-Fwd (in the time domain) is defined and explained as the simultaneous operation or concurrent operation of NCR.

[0296] 1. Duration of simultaneous operation related to reception of DL signals / channels

[0297] A method of determining / defining a duration of a simultaneous operation of performing NCR in relation to reception of a DL signal / channel will be explained in detail below.

[0298] (1) Alternative 3-1

[0299] Regarding determining the simultaneous operation of the NCR according to Alternative Scheme 3-1, the NCR may determine only the time resource for receiving a specific DL signal / channel from the gNB as the duration or time resource of the DL reception operation (or reception operation of the control link) of the NCR-MT. The specific DL signal / channel may be defined as at least one of the following signals / channels.

[0300] -PDSCH

[0301] -Search space for PDCCH monitoring (however, specific search spaces such as type-0 CSS may be excluded from the search space for PDCCH monitoring)

[0302] As the beam of NCR-Fwd (the beam of the backhaul link or the Rx beam of the backhaul link), the NCR can set the beam (the beam of the control link or the Rx beam of the control link) that the NCR-MT uses to receive the DL signal / channel on the time resource for sending / receiving the signal / channel. In this case, for the remaining time resources of the DL time resources of the NCR-MT except the time resources for sending a specific DL signal / channel, the NCR can assume that the NCR-MT does not receive the specific DL signal / channel, and determine the remaining time resources as the duration for performing only the NCR-Fwd operation. In other words, the NCR can assume that the NCR-MT does not perform a DL reception operation on the remaining time resources. Alternatively, whether the NCR-MT performs a DL reception operation on the remaining time resources can be determined based on the simultaneous operation capability of the NCR. For example, if the NCR-MT has the simultaneous operation capability, the gNB can assume that the NCR-Fwd and the NCR-MT can perform reception simultaneously on the remaining time resources. However, if NCR-MT does not have simultaneous operation capability and NCR-Fwd operates on the remaining time resources, the gNB may assume that NCR-MT does not operate on the remaining time resources.

[0303] Alternatively, the NCR may determine only the time resources for performing / attempting to receive a UE-specific DL signal / channel as the time resources for the NCR-MT to perform DL reception through the control link.

[0304] Therefore, the NCR can determine the beam direction applied to the control link on the time resources where the NCR-MT performs DL reception via the control link as the beam direction of the return link of the NCR-Fwd. The NCR can determine / configure the beam direction of the return link based on the beam direction indicated on the remaining time resources according to the above-mentioned explicit / implicit rules (scenario 1 and scenario 2). If the NCR-Fwd performs a forwarding operation on the remaining time resources and the beam applied to the control link is different from the beam applied to the return link, the NCR can perform DL reception without via the control link.

[0305] (2) Alternative 3-2

[0306] In alternative 3-2, even if the NCR-MT does not perform actual DL reception, the NCR-MT may determine the time resources in which the serving cell is scheduled / configured to send DL signals / channels as the time resources for performing DL reception via the control link.

[0307] Such specific DL signal / channel (DL signal / channel transmitted by the serving cell) may include at least one of the following signals / channels.

[0308] -Search space used for PDCCH monitoring (however, specific search spaces such as type-0 CSS may be excluded from the search space used for PDCCH monitoring).

[0309] -PDSCH

[0310] -CSI-RS

[0311] -SIB1

[0312] -SS / PBCH blocks (e.g., ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon)

[0313] In other words, in order to monitor the time resources (or first time resources) in which the NCR-MT actually receives DL signals as described in Alternative Solution 3-1, and monitor the reception of signals / channels from the serving cell, the gNB and the NCR may assume / determine that simultaneous operations are performed on the time resources (or second time resources) configured for the NCR-MT. Specifically, for the second time resources, the gNB may assume / determine that the time resources in which the NCR-MT is expected to monitor and / or the time resources configured for future monitoring will be regarded as the duration of performing simultaneous operations, regardless of whether the NCR-MT actually performs a signal / channel reception operation.

[0314] Alternatively, the gNB may assume / determine that simultaneous operation between NCR-MT and NCR-Fwd is performed on all time resources configured for NCR-MT. For example, the gNB may assume that simultaneous operation between NCR-MT and NCR-Fwd is performed on (all) time resources configured for NCR-MT (such as search space for PDCCH monitoring, PDSCH, CSI-RS, SSB, etc.). For example, regardless of whether NCR-MT actually receives signals, the gNB and NCR may assume / determine that simultaneous operation between NCR-MT and NCR-Fwd is performed on time resources configured by the gNB for sending cell-specific signals / channels.

[0315] The NCR may determine that, for the time resources for performing simultaneous operation as determined in alternative 3-2, the NCR-Fwd sets the beam direction of the backhaul link to the beam direction used / applied by the NCR-MT for receiving the corresponding signal / channel. Alternatively, the beam direction of the NCR-Fwd on the time resources for performing simultaneous operation may be configured based on an indication from the gNB, or the beam direction of the NCR-Fwd (or the backhaul link) during the duration for performing simultaneous operation may be configured based on a previous agreement.

[0316] For the time resources determined to perform simultaneous operation, the NCR may determine the beam corresponding to the beam of the control link of the NCR-MT as the beam of the backhaul link (e.g., DL beam), even if DL signal reception is not performed via the control link on the second time resource. For the remaining time resources other than the above time resources, the beam of the backhaul link may be configured / determined according to explicit / implicit indication (based on at least one alternative in scenario 1 and / or scenario 2).

[0317] 2. Duration of simultaneous operation associated with transmission of UL signals / channels

[0318] Regarding the transmission of UL signals / channels, the duration for which the NCR performs this simultaneous operation may be determined / defined as a time resource for performing UL transmission to the gNB via a control link.

[0319] (1) Alternative 4-1

[0320] In alternative 4-1, the time resources / duration associated with the simultaneous operation may be determined as time resources scheduled / configured by the gNB for actual transmission of UL signals (such as PRACH, PUSCH, PUCCH, etc.) of the NCR-MT. In other words, the NCR may configure / determine that the UL Tx beam of the NCR-Fwd is aligned with the UL Tx beam of the NCR-MT on the time resources configured for actual transmission of the UL signals / channels. For example, the time resources configured / scheduled for actual transmission of the UL signals may be time resources for PUSCH and / or PUCCH scheduled by the DCI received from the gNB. At the same time, the NCR may determine that the remaining time resources after excluding the time resources scheduled / configured for actual transmission of the UL signals of the NCR-MT are time resources for not performing the simultaneous operation.

[0321] Alternatively, for the remaining time resources (e.g., the remaining time resources after excluding the time resources configured for the transmission of UL signals / channels in the UL duration indicated by the TDD configuration of the NCR-MT), the NCR may assume that the UL Tx of the NCR-MT (or the UL Tx via the control link) is not performed, and may determine / configure the UL Tx beam of the backhaul link (NCR-Fwd link). Alternatively, the method of configuring the UL Tx beam of the backhaul link (NCR-Fwd link) may vary according to the simultaneous operation capability of the NCR (i.e., the ability to simultaneously transmit on both the control link and the backhaul link (NCR-Fwd link)). For example, if the NCR does not have this simultaneous operation capability, the NCR may determine to perform the transmission operation on the backhaul link on the remaining time resources after excluding the time resources in which the PUSCH and PUCCH configured for the control link (or NCR-MT) are transmitted. For the remaining time resources, the NCR may configure / determine the indicated beam direction as the direction of the ULTx beam of the backhaul link according to scenario 1 and / or scenario 2.

[0322] (2) Alternative 4-2

[0323] In alternative 4-2, even if actual UL transmission of the NCR-MT is not performed, the duration for performing the simultaneous operation may be determined by considering the time resources configured for UL transmission through the control link. In other words, the duration for performing the simultaneous operation may be determined as the time resources configured for actual UL transmission of the NCR-MT as described in alternative 4-1 and the time resources configured for UL transmission to the serving cell. In other words, the gNB and the NCR may assume / determine that the simultaneous operation of the NCR will be performed on the time resources configured for actual UL transmission of the NCR-MT as described in alternative 4-1 and the time resources configured for UL transmission to the serving cell. For example, the time resources configured for UL transmission to the serving cell may be time resources configured by SSB to RO mapping for the NCR-MT and / or time resources configured for contention-based RACH transmission.

[0324] In this case, the NCR may configure / determine that the UL Tx beam of the backhaul link (NCR-Fwd) is aligned with the UL Tx beam of the control link (NCR-MT) for the duration of performing the simultaneous operation determined by alternative 4-2. Alternatively, the beam direction of the backhaul link (NCR-Fwd) may be configured on the time resources for performing the simultaneous operation according to an instruction from the gNB, or the beam direction of the backhaul link (NCR-Fwd) may be configured for the duration of performing the simultaneous operation based on a previous agreement.

[0325] For the remaining time resources after excluding the time resources configured / scheduled by the gNB for the actual transmission of UL signals (such as PRACH, PUSCH, PUCCH, etc.) of the control link (NCR-MT) and the time resources configured for UL signal transmission to the serving cell, the NCR may determine not to perform the simultaneous operation on the remaining time resources. In this case, the NCR may not align the beam of the control link (NCR-MT) with the beam of the backhaul link (NCR-Fwd) on the remaining time resources.

[0326] Hereinafter, a method of configuring the on / off state of the forwarding operation of the NCR will be explained in detail.

[0327] The ON-OFF state of the NCR may be defined / determined in certain scenarios, as shown in Table 18 and / or Table 19 below.

[0328] [Table 18]

[0329]

[0330] [Table 19]

[0331]

[0332] Additionally, the beam used for the backhaul link (NCR-Fwd) can be indicated as shown in Table 20.

[0333] [Table 20]

[0334]

[0335]

[0336] Based on the contents defined in Table 20, the method of configuring / applying the beam of the backhaul link of NCR can be summarized as follows.

[0337] -NCR may apply / configure a beam corresponding to a beam of C-link (applied / used) during a duration in which simultaneous operation is performed between the control link (C-link) and the backhaul link (Fwd-link) as a beam of Fwd-link.

[0338] -If independent beam direction indication of the backhaul link is not supported (i.e., if the NCR does not support adaptive beams of the backhaul link), the NCR may determine / apply the beam of the backhaul link based on a predefined rule (e.g., DL beam according to QCL of CORESET 0, control link beam corresponding to PUCCH resource ID 0) for a duration during which no simultaneous operation is performed between the control link and the backhaul link (non-simultaneous operation duration).

[0339] -If independent beam direction indication of the backhaul link is supported (i.e., if the NCR does not support adaptive beam of the backhaul link), and if the gNB does not indicate the beam of the backhaul link through MAC-CE, the NCR may determine / apply the beam of the backhaul link based on a predefined rule (e.g., DL beam according to QCL of CORESET 0, control link beam corresponding to PUCCH resource ID 0) for a duration during which no simultaneous operation is performed between the control link and the backhaul link (non-simultaneous operation duration).

[0340] -If independent beam direction indication of the backhaul link is supported (i.e., if the NCR supports adaptive beams of the backhaul link), and if the gNB indicates the beam of the backhaul link through MAC-CE, the NCR may determine / apply the indicated DL beam (e.g., the DL beam indicated based on the TCI state ID) and the indicated UL beam (e.g., the UL beam indicated based on the SRI) as the beam of the backhaul link for the backhaul link during the duration in which no simultaneous operation is performed (non-simultaneous operation duration).

[0341] Regarding the application of the method for configuring the backhaul link beam, two types of NCRs are additionally considered. Here, the two types of NCRs are: an NCR that does not support backhaul link beam indication (i.e., an NCR that does not support adaptive beams of backhaul links); and an NCR that supports backhaul link beam indication (i.e., an NCR that supports adaptive beams of backhaul links). Hereinafter, the application method for configuring the backhaul link beam for each type of NCR will be explained in detail.

[0342] Fig.10 is a diagram for explaining a method of configuring a backhaul link beam based on whether backhaul link beam indication and simultaneous operation are performed.

[0343] First, an NCR that is not capable of receiving a backhaul link beam indication (i.e., an NCR that does not support adaptive beams of the backhaul link) may be considered. In this case, since the application of the predefined rule related to the beam of the backhaul link is determined based on whether simultaneous operation is performed, if there is a clear understanding of the duration of the period during which simultaneous operation is performed between the NCR and the gNB, there may be no confusion or ambiguity in the configuration of the beam of the backhaul link of the NCR.

[0344] Secondly, an NCR capable of receiving a backhaul link beam indication (i.e., an NCR supporting adaptive beams for the backhaul link) may be considered. In this case, the beam of the backhaul link applied to the NCR may vary depending on whether simultaneous operation is performed and whether a backhaul link beam indication is received. Therefore, if there is a clear understanding of the duration of the simultaneous operation period between the NCR and the gNB, the NCR can clearly configure the beam of the backhaul link. However, if the simultaneous operation state of the NCR and the order of receiving the backhaul link beam indication vary, the application / configuration of the backhaul link beam in the NCR may become ambiguous.

[0345] Reference Fig.10 , after receiving the backhaul link beam indication, the NCR configures the backhaul link beam during the duration of no simultaneous operation. When the duration for simultaneous operation starts, the NCR may reconfigure the beam of the backhaul link during the duration of no simultaneous operation after configuring the beam of the backhaul link to be applied to the beam of the control link instead of the indicated beam from the backhaul link beam indication. Specifically, when an NCR capable of receiving a backhaul link beam indication (i.e., an NCR supporting adaptive beams of the backhaul link) receives a backhaul link beam indication during the duration of no simultaneous operation, the NCR may apply / configure the indicated beam as the beam of the backhaul link during the duration of no simultaneous operation. Subsequently, for the duration of performing simultaneous operation, the NCR may apply / configure the beam of the control link as the backhaul link beam. After this duration, if the duration of no simultaneous operation starts, the NCR may face ambiguity as to whether the indicated backhaul link beam was applied as a valid backhaul link beam before the duration of simultaneous operation.

[0346] like Fig.10 As shown, when the NCR performs beam configuration of the backhaul link for the control link and the Fwd-link in the order of non-simultaneous operation -> simultaneous operation -> non-simultaneous operation, the following two alternatives may be considered as beam configuration / determination methods for the backhaul link during the duration of the second non-simultaneous operation. The NCR may consider the following cases: a case where the backhaul link beam indicated during the duration of the first non-simultaneous operation is determined to be indicated during the duration of the second non-simultaneous operation (case 1); and a case where the backhaul link beam indicated during the duration of the first non-simultaneous operation is determined not to be indicated during the duration of the second non-simultaneous operation (case 2). Specifically, the following alternatives may be considered for each case.

[0347] (1) Alternative 5-1

[0348] The NCR may determine / consider that the indication of the backhaul link beam is valid for the duration of performing the non-simultaneous operation until a new backhaul link beam is indicated / configured.

[0349] In other words, the NCR may consider the existing backhaul link beam indication as valid until a new backhaul link beam indication is received. For the duration of performing non-simultaneous operation, the NCR may determine / configure the beam corresponding to the existing backhaul link beam indication as the beam of the backhaul link (corresponding to case 1). This has the advantage of minimizing the ambiguity of the backhaul link beam indication while allowing the backhaul link beam to be configured over a long duration through a single beam indication. Additionally, alternative 5-1 has the advantage of not requiring a separate indication of time resources related to the application of beam information based on the backhaul link beam indication.

[0350] However, after the beam of the backhaul link is configured during the duration of the non-simultaneous operation based on the backhaul link beam indication, if the simultaneous operation is performed for a long period of time and then the non-simultaneous operation is started again, the backhaul link beam indication may become outdated. In this case, if the backhaul link beam is configured according to the backhaul link beam indication during the resumed non-simultaneous operation, the performance of the backhaul link may be significantly degraded. Additionally, in alternative 5-1, upon receiving the backhaul link beam indication, the NCR may not apply the beam according to the predefined rules from scenario 1 and scenario 2 during the duration of performing the non-simultaneous operation. In this case, since new backhaul link beam indications are required over time, the signaling overhead may increase.

[0351] (2) Alternative 5-2

[0352] In alternative 5-2, the information about the beam to be applied to the backhaul link indicated during the duration of performing non-simultaneous operation may be valid only for a specific duration. Here, the specific duration may be configured / determined based on the following options.

[0353] 1) Option 5-1

[0354] The specific duration may be defined as the duration from the time when the beam information is indicated until the backhaul link beam of the NCR is changed based on a predefined rule. That is, during the duration of performing non-simultaneous operation, the indicated beam of the backhaul link may no longer be valid from the start of the duration of performing simultaneous operation. In other words, the specific duration is defined as the duration from the time when the backhaul link beam is indicated until the start of simultaneous operation. Therefore, Option 5-1 of Alternative 5-2 may be the same as Option 5-2. Fig.10 This is relevant to case 2.

[0355] 2) Option 5-2

[0356] The return link beam indication may further include information about time domain resources similar to the access link beam indication. At this time, the specific duration may be defined as a time resource based on the information about the time domain resource. For example, the return link beam indication may further include time resource information about at least one of the following items: symbol offset, slot offset, duration defined by slot, symbol, periodicity, and reference SCS. The specific duration can be determined / defined based on the time resource information. On the other hand, if the specific duration overlaps with the duration of simultaneous operation, the NCR can determine that the return link beam indication is invalid during the duration of simultaneous operation. In other words, during the duration of simultaneous operation, the NCR can set the return link beam based on existing rules (e.g., setting the return link beam to the control link beam) regardless of the return link beam indication.

[0357] 3) Option 5-3

[0358] The backhaul link beam indication may be considered valid only within a predetermined or agreed specific time period. In other words, the specific duration may be defined as a predetermined or agreed specific time period starting from the receipt of the backhaul link beam indication. For example, the backhaul link beam indicated by the MAC-CE may be valid only within a predefined / preconfigured period (e.g., k time slots). The value of k time slots may be fixed based on a previous protocol or configured by the NB via RRC / MAC-CE / DCI. If the simultaneous operation starts during the duration of k time slots, the NCR may determine that the backhaul link beam indication is invalid during the time period during which the simultaneous operation is performed within the duration of k time slots.

[0359] Alternative 5-2 can eliminate the ambiguity of the return link beam indication, but when the duration of performing non-simultaneous operations is short, the application time of the indicated return link beam may be limited. Nevertheless, the possibility of the indicated return link beam being outdated is significantly reduced compared to alternative 5-1. Additionally, once a specific duration has passed, the beam of the return link can be continuously updated according to predefined rules (scenario 1 to scenario 3). For example, since the indicated return link beam may no longer be applicable once a specific duration has passed, the NCR can change and configure the beam of the return link according to predefined rules after the specific duration has passed. In this case, there is no need to indicate the beam of the return link each time, which can minimize signaling overhead compared to alternative 5-1.

[0360] Fig.11 is a diagram for explaining a method in which a device having a control link and a backhaul link formed with a BS configures a backhaul link beam.

[0361] The device may be a device corresponding to an NCR. The device may form a control link with the BS through an NCR-MT, and form a backhaul link with the BS through an NCR-Fwd (or NCR-RU). Additionally, the device may form an access link with the UE through an NCR-Fwd. The device may forward or relay a DL signal received from the BS through a backhaul link to the UE via an access link, or the device may forward or relay a UL signal received from the UE via an access link to the BS via a backhaul link. The access link and the backhaul link may be defined as a forwarding link or an NCR-Fwd link. In the following, it is assumed that the first beam configuring the backhaul link involves an Rx beam configured by the device for receiving a DL signal through the backhaul link.

[0362] Reference Fig.11 , the device may receive configuration information of a first operation duration related to the backhaul link through a control link (S111). As described above, the configuration information may be included in the side control information for controlling the backhaul link sent by the BS through the control link (towards the NCR-MT). For example, the device may determine a first operation duration based on the configuration information, and perform an operation of forwarding a DL signal to the UE during the first operation duration. As described in Table 18, the first operation duration may be a duration for performing an operation of receiving a DL signal (a DL signal to be forwarded to the UE) through the backhaul link within the duration of the forwarding operation through the NCR-Fwd being turned on.

[0363] Next, the device may configure a first beam of the backhaul link within the first operation duration (S113). Based on the above scenarios 1 to 3, the device may set the implicitly / explicitly indicated (DL Rx) beam direction to the first beam for the first operation duration (i.e., the Rx beam for the DL signal), or the device may set the same beam as the beam configured for the control link as the first beam.

[0364] As described in the "Determination of simultaneous operation between the control link and the backhaul link" section, the device can configure the first beam of the backhaul link by further considering the existence of a simultaneous operation duration in which a DL reception operation on the control link and a DL reception operation on the backhaul link are simultaneously performed. For example, if the simultaneous operation duration exists within the first operation duration, the device can set / determine the first beam to be the same as the second beam of the control link used / configured for receiving DL signals during the simultaneous operation duration. On the other hand, for the remaining operation duration other than the simultaneous operation duration within the first operation duration, the device can set the first beam to an explicitly / implicitly indicated beam direction based on the above-mentioned scenarios 1 to 3.

[0365] Therefore, as described above, the apparatus needs to accurately specify / determine the simultaneous operation duration for performing the simultaneous operation within the first operation duration in order to configure the direction of the first beam.

[0366] Specifically, the device may determine the second operation duration based on the configuration information or scheduling information from the BS, and perform the operation of receiving the DL signal via the control link during the second operation duration. As described in the "Determination of simultaneous operation between the control link and the backhaul link" section, the device may determine / specify a first time resource, which is a time resource for actually receiving the DL signal via the control link (e.g., a time resource for the PDSCH scheduled by the DCI included in the PDCCH), and / or a time resource configured for monitoring the DL signal via the control link (e.g., there may be a time resource for receiving the DL signal via the control link). For example, the device may determine / specify the second operation duration based on the DCI or RRC configuration information for scheduling the control link DL signal.

[0367] The second time resource may include a time resource configured to monitor at least one of SSB, SIB1, CSI-RS and PDCCH related to the control link. Alternatively, the second time resource may also include a time resource based on SPS configuration information related to DL signal reception.

[0368] The device may determine the second operation duration based on the first time resource and the second time resource. In this case, the device determines the second operation duration by considering not only the first time resource in which actual DL signal reception via the control link is performed, but also the second time resource in which a DL signal may be received via the control link (needing to monitor the DL signal). For example, the device may include the second time resource in the second operation duration by considering that monitoring of the DL signal may be performed even if the DL signal is not actually received via the control link on the second time resource.

[0369] In this case, the device may configure the first beam for the remaining operation duration and the simultaneous operation duration in the first operation duration, respectively, except for the simultaneous operation duration. Fig.10 The device may set the first beam to be the same as the second beam configured for receiving DL signals via the control link during the simultaneous operation duration, and / or to be the same as the second beam configured for receiving DL signals via the control link during the simultaneous operation duration.

[0370] Alternatively, as described in the “Determination of simultaneous operation between the control link and the backhaul link” section, the device may receive indication information about a beam of the backhaul link during the first operation duration. The device may configure the first beam of the backhaul link based on the indication information during the remaining operation durations other than the simultaneous operation duration in the first operation duration. During the simultaneous operation duration, the device may set the first beam as a second beam of the control link for the simultaneous operation duration, which is not based on the indication information.

[0371] Next, the device may receive a DL signal through the backhaul link using the first beam of the backhaul link (S115). The device may send / forward the received DL signal to the UE through the access link formed with the UE. For example, if the device receives a DL signal via the backhaul link during the simultaneous operation duration, the device may set the beam direction of the backhaul link to match the beam direction of the control link configured for the simultaneous operation duration, and then receive the DL signal via the backhaul link.

[0372] Fig.12 is a diagram for explaining a method in which a BS having a control link and a backhaul link with a device configures a beam of a backhaul link.

[0373] Reference Fig.12 , the BS may send configuration information about a first operation duration related to the backhaul link to the device via a control link (S121). As described above, the configuration information may be included in the side control information for controlling the backhaul link sent by the BS to the NCR-MT via the control link. For example, the BS may send the configuration information to instruct / configure the first operation duration of the device to forward the DL signal to the UE.

[0374] Next, the BS may configure a third beam for the backhaul link during the first operation duration (S123). Based on the above scenarios 1 to 3, the BS may set the Tx beam direction corresponding to the Rx beam direction of the implicitly / explicitly indicated DL signal to the third beam (i.e., the Tx beam of the DL signal). Alternatively, the BS may set the third beam to be the same as the Tx beam configured for the control link.

[0375] As described in the "Determination of simultaneous operation between the control link and the backhaul link" section, the BS can configure the third beam of the backhaul link by further considering the existence of a simultaneous operation duration in which a DL transmission operation on the control link and a DL transmission operation on the backhaul link are simultaneously performed. For example, if the simultaneous operation duration exists within the first operation duration, the BS can set / determine the third beam to be the same as the Tx beam of the control link used / configured to transmit DL signals during the simultaneous operation duration. On the other hand, for the remaining operation duration other than the simultaneous operation duration within the first operation duration, the BS can set the Tx beam direction corresponding to the explicitly / implicitly indicated (Rx) beam direction described in scenarios 1 to 3 to the third beam.

[0376] Therefore, as described above, the BS needs to accurately specify / determine a simultaneous operation duration for performing a simultaneous operation within a first operation duration in order to configure the direction of the first beam.

[0377] As described in the "Determination of simultaneous operation between the control link and the backhaul link" section, the BS may determine / specify a first time resource, which is a time resource for a PDSCH scheduled by a DCI included in a PDCCH, and / or a time resource configured for monitoring a DL signal via a control link (e.g., there may be a time resource for sending a DL signal to a device via a control link). For example, the BS may determine / specify a second operation duration based on DCI or RRC configuration information for scheduling a control link DL signal.

[0378] The second time resource may include a time resource configured to monitor at least one of SSB, SIB1, CSI-RS and PDCCH related to the control link. Alternatively, the second time resource may also include a time resource based on SPS configuration information related to the transmission of a DL signal.

[0379] The BS may determine the second operation duration based on the first time resource and the second time resource. In this case, the BS determines the second operation duration by considering not only the first time resource for performing actual DL signal transmission via the control link, but also the second time resource as a time resource configured for monitoring DL signals. For example, if the BS transmits a DL signal to be monitored on the second time resource, the BS may determine the second time resource as the second operation duration for performing a reception operation via the control link, regardless of whether the device actually receives the DL signal.

[0380] Next, the BS may transmit a DL signal through the backhaul link using the third beam of the backhaul link (S125). Here, the DL signal may be a signal forwarded or transmitted by the device to the UE.

[0381] According to the present disclosure, it is possible to clearly define / specify a simultaneous operation duration for a device to simultaneously perform signal transmission and reception operations through a control link and a backhaul link. By clearly specifying the simultaneous operation duration, it is possible to resolve the ambiguity of the beam configuration of the backhaul link between the device as an NCR and the BS. Additionally, by clearly defining the duration for applying indication information indicating the beam of the backhaul link, it is possible to effectively update the beam of the backhaul link according to a predefined rule.

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

[0383] 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.

[0384] 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.

[0385] Fig.13 A communication system applied to the present disclosure is illustrated.

[0386] Reference Fig.13, 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.

[0387] 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.

[0388] 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.

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

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

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

[0392] 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.

[0393] For example, the first wireless device 100 or apparatus may include a processor 102 connected to an RF transceiver 106 and a memory 104. The memory 104 may include a processor capable of executing Figures 9 to 12 At least one procedure of the operations related to the embodiments described in the present invention.

[0394] Specifically, the processor 102 may control the RF transceiver 106 to: receive information about a first operation duration for DL ​​reception through a backhaul link; configure a first beam of the backhaul link for the first operation duration; and receive a DL signal to be forwarded to the UE from the BS based on the first beam of the backhaul link. Based on the second operation duration for receiving DL signals through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link may be set to be the same as the second beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated through the DCI and a second time resource configured for monitoring DL signals.

[0395] Alternatively, a processing device is provided, the processing device being configured to control a device having a control link and a backhaul link formed with a BS, the device having a processor 102 and a memory 104. In this case, the processing device includes: at least one processor and at least one memory, the at least one memory being connected to the at least one processor and storing instructions, which, when executed by the at least one processor, cause the UE to: receive information about a first operation duration for DL ​​reception through a backhaul link; configure a first beam of the backhaul link for the first operation duration; and receive a DL signal to be forwarded to the UE from the BS based on the first beam of the backhaul link. Based on the second operation duration for receiving the DL signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link may be set to be the same as the second beam of the control link for the at least one time resource. The second operation duration may include a first time resource allocated through DCI and a second time resource configured to monitor the DL signal.

[0396] Alternatively, a non-transitory computer-readable storage medium having recorded thereon a method for executing the reference Figures 9 to 12 Instructions for describing the proposed method.

[0397] 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.

[0398] 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.

[0399] 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.

[0400] 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.

[0401] 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.

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

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

[0404] Reference Fig.15 , the wireless devices 100 and 200 may correspond to Fig.14The 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.14 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.14 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.

[0405] 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.13 100a), vehicles ( Fig.13 100b-1 and 100b-2), XR devices ( Fig.13 100c), handheld device ( Fig.13 100d), household appliances ( Fig.13 100e), IoT devices ( Fig.13 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.13 400), BS( Fig.13 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.

[0406] exist Fig.15In 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.

[0407] 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.

[0408] 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.

[0409] 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).

[0410] 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.

[0411] 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.

[0412] 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.

[0413] Industrial Applicability

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

Claims

1. A method for performing communication in a wireless communication system by a device having a control link and a backhaul link formed with a base station BS, the method comprising: receiving information about a first operation duration for the backhaul link; configuring a first beam of the backhaul link for the first operation duration; as well as receiving a downlink signal to be forwarded to a user equipment UE from the BS based on the first beam of the backhaul link, wherein, based on the second operation duration for receiving the downlink signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link is configured to be the same beam as the second beam of the control link for the at least one time resource; The second operation duration includes a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

2. The method according to claim 1, wherein: The second time resource includes a time resource configured to monitor at least one of the following items related to the control link: a synchronization signal block SSB, a system information block 1 SIB1, a channel state information reference signal CSI-RS and a physical downlink control channel PDCCH.

3. The method according to claim 1, further comprising: Indication information indicating a beam used for the backhaul link is received.

4. The method according to claim 3, wherein: Even based on receiving the indication information, the first beam of the backhaul link is configured as the same beam as the second beam for the at least one time resource.

5. The method according to claim 3, wherein: For remaining time resources except the at least one time resource among the time resources included in the first operation duration, the first beam of the backhaul link is configured as the beam indicated by the indication information.

6. The method according to claim 5, wherein: Only for the time resources earlier than the at least one time resource among the remaining time resources, the first beam of the backhaul link is configured as the beam indicated by the indication information.

7. The method according to claim 1, wherein: Based on not receiving indication information indicating the beam used for the backhaul link, for remaining time resources excluding the at least one time resource among the time resources included in the first operation duration, the first beam of the backhaul link is configured as a beam determined based on a predefined rule.

8. The method according to claim 7, wherein: Based on the predefined rule, the first beam of the backhaul link is configured as a beam corresponding to a CORESET with a lowest index among a control resource set CORESET related to the control link.

9. The method according to claim 1, further comprising: The downlink signal is forwarded to the UE via an access link formed with the UE.

10. The method according to claim 1, wherein: The device is a Network Control Repeater NCR. 11 . A non-transitory computer-readable storage medium having recorded thereon instructions for executing the method according to claim 1 .

12. An apparatus configured to perform communication based on a control link and a backhaul link formed with a base station BS in a wireless communication system, the apparatus comprising: Radio frequency RF transceiver; as well as a processor connected to the RF transceiver, Wherein, the processor is configured to: controlling the RF transceiver to receive information about a first operation duration for downlink reception through the backhaul link; configuring a first beam of the backhaul link for the first operation duration; and receiving a downlink signal to be forwarded to a user equipment UE from the BS based on the first beam of the backhaul link, wherein, based on the second operation duration for receiving the downlink signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link is configured to be the same beam as the second beam of the control link for the at least one time resource; The second operation duration includes a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

13. A processing device configured to control a device having a control link and a backhaul link formed with a base station BS in a wireless communication system, the processing device comprising: at least one processor; as well as At least one memory, the at least one memory is connected to the at least one processor and stores instructions, the instructions, upon being executed by the at least one processor, causing a user equipment UE to: receiving information about a first operation duration for downlink reception over the backhaul link; configuring a first beam of the backhaul link for the first operation duration; and receiving a downlink signal to be forwarded to a UE from the BS based on the first beam of the backhaul link, wherein, based on the second operation duration for receiving the downlink signal through the control link overlapping with the first operation duration on at least one time resource, the first beam of the backhaul link is configured to be the same beam as the second beam of the control link for the at least one time resource; The second operation duration includes a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

14. A method for performing communication in a wireless communication system through a base station BS having a control link and a backhaul link formed with a device, the method comprising: transmitting information about a first operation duration for downlink reception over the backhaul link; determining a third beam for transmitting a downlink signal through the backhaul link; as well as transmitting the downlink signal to be forwarded to a user equipment UE to the device based on the third beam of the backhaul link during the first operation duration, wherein, based on the second operation duration for receiving the downlink signal through the control link overlapping with the first operation duration on at least one time resource, the third beam of the backhaul link is determined to be the same beam as the transmit beam of the control link for the at least one time resource, and The second operation duration includes a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

15. A base station BS configured to perform communication based on a control link and a backhaul link formed with a device in a wireless communication system, the BS comprising: Radio frequency RF transceiver; as well as a processor connected to the RF transceiver, Wherein, the processor is configured to: controlling the RF transceiver to transmit information about a first operation duration for downlink reception through the backhaul link; determining a third beam for transmitting a downlink signal through the backhaul link; and transmitting the downlink signal to be forwarded to a user equipment UE to the device based on the third beam of the backhaul link during the first operation duration, wherein, based on the second operation duration for receiving the downlink signal through the control link overlapping with the first operation duration on at least one time resource, the third beam of the backhaul link is determined to be the same beam as the transmit beam of the control link for the at least one time resource, and The second operation duration includes a first time resource allocated through downlink control information and a second time resource configured to monitor the downlink signal.

Images