Method in which device performs communication in wireless communication system and device therefor

Abstract

According to various embodiments, disclosed are a method in which a terminal communicates with a base station and a device therefor, the method having a device for forwarding a forwarding link for forwarding a signal received from a control link in a wireless communication system. Disclosed are a method and an apparatus therefor, the method comprising the steps of: receiving a configuration of a first time resource for performing a forwarding operation of a forwarding link through a control link; receiving resource allocation information on a second time resource that performs transmission of an uplink signal of a control link; and determining whether to perform transmission of the uplink signal prior to the forwarding operation in a second time resource overlapping the first time resource based on the type or payload of the uplink signal.

Description

Technical Field

[0001] A method for a device to perform communication in a wireless communication system and a device 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 to be achieved is to provide a method and apparatus for efficiently performing time division multiplexing (TDM) between a forwarding operation on a forwarding link and a transmission operation of an uplink signal on a control link.

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

[0007] Technical Solution

[0008] According to one aspect of the present disclosure, a method for performing communication by a device is provided herein, wherein a forwarding link and a control link for forwarding a signal received from a user equipment (UE) are formed with a base station (BS) in a wireless communication system, the method comprising: configuring a first time resource for performing a forwarding operation on the forwarding link through the control link; receiving resource allocation information about a second time resource for performing the sending of an uplink signal on the control link; and determining, based on the type or payload of the uplink signal, whether to perform the sending of the uplink signal on the second time resource overlapping with the first time resource in priority to the forwarding operation.

[0009] Alternatively, the transmission of the uplink signal may be performed with priority over the forwarding operation based on the uplink signal including uplink control information (UCI).

[0010] Alternatively, based on the uplink signal including the UCI, the apparatus may determine, based on the resource allocation information, to set the forwarding operation on the first time resource overlapping with the second time resource to be turned off.

[0011] Alternatively, based on the uplink signal not including UCI, the transmission of the uplink signal may be dropped.

[0012] Alternatively, based on the uplink signal being a dynamic grant physical uplink shared channel (DG PUSCH), the transmission of the uplink signal is performed with priority over the forwarding operation.

[0013] Alternatively, based on whether the uplink signal is a configuration grant physical uplink shared channel (CG PUSCH) of type 1 or type 2, transmission of the uplink signal may be performed with priority over the forwarding operation.

[0014] Alternatively, based on the uplink signal being an uplink signal for a random access channel (RACH) procedure, the transmission of the uplink signal may be performed with priority over the forwarding operation.

[0015] Alternatively, the first time resource may be configured through side control information for controlling the forwarding link.

[0016] Alternatively, the forwarding operation on the forwarding link may be skipped on the time resource in which the transmission of the uplink signal is performed.

[0017] Alternatively, the device may be a Network Controlled Repeater (NCR).

[0018] In another aspect of the present disclosure, a device is provided herein, wherein a forwarding link and a control link for forwarding a signal received from a user equipment (UE) are formed with a base station (BS) in a wireless communication system, and the device includes a radio frequency (RF) transceiver and a processor configured to control the RF transceiver. The processor configures a first time resource for performing a forwarding operation on the forwarding link through the control link; receives resource allocation information about a second time resource for performing transmission of an uplink signal on the control link; and determines whether to perform transmission of an uplink signal on a second time resource overlapping with the first time resource in priority to the forwarding operation based on the type or payload of the uplink signal.

[0019] In another aspect of the present disclosure, a chipset for controlling a device is provided herein, wherein a forwarding link and a control link for forwarding a signal received from a user equipment (UE) are formed with a base station (BS) in a wireless communication system, and the chipset includes at least one processor and at least one memory, the at least one memory being operatively connected to the at least one processor and configured to cause the at least one processor to perform operations when executed. These operations include: configuring a first time resource for performing a forwarding operation on a forwarding link through a control link; receiving resource allocation information about a second time resource for performing transmission of an uplink signal on a control link; and determining whether to perform transmission of an uplink signal on a second time resource overlapping with the first time resource in priority to the forwarding operation based on the type or payload of the uplink signal.

[0020] Beneficial Effects

[0021] According to various embodiments, TDM between a forwarding operation on a forwarding link and a transmission operation of an uplink signal on a control link is efficiently performed.

[0022] Alternatively, delay in the control operation of the base station for the device is minimized by exceptionally allowing an uplink transmission operation on the control link in a specific case (even in a time interval of a forwarding operation on the forwarding link).

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

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

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

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

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

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

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

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

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

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

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

[0034] Fig.10 is a diagram illustrating a method in which an apparatus performs a forwarding operation on a forwarding link and performs an uplink transmission operation on a control link.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] [Table 1]

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

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

[0059] [Table 2]

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

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

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

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

[0064] [Table 3]

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

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

[0067] [Table 4]

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

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

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

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

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

[0073] Bandwidth Part (BWP)

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] -interleaverSize: Indicates the interleaver size.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] [Table 5]

[0105]

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

[0107] [Table 6]

[0108]

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

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

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

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

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

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

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

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

[0117] [Table 7]

[0118]

[0119] Next, BWP-DownlinkCommon is the configuration information for configuring the common parameters of DL BWP. That is, 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.

[0120] [Table 8]

[0121]

[0122] Among the above parameters, PDCCH-ConfigCommon may be used to configure cell-specific PDCCH parameters provided through dedicated signaling as well as through SIB. Referring to Table 9, PDCCH-ConfigCommon may include configuration parameters for cell-specific PDCCH.

[0123] [Table 9]

[0124]

[0125]

[0126] PDSCH-ConfigCommon defined in Table 10 is configuration information for configuring a cell-specific PDSCH.

[0127] [Table 10]

[0128]

[0129]

[0130] The IE ServingCellConfigCommon defined in Table 11 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 a synchronization signal block (SSB), MIB, or SIB when accessing a cell in an idle state.

[0131] [Table 11]

[0132]

[0133]

[0134]

[0135] The ServingCellConfigCommonSIB defined in Table 12 may be used to configure cell-specific parameters of the serving cell of the UE in SIB1.

[0136] [Table 12]

[0137]

[0138]

[0139] BWP-UplinkCommon defined in Table 13 may be used to configure common parameters of UL BWP and configure parameters for cell-specific signals.

[0140] [Table 13]

[0141]

[0142] The initialDownlinkBWP defined in Table 14 may be used to configure the initial DL BWP.

[0143] [Table 14]

[0144]

[0145] PUCCH-ConfigCommon defined in Table 15 may be used to configure cell-specific PUCCH parameters.

[0146] [Table 15]

[0147]

[0148] PUSCH-ConfigCommon defined in Table 16 may be used to configure cell-specific PUSCH parameters.

[0149] [Table 16]

[0150]

[0151]

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

[0153] [Table 17]

[0154]

[0155]

[0156] 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 of cell-specific signals or channels and / or transmission resources.

[0157] IAB (Integrated Access / Backhaul)

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

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

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

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

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

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

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

[0165] - Efficient and flexible operation of in-band and out-of-band broadcasts in indoor and outdoor scenarios

[0166] -Multi-hop and redundant connections

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

[0168] -Backhaul link support with high spectral efficiency

[0169] - Legacy NR UE support

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

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

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

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

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

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

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

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

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

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

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

[0181] -DU-Tx / MT-Tx

[0182] -DU-Rx / MT-Rx

[0183] -DU-Tx / MT-Rx

[0184] -DU-Rx / MT-Tx

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

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

[0187] Network Controlled Repeater (NCR) in NR

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

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

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

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

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

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

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

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

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

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

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

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

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

[0201] Side control information for NCR

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

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

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

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

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

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

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

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

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

[0211] NCR can be composed of two parts: NCR mobile terminal (NCR-MT), which is an entity that receives side control information from gNB and reports to gNB; and NCR forwarding (NCR-Fwd), which receives the Tx signal of gNB and forwards the Tx signal to UE, or receives the Tx of UE and forwards the Tx signal to gNB.

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

[0213] -NCR-MT may 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 the NCR-Fwd.

[0214] -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 gNB.

[0215] In the following, a description will be given based on the C link and the backhaul link in the above scenario. Specifically, a method for TDM operation of NCR's Tx on the C link (UL Tx of NCR-MT) and NCR's Tx on the backhaul link (UL Tx of NCR-Fwd) will be described.

[0216] In addition, since cost efficiency is important in NCR of NR, NCR assumes amplify and forward (AF) relay rather than decode and forward (DF) relay. Therefore, since the signal received by NCR-Fwd from the UE and sent to the gNB is simply amplified and forwarded without performing decoding, there may be limitations in sending the Tx signal of NCR-MT together on such Tx resources. For example, in order to multiplex the Rx signal received from the UE and the Tx signal of NCR-MT, NCR-Fwd should know in advance in which time domain / frequency domain or on which resource the Rx signal received from the UE exists, and the Rx signal and Tx signal should also be fully synchronized. However, such identification of the time / frequency resource of the Rx signal and the synchronization matching between the Tx signal and the Rx signal may not be possible in the AF relay. Alternatively, due to the Tx signal strength limitation of the NCR according to the prescribed limit, it may be difficult to perform UL Tx of NCR-Fwd and UL Tx of NCR-MT on the same time resource. In this context, it may be assumed that the UL operations of NCR-Fwd and NCR-MT are performed by TDM.

[0217] In this way, the side control information related to or related to the UL TDM of the NCR-MT and NCR-Fwd received by the NCR, or the previous protocol defined about the side control information, can be related to the opening / closing (on / off) operation of the NCR. Therefore, the UL TDM operation of the NCR-MT and NCR-Fwd or the opening / closing rule of the NCR according to the side control information will be described in detail later.

[0218] Hereinafter, during operation of NCR in an NR environment, side control information indicating UL TDM operation of NCR-MT for sending and receiving control information and NCR-Fwd serving as a relay between UE and gNB, and operation methods of NCR-MT and NCR-Fwd based on the side control information will be proposed.

[0219] UL TDM Operation of NCR

[0220] In the following, although the UL operation of NCR will be described, the UL operation of NCR may be an operation that is independent of the time slot format of NCR. In addition, a description will be given based on the UL TDM operation of NCR-MT and NCR-Fwd. For example, it is assumed that NCR-Fwd does not perform UL Tx on the time resources where NCR-MT performs UL Tx, and NCR-MT does not perform UL Tx on the time resources where NCR-Fwd performs UL Tx. In addition, it is assumed that NCR supports the on / off operation of NCR-Fwd. Here, the on operation of NCR-Fwd means that the Tx of NCR-Fwd takes precedence over the Tx of NCR-MT. For example, even if the gNB indicates that the UL Tx of NCR-MT is on the time resources where NCR-Fwd is set to on, the UL Tx of NCR-MT may not be performed. The off operation of NCR-Fwd means that the Tx of NCR-MT takes precedence over the Tx of NCR-Fwd. For example, on the time resource when NCR-Fwd is set to off, UL Tx of NCR-MT indicated by gNB may be performed, and UL Tx of NCR-Fwd may not be performed. Alternatively, NCR may receive information about the time interval when NCR-Fwd is set to on through the above-mentioned side control information, and assume that NCR-Fwd is indicated to be off instead of the time interval when NCR-Fwd is set to on. Here, the on operation of NCR-Fwd means that the forwarding operation through the forwarding link can be performed, and the off operation of NCR-Fwd means that the forwarding operation through the forwarding link is impossible.

[0221] 1. Scenario 1

[0222] The NCR-MT may receive from the gNB (or BS) an explicit indication of the time intervals or time resources related to the on / off operation of the NCR-Fwd.

[0223] For example, the NCR may receive a semi-static indication of time resource information regarding the on / off of the NCR-Fwd through side control information via RRC and / or operations and management (OAM). Alternatively, the NCR may receive a dynamic indication of the time resource information through a medium access control-control element (MAC-CE) / downlink control information (DCI). Alternatively, the NCR may not only receive a semi-static indication of the time resource information through RRC and / or OAM, but may also receive a dynamic indication of the time resource information through MAC-CE / DCI. Hereinafter, scenario 1 describes in detail a method for determining whether to send a signal (UL signal) of the NCR-MT based on the time resource information regarding the on / off of the NCR-Fwd.

[0224] Regarding the above indication method, the time resource information about turning on / off of NCR-Fwd of the gNB or BS is explained by classifying the time resource information into Case 1 to Case 4.

[0225] Specifically, time resources can be divided into time resources in which NCR-Fwd is indicated as on (Case 1), time resources in which NCR-Fwd is indicated as on but is overwritten by a later indication as off (Case 2), time resources in which NCR-Fwd is indicated as off (Case 3), and time resources in which NCR-Fwd is indicated as off but is overwritten by a later indication as on (Case 4).

[0226] Meanwhile, the above cases 1 to 4 may be applied to a method in which the UL Tx of the NCR-MT and the UL Tx of the NCR-Fwd are configured not to occur simultaneously. Alternatively, when a UL Tx conflict occurs between the NCR-MT and the NCR-Fwd (i.e., when the NCR-MT and the NCR-Fwd perform UL Tx on the same time resource or on overlapping time resources) (although the UL Tx of the NCR-MT and the UL Tx of the NCR-Fwd are configured not to occur simultaneously or are expected not to occur simultaneously), the above cases 1 to 4 may be applied to a method for resolving overlap between the UL Tx of the NCR-MT and the UL Tx of the NCR-Fwd.

[0227] (1) Case 1: gNB indicates that NCR-Fwd is the time resource to be turned on

[0228] In the following, the operation of NCR-MT on the time resources when gNB indicates NCR-Fwd as turned on will be described. In this article, the indication of gNB to NCR-MT may mean an explicit indication through signaling such as RRC / MAC-CE / DCI.

[0229] 1) Alternative 1

[0230] NCR-MT may always determine that UL Tx of NCR-MT is not possible on the time resources where gNB indicates NCR-Fwd is on. Specifically, to ensure TDM operation of NCR-MT and NCR-Fwd, NCR-MT may determine that NCR-MT cannot perform UL Tx on the time resources where gNB explicitly indicates NCR-Fwd is on, or may assume that the time resources for DL ​​Rx have been configured. This indication method may be related to the operation of NCR where it is expected that UL TDM of NCR-MT and NCR-Fwd will be perfectly indicated by the scheduler.

[0231] Meanwhile, depending on the capability or requirement of the NCR, the UL Tx switching operation between the NCR-MT and the NCR-Fwd may be considered at the symbol level and the time slot level. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the symbol level, the UL Tx of the NCR-MT is not performed on the symbol resources where the NCR-Fwd is set to on. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the time slot level, the UL Tx of the NCR-MT may not be performed on the time slot resources including the symbol resources where the NCR-Fwd is set to on.

[0232] Alternatively, if the gNB indicates that the time resources for which NCR-Fwd is on are at the slot level, the NCR may determine that all UL Tx of the NCR-MT overlapping with the slot corresponding to the indicated time resources is always impossible. Therefore, the UL Tx of the NCR-MT may not be performed in the slot corresponding to the indicated time resources. If the gNB indicates that the time resources for which NCR-Fwd is on are at the symbol level, the NCR may determine that all UL Tx of the NCR-MT overlapping with all slots including the symbol corresponding to the indicated time resources is impossible.

[0233] 2) Alternative 2

[0234] Even when NCR-Fwd is set or indicated as on during a time interval, if the time interval is scheduled as a time resource for UL Tx of the NCR-MT, the NCR-MT may assume that NCR-Fwd is set to off during the scheduled time interval.

[0235] Specifically, the NCR-MT may perform UL Tx regardless of whether the BS indicates the time interval for turning on / off of the NCR-Fwd. That is, even when the NCR-Fwd is set to be turned on during the time interval, if the time interval is scheduled as a time resource for UL Tx, the NCR-MT may determine that the NCR-Fwd is indicated to be turned off during the time interval (through the control information for scheduling the UL Tx of the NCR-MT). In this case, the UL Tx of the NCR-Fwd is not performed during the time interval, and the UL Tx of the NCR-MT may be performed. Considering the fact that the UL Tx of the NCR-MT corresponding to the entity that transmits and receives the side control information is relatively important compared to the UL Tx of the NCR-Fwd and the time interval of the UL Tx of the NCR-MT is scheduled by the gNB, the method aims to give priority to the UL Tx of the NCR-MT over the UL Tx of the NCR-Fwd.

[0236] Meanwhile, depending on the capability or requirement of the NCR, the UL Tx switching operation between the NCR-MT and the NCR-Fwd may be considered at the symbol level and the slot level. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the symbol level, the NCR-MT may perform UL Tx by determining that the NCR-Fwd is indicated as turned off for overlapping symbol resources for which the NCR-Fwd is set to on by the UL Tx scheduling of the NCR-MT. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the slot level, the NCR-MT may perform UL Tx of the NCR-MT by determining that the NCR-Fwd is indicated as turned off for overlapping symbol resources for which the NCR-Fwd is set to on by the UL Tx scheduling of the NCR-MT.

[0237] 3) Alternative 3

[0238] Except for Tx of a specific signal / channel of the NCR-MT, the NCR-MT cannot perform UL Tx on a time resource in which the NCR-Fwd is set to on. That is, the NCR-MT can perform Tx of a specific signal / channel by determining that the NCR-Fwd is exceptionally set and / or indicated to be off (through scheduling information for scheduling a specific signal / channel) for a time resource in which the NCR-Fwd is set to on.

[0239] This method is proposed to solve the problem that the Tx of NCR-Fwd is not continuously performed when the UL Tx of NCR-MT always takes precedence over the UL Tx of NCR-Fwd in Alternative Scheme 2. That is, unlike Alternative Scheme 2, Alternative Scheme 3 is a method of giving priority to only the UL Tx of a specific signal / channel of NCR-MT over the UL Tx of NCR-Fwd.

[0240] For example, the NCR-MT may perform UL Tx of the NCR-MT by determining to set NCR-Fwd to off for Tx of the following all or part of the signals / channels. That is, the NCR-MT may perform UL Tx of the following all or part of the signals / channels exceptionally on time resources overlapping with time resources where the NCR-Fwd is set to on.

[0241] -Signals / channels related to the RACH procedure of NCR-MT: For example, the RACH preamble, RACH MsgA preamble, Msg3 PUSCH and MsgA PUSCH of NCR-MT may be considered.

[0242] -Specific PUSCH for NCR-MT: For example, since the dynamic grant (DG) PUSCH is the PUSCH that the gNB has recently scheduled as DCI, the DG PUSCH can be a specific PUSCH. Alternatively, since the type 1 and / or type 2 configuration grant (CG) PUSCH is the PUSCH configured for low latency, the type 1 and / or type 2 CG PUSCH can be a specific PUSCH.

[0243] - ACK / NACK (A / N) feedback Tx of NCR-MT: UL signal of UL A / N feedback Tx for all or some PDSCHs

[0244] - PUSCH or PUCCH with UCI payload according to NCR-MT: Tx of PUSCH and / or PUCCH including Scheduling Request (SR)

[0245] - SRS Tx of NCR-MT: Tx of Sounding Reference Signal (SRS) configured or scheduled for NCR-MT for the purpose of beam management of NCR

[0246] In addition to the above-mentioned specific signals / channels for NCR-MT, NCR can perform Tx of NCR-Fwd for all ULs of NCR-MT only on the time resources where gNB indicates that NCR-Fwd is turned on, and Tx of NCR-MT can be discarded or canceled.

[0247] Meanwhile, depending on the capability or requirement of the NCR, the UL Tx switching operation between the NCR-MT and the NCR-Fwd may be considered at the symbol level and the time slot level. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the symbol level, the NCR-MT may perform the UL Tx of the NCR-MT by indicating the NCR-Fwd as off for overlapping symbol resources for which the NCR-Fwd is set to on by the UL Tx scheduling of the NCR-MT based on the determination that the UL of the NCR-MT is a specific signal / channel. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the time slot level, the NCR-MT may perform the UL Tx of the NCR-MT by indicating the NCR-Fwd as off for the time slot including overlapping symbol resources for which the NCR-Fwd is set to on by the UL Tx scheduling of the NCR-MT based on the determination that the UL of the NCR-MT is a specific signal / channel.

[0248] 4) Alternative 4

[0249] If UL Tx of NCR-MT is expected or predicted on the time resources where NCR-Fwd is set to on, the NCR may assume that NCR-Fwd is set to off for the time resources where NCR-Fwd is set to on.

[0250] Specifically, if the NCR-MT is instructed to perform UL Tx regardless of whether the NCR-MT actually performs UL Tx, or if the time resource on which the NCR-MT is expected to perform UL Tx overlaps with the time resource on which the NCR-Fwd is set to on, the NCR may determine to indicate the NCR-Fwd to be off for the overlapping time resource. Considering the fact that the UL Tx of the NCR-MT corresponding to the entity that transmits and receives the side control information is relatively important compared to the UL Tx of the NCR-Fwd and the time interval of the UL Tx of the NCR-MT is scheduled by the gNB, the method is intended to give priority to the UL Tx of the NCR-MT over the UL Tx of the NCR-Fwd.

[0251] Meanwhile, in Alternative 2, UL Tx of NCR-MT takes precedence over UL Tx of NCR-Fwd only for signals / channels where actual UL Tx occurs. However, in Alternative 4, it is assumed that UL Tx of NCR-Fwd does not take precedence over potential UL Tx of NCR-MT even for UL Tx resources where NCR-MT is expected to perform Tx (even if NCR-MT does not actually perform Tx).

[0252] For example, for a RACH opportunity (RO) at which the NCR-MT can send a RACH configured by the gNB for the NCR and a time resource identified by the periodicity and offset configured for the CG PUSCH, and / or a time resource that explicitly allows the NCR-MT to perform UL Tx, even if the NCR-Fwd is set to on, the NCR may not perform UL Tx of the NCR-Fwd by determining to indicate the NCR-Fwd as off.

[0253] Meanwhile, depending on the capability or requirement of the NCR, the UL Tx switching operation between the NCR-MT and the NCR-Fwd may be considered at the symbol level and the time slot level. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the symbol level, the NCR-MT may determine to indicate the NCR-Fwd as off for symbols where the NCR-Fwd is set to on and overlaps with the time resources of the expected NCR-MT's UL Tx. In this case, the NCR-MT may perform UL Tx on the overlapping time resources. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the time slot level, the NCR-MT may perform UL Tx by determining to indicate the NCR-Fwd as off for (all) time slots including symbols where the NCR-Fwd is set to on and overlaps with the time resources of the expected NCR-MT's UL Tx.

[0254] (2) Case 2

[0255] Case 2 involves handling time resources for which the NCR-MT receives an indication or configuration from the gNB indicating that the NCR-Fwd has been set to on, but the gNB later indicates or sets the NCR-Fwd to off. For example, the time resources may mean time resources for which the NCR-Fwd has been semi-statically indicated or set to on through a signal such as MAC-CE, but later indicated to be off through a dynamic signal such as DCI (i.e., resources indicated to be covered). Here, the indication of the NCR-MT received from the gNB means an explicit indication through signaling such as RRC / MAC-CE / DCI. For example, although the NCR-MT receives an indication or configuration from the gNB through RRC / OAC indicating that the NCR-Fwd is set to on for a specific time resource, the NCR-Fwd is overlappedly indicated as off for the time resource for which the gNB indicated or set the NCR-Fwd to on through MAC-CE / DCI. The following describes the operation of the NCR-MT in the case where the gNB newly indicates that the NCR-Fwd is turned off for the time resources in which the NCR-Fwd is indicated as on.

[0256] 1) Alternative 1

[0257] For resources where NCR-Fwd is set to off, NCR-MT can operate the same regardless of whether the time resources are overlapped. In other words, if NCR-Fwd is indicated or set to off by the gNB after a first time resource, which is a time resource where NCR-Fwd is indicated or set to on by the gNB, then NCR-MT can consider the first time resource to be a time resource where NCR-Fwd is indicated to be off, even if there is an overlapping indication or configuration with the first time resource.

[0258] That is, alternative 1 of case 2 can perform the same operation as that of the NCR-MT in alternatives 1, 2, and 3 of the following case 3. For example, the operation of the NCR-MT on the time resource for which the NCR-Fwd is set to off after being set to on is the same as the operation of the NCR-MT on the time resource for which the NCR-Fwd is set to off. That is, even if the NCR-Fwd is indicated to be changed from on to off for a resource, the NCR can expect that the scheduler will notify such an operation (or only the operation for the indication of off) according to the requirements of the operation.

[0259] 2) Alternative 2

[0260] NCR-MT can operate in consideration of whether the time resource is covered. For example, the UL Tx operation of NCR-MT on the time resource for which NCR-Fwd is set to off can be different from the UL Tx operation of NCR-MT on the time resource for which NCR-Fwd has been set to on but is later covered to off.

[0261] In other words, NCR-MT can perform different operations on time resources that are set to be off after NCR-Fwd is set to be on and on time resources that are set to be off. For example, NCR-MT can consider its operation based on one of Alternatives 1, 2, and 3 of Case 3 described later for time resources that are set to be off after NCR-Fwd is set to be on and for time resources that are set to be off.

[0262] In addition, the operation of NCR-MT may differ depending on the timeline requirements of NCR. Specifically, the timeline requirements of NCR-MT and the timeline requirements of NCR-Fwd may be considered separately or together. The timeline requirements of NCR-MT may be related to the preparation time required for Tx (e.g., Tx timeline requirements). For example, existing timeline requirements such as PUSCH preparation time for NCR-MT may be applied to resources for which the gNB sets NCR-Fwd to off. Alternatively, timeline requirements such as PUSCH preparation time for NCR-MT may not be applied to resources for which NCR-Fwd has been set to on by the gNB but is later set back to off according to the instructions of the gNB. Alternatively, if the timeline requirements of NCR-MT are not met for resources for which NCR-Fwd has been set to on by the gNB but is later set to off according to the instructions of the gNB, the NCR-MT may not perform ULTx even if NCR-Fwd is set to off. Alternatively, the first timeline requirement for the time resource in which the NCR-Fwd is set to be turned off from the beginning and the second timeline requirement for the time resource in which the NCR-Fwd has been set to be turned on according to the instruction of the gNB but is later set to be turned off may be different from each other. For example, the first timeline requirement may be set to a shorter time than the second timeline requirement.

[0263] In addition, the UL Tx operation of the NCR-MT may be different depending on the timeline requirements for turning on / off the NCR-Fwd. For example, a transition time may be required to switch the UL TX of the NCR-Fwd from on to off, or the time required for the NCR-Fwd may be required to activate the RF. The NCR-MT may previously report information about the timeline requirements related to such on / off operation of the NCR-Fwd to the gNB through RRC / MAC-CE / UCI, etc. Therefore, the gNB may expect that the UL Tx of the NCR-MT may be performed on the time resources where the NCR-Fwd is set to off. However, the gNB may predict that the NCR-Fwd may not be set to off due to reasons such as timeline requirements for time resources that are indicated as off after the NCR-Fwd is set to on, or predict that the UL Tx of the NCR-MT may not be performed even if the NCR-Fwd is set to off.

[0264] (3) Case 3

[0265] Case 3 involves UL Tx operation of NCR-MT on time resources where the gNB indicates NCR-Fwd as off.

[0266] 1) Alternative 1

[0267] NCR-MT can always perform UL Tx on the time resources where the gNB indicates or sets NCR-Fwd to be off. That is, in order to ensure the TDM operation of NCR-MT and NCR-Fwd, NCR-MT can determine that UL Tx of NCR-MT can always be performed on the time resources where the gNB explicitly indicates NCR-Fwd to be off.

[0268] Meanwhile, depending on the capability or requirement of the NCR, the UL Tx switching operation between the NCR-MT and the NCR-Fwd may be considered at the symbol level and the timeslot level. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the symbol level, the NCR-MT may always perform UL Tx of the NCR-MT on overlapping symbol resources for which the NCR-Fwd is set to off for UL Tx scheduling by the NCR-MT. If the UL Tx switching operation between the NCR-MT and the NCR-Fwd is possible at the timeslot level, the NCR-MT may always perform UL Tx of the NCR-MT for timeslots including overlapping symbol resources for which the NCR-Fwd is set to off for UL Tx scheduling by the NCR-MT.

[0269] 2) Alternative 2

[0270] Even when NCR-Fwd is set to off for a time resource, the NCR-MT may perform UL Tx only on that time resource only if there is an additional or separate indication.

[0271] Specifically, the NCR-MT may receive an indication of the periodicity and / or offset of the time intervals in which Tx is expected to be performed from the gNB via RRC / MAC-CE / DCI at the symbol level or the time slot level. It may be considered that the UL Tx of the NCR-MT is performed only on the time resources for which the NCR-Fwd is set to be turned off in the time intervals in which the NCR-MT Tx is expected to be performed according to such indication of the gNB. In other words, for the UL Tx of the NCR-MT, the gNB may be required to (explicitly) indicate the NCR-Fwd as the time resource for turning off and the time intervals in which the UL Tx of the NCR-MT is allowed.

[0272] Alternatively, even for time resources where NCR-Fwd is set to off, it can be considered that NCR-MT performs UL Tx only for specific signals / channels. For example, even if NCR-Fwd is set to off, NCR-MT can perform UL Tx of NCR-MT for Tx of all or part of the following signals / channels. In other words, even if there are time resources where NCR-Fwd is set to off, NCR-MT can allow UL Tx only for specific signals / channels described below.

[0273] -Signals / channels related to the RACH procedure of NCR-MT: For example, the RACH preamble, RACH MsgA preamble, Msg3 PUSCH and MsgA PUSCH of NCR-MT may be considered.

[0274] -Specific PUSCH of NCR-MT: For example, since DG PUSCH is the PUSCH that the gNB relatively recently scheduled as DCI, DG PUSCH can be a specific PUSCH. Alternatively, since Type 1 and / or Type 2CG PUSCH is a PUSCH configured for low latency, Type 1 and / or Type 2CG PUSCH can be a specific PUSCH.

[0275] - A / N feedback Tx of NCR-MT: UL signal of UL A / N feedback Tx for all or some PDSCHs.

[0276] - PUSCH or PUCCH with UCI payload according to NCR-MT: Tx of PUSCH and / or PUCCH including SR.

[0277] - SRS Tx of NCR-MT: SRS Tx configured or scheduled for NCR-MT for the purpose of beam management of NCR

[0278] 3) Alternative 3

[0279] Even for a time resource for which NCR-Fwd is set or indicated as off, if cell-specific UL forwarding is expected to be performed by NCR-Fwd, the NCR-MT may determine that NCR-Fwd is set to on for the time resource. Here, the cell-specific UL may be the UL defined in Tables 7 to 17. In other words, even when NCR-Fwd is set to off for a time resource, if NCR-Fwd is expected to perform UL forwarding of a cell-specific signal on the time resource, the NCR-MT may determine that NCR-Fwd is exceptionally set to on within the time resource.

[0280] In this case, the NCR-MT cannot perform UL Tx in the time interval where the NCR-Fwd is indicated or set to on by the gNB or on the time resources expected to require cell-specific UL forwarding (resources on which the UE with cell-specific configuration is expected to perform or be able to perform UL Tx). For example, the time resources expected to require cell-specific UL forwarding can be predicted based on the cell-specific configured RO and / or the time resource information of the cell-specific (or cell-common) UL Tx scheduling for the UE (see Tables 7 to 17). That is, for the time resources for which the UE is expected or predicted to perform UL Tx configured by cell-specific, cell-common, or UE group-common, the NCR-MT may consider or determine that the gNB has indicated NCR-Fwd as on. If the expected time resources (the time resources for which the gNB expects or predicts that the UE is to perform UL Tx configured by cell-specific, cell-common, or UE group-common) are indicated at the symbol level, the NCR may determine or consider that the gNB indicates NCR-Fwd as on for all time slots including the symbol as the expected time resource.

[0281] In other words, the NCR or NCR MT can predict the time / frequency resources on which the cell-specific signals for the UE are to be sent through system information or RRC configuration information received from the gNB or BS, and can consider that the NCR-Fwd is set to on for the expected resources (which are the predicted time / frequency resources) or the expected time resources, even if the gNB does not separately indicate the NCR-Fwd as on for the expected resources or the expected time resources (or even if the NCR-Fwd is indicated as off).

[0282] (4) Case 4

[0283] Case 4 involves time resources where NCR-Fwd has been indicated as OFF by the gNB but is later overridden as ON based on the gNB’s indication.

[0284] 1) Alternative 1

[0285] The NCR-MT may operate corresponding to the operation of the NCR-MT for a resource for which the NCR-Fwd is set to on, regardless of whether the resource is covered. For example, the NCR-MT may perform an operation corresponding to the operation of the NCR-MT in Alternatives 1, 2, 3, and 4 of the above-mentioned Case 1. That is, the operation of the NCR-MT for a time resource that is set to on after the NCR-Fwd is set to off may be the same as the operation for a time resource for which the NCR-Fwd is set to on.

[0286] 2) Alternative 2

[0287] NCR-MT may operate differently depending on whether NCR-Fwd is overridden as on / off. For example, the Tx operation of NCR-MT for a time resource where NCR-Fwd is set to on may be different from the Tx operation of NCR-MT for a time resource where NCR-Fwd has been set to off but is later overridden as on.

[0288] In addition, the operation of NCR-MT may be different depending on the timeline requirements of NCR. Specifically, the timeline requirements of NCR-MT and the timeline requirements of NCR-Fwd may be considered separately or together. The timeline requirements of NCR-MT may be related to the Tx timeline requirements. For example, since the UL Tx of NCR-MT is not expected for resources for which the gNB sets NCR-Fwd to on, the timeline requirements of NCR-MT are not considered. However, for resources for which NCR-Fwd has been set to off by the gNB but is later set back to on according to the instructions of the gNB, the timeline requirements for canceling the UL Tx of NCR-MT may be additionally considered. In this case, if the timeline requirements of NCR-MT are not met, even if NCR-Fwd is set to on, the UL Tx operation of NCR-MT may be performed without performing UL Tx of NCR-Fwd.

[0289] In addition, the UL Tx operation of the NCR-MT may be different depending on the timeline requirements for turning on / off the NCR-Fwd. For example, a transition time may be required to switch the NCR-Fwd from off to on, or time may be required to deactivate the RF. In this case, the NCR-MT may have previously reported information about the timeline requirements for the turning on / off operation of the NCR-Fwd (e.g., information about the transition time) to the gNB through RRC / MAC-CE / UCI, etc. The gNB may predict that UL Tx of the NCR-Fwd will not be performed for the time resources indicating the switch from turning off the NCR-Fwd to turning on the NCR-Fwd based on the reported information. Alternatively, the gNB may predict that UL Tx of the NCR-MT will be performed instead of the operation of the NCR-Fwd on the time resources where the NCR-Fwd is indicated or set to turn on from off based on the reported information.

[0290] 2. Scenario 2

[0291] In scenario 2, the NCR-MT may not receive an explicit indication of the time interval or time resources for performing the on / off operation of NCR-Fwd from the gNB.

[0292] Since indicating the time resource / time interval related to the on / off operation of the NCR-Fwd each time may cause signaling overhead, the time resource / time interval related to the on / off operation of the NCR-Fwd may be implicitly determined or configured based on a combination of various types of side control information (e.g., beamforming information, TDD configuration, power control information, etc.). Alternatively, the NCR may implicitly determine the time resource / time interval related to the on / off operation of the NCR-Fwd based on the operation of the NCR-MT such as whether the NCR-MT performs Tx. The time resource / time interval related to the on / off operation of the NCR-Fwd may be determined or configured based on the time interval or time resource for performing UL Tx of the NCR-MT (or depending on whether the NCR-MT performs Tx or operation).

[0293] Hereinafter, whether to perform UL Tx of NCR-MT and whether to set NCR-Fwd to on / off will be described. The following alternatives can be applied to two cases. First, the following alternatives can be applied to ensure that simultaneous UL Tx operation of NCR-MT and NCR-Fwd does not occur. Second, when simultaneous UL Tx operation of NCR-MT and NCR-Fwd is configured not to occur, or when a conflict occurs between the UL Tx operations of NCR-MT and NCR-Fwd (i.e., when NCR-MT and NCR-Fwd attempt to perform UL Tx on the same time resource or overlapping time resources), in order to resolve the conflict, the following alternatives can be applied.

[0294] 1) Alternative 1

[0295] The NCR may determine to indicate NCR-Fwd as OFF for resources where UL Tx of NCR-MT is actually performed, and indicate NCR-Fwd as ON for remaining resources (time resources where UL Tx of NCR-MT is not actually performed).

[0296] Specifically, the NCR may confirm whether the NCR-Fwd is set to on / off, and set the NCR-Fwd to on for all time resources by default. That is, if the NCR fails to receive a separate indication of whether the NCR-Fwd is set to on / off, the NCR may determine that the NCR-Fwd is set to on for all time resources, but determines that the NCR-Fwd is set to off (or indicated as off) only for the time interval in which the UL Tx of the NCR-MT is performed.

[0297] Depending on the configuration of NCR-MT and NCR-Fwd, the following options may be considered. The NCR may consider setting NCR-Fwd to off only for symbols in which UL Tx of NCR-MT is performed. Alternatively, the NCR may determine to set NCR-Fwd to off for a time resource including a time interval of a symbol in which UL Tx of NCR-MT is performed and a time interval for switching the on / off operation of NCR-Fwd. For example, if UL Tx of NCR-MT is indicated for the third symbol, the fourth symbol, the fifth symbol, the sixth symbol, and the seventh symbol of a specific time slot, and NCR-Fwd requires a transition time of 2 symbols to switch from on to off (and / or NCR-Fwd requires a transition time of 1 symbol to switch from off to on), the NCR may determine to set NCR-Fwd to off for the first symbol, the second symbol, the third symbol, the fourth symbol, the fifth symbol, the sixth symbol, and the seventh symbol of the time slot (while performing UL Tx of NCR-MT for the third symbol, the fourth symbol, the fifth symbol, the sixth symbol, and the seventh symbol of the time slot).

[0298] Alternatively, the NCR may determine to set NCR-Fwd to OFF for all slots including symbols in which UL Tx of the NCR-MT is performed. Alternatively, the NCR may determine to set NCR-Fwd to OFF for time resources including time intervals of all slots including symbols in which UL Tx of the NCR-MT is performed and time intervals required for switching the ON / OFF operation of the NCR-Fwd. For example, if UL Tx of the NCR-MT is indicated for the third symbol, the fourth symbol, the fifth symbol, the sixth symbol, and the seventh symbol in the i-th slot, the transition time required to switch the NCR-Fwd from ON to OFF is 2 symbols, and the transition time required to switch the NCR-Fwd from OFF to ON is 1 symbol, the NCR-MT may perform UL Tx in the third symbol, the fourth symbol, the fifth symbol, the sixth symbol, and the seventh symbol of the i-th slot, but may set NCR-Fwd to OFF in the last two symbols of the (i-1)th slot, the entirety of the i-th slot, and the first symbol of the (i+1)th slot.

[0299] 2) Alternative 2

[0300] NCR may determine to set NCR-Fwd to off even for time resources where UL Tx of NCR-MT is expected or predicted, and always set NCR-Fwd to on for all remaining time resources except the expected / predicted time resources.

[0301] That is, for whether NCR-Fwd is set to on / off, the NCR may determine by default that NCR-Fwd is set to on for all time resources. In addition, the NCR may determine that NCR-Fwd is indicated as off even for time resources indicating that the NCR-MT is capable of performing UL Tx or that the NCR-MT is expected to perform UL Tx, regardless of whether the NCR-MT actually performs UL Tx. Considering the fact that the UL Tx of the NCR-MT corresponding to the entity that sends and receives the side control information is relatively important compared to the UL Tx of the NCR-Fwd and the time interval of the UL Tx of the NCR-MT is scheduled by the gNB, the method aims to give priority to the UL Tx of the NCR-MT over the UL Tx of the NCR-Fwd. In Alternative Scheme 1, UL Tx of NCR-MT takes precedence over UL Tx of NCR-Fwd only for signals / channels where UL Tx is actually performed, whereas in Alternative Scheme 2, UL Tx of NCR-MT may take precedence over UL Tx of NCR-Fwd even for time resources where UL Tx of NCR-MT is predicted or expected to be performed (i.e., potential UL Tx of NCR-MT).

[0302] For example, the NCR may determine or consider the time resources for UL Tx of the expected NCR-MT (such as the time resources configured as RO, which are the RACH Tx resources of the NCR-MT configured by the gNB or the periodicity and offset configured for the CG PUSCH) and / or explicitly allow the time resources for UL Tx of the NCR-MT, indicating the NCR-Fwd as off.

[0303] Alternatively, if the time resource for which the gNB indicates that NCR-Fwd is turned on is at a time slot level, the NCR may determine to set NCR-Fwd to off for a time slot including some symbols overlapping with a time interval for UL Tx in which NCR-MT may occur among the time slots of the time resource. Alternatively, if the gNB indicates that NCR-Fwd is turned on is at a symbol level, the NCR may determine to set NCR-Fwd to off for a symbol overlapping with a time interval for UL Tx in which NCR-MT may occur or a time slot including a symbol among the symbols indicated as the time resource.

[0304] Fig.10 is a diagram illustrating a method in which an apparatus performs a forwarding operation on a forwarding link and a UL Tx operation on a C link.

[0305] As described above, the device may correspond to an NCR including an NCR-MT that receives control information or transmits a UL signal through a C link formed with a BS or a gNB, and an NCR-Fwd that relays or amplifies an Rx signal (or an Rx UL signal) received from a UE and forwards the Rx signal to the BS through a forwarding link. In addition, as described above, the device may perform a forwarding operation on a forwarding link or a Tx operation of a UL signal on a C link based on TDM. For example, the device may not perform a forwarding operation and a Tx operation of a UL signal at the same time.

[0306] Hereinafter, for the sake of convenience of explanation, UL Tx of NCR-MT is defined as Tx of UL signal or Tx operation of UL signal on C link, and on / off of NCR-Fwd is defined as on / off of forwarding operation on forwarding link. Here, on-operation of forwarding includes not only the operation of actually performing forwarding of received Rx signal, but also the standby condition of enabling forwarding of Rx signal.

[0307] Reference Fig.10 , the device may configure a first time resource for performing a forwarding operation on a forwarding link (S101). As described above, the first time resource may be configured or determined based on side control information about the forwarding link received from the BS through the C link or separate time resource allocation information about the on period of the forwarding operation. In addition, as described above, the device may be configured with the first time resource through RRC signaling, or may be dynamically configured with the first time resource through DCI or MAC CE.

[0308] Next, the device may receive scheduling information or resource allocation information (or control information including scheduling information or resource allocation information) about a UL signal to be sent on the C link (S103). The resource allocation information may include information about a second time resource (or multiple second time resources) for sending a UL signal to the BS on the C link. For example, the device may receive the resource allocation information through DCI sent by the BS, etc.

[0309] Meanwhile, the first time resource on which the device expects to perform forwarding operation and the second time resource for transmitting UL signal will be subject to TDM. However, in the case where the first time resource and the second time resource partially or completely overlap, it is necessary to define which operation should be prioritized.

[0310] As described above (particularly Alternative 3 in Case 1 of Scenario 1), the device may determine whether to perform Tx of the UL signal on a second time resource overlapping with the first time resource based on the type of the UL signal scheduled by the resource allocation information or based on the payload included in the UL signal (S105).

[0311] For example, if the UL signal includes a specific type or a specific payload of the UL signal, the device can discard or cancel the Tx of the UL signal by prioritizing the forwarding operation. Alternatively, if the UL signal is not a specific type of UL signal or (and / or) does not contain a specific payload, the device can discard or cancel the Tx of the UL signal by prioritizing the forwarding operation.

[0312] Here, the specific type of UL signal may be (or may be preset to be) at least one of a UL signal related to performing a RACH process (MsgA (MsgAPRACH or PUSCH), Msg1, or Msg3), a UL signal based on DG scheduling (e.g., DG PUSCH), a UL signal based on CG scheduling (e.g., CG PUSCH), or a configured SRS of an NCR-MT for beam management purposes. In addition, the specific payload may be UCI including SR or CSI information, or may be A / N feedback information for a received PDSCH.

[0313] For example, if the UL signal to be sent on the C link includes UCI, the device may send the UL signal in priority to the forwarding operation even on the second time resource overlapping with the first time resource. That is, the device may determine or assume that the forwarding operation for the first time resource overlapping with the second time resource is indicated or set to be closed by including control information for scheduling resource allocation information of the UL signal including UCI. In this case, the device may give priority to performing Tx of the UL signal on the second time resource without performing the forwarding operation. On the contrary, if the UL signal to be sent on the C link does not include UCI, the device may give priority to the forwarding operation and discard or cancel the Tx of the UL signal. Here, the execution of the forwarding operation includes not only the operation of actually performing the forwarding of the received Rx signal, but also a standby state for forwarding the Rx signal. That is, if the UL signal to be sent on the C link does not include UCI, the device may maintain the on state of the NCR-Fwd associated with the forwarding link to enable forwarding on the forwarding link without performing Tx of the UL signal.

[0314] Alternatively, if the UL signal to be sent on the C link is MsgA PRACH, MsgA PUSCH, DG PUSCH, CGPUSCH, PUCCH or SRS, the device may send the UL signal in priority to the forwarding operation even on the second time resource overlapping with the first time resource. That is, the device may set the NCR-Fwd (or wireless unit) related to the forwarding operation to be turned off and perform Tx of the UL signal. On the contrary, if the UL signal to be sent on the C link is not a UL signal of the type MsgA PRACH, MsgA PUSCH, DG PUSCH, CG PUSCH, PUCCH or SRS, the device may cancel or discard the Tx of the UL signal and maintain the NCR-Fwd in the on state.

[0315] In this way, the device performs a forwarding operation that takes precedence over a Tx operation of a UL signal in a time interval configured or indicated by the BS, but for Tx of a specific UL signal or a UL signal including a specific payload, the Tx operation of the UL signal can be exceptionally prioritized over the forwarding operation. In this case, although the forwarding operation in a time interval predictable by the BS is guaranteed, by exceptionally allowing Tx of a specific UL signal in a time interval overlapping with the above time interval, the degradation of service requirements and service quality caused by Tx delay of the UL signal is minimized.

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

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

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

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

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

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

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

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

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

[0325] Reference Fig.12 , 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.11 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

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

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

[0328] Specifically, the processor can report capability information related to the beam configuration of the backhaul link to the BS through the control link, configure a first time resource on which a forwarding operation on the forwarding link is performed through the control link, receive resource allocation information about a second time resource on which the sending of an uplink signal on the control link is performed, and determine whether to perform the sending of an uplink signal on the second time resource overlapping with the first time resource in preference to the forwarding operation based on the type or payload of the uplink signal.

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

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

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

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

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

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

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

[0336] Reference Fig.13 , the wireless devices 100 and 200 may correspond to Fig.12The wireless devices 100 and 200 may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.12 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.12 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

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

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

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

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

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

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

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

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

[0345] Industrial Applicability

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

Claims

1. A method for performing communication by a device in a wireless communication system, in which a forwarding link for forwarding a signal received from a base station and a control link and a terminal is formed in the device, the method comprising: configuring, through the control link, a first time resource for performing a forwarding operation on the forwarding link; receiving resource allocation information of a second time resource for performing transmission of an uplink signal for the control link; as well as Based on the type or payload of the uplink signal, it is determined whether to perform the transmission of the uplink signal in priority to the forwarding operation in the second time resource overlapping with the first time resource.

2. The method according to claim 1, wherein: The transmitting of the uplink signal is performed with priority over the forwarding operation based on that the uplink signal includes UCI (Uplink Control Information).

3. The method according to claim 2, wherein: Based on the uplink signal including the UCI, the apparatus determines, based on the resource allocation information, to set the forwarding operation on the first time resource overlapping with the second time resource to be turned off.

4. The method according to claim 2, wherein: Based on the uplink signal not including the UCI, the sending of the uplink signal is dropped.

5. The method according to claim 1, wherein: The transmitting of the uplink signal is performed with priority over the forwarding operation based on that the uplink signal is a DG PUSCH (Dynamic Grant Physical Uplink Shared Channel).

6. The method according to claim 1, wherein: The transmitting of the uplink signal is performed with priority over the forwarding operation based on that the uplink signal is a CGPUSCH (Configuration Grant Physical Uplink Shared Channel) of type 1 or type 2.

7. The method according to claim 1, wherein: The transmitting of the uplink signal is performed with priority over the forwarding operation based on that the uplink signal is an uplink signal for a RACH (Random Access Channel) procedure.

8. The method according to claim 1, wherein: The first time resource is configured by side control information used to control the forwarding link.

9. The method according to claim 1, wherein: The transmission operation of the uplink signal in the control link is not performed in a time resource in which the forwarding operation in the forwarding link is performed.

10. The method according to claim 1, wherein: The device is an NCR (Network Controlled Repeater).

11. A non-transitory computer-readable medium recording a program code, wherein the program code is used to execute the method according to claim 1.

12. An apparatus for forming a control link connected to a base station and a forwarding link for forwarding a signal received from a user equipment in a wireless communication system, the apparatus comprising: RF (radio frequency) transceiver; as well as a processor connected to the RF transceiver, Wherein, the processor is configured to: configuring, through the control link, a first time resource for performing a forwarding operation on the forwarding link; receiving resource allocation information of a second time resource for performing transmission of an uplink signal for the control link; and Based on the type or payload of the uplink signal, it is determined whether to perform the transmission of the uplink signal in priority to the forwarding operation in the second time resource overlapping with the first time resource.

13. The device according to claim 12, wherein: The transmitting of the uplink signal is performed with priority over the forwarding operation based on that the uplink signal includes UCI (Uplink Control Information).

14. The device according to claim 12, wherein: Based on the uplink signal including the UCI, the apparatus determines, based on the resource allocation information, to set the forwarding operation on the first time resource overlapping with the second time resource to be turned off.

15. A chipset for a control device, wherein a control link connected to a base station and a forwarding link for forwarding a signal received from a terminal are formed in a wireless communication system, the chipset comprising: at least one processor; as well as at least one memory operatively connected to the at least one processor and configured to, when executed, cause the at least one processor to perform operations, The operations include: configuring, through the control link, a first time resource for performing a forwarding operation on the forwarding link; receiving resource allocation information of a second time resource for performing transmission of an uplink signal for the control link; and Based on the type or payload of the uplink signal, it is determined whether to perform the transmission of the uplink signal in priority to the forwarding operation in the second time resource overlapping with the first time resource.

Images